[Liquibase-user] New Topic: Longterm schema management with Liquibase

[Liquibase Community Forum]

A new topic, 'Longterm schema management with Liquibase', has been made on a board you are watching.

You can see it at
http://liquibase.org/forum/index.php?topic=826.new#new

The text of the topic is shown below:

Hi

I'm currently in the process of starting a new project, so I'm trying to figuring out how to manage my db schema.

I see that liquibase can handle the incremental updates of the db schema. That's great! But how will this look like in a few years? Will my project be flooded by hunderts of little changes leading back though all minor and major versions down to the empty schema?

This seems a bit strange to me. So how does liquibase handle the situation when I (or even more importantly, the customer) create a fresh database? Will it migrate it though the hole history of the project?

In previous projects I managaged sql-change-scripts manually. Basically at every release (~every week) I exported a sql script that created the complete schema from scratch. During the week incremental scripts were written. What I liked on that is that we had (at least for every release) a complete, selfcontained schema description.

Can you give me a bit of insight on how liquibase should be used for a multi-year project?

Thanks,
Stefan

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.