Pertaining the 4.2.6 release's "recreate indexes" footnote

[Michael]

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.

Re: Link to alternative Python resource

[Amogh]

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 recommendation for the tutorial and “you 
> should have a good understanding of Python itself” seem sufficient to me.
>
> I noticed we have other “Dive Into Python” links throughout the docs. 
> These could be updated to the official Python docs.
>
> On Thu, Oct 5, 2023, at 2:09 AM, Amogh wrote:
>
> Hey there, I was going through Writing your first patch for Django 
> , there is a 
> link to Dive Into Python 
> , and apart from the 
> table of contents, it seems that the resource is pretty old. I was thinking 
> of updating with some new resources that are freely available online. My 
> first preference would be the official documentation of Python.
>
> It's not technical, but something that I noticed along the way.
>
> What do you folks think? Do you have any recommendations?
>  
>
>
>
> -- 
> 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-develop...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-developers/3c274347-f5e3-4bcc-973c-ddb141dec649n%40googlegroups.com
>  
> 
> .
>
>
>

-- 
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/9ce44323-c6c0-419e-9597-ba0e426023e4n%40googlegroups.com.

Re: Pertaining the 4.2.6 release's "recreate indexes" footnote

[אורי]

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, 2023 at 12:32 AM Michael  wrote:

> 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
> 
> .
>

-- 
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/CABD5YeGKoznt-svAZkc8kCXnJLQXT8qdUh5KxNpKrVMChDozwA%40mail.gmail.com.

Re: Pertaining the 4.2.6 release's "recreate indexes" footnote

[Mariusz Felisiak]

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/a6a82877-eb21-45a7-bc1c-6fe055aaa650n%40googlegroups.com.