Hi Boris,
How did you implement the timestamp? Only through the interface, or also through the db records in the table? If only through the interface, Castor will probutly not reconize your db updates. If implemented through db records with timestamp, then also update the timestamp when you modify the record (otherwise Castor probutly also doesn't see your update). I'm not a expert, I could be wrong, but I thought of the things. Tjeerd > -----Original Message----- > From: Boris Klug [mailto:[EMAIL PROTECTED]] > Sent: 04 October 2002 16:21 > To: [EMAIL PROTECTED] > Subject: Re: [castor-dev] Long transactions - how to do it (again!) > > > Hello! > > now I have long transaction running. I implemented > TimeStampable for my > objects and it works now. The problem is now the caching of > the objects. When > I set cache-type in the mapping for for my class to "none", > the timestamp > does not work any longer (like stated in the docs). If I > enable caching, > everything works well, but modification to objects by other > applications > outside castor are not recognized. > > So any hints? I need long transaction but I also have to > modify the objects > outside Castor. Clues? > > > -- > 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
