Sorry that's not correct. CFTRANSACTION starts a db transaction like any other, including the ability to make the transaction SERIALIZABLE. That's what it's for.
You may be thinking of CFLOCK. -----Original Message----- From: Adrocknaphobia [mailto:[EMAIL PROTECTED] Sent: Wednesday, 8 June 2005 12:06 To: CF-Talk Subject: Re: Get New Record ID in ORACLE Well its not really the same. CFtransaction will prevent race conditions and rollbacks in CF, while CF has a lock and wont send similar requests until the transaction is complete. Another request could come in through cf that is not in a transaction that is executed. Transactions on the database side will actually lock rows and the specific data being updated. CF doesnt have that level of power, all its basically doing is pausing all other requests, not locking rows. They are almost two completely different functions. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:208825 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
