#30210: Allow empty strings of blank=True model fields to pass unique_together
constraint
-------------------------------------+-------------------------------------
Reporter: Spleeding1 | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: unique_together, | Triage Stage:
Models | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => wontfix
* component: Uncategorized => Database layer (models, ORM)
* type: Uncategorized => New feature
Comment:
A solution would require Django to change input data from empty strings to
nulls. This would be backwards incompatible and often undesired. See
[https://stackoverflow.com/questions/5772176/django-unique-together-and-
blank-true stackoverflow] for possible solutions you can implement for the
use case.
--
Ticket URL: <https://code.djangoproject.com/ticket/30210#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.99430fda7d7527def99cc44343fc2c1b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
