Pardon, @Mariusz, I didn't mean to specify "non-text fields" - I had re-worded that sentence before posting.
On Wednesday, October 11, 2023 at 2:29:58 AM UTC-4 Mariusz Felisiak wrote: > My immediate thought is that any indexes on non-text fields, created with > these versions, will be useless in ORM-based queries. If that's the case, > this seems like a much bigger deal than the footnote would imply. > > > I'm puzzled. Why you assumed that all non-string based fields are > affected? Release note explicitly specifies what kind of indexes are > affected: > > Indexes *"on string based fields (CharField, EmailField, TextField, > CICharField, CIEmailField, and CITextField) used with the __isnull lookup > on PostgreSQL".* > > Do you it's worth mentioning again after *"You may need to recreate > indexes.."?* For example > > *"You may need to recreate indexes on string based fields (CharField, > EmailField, TextField, CICharField, CIEmailField, and CITextField) used > with the __isnull lookup propagated to the PostgreSQL database with Django > 4.2 - 4.2.5, as they contain unnecessary ::text casting that is avoided as > of this release."* > > Best, > Mariusz > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/726c4a23-6795-4e8e-aa4e-238b9ab2dba1n%40googlegroups.com.
