Oh Crap Bad Baseline!

2 views
Skip to first unread message

RunThePun

unread,
Jun 2, 2009, 2:32:59 PM6/2/09
to Django Evolution
I updated my svn project with a model change, and the evolution app at
the same time. So when evolution made a baseline, it used the model I
wanted it to change as a baseline.

I'm trying to drop the 2 evolution tables django_project_version and
django_evolution, then rebaseline with the old models.py. Lets hope
this works.

--runthepun

Russell Keith-Magee

unread,
Jun 2, 2009, 7:50:57 PM6/2/09
to django-e...@googlegroups.com

This should work. Everything Evolution does is stored in those two
tables, so if you delete them, you are essentially starting from
scratch.

The general use case you describe is a common problem, and it is
something that I would like to address. As an intermediate
workaround, there is a long standing ticket to add some commands to
rebaseline and/or force evolutions in/out of the current baseline.

Yours,
Russ Magee %-)

Reply all
Reply to author
Forward
0 new messages