thanks a lot!
On Mon, Dec 19, 2011 at 10:19 PM, Adrian Klaver adrian.kla...@gmail.comwrote:
On Sunday, December 18, 2011 10:54:21 pm Yan Chunlu wrote:
I am using COPY public.table_name FROM STDIN to import data. it is
very efficient, but if there's any duplicate key exists, the whole
On Sunday, December 18, 2011 10:54:21 pm Yan Chunlu wrote:
I am using COPY public.table_name FROM STDIN to import data. it is
very efficient, but if there's any duplicate key exists, the whole
procedure has been stopped. is there anyway to around this?
why does not postgresql just give a
I am using COPY public.table_name FROM STDIN to import data. it is
very efficient, but if there's any duplicate key exists, the whole
procedure has been stopped. is there anyway to around this?
why does not postgresql just give a warning and continue the copy?
--
Sent via pgsql-general
Copy to a staging table without the constraint and then write a query to
consolidate/remove the duplicate data and insert the clean data into the final
table.
It doesn't just give a warning because not importing a record from the source
data should be a fatal error since it means you have a
