AHH...
>Use the ISOLATION attribute for additional control over how the database
>engine performs locking during the transaction.
>
This is what I was looking for!!
-----Original Message-----
From: Semrau, Steven L Mr SRA
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 17, 2001 1:14 PM
To: CF-Talk
Subject: RE: CFTRANSACTION
Are you saying that the example in the documentation with regards to using
the ACTION of /ROLLBACK and /COMMIT does not work? I haven't had a need to
use CFTRANSACTION in 4.5 as of yet.
>From Documentation:
Within the transaction block, you can commit a transaction by nesting the
<cftransaction ACTION="COMMIT"/> tag or roll the transaction back by nesting
the <cftransaction ACTION="ROLLBACK"/> tag within the block.
Within one transaction block, you can write queries to more than one
database; however, you must commit or rollback the transaction to a
particular database prior to writing a query to another database.
By using CFML error handling, you have control over whether each transaction
is to be committed based on the success or failure of the database query.
Use the ISOLATION attribute for additional control over how the database
engine performs locking during the transaction.
Steven Semrau
SRA International, Inc.
Senior Member, Professional Staff
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Com: (703) 805-1095
DSN: (703) 655-1095
-----Original Message-----
From: Diana Nichols [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 17, 2001 2:54 PM
To: CF-Talk
Subject: RE: CFTRANSACTION
As I understand it, CFtransaction ONLY does just that...it rolls back all
database operations within it if any of them fails. The only way I'm aware
of to be sure that there is no transaction between one query and another is
to use <cflock> around them....or, if using SQL, to retrieve the new ID with
@@identity in the same query.
D
*************
Diana Nichols
Webmistress
http://www.lavenderthreads.com
770.434.7374
"One man's magic is another man's engineering." ---Lazarus Long
-----Original Message-----
From: G [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 17, 2001 1:46 PM
To: CF-Talk
Subject: Re: CFTRANSACTION
I don't think a flaw in <CFTRANSACTION> would not necessarily be a candidate
for causing this kind of problem. CFTRANSACTION is concerned with defining
a set of (usually) database operations as a "transaction" for roll back
purposes. Most of the problems we've had with this tag stem from misuse as
opposed to reliability of the tag.
Are there problems with this tag that I am not familiar with????
Brian
----- Original Message -----
From: "Bill King" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, May 17, 2001 11:47 AM
Subject: RE: CFTRANSACTION
> Speaking of "purpose-free" the <CFTRANSACTION> is not even reliable for
> multiple queries.
>
> I had a problem with users on a high-volume site having OrderIDs
duplicated
> and caused major problems. I fixed it by getting the ID within my order
> query with that lovely SET NO COUNT option in SQL 7.
>
> I wonder if there are going to be any improvements in the future of this
> tag?
>
> - BILL -
>
> -----Original Message-----
> From: Aidan Whitehall [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 17, 2001 10:06 AM
> To: CF-Talk
> Subject: RE: CFTRANSACTION
>
>
> > Yes, as written this use of CFTRANSACTION is purpose-free.
>
> I'll have to remember that phrase... extrememly diplomatic!
>
>
>
> Thanks
>
> --
> Aidan Whitehall <[EMAIL PROTECTED]>
> Netshopperuk
> Telephone +44 (01744) 648650
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
