Barry, in the example given why do you need a transaction at all, since it is a single delete statement. Am I missing something or is the example trivial?
Certainly if there was a a group of changes that need to succeed or fail together they would need a transaction. Generally databases use implicit transactions anyway so a single delete statement that may delete more that one record and also cascade delete dependent records will succeed or fail as a single atomic action. Be aware that often in ADO (depending on cursors selected) a 'live' recordset is returned not a snapshot of the data at the moment of query, as is always the case in CF. The isolationlevel attribute of the cftransaction tag controls how this 'explicit' transaction interacts with other current transactions (other current actions by other users) Good article here: http://www.macromedia.com/devnet/mx/coldfusion/articles/cftransaction.html You do need to determine what capabilities the Database supports. My particular beef is that <cftransaction> must be opened and closed in the same template - so while I might try to encapsulate various database actions I cannot nest transactions tags (and have them automatically collapse into a single transaction like they do when I use stored procs that nest transactions in SQL Server). I am trying to work out how I might use the underlying Java classes to have a little more control without having to use stored procs which just add to maintenance hassles Elliot ---------------------------------------------------------- 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 www.mail-archive.com/[EMAIL PROTECTED]
