Re: Deprecate CICharField, CIEmailField, CITextField

2023-05-12 Thread 'Johannes Maron' via Django developers (Contributions to Django itself)
Hi, Yes, I hope Django will continue to expand expression support. I worked so hard on the SQL compiler to facilitate those kinds of features. Anyhow, since db collations are not an adequate replacement for CI text, we will create an open-source backport of the CITEXT fields. Once we are done, I

Re: Conclusion of ticket #26761

2023-05-12 Thread 'Adam Johnson' via Django developers (Contributions to Django itself)
I have replied on the ticket with an example using arbitrary HTML as required. On Wed, May 10, 2023 at 10:30 AM Carsten Fuchs wrote: > Hello, > > ticket #26761 was closed as wontfix, however I don't understand the reason. > https://code.djangoproject.com/ticket/26761#comment:19 > > The ticket's

Re: Ticket #34555 ModelBase prevents addition of model Fields via __init_subclass__

2023-05-12 Thread 'Adam Johnson' via Django developers (Contributions to Django itself)
+1 from me. As Simon covered on the ticket, the change is small. Making Django classes support __init_subclass__ might unlock some nice dynamic field patterns. On Thu, May 11, 2023 at 12:47 PM hottwaj wrote: > Hi there, I opened the above ticket and submitted a PR with fix and test > added. I

Re: Deprecate CICharField, CIEmailField, CITextField

2023-05-12 Thread 'Adam Johnson' via Django developers (Contributions to Django itself)
> What I am struggling now with is whenever I specify > `db_collation="case_insensitive"` on the field and this field is used in > `ModelAdmin.search_fields` - Django simply breaks (as it by default uses > `icontains` lookup). > That is quite unfortunate for the big projects, as I have to come up