You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Date: 2014-04-08 16:22:25 +0200
From: Edward Clarkson <<edward.clarkson>>
To: clients devs <>
Version: 11.17.13 (Jan2014-SP1)
CC: @njnes
Last updated: 2015-01-29 14:07:32 +0100
Comment 19733
Date: 2014-04-08 16:22:25 +0200
From: Edward Clarkson <<edward.clarkson>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.75.14 (KHTML, like Gecko) Version/7.0.3 Safari/537.75.14
Build Identifier:
See the following query sequence:
sql>CREATE TABLE test (a int);
operation successful (5.230ms)
sql>SELECT a AS "" FROM test;
+--+
| |
+==+
+--+
0 tuples (3.320ms)
In contrast:
sql>SELECT a AS "@" FROM test;
+---+
| @ |
+===+
+---+
0 tuples (1.672ms)
This is the simplest replication: this is more severe/inconvenient when selecting multiple columns: ALL fields after one with a '' are then blanked). So even if I'm missing something w/r/t escaping ''--which then should be documented somewhere--it's still not right to blank other field names.
Note that all the results are fine, it's just the field names that are bad--which causes a lot of problems in client code that grabs result set data by field name rather than position.
The '' is part of the mapi protocol. This means we should disallow this within names or somehow escape it. Tested with python also gives a similar problem.
Date: 2014-04-08 16:22:25 +0200
From: Edward Clarkson <<edward.clarkson>>
To: clients devs <>
Version: 11.17.13 (Jan2014-SP1)
CC: @njnes
Last updated: 2015-01-29 14:07:32 +0100
Comment 19733
Date: 2014-04-08 16:22:25 +0200
From: Edward Clarkson <<edward.clarkson>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.75.14 (KHTML, like Gecko) Version/7.0.3 Safari/537.75.14
Build Identifier:
See the following query sequence:
sql>CREATE TABLE test (a int);
operation successful (5.230ms)
sql>SELECT a AS "" FROM test;
+--+
| |
+==+
+--+
0 tuples (3.320ms)
In contrast:
sql>SELECT a AS "@" FROM test;
+---+
| @ |
+===+
+---+
0 tuples (1.672ms)
This is the simplest replication: this is more severe/inconvenient when selecting multiple columns: ALL fields after one with a '' are then blanked). So even if I'm missing something w/r/t escaping ''--which then should be documented somewhere--it's still not right to blank other field names.
Note that all the results are fine, it's just the field names that are bad--which causes a lot of problems in client code that grabs result set data by field name rather than position.
Reproducible: Always
Steps to Reproduce:
Actual Results:
An empty result set with an empty field name.
Expected Results:
An empty result set with a field named "".
Comment 19738
Date: 2014-04-09 13:18:12 +0200
From: @njnes
The '' is part of the mapi protocol. This means we should disallow this within names or somehow escape it. Tested with python also gives a similar problem.
Comment 20555
Date: 2015-01-14 14:39:51 +0100
From: MonetDB Mercurial Repository <>
Changeset 6e51939fcef0 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=6e51939fcef0
Changeset description:
Comment 20599
Date: 2015-01-29 14:07:32 +0100
From: @sjoerdmullender
Oct2014-SP2 has been released.
The text was updated successfully, but these errors were encountered: