Hi,
I don't really have an issue, but would just like to get some feedback on the SequenceHiLoGenerator impl. being used when specifying a value larger than 1 to the allocationSize parameter of the @SequenceGenerator annotation.

I am indeed wondering why it isn't simply incrementing the sequence.nextval by one until it has consumed all values until sequence.nextval + allocationSize...

The reason is two folded:
1/ Why would I want to fall back to such large row ids?
2/ What if some other system is accessing the sequence to insert row in the same table and eventually leads to duplicated values?

Is there actually a good reason to use the HiLo algorithm to implement that feature and not the "simple way"? Am I missing something? And is there a way to provide my own Generator, should I really want to do so?

Thanks,
Alex

Wow that's good news:
http://in.relation.to/Bloggers/New323Hi ... Generators

Thanks for the link, Max Rydahl Andersen