#35002: nulls_distinct not honored for ALTER
-------------------------------------+-------------------------------------
Reporter: Peter Thomassen | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* stage: Unreviewed => Accepted
Comment:
Definitely a release blocker thanks for testing against the release
candidate.
Please submit a PR with the proposed changes and a regression test. I'd
suggest making the `includes` change in a distinct commit as this feature
was added in 3.2 and thus I don't think it will qualify for a backport.
--
Ticket URL: <https://code.djangoproject.com/ticket/35002#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/0107018c1ca42cfb-b0bb4e5a-b6db-4f0b-9b01-89f33b391e0c-000000%40eu-central-1.amazonses.com.
