Broadleaf recommends using our Liquibase approach for the greatest flexibility and ease during upgrades. However, if you are not using Liquibase as your strategy for database schema maintenance and wish to acquire raw SQL for Broadleaf schema changes during an upgrade, you may do so using standard utilities provided by Liquibase. This involves several steps:
-
Establish a baseline schema and databasechangelog reference for you current version in a temporary database using Liquibase utilities.
-
Emit a migration sql file by referencing your target version liquibase changelog file and temporary baseline database using Liquibase utilities.
-
Repeat steps 1 and 2 for each microservice you plan to upgrade.
The end result of steps 1 & 2 should be a migrate.sql file that represents the delta between the baseline and the target version. This SQL will then be useful to apply manually against a development environment for confirmation of functionality with the upgraded codebase.