#23030: Geo model table rename (in migrations) with spatialite UNIQUE constraint
failed
-------------------------------------+-------------------------------------
Reporter: kunitoki | Owner: claudep
Type: Bug | Status: closed
Component: GIS | Version: 1.7-rc-1
Severity: Release blocker | Resolution: fixed
Keywords: gis spatialite | Triage Stage: Accepted
sqlite geometry | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by Claude Paroz <claude@…>):
In [changeset:"ddb5674945725ec8f6e6336f73d3d56e331f34ae"]:
{{{
#!CommitTicketReference repository=""
revision="ddb5674945725ec8f6e6336f73d3d56e331f34ae"
[1.7.x] Fixed #23030 -- Properly handled geometry columns metadata during
migrations
Thanks kunitoki for the report and initial patches.
Backport of 8c30df15f1 from master.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23030#comment:11>
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.b8fdf13c68098d6a97c7da4df57e5cd5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
