#31583: Extend deferred unique constraint support to OneToOneField
-------------------------------------+-------------------------------------
Reporter: BorisZZZ | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: DEFERRED | Triage Stage:
| Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* stage: Unreviewed => Someday/Maybe
Comment:
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.
e.g.
{{{#!python
OneToOneField(OtherModel,
unique=UniqueConstraint(defer=models.Deferrable.DEFERRED))
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31583#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.0ff73c630eb6bcb1215405109303515c%40djangoproject.com.
