#34932: Setting deterministic Postgres collations incorrectly disallows use of
varchar_pattern_ops and text_pattern_ops
---------------------------------+---------------------------------------
Reporter: Tom Carrick | Owner: Tom Carrick
Type: Bug | Status: assigned
Component: Migrations | Version: 4.2
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+---------------------------------------
Changes (by Mariusz Felisiak):
* severity: Normal => Release blocker
* stage: Unreviewed => Accepted
Comment:
Thanks for the report. We should be able to skipped
`varchar_pattern_ops/text_pattern_ops` index creation only for non-
deterministic collations by introspecting
`pg_collation.collisdeterministic`.
Regression in f3f9d03edf17ccfa17263c7efa0b1350d1ac9278 (4.2) and
8ed25d65ea7546fafd808086fa07e7e5bb5428fc (5.0).
--
Ticket URL: <https://code.djangoproject.com/ticket/34932#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/0107018b7083b659-4d500e6e-da9e-43b4-a9f0-00187551782f-000000%40eu-central-1.amazonses.com.
