by another application???
I'd be very gratefull for information on how this might work
/Keld
- Original Message -
From: "Rainer Müller" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, March 28, 2003 5:40 PM
Subject: Re: [castor-dev] Long transactions - how does it
Hi Keld!
Your class should have a instance variable where the timestamp will be
held. You do not have to put a timestamp into the database. The
timestamp variable in the object is used by Castor to see if the object
has been modified.
So, you will open a transaction, load the object and close
On Castor's web site you can read about long transactions:
http://castor.exolab.org/long-transact.html
It says
"Since the time interval between the first and the second transaction is relatively
big, it is desirable to perform dirty checking, i.e. to check that the object has not
been modifie
