The problem it seems is that you are expecting a web app to behave like a classic client server app. Unfortunately, HTTP is a stateless protocol, and simply doesn't behave the same way.
For example, many databases do have the kind of locking you are talking about - for example in Oracle you can do select...for update, which locks the selected record until the update is completed by the session that initiated the select. However, in a web app, this doesn't work - there is no continuous session state for Oracle to track - the select and the subsequent update are entirely unconnected events. It's the nature of the beast. Web application servers work around statelessness to a degree with session management, but it's a bit of a kludge, and doesn't introduce true statefulness. It merely makes the application capable of knowing that two separate actions are part of one session, but since the app isn't connected to the browser in real time, there is no real knowledge of the "in between". There have been a couple of good suggestions on how to potentially work around this, but it's not a flaw in CF or SQL, but rather in the underlying statelessness of HTTP. > -----Original Message----- > From: Claude Schneegans [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 07, 2006 3:29 PM > To: CF-Talk > Subject: Re: Locking Theory > > >>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. > > Easier? This is just a patch to eventually fix problems by hand when > they appear, > PROVIDED someone finds it, not really a method to PREVENT problems from > happening. > > >>DB's are a lot faster than Clipper now, and can store alot more too. > > Hmmm Faster? DB are running on PC 1000 times faster than in the 80's, > this makes a big diffference. > About 7 years ago, I wrote an interpreter for a script language > ColdFusion like, > but based on the Clipper syntax instead of SQL, and believe it or not, > it was FASTER > than ColdFusion! ;-) And it was not written in C nor in Java, but 100% > in Clipper! > > >>Yech. Clipper. What a tank. > > Of course, it is completely medieval now, but in its own time it really > was a great product. > And at least it DID HAVE record and table lock facilities, which CF and > SQL do not have! ;-) > > -- > _______________________________________ > REUSE CODE! Use custom tags; > See http://www.contentbox.com/claude/customtags/tagstore.cfm > (Please send any spam to this address: [EMAIL PROTECTED]) > Thanks. > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:252419 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
