A new topic, 'FeatureRequest: Specify the 'database' version using properties
(updateDatabase)', has been made on a board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=666.new#new
The text of the topic is shown below:
Hi,
i'am currently using liquibase with pleasure. But i'm missing one thing that
stops me to automate my release process.
Story:
------
To prepare a release I need a SQL File containing all changeSets for a target
version. As a developer I want to specify that target 'database' version using
properties instead of a database table (databasechangelog table) to be
independent from the db.
Background:
Writing a lot of changeSets is easy. But to export them alltotether in one sql
file can only be done by preparing a database for a certain version and run the
task updateDatabase against it. This takes a lot of time.
idea:
-----
I can imagine that this feature is easy to accomplish by changing the code that
is taking the version information from the database table to use a property if
available.
Because we need this feature soon I could also try to implement it and provide
a patch or whatever. How do you think about that?
Regards,
Oliver
Unsubscribe to new topics from this board by clicking here:
http://liquibase.org/forum/index.php?action=notifyboard;board=1.0
Regards,
The Liquibase Community Forum Team.
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Liquibase-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/liquibase-user
