Ah, yes, in that sense, I would agree with him, too, from a performance stand point. It still might be preferable to use CFTRANSACTION and rely on ColdFusion's inherent database abstraction when building a packaged application or any other application that could be expected to run against different databases.
I still don't believe that an application that uses CFTRANSACTION is necessarily a bad one, as Jon stated. Perhaps there are some issues with CFTRANSACTION I'm not aware of though? In any case, I hadn't considered Jon's statement from the performance standpoint when comparing the use of CFTRANSACTION to its native equivalents. Benjamin S. Rogers http://www.c4.net/ v.508.240.0051 f.508.240.0057 -----Original Message----- From: Dave Watts [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 04, 2001 3:18 PM To: CF-Talk Subject: RE: CF Webstore > The CFTRANSACTION tag is used to bundle multiple queries into a > single transaction so that the queries can be committed or rolled > back as a group. This is a fundamental aspect of SQL itself: it > is not a short cut. I think that what Jon meant (and I kind of agree with him, if this is in fact what he meant) is that transactional processing should be handled within the database, as opposed to within the application. So, rather than using CFTRANSACTION, you'd put your transactional processing within a stored procedure, and simply call that from CF. Of course, maybe he meant something else entirely. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.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
