Opened 4 years ago

Last modified 4 months ago

#31583 new New feature

Extend deferred unique constraint support to OneToOneField

Reported by: BorisZZZ Owned by: nobody
Component: Database layer (models, ORM) Version: dev
Severity: Normal Keywords: DEFERRED
Cc: Ian Foote, Petr Přikryl Triage Stage: Someday/Maybe
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


Support for DEFERRABLE INITIALLY DEFERRED was added in . It would be great if it could be extended to the implicit Unique constraint generated by OneToOneField, say, by adding an argument:
OneToOneField(OtherModel, defer=models.Deferrable.DEFERRED)

Change History (5)

comment:1 by Simon Charette, 4 years ago

Triage Stage: UnreviewedSomeday/Maybe

Not sure we should do that as it seems pretty niche.

I guess an alternative API could be to allow passing a UniqueConstraint to the unique kwarg like we've discussed doing to the Field.index one.


OneToOneField(OtherModel, unique=UniqueConstraint(defer=models.Deferrable.DEFERRED))

comment:2 by Ian Foote, 3 years ago

Cc: Ian Foote added

comment:3 by Petr Přikryl, 3 years ago

Cc: Petr Přikryl added

comment:4 by Petr Přikryl, 3 years ago

comment:5 by jefflieb-wavy, 4 months ago

There is a use case for this, ordering of database rows using a linked list. OneToOne can be used to define the field pointing to the previous row, but the associated constraint needs to be deferred to allow for updates that temporarily violate the constraint while changing the row ordering.

We were able to implement this, but it involved a workaround. Specifically we had to manually delete the constraint created by the OneToOne and then recreate it with deferred in our migrations, then add that constraint to the model definition also.

Note: See TracTickets for help on using tickets.
Back to Top