Hibernate Sequence Logic

Question

I am having a constraint violation issue with Hibernate and the constraint is related primary key. I debugged a bit and see that the before insertion, sequence value selection as below

select table_seq.nextval from dual;

runs only at the beginning for the related table. Following the first sequence fetching, the rest utilized by hibernate manually. I mean if the selected sequence is 25 on the first insertion. Rest of the sequences generated automatically by hibernate itself. No more sequence selection triggered. This causes some weird issues like, app runs on two different servers crashes due to primary key constraint.

I found below, but not sure if I am hitting to the same wall. Issue with Hibernate @SequenceGenerator in Spring 3 application

p.s : I am trying to upgrade the app from hibernate 3.x to 5.2.12.

Olgun Kaya · Accepted Answer · 2022-03-01 12:34:12Z

0

The problem was with the sequence auto increment value. The entity was set to 50 while db value was 1. I changed the sequence generation logic to old strategy which is ;

hibernate.id.new_generator_mappings -> false

answered Mar 1, 2022 at 12:34

Olgun Kaya

2,5854 gold badges34 silver badges55 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Hibernate Sequence Logic

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related