how is it that you can call castor a cache if the oql is not touching the changes that are happening within the transaction? This is a feature of any database system that when you run a query within a transaction the previous changes and updates are reflected in the results to the query. Adam Carbone Open Channel Solutions 1400 Providence Hwy. Suite 1000 Norwood, Ma -----Original Message----- From: Thomas Yip [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 25, 2001 9:04 PM To: [EMAIL PROTECTED] Subject: Re: [castor-dev] castor OQL transaction query scope... -----Original Message----- >From: Dafydd Hopkin [mailto:[EMAIL PROTECTED]] >Sent: Monday, July 23, 2001 9:56 AM >To: [EMAIL PROTECTED] >Subject: [castor-dev] castor OQL transaction query scope... > >Hi, > >Are altered objects, cached within Castor subject to OQL queries, or do >these go straight to the database? go straight. >i.e. If a transaction is begun, and object is retrieved by >database.get(...), and some fields altered, will an OQL query then run >return a list of objects as per the status before the transaction, or will >it take it to consideration any changes to this object? No, it doesn't not consider the recent change. Thomas ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
