#21889: Record hash of applied migrations
-----------------------------+--------------------
Reporter: thomasf@… | Owner:
Type: New feature | Status: new
Component: Migrations | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------
Simple list spec:
* After an migration has been applied its hash is stored in the migration
table
* The hash value could probably just be a file hash of the migration
python source file
* Before new migrations are applied all previous migrations should be
checked to not only have the correct id but also the same content.
* Migration modification without triggering any hash errors (like
documentation only updates) can be supported using a hash property on the
migration model that allows the developer to let the migration keep its
previous hash.
* An --force-update-migration-hash option can be added the migration
command for an explicit "i don't care' situation.
I've seen this other database migration frameworks and it has been a very
useful thing to have at times.
--
Ticket URL: <https://code.djangoproject.com/ticket/21889>
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/063.1f5eb763406138f033943afe4626c950%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
