Re: Duplicates Processing - Mailing list pgsql-sql

From Gary Chambers
Subject Re: Duplicates Processing
Date
Msg-id AANLkTimRfzKH0DhyuMLpeU3g5GnCU6CuzYdxcph5HjqL@mail.gmail.com
Whole thread Raw
In response to Re: Duplicates Processing  (Rob Sargent <robjsargent@gmail.com>)
Responses Re: Duplicates Processing  (Rob Sargent <robjsargent@gmail.com>)
List pgsql-sql
Rob,

> Perhaps a trade off between nullable fields and redundant types.  If
> your original table simply had a nullable column called
> isReplacementFor, into which you place in the subsequent rows the id of
> the first instance found.

Am I misunderstanding you when you're suggesting a table like:

part_number           INTEGER
is_replacement_for INTEGER references part_number
value                       INTEGER
wattage                   FLOAT8
...

-- Gary Chambers


pgsql-sql by date:

Previous
From: Rob Sargent
Date:
Subject: Re: Duplicates Processing
Next
From: Rob Sargent
Date:
Subject: Re: Duplicates Processing