#33872: Deprecate CICharField, CIEmailField, CITextField.
-------------------------------------+-------------------------------------
Reporter: Mariusz Felisiak | Owner: Mariusz
Type: | Felisiak
Cleanup/optimization | Status: closed
Component: contrib.postgres | Version: dev
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Johannes Maron):
* stage: Ready for checkin => Unreviewed
Comment:
In case my mailing list comment gets lost, I make this as unreviewed and
leave a copy here:
Hi there,
I am sorry that I missed this in the alpha. But to the best of my
knowledge, CITEXT and non-deterministic collations are not the same. They
don't support the same operations and their string comparison operations
are similar, yet not identical.
Furthermore, PostgreSQL doesn't discourage the use of CITEXT, but hints
towards a native alternative. That's maybe more than just a subtle
difference.
99% of all use-cases might be email, but even email LIKE-queries would be
affected (good for +-searches).
Unless we want to drop support for the CITEXT extension, collations might
not be a sufficient replacement.
I'd caution to revert the deprecation and keep support unless we make an
informed decision to drop CITEXT for a 3rd party integration.
Best
Joe!
--
Ticket URL: <https://code.djangoproject.com/ticket/33872#comment:6>
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/0107018774cdf13c-58ec35a0-cbef-48f2-ba47-0b66b25654ac-000000%40eu-central-1.amazonses.com.
