On Tue, Mar 25, 2025 at 2:31 PM vignesh C <vignesh21@gmail.com> wrote:
>
> 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"
>
It took me a while to figure out why.
with the attached, now the error message becomes:
ERROR: null value in column "c1" of relation "t3" violates not-null constraint
DETAIL: Failing row contains (null, null).
CONTEXT: COPY t3, line 1: "a,b"
while at it,
(on_error set_to_null, log_verbosity verbose)
error message CONTEXT will only emit out relation name,
this aligns with (on_error ignore, log_verbosity verbose).
one of the message out example:
+NOTICE: column "b" was set to null due to data type incompatibility at line 2
+CONTEXT: COPY t_on_error_null
> 3) typo becomen should be become:
> null will becomen reserved to non-reserved
fixed.
> 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.
fixed.
