On Wed, Jan 14, 2015 at 3:03 PM, Abraham Varricatt < abraham.varric...@googlemail.com> wrote:
> Hello everyone, > > One of the biggest features introduced in Django 1.7 are migrations. They > can broadly be classified into 2 types - > * schema migrations > * data migrations > > Schema migrations deal with changes to the database schema. eg - changing > max_digits of a DecimalField. > Data migrations revolve around the actual data in your database and are > not automatically taken care of. > > My question is; > > Why is there so much praise for the Django (1.7) migrations feature if it > can't handle data? Yes, I can understand the convenience of schema > migrations, but without it being accompanied by data migrations, what's the > point? (I'm assuming that this is something run on a production > environment. For test/development environments, the data can arguably be > worthless) > What gave you the impression that Django's migrations doesn't handle data? There's a section in the Migration topic guide in Django's documentation entitled "Data Migrations": https://docs.djangoproject.com/en/1.7/topics/migrations/#data-migrations Yours, Russ Magee %-) -- 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/CAJxq848Rz1kLjFjUoBs6gASNd1QzKDBGj%3DnY1O-QoLmSkzfwtQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
