On 3/10/2015 8:35 AM, Daniel Chen wrote:
My confusion is in the fact that the model state wouldn't roll back to state X after the first failed transaction (like the DB did).
No. The model is all your own work. Anything you write stays written. The migration system tries to implement your work. If it fails, it will roll the database back to its previous state. It does nothing to your work. You need to take note of the failure, decide how to fix your work and try again.
If you eliminate the error in your work (assuming no bugs in the framework) the migration will work and advance the database state to match the model state.
Mike -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/560F0DEC.7050401%40dewhirst.com.au. For more options, visit https://groups.google.com/d/optout.