That's the whole point of using CFTRANSACTION; it gives you the ability to
roll back multiple transactions if something goes wrong. This is
accomplished by doing a database lock.
Alan McCollough
Web Programmer
Allaire Certified ColdFusion Developer
Alaska Native Medical Center
> -----Original Message-----
> From: dave fauth [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, November 17, 2000 1:04 PM
> To: CF-Talk
> Subject: CFTRANSACTION and Oracle 8.1.6
>
> I have a programmer working for me doing some data conversion using CF
> 4.5.1 sp1. The database is Oracle 8.1.6 on NT using native drivers. He
> wrapped the code in CFTRANSACTION and it is database intensive code. A
> lot
> of selects/updates. When he runs the code, it locks out all other
> database
> queries until the script is done. Is this normal and is this how
> CFTRANSACTION works? Is there something I should be looking at?
>
> dave
> ---------------
> dave fauth
> [EMAIL PROTECTED]
>
> "The opinions expressed here
> are my own and not those of
> DOMAIN technologies, inc."
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Structure your ColdFusion code with Fusebox. Get the official book at
> http://www.fusionauthority.com/bkinfo.cfm
>
> Archives: http://www.mail-archive.com/[email protected]/
> Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
