+1. Like anything that can be done in ant.
Pat wrote: > You could achieve a DB Rollback routine with SVN and ANT. > > 1. each schema update you make, you export your DB schema again to an > SQL file. eg > > <project>\data\create.sql > > this is a few clicks routine for SQL server, not sure about other DB's > but im sure its possible. For multiple DB's you would have > > <project>\data\create_mssql.sql > <project>\data\create_mysql.sql > <project>\data\create_oracle.sql > > Also you then have some static data or default data (country > names,product categores etc etc) you want to populate the DB with so > you create the eqivalent to your schema 'create' file as an 'insert' > file > > <project>\data\insert_mssql.sql > <project>\data\insert_mysql.sql > <project>\data\insert_oracle.sql > > you might also want some test data, eg. some products,orders, > customers etc so you create another test SQL file for those too. > > this relies on the fact your db can support exporting such scripts for > you, cos its a PITA to do them by hand. > > 2. you can then use SVN to manage changes as you would with your > codebase. > > 3. when you checkout your codebase use an ANT script that does the SVN > checkout and at the same time runs the SQL scripts you checkout to a > given DB. (ANT scripts have an <SQL> tag just like cfquery!) > > hth > > Pat > > > > On Apr 16, 11:36 pm, "Andrew Scott" <[EMAIL PROTECTED]> > wrote: > >> Ok, >> >> Now it seems that everyone is getting the wrong end of the stick here, the >> scenario is going to be simple. This is for development only, and we are in >> the middle of a huge project with many developers working away, we have >> already introduced TDD with XP Agile development and have everyone using SVN >> for creating different versions. >> >> But the problem now is the database, if we need to support n versions of an >> application we are finding that the database requires more work and >> maintenance than it really should when switching between different branches >> of our code. >> >> So as someone mentioned I would not be looking for a solution for >> production, come on guys I have been developing long enough to not make a >> stupid move like that. The problem is that we currently use RedGate as I >> said earlier and its works well for MS SQL Server, but it doesn't work for >> mySQL or Oracle or DB2. >> >> Now if you look at having to switch to a different branch of code to >> maintain, there really needs to be someway to do this with SQL schemas as >> well. >> >> And yes we have daily backups, but this is not the issue. >> > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
