First, I thought about writing a new IdGenerator, but then I found out that
class names such as IDBroker and SequenceIdGenerator are hard coded in
TurbineDatabaseService.java. Therefore, I concluded that new IdGenerators
cannot be added with a change in a configuration file. Am I right?
The solution to my problem would be to modify IDBroker so that it doesn't
prefetch IDs (this could be a configuration flag such as clever quantities)
In addition, I would set ID_TABLE.QUANTITY=1 and turn off "clever quantities".
I've seen that the code to test for idbroker.clever.quantity is commented out
because the configuration object is never set. Where should that be done? In
TurbineDatabaseService.setupIdTable() ?
Thanks,
Gabriel
John McNally wrote:
> I do not believe so. Please feel free to add the functionality and
> submit it.
>
> john mcnally
>
> Gabriel Moreno wrote:
> >
> > Hi,
> > I want to use IDBroker for a table but the problem is that the IDs in
> > this table are renumbered by an overnight process. I think that IDBroker
> > has a "cache" of IDs to be used, and those may not be valid after the
> > renumbering. Is there any way to "turn off" the cache or invalidate the
> > cache so that it queries ID_TABLE again.
> >
> > Thanks in advance,
> >
> > Gabriel
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
