On Wed, Sep 10, 2014 at 02:06:09PM -0500, Andrew Pinkham wrote: > On Sep 10, 2014, at 12:25 PM, John Schmitt <marmalo...@gmail.com> wrote: > > Which file? What do I look for? What do I 'verify' and to what should it > > be compared? > > When you run `makemigrations app_name`, the output will inform you of the > creation of at least one migration file, typically in > project_name/app_name/migrations. You may look in this(/these) file(s), and > ensure that the changes made are the changes you intended on your models. > > The documentation allows for understanding of the new files: > > https://docs.djangoproject.com/en/1.7/topics/migrations/ > https://docs.djangoproject.com/en/1.7/ref/migration-operations/ > > Note that the verification step is entirely optional. The check is not to > ensure that migrations work properly. The check is so that you can check that > the changes you made in your models are the ones you intended.
I see. This is exactly what I wanted to know, thank you. > > If you've worked with South, the workflow for working with with native > migrations is nearly identical. I've used Python for years but I'm new to Django so I can't relate to South. My references are the official documentation, stackexchange, and this list. -- 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/20140912182609.GG12100%40mediapc.snapdragonfly.net. For more options, visit https://groups.google.com/d/optout.
