idbroker grabs a series of ids and keeps the count in memory until the range is used up. If all the ids are not handed out before the app is stopped there will be gaps. There is no attempt to keep these sequential as this should be unimportant in a pk. However if you do not want to cache you can use
<services.DatabaseService>.<database.>idbroker.prefetch=false and id's will be grabbed from the db one at a time on an as needed basis. the stuff in <> are guesses and/or optional, look for it (or one like it) in TR.props. john mcnally Nathaniel Reed wrote: > > I'm using Turbine 2.1 on the Ingres RDBMS. > > Is there a way to force the ID broker to generate sequential keys for my > table? For some reason, it "jumps" to a higher number whenever I > restart the application and then create another object. If the sequence > starts at 100, for instance, I create 100, 101, and 102, then if I > restart the next object I create has id 120. What's going on? > > Nate > > -- > Nate Reed > Physical Oceanography Distributed Active Archive Center > Jet Propulsion Laboratory (Raytheon) > [EMAIL PROTECTED] > (626) 744-5528 > (626) 744-5506 > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
