Closed alexbudarov closed 4 years ago
Looks like an HSQL-only issue. Try to set "start with 1" when defining identity column in the DB.
The problem relates to 0-ID handling in EclipseLink. As a result, CUBA generates an IDENTITY column that starts from 1.
Sample CUBA script:
ID int generated by default as identity(start with 1) not null
Jmix Studio issue: https://youtrack.haulmont.com/issue/JST-250
Project: attached jfresh2.zip
Cousine:
Dish:
Case number 1
Case number 2
org.hsqldb.HsqlException: integrity constraint violation: unique constraint or index violation; UC_JFRESH2_COUSINE_NAME table: JFRESH2_COUSINE at org.hsqldb.error.Error.error(Unknown Source) at org.hsqldb.Constraint.getException(Unknown Source) at org.hsqldb.index.IndexAVL.insert(Unknown Source) at org.hsqldb.persist.RowStoreAVL.indexRow(Unknown Source) at org.hsqldb.TransactionManager2PL.addInsertAction(Unknown Source) at org.hsqldb.Session.addInsertAction(Unknown Source) at org.hsqldb.Table.insertSingleRow(Unknown Source) at org.hsqldb.StatementDML.insertSingleRow(Unknown Source)