On Sun, Oct 4, 2009 at 9:51 PM, Matt Juszczak <m...@atopia.net> wrote:
> > - Merge changes from trunk -> stable -> live repositories. svn merge works > well for this but it doesn't really track well. > Define "doesn't really track well" If you don't like how it looks in the history, what do you expect scripts to accomplish? Comments that make it easier to track forks and merges? > - Manage db schema inside SVN. Something like this: > http://www.codeproject.com/KB/database/DatabaseSchemaVersioning.aspxexcept > for Unix/MySQL. > I'm not sure SCM is the best tool for this job. I think what you need is a tool that can generate the DDL scripts to make one databases schema match anothers ( like RedGate SQL compare for MS SQL server), and a backup of your production staging and test database at each branch or version of your app. It won't eliminate the need for manual DML scripts (nothing does), but it will give you the best possible chance of actually being able to migrate a database up or down to an arbitrary version of the app. In actuality, you only need a permanent copy of each version of the dev database, which should be small, to make this work
_______________________________________________ New York PHP Users Group Community Talk Mailing List http://lists.nyphp.org/mailman/listinfo/talk http://www.nyphp.org/Show-Participation
