#33901: non-deterministic collations doesn't work with Unique=True on
Postgres13.3
-------------------------------------+-------------------------------------
Reporter: DrChai | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: dev
Severity: Normal | Resolution:
Keywords: collation unique | Triage Stage: Accepted
citext |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* version: 4.0 => dev
* stage: Unreviewed => Accepted
Comment:
Closely related if not a duplicate of #24082 but since `db_collation` is
the documented way off the now deprecated `contrib.postgres.CIText` I
think it's worth keeping the two issue distinct for now.
Could we have the Postgres schema editor not create these `opclass`
indexes when a custom `db_collation` is specified until we get a consensus
on #24082?
--
Ticket URL: <https://code.djangoproject.com/ticket/33901#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/0107018274ec7808-4c846c5f-cd8d-45da-a990-43e347a41b72-000000%40eu-central-1.amazonses.com.
