Skip to content

MariaDB Error in Hibernate DDL validation #916

@MichaelVonB

Description

@MichaelVonB

Steps to reproduce

  • camunda-bpm-taskpool version: 4.1.0
  • Camunda BPM version: 7.20
  • JDK version: 17
  • 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 SchemaManagementException
    Schema-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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type: bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions