Subject | Readonly datasets |
---|---|
Author | Magni Thor Mortensen |
Post date | 2006-10-13T15:54:14Z |
Hi
I have an application with browsable dbgrids. Whenever a grid is open
the OAT stops moving.
I have tried many variations of "TimeoutProps" settings on the
Transaction to no avail.
The only solution I found was to create a timer to auto commit every 5
seconds. and have all my TIBOQuery's commit action on invalidateCursor.
This works fine, except for the fact that the datasets get very slow
(browsing, incremental search, etc...)
I had an idea to have the datasets use a readonly/read commited
transaction, and do all my updates,inserts and deletes with another
query connected to a read/write transaction.
but the problem with that is that the dataset insists on being read-only
when connected to a read-only transaction.
Is there a better way of doing this?
Best regards
Magni
I have an application with browsable dbgrids. Whenever a grid is open
the OAT stops moving.
I have tried many variations of "TimeoutProps" settings on the
Transaction to no avail.
The only solution I found was to create a timer to auto commit every 5
seconds. and have all my TIBOQuery's commit action on invalidateCursor.
This works fine, except for the fact that the datasets get very slow
(browsing, incremental search, etc...)
I had an idea to have the datasets use a readonly/read commited
transaction, and do all my updates,inserts and deletes with another
query connected to a read/write transaction.
but the problem with that is that the dataset insists on being read-only
when connected to a read-only transaction.
Is there a better way of doing this?
Best regards
Magni