#29051: unique_together behavior undocumented changes in 1.11
----------------------------------------------+------------------------
Reporter: Christian Pedersen | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.11
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
----------------------------------------------+------------------------
In Django 1.10 unique_together would take complain even if a field was
null.
In 1.11 this changed so that it uses the database style, in this case
Postgres.
The only thing in the release notes is:
On Oracle, Model.validate_unique() no longer checks empty strings for
uniqueness as the database interprets the value as NULL.
no mention of Postgres.
--
Ticket URL: <https://code.djangoproject.com/ticket/29051>
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/051.a2e33472520569a076f9a0d94621913c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
