my 2c
you don't have to worry about a try/catch within the transaction 'cos if
something goes wrong it'll roll back anyway (so <cftransaction
action="rollback"/> isn't needed). The error will still travel up the stack
until it's handled though...
I'm more inclined to have the try/catch "further out" to understand what to do
if the transaction *does* encounter the error and fail - maybe have the try
catch on the method call (that has the transaction within it)
try
reset_account_with_trans(args)
catch
reload_account(args.id)
/catch
/try
but maybe that's me...
HTH
barry.b
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Scott
> Thornton
> Sent: Thursday, 19 May 2005 9:59 AM
> To: CFAussie Mailing List
> Subject: [cfaussie] cftransaction and cftry
>
>
> Hi,
>
> Is it appropriate to use cftransactions with cftry cfcatch blocks?
>
> ala:
>
> <cftransaction isolation="read_committed">
>
> <cftry>
>
> <cfquery>
> </cfquery>
>
> <cfquery>
> </cfquery>
>
> <cfcatch type="database">
> <cftransaction action="rollback"/>
> </cfcatch>
>
> </cftry>
>
> <cftransaction action="commit"/>
>
> </cftransaction>
>
>
> Scott Thornton, Programmer
> Application Development
> Information Services and Telecommunications
> Hunter-New England Area Health Service
> Phone RNH +61 2 49236078
> Fax +61 2 49236076
>
> [EMAIL PROTECTED]
>
> ---
> You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
> To unsubscribe send a blank email to
> [EMAIL PROTECTED]
> Aussie Macromedia Developers: http://lists.daemon.com.au/
>
---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/
