One active IB transaction the whole lifetime of a single user application

Question

Are there any negative impacts when a single user application uses only one IB transaction, which is active as long the program runs? By using only CommitRetaining and RollbackRetaining.

Background: I want to use IBQuery(s) and connect them to a DB Grid(s) (DevExpress), which loads all records into memory at once. So I want to avoid re-fetching all data after every SQL insert command. IBTransaction.Commit would close the dataset.

Answer 1

It sounds to me like you're trying to use a database feature in order to avoid using TClientDataSet, which is clearly the preferred way of working in Delphi these days. Why go out of your way and use questionable transaction practices instead of following the more common pattern for database component use, which already is a better solution to the problem at hand?

Answer 2

CommitRetaining and RollbackRetaining are not good.

transaction have to be very short.