Hacker News new | ask | show | jobs
by ubernostrum 3440 days ago
If you were supporting applications which needed to work with or without South at the time of the transition, the best thing to do was probably ship two separate sets of migrations (one set written for South, one written for Django's built-in migration framework).
1 comments

Yes, that's what I am doing. The problem is, how to preserve the state of the migrations when the user updates the django version.