30 октября 2012 г.

Yesterday I was playing with Django to obtain the best way to do automatically backuping and properly update data on production system during continuously deployments even when data model has changed.
As known, Django has it's own way to work with data, using fixtures and manage.py tools: flush, syncdb, loaddata, dumpdata. It was obviously for me, that loading/updating/uploading SQL dumps is a bad practice, while Django has it's own solution. But when I've tried to update local developer's database with data from production system I have got an error.