Steffen Heil wrote:

> >
> > Database semantics provide explicit transaction control. Use it.
>
> Sorry, I do not understand your statement.
>

Sorry. Database systems provide commit and rollback statement or calls
to control transactions. Unless you are doing something completely
trivial, you should turn auto-commit off and manager transactions
yourself. There is no free lunch in auto-commit: transactions are
started and committed on your behalf. Auto-commit, at least for
Firebird, will be no faster than an explicit commit after every
statement, and a great deal slower that performing commits at the end of
a logical transaction.

Auto-commit basically exists for database system that do record locking
where a causual record access will block updates until a user explicitly
concludes the transaction or terminates the session. For a database
using multi-generational concurrency control, it buys you nothing the
overhead.

Whether for consistence or performances, formal transactions are good
things.

--

Jim Starkey
Netfrastructure, Inc.
978 526-1376