#30189: sqlmigrate wraps it's outpout in BEGIN/COMMIT even if the database
doesn't
support transactional DDL
--------------------------------+---------------------------------------
Reporter: Simon Charette | Owner: Parth Patil
Type: Bug | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------+---------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"acc041984fac1e79d9a1258c94479dd3ffc7f186" acc04198]:
{{{
#!CommitTicketReference repository=""
revision="acc041984fac1e79d9a1258c94479dd3ffc7f186"
Fixed #30189 -- Removed transaction from sqlmigrate output if database
doesn't use one.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30189#comment:7>
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.cc3f6bc2e857e6cbe7c835e0de26287c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.