#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
----------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"25a0781a1661e7329bc1ba9bce12dfddf7f2d433" 25a0781a]:
{{{
#!CommitTicketReference repository=""
revision="25a0781a1661e7329bc1ba9bce12dfddf7f2d433"
Refs #29182 -- Corrected SQLite's supports_atomic_references_rename
feature flag.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29182#comment:42>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.122f247d266e38562be59da3dbbb89d3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
