On 16.02.24 21:31, David G. Johnston wrote: > 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. Yeah, you have a point there. I guess if users want to avoid it to happen they can rely on NOT NULL constraints. Thanks -- Jim
- Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_r... Jim Jones
- Re: Change COPY ... ON_ERROR ignore to ON_ERROR ign... David G. Johnston
- Re: Change COPY ... ON_ERROR ignore to ON_ERROR... Jim Jones