Subject Commit/CommitRetaining
Author bhatakeyama
I have an application where the user modifies the database with a DBGrid.
Generally the application will be kept open most of the workday. After the
user edits a row a CommitRetaining() is executed.

I read, however, that CommitRetaining() leaves the transaction open
and holds up 'garbage collection'. Is this necessarily a bad thing?
I don't necessarily like the time delay that a Commit and reopening
of all the datasets. Is TIB_Database::Refresh() a better choice?
What's the pro/con's between CommitRetaining & Refresh()?