IIRC, the Oracle JDBC drivers set read committed on every connection. Been
a few months though since I've been in Oracle world. You can use Toad or
something to watch the SQL executing live in Oracle to see this. This can
be changed by adding a statement ALTER SESSION me thinks, ahead of your SQ
>From my experience when using queries that need to be wrapped in a
transaction to prevent dirty reads or dirty writes, I will use the
transaction code within the query itself and use the COMMIT at the end
of the query. That way, the ROLLBACK will automatically occur if the
query (that is wrappe
To be clear - database config was only one of several potential
solutions. Good luck!
-Cameron
On 12/3/07, Fennell, Mark P. <[EMAIL PROTECTED]> wrote:
> It helps alright. Helps confirm that the problem is probably in the
> database.
> Thank you!
> As always, ACFUG rocks.
> mf
--
Cameron Childr
Subject: Re: [ACFUG Discuss] Transactions and Commits
I didn't realise cftransaction made everything "golden". Good to know.
Seriously though, it sounds a little like you may be trying to wrap your
entire application or page in a giant cftransaction block. If so,
that's general
I didn't realise cftransaction made everything "golden". Good to know.
Seriously though, it sounds a little like you may be trying to wrap
your entire application or page in a giant cftransaction block. If
so, that's generally a pretty bad idea since heavy use of transactions
can cause locking c
>From my experience when using queries that need to be wrapped in a
transaction to prevent dirty reads or dirty writes, I will use the
transaction code within the query itself and use the COMMIT at the end
of the query. That way, the ROLLBACK will automatically occur if the
query (that is wrapped
