Consistent use of current_timestamp and now()

[monetdb-team]

Date: 2014-02-01 11:20:30 +0100
From: @mlkersten
To: SQL devs <>
Version: 11.15.7 (Feb2013-SP2)
CC: @njnes

Last updated: 2014-02-20 15:03:00 +0100

Comment 19514

Date: 2014-02-01 11:20:30 +0100
From: @mlkersten

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:26.0) Gecko/20100101 Firefox/26.0
Build Identifier:

Unexpected type error using now() and current_timestamp in table creation.
Enlarged test file has been added.

Reproducible: Always

Comment 19517

Date: 2014-02-01 15:07:43 +0100
From: MonetDB Mercurial Repository <>

Changeset 9fa129eaa0d9 made by Stefan Manegold Stefan.Manegold@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9fa129eaa0d9

Changeset description:

current_timestamp.Bug-3427: ensure deterministic test result
(otherwise, current output will always differ from (to be provided) stable output)

Comment 19518

Date: 2014-02-01 15:07:45 +0100
From: MonetDB Mercurial Repository <>

Changeset bdff2217856f made by Stefan Manegold Stefan.Manegold@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bdff2217856f

Changeset description:

current_timestamp.Bug-3427: completed test:

now() can be used for / assigned to both time & timestamp


current_timestamp can be used for / assigned to both time & timestamp

current_time can only be used for / assigned to time, but not to timestamp:
"ERROR = !types timetz(7,0) and timestamp(7,0) are not equal"

Comment 19519

Date: 2014-02-01 15:07:47 +0100
From: MonetDB Mercurial Repository <>

Changeset 394aed897576 made by Stefan Manegold Stefan.Manegold@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=394aed897576

Changeset description:

current_timestamp.Bug-3427: added expected stable output

Comment 19539

Date: 2014-02-05 11:12:14 +0100
From: @njnes

We correctly give an error when a time value is assigned to a timestamp.

Comment 19544

Date: 2014-02-05 13:00:17 +0100
From: MonetDB Mercurial Repository <>

Changeset be0051b026da made by Niels Nes niels@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=be0051b026da

Changeset description:

approved output for bug #3427 (also use auto commit mode)
fixed bug #3430, ie check if local temporary tables are stored in the 'tmp' schema
fixed bug #3428, don't overwrite the statement number, but use a temporary structure to store the
NotNil select statements. Solves the problem that the sum(a), sub(a*b) uses the a after nil
removal in the a*b.

fixed bug #3425, correctly add the timezone with the proper type (ie second interval (ie with scale 3))

Comment 19616

Date: 2014-02-20 15:03:00 +0100
From: @sjoerdmullender

Jan2014 has been released.