Re: Commit after transacton is completed

On Fri, 25 Nov 2005 07:57:39 -0700, "Mark A" <nobody_at_nowhere.com> wrote:

>In this case, the "logical transaction" is really one update (or delete in
>my example), however doing a commit for every delete is a waste of
>resources. But only committing after all the rows are updated (or deleted)
>is equally bad (as already noted). So committing every 1000 updates (or
>deletes) does make sense with such a "transaction".
>

But only committing after all the rows are updated (or deleted)
>is equally bad (as already noted).

Actually it isn't bad at all (as also already noted), if you are aware what a transaction is.
Status flags are just a hack implemented by developers exposed to lousy commercial software and equally lousy products forcing you into single record commit.
One should address the causes, and stop implementing further hacks.

--
Sybrand Bakker, Senior Oracle DBA