Date: 2018-10-08 14:19:57 +0200
From: @PedroTadim
To: SQL devs <>
Version: 11.31.7 (Aug2018)

Last updated: 2018-10-17 10:07:10 +0200

Comment 26632

Date: 2018-10-08 14:19:57 +0200
From: @PedroTadim

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

Performing a projection with a selection in a table that was updated previously in a transaction gives wrongs results.

Reproducible: Always

Steps to Reproduce:

1. CREATE TABLE updating (a INT);
2. INSERT INTO updating VALUES (1), (2);
3. START TRANSACTION;
4. UPDATE updating SET a = 3 WHERE a = 2;
5. SELECT a FROM updating WHERE a = 3;

Actual Results:

2

Expected Results:

3

If the table creation and the inserts are performed inside the transaction, the expected result is obtained. The same happens if only the updated value "2" was inserted beforehand.

Comment 26633

Date: 2018-10-08 14:22:41 +0200
From: MonetDB Mercurial Repository <>

Changeset 0c647922bc86 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=0c647922bc86

Changeset description:

Added test and output for bug #6649.

Comment 26634

Date: 2018-10-08 16:11:16 +0200
From: MonetDB Mercurial Repository <>

Changeset 633eafe2042a 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=633eafe2042a

Changeset description:

Fix a thinko in sql.projectdelta.
This fixes bug #6649.