search

aformusatii / dbdeploy

Automatically exported from code.google.com/p/dbdeploy
0 stars 0 forks source link

Support idea of a version number #38

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
We use a continuous integration server (Hudson) to do our builds/ 
deployment. It would be nice if dbdeploy supports the concept of a version 
# -i.e. the ChangeLog table has a version number column and have that 
value set by passing parameters from the build server to the dbdeploy 
scripts.

Original issue reported on code.google.com by roshan.s...@gmail.com on 12 Jan 2010 at 3:29

GoogleCodeExporter commented 8 years ago 
Also, is it possible to get dbdeploy to run only scripts upto a certain #? This 
would be useful to create an older version of the application

E.g. Current Version 1.12 = deploy all 12 database scripts 001-012
Version .09 = deploy the first 9 scripts 001-009
It would be nice if there is a way to specify if I want dbdeploy to run all 
scripts, 
or upto a number.

Or, even scripts matchings a certain format - e.g. if I have a need to support 
multiple db formats - 001_myschema_mysql.sql is for MySQL and 
001_myschema_sqlserver.sql is for SQL Server

Original comment by roshan.s...@gmail.com on 12 Jan 2010 at 11:51

GoogleCodeExporter commented 8 years ago 
Sounds like a useful idea.  

Re comment 1: what we do in this case is just check out the version of the sql 
scripts from source control.  
Dbdeploy also supports lastChangeToApply to support application of changes up 
to a given change script number 
(see http://code.google.com/p/dbdeploy/wiki/UsingTheAntInterface) which isn't 
quite what you want but may be 
close.

Original comment by gtack...@googlemail.com on 10 May 2010 at 8:20