See my latest commit for an - hopefully - acceptable degree of certainty that the id really is unique. In the - very unlikely - case that it really is not unique you can still catch the exception when starting the tx and retry with a new one.
Acceptable? Oliver 2005/11/23, Oliver Zeigermann <[EMAIL PROTECTED]>: > 2005/11/23, Joerg Heinicke <[EMAIL PROTECTED]>: > > Oliver Zeigermann <oliver.zeigermann <at> gmail.com> writes: > > > > > To me it seems generatedUniqueTxId does exactly as advertised in > > > Javadocs. Don't you agree? > > > > No. :) This dismisses my argument about externally generated ids, yes. But > > two > > different threads calling generateUniqueTxId() at the same time still get > > the > > same "unique" id as the first thread calling this method does not > > "preserve" the > > id. So the current implementation does not fulfill the "contract" mentioned > > in > > the Javadocs. > > Argh! That's right, I guess :( Any idea how to solve this? > > Oliver > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
