Subject long commit on read transactions
Author David Goodman
We're using IB6 and Firebird InterClient. Our app does all database
access in a transaction. For fetches, the select completes in about
100ms, but the commit afterwards takes 10,000ms to execute.

When we switched it to rollback after a fetch, it took 0ms.

When we perform an update the whole thing, including commit takes
about 1,700ms.

Our questions are twofold:
1) Why does a commit after a fetch take so long?
2) Is it safe to use rollback as a work-around?

Thanks,
- Dave