Subject | [IBO4] RollBackRetaining |
---|---|
Author | hans@hoogstraat.ca |
Post date | 2001-08-05T05:08:15Z |
Hello,
Same setup as previos CommitRetaing question. (IBO4)
Got a TIBOQuery hooked up to TIB_DataBase with AutoCommit = False
to enable Transaction CommitRetaining and RollBackRetaining control.
All works, I can commit or rollback.
The program goes thru various screens opening TIBOQUERY tables,
lots of them M/D via DataSource properties, all in READ ONLY
mode, to finally get to a R/W table for user updates.
None of the READ ONLY tables are closed, most screens Modal.
Interesting effect, when a RollBackRetaining is issued after
an update on the last R/W table, it takes a while and the reason
is that IB rolls back and re-issues all SQL for every open table of
every open screen as seen in IB_Monitor. Question why ?
When I close all R/O tables when reaching the last screen with
the R/W table, a RollBackRetaining only affects this only open
table. What I'm I doing wrong, any ideas ?
Best Regards,
Hans
Same setup as previos CommitRetaing question. (IBO4)
Got a TIBOQuery hooked up to TIB_DataBase with AutoCommit = False
to enable Transaction CommitRetaining and RollBackRetaining control.
All works, I can commit or rollback.
The program goes thru various screens opening TIBOQUERY tables,
lots of them M/D via DataSource properties, all in READ ONLY
mode, to finally get to a R/W table for user updates.
None of the READ ONLY tables are closed, most screens Modal.
Interesting effect, when a RollBackRetaining is issued after
an update on the last R/W table, it takes a while and the reason
is that IB rolls back and re-issues all SQL for every open table of
every open screen as seen in IB_Monitor. Question why ?
When I close all R/O tables when reaching the last screen with
the R/W table, a RollBackRetaining only affects this only open
table. What I'm I doing wrong, any ideas ?
Best Regards,
Hans