From: | Michael Glaesemann <grzm(at)myrealbox(dot)com> |
---|---|
To: | "Joolz" <joolz(at)arbodienst-limburg(dot)nl> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: error-tolerant COPY FROM |
Date: | 2005-02-04 13:00:11 |
Message-ID: | e5b820162eb17faf47ceb08b23294ea4@myrealbox.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Feb 4, 2005, at 21:32, Joolz wrote:
> What I need is an import where all valid lines from the csv files
> are read into the db, and I also get a logfile for all invalid
> lines, stating the line number plus the pg error message so I can
> see which constraint was violated.
>
> I can't think of a direct, elegant solution for this, does anyone
> have any suggestions? Thanks a lot!
I don't know if it's elegant or not, but my approach to this situation
is to read the data into a temp table that does not have as strict
constraints. Once the data is in the database, I process it further,
moving the data that's valid into the appropriate table. Then I see
what's left, and what further processing I need to do to "fix" the
invalid data. Perhaps a similar strategy would work for you.
Michael Glaesemann
grzm myrealbox com
From | Date | Subject | |
---|---|---|---|
Next Message | Joolz | 2005-02-04 13:06:19 | Re: error-tolerant COPY FROM |
Previous Message | Joolz | 2005-02-04 12:56:23 | Re: error-tolerant COPY FROM |