#30972: USERNAME_FIELD UniqueConstraint option
-------------------------------------+-------------------------------------
Reporter: Iman Kermani | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: AbstractUser | Triage Stage:
UniqueConstraint | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* status: new => closed
* resolution: => duplicate
* version: 2.2 => 3.0
* component: contrib.auth => Database layer (models, ORM)
Comment:
On PostgreSQL you should be able to implement this with
[https://docs.djangoproject.com/en/3.0/ref/contrib/postgres/constraints/#exclusionconstraint
ExclusionConstraint] (available from Django 3.0). As far as I'm concerned
they are not available on other databases.
Duplicate of #29824.
--
Ticket URL: <https://code.djangoproject.com/ticket/30972#comment:2>
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.6cf295b47b6f20652fcd98f7c1acf905%40djangoproject.com.
