> Hello Thomas, > > This might have been my own fault. I fetched the an object within other > transaction and tried to set it to another object's field within another > transaction and then tried to persist the container object. This caused > a primary key violation because it was already in the database.
OK! > All JDO > flags (pesistent, dirty, transient) seem to be false even after data has > just been fetched from database, which is weird. > > Is this expected behaviour? No, it's really an issue. there is already a thread regarding this issue on the mailinglist. I'm currently working on a fix for this problem. Objects loaded by OJB should show the right flags to user code ! cheers, Thomas > -Marko > > > > > I'm not aware of any shortcomings of the JDO stuff. > > please post a code sample to understand your problem. > > > > If there is a bug we'll have to fix it! > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > ______________________________________________________________________________ Spam-Filter fuer alle - bester Spam-Schutz laut ComputerBild 15-03 WEB.DE FreeMail - Deutschlands beste E-Mail - http://s.web.de/?mc=021120 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
