#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 Simon Charette):

 Awesome, thanks for confirming Florian. I'll turn it into a PR with a
 release note for the next 2.1 release later today.

 I feel like we'll want to stick to this solution until we drop support for
 < 3.26 as the logic involved, as you've come to notice yourself, is
 already quite convoluted and adding some version branching in there would
 make it even worst. We've got a solution that allows us to keep atomic
 migrations enabled on SQLite so I suggest we stick to it.

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

Reply via email to