#29182: SQLite database migration breaks ForeignKey constraint, leaving
<table_name>__old in db schema
----------------------------------+------------------------------------
Reporter: ezaquarii | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 2.0
Severity: Release blocker | Resolution:
Keywords: sqlite migration | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by Simon Charette):
Florian, if you still have a few minutes to dedicate to this issue I'd
appreciate if you could add a
[https://github.com/django/django/pull/9389/files#diff-
888b45a0a8f38ee67e8d22403cf994dbR1151 schema test] based on your
investigation reproducing the issue. It's surprising that this wasn't
caught by an existing foreign key addition test.
--
Ticket URL: <https://code.djangoproject.com/ticket/29182#comment:13>
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/067.5d3887e891622077140ff4d1f8bb6fcb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
