Hey,
I've recently written an app that implements a closure tree using
views... and in order to make the migrations work as needed you must
manually add an entry to the migrations.
Another friend of mine, a recent django convert, was wanting a way to
add to the migration script generated when creating certain tables...
And today I realised I wanted quite involved control of how migration
actions are written for the idea I was working on...
What I conceived was what I call a MigrationAdapter, which controls at
least how create/modify/delete actions for a given object are generated.
I've started looking into the migrations code, and it appears the steps
are very much hard-coded [and, it appears, with much painfully learned
good reasons]...
Anyone with more familiarity with the migration machinery got input on
if this is feasible?
--
Curtis
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/12134aff-d37c-2b35-27a2-58d52f9358ff%40tinbrain.net.
For more options, visit https://groups.google.com/d/optout.
