I'm looking for more information about using <CFTransaction>.
My personal opinion is that it's better to use SQL Server transactions
within our stored procedures (cuz we are using SQL 2000 as our back end),
and transfer as much business logic as possible to the stored procs.
However, in a few cases, we've seen the requirement for something like this:
<cftransaction action="BEGIN">
<cfstoredproc></cfstoredproc>
<cfif somecondition>
<cfstoredproc></cfstoredproc>
<cfelse>
<cfstoredproc></cfstoredproc>
</cfif>
</cftransaction>
My concerns are that this may cause problems if the stored procedures
themselves contain transaction processing. And I need to make a
recommendation based on solid information on whether to allow this process,
or force the developers to take the time to wrap this logic within one
stored proc call. (of course, they can call existing stored procs from
within a stored procedure, and check the return codes to determine if a
rollback needs to happen before processing is complete).
So, any suggestions? Thanks in advance.
Shawn Grover
______________________________________________________________________
Why Share?
Dedicated Win 2000 Server · PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER
Instant Activation · $99/Month · Free Setup
http://www.pennyhost.com/redirect.cfm?adcode=coldfusionc
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
