> -----Original Message----- > From: Adam Churvis [mailto:[EMAIL PROTECTED] > Sent: Saturday, July 12, 2003 12:32 PM > To: CF-Talk > Subject: Re: datasource connections > > > > Jim Davis said: > > > > Run the fist and before it finishes, run the second - the second > will > > > return > > > > while the first is still working showing that two connections are in > > > use. > > > > > > > > This is exactly the reason that DB Transactions (and by extension > the > > > > CFTRANSACTION tag) exist. > > > > > > Huh???????? > > > > I'm not sure what you're confused about so I'll assume. > > Jim, > > My "Huh?" was not because I don't understand transactions (trust that I > do), > but was instead a shocked plea for you to explain how you linked threading > to transactions. You are way off base here, Jim; transactional isolation > and ColdFusion request threading have almost nothing to do with each other > when it comes to the essence of what a transaction does.
It wasn't "ColdFusion Request threading" but rather multi-threading in general - there are two main reasons DB transactions exist: 1) because multithreading apps allow concurrent access of resources and 2) to allow for roll-back processing. In other words "since I allow you to do two things at once I need to allow you a way to force only one thing at a time". In SQL transactions solve that problem (as CFLOCK does in CF). If that's not the case (and lord knows I've been wrong before) then I beg humbly for enlightenment. ;^) Jim Davis ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
