#33901: non-deterministic collations doesn't work with Unique=True on
Postgres13.3
-------------------------------------+-------------------------------------
Reporter: Ed Chai | 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
-------------------------------------+-------------------------------------
Comment (by Ed Chai):
Replying to [comment:1 Simon Charette]: I found #24082 but filed the issue
for the same reason, `CIText` is deprecated and `db_collation` is
documented way to do this job without any conflicts. Removing the
duplicate index is an optimal solution and unique only for constraint
seems semantic to me. Although I know some others still need `LIKE` and
regex expression for regular case sensitive `CharFeild` and `Textfield`.
> 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:2>
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/010701827676f414-e9e0c00c-aeed-4030-9977-1e91b3c88471-000000%40eu-central-1.amazonses.com.
