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
like produces error when you execute a query in a schema other than sys and the like operator is used in the select-list.
Reproducible: Always
Steps to Reproduce:
Start mserver5 ()
Start mclient
run SQL commands:
set schema sys;
SELECT cast(CASE WHEN "columns"."default" IS NOT NULL AND "columns"."default" LIKE 'next value for %' THEN 'YES' ELSE 'NO' END AS varchar(3)) AS "IS_AUTOINCREMENT"
FROM "sys"."columns"
WHERE "columns"."default" LIKE 'next value for %';
set schema tmp;
SELECT cast(CASE WHEN "columns"."default" IS NOT NULL AND "columns"."default" LIKE 'next value for %' THEN 'YES' ELSE 'NO' END AS varchar(3)) AS "IS_AUTOINCREMENT"
FROM "sys"."columns"
WHERE "columns"."default" LIKE 'next value for %';
set schema profiler;
SELECT cast(CASE WHEN "columns"."default" IS NOT NULL AND "columns"."default" LIKE 'next value for %' THEN 'YES' ELSE 'NO' END AS varchar(3)) AS "IS_AUTOINCREMENT"
FROM "sys"."columns"
WHERE "columns"."default" LIKE 'next value for %';
Actual Results:
sql>set schema sys;
auto commit mode: on
sql>
sql>SELECT cast(CASE WHEN "columns"."default" IS NOT NULL AND "columns"."default" LIKE 'next value for %' THEN 'YES' ELSE 'NO' END AS varchar(3)) AS "IS_AUTOINCREMENT"
more>FROM "sys"."columns"
more>WHERE "columns"."default" LIKE 'next value for %';
+------------------+
| IS_AUTOINCREMENT |
+==================+
+------------------+
0 tuples (2.503ms)
sql>
sql>set schema tmp;
auto commit mode: on
sql>
sql>SELECT cast(CASE WHEN "columns"."default" IS NOT NULL AND "columns"."default" LIKE 'next value for %' THEN 'YES' ELSE 'NO' END AS varchar(3)) AS "IS_AUTOINCREMENT"
more>FROM "sys"."columns"
more>WHERE "columns"."default" LIKE 'next value for %';
SELECT: no such binary operator 'like(varchar,varchar)'
sql>
sql>set schema profiler;
auto commit mode: on
sql>
sql>SELECT cast(CASE WHEN "columns"."default" IS NOT NULL AND "columns"."default" LIKE 'next value for %' THEN 'YES' ELSE 'NO' END AS varchar(3)) AS "IS_AUTOINCREMENT"
more>FROM "sys"."columns"
more>WHERE "columns"."default" LIKE 'next value for %';
SELECT: no such binary operator 'like(varchar,varchar)'
sql>
Expected Results:
sql>set schema sys;
auto commit mode: on
sql>
sql>SELECT cast(CASE WHEN "columns"."default" IS NOT NULL AND "columns"."default" LIKE 'next value for %' THEN 'YES' ELSE 'NO' END AS varchar(3)) AS "IS_AUTOINCREMENT"
more>FROM "sys"."columns"
more>WHERE "columns"."default" LIKE 'next value for %';
+------------------+
| IS_AUTOINCREMENT |
+==================+
+------------------+
0 tuples (2.503ms)
sql>
sql>set schema tmp;
auto commit mode: on
sql>
sql>SELECT cast(CASE WHEN "columns"."default" IS NOT NULL AND "columns"."default" LIKE 'next value for %' THEN 'YES' ELSE 'NO' END AS varchar(3)) AS "IS_AUTOINCREMENT"
more>FROM "sys"."columns"
more>WHERE "columns"."default" LIKE 'next value for %';
+------------------+
| IS_AUTOINCREMENT |
+==================+
+------------------+
0 tuples (2.503ms)
sql>
sql>set schema profiler;
auto commit mode: on
sql>
sql>SELECT cast(CASE WHEN "columns"."default" IS NOT NULL AND "columns"."default" LIKE 'next value for %' THEN 'YES' ELSE 'NO' END AS varchar(3)) AS "IS_AUTOINCREMENT"
more>FROM "sys"."columns"
more>WHERE "columns"."default" LIKE 'next value for %';
+------------------+
| IS_AUTOINCREMENT |
+==================+
+------------------+
0 tuples (2.503ms)
sql>
The issue is introduced recently in default branch. 3 weeks ago (and in Jun2016 release) this SQL syntax worked.
This query scenario is used in in MonetDB JDBC driver getColumns() implementation, so it is important this is fixed asap.
Date: 2016-09-01 15:13:51 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <>
Version: -- development
CC: @njnes
Last updated: 2016-10-13 11:43:22 +0200
Comment 22344
Date: 2016-09-01 15:13:51 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0
Build Identifier:
like produces error when you execute a query in a schema other than sys and the like operator is used in the select-list.
Reproducible: Always
Steps to Reproduce:
set schema sys;
SELECT cast(CASE WHEN "columns"."default" IS NOT NULL AND "columns"."default" LIKE 'next value for %' THEN 'YES' ELSE 'NO' END AS varchar(3)) AS "IS_AUTOINCREMENT"
FROM "sys"."columns"
WHERE "columns"."default" LIKE 'next value for %';
set schema tmp;
SELECT cast(CASE WHEN "columns"."default" IS NOT NULL AND "columns"."default" LIKE 'next value for %' THEN 'YES' ELSE 'NO' END AS varchar(3)) AS "IS_AUTOINCREMENT"
FROM "sys"."columns"
WHERE "columns"."default" LIKE 'next value for %';
set schema profiler;
SELECT cast(CASE WHEN "columns"."default" IS NOT NULL AND "columns"."default" LIKE 'next value for %' THEN 'YES' ELSE 'NO' END AS varchar(3)) AS "IS_AUTOINCREMENT"
FROM "sys"."columns"
WHERE "columns"."default" LIKE 'next value for %';
Actual Results:
sql>set schema sys;
auto commit mode: on
sql>
sql>SELECT cast(CASE WHEN "columns"."default" IS NOT NULL AND "columns"."default" LIKE 'next value for %' THEN 'YES' ELSE 'NO' END AS varchar(3)) AS "IS_AUTOINCREMENT"
more>FROM "sys"."columns"
more>WHERE "columns"."default" LIKE 'next value for %';
+------------------+
| IS_AUTOINCREMENT |
+==================+
+------------------+
0 tuples (2.503ms)
sql>
sql>set schema tmp;
auto commit mode: on
sql>
sql>SELECT cast(CASE WHEN "columns"."default" IS NOT NULL AND "columns"."default" LIKE 'next value for %' THEN 'YES' ELSE 'NO' END AS varchar(3)) AS "IS_AUTOINCREMENT"
more>FROM "sys"."columns"
more>WHERE "columns"."default" LIKE 'next value for %';
SELECT: no such binary operator 'like(varchar,varchar)'
sql>
sql>set schema profiler;
auto commit mode: on
sql>
sql>SELECT cast(CASE WHEN "columns"."default" IS NOT NULL AND "columns"."default" LIKE 'next value for %' THEN 'YES' ELSE 'NO' END AS varchar(3)) AS "IS_AUTOINCREMENT"
more>FROM "sys"."columns"
more>WHERE "columns"."default" LIKE 'next value for %';
SELECT: no such binary operator 'like(varchar,varchar)'
sql>
Expected Results:
sql>set schema sys;
auto commit mode: on
sql>
sql>SELECT cast(CASE WHEN "columns"."default" IS NOT NULL AND "columns"."default" LIKE 'next value for %' THEN 'YES' ELSE 'NO' END AS varchar(3)) AS "IS_AUTOINCREMENT"
more>FROM "sys"."columns"
more>WHERE "columns"."default" LIKE 'next value for %';
+------------------+
| IS_AUTOINCREMENT |
+==================+
+------------------+
0 tuples (2.503ms)
sql>
sql>set schema tmp;
auto commit mode: on
sql>
sql>SELECT cast(CASE WHEN "columns"."default" IS NOT NULL AND "columns"."default" LIKE 'next value for %' THEN 'YES' ELSE 'NO' END AS varchar(3)) AS "IS_AUTOINCREMENT"
more>FROM "sys"."columns"
more>WHERE "columns"."default" LIKE 'next value for %';
+------------------+
| IS_AUTOINCREMENT |
+==================+
+------------------+
0 tuples (2.503ms)
sql>
sql>set schema profiler;
auto commit mode: on
sql>
sql>SELECT cast(CASE WHEN "columns"."default" IS NOT NULL AND "columns"."default" LIKE 'next value for %' THEN 'YES' ELSE 'NO' END AS varchar(3)) AS "IS_AUTOINCREMENT"
more>FROM "sys"."columns"
more>WHERE "columns"."default" LIKE 'next value for %';
+------------------+
| IS_AUTOINCREMENT |
+==================+
+------------------+
0 tuples (2.503ms)
sql>
The issue is introduced recently in default branch. 3 weeks ago (and in Jun2016 release) this SQL syntax worked.
This query scenario is used in in MonetDB JDBC driver getColumns() implementation, so it is important this is fixed asap.
Comment 22345
Date: 2016-09-01 15:20:48 +0200
From: MonetDB Mercurial Repository <>
Changeset 5e2066630c3f made by Martin van Dinther martin.van.dinther@monetdbsolutions.com in the MonetDB repo, refers to this bug.
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=5e2066630c3f
Changeset description:
Comment 22353
Date: 2016-09-04 17:14:54 +0200
From: @njnes
fixed, we now use the proper sys schema when we lookup the (i)like functions
Comment 24502
Date: 2016-10-13 10:04:48 +0200
From: @sjoerdmullender
Jun2016-SP2 has been released.
The text was updated successfully, but these errors were encountered: