> Still, I don't get the whole concept of "If it's not that > important, don't lock it"... because.. if it's not that > important, and you know the numbers might be inaccurate, why > do it at all?
The cost of locking may outweigh the value of an individual data point. For example, in a database, you may want to determine the average value of a column, in a table that has a million rows. The SQL to do this is quite easy, but by default it will prevent write access to those rows while the query is running. If a couple of values changed during the query, it wouldn't noticeably affect the outcome anyway. 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! This email has been processed by SmoothZap - www.smoothwall.net ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create Web Applications With ColdFusion MX7 & Flex 2. Build powerful, scalable RIAs. Free Trial http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJS Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:283976 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
