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?
Re
Hi,
I also think a more specific documentation as to how to fix this issue is
required.
I usually upgrade Django about 6 months after the initial major release,
which is this month. But because of this issue I decided to wait 2 more
months.
Thanks,
Uri.
אורי
u...@speedy.net
On Wed, Oct 11, 202
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 gu
It seems plausible to me. I'll try to look into other places where it has
been repeated and try to make a PR.
On Monday, 9 October 2023 at 20:58:15 UTC+5:30 Adam Johnson wrote:
> I think it would be better to remove the link from the contribution guide,
> since it’s quite advanced. The recommen
