Hi Boris,
I don't think you have a other option. The implements interface TimeStampled simmulates the actual storing of that inforamtion in the db. So to make use of that same object again, you need to keep it. Getting the same object later again, will give it a new timestamp. The two sollutions are indead, to store the instance (object with the timestamp) in a session instance. Or store the timestamp information in the db. Tjeerd > -----Original Message----- > From: Boris Klug [mailto:[EMAIL PROTECTED]] > Sent: 02 October 2002 17:01 > To: [EMAIL PROTECTED] > Subject: [castor-dev] Long transactions - how to do it (again!) > > > Hello! > > I have a question regarding long transaction. I read the ml > archive and found > a lot of posting regarding long transaction but no posting > fits to me. > > What I want to do is the usual stuff: > Web-application, user get information, sometimes modifies it > and than wants to > store it. > > Solution would be using long transactions for this. The > problem is that when > the user hit "save", all I have is the id of the object and > the values that > were changed but no longer the object I got from db.load(). > So I tried to get the object from the db again using OQL, > modified the context > of the object and than do a db.update(). Castor than told me, > that this is > not the object I db.load()ed (which is right). The object ist > implements > TimeStampled. > One solution would be to store the original object in the > session data but I > dont wanna do it. Any other solution to do it whithout > storing the timestamp > in the database? > > -- > Dipl. Inform. Boris Klug, control IT GmbH, Germany > > ----------------------------------------------------------- > If you wish to unsubscribe from this mailing, send mail to > [EMAIL PROTECTED] with a subject of: > unsubscribe castor-dev > This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
