Re: [hibernate-dev] hibernate.id.optimizer.pooled.preferred=hilo or legacy-hilo

I agree completely. Thanks, Gail On Wed, Aug 28, 2019 at 5:09 AM Steve Ebersole wrote: > In my opinion we really should not drop them unless we also write a > conversion for the existing I'd values in the database to account for the > new scheme the user picks. It's really just left there to al

Re: [hibernate-dev] hibernate.id.optimizer.pooled.preferred=hilo or legacy-hilo

In my opinion we really should not drop them unless we also write a conversion for the existing I'd values in the database to account for the new scheme the user picks. It's really just left there to allow these legacy databases keep working On Wed, Aug 28, 2019 at 7:09 AM Steve Ebersole wrote:

[hibernate-dev] hibernate.id.optimizer.pooled.preferred=hilo or legacy-hilo

Hi, The documentation for hibernate.id.optimizer.pooled.preferred says the following: hilo; legacy-hilo Define a custom algorithm for generating pools of values based on a single value from a table or sequence. These optimizers are not recommended for use. They are maintained (and mentioned) he