Operating system: tested with linux/windows, should be independent of plattform
Steps: Use Hibernate to generate DDL with MariaDB Dialect. TaskEntity payload will be generated as tinytext (255 bytes). This does not fit with the purpose of payload.
With Spring Boot 3 comes a new Version of Hibernate (5 -> 6) the old 5.x version was generating longtext ~4gb for payload.
For our local profile we use spring.jpa.hibernate.ddl-auto: validate, our application failed to start due to SchemaManagementExceptionSchema-validation: wrong column type encountered in column [payload] in table [plf_data_entry]; found [longtext (Types#LONGVARCHAR)], but expecting [tinytext (Types#CLOB)]
Expected behaviour
DDL-Validation should work with polyflow for any database type.
Actual behaviour
Expected database type does not match with the actual database type.
Possible Workarounds
Dont use ddl-validation, i.e. spring.jpa.hibernate.ddl-auto: none
Steps to reproduce
SchemaManagementExceptionSchema-validation: wrong column type encountered in column [payload] in table [plf_data_entry]; found [longtext (Types#LONGVARCHAR)], but expecting [tinytext (Types#CLOB)]Expected behaviour
DDL-Validation should work with polyflow for any database type.
Actual behaviour
Expected database type does not match with the actual database type.
Possible Workarounds
Dont use ddl-validation, i.e. spring.jpa.hibernate.ddl-auto: none