On 9/7/06, Claude Schneegans <[EMAIL PROTECTED]> wrote: > >>cftransaction could lock for the duration of user edit ... it however, > depending on the DB level of locking could prevent any other user from > reading data in the table. I would consider implementing such locking a bug > not a feature. [...]
To quip in, usually in a situation where you're concerned about people overwriting other's work, or having to track who's working one what when, it's easier to treat every update as an insert, and just keep a history of who's done what when, and what was there before. Just my .02 US dollars. DB's are a lot faster than Clipper now, and can store alot more too. Yech. Clipper. What a tank. We've still got a couple of DBs in it... thank god for Java and JDBC, neh? Woot... back to your regularly scheduled talk... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:252393 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
