3 ms·
Until you hit the migrations in 1.7. But you are right. At my previous job, I spent countless hours getting from 1.4 to 1.5, but the step from 1.5 to 1.6 was r
by St-Clock 10y ago
Until you hit the migrations in 1.7.
But you are right. At my previous job, I spent countless hours getting from 1.4 to 1.5, but the step from 1.5 to 1.6 was relatively painless.
- merb 10y agoif you can screw your old migrations it's not a big deal.
- mangeletti 10y agoFor others: https://docs.djangoproject.com/en/1.9/ref/django-admin/#cmdoption-migrate--fake-initial https://docs.djangoproject.com/en/1.9/ref/django-admin/#cmdo...
- St-Clock 10y agoThis was introduced in 1.8 (which is great if you move to 1.8 or beyond), but if you are trying to go step by step, 1.7 was not a fun release to migrate to. There were also many problems with custom user model and the like. 1.7 was a very important release in the history of Django, just not a fun release to move to if you had a large codebase.