I recall back in the early EARLY 80s working on a version of Pick (cannot remember which though!) that did not have any implicit locking at all on READs or WRITEs, only the LOCK / UNLOCK mechanism. We had a header file of assigned LOCKs that we included everywhere so others could figure out what the heck we were doing. I don't actually remember if the version didn't HAVE things like READU/ WRITEU/ etc, but that was how we were told to do things. It was a very nice thing to see real locking implemented.
-----Original Message----- From: Mark Johnson To: [EMAIL PROTECTED] Sent: 7/5/2004 8:48 AM Subject: [U2] READU vs LOCK I've just acquired another client who's system doesn't use READU (sic) but uses LOCK then UNLOCK to surround the READ and WRITE statements. They have a table to assign the LOCK numbers to specific files but it seems incredibly overkill. Does anyone else have this kind of setup and can offer some form of rationale. I can imagine the prevailing thought process but I would like to hear it first hand. Another client who's software is circa 1975 (still running, thank you) has this and I thought it was the way things were done then. So that begs the question, was there a time when READU (sic) wasn't available and you could only use READ so you had to protect things yourself. This is not to be confused with manual record locking with a support table or fields. These examples use the system LOCK command. Thanks in advance. Mark Johnson ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
