> I have some test fixtures with scenarios under test. Later, I need to
> migrate (with South) the DB schema around, which of cours necessitates
> changing domain and test code.
>
> A common problem I run into, though, is that I also need to migrate
> the data in my fixtures. It is possible to create a new DB, sync it
> to a given migration point, load the fixture, run the remaining
> migrations, and dump a new fixture, then drop the extra db. But it
> seems like a very awkward dance given how often I have the problem.
>
> Is there already a solution to this? It seems to me that South could
> manage some book keeping to maintain what fixtures are at which
> migration level, and a new south command could manage the migration of
> fixtures.
>
Agreed.
The fact that I have to manually migrate fixtures.
(initialize db with old version, apply fixtures, migrate, extract
fixtures) is one of the reasons why I use fixtures less often then code
generating input data.
A small tool migrating fixtures (at least for amy trivial migrations)
with south might be an incentive to use them a little more often.
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment