2015-11-23 23:52 GMT+01:00 Carl Meyer <c...@oddbird.net>:
I've implemented the CITEXT-based solution a couple times; I think for a
> PostgreSQL-based project it's the preferable option overall.
>
Perhaps we should add native support in contrib.postgres?
I'm forseeing a small difficulty in terms of API. This is a behavior I'd
like
to "mix in" to some fields but I can't say if that will be easy to
implement.
The general ideas would be:
# A mixin
class CITextField(TextField):
# ...
# Case-insensitive versions of some built-in Django default fields
# (if we consider that makes sense)
class CIEmailField(CITextField, EmailField):
pass
# The possibility for users to make custom fields case insensitive
class CITagField(CITextField, TagField):
pass
--
Aymeric.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/CANE-7mW60wZcJ-6ahReqNAf4rDN%2BV5dQ%3Dahn%3Dh3Oz3X4uz81pg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
