Claude Schneegans wrote: >> 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.
Actually, until the transaction that locked the record committed or rolled back. >> 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. > > If this kind of feature was implemented in ODBC or JDBC, and was > standard in SQL, there could be a tool in CF. > CF is able to keep connections open, manage time limits. > IF ODBC or JDBC was able to manage locks, there would be no problem. Then I have news for you: the feature is implemented in both ODBC and JDBC and is standard in SQL. > I don't agree, it is a lack of facilities in SQL first. > suppose there was an SQL satement like > > LOCK FROM table > WHERE id = blah... SELECT * FROM table WHERE id = blah FOR UPDATE > and that this acted like a query returning a lock handle, > and suppose there was a twin statement like > > UNLOCK handle COMMIT and ROLLBACK unlock everything you locked FOR UPDATE automatically. Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:252522 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
