Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row
От | vignesh C |
---|---|
Тема | Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row |
Дата | |
Msg-id | CALDaNm0FUtPjH9wz5dgwOBNtsAXEZj=0-TYGsyQXchQy-hXGrw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row (jian he <jian.universality@gmail.com>) |
Ответы |
Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row
|
Список | pgsql-hackers |
On Mon, 24 Mar 2025 at 13:21, jian he <jian.universality@gmail.com> wrote: > > I am not sure this is what we want. > Anyway, I attached both two version Few comments 1) I understood the problem, your first approach is ok for me. 2) Here in error we say column c1 violates not-null constraint and in the context we show column c2, should the context also display c2 column: postgres=# create table t3(c1 int not null, c2 int, check (c1 > 10)); CREATE TABLE postgres=# COPY t3 FROM STDIN WITH (on_error set_to_null); Enter data to be copied followed by a newline. End with a backslash and a period on a line by itself, or an EOF signal. >> a b >> \. ERROR: null value in column "c1" of relation "t3" violates not-null constraint DETAIL: Failing row contains (null, null). CONTEXT: COPY t3, line 1, column c2: "b" 3) typo becomen should be become: null will becomen reserved to non-reserved 4) There is a whitespace error while applying patch Applying: COPY (on_error set_to_null) .git/rebase-apply/patch:39: trailing whitespace. a <literal>NOTICE</literal> message indicating the number of rows warning: 1 line adds whitespace errors. Regards, Vignesh
В списке pgsql-hackers по дате отправления: