Re: Ignore when using COPY FROM

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Fredrick Bartlett <palmtreefrb(at)earthlink(dot)net>
Cc: Matthew Kennedy <mkennedy(at)hssinc(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Ignore when using COPY FROM
Date: 2000-10-16 16:10:33
Message-ID: 200010161610.MAA09176@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Added to TODO:

* Allow COPY to specify column names

> Yes, I have same problem. This functionality is "almost" standard,
> and
> found on other RDBMS. How do new features get added to the todo list's.
> Where can I view the current todo list?
>
> Fredrick
>
> Matthew Kennedy wrote:
>
> > I have a ton of data in a text delimited file from an old legacy system.
> > When uploading it into postgres, I'd do something like this:
> >
> > COPY stuff FROM 'stuff.txt' USING DELIMITERS = '|';
> >
> > The problem is some of the rows in stuff.txt may not conform to the
> > stuff table attributes (duplicate keys, for example). The command above
> > terminates with no change to the table stuff when it encounters an error
> > in stuff.txt. Is there a way to have postgres ignore erroneous fields
> > but keep information about which fields weren't processed. I believe
> > Oracle has some support for this through an IGNORE clause.
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jim Mercer 2000-10-16 16:12:36 Re: 7.1 Release Date
Previous Message Bruce Momjian 2000-10-16 16:00:59 Re: 7.1 Release Date