On Thu, Apr 3, 2008 at 7:36 AM, Julien <[EMAIL PROTECTED]> wrote: > We're using SVN between several developers to work on the same project > and it's working quite well. But it's not as simple concerning the > database. > > Each of us has a local database to muck around with, and if one of us > makes a change in the models that implies modifying the database > manually (e.g. renaming a field, changing the type or the field, etc.) > that developer has to inform all others of the changes so they all > make the change manually on their own local database. > > Having a common database would avoid that, but that's not ideal since > an online database would be slower to access, and it could quickly go > out of control if many people add records or change the database > structure at the same time. > > So, I just wanted to get some advice from you as to what is the best > approach to go?
For our last project (not Django, unfortunately), we created a directory that holds SQL changes files. The files were named "from-1234.sql" where 1234 is the current svn revision when the file was created. Everytime we made a change to the database model, we modified the main sql file (equivalent to models.py in django), then we also created an SQL change file containing all the changes (alter, drop, etc.), then we ran the SQL change file to actually modify the database instead of modifying the database directly. Other developers would need to pay attention for additions in the SQL changes directory and update their database accordingly whenever there's a new file there. Ronny --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
