Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 7D04E1337D56 for ; Fri, 8 Oct 2010 20:52:06 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 17154-05-6 for ; Fri, 8 Oct 2010 23:52:00 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from out02.mta.xmission.com (out02.mta.xmission.com [166.70.13.232]) by mail.postgresql.org (Postfix) with ESMTP id DF4981337D9F for ; Fri, 8 Oct 2010 20:48:00 -0300 (ADT) Received: from in02.mta.xmission.com ([166.70.13.52]) by out02.mta.xmission.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1P4MfQ-0001Wv-20; Fri, 08 Oct 2010 17:48:00 -0600 Received: from [208.187.158.94] (helo=[172.16.1.223]) by in02.mta.xmission.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1P4MfP-0005iJ-Ef; Fri, 08 Oct 2010 17:47:59 -0600 Message-ID: <4CAFADAD.7060600@gmail.com> Date: Fri, 08 Oct 2010 17:47:57 -0600 From: Rob Sargent User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.11) Gecko/20100714 SUSE/3.0.6 Lightning/1.0b1 Thunderbird/3.0.6 MIME-Version: 1.0 To: Gary Chambers CC: pgsql-sql@postgresql.org References: <4CAF79EB.1080606@gmail.com> <4CAF8E64.8010000@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-XM-SPF: eid=; ; ; mid=; ; ; hst=in02.mta.xmission.com; ; ; ip=208.187.158.94; ; ; frm=robjsargent@gmail.com; ; ; spf=neutral X-SA-Exim-Connect-IP: 208.187.158.94 X-SA-Exim-Mail-From: robjsargent@gmail.com X-Spam-DCC: XMission; sa06 1397; Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: ;Gary Chambers X-Spam-Relay-Country: Subject: Re: Duplicates Processing X-SA-Exim-Version: 4.2.1 (built Fri, 06 Aug 2010 16:31:04 -0600) X-SA-Exim-Scanned: Yes (on in02.mta.xmission.com) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201010/27 X-Sequence-Number: 34678 My understanding was that the values were in fact in the data of the "replacers". If not, you are correct. In this case the replacers are more like alias for the only instance you have. If the replacers are immutable by all means ship them off to some other table (where I suppose the become pointers to other suppliers of the type of thing holding the real data). Not sure I've ever met immutable data but there you go ;) And to your point of self-reference, it would be to a co-worker more than a manager. Managers are often not good replacements for workers. :) On 10/08/2010 04:12 PM, Gary Chambers wrote: > Rob, > >> Yes. With this you can find all part numbers/supplies which match your >> value, wattage criteria in one table. Or exclude any which have a >> non-null is_replacement_for value. > > I understand -- thanks. I have received contradictory advice in a > purely data modeling context. What about the null values that will be > in the properties columns of the part? It would appear to be more > applicable to an employee database where the columns are populated > regardless and the "replacement_for" in the context of our discussion > would be a self-reference to the employee's manager. No? > > Thanks again for your help. > > -- Gary Chambers