I'm just wondering how you could handle database changes.Let's say you have a existing working project and the client asks for some changes.
These changes force you to create an extra table and modify some tables (models).
On the development server I could modify the changes to the database and the models files myself.
But deploying these changes to the production server seems a bit harder to overcome without the fear of loosing your data.I don't think the newly created models and database tables would form a problem. Simply running ./manage.py syncdb would create the table(s) for us without any problems.
But what about tables (models) that are modified ?How would you best handle such cases of deployment ?
That's what South is for.
--
DR.
-- You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment