Liquibase Community Forum
2010-10-05 16:58:24 UTC
A new topic, 'First changeset', has been made on a board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=726.new#new
The text of the topic is shown below:
As the number of changesets grow for a system, is it possible to bypass them with a complete schema definition?
To illustrate, imagine there are 500,000 changesets for my application. I want to deploy a brand new version on a clean database. Is it really necessary to go through all 500,000 changesets, adding tables, dropping tables, modifying columns, etc, just to get it up to the right version, or would it be possible to periodically specify a "starting" changeSet that executes only if no previous changesets have been run, and then assumes the database is all up to date?
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.
You can see it at
http://liquibase.org/forum/index.php?topic=726.new#new
The text of the topic is shown below:
As the number of changesets grow for a system, is it possible to bypass them with a complete schema definition?
To illustrate, imagine there are 500,000 changesets for my application. I want to deploy a brand new version on a clean database. Is it really necessary to go through all 500,000 changesets, adding tables, dropping tables, modifying columns, etc, just to get it up to the right version, or would it be possible to periodically specify a "starting" changeSet that executes only if no previous changesets have been run, and then assumes the database is all up to date?
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.