#29721: Migrations are not applied atomically -------------------------------+------------------------------------ Reporter: Gavin Wahl | Owner: nobody Type: Uncategorized | Status: new Component: Migrations | Version: 2.1 Severity: Normal | Resolution: Keywords: | Triage Stage: Accepted Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------+------------------------------------ Changes (by Simon Charette):
* stage: Unreviewed => Accepted Comment: I guess we could move the recording logic in the context manager to be entirely correct but I'm surprised this has happened to you given the small amount of operations performed between the two blocks. Are you certain you didn't [https://docs.djangoproject.com/en/2.1/topics/migrations/#mysql the documented caveat of MySQL regarding atomic migrations]? In that case this change wouldn't help at all. Was it the `django_migrations` table creation that failed? Are you able to provide a patch/PR? -- Ticket URL: <https://code.djangoproject.com/ticket/29721#comment:1> 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.af6fff83541a5c7fd6c8a10e45ba5da0%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.