Date: 2018-02-04 18:46:54 +0100
From: @sjoerdmullender
To: SQL devs <>
Version: 11.27.11 (Jul2017-SP3)

Last updated: 2018-03-29 15:39:23 +0200

Comment 26161

Date: 2018-02-04 18:46:54 +0100
From: @sjoerdmullender

Comment 26162

Date: 2018-02-04 18:53:10 +0100
From: @sjoerdmullender

The following creates a table and insert one row where the first column is filled in using the default value (a sequence) and the other columns come from a file. When doing this, the NULL AS blurb gets ignored.

create table t (id int auto_increment, a clob, b clob);
copy 1 records into t (a, b) from stdin (id, a, b) using delimiters ',','\n','"' null as '';
2,,

select * from t;
this now results in a row with values id=1, a='', b='' instead of id=1,a=NULL,b=NULL.

Comment 26163

Date: 2018-02-04 18:54:37 +0100
From: @sjoerdmullender

The first column must be in the file, but it must be ignored by the COPY IN.

Comment 26164

Date: 2018-02-04 22:36:20 +0100
From: MonetDB Mercurial Repository <>

Changeset e2fda4b58c9f made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.

For complete details, see https//devmonetdborg/hg/MonetDB?cmd=changeset;node=e2fda4b58c9f

Changeset description:

Don't skip checking for nullstr when skipping first column.
This fixes bug #6532.

Comment 26323

Date: 2018-03-29 15:39:23 +0200
From: @sjoerdmullender

The Mar2018 version has been released.