Date: 2017-01-27 11:23:33 +0100
From: @sjoerdmullender
To: SQL devs <>
Version: 11.25.5 (Dec2016-SP1)

Last updated: 2017-03-03 10:24:57 +0100

Comment 24921

Date: 2017-01-27 11:23:33 +0100
From: @sjoerdmullender

Even though we're allowed to truncate or round at our discretion, it would be good if we were consistent.

There are also some bugs where rounding is implemented incorrectly.

See allso (closed) bugs 3744, 3310.

Comment 24922

Date: 2017-01-27 11:39:20 +0100
From: MonetDB Mercurial Repository <>

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

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

Changeset description:

Be consistent about rounding or truncating values.

There is now a symbol TRUNCATE_NUMBERS that, if defined, which it
currently is not, will cause the code to always truncate towards zero
when values need to be converted from higher precision (number of
decimals after the decimal point) to lower precision, including from
floating point to integer.  Without the symbol, we always round.
This checkin also fixes some rounding bugs (don't add 0.5 to a
negative number and then truncate toward zero).

This fixes bug #6193.

Also added test.

Comment 24923

Date: 2017-01-27 11:41:04 +0100
From: @sjoerdmullender

This bug was fixed.
Since changeset 412cc3428d91 (which will be in the Dec2016-SP2 release), we round consistently, but there is a compile-time option to always truncate.

Comment 25132

Date: 2017-03-03 10:24:57 +0100
From: @sjoerdmullender

Dec2016-SP2 has been released, incorporating the fix.