#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:3 Mariusz Felisiak]: Sure, I think i can make a pull
request this week.
> Replying to [comment:1 Simon Charette]:
> > 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?
>
> Sounds good to me. Ed, would you like to prepare a patch?
--
Ticket URL: <https://code.djangoproject.com/ticket/33901#comment:4>
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/010701828990bf2d-78558a5a-9005-42b4-ae1b-eb1d902e81b2-000000%40eu-central-1.amazonses.com.
