Date: 2010-11-19 11:23:17 +0100
From: Alexander Ulrich <>
To: SQL devs <>
Version: 2.40.1 (Oct2010) [obsolete]
CC: @njnes

Last updated: 2011-03-28 17:31:42 +0200

Comment 15211

Date: 2010-11-19 11:23:17 +0100
From: Alexander Ulrich <>

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_5; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
Build Identifier:

The following SQL query (which executes fine on e.g. Postgres) fails with an unknown column:

$ cat foo2.sql
SELECT t0.a
FROM (VALUES (1), (3)) AS t0(a),
(VALUES (1), (3)) AS t1(b)
WHERE a = b;
$ mclient -l sql -d test foo2.sql
SELECT: no such column 't0.a'

The same statement, slightly modified by removing the 't0.' part in the SELECT clause
results in an mserver5 process which consumes lots of CPU and is not finished after
5 minutes. The mclient process on the command line does not return.

u-080-c155:git-links ulricha$ cat foo1.sql
SELECT a
FROM (VALUES (1), (3)) AS t0(a),
(VALUES (1), (3)) AS t1(b)
WHERE a = b;
$ mclient -l sql -d test foo1.sql
[hanging, process does not finish in reasonable time]

Reproducible: Always

Steps to Reproduce:

1. MonetDB installed from the Oct2010 Super Source Tarball via the monetdb-install.sh script (http://dev.monetdb.org/downloads/sources/Oct2010/MonetDB-Oct2010-SuperBall.tar.bz2)
2. started merovingian as unpriviledged user
3. created and started database 'test' with one table
4. executed the above mentioned SQL fragments via mclient

Actual Results:

False error 'SELECT: no such column 't0.a'' or a non-terminating mclient/mserver5.

Expected Results:

Something like:

$ psql90 test < foo2.sql
a

1
3

Comment 15221

Date: 2010-11-24 18:59:30 +0100
From: @njnes

Changeset 6e3a607bc001 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=6e3a607bc001

Changeset description:

fixes for bug #2726 (join /union with single values)
Added test for bug #2726

Comment 15222

Date: 2010-11-24 19:06:40 +0100
From: @njnes

fixed, simple value projections are now processed earlier

Comment 15224

Date: 2010-11-24 20:00:07 +0100
From: @sjoerdmullender

There is actually a reason why we have "NEXTRELEASE". I use it when preparing a release.

Comment 15655

Date: 2011-03-28 17:31:42 +0200
From: @sjoerdmullender

The Mar2011 version has been released.