> But the core advice of "always lock" is definitely the safer option.
I don't think I agree with the "always lock" mentality. This inevitably leads to deadlocks, and I don't believe ColdFusion handles deadlocks in a graceful way. By that I mean that ColdFusion does not roll back all operations in a lock (as if it were a transaction) when killing off deadlock victims. Consequently, you still end up with inconsistent or corrupted data, and the end user sees hard error messages. So, unless you fully understand locking and its side effects, I would not recommend that you lock your code. Even understanding all this, I would recommend locking judiciously. Ben Rogers http://www.c4.net v.508.240.0051 f.508.240.0057 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Silver Sponsor - New Atlanta http://www.newatlanta.com Message: http://www.houseoffusion.com/lists.cfm/link=i:4:189080 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
