Hi!
On 12.02.24 01:00, jian he wrote:
> attached v2.
> syntax: `on_error set_to_null`
> based on upthread discussion, now if you specified `on_error
> set_to_null` and your column has `not
> null` constraint, we convert the error field to null, so it may error
> while bulk inserting for violating NOT NULL constraint.
That's a very nice feature. Thanks for implementing it!
v2 applies cleanly and works as described.
\pset null '(NULL)'
CREATE TEMPORARY TABLE t1 (a int, b int);
COPY t1 (a,b) FROM STDIN;
1 a
2 1
3 2
4 b
a c
\.
SELECT * FROM t1;
CONTEXT: COPY t1, line 1, column b: "a"
a | b
---+---
(0 rows)
CREATE TEMPORARY TABLE t2 (a int, b int);
COPY t2 (a,b) FROM STDIN WITH (on_error set_to_null);
1 a
2 1
3 2
4 b
a c
\.
SELECT * FROM t2;
psql:test-copy-on_error-2.sql:12: NOTICE: some columns of 3 rows, value
were converted to NULL due to data type incompatibility
COPY 5
a | b
--------+--------
1 | (NULL)
2 | 1
3 | 2
4 | (NULL)
(NULL) | (NULL)
(5 rows)
I have one question though:
In case all columns of a record have been set to null due to data type
incompatibility, should we insert it at all? See t2 example above.
I'm not sure if these records would be of any use in the table. What do
you think?
Since the parameter is already called "set_to_null", maybe it is not
necessary to mention in the NOTICE message that the values have been set
to null.
Perhaps something like "XX records were only partially copied due to
data type incompatibility"
--
Jim
