#23030: Migration code not working with GeometryField and more than 2 foreign
keys
-------------------------------------+-------------------------------------
Reporter: kunitoki | Owner: nobody
Type: Bug | Status: new
Component: GIS | Version: 1.7-rc-1
Severity: Release blocker | Resolution:
Keywords: gis spatialite | Triage Stage:
sqlite geometry | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by kunitoki):
It seems that '''geometry_columns''' spatialite table is populated with 2
tables
{{{
Applying gis.0001_initial...
SELECT AddGeometryColumn('gis_first', 'objs', 4326, 'GEOMETRY', 2, 0)
SELECT CreateSpatialIndex("gis_first", "objs")
SELECT AddGeometryColumn('gis_first__new', 'objs', 4326, 'GEOMETRY', 2, 0)
SELECT CreateSpatialIndex("gis_first__new", "objs")
UPDATE geometry_columns SET f_table_name = "gis_first" WHERE f_table_name
= "gis_first__new"
}}}
then the update is obviously failing cause in the '''geometry_columns'''
table there are already 2 entries...
--
Ticket URL: <https://code.djangoproject.com/ticket/23030#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.30cb87a8dc2baca304ceb407a47df647%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
