| From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Importing/Appending to Existing Table |
| Date: | 2011-02-02 14:29:54 |
| Message-ID: | alpine.LNX.2.00.1102020626300.4447@salmo.appl-ecosys.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 2 Feb 2011, Greg Williamson wrote:
> It will not overwrite any existing data; if the table has constraints that
> will prevent duplicates then the entire load will fail if any item fails
> (it is a single transaction).
>
> If the table doesn't have such constraints then duplicate data in the copy file
> will result in duplicate rows.
Greg,
These data originate in highly undisciplined Excel spreadsheets over the
past 10+ years. They need a lot of preprossing in emacs and python scripts
I've written but there are no primary keys or other constraints until all
the data are entered then moved to the actual application tables. I will not
be surprised to discover duplicate data because of data-entry errors, but
there should not be any duplicates in these permit compliance monitoring
results.
Thanks,
Rich
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wim Bertels | 2011-02-02 14:41:03 | redirecting query statement and output to a marked up file, using psql |
| Previous Message | Rich Shepard | 2011-02-02 14:26:10 | Re: Importing/Appending to Existing Table |