Hi Jin,
Jin Bal wrote:
At the moment it is not causing side effects as there is no key collision (yet) - I was wondering whether this was expected behaviour.
My understanding is that OJB uses a temp negative PK before insert. does it then lookup the db generated one and set it in the persistent object durign the afterStore() operation?
yep! I made some tests with PB-api and ODMG-api and it seems that when using the odmg api + SequenceManagerNativeImpl + main object with single reference, the FK set in the main object be wrong (negative value). Is this your problem too?
Haven't got any code to post right now (will follow shortly) could there be an issue with the cache (i.e not flushing after insert)?
normally the object will be stored to cache after the afterStore() call.
regards, Armin
Thanks Jin
----- Original Message ----- From: "Armin Waibel" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]> Sent: Tuesday, July 06, 2004 5:57 PM Subject: Re: sequencemanagernative and mysql
Hi Jin,
Jin Bal wrote:
I'm finding that the PK field with autoincrement are negative numbers -
is this normal behaviour or is somehting up?
hmm, the negative values are temporary used before the object was written to DB. See here
http://db.apache.org/ojb/docu/guides/sequencemanager.html#Identity+based+seq uence+manager
Does it cause side-effects in your environment? Could you post some pseudo code to show the problem?
regards, Armin
TIA Jin
--------------------------------------------------------------------- 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]
