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 <steven.ebers...@gmail.com> 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 allow these > legacy databases keep working > > On Wed, Aug 28, 2019, 12:08 AM Gail Badner <gbad...@redhat.com> wrote: > >> 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) here simply for use by legacy applications that used these >> strategies previously. >> >> Will these settings be supported long-term, or are there plans to >> deprecate/remove them? >> >> Thanks, >> Gail >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
