> We usually do it this way:
>
> <cftransaction action="begin">
> <cftry>
>
> [CODE HERE!!!]
>
> <cftransaction action="commit" />
> <cfcatch>
> <cftransaction action="rollback" /> </cfcatch> </cftry>
> </cftransaction>
Unless you're catching errors related to CF-specific logic, as opposed to
database errors, this really isn't necessary. If you simply have something
like this, and the second query fails, the first will also be rolled back:
<cftransaction>
<cfquery datasource="foo"> ... </cfquery>
<cfquery datasource="foo"> ... </cfquery>
</cftransaction>
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev'
in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at
[EMAIL PROTECTED]