>>> Yes, I discovered this too. It's what prompted me to write the
>>>>>> parametrized admin tests covered in my later blog post:
>>>>>> https://adamj.eu/tech/2023/03/17/django-parameterized-tests-model-admin-classes/
>>>>>>
>>>&
(expression=Lower("email")), with the
>> lowercase collation and a unique consrtaint. We'll have to see...
>>
>>
>>> For example, in terms of documentation, we could add a note on
>>> `db_collation` to `icontains` page:
>>> https://docs.django
ample, in terms of documentation, we could add a note on
>> `db_collation` to `icontains` page:
>> https://docs.djangoproject.com/en/4.2/ref/models/querysets/#icontains
>
>
> That sounds like too specific a note to add. Many different data types in
> many different databases fail t
Hello again,
I trust Mariusz' assessment regarding the maintainability. In that case, I
presume a separate package from a 3rd party with commercial interest might
be the best option going forward.
Thanks for all the considerations and explanations.
Cheers!
Joe
On Wed, Apr 19, 2023 at 3:48 PM
Thanks Adam,
of course I read your well-written article before diving into this topic,
thanks for sharing.
However, I don't agree about the index. The best solution is using the
CITEXT db type, which is very much alive.
Should Django to deprecate support for the db type, a 3rd party package
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
