I have noticed quite a few major issues which stops javers from working properly on oracle. It will probably now remain disabled until there are fixes.
- Whilst you can define in properties / yml file the following overrides for table names:
javers.sqlCommitTableName=t_jv_commit
javers.sqlGlobalIdTableName=t_jv_global_id
javers.sqlCommitPropertyTableName=t_jv_commit_property
javers.sqlSnapshotTableName=t_jv_snapshot
Notice the t_ pre the table names, in our work place oracle instances are not configured / accessible for users to interact with directly instead their wrapped with a synonym and assuming they now start with t_
This part works well until a record is inserted, then the underlying process to find next id refers to the raw table name.
In our case only synonym names are available for tables and sequences and therefore the sequence should also start with t_ or whatever our synonym declaration is.
There was something raised about tables and reserved words of type and version but think they were initiallly created with quotes that caused all the issues having recreated table using process it seems to work
I have noticed quite a few major issues which stops javers from working properly on oracle. It will probably now remain disabled until there are fixes.
Notice the t_ pre the table names, in our work place oracle instances are not configured / accessible for users to interact with directly instead their wrapped with a synonym and assuming they now start with
t_This part works well until a record is inserted, then the underlying process to find next id refers to the raw table name.
In our case only synonym names are available for tables and sequences and therefore the sequence should also start with
t_or whatever our synonym declaration is.There was something raised about tables and reserved words of
typeandversionbut think they were initiallly created with quotes that caused all the issues having recreated table using process it seems to work