#23030: Geo model table rename (in migrations) with spatialite UNIQUE constraint
failed
-------------------------------------+-------------------------------------
Reporter: kunitoki | Owner: nobody
Type: Bug | Status: new
Component: GIS | Version: 1.7-rc-1
Severity: Release blocker | Resolution:
Keywords: gis spatialite | Triage Stage: Accepted
sqlite geometry | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 1 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by kunitoki):
last patch will work correctly with migrations without leaving the
database in a inconsistent state.
i don't know if DatabaseSchema.alter_db_table is called also outside of
migrations, so i don't know if it will work in any corner case.
will try to write a test for this
--
Ticket URL: <https://code.djangoproject.com/ticket/23030#comment:7>
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.8ac5f197158407474770530fa972b18f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
