Database changes when migrating from CUBA to Jmix in PostgreSQL 12

Support
#1

Hello:

I am attempting to convert some CUBA 7.2 applications to Jmix 1.5.2 using a PostgreSQL 12 database. There appear to be database changes required as part of the conversion.

I am concerned that executing my test Jmix application will break my production CUBA applications when it updates the database.

Are they compatible? Will my CUBA applications continue to operate normally?

Do I have to clone my entire database to test?

As an alternative, do you have a list of database changes so I can copy the tables that will change to a new schema and create a search_path to use them first? Will that work?

#2

Hi,

You should definitely test the migration on the copy of the production database. Jmix modules contain database migration scripts that will be automatically applied to the existing CUBA database to make it compatible with Jmix.

You will not be able to have two applications (CUBA and Jmix) working simultaneously with the same database.

The migration procedure is described in the documentation.

#3

Well, that makes it a bit harder to migrate. Too bad there isn’t a way for them to co-exist while I rewrite the code.

I have 3 applications that all use the same tables. It is not possible to replace them all at once.

Is there any documentation at all that describes which CUBA tables are affected by the migration? Could I copy just those tables to a new schema and use the Additional Data Store function to access my application tables?

Alternatively, would I have to copy all of the CUBA-related tables (bpm_, act_, sys_* and sec_*)?