The release notes on https://docs.djangoproject.com/en/dev/releases/4.2.6/ contain:
> You may need to recreate indexes propagated to the database with Django 4.2 - 4.2.5 as they contain unnecessary ::text casting that is avoided as of this release. This doesn't give much context or give any guidance on how best to handle this, whether Django could help, etc. It also doesn't clarify why this is a "may need to" situation. Were Django versions 4.2-4.2.5 randomly doing this from time to time, or is this actually "you definitely do need to" situation; or is only relevant in specific scenarios? 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. Thoughts on this? -- 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/e686415b-0c4b-4643-8d0f-707aa859992bn%40googlegroups.com.
