Can you provide a short example of statements that will cause problems in two separate DNS in a cftransaction block that won't cause the same problems in a stored proc?
-----Original Message----- From: Adrocknaphobia [mailto:[EMAIL PROTECTED] Sent: Wednesday, 8 June 2005 1:58 To: CF-Talk Subject: Re: FW: Get New Record ID in ORACLE [snip] I've said this above, but cftransaction is drastically different than the transaction in a database. Plus it really doesnt fit well in an MVC pattern. Again, cftransaction doesnt give you row level locking. Which is pretty key in a database transaction. If you had two applications using the say schema. Both apps in CF, running seperate instances or using two seperate DSNs. They know nothing of each other transactions. You are going to end up with race conditions, which is what the transaction in the database will prevent. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:208919 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=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
