#29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving
<table_name>__old in db schema
----------------------------------+------------------------------------
     Reporter:  ezaquarii         |                    Owner:  nobody
         Type:  Bug               |                   Status:  new
    Component:  Migrations        |                  Version:  2.1
     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 Florian Apolloner):

 Replying to [comment:22 Chris Lamb]:
 > However, the patch in
 https://code.djangoproject.com/ticket/29182#comment:12 does not work for
 me:

 As said this is just a starting point and we might come around to make
 this actually the expected behavior. We cannot safely alter a SQLite
 database inside a transaction from the looks of it (If you look at the
 patch we rewrite internal tables and then need to issues a VACUUM -- not
 sure if we can do that safely in transactions).

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

Reply via email to