|Subject||Re: [IBO] TIBOTable Access Violations when Using set ranges|
> I have investigated it and we discussed this issue someLike I said, that is what it is doing. There is a flag that gets set when an
> eight months ago. One way or another a stamp has to be
> associated with the TIBOQueries indicating last time an
> table UPDATE was issued since the start of a TRANSACTION,
> this flag to be checked on a ROLLBACK forcing a (SQL) REFRESH
> or not and to be reset after either a ROLLBACK or COMMIT.
update takes place. Only those datasets are to be affected when a rollback
> I know it still won't be absolute perfect, but probablyYes, that is already part of the design and has been for some time.
> quite a bit better than waiting for all open TIBOQueries
> to ROLLBACK and refreshing their SQL Queries.
CPS - Mesa AZ