Ask a Question related to Coldfusion Database Access, Design and Development.
-
f_u_c_k_h_e_a_d #1
MX7 Transactions - Read Committed VS SerializeableProblem
I am upgrading a large app from CF5 to MX7 and in testing have discovered a
bunch of problems associated with Oracle database access. The error is
"ORA-08177: can't serialize access for this transaction". After looking a bit
into this error I have discovered that the default database access mode of cold
fusion MX6 or MX7 after applying the client variable hot fix is now
"serializeable" instead of "read committed". I want teh db access to continue
to be "read committed" as it was - I can override the coldfusion default access
by establishing a <cftransaction> for each query and plugging in a database
access mode for each - but there's got to be a better way . Can I override the
Coldfusion default database access mode and set it back to read-committed w/o
wrapping a transaction around all my queries? Why was this changed in the
first place? The solution offered by macomedia does not address the fact that
I need to run in read-committed mode. Thanks!
f_u_c_k_h_e_a_d Guest
-
Transactions
I'm trying to determine where within my code I need to place 'ObjectContext.SetAbort' Here's some pseudocode:... -
example for read committed/volitile functions
I tried to reproduce the case where 7.4 and 8.0 differ on the scope of volitile function with READ COMMITTED transactions. In an open... -
Transactions - ADO/SQL or both?
Hi, When considering transactions should you: 1) - Put a begin and end tran inside every SP that alters data? 2) - Use the ADO Transaction... -
Visibility of committed changes
Hello. I've been reading up on Oracle lately and I find something quite strange in the "Concepts" manual. This is what they claim: ... -
committed data being rolled back???
David wrote: What is affecting the updated rows is other code in the database. Your job is to figure out what it is. I would suggest using...



Reply With Quote

