#23542: Add ability to disable migrations
-------------------------------+--------------------
Reporter: yuriiz | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.7
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
Django 1.7 introduces migrations which are described at:
https://docs.djangoproject.com/en/1.7/topics/migrations/
Unfortunately this step is now mandatory which restricts Django 1.7 usage.
(Otherwise the one get
"CommandError: App 'sessions' has migrations. Only the sqlmigrate and
sqlflush commands can be used when an app has migrations." on manage.py
test immediately).
There are great number of projects that are established enough to have DB
schema unmodified for long time already but would benefit from Django 1.7
securiry/bug fixes. Some projects have third-party migration solutions
(South is not the only one in the world), some of them could be even non-
Python. These projects can not upgrade Django from now either or forced to
make dummy migrations.
It would be great if Django had settings to disable new Django's built-in
migrations completely. Like
ENABLE_MIGRATIONS = default True and False would fallback syncdb to old
create-table-if-not-exists behaviour and manage.py test could be still
used for testing applications with no Django migrations created.
--
Ticket URL: <https://code.djangoproject.com/ticket/23542>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/049.958098121c2dc8b2d455c9b93dc1e794%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
