home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases.sybase
- Path: sparky!uunet!paladin.american.edu!darwin.sura.net!spool.mu.edu!sdd.hp.com!ux1.cso.uiuc.edu!news.iastate.edu!howard
- From: howard@cs.iastate.edu (Chris howard)
- Subject: Re: Sequencer or Serial
- Message-ID: <howard.716504676@judy.cs.iastate.edu>
- Sender: news@news.iastate.edu (USENET News System)
- Organization: Iowa State University, Ames IA
- References: <howard.716498215@judy.cs.iastate.edu> <14821@gazette.bcm.tmc.edu>
- Date: Mon, 14 Sep 1992 21:04:36 GMT
- Lines: 16
-
- mparsons@fleming.csc.bcm.tmc.edu (Mark Parsons) writes:
-
- >Why not set up one table, with one column of type int. Lock
- >the table when accessing/updating it. The idea is that this
- >column will hold a counter . . . just increment the column
- >each time you read the number . .
-
- >Mark
-
- Well, we thought of that, but we have been unable to determine how to
- get an exclusive lock on that column between the time that we read
- the counter, and the time it is updated.
-
- The best answer we've come up with is to use a trigger on Update to
- grab the value after incrementing it. It seems like a hack... at best.
-
-