From: Gary Chambers <gwchamb@gmail.com>
To: Rob Sargent <robjsargent@gmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Duplicates Processing
Date: Fri, 8 Oct 2010 16:42:29 -0400
Message-ID: <AANLkTimRfzKH0DhyuMLpeU3g5GnCU6CuzYdxcph5HjqL@mail.gmail.com> (raw)
In-Reply-To: <4CAF79EB.1080606@gmail.com>
References: <AANLkTinSF+zqTVHbHp5HgN0TwHX-DjLAwQ4LhE7FYFxZ@mail.gmail.com>
<m3iq1cr0fi.fsf@passepartout.tim-landscheidt.de>
<AANLkTinr=cNsOeMGfOAjg5ncWhQ9p4RbpfyaoV1YN66T@mail.gmail.com>
<4CAF79EB.1080606@gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: gwchamb@gmail.com, robjsargent@gmail.com
Subject: Re: Duplicates Processing
In-Reply-To: <AANLkTimRfzKH0DhyuMLpeU3g5GnCU6CuzYdxcph5HjqL@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox