Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!pasteur!agate!violet.berkeley.edu!lindahl
From: lindahl@violet.berkeley.edu (Ken Lindahl   642-0866)
Newsgroups: comp.databases
Subject: Re: Ingres Question: Duplicate Rows
Message-ID: <1990Aug9.140025.1629@agate.berkeley.edu>
Date: 9 Aug 90 14:00:25 GMT
References: <1990Aug8.230913.2897@agate.berkeley.edu>
Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44)
Reply-To: lindahl@violet.berkeley.edu (Ken Lindahl   642-0866)
Organization: University of California, Berkeley
Lines: 26

In article <1990Aug8.230913.2897@agate.berkeley.edu> steve@violet.berkeley.edu (Steve Goldfield) writes:
>...
>The Ingres/Quel reference manual (we are using Release 5.0)
>says that duplicate rows are not allowed except in a heap
>structure. The table in question was a heap, but duplicates
>appear to have been suppressed anyway.

This is just a guess, but let's see if this is the same feature
that bit me. Are you doing a "retrieve ... sort by ..."? If so,
the result is stored as a cheapsort and duplicate rowd are removed
(cf. the "Retrieve" in INGRES/QUEL Reference Manual.

>Does anyone know whether the unwanted suppression of duplicate
>rows is a bug or a feature? 

If my guess is correct, it's a feature, since it's in the manual, right? :-)

>...
>Steve Goldfield
>College of Engineering
>UC Berkeley

Ken Lindahl				lindahl@violet.berkeley.edu
Advanced Technology Planning,
Information Systems and Technology
University of California at Berkeley