#25833: Non-atomic migrations
-----------------------------+------------------------------------
Reporter: Pankrat | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Comment (by Pankrat):
If the migration doesn't apply without errors, it will not be marked as
applied.
It's up to the user to handle those migration errors gracefully (e.g. skip
already migrated rows when re-running a previously failed non-atomic
migration).
Would it be enough to mention this behaviour in the non-atomic migration
documentation?
AFAIU, non-atomic migrations have the same semantics as applying
migrations on a database that doesn't support transactional DDL.
--
Ticket URL: <https://code.djangoproject.com/ticket/25833#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 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/065.fcd1ad190ef1b27a0067e50d51369991%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
