Liquibase another error

Hi All

I have a working application which I am now working locally with a backup from the active database.

When I want to debug, I get
image

and then
image

a) there is no need to change any column
b) how to debug and resolve this ?

( Meanwhile I did disable creation of migration scripts by editing the Run/Debug configuration settings. )

Thank you

Felix

Hello,

Liquibase relies heavily on 2 database tables:
databasechangelog - if a particular changelog has been applied, when and by whom, deploymentid, what, etc … take a look at this, neat :slight_smile:

databasechangeloglock - lock to prevent more than 1 Liquibase process from applying changes simultaneously -
image
Check that it is like on the picture - there should be only one row in this table. Sometimes when you restart the application/IDE process is left hanging and then one needs to manually sort this

So, regarding your problem, is that you copied the production tables, and they contain something that is not in sync with your Jmix liquibase changelogs locally.

→ do you still have the original development database? is the column really of the same type?
→ if you have original databasechangelog can you run quick diff on the 2 tables?
→ what happens if you change your jmix datastore back to development database is it ok?

Generate changelog yourself,
image
and when this dialog appears, set that field type change to be ignored, top left minus button, help also can.

Kind regards,
Mladen

Hello

Yes, the databasechangeloglock looks this way
image

So, regarding your problem, is that you copied the production tables, and they contain something that is not in sync with your Jmix liquibase changelogs locally.

Nope. The production system is running the same program without any problem. When I switch off the liquibase generation, the system is running as expected :wink:

The problem occurs, meanwhile generating not executing the liquibase files …

So if I click on
image

I get another errorbox
image

The generation process should not change anything on the database, isn’t it ?

But, I found a problem

In the entity, conAddfloat1 is defined as double ( generation from database ).

In the MSSQL DB the column exists as a float, no problem.
In the MariaDb the column exists as a float → problem generating the liquibase log.

I think, this is a new feature ? For me I can solve now the problem, changing all the entities, but for somebody else, this might be a problem.

Regards

Felix

1 Like