MIME-Version: 1.0
References: <CAKFQuwawy1e6YR4S=j+y7pXqg_Dw1WBVrgvf=BP3d1_aSfe_+Q@mail.gmail.com>
 <20240129172858.ccb6c77c3be95a295e2b2b44@sraoss.co.jp> <CACJufxFFU92-H7G8tmpxt9oTSfL062OA7n5rPx-YbOAtDUUzGw@mail.gmail.com>
 <04bf425ad1b15a4daefe96c478a5253b@oss.nttdata.com> <CACJufxGnc+=No=Ua6NFT2ADt0vRL=m1QsuCOM=9aKPKWh9_L6Q@mail.gmail.com>
 <20240206191937.72eaf0ccc20cfea37944b422@sraoss.co.jp> <CACJufxFT9j8o5kEC8dPCQqLomWjeJm9V9m8eZjj2Gvc_F5ha=g@mail.gmail.com>
 <76da9fcc-93c5-4053-872e-12932a95356d@uni-muenster.de>
In-Reply-To: <76da9fcc-93c5-4053-872e-12932a95356d@uni-muenster.de>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Fri, 16 Feb 2024 13:31:25 -0700
Message-ID: <CAKFQuwaYNw8U-9JkFdyOX4i4Y3J1sp6+dk-sh8YmZGCq8gMeVQ@mail.gmail.com>
Subject: Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row
To: Jim Jones <jim.jones@uni-muenster.de>
Cc: jian he <jian.universality@gmail.com>, Yugo NAGATA <nagata@sraoss.co.jp>, 
	torikoshia <torikoshia@oss.nttdata.com>, 
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000fabba7061185a237"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwaYNw8U-9JkFdyOX4i4Y3J1sp6%2Bdk-sh8YmZGCq8gMeVQ%40mail.gmail.com>
Precedence: bulk

--000000000000fabba7061185a237
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 16, 2024 at 1:16=E2=80=AFPM Jim Jones <jim.jones@uni-muenster.d=
e> wrote:

> In case all columns of a record have been set to null due to data type
> incompatibility, should we insert it at all?


Yes.  In particular not all columns in the table need be specified in the
copy command so while the parsed input data is all nulls the record itself
may not be.

The system should allow the user to exclude rows with incomplete data by
ignoring a not null constraint violation.

In short we shouldn't judge non-usefulness and instead give tools to the
user to decide for themselves.

David J.

--000000000000fabba7061185a237
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif"><span style=3D"font-family:Arial,Helve=
tica,sans-serif">On Fri, Feb 16, 2024 at 1:16=E2=80=AFPM Jim Jones &lt;<a h=
ref=3D"mailto:jim.jones@uni-muenster.de">jim.jones@uni-muenster.de</a>&gt; =
wrote:</span><br></div></div><div class=3D"gmail_quote"><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">In case all columns of a record have been =
set to null due to data type<br>
incompatibility, should we insert it at all?</blockquote><div><br></div><di=
v><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-se=
rif">Yes.=C2=A0 In particular not all columns in the table need be specifie=
d in the copy command so while the parsed input data is all nulls the recor=
d itself may not be.</div><div class=3D"gmail_default" style=3D"font-family=
:arial,helvetica,sans-serif"><br></div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif">The system should allow the use=
r to exclude rows with incomplete data by ignoring a not null constraint vi=
olation.</div></div><div class=3D"gmail_default" style=3D"font-family:arial=
,helvetica,sans-serif"><br></div><div class=3D"gmail_default" style=3D"font=
-family:arial,helvetica,sans-serif">In short we shouldn&#39;t judge non-use=
fulness and instead give tools to the user to decide for themselves.</div><=
div><br></div><div><div class=3D"gmail_default" style=3D"font-family:arial,=
helvetica,sans-serif">David J.</div><br></div></div></div>

--000000000000fabba7061185a237--