That looks plausible. The place to patch would probably be
https://github.com/django/django/blob/master/django/contrib/gis/db/backends/postgis/schema.py.
Could you create a Trac ticket and, if possible, a patch?
On Wednesday, August 31, 2016 at 6:33:23 PM UTC-4, Arjun Attam wrote:
>
> Hi,
>
> I have a model with a PointField, created with the spatial_index set as
> True
> (the default value). Doing a \d table_name on postgresql revealed the index
> that was created, as expected.
>
> I updated the spatial_index to False and ran the migrations, which *did
> not*
> drop the index in the db.
>
> I was also able to repro this with a PointField created with spatial_index
> as
> False. When the field was updated to set spatial_index as True, an index
> was
> not created in the database. Looks like AlterField migration is not working
> with PointField and spatial_index.
>
> I'm running Django 1.9.9 and PostgreSQL 9.5.1
>
> Best,
> Arjun
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/af64d1d9-69ea-4931-b646-5b4c364cee90%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
