Hi Rainer, I think that you encounter an interference of the cache. Please try if clearing the cache right before the secong OQL query solves the problem.
If this is the case I think using the PerBroker cache implementation should solve the issue. cheers, Thomas > -----Original Message----- > From: Rainer Klute [mailto:[EMAIL PROTECTED] > Sent: Friday, February 20, 2004 12:06 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: ODMG: Object modifications outside transactions > > > From the ODMG tutorial and the API doc I had the impression > that a persistant object has to be modified inside a > transaction in order to become effective in the database. > > My application begins a transaction, retrieves a persistant > object from the database using an OQLQuery and closes the > transaction. Then it modifies one of the object's attributes > outside any transaction. After that the reference variable > pointing to the object is to null to make sure that no more > modifications are done, especially not inside a transaction. > > What I expected was that the modification was not persisted, > i.e. when retrieving the object again from the database in a > new transaction using the same OQLQuery as above, it should > be the original, unmodified version. However, this is not the > case: the modification is visible. > > Is this a bug in OJB's ODMG implementation or a > misunderstanding on my side? > > Best regards > Rainer Klute > > Rainer Klute IT-Consulting GmbH > Dipl.-Inform. > Rainer Klute E-Mail: [EMAIL PROTECTED] > K�rner Grund 24 Telefon: +49 172 2324824 > D-44143 Dortmund Telefax: +49 231 5349423 > > --------------------------------------------------------------------- > 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]
