#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 Christoph Trassl):

 It's broken with SQLite 3.26. SQLite 3.25.3 is fine, regardless of Django
 version. Perhaps it is related to changes to the ALTER TABLE statement in
 SQLite 3.26 (https://sqlite.org/pragma.html#pragma_legacy_alter_table).

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29182#comment:17>
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.ffe03597527c0eef46cc4667296691a5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to