Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!pt.cs.cmu.edu!andrew.cmu.edu!bg0l+ From: bg0l+@andrew.cmu.edu (Bruce E. Golightly) Newsgroups: comp.databases Subject: Re: Ingres Question: Duplicate Rows Message-ID: Date: 9 Aug 90 13:15:42 GMT References: <1990Aug8.230913.2897@agate.berkeley.edu> Organization: Carnegie Mellon, Pittsburgh, PA Lines: 15 In-Reply-To: <1990Aug8.230913.2897@agate.berkeley.edu> Sounds like the report used a sort. This is a "feature" of sorting that turns up in all sorts of irritating places, not only Ingres. One work-around is to retrieve something that is sure to be unique, like the tuple ID, and simply not write it in the report. ############################################################################# ! Bruce E. Golightly ! bg0l@andrew.cmu.edu (BeeGeeZeroEl) Chief of Data Base Development ! (412)268-8560 Telecommunications Group ! Carnegie Mellon University ! UCC 117, 4910 Forbes Ave. ! Pittsburgh PA 15213-3890 President, Western Penna IUA ! #############################################################################