#30033: SQLite schema editor should use the documented process to emulate table
alterations on SQlite3.
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Simon
Type: | Charette
Cleanup/optimization | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson <carlton.gibson@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"7289874adceec46b5367ec3157cdd10c711253a0" 7289874a]:
{{{
#!CommitTicketReference repository=""
revision="7289874adceec46b5367ec3157cdd10c711253a0"
Fixed #30033 -- Conformed to the recommended table alterations procedure
on SQlite3.
Refs #29182.
The previous implementation was following a procedure explicitly
documented
as incorrect and was the origin of the breakage experienced on SQLite 3.26
release that were addressed by c8ffdbe514b55ff5c9a2b8cb8bbdf2d3978c188f.
Thanks to Richard Hipp for pointing out the usage of the incorrect
procedure.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30033#comment:4>
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.54fc8fa92ba1c772f9bd224fbf1d4157%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
