#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 Simon Charette):
Ismael, the only way to work around the issue on Django 3.2 would to be
subclass the postgres `SchemaEditor` to override its
`_create_like_index_sql` method and then use the adjusted backend in your
`DATABASES` entries.
You can refer to the [https://docs.djangoproject.com/en/4.1/ref/databases
/#subclassing-the-built-in-database-backends documentation on the
subject].
--
Ticket URL: <https://code.djangoproject.com/ticket/33901#comment:10>
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/01070183f3044f87-88c02977-ab72-4939-b696-953541453739-000000%40eu-central-1.amazonses.com.
