On Thursday 16 March 2006 13:48, oggie rob wrote: > You also have to consider data - coordinating data changes can be > tricky within a team. You should at least have a policy on data in the > servers (i.e. do developers have to have a "filled" database or can > they work with an "empty" one), as well as a database conversion policy > for changes to a staging & production machine. Again this depends a lot > on how much testing you expect your developers to do.
Good point. We have a set of test data and a script to load it, both of which are kept in our svn repository. During heavy development, I might reload all my test data many times a day. The reload script has safeguards to keep it from running on the production server. The unit tests would mostly create their own data on which to test. This system worked well for us. Eric. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
