In our project we are using spring boot’s built in hibernate dependencies with Oracle DB . We are now updating spring boot 2.7 to 3.0.
One of our test is containing schema validation with hibernate.
There is an issue currently when it wants to validate a sequence that is not existing.
I put the breakpoint in the AbstractSchemaValidator:194
and on the failing sequence (on step back) AbstractSchemaValidator:112 i get the following:
(Sequence.contributor=”orm”). Looks like the orm made this sequence naming is: Identifier.key=a_table_name_SEQ, where a_table_name is an existing table, but this seq is non existent in the db.
It lists (saw them in debugger->namespace->sequences) all the sequences correctly except one called “hibernate_sequence” (The exact name in our db. The other name (a_table_name) are made up to not be project specific)
I’m not sure though if it is trying to name this hibernate_sequence to something else or is it a completely new one.
I’m wondering if there is a setting to not let the validator validate orm created sequences. |
|
