The new behaviour is the followings:
AllocationSize is a range of primary key values reserved for Hibernate.
And the select seq.nextval
from dual will be done only after hibernate consumed this range of primary keys.
So you must declare the same value on both allocationSize
(Hibernate) and sequence increment by
(DB)
When explicitly set allocationSize=500
, e.g. on Oracle
create sequence SEQ_ACE_WORKERS_QUEUE_STATS_ID
MINVALUE 1
MAXVALUE 999999999999999999999999999
START WITH 1
INCREMENT BY 500
NOCACHE
NOCYCLE;
Otherwise, you'll notice negative values or constraint errors raised from your DB because of primary key collisions.
When the app server is restarted, you'll notice the 'jump' between the latest primary key allocated, and the 'newly' sequence number selected at restart.
Final comment: default value is 50. So if you don't specify allocationSize
on the Hibernate side, you must declare increment by
50 on the DB side.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…