Maintain order of deployments in sybase using Liquibase

General Discussion
1

Hi Steve,

Thanks for the quick response. I am also looking for a scenario where I have 10 different artifacts and some of them have tables creation, insert/update statements and stored procedures. Now, I will be adding these artifacts in a order in the changelog xml, deployment follows artifact-by-artifact but whereas I would like to have all tables to be created first, followed by insert/update statements and stored procedures.

Regards,

Skandakumar

2

Hi,

I am a new user of Liquibase. I have to implement Liquibase for sybase database deployments. Question I have is, is there a way to maintain the priorities of object deployments. Say, Tables followed by indexes, views, etc., I tried to search for this info but of no luck. If there is a thread that discussed this topic please point it to me

Thanks in advance

Skandakumar

3

When deploying changes, Liquibase follows the order of changesets as they are in the changelog. When creating a brand-new changelog from an existing database (or when appending changes using the diffChangeLog command), Liquibase does its best to take into account typical dependencies, but there may be cases where it is unable to create a changelog that will deploy properly. In the case a newly-created changelog does not deploy cleanly, you may need to re-arrange changesets to fix dependency issues.

Steve Donie
Principal Software Engineer
Datical, Inc. http://www.datical.com/

4

I don’t think I understand what the problem is. What do you mean by “artifacts”? Your understanding of that word and mine may be vastly different.

Do you have an existing changelog, or a set of SQL scripts, or just some pile of databases that you want to ‘automate’ somehow?

In general,

  • what steps are you taking right now that aren’t working?* what is the actual result from following those steps?

  • what result were you expecting?

Steve Donie
Principal Software Engineer
Datical, Inc. http://www.datical.com/