|Subject||RE: [IBO] IB_TransForUpdates and BLOB fields|
|Author||IBO Support List|
From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com] On Behalf Of Thomas Lenders
Sent: Monday, December 2, 2013 6:20 AM
Subject: [IBO] IB_TransForUpdates and BLOB fields
I recently started to experiment with setting IB_Transaction to a READONLY Transaction and supplying an additional READ/WRITE Transaction in IB_TransForUpdates property.
The idea is to reduce the amount of READ/WRITE Transaction open at the same time on the server.
1. Is this an intended use of this property?
2. I noticed that I seem to be unable to edit BLOB fields now (using TIB_Memo component).
3. Deleting IB_TransForUpdates and setting IB_Transaction to be READ/WRITE makes the BLOB editable again (it’s “editable” before as well but changes are not preserved).
Hope someone can help me out or share some thoughts on how to overcome the problem of long running transactions. We also have the problem that we can’t just use a component with client-side caching (like TClientDataset) because there is business logic in the database, implemented as triggers, that needs to fire and possibly prevent some data from being edited on posting the changes but before the Tx is being committed (or let’s say I don’t yet know how to use a TClientDataset in that way).