Re: Duplicates Processing

From: Gary Chambers <gwchamb(at)gmail(dot)com>
To: Rob Sargent <robjsargent(at)gmail(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Duplicates Processing
Date: 2010-10-08 22:12:39
Message-ID: AANLkTi=DiRzwbcrOx8-Y52=oM4GBmA7MEAOb1VvnZcU8@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

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

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Frank Bax 2010-10-08 23:09:56 Re: counting related rows
Previous Message James Cloos 2010-10-08 22:02:26 counting related rows