Ken, in NH is even better because it respect a "sequence per table". An High is requested per sessionFactory per Persister... Example: Table-A: 101, 102,103,104......501,502.... Table-B: 201, 202, 203, 204... 801,802....
2009/3/26 Ken Egozi <egoz...@gmail.com> > the way I understand it: > > a generated 64bit ID will consist of a HI and LO 32bit values > (HI*32bit+LO) > > when a SessionFactory kicks in, it requests (and increments) the HI from > the DB. > as an outcome - every SessionFactory gets a range (using the HI) then > increments the LO on each new entity. > > > > > On Thu, Mar 26, 2009 at 11:12 AM, Peter Morris <mrpmor...@gmail.com>wrote: > >> >> > >> It is the thing that you last said, when exhaust a new Hi value is >> obtained, >> Lo values are incremented everytime an object is persisted. >> < >> >> Ah I see, that makes sense. I am confusing it with the other approach >> where >> only the exact number of IDs are requested when an update is required. >> >> >> >> Pete >> ==== >> http://mrpmorris.blogspot.com >> >> >> >> > > > > > -- > Ken Egozi. > http://www.kenegozi.com/blog > http://www.delver.com > http://www.musicglue.com > http://www.castleproject.org > http://www.gotfriends.co.il > > > > -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to nhusers@googlegroups.com To unsubscribe from this group, send email to nhusers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
