3 ms·
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 separat
by ubernostrum 10y 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).
- Animux 10y agoYes, that's what I am doing. The problem is, how to preserve the state of the migrations when the user updates the django version.