#34949: Fails to create unique constraints
-------------------------------------+-------------------------------------
Reporter: Roman Odaisky | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by David Sanders):
* stage: Unreviewed => Accepted
Comment:
Hey thanks for the report!
Accepting though I don't know whether this will end up being a
documentation change or behaviour change. I agree the behaviour is
inconsistent between indexes & constraints, though there may be a few
factors to consider here and other team members will weigh in on whether
making the behaviour consistent is a desirable outcome. (If we do change
behaviour this ticket may need to be split in 2 as `nulls_distinct` is a
new Django 5.0 feature.)
--
Ticket URL: <https://code.djangoproject.com/ticket/34949#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/0107018ba86035f6-b21ffda3-5d92-4519-9c67-769537806e9b-000000%40eu-central-1.amazonses.com.
