On Jun 22, 2006, at 10:47 PM, Usha wrote: It is the same process which holds the lock on ^TIU(8925,18) when I lock the node using the LOCK command. And the process status shows Forgive me if I'm stating the obvious here, but locks in MUMPS are purely advisory (some people say they don't "lock" anything), and in Fileman, enforcing mutual exclusion is generally left up to the user (programmer). In the case of the DBS calls, there are flags you can use to ask Fileman to do the locking for you, but for some reason that I don't fully understand, the manual recommends that you not use them. (My guess is that it's a matter of the unpredictability of what other processes might do.) Database integrity tends to be a bit ad hoc in Fileman in the sense that you'll find that different programmers will come up with different techniques to try and enforce integrity constraints. My guess is that this is one of those cases. Gregory Woodhouse "Judge a man by his questions not his answers." --Voltaire |
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
