#29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving
<table_name>__old in db schema
----------------------------------+------------------------------------
     Reporter:  ezaquarii         |                    Owner:  nobody
         Type:  Bug               |                   Status:  closed
    Component:  Migrations        |                  Version:  2.0
     Severity:  Release blocker   |               Resolution:  fixed
     Keywords:  sqlite migration  |             Triage Stage:  Accepted
    Has patch:  1                 |      Needs documentation:  0
  Needs tests:  0                 |  Patch needs improvement:  0
Easy pickings:  0                 |                    UI/UX:  0
----------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53b17d4734f06372b66e3ac4db7a1740c503b330" 53b17d4]:
 {{{
 #!CommitTicketReference repository=""
 revision="53b17d4734f06372b66e3ac4db7a1740c503b330"
 [2.0.x] Fixed #29182 -- Fixed schema table alteration on SQLite 3.26+.

 SQLite 3.26 repoints foreign key constraints on table renames even when
 foreign_keys pragma is off which breaks every operation that requires
 a table rebuild to simulate unsupported ALTER TABLE statements.

 The newly introduced legacy_alter_table pragma disables this behavior
 and restores the previous schema editor assumptions.

 Thanks Florian Apolloner, Christoph Trassl, Chris Lamb for the report and
 troubleshooting assistance.

 Backport of c8ffdbe514b55ff5c9a2b8cb8bbdf2d3978c188f from master.
 }}}

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

Reply via email to