Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!cornell!uw-beaver!ssc-vax!voodoo!bcsfse!paul
From: paul@bcsfse.UUCP (Paul Hardiman)
Newsgroups: comp.databases
Subject: Locks on Online Transaction DBMS
Message-ID: <268@bcsfse.UUCP>
Date: 1 Nov 88 17:10:42 GMT
Reply-To: paul@bcsfse.UUCP (Paul Hardiman)
Organization: bcs
Lines: 18

I need some expertise on a locking issue.

My project is investigating moving from a database
connection environment to one that is transaction oriented.
The issue has to do with locks on rows.  It is a relatively
simple matter to hold a lock for the duration of a connection
session, but the picture changes in a transaction environment.
So, how do transaction systems preserve locks on one transaction
and release it on a later transaction from the same user.

We have considered the possibility of using conceptual locks by tagging
a field on a row with something unique like the user's id.  However,
at first glimpse, this method seems to detract from the eloquence of
the system.

	Thank you for any assistance.
-- 
                             Paul Hardiman
                ...!uw-beaver!ssc-vax!voodoo!bcsfse!paul