Path: dp-news.maxwell.syr.edu!spool.maxwell.syr.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!news.astraweb.com!newsrouter-eu.astraweb.com!hwmnpeer01.ams!hwmedia!news.highwinds-media.com!hq-usenetpeers.eweka.nl!212.159.2.67.MISMATCH!nntp-peering.plus.net!ptn-nntp-feeder03.plus.net!ptn-nntp-spool01.plus.net!ptn-nntp-reader03.plus.net!not-for-mail
Date: Fri, 03 Mar 2006 11:31:37 +0000
From: bugbear <bugbear@trim_papermule.co.uk_trim>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.7.12-1.3.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: comp.databases.oracle.server
Subject: Re: slightly OT - cleaning up "dirty" keys?
References: <4405a556$0$3558$ed2619ec@ptn-nntp-reader03.plus.net> <1141337909.206964.158370@t39g2000cwt.googlegroups.com>
In-Reply-To: <1141337909.206964.158370@t39g2000cwt.googlegroups.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 21
Message-ID: <4408291a$0$70321$ed2619ec@ptn-nntp-reader03.plus.net>
Organization: Customer of PlusNet plc (http://www.plus.net)
NNTP-Posting-Host: 18e83e08.ptn-nntp-reader03.plus.net
X-Trace: DXC=0D[6CeABSQQ=P]4P:ER:]Uigd3Y`7Rb;^@`8gV4CC7IWfeJ;AX9aGU\LWV4BSm9hiPMcHWBhHIbdP^`];2kc`PF[
X-Complaints-To: abuse@plus.net
Xref: dp-news.maxwell.syr.edu comp.databases.oracle.server:262681

Joel Garry wrote:
> Is there any other information that might give a clue, ie, address?
> group by address having count(*) > 1
> 
> Then all you have to worry about is wrong addresses :-)

Heh. That's the problem.

Different operators are FAILING to locate
the original record, and are entering a new one.
The address fields are just as "dirty" as
th so-called (name) primary key.

All the data is a freakin' dirty mess.

I was hoping to cluster "likely"
primary-keys, so a human
could merge them, and also merge/fix the associated
non-primary data.

   BugBear