| Subject | RE: [IBO] Accessing cached changes of IBOQuery1 by IBOQuery2 within the same transaction |
|---|---|
| Author | Jason Wharton |
| Post date | 2018-10-17T17:05:34Z |
Yes, this is one of the weaknesses of using
CachedUpdates. If you use the Lookup() operation on the dataset with
cached updates then you should get the modified values from the
dataset.
Please let me know if this is sufficient or if you need
something more comprehensive.
Kind regards,
Jason Wharton
From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]
Sent: Wednesday, October 17, 2018 2:05 AM
To: IBObjects@yahoogroups.com
Subject: [IBO] Accessing cached changes of IBOQuery1 by IBOQuery2 within the same transaction
I'm testing the CachedUpdates feature with an IBOQuery. Since all the changes are done in memory, until they are applied, how can I access these changes via other queries within the same transaction *before applying*?
With direct updates I just do a select over the required data, which doesn't work with CachedUpdates as the changes aren't in the database yet.
As far as I see in the "TransactionOAT" tutorial, only the "DML Caching" feature seems to be at least partly related to this topic, but for it to work the chached changes have to be applied first, which is not what I'm looking for, because that way conflicts could happen again, which I'm trying to avoid by using CachedUpdates.
Since both queries use the same transaction, it is aware of the
changes, so I'm wondering if there is a way to access the cached changes by
doing something like "select * from A_TABLE using chachedupdate".
Best regards,
Patrick