Thx For the reply chris. Actually I was thinking the same but just wanted to confirm.
Anyway thanks for quick reply. On 11/24/06, Chris Howe <[EMAIL PROTECTED]> wrote:
For performance purposes, when it the service picks calls the database for the first next sequence (10020) it will cache the next ten (10020-10029) so that it doesn't need to go back for some more. If you do a search for SequenceValueItem, I'm sure you'll be able to find where this (10) is set --- "Alex D. Fleming" <[EMAIL PROTECTED]> wrote: > Hi, > > I noticed that whenever the next sequence id is > generated it takes the next > value from the previous one.But when we start the > server then it takes the > first value that is multiple of 10. > For Example : If previous id is 10012 then the next > sequence id that it will > take will be 10013 and when I restart the server > then it takes 10020 instead > of 10014. > > Any specific reason about it. > Just asking it to increase my knowledge. > > Thanks in advance > -- > Regards > Alex D. Fleming >
-- Regards Alex D. Fleming
