From: chester c young <chestercyoung@yahoo.com>
To: Paul Lambert <paul.lambert@autoledgers.com.au>
Cc: sql pgsql <pgsql-sql@postgresql.org>
Subject: Re: ignoring primary key violations in COPY command
Date: Sat, 19 May 2007 16:58:13 -0700 (PDT)
Message-ID: <567285.51917.qm@web54309.mail.yahoo.com> (raw)
In-Reply-To: <464F7A31.6020501@autoledgers.com.au>
> In my opinion your best bet in terms of getting around the primary
> key
> violation is to create a temporary table ...
good idea! from my experience it's almost always best to pull raw info
into a buffer table before introducing it into the real world.
____________________________________________________________________________________
Bored stiff? Loosen up...
Download and play hundreds of games for free on Yahoo! Games.
http://games.yahoo.com/games/front
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: chestercyoung@yahoo.com, paul.lambert@autoledgers.com.au
Subject: Re: ignoring primary key violations in COPY command
In-Reply-To: <567285.51917.qm@web54309.mail.yahoo.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