#24535: Make "manage.py migrate" atomic, i.e. rolling back any migrations on failure -------------------------------+-------------------------------------- Reporter: Daniel Hahler | Owner: nobody Type: New feature | Status: closed Component: Migrations | Version: 1.7 Severity: Normal | Resolution: wontfix Keywords: | Triage Stage: Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------+--------------------------------------
Comment (by Andrew Badr): Replying to [comment:1 Tim Graham]: > I'm not sure it's feasible. For example, in PostgreSQL you cannot update a table (data migration) and then alter the table schema in one transaction. That's not true (anymore?). I just tried it in a local shell and it worked. Maybe there are certain sequences of alter/updates that don't work. Haven't been able to find docs spelling it out. -- Ticket URL: <https://code.djangoproject.com/ticket/24535#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 django-updates+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/065.beb4d4a7e89dcd7d47e893078ac6cc44%40djangoproject.com.