> I've been under the impression that <cftransaction> serializes access to the > entire datasource ... in which case I think I would be more inclined to use > the named cflock approach since it wouldn't affect the performance of any > other pages which might be accessing other parts of the db in question...
It would depend on the database. CFTRANSACTION just tells the database to start, end commit or rollback a transaction, wether the database engine thinks it should serialize all access to the entire datasource is up to it, but most would be sensible about it (i.e they will allow transactions to execute simultaneously until such point as a conflict is found, if one transaction would not interfere with another then the (good) database should have no problem allowing them to execute at the same time). :-) --- James Sleeman Innovative Media Ltd Ph: (03) 377 6262 http://www.websolutions.co.nz CAUTION: The information contained in this email message is confidential and may be legally privileged. If the reader of this message is not the intended recipient you are notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately and destroy the original message and any attachments. Views expressed in this communication may not be those of Innovative Media Ltd. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.372 / Virus Database: 207 - Release Date: 6/20/2002 ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
