home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cimshop!davidm
- From: davidm@consilium.com (David S. Masterson)
- Newsgroups: comp.databases.theory
- Subject: Re: ordered collections
- Message-ID: <DAVIDM.92Sep10100820@consilium.com>
- Date: 10 Sep 92 17:08:20 GMT
- References: <cdk.715362552@neptune> <DAVIDM.92Sep2112813@consilium.com>
- <cdk.716057364@neptune>
- Sender: root@cimshop.UUCP
- Organization: Consilium Inc., Mountain View, California
- Lines: 26
- In-reply-to: cdk@neptune.dsc.com's message of 9 Sep 92 16:49:24 GMT
- X-Posting-Software: GNUS 3.13 [ NNTP-based News Reader for GNU Emacs ]
-
- >>>>> On 9 Sep 92 16:49:24 GMT, cdk@neptune.dsc.com (Colin Kelley) said:
-
- > davidm@consilium.com (David S. Masterson) writes:
-
- >>>>>>> On 1 Sep 92 15:49:12 GMT, cdk@neptune.dsc.com (Colin Kelley) said:
-
- >>> Is there a standard way to implement ordered collections in a relational
- >>> database that would allow for random insertion?
-
- >>Well, I don't think there is a standard, but here's one way.
-
- >>1. Make the primary key be (sequence_number, current_date).
- >>2. Generate a new sequence_number for additions to the end of the collection.
- >>3. Insertion anywhere else uses the sequence_number of preceding item.
-
- > I'm confused.
-
- You're right -- I realized later that this didn't make sense... :-(
- --
- ====================================================================
- David Masterson Consilium, Inc.
- (415) 691-6311 640 Clyde Ct.
- davidm@consilium.com Mtn. View, CA 94043
- ====================================================================
- "When the government attempts to regulate everything, all is lost."
- -- Thibaudeau
-