| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>, torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row |
| Date: | 2024-02-16 20:31:25 |
| Message-ID: | CAKFQuwaYNw8U-9JkFdyOX4i4Y3J1sp6+dk-sh8YmZGCq8gMeVQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 16, 2024 at 1:16 PM Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2024-02-16 20:31:47 | Re: System username in pg_stat_activity |
| Previous Message | John Morris | 2024-02-16 20:28:59 | Re: Where can I find the doxyfile? |