I have several changelogs from a couple of years worth of database manipulation. It contains several schema alterations, index creations and removals, etc etc. I’d like to “start again”, so that all of the unnecessary create/drops are not run when creating a new database. Is there a programmatic way of dealing with migrating existing databases to use this new rolled up change log instead of the series that were used before? I’ve done some searching on this, but haven’t seen a great way of doing it. Thanks in advance for suggestions!
-
Learn
-
Resources
-
Free Tools
OSS Risk Scanner Database DevOps Risk AssessmentCheat Sheets
Snowflake + Liquibase Databricks + Liquibase -
eBooks
6 Liquibase Community Risks & How to Avoid Guide: SOC 2 Compliance at the Database Layer Guide: Quantify the Value of Liquibase Secure -
Comparison Guides
Liquibase vs. Flyway Liquibase vs. Bytebase Liquibase Community vs Liquibase Secure
-
- Quickstart
- Get Started
- Documentation
- University
-
Resources
- Connect
- Contribute
- Join
- Blog