#34898: Adding non-deterministic collations to unique CharFields crashes on
PostgreSQL.
-------------------------------------+-------------------------------------
Reporter: Mariusz Felisiak | Owner: Tom
| Carrick
Type: Bug | Status: assigned
Component: Migrations | Version: 4.2
Severity: Normal | Resolution:
Keywords: PostgreSQL | Triage Stage: Accepted
collation |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:3 Tom Carrick]:
> I think handling this in the `schema` module is a really bad idea, as we
would be dropping and creating an index or constraint without the user's
knowledge. I don't see another way to handle it.
I don't think it's that bad. We've already don't create
`varchar_pattern_ops`/`text_pattern_ops` indexes when non-deterministic
`db_collation` is set, so removing them before adding a collation would be
somehow consistent with the current behavior.
--
Ticket URL: <https://code.djangoproject.com/ticket/34898#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/0107018bd21fcc20-5e1a6bc6-3c63-4efb-becb-093b72ff53bb-000000%40eu-central-1.amazonses.com.
