Yes, it is possible to separate the storage of metadata and the execution of changelog in Liquibase. This can be done by configuring Liquibase to use different databases for storing metadata and executing changelogs.
For example, the metadata can be stored in a MySQL database and the changelogs can be executed in a PostgreSQL database. This can be achieved by specifying different database URIs, usernames, and passwords for metadata and changelog in Liquibase configuration.
Another approach is to store the metadata in the file system and execute changelogs from the database. This can be done using Liquibase's file-based change log feature. In this approach, the metadata is stored in XML or YAML files, and Liquibase executes the changelogs from the database.
Overall, the separation of metadata storage and changelog execution in Liquibase provides flexibility and can help in managing the database schema changes effectively.
Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss
Asked: 2023-06-02 06:21:17 +0000
Seen: 22 times
Last updated: Jun 02 '23
How can pgcrypto be used to secure data on Postgres?
In PySpark, how does the lead function work when the value of a column changes?
How can SQL output be structured in a column-based XML format instead of row-based?
What is the SQL grammar used for addSql in Doctrine?
How can Django Admin accommodate a variety of formats and locales for its input fields?
How can an array be passed using typo3 flexform xml and itemsProcConfig?