Ticket #113 (closed defect: wontfix)
Unable to migrate data with schema when creating geometry fields
|Reported by:||benjamin.c.burns@…||Owned by:||andrew|
I am trying to migrate my model by adding a PointField? from django.contrib.gis.db.models. Upon committing the transaction and opening a new one, the column has still not been created. I believe this occurs because the support for these fields is implemented using the "deferred sql" feature of the generic db class.
My current workaround is to separate out the migration of any GIS fields from normal fields, write a normal migration for the normal fields, and then build two additional migrations, one that handles the schema, and one that handles the data.
This is a bit tedious, and while it works it seems semantically invalid to separate it out into multiple migrations. The biggest problem I see with this is that later on if I need to roll back I'll need to remember not to roll back to one of the intermediate migrations. Not a major issue, but still an annoyance.