Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!rice!uw-beaver!zephyr.ens.tek.com!tektronix!sequent!jsc
From: jsc@sequent.UUCP (J. Scott Carr)
Newsgroups: comp.databases
Subject: Re: Unique code numbers
Message-ID: <27884@sequent.UUCP>
Date: 17 Jan 90 01:29:54 GMT
References: <1990Jan16.081519.279@cs.eur.nl>
Reply-To: jsc@crg4.UUCP (J. Scott Carr)
Organization: Sequent Computer Systems, Inc
Lines: 18

In article <1990Jan16.081519.279@cs.eur.nl> reino@cs.eur.nl (Reino de Boer) writes:
>I was wondering if there is a relational DBMS that gives me the
>opportunity to indicate that:
>1. SupplierIDs need to be unique
>2. PartIDs need to be unique
>and, most important of all
>3. Frees me from the burden to make up new SupplierIDs and PartIDs.

ORACLE Version 6.0 introduces a database object called a Sequence, which
is used to generate unique identifiers.  When inserting a new row,
you select sequence.next, which provides the next unique ID.  The object
allow specification of starting value, increment, and whether the 
sequence should cycle.  All in all a good extension.


--------
Scott Carr   				 uunet!sequent!jsc
Sequent Computer Systems		 (503) 526-5940