JMIX with Liquibase

Support
#1

General question. We have a database with lots of other tables that are not hooked to the JMIX application we are using. With Liquibase it is dropping these tables on startup. I am wondering how we can create new tables and update schema to only JMIX application tables and NEVER drop tables in the DB. I saw there was an option in the application properties, but we have lots of tables and I don’t want to maintain this list and possible have an engineer not add one in here and wipes out our tables.

Any better options?

#2

Hello,

if you don’t want to use the application properties method, I can think of something else - database user permissions. Do not grant any undesired table rights to the database user you are using to connect with the Jmix application. Without those rights, the Liquibase script that is running under the Jmix database user can’t touch them.

Kind regards,
Mladen

#3

Why not create separate database schema for Jmix application’s tables?
Or even create a separate database for Jmix tables?

Legacy database can be attached to the Jmix application as additional data store, with setting set not to change any DDL.

By separating database/schema on physical level, you will also clearly separate your data on architectural level.