#33901: non-deterministic collations doesn't work with Unique=True on
Postgres13.3
-------------------------------------+-------------------------------------
Reporter: Ed Chai | Owner: Ed Chai
Type: Bug | Status: closed
Component: Migrations | Version: dev
Severity: Normal | Resolution: fixed
Keywords: collation unique | Triage Stage: Ready for
citext | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Ed Chai):
Replying to [comment:9 Ismael ABBO]:
> Replying to [comment:8 Tim Graham]: Thanks for that information!
> Then, is there any workaround for 3.2.x versions?
> > Yes, the fix will only be applied for Django 4.2. Since the bug isn't
a regression from a previous release or a major bug in a new feature it
won't be backported. See our
[https://docs.djangoproject.com/en/dev/internals/release-process
/#supported-versions supported versions policy].
You can keep using `CITEXT`, or set unique constraints directly via psql
terminal.
--
Ticket URL: <https://code.djangoproject.com/ticket/33901#comment:11>
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/01070183f5b416f6-397176bb-bece-450c-b451-69a8ee336879-000000%40eu-central-1.amazonses.com.
