Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!rochester!pt.cs.cmu.edu!o.gp.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: 28 Sep 90 13:02:17 GMT References: <1990Aug8.230913.2897@agate.berkeley.edu> <26867@pasteur.Berkeley.EDU>, <12314@blia.BLI.COM> , <1990Sep27.191853.14153@inel.gov> Organization: Carnegie Mellon, Pittsburgh, PA Lines: 9 In-Reply-To: <1990Sep27.191853.14153@inel.gov> A number of people have pointed out the obvious - use some form of surrogate key to resolve the duplicate row problem. This is, obviously, exactly what I did. The real point of the original message was that the real world really does have to cope with duplicate items. Any model that does not permit the existance of duplicates has to be "fixed" to allow the handling of real cases. If it cannot be fixed/hacked/monkeyed with. this it should be discarded.