I'm +1 on being able to continue using the line ./manage.py makemigrations && ./manage.py migrate
I can't see many (any?) situation where someone *wouldn't* run makemigrations & migrate as one logical operation, whether by typing the commands or running a script. What would the workflow be where you would make migrations but not apply them? D On 30 October 2014 12:29, Tim Heap <t...@timheap.me> wrote: > The backwards compatibility issue I was thinking of is for people using > `makemigrations` in a script currently, expecting it to exit with 0 unless > something very wrong has happened. For example, if `makemigrations` is run > in a bash script with `set -e`, and it does not find any migrations, that > script will then exit. Alternately, if someone is using a one-liner like > `./manage.py makemigrations && ./manage.py migrate && another command` the > makemigrations command will cause the whole command to abort early, even > though no 'error' as such has happened. Backwards compatibility aside, this > would be awkward to work around in scripts without simply ignoring the exit > code of `makemigrations` completely, which then ignores legitimate errors. > > I have made a patch that calls `sys.exit(1)` when no changes are found, and > made a pull request at https://github.com/django/django/pull/3441 > > Tim > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CALzH9qsJ-qgPxGzmeMF3Lt9oXsn-eRk%3DUSNS%2BxZmbaKinMA2ww%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
