South's `--update` also rolled the previous migration back, changed it and then reapplied it to the current database.
M On 28 March 2014 10:48, Bernie Sumption <[email protected]> wrote: > > That script would be bad if you'd run any of those migrations against your >> development db (yes it should be "throwaway" or rebuildable but...) >> > > I'd think the same could be said of --update? As I understand it, --update > is the equivalent of deleting the most recent migration and recreating it. > If you'd applied the most recent migration to your development database and > then you --update that migration, you'd need to rebuild the database. > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" 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]. > 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/f3e1b67b-f1fc-4c94-964f-23ec7fb27755%40googlegroups.com<https://groups.google.com/d/msgid/django-developers/f3e1b67b-f1fc-4c94-964f-23ec7fb27755%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers" 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]. 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/CAMwjO1Gw5efPyC%2BFH%2BzEvXeW2p_6z-JkqbVUScrvtyXAJmmK6A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
