hsteigstra
Member²
I have a small problem in using Cached Updates.
I am "abusing" cached updates to do some temporary administration that will not be inserted into the database. So I have a SQL and unique rowid chosen arbitrary from one of the tables. After receiving a "record changed by another user" I found that the TOracleDataSet fetches the row that is involved from the database for verification?
OK, I can adapt for that, problem solved now, but why is the database addressed with cached updates when only posting? In my perception it should be done only when the modifications are applied or am I incorrect in this? I now get an overhead of database access that is unnecessary.
I am "abusing" cached updates to do some temporary administration that will not be inserted into the database. So I have a SQL and unique rowid chosen arbitrary from one of the tables. After receiving a "record changed by another user" I found that the TOracleDataSet fetches the row that is involved from the database for verification?
OK, I can adapt for that, problem solved now, but why is the database addressed with cached updates when only posting? In my perception it should be done only when the modifications are applied or am I incorrect in this? I now get an overhead of database access that is unnecessary.
