From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Recommended Protocol: Adding Rows to Table |
Date: | 2011-11-25 16:49:40 |
Message-ID: | alpine.LNX.2.00.1111250845560.321@salmo.appl-ecosys.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 25 Nov 2011, David Johnston wrote:
> Simplistically you load all the data into a staging table that has no
> natural primary key and then write a query that will result in only a
> single record for whatever you define as a primary key. Insert the
> results of that query into the final table.
David,
I was leaning toward doing this.
> If you only use a subset of columns to uniquely determine the PK than you
> need to decide how to resolve situations where the PK fields are
> duplicated but the extra fields are unique. That step is why the first
> description is simplistic.
Well, that's point of a PK, isn't it? There should be only one row with
that specific set of column values. The additional columns are unique to
that set of PK values.
Thanks,
Rich
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2011-11-25 19:17:15 | Re: Recommended Protocol: Adding Rows to Table |
Previous Message | Tom Lane | 2011-11-25 16:36:10 | Re: error when defining a search configuration named "default" |