On Feb 8, 2006, at 17:10, Doug Nebeker wrote:
When you don't wrap everything in a transaction, each statement
becomes
it's own transaction. And the database file is opened, updated, and
closed on each transaction. So your first case had roughly 50
times the
amount of file I/O and transaction startup/commit overhead as the
second
case.
I see. Let me ask a few more questions to help me get the picture.
A transaction is stored in memory until committed? As a rule of thumb
can I imagine that one transaction equals roughly to a single open/
edit/close? Is the file opened and locked right when the transaction
begins?
-- fxn
