#32374: Migrations are marked applied even if deferred SQL fails to execute
--------------------------------+------------------------------------------
Reporter: Simon Charette | Owner: Simon Charette
Type: Bug | Status: closed
Component: Migrations | Version: 2.2
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+------------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"0c42cdf0d2422f4c080e93594d5d15381d6e955e" 0c42cdf0]:
{{{
#!CommitTicketReference repository=""
revision="0c42cdf0d2422f4c080e93594d5d15381d6e955e"
Fixed #32374 -- Stopped recording migration application before deferred
SQL.
Migrations cannot be recorded in the same transaction as its associated
DDL operations when some of it is deferred until the schema editor
context exits.
Regression in c86a3d80a25acd1887319198ca21a84c451014ad.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32374#comment:3>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.dae91fdc36fdc075686465ff4b084ae3%40djangoproject.com.
