Resent-From: POSTGRES mailing list <postman@postgres.Berkeley.EDU>
Resent-Message-Id: <199405310540.WAA12089@nobozo.CS.Berkeley.EDU>
Sender: owner-postman@postgres.Berkeley.EDU
Date: Tue, 31 May 1994 02:40:14 +0100
From: Mark Metson <gpurdy@fox.nstn.ns.ca>
Subject: Re: Use by a Business 
To: "Paul M. Aoki" <aoki@postgres.Berkeley.EDU>
Cc: postgres@postgres.Berkeley.EDU
In-Reply-To: <199405301940.MAA19840@faerie.CS.Berkeley.EDU>
Message-Id: <Pine.3.89.9405310244.A1720-0100000@acamn.aca.uucp>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Resent-To: postgres-redist@postgres.Berkeley.EDU
Resent-Date: Mon, 30 May 94 22:40:37 -0700
Resent-XMts: smtp

Perhaps I dont really specifically need 'record locking' per se. I am 
just used to thinking in such terms because in Business Basic when I call 
up a record onscreen in modify mode for a user and dont want its contents 
changing behind their back, I "EXTRACT" the record. I dont like the idea 
of the entire (for example) debt-masterfile or client-masterfile locked
because one bozo went to lunch with one record onscreen in 
potentially-modifying mode, so the BASIC's approach of locking the record 
seemed a natural approach.

--
Mark Metson              How many mystics does it take to bring Peace on Earth?
gpurdy@fox.nstn.ns.ca    Only one - but each one has to do it for themself.....

==============================================================================
   To add/remove yourself to/from the POSTGRES mailing list: send mail with 
   the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU"

   If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
   a human will deal with it.  DO NOT post to the "postgres" mailing list.
==============================================================================