Date: 2018-07-25 11:16:36 +0200
From: @PedroTadim
To: SQL devs <>
Version: -- development
CC: @njnes

Last updated: 2018-08-31 13:23:15 +0200

Comment 26569

Date: 2018-07-25 11:16:36 +0200
From: @PedroTadim

User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36
Build Identifier:

The query bellow returns the number used by mserver5 to represent a NULL value instead of the NULL value itself.

Reproducible: Always

Steps to Reproduce:

1. SELECT 0 + CAST ( NULL AS INTEGER ) + 0;

Actual Results:

-9223372036854775808 (Mserver5 compiled with hugeint)

Expected Results:

A single NULL value.

In the test I'm about to commit I added more examples.

Comment 26570

Date: 2018-07-25 11:20:17 +0200
From: MonetDB Mercurial Repository <>

Changeset d050192b5c60 made by Pedro Ferreira pedro.ferreira@monetdbsolutions.com in the MonetDB repo, refers to this bug.

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

Changeset description:

Added test for bug #6630.

Comment 26571

Date: 2018-07-25 16:46:05 +0200
From: MonetDB Mercurial Repository <>

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

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

Changeset description:

fixes for bug #6630, ie handle null in atom_* (add,sub,mul) code

Comment 26572

Date: 2018-07-25 17:57:37 +0200
From: @njnes

fixed by handling null's in atom_add etc