> Just to follow up on this thread, is the final verdict that > you must use cflock to prevent these kinds of concurrency > issues in the database, UNLESS you use CFTRANSACTION with the > serializable isolation level?
That's not my final verdict, for what that's worth; depending on the specific queries and the granularity of locks (in databases that use locking) you may well be able to use REPEATABLE_READ or even READ_COMMITTED. But if you need a serializable transaction, you shouldn't be afraid to use one. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion 8 - Build next generation apps today, with easy PDF and Ajax features - download now http://download.macromedia.com/pub/labs/coldfusion/cf8_beta_whatsnew_052907.pdf Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:288385 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
