I have a Spring Boot project which I updated to SB3, before everything worked, but after update I am getting schema-validation error in audit tables. Minimal sample project can be found here [ https://github.com/Neloop/sb3-hibernate-envers-demo |https://github.com/Neloop/sb3-hibernate-envers-demo]
The project uses * liquibase * as migration tool and with it the database structure is created, in this case there is only one table 'demo' and two audit tables. If I try to run the project I get:
{code:java}
org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: wrong column type encountered in column [description] in table [demo_aud]; found [character (Types#CLOB)], but expecting [varchar(255) (Types#VARCHAR)]
{code}
Which is unexpected because on the *DemoEntity* there is column *description* which has *@Lob* annotation and therefore its type should definitely not be VARCHAR(255), but it seems that envers metadata thinks that it is. It seems like a regression, because as I said this was working before I updated to SB3 with Hibernate 6.1
|
|
