On 22.10.2010 13:20, Riccardo Magliocchetti wrote:
BTW, when we are adding south as dependency? :)
That would probably happen once we'll decide that we don't need to
change anything in DB before 0.9 release. Of course it's possible to add
it earlier, but I'm interested in using it in first place for migrating
between releases.
It looks like you want to distribute the migration file with updates,
i think instead you should let the user do the schema migration when
upgrading. This way they won't have issues if they have customized
models. And you can use south everytime you need to change models.
I think that if someone is smart enough to customize data models, he
should be able to handle his migrations as well. I'm interested in
adding south only to have an official and tested path for upgrades
between releases for stock version of wikipbx for people that aren't
advanced users.
At work I usually put migrations directory under stuff ignored by dvcs.
I didn't get to use it before on any projects, so I'll have to rely on
other people's opinion here. I know that there are some cases when
you'll still have to write migrations manually, i.e. data was changed,
but schema was kept the same. Just relying on autogenerated migrations
didn't work too good according to a friend of mine - he said that he had
to return to writing SQL manually since it was actually more reliable.
