Each entity will have its own hilo generator, which means it has its own set of hi/lo values, regardless of whether you're using the same table or not.
"reasonable" values depend a lot in the app type and usage. If you care to expand... Diego On Thu, May 6, 2010 at 15:50, nicklang <[email protected]> wrote: > Hi, > > I'm using hilo for my id generation - and here is my confusion... > > I'm updating 3 entities (corresponding to 3 tables). > > I checked the mysql log and I see 3 select/update queries to the hilo > table before the real queries - I thought the idea of hilo was that it > only needs to get the hi once?? > > I'm using the value of 1000 for maxlo - I'm not sure if this is > reasonable. The way I understand it is that the client gets the hi > once say its value is 58 - then it multiplies by the maxlo and > increments to generate more ids - for example 58001, 58002, 58003... > > But instead I'm getting 58058, 59059, 60060 - what is up with that?? > > Any insight is appreciated! > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<nhusers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
