3 ms·
I wish this article was around year or two ago. I had an awful experience with south so much so that I switched to ruby and sequel. Sequel totally decouples you
by peregrine 14y ago
I wish this article was around year or two ago. I had an awful experience with south so much so that I switched to ruby and sequel. Sequel totally decouples your migrations from your model. It's pretty nice actually and ends up saving quite a bit of headache.
- andybak 14y agoWow. Must have been a pretty bad experience to warrant switching languages and frameworks! Care to elaborate? I've always found South pretty straightforward.
- peregrine 14y agoLot of things described here, circular references, conflicts amongst the team, trouble with simple data import. These things are a result of the coupling of models to migrations. The method of models describing and generating the migration which generates the db is troublesome.
- andrewgodwin 14y agoHowever, in the reverse way, the migrations defining the models (as in Rails) often leads to mismatches as well. There's no easy solution to this problem, alas. When model-based migrations work, they work really well, and help reinforce code schema/database schema being entirely in sync.