issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.46B | issue_number int64 1 127k |
|---|---|---|---|---|---|---|---|---|---|
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-27 17:39:26 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.23.13 (Jun2016-SP2)
CC: @njnes
Last updated: 2017-05-01 13:32:45 +0200
## Comment 24638
Date: 2016-10-27 17:39:26 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0
Build Identifier:
boolean values true and false are not converted to strings: "true" and "false" when casting or converting to string, clob, char or varchar.
Reproducible: Always
### Steps to Reproduce:
1. Start mserver5
2. Start mclient
3. Execute SQL commands:
CREATE TABLE t_boolean (val BOOLEAN, valstr VARCHAR(5));
INSERT INTO t_boolean VALUES (true, 'True');
INSERT INTO t_boolean VALUES (false, 'False');
INSERT INTO t_boolean VALUES (Null, 'Null');
SELECT val, valstr, cast(val as bool) as cast2bool FROM t_boolean order by val;
SELECT val, valstr, cast(valstr as bool) as caststr2bool FROM t_boolean where val is not null order by val;
-- the next conversions to char strings are wrong
SELECT val, valstr, cast(val as string) as cast2str FROM t_boolean order by val;
SELECT val, valstr, cast(val as char(5)) as cast2char5 FROM t_boolean order by val;
SELECT val, valstr, cast(val as varchar(5)) as cast2varchar5 FROM t_boolean order by val;
SELECT val, valstr, cast(val as clob) as cast2clob FROM t_boolean order by val;
SELECT val, valstr, convert(val, string) as convert2str FROM t_boolean order by val;
SELECT val, valstr, convert(val, char(5)) as convert2char5 FROM t_boolean order by val;
SELECT val, valstr, convert(val, varchar(5)) as convert2varchar5 FROM t_boolean order by val;
SELECT val, valstr, convert(val, clob) as convert2clob FROM t_boolean order by val;
-- the next conversions are okay
SELECT val, valstr, cast(val as int) as cast2int FROM t_boolean order by val;
SELECT val, valstr, cast(val as smallint) as cast2smallint FROM t_boolean order by val;
SELECT val, valstr, cast(val as tinyint) as cast2tinyint FROM t_boolean order by val;
SELECT val, valstr, cast(val as bigint) as cast2bigint FROM t_boolean order by val;
SELECT val, valstr, cast(val as hugeint) as cast2hugeint FROM t_boolean order by val;
-- next casting should fail
SELECT val, valstr, cast(val as real) as cast2real FROM t_boolean order by val;
SELECT val, valstr, cast(val as float) as cast2float FROM t_boolean order by val;
SELECT val, valstr, cast(val as double) as cast2double FROM t_boolean order by val;
SELECT val, valstr, cast(val as time) as cast2time FROM t_boolean order by val;
SELECT val, valstr, cast(val as date) as cast2date FROM t_boolean order by val;
DROP TABLE t_boolean;
### Actual Results:
bash-4.3$ mclient
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.26.0 (unreleased), 'demo'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>CREATE TABLE t_boolean (val BOOLEAN, valstr VARCHAR(5));
operation successful (26.123ms)
sql>INSERT INTO t_boolean VALUES (true, 'True');
1 affected row (7.397ms)
sql>INSERT INTO t_boolean VALUES (false, 'False');
1 affected row (7.853ms)
sql>INSERT INTO t_boolean VALUES (Null, 'Null');
1 affected row (8.000ms)
sql>
sql>SELECT val, valstr, cast(val as bool) as cast2bool FROM t_boolean order by val;
+-------+--------+-----------+
| val | valstr | cast2bool |
+=======+========+===========+
| null | Null | null |
| false | False | false |
| true | True | true |
+-------+--------+-----------+
3 tuples (0.753ms)
sql>SELECT val, valstr, cast(valstr as bool) as caststr2bool FROM t_boolean where val is not null order by val;
+-------+--------+--------------+
| val | valstr | caststr2bool |
+=======+========+==============+
| false | False | false |
| true | True | true |
+-------+--------+--------------+
2 tuples (3.137ms)
sql>
sql>-- the next conversions to char strings are wrong
sql>SELECT val, valstr, cast(val as string) as cast2str FROM t_boolean order by val;
+-------+--------+----------+
| val | valstr | cast2str |
+=======+========+==========+
| null | Null | null |
| false | False | 0 |
| true | True | 1 |
+-------+--------+----------+
3 tuples (2.900ms)
sql>SELECT val, valstr, cast(val as char(5)) as cast2char5 FROM t_boolean order by val;
+-------+--------+------------+
| val | valstr | cast2char5 |
+=======+========+============+
| null | Null | null |
| false | False | 0 |
| true | True | 1 |
+-------+--------+------------+
3 tuples (2.177ms)
sql>SELECT val, valstr, cast(val as varchar(5)) as cast2varchar5 FROM t_boolean order by val;
+-------+--------+---------------+
| val | valstr | cast2varchar5 |
+=======+========+===============+
| null | Null | null |
| false | False | 0 |
| true | True | 1 |
+-------+--------+---------------+
3 tuples (0.925ms)
sql>SELECT val, valstr, cast(val as clob) as cast2clob FROM t_boolean order by val;
+-------+--------+-----------+
| val | valstr | cast2clob |
+=======+========+===========+
| null | Null | null |
| false | False | 0 |
| true | True | 1 |
+-------+--------+-----------+
3 tuples (0.708ms)
sql>
sql>SELECT val, valstr, convert(val, string) as convert2str FROM t_boolean order by val;
+-------+--------+-------------+
| val | valstr | convert2str |
+=======+========+=============+
| null | Null | null |
| false | False | 0 |
| true | True | 1 |
+-------+--------+-------------+
3 tuples (2.842ms)
sql>SELECT val, valstr, convert(val, char(5)) as convert2char5 FROM t_boolean order by val;
+-------+--------+---------------+
| val | valstr | convert2char5 |
+=======+========+===============+
| null | Null | null |
| false | False | 0 |
| true | True | 1 |
+-------+--------+---------------+
3 tuples (0.720ms)
sql>SELECT val, valstr, convert(val, varchar(5)) as convert2varchar5 FROM t_boolean order by val;
+-------+--------+------------------+
| val | valstr | convert2varchar5 |
+=======+========+==================+
| null | Null | null |
| false | False | 0 |
| true | True | 1 |
+-------+--------+------------------+
3 tuples (3.000ms)
sql>SELECT val, valstr, convert(val, clob) as convert2clob FROM t_boolean order by val;
+-------+--------+--------------+
| val | valstr | convert2clob |
+=======+========+==============+
| null | Null | null |
| false | False | 0 |
| true | True | 1 |
+-------+--------+--------------+
3 tuples (2.021ms)
sql>
sql>-- the next conversions are okay
sql>SELECT val, valstr, cast(val as int) as cast2int FROM t_boolean order by val;
+-------+--------+----------+
| val | valstr | cast2int |
+=======+========+==========+
| null | Null | null |
| false | False | 0 |
| true | True | 1 |
+-------+--------+----------+
3 tuples (0.659ms)
sql>SELECT val, valstr, cast(val as smallint) as cast2smallint FROM t_boolean order by val;
+-------+--------+---------------+
| val | valstr | cast2smallint |
+=======+========+===============+
| null | Null | null |
| false | False | 0 |
| true | True | 1 |
+-------+--------+---------------+
3 tuples (0.680ms)
sql>SELECT val, valstr, cast(val as tinyint) as cast2tinyint FROM t_boolean order by val;
+-------+--------+--------------+
| val | valstr | cast2tinyint |
+=======+========+==============+
| null | Null | null |
| false | False | 0 |
| true | True | 1 |
+-------+--------+--------------+
3 tuples (0.731ms)
sql>SELECT val, valstr, cast(val as bigint) as cast2bigint FROM t_boolean order by val;
+-------+--------+-------------+
| val | valstr | cast2bigint |
+=======+========+=============+
| null | Null | null |
| false | False | 0 |
| true | True | 1 |
+-------+--------+-------------+
3 tuples (2.801ms)
sql>SELECT val, valstr, cast(val as hugeint) as cast2hugeint FROM t_boolean order by val;
+-------+--------+--------------+
| val | valstr | cast2hugeint |
+=======+========+==============+
| null | Null | null |
| false | False | 0 |
| true | True | 1 |
+-------+--------+--------------+
3 tuples (0.666ms)
sql>
sql>-- next casting should fail
sql>SELECT val, valstr, cast(val as real) as cast2real FROM t_boolean order by val;
types boolean(1,0) and real(24,0) are not equal for column 'val'
sql>SELECT val, valstr, cast(val as float) as cast2float FROM t_boolean order by val;
types boolean(1,0) and double(53,0) are not equal for column 'val'
sql>SELECT val, valstr, cast(val as double) as cast2double FROM t_boolean order by val;
types boolean(1,0) and double(53,0) are not equal for column 'val'
sql>SELECT val, valstr, cast(val as time) as cast2time FROM t_boolean order by val;
types boolean(1,0) and time(1,0) are not equal for column 'val'
sql>SELECT val, valstr, cast(val as date) as cast2date FROM t_boolean order by val;
types boolean(1,0) and date(0,0) are not equal for column 'val'
sql>
sql>DROP TABLE t_boolean;
operation successful (7.385ms)
sql>
### Expected Results:
sql>SELECT val, valstr, cast(val as string) as cast2str FROM t_boolean order by val;
+-------+--------+----------+
| val | valstr | cast2str |
+=======+========+==========+
| null | Null | null |
| false | False | false |
| true | True | true |
+-------+--------+----------+
3 tuples (2.900ms)
sql>SELECT val, valstr, cast(val as char(5)) as cast2char5 FROM t_boolean order by val;
+-------+--------+------------+
| val | valstr | cast2char5 |
+=======+========+============+
| null | Null | null |
| false | False | false |
| true | True | true |
+-------+--------+------------+
3 tuples (2.177ms)
sql>SELECT val, valstr, cast(val as varchar(5)) as cast2varchar5 FROM t_boolean order by val;
+-------+--------+---------------+
| val | valstr | cast2varchar5 |
+=======+========+===============+
| null | Null | null |
| false | False | false |
| true | True | true |
+-------+--------+---------------+
3 tuples (0.925ms)
sql>SELECT val, valstr, cast(val as clob) as cast2clob FROM t_boolean order by val;
+-------+--------+-----------+
| val | valstr | cast2clob |
+=======+========+===========+
| null | Null | null |
| false | False | false |
| true | True | true |
+-------+--------+-----------+
3 tuples (0.708ms)
sql>
sql>SELECT val, valstr, convert(val, string) as convert2str FROM t_boolean order by val;
+-------+--------+-------------+
| val | valstr | convert2str |
+=======+========+=============+
| null | Null | null |
| false | False | false |
| true | True | true |
+-------+--------+-------------+
3 tuples (2.842ms)
sql>SELECT val, valstr, convert(val, char(5)) as convert2char5 FROM t_boolean order by val;
+-------+--------+---------------+
| val | valstr | convert2char5 |
+=======+========+===============+
| null | Null | null |
| false | False | false |
| true | True | true |
+-------+--------+---------------+
3 tuples (0.720ms)
sql>SELECT val, valstr, convert(val, varchar(5)) as convert2varchar5 FROM t_boolean order by val;
+-------+--------+------------------+
| val | valstr | convert2varchar5 |
+=======+========+==================+
| null | Null | null |
| false | False | false |
| true | True | true |
+-------+--------+------------------+
3 tuples (3.000ms)
sql>SELECT val, valstr, convert(val, clob) as convert2clob FROM t_boolean order by val;
+-------+--------+--------------+
| val | valstr | convert2clob |
+=======+========+==============+
| null | Null | null |
| false | False | false |
| true | True | true |
+-------+--------+--------------+
3 tuples (2.021ms)
output boolean true as "true" when converting to character string
output boolean false as "false" when converting to character string
## Comment 24961
Date: 2017-02-03 14:28:53 +0100
From: @sjoerdmullender
The reason for the values '0' and '1' is given in changeset [fc4bf3655bd0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=fc4bf3655bd0)
## Comment 25082
Date: 2017-03-02 16:46:28 +0100
From: Martin van Dinther <<martin.van.dinther>>
In case the target is (var)char of 5 or more (or clob or text or string) it would be better to return 'true' or 'false'.
Only when target is (var)char 1..4 it should:
- give an error
or
- truncate the string value to first 1..4 characters (this is preferred)
or
- return '0' or '1' (as currently implemented).
Note that if you wanted to convert a boolean to an int (or bit) you should use:
cast(boolean_col as tinyint)
Which can be converted to char(1) using:
cast(cast(boolean_col as tinyint) as char(1))
## Comment 25083
Date: 2017-03-02 17:11:50 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [5164261b899a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=5164261b899a) 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=5164261b899a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=5164261b899a)
Changeset description:
Adding test script for bug #6110
## Comment 25208
Date: 2017-04-08 15:36:44 +0200
From: @njnes
solved, ie we use t/f for small char strings (len 1-5) and full true/false for longer strings
## Comment 25209
Date: 2017-04-08 15:37:27 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [1697b26f2155](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1697b26f2155) 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=1697b26f2155](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=1697b26f2155)
Changeset description:
fix bug #6110, if use t/f and true/false when possible, when converting boolean
values to string
| cast of a SQL boolean value to a string or clob or (var)char is wrong | https://api.github.com/repos/MonetDB/MonetDB/issues/6110/comments | 0 | 2020-11-30T15:26:52Z | 2024-06-27T12:56:58Z | https://github.com/MonetDB/MonetDB/issues/6110 | 753,572,141 | 6,110 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-26 23:45:30 +0200
From: @eyalroz
To: SQL devs <<bugs-sql>>
Version: 11.23.13 (Jun2016-SP2)
CC: bylexewu, @joerivanruth, jordanbelfort533, @kutsurak, martin.van.dinther, @mlkersten, @yzchang, yadavtheddie007
Last updated: 2020-10-06 13:10:12 +0200
## Comment 24635
Date: 2016-10-26 23:45:30 +0200
From: @eyalroz
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0
Build Identifier:
Some DBMSes, as well as applications dealing with tabular data, support descriptions/comments for table columns - essentially, a string associated with each column of a table (not each record). It's a usability feature that has no negative effect on query execution performance, but helps humans who work with the DB (e.g. by describing semantics, or units, or including a web link to other documentation etc.)
MonetDB seems not to support setting column comments/descriptions. It seems like it should not be very difficult to implement, considering how there's a sys.columns table - it would be another column in sys.column. There will also need to be a minor syntax extension; here:
https://www.monetdb.org/Documentation/SQLreference/TableIdentityColumn
there would be another variant for the column_option expansion, specifying a DESCRIPTION or a COMMENT.
Reproducible: Always
## Comment 24636
Date: 2016-10-27 00:02:20 +0200
From: @eyalroz
I might just do that some time, actually. Not until later this year, though.
## Comment 24637
Date: 2016-10-27 00:03:56 +0200
From: @eyalroz
(In reply to Eyal Rozenberg from comment 1)
Oh, sorry the comment spam; that was a reply to a comment by Martin asking whether I would like to add that feature. Like I said, I might.
## Comment 25156
Date: 2017-03-17 16:12:14 +0100
From: @joerivanruth
Many databases allow one to attach a comment to various database
objects such as tables, columns, domains, functions, etc. The
syntax varies between implementations: PostgreSQL, Oracle and
DB2 all have a "COMMENT ON <thing> IS <string>" statement. MySQL
has "COMMENT [=] string" clauses in various parts of its CREATE
and ALTER statements. MS SQL has this:
EXECUTE sp_addextendedproperty 'MS_Description',
'This is my table comment',
'user', @CurrentUser, 'table', 'TABLE_1'
SQLite does not have comments in the catalog at all but
preserves the regular -- comments found in the original CREATE
statement.
It might be easiest to begin with implementing
COMMENT ON <thing> IS <string>
and only as a second step implement the MySQL style extensions on the
CREATE and ALTER statements.
The following table first lists all suitable <thing>s available
in the MonetDB catalog, and whether or not the other databases
support a comment on it. Below the dashes is a list of <thing>s
which other databases support but which do not have a suitable
counterpart in the MonetDB catalog:
| OBJECT | MONETDB | POSTGRES | ORACLE | DB2 | MYSQL |
|--------------------------------+---------+----------+--------+-----+-------|
| AGGREGATE [sc.] f (a...) | y | y | | | |
| COLUMN [sc.] r.c | y | y | y | | y |
| FILTER FUNCTION [sc.] f (a...) | y | | | | |
| FUNCTION [sc.] f (a...) | y | y | | y | y |
| INDEX [ [sc.] r.] i | y | y | | y | |
| CONSTRAINT r.x | y | | | | y |
| LOADER [sc.] f (a...) | y | | | | |
| PROCEDURE [sc.] f (a...) | y | | | y | y |
| ROLE ??? | y | y | | y | |
| SCHEMA sc | y | y | | | |
| SEQUENCE [sc.] s | y | y | | y | |
| TABLE [sc.] r | y | y | y | y | y |
| TRIGGER t ON [sc.] r | y | y | | y | |
| TYPE [sc.] t | y | y | | y | |
| USER ??? | y | | | | |
| VIEW [sc.] v | y | y | | | |
|--------------------------------+---------+----------+--------+-----+-------|
| ACCESS METHOD | | y | | | |
| ALIAS | | | | y | |
| CAST | | y | | | |
| COLLATION | | y | | | |
| CONSTRAINT | | y | | | |
| CONVERSION | | y | | | |
| DATABASE | | y | | | |
| DOMAIN | | y | | | |
| EXTENSION | | y | | | |
| EVENT | | y | | | y |
| FOREIGN DATA WRAPPER | | y | | | |
| FOREIGN TABLE | | y | | | |
| INDEXTYPE | | | y | | |
| LARGE OBJECT | | y | | | |
| MATERIALIZED VIEW | | y | y | | |
| MASK | | | | y | |
| OPERATOR [CLASS or FAMILY] | | y | y | | |
| PARTITION | | | | | y |
| PACKAGE | | | | y | |
| PERMISSION | | | | y | |
| PLAN | | | | y | |
| POLICY | | y | | | |
| RULE | | y | | | |
| SERVER | | y | | | |
| SPECIFIC FUNCTION | | | | y | |
| TABLESPACE | | y | | | y |
| TEXT SEARCH * | | y | | | |
| TRANSFORM FOR | | y | | | |
| TRUSTED CONTEXT | | | | y | |
DB2 seems to support commenting on a list of columns, at once.
This doesn't sound too useful. However, DB2 also allows you to
leave out the parameter names of a function if there is no
ambiguity, which is a nice feature to have.
Comments can be dropped by setting them to NULL or ''.
I haven't yet checked exactly which privileges you need to be
able to set a comment.
## Comment 25297
Date: 2017-05-12 10:08:31 +0200
From: @joerivanruth
Pushed some code on a new branch named comment-on.
It includes some tests under sql/test/Tests/comment-on-*.sql
Still to do:
- add support for more database objects, this should be fairly straightforward
- extend mclient to display the comments
- extend msqldump to dump/restore them
- correctly deal with tmp tables
- verify error handling / error codes returned
- write documentation
## Comment 26379
Date: 2018-04-18 19:25:30 +0200
From: Martin van Dinther <<martin.van.dinther>>
This enhancement request has been implemented in the Mar2018 release.
Extract from the Mar2018 release notes, SQL part:
Added support for COMMENT ON statements using SQL syntax:
COMMENT ON { SCHEMA | TABLE | VIEW | COLUMN | INDEX | SEQUENCE | FUNCTION | PROCEDURE | AGGREGATE | FILTER FUNCTION | LOADER } qname IS { 'my description text' | NULL | '' } ;
For COLUMN the qname can be "table_name"."column_name" or fully qualified as in: "schema_name"."table_name"."column_name".
For FUNCTION, PROCEDURE, AGGREGATE, FILTER FUNCTION and LOADER the qname may need to include the signature (argument types) to be able to differentiate between multiple overloaded functions which have the same name and schema.
By specifying IS NULL or IS '' you remove the comment for the database object.
If a database object is dropped, the associated comment is also removed.
Note: it is not allowed or possible to add comments for temporary tables or objects in schema "tmp".
The sql catalog has been extended with system table: sys.comments.
The keyword 'COMMENT' has now become a reserved keyword.
| Support column descriptions/comments | https://api.github.com/repos/MonetDB/MonetDB/issues/6109/comments | 0 | 2020-11-30T15:26:48Z | 2024-06-27T12:56:57Z | https://github.com/MonetDB/MonetDB/issues/6109 | 753,572,088 | 6,109 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-25 15:41:18 +0200
From: Richard Hughes <<richard.monetdb>>
To: Merovingian devs <<bugs-merovingian>>
Version: 11.23.13 (Jun2016-SP2)
Last updated: 2016-12-21 13:07:17 +0100
## Comment 24627
Date: 2016-10-25 15:41:18 +0200
From: Richard Hughes <<richard.monetdb>>
Created attachment 489
Fix patch
To reproduce:
1) service monetdb5-sql stop; pidof monetdbd
Expected result:
<nothing>
Actual result:
<some pid>
Fix attached.
This affects apt in particular, where during an apt-get upgrade the previous installation may not have stopped by the time the new installation is trying to start up, thus causing a failed start.
> Attached file: [synchronous-monetdbd-stop.patch](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6108_synchronous-monetdbd-stop.patch_489) (text/plain, 756 bytes)
> Description: Fix patch
## Comment 24628
Date: 2016-10-25 16:21:55 +0200
From: @sjoerdmullender
Is this still necessary after changesets [1024269b8b67](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1024269b8b67) and [c786801bc515](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c786801bc515) (the latter from Oct 18)?
The idea of those changes is that when you call monetdbd stop $DBFARM, it now waits until the monetdbd that is serving that farm has actually stopped.
## Comment 24630
Date: 2016-10-25 19:53:26 +0200
From: Richard Hughes <<richard.monetdb>>
(In reply to Sjoerd Mullender from comment 1)
> Is this still necessary after changesets [1024269b8b67](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1024269b8b67) and [c786801bc515](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c786801bc515) (the
> latter from Oct 18)?
> The idea of those changes is that when you call monetdbd stop $DBFARM, it
> now waits until the monetdbd that is serving that farm has actually stopped.
I think it is still necessary. According to the man page, "start-stop-daemon --stop" doesn't actually execute the command with the given arguments (so that bit of the command line could be removed with the patch too), hence none of the code in argvcmds.c gets executed. Instead, it just sends SIGTERM and immediately returns (when --retry is not specified).
## Comment 24632
Date: 2016-10-26 10:22:38 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [4e7ab88f76dd](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4e7ab88f76dd) 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=4e7ab88f76dd](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4e7ab88f76dd)
Changeset description:
Use proper way to stop daemon.
When using "monetdbd stop $FARM", the running daemon is sent a
SIGTERM, after which the sending monetdbd waits a while until the
daemon has actually stopped. When using start-stop-daemon, we can do
the same thing: send a SIGTERM, and wait. start-stop-daemon does not
invoke an external program to stop the daemon as the old code
apparently assumed.
This fixes bug #6108.
## Comment 24649
Date: 2016-11-07 09:29:00 +0100
From: @sjoerdmullender
I have no easy way to test this, but since I followed the rlevant manual page, and my fix is basically the same as the given by Richard, I assume that this is now fixed.
## Comment 24653
Date: 2016-11-07 19:57:01 +0100
From: Richard Hughes <<richard.monetdb>>
Sorry, I didn't realize you wanted me to test it: yes, it works in all the cases I've tried.
| monetdb5-sql sysv init script does not wait for shutdown | https://api.github.com/repos/MonetDB/MonetDB/issues/6108/comments | 0 | 2020-11-30T15:26:44Z | 2024-06-27T12:56:56Z | https://github.com/MonetDB/MonetDB/issues/6108 | 753,572,029 | 6,108 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-24 23:28:37 +0200
From: @eyalroz
To: MonetDB5 devs <<bugs-monetdb5>>
Version: -- development
CC: @mlkersten
Last updated: 2020-03-15 09:31:27 +0100
## Comment 24617
Date: 2016-10-24 23:28:37 +0200
From: @eyalroz
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0
Build Identifier:
Suppose I have the following CSV
foo,bar,baz
quick,1,aaa
brown,2,bbb
fox,,ccc
jumped,3,ddd
and I want bar to be an INT NOT NULL column. At the moment, it seems (if I understand Niels' message to the users' mailing list correctly) that it can't be done. That's a shame, because it forces you to parse and rewrite the data before loading it.
Now, Stefan said:
> The default is (only) used, if you provide (insert) no other value,
> but not is you explicitly provide (insert) a NULL value (see below).
> With copy into you always provide for each record you insert
> values for all columns, possibly indeed NULL values.
>
> sql>create table x (a int, b int not null default 0);
> operation successful (9.079ms)
> sql>insert into x (a) values (1);
> 1 affected row (6.517ms)
> sql>select * from x;
> +------+------+
> | a | b |
> +======+======+
> | 1 | 0 |
> +------+------+
> 1 tuple (1.532ms)
> sql>insert into x (a,b) values (1,NULL);
> INSERT INTO: NOT NULL constraint violated for column x.b
> sql>select * from x;
> +------+------+
> | a | b |
> +======+======+
> | 1 | 0 |
> +------+------+
> 1 tuple (1.634ms)
> sql>
Now, it should not be semantically problematic to make previously-erroneous input acceptable, assigning it a valid interpretation. That is, any CSV that was correctly parsed before would still be parsed just the same if we allowed the default to be applied when NOT NULL is specified, NULL is provided and a DEFAULT is specified.
So, I'm proposing that this be done. To be precise, I propose that:
When parsing a CSV,
if a NULL value is encountered for a certain field of a certain record,
and that field corresponds to a "NOT NULL DEFAULT foo" column for some value foo
then this field of this record will be considered to have had the value foo.
Reproducible: Always
## Comment 27591
Date: 2020-03-15 09:31:27 +0100
From: @mlkersten
This feature request is postponed
| Ability to have empty non-char fields take a default value when loading a CSV | https://api.github.com/repos/MonetDB/MonetDB/issues/6107/comments | 0 | 2020-11-30T15:26:42Z | 2024-06-28T07:06:31Z | https://github.com/MonetDB/MonetDB/issues/6107 | 753,571,993 | 6,107 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6106/comments | 0 | 2020-11-30T15:26:39Z | 2020-11-30T15:26:41Z | https://github.com/MonetDB/MonetDB/issues/6106 | 753,571,953 | 6,106 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6105/comments | 0 | 2020-11-30T15:26:36Z | 2020-11-30T15:26:38Z | https://github.com/MonetDB/MonetDB/issues/6105 | 753,571,916 | 6,105 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6104/comments | 0 | 2020-11-30T15:26:33Z | 2020-11-30T15:26:35Z | https://github.com/MonetDB/MonetDB/issues/6104 | 753,571,882 | 6,104 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6103/comments | 0 | 2020-11-30T15:26:31Z | 2020-11-30T15:26:32Z | https://github.com/MonetDB/MonetDB/issues/6103 | 753,571,847 | 6,103 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6102/comments | 0 | 2020-11-30T15:26:28Z | 2020-11-30T15:26:30Z | https://github.com/MonetDB/MonetDB/issues/6102 | 753,571,811 | 6,102 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6101/comments | 0 | 2020-11-30T15:26:25Z | 2020-11-30T15:26:27Z | https://github.com/MonetDB/MonetDB/issues/6101 | 753,571,758 | 6,101 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6100/comments | 0 | 2020-11-30T15:26:23Z | 2020-11-30T15:26:24Z | https://github.com/MonetDB/MonetDB/issues/6100 | 753,571,729 | 6,100 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6099/comments | 0 | 2020-11-30T15:26:20Z | 2020-11-30T15:26:22Z | https://github.com/MonetDB/MonetDB/issues/6099 | 753,571,693 | 6,099 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6098/comments | 0 | 2020-11-30T15:26:17Z | 2020-11-30T15:26:19Z | https://github.com/MonetDB/MonetDB/issues/6098 | 753,571,637 | 6,098 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6097/comments | 0 | 2020-11-30T15:26:14Z | 2020-11-30T15:26:15Z | https://github.com/MonetDB/MonetDB/issues/6097 | 753,571,592 | 6,097 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6096/comments | 0 | 2020-11-30T15:26:11Z | 2020-11-30T15:26:13Z | https://github.com/MonetDB/MonetDB/issues/6096 | 753,571,545 | 6,096 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6095/comments | 0 | 2020-11-30T15:26:07Z | 2020-11-30T15:26:09Z | https://github.com/MonetDB/MonetDB/issues/6095 | 753,571,496 | 6,095 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6094/comments | 0 | 2020-11-30T15:26:03Z | 2020-11-30T15:26:06Z | https://github.com/MonetDB/MonetDB/issues/6094 | 753,571,427 | 6,094 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6093/comments | 0 | 2020-11-30T15:26:00Z | 2020-11-30T15:26:02Z | https://github.com/MonetDB/MonetDB/issues/6093 | 753,571,379 | 6,093 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6092/comments | 0 | 2020-11-30T15:25:57Z | 2020-11-30T15:25:58Z | https://github.com/MonetDB/MonetDB/issues/6092 | 753,571,344 | 6,092 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6091/comments | 0 | 2020-11-30T15:25:54Z | 2020-11-30T15:25:56Z | https://github.com/MonetDB/MonetDB/issues/6091 | 753,571,305 | 6,091 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6090/comments | 0 | 2020-11-30T15:25:51Z | 2020-11-30T15:25:53Z | https://github.com/MonetDB/MonetDB/issues/6090 | 753,571,266 | 6,090 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6089/comments | 0 | 2020-11-30T15:25:49Z | 2020-11-30T15:25:50Z | https://github.com/MonetDB/MonetDB/issues/6089 | 753,571,222 | 6,089 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6088/comments | 0 | 2020-11-30T15:25:46Z | 2020-11-30T15:25:47Z | https://github.com/MonetDB/MonetDB/issues/6088 | 753,571,190 | 6,088 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6087/comments | 0 | 2020-11-30T15:25:44Z | 2020-11-30T15:25:45Z | https://github.com/MonetDB/MonetDB/issues/6087 | 753,571,173 | 6,087 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6086/comments | 0 | 2020-11-30T15:25:42Z | 2020-11-30T15:25:43Z | https://github.com/MonetDB/MonetDB/issues/6086 | 753,571,148 | 6,086 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6085/comments | 0 | 2020-11-30T15:25:39Z | 2020-11-30T15:25:41Z | https://github.com/MonetDB/MonetDB/issues/6085 | 753,571,107 | 6,085 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-24 18:24:43 +0200
From: @rkoopmanschap
To: SQL devs <<bugs-sql>>
Version: 11.23.13 (Jun2016-SP2)
CC: @njnes
Last updated: 2016-12-21 13:08:25 +0100
## Comment 24591
Date: 2016-10-24 18:24:43 +0200
From: @rkoopmanschap
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:49.0) Gecko/20100101 Firefox/49.0
Build Identifier:
richard.koopmanschap@monetdbsolutions.com
Reproducible: Always
### Steps to Reproduce:
Run the following SQL code in mclient:
start transaction;
CREATE TABLE test_table (d int);
INSERT INTO test_table VALUES (6),(6);
CREATE MERGE TABLE test_merge_table (t int);
ALTER TABLE test_merge_table ADD TABLE test_table;
SELECT * FROM test_merge_table;
ALTER TABLE test_table ADD COLUMN u int;
UPDATE test_table SET u = 2;
SELECT * FROM test_table;
ALTER TABLE test_table DROP COLUMN d;
SELECT * FROM test_merge_table;
rollback;
### Actual Results:
SELECT * FROM mt3;
+------+
| t |
+======+
| 6 |
| 6 |
+------+
SELECT * FROM t5;
+------+------+
| d | u |
+======+======+
| 6 | 2 |
| 6 | 2 |
+------+------+
SELECT * FROM mt3;
+------+
| t |
+======+
| 2 |
| 2 |
+------+
### Expected Results:
Altering the partition table should throw an error. An alternative solution would be to build in support for this in some way.
There is a test for this bug report called: merge-table-edit
## Comment 24592
Date: 2016-10-24 18:32:36 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [6f78ed3dedde](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=6f78ed3dedde) made by Richard Koopmanschap <richard.koopmanschap@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=6f78ed3dedde](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=6f78ed3dedde)
Changeset description:
Added test for bug #6084: Altering partition tables of merge tables
## Comment 24621
Date: 2016-10-25 09:13:12 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [7c12f11415eb](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=7c12f11415eb) 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=7c12f11415eb](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7c12f11415eb)
Changeset description:
fixes for bug #6084 (ie do not allow changes to tables which
are a part of a merge or replica table).
## Comment 24631
Date: 2016-10-26 09:54:31 +0200
From: @njnes
for now we disallow alter add/drop column/constraint on partitions of a merge or replica table.
| Merge table point to wrong columns if columns in partition tables are deleted | https://api.github.com/repos/MonetDB/MonetDB/issues/6084/comments | 0 | 2020-11-30T15:25:35Z | 2024-06-27T12:56:48Z | https://github.com/MonetDB/MonetDB/issues/6084 | 753,571,051 | 6,084 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-24 16:40:15 +0200
From: @eyalroz
To: buildtools devs <<bugs-buildtools>>
Version: 11.23.13 (Jun2016-SP2)
Last updated: 2016-10-25 17:39:04 +0200
## Comment 24588
Date: 2016-10-24 16:40:15 +0200
From: @eyalroz
(This is not about the autogen component nor development tools, it's about the MonetDB package releases)
On 21-10-16 15:49, Peter Lee <peter.y.lee@gmail.com> wrote:
> Hi- I couldn't install MonetDB on Ubuntu 16.04.1 LTS (Xenial Xerus)
> hosted on EC2 yesterday. I kept getting the error below. It looks like
> the repository does not have a "source" folder. However, I noticed that
> the "Trusty" version had a "source" folder, and so I tried installing
> the Trusty version on my Xenial box, and it installed successfully.
>
> So far, I haven't encountered any problems, but was there anything I did
> wrong in the installation process? Will I encounter problems down the
> road with the Trusty version installed on a Xenial box?
>
> $ sudo apt-get update
...
> W: http://dev.monetdb.org/downloads/deb/dists/xenial/Release.gpg:
> Signature by key 213E64DCD5DDC2C063CC39FD053C3ED40583366F uses weak
> digest algorithm (SHA1)
> E: Failed to fetch
> http://dev.monetdb.org/downloads/deb/dists/xenial/Release
> Unable to
> find expected entry 'monetdb/source/Sources' in Release file (Wrong
> sources.list entry or malformed file)
Indeed, in the repository for Ubuntu Trusty Tahr we find
http://dev.monetdb.org/downloads/deb/dists/trusty/monetdb/source/
but there are no such folders for Wily, Xenial, Yakkety:
http://dev.monetdb.org/downloads/deb/dists/wily/monetdb/source/
http://dev.monetdb.org/downloads/deb/dists/xenial/monetdb/source/
http://dev.monetdb.org/downloads/deb/dists/yakkety/monetdb/source/
and they're not mentioned in the Release files
http://dev.monetdb.org/downloads/deb/dists/wily/Release
http://dev.monetdb.org/downloads/deb/dists/xenial/Release
http://dev.monetdb.org/downloads/deb/dists/yakkety/Release
Note: source folders exist for Debian Wheezy and Ubuntu Precise Pangolin - but not for Debian Jessie.
## Comment 24593
Date: 2016-10-24 18:53:18 +0200
From: @sjoerdmullender
Can you try again? Please first run "apt-get update".
## Comment 24619
Date: 2016-10-24 23:40:35 +0200
From: @eyalroz
(In reply to Sjoerd Mullender from comment 1)
> Can you try again? Please first run "apt-get update".
I think you should ask Peter Lee <peter.y.lee@gmail.com> ... I wasn't even trying the first time :-P (I build my version myself).
But I do see that the files and directories have appeared and on a cursory inspection seem be in order.
## Comment 24629
Date: 2016-10-25 17:39:04 +0200
From: @sjoerdmullender
Since I'm able to upgrade to the Jun2016-SP2 version on my Xenial VM, I'm closing this as fixed.
| Sources subfolder missing in the APT repositories for Ubuntu Wily, Xenial | https://api.github.com/repos/MonetDB/MonetDB/issues/6083/comments | 0 | 2020-11-30T15:25:32Z | 2024-06-27T12:56:47Z | https://github.com/MonetDB/MonetDB/issues/6083 | 753,571,000 | 6,083 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-22 14:06:55 +0200
From: @kutsurak
To: SQL devs <<bugs-sql>>
Version: 11.23.13 (Jun2016-SP2)
CC: @mlkersten, @njnes
Last updated: 2017-03-03 10:24:17 +0100
## Comment 24578
Date: 2016-10-22 14:06:55 +0200
From: @kutsurak
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36
Build Identifier:
This bug was reported by José Cavieres in the mailing list. I tried to simplify the query as much as possible, so it might not make any sense :)
Reproducible: Always
### Steps to Reproduce:
sql> create table foo (a int, b int);
sql> select 1 + 1 as bar, sum(b) from foo group by bar;
### Actual Results:
A MAL plan is generated but during its execution the instruction group.subgroupdone is found to be undefined.
The generated MAL plan:
function user.s2_1(A0:sht,A1:sht):void;
sql.mvc();
A0;
A1;
X_6:sht := calc.+(X_4,X_5);
(X_7,r1_7,r2_7) := group.subgroupdone(X_6);
algebra.projection(r1_7,X_6);
bat.setKey(X_10,true);
X_13:bat[:oid] := sql.tid(X_3,"sys","foo");
X_16:bat[:int] := sql.bind(X_3,"sys","foo","b",0);
(X_19,r1_19) := sql.bind(X_3,"sys","foo","b",2);
X_22:bat[:int] := sql.bind(X_3,"sys","foo","b",1);
sql.delta(X_16,X_19,r1_19,X_22);
algebra.projection(X_13,X_24);
X_26:bat[:hge] := aggr.subsum(X_25,X_7,r1_7,true,true);
bat.new(nil:oid,nil:str);
bat.new(nil:oid,nil:str);
bat.new(nil:oid,nil:str);
bat.new(nil:oid,nil:int);
bat.new(nil:oid,nil:int);
bat.append(X_28,".L1");
bat.append(X_31,"bar");
bat.append(X_32,"smallint");
bat.append(X_33,16);
bat.append(X_35,0);
bat.append(X_36,"sys.L3");
bat.append(X_38,"L2");
bat.append(X_40,"hugeint");
bat.append(X_42,128);
bat.append(X_44,0);
sql.resultSet(X_45,X_47,X_49,X_51,X_53,X_11,X_26);
end user.s2_1;
querylog.define("explain select 1 + 1 as bar, sum(b) from foo group by bar;","default_pipe")
## Comment 24634
Date: 2016-10-26 23:41:08 +0200
From: @mlkersten
This error is already triggered in sql_optimizer line 228.
It means that the code generation itself is likely incorrect.
## Comment 24962
Date: 2017-02-03 14:44:16 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [6520196eefda](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=6520196eefda) 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=6520196eefda](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=6520196eefda)
Changeset description:
Added test for bug #6082.
## Comment 24991
Date: 2017-02-08 20:57:39 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [16a638844c75](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=16a638844c75) 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=16a638844c75](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=16a638844c75)
Changeset description:
fixed bug #6082, ie insert constant into a bat before a group mal statement
## Comment 24992
Date: 2017-02-08 20:58:43 +0100
From: @njnes
fixed. make sure we have a bat before calling a group_done
## Comment 25112
Date: 2017-03-03 10:24:17 +0100
From: @sjoerdmullender
Dec2016-SP2 has been released, incorporating the fix.
| group.subgroup is undefined if group by is used on an expression involving only constants | https://api.github.com/repos/MonetDB/MonetDB/issues/6082/comments | 0 | 2020-11-30T15:25:29Z | 2024-06-27T12:56:46Z | https://github.com/MonetDB/MonetDB/issues/6082 | 753,570,949 | 6,082 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-20 11:40:47 +0200
From: Bo Tang <<tangloner>>
To: SQL devs <<bugs-sql>>
Version: 11.23.13 (Jun2016-SP2)
CC: @drstmane
Last updated: 2017-03-03 10:24:55 +0100
## Comment 24558
Date: 2016-10-20 11:40:47 +0200
From: Bo Tang <<tangloner>>
Created attachment 484
debug query
sqlsmith triggered the following assertion:
Segmentation fault (core dumped)
I re-run the attached query with mclient manually, it returned:
TypeException:user.update[1048]:'calc.==' undefined in: calc.==(X_1442:str,X_1444:int);
> Attached file: [bug-6.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6081_bug-6.sql_484) (application/sql, 8433 bytes)
> Description: debug query
## Comment 24560
Date: 2016-10-20 12:38:03 +0200
From: @drstmane
With Jun2016, I see no segfault or assertion (server keeps running), "just" an error:
"TypeException:user.main[1023]:'calc.==' undefined in: calc.==(X_26871:str,X_26873:int);"
And the server reports
"
WARNING To speedup calc.== a bulk operator implementation is needed
X_26473:bat[:bit] := mal.multiplex("calc":str,"==":str,X_26471:bat[:str],X_26472:bat[:int]);
WARNING To speedup calc.== a bulk operator implementation is needed
X_26485:bat[:bit] := mal.multiplex("calc":str,"==":str,X_26482:bat[:bit],X_26484:bat[:int]);
"
## Comment 24561
Date: 2016-10-20 12:39:41 +0200
From: @drstmane
correction:
I used the Dec2016 branch (changeset 8733d8f211a8), not the Jun2016 branch.
## Comment 24565
Date: 2016-10-20 14:49:12 +0200
From: @drstmane
While not occurring with the default and Dec2016 branches,
the segfault indeed occurs with the Jun2016 branch:
WARNING To speedup calc.== a bulk operator implementation is needed
X_1137:bat[:bit] := mal.multiplex("calc":str,"==":str,X_1135:bat[:str],X_1136:bat[:int]);
WARNING To speedup calc.== a bulk operator implementation is needed
X_1142:bat[:bit] := mal.multiplex("calc":str,"==":str,X_1140:bat[:bit],X_1141:bat[:int]);
Thread 5 "mserver5" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffc0930700 (LWP 17487)]
0x00007fffe8177c87 in sa_reset (sa=0x7fff00000000) at /ufs/manegold/_/Monet/HG/Jun2016/source/MonetDB/sql/common/sql_mem.c:65
65 for (i = 1; i<sa->nr; i++) {
Missing separate debuginfos, use: dnf debuginfo-install R-core-3.3.1-2.fc24.x86_64 SuperLU-5.2.0-1.fc24.x86_64 armadillo-7.300.1-1.fc24.x86_64 arpack-3.3.0-2.b0f7a60git.fc24.x86_64 atlas-3.10.2-12.fc24.x86_64 blas-3.6.1-1.fc24.x86_64 boost-atomic-1.60.0-7.fc24.x86_64 boost-chrono-1.60.0-7.fc24.x86_64 boost-date-time-1.60.0-7.fc24.x86_64 boost-filesystem-1.60.0-7.fc24.x86_64 boost-iostreams-1.60.0-7.fc24.x86_64 boost-program-options-1.60.0-7.fc24.x86_64 boost-regex-1.60.0-7.fc24.x86_64 boost-system-1.60.0-7.fc24.x86_64 boost-thread-1.60.0-7.fc24.x86_64 bzip2-libs-1.0.6-20.fc24.x86_64 cfitsio-3.370-6.fc24.x86_64 cyrus-sasl-lib-2.1.26-26.2.fc24.x86_64 expat-2.1.1-2.fc24.x86_64 fontconfig-2.11.94-7.fc24.x86_64 freetype-2.6.3-2.fc24.x86_64 freexl-1.0.2-3.fc24.x86_64 gdal-libs-2.0.2-6.fc24.x86_64 geos-3.5.0-1.fc24.x86_64 giflib-4.1.6-15.fc24.x86_64 gsl-2.1-4.fc24.x86_64 hdf5-1.8.16-3.fc24.x86_64 jasper-libs-1.900.1-34.fc24.x86_64 jbigkit-libs-2.1-5.fc24.x86_64 keyutils-libs-1.5.9-8.fc24.x86_64 krb5-libs-1.14.4-4.fc24.x86_64 lapack-3.6.1-1.fc24.x86_64 laszip-2.2.0-6.fc24.x86_64 lcms2-2.8-2.fc24.x86_64 libICE-1.0.9-5.fc24.x86_64 libSM-1.2.2-4.fc24.x86_64 libX11-1.6.3-3.fc24.x86_64 libXau-1.0.8-6.fc24.x86_64 libatomic_ops-7.4.2-9.fc24.x86_64 libcom_err-1.42.13-4.fc24.x86_64 libcurl-7.47.1-8.fc24.x86_64 libdap-3.17.2-1.fc24.x86_64 libgcc-6.2.1-2.fc24.x86_64 libgeotiff-1.4.0-7.fc24.x86_64 libgfortran-6.2.1-2.fc24.x86_64 libgomp-6.2.1-2.fc24.x86_64 libgta-1.0.7-3.fc24.x86_64 libicu-56.1-4.fc24.x86_64 libidn-1.33-1.fc24.x86_64 libjpeg-turbo-1.5.0-4.fc24.x86_64 liblas-1.8.0-13.fc24.x86_64 libnghttp2-1.7.1-1.fc24.x86_64 libpng-1.6.23-1.fc24.x86_64 libpsl-0.13.0-2.fc24.x86_64 libquadmath-6.2.1-2.fc24.x86_64 libselinux-2.5-9.fc24.x86_64 libspatialite-4.3.0a-2.fc24.x86_64 libssh2-1.7.0-5.fc24.x86_64 libstdc++-6.2.1-2.fc24.x86_64 libtiff-4.0.6-2.fc24.x86_64 libtool-ltdl-2.4.6-12.fc24.x86_64 libunistring-0.9.4-3.fc24.x86_64 libuuid-2.28.2-1.fc24.x86_64 libwebp-0.5.1-1.fc24.x86_64 libxcb-1.11.1-2.fc24.x86_64 libxml2-2.9.3-3.fc24.x86_64 mariadb-libs-10.1.18-1.fc24.x86_64 ncurses-libs-6.0-6.20160709.fc24.x86_64 netcdf-4.4.0-3.fc24.x86_64 nspr-4.13.0-1.fc24.x86_64 nss-3.27.0-1.1.fc24.x86_64 nss-softokn-freebl-3.27.0-1.0.fc24.x86_64 nss-util-3.27.0-1.0.fc24.x86_64 ogdi-3.2.0-0.26.beta2.fc24.x86_64 openblas-openmp-0.2.18-5.fc24.x86_64 openjpeg2-2.1.2-1.fc24.x86_64 openldap-2.4.44-1.fc24.x86_64 openssl-libs-1.0.2j-1.fc24.x86_64 pcre-8.39-3.fc24.x86_64 poppler-0.41.0-3.fc24.x86_64 postgresql-libs-9.5.4-1.fc24.x86_64 proj-4.9.2-2.fc24.x86_64 readline-6.3-8.fc24.x86_64 sqlite-libs-3.13.0-1.fc24.x86_64 tre-0.8.0-16.20140228gitc2f5d13.fc24.x86_64 unixODBC-2.3.4-2.fc24.x86_64 xerces-c-3.1.4-1.fc24.x86_64 xz-libs-5.2.2-2.fc24.x86_64 zlib-1.2.8-10.fc24.x86_64
(gdb) bt
0 0x00007fffe8177c87 in sa_reset (sa=0x7fff00000000) at /ufs/manegold/_/Monet/HG/Jun2016/source/MonetDB/sql/common/sql_mem.c:65
1 0x00007fffe7fe80c8 in sqlcleanup (c=0x7fffb8010c40, err=0) at /ufs/manegold/_/Monet/HG/Jun2016/source/MonetDB/sql/backends/monet5/sql.c:172
2 0x00007fffe800f221 in SQLparser (c=0x7fffe9db2330) at /ufs/manegold/_/Monet/HG/Jun2016/source/MonetDB/sql/backends/monet5/sql_scenario.c:1326
3 0x00007ffff797d85a in runPhase (c=0x7fffe9db2330, phase=1) at /ufs/manegold/_/Monet/HG/Jun2016/source/MonetDB/monetdb5/mal/mal_scenario.c:531
4 0x00007ffff797da01 in runScenarioBody (c=0x7fffe9db2330) at /ufs/manegold/_/Monet/HG/Jun2016/source/MonetDB/monetdb5/mal/mal_scenario.c:566
5 0x00007ffff797dbac in runScenario (c=0x7fffe9db2330) at /ufs/manegold/_/Monet/HG/Jun2016/source/MonetDB/monetdb5/mal/mal_scenario.c:595
6 0x00007ffff797f738 in MSserveClient (dummy=0x7fffe9db2330) at /ufs/manegold/_/Monet/HG/Jun2016/source/MonetDB/monetdb5/mal/mal_session.c:457
7 0x00007ffff797f18c in MSscheduleClient (command=0x7fffb80008d0 "\340`\f\270\377\177", challenge=0x7fffc092fd70 "noo75rWC", fin=0x7fffb8002980, fout=0x7fffb4002b60) at /ufs/manegold/_/Monet/HG/Jun2016/source/MonetDB/monetdb5/mal/mal_session.c:342
8 0x00007ffff7a39dd5 in doChallenge (data=0x7fffb40008d0) at /ufs/manegold/_/Monet/HG/Jun2016/source/MonetDB/monetdb5/modules/mal/mal_mapi.c:205
9 0x00007ffff739475f in thread_starter (arg=0x7fffb4004c50) at /ufs/manegold/_/Monet/HG/Jun2016/source/MonetDB/gdk/gdk_system.c:485
10 0x00007ffff48f25ca in start_thread () from /lib64/libpthread.so.0
11 0x00007ffff462bf6d in clone () from /lib64/libc.so.6
(gdb) li
60
61 sql_allocator *sa_reset( sql_allocator *sa )
62 {
63 size_t i ;
64
65 for (i = 1; i<sa->nr; i++) {
66 _DELETE(sa->blks[i]);
67 }
68 sa->nr = 1;
69 sa->used = 0;
(gdb) p sa
$1 = (sql_allocator *) 0x7fff00000000
(gdb) p *sa
Cannot access memory at address 0x7fff00000000
(gdb) p i
$2 = 1
(gdb) up
1 0x00007fffe7fe80c8 in sqlcleanup (c=0x7fffb8010c40, err=0) at /ufs/manegold/_/Monet/HG/Jun2016/source/MonetDB/sql/backends/monet5/sql.c:172
172 c->sa = sa_reset(c->sa);
(gdb) li
167 c->emod = 0;
168 }
169 /* some statements dynamically disable caching */
170 c->sym = NULL;
171 if (c->sa)
172 c->sa = sa_reset(c->sa);
173 if (err >0)
174 c->session->status = -err;
175 if (err <0)
176 c->session->status = err;
(gdb) p c
$3 = (mvc *) 0x7fffb8010c40
(gdb) p *c
$4 = {errstr = '\000' <repeats 20 times>, "\005", '\000' <repeats 31 times>, "\005", '\000' <repeats 31 times>, "\005", '\000' <repeats 31 times>, "\005", '\000' <repeats 31 times>, "\005", '\000' <repeats 31 times>, "\005", '\000' <repeats 31 times>..., sa = 0x7fff00000000, qc = 0x7fffb8003a50, clientid = 0, scanner = {rs = 0x7fffb8002980, ws = 0x7fff00000000, log = 0x0, yynext = 0, yylast = 5, yysval = 8431,
yyval = 385, yycur = 0, yybak = 0 '\000', as = 0, key = 0, started = 0, mode = (LINE_N | unknown: 4), schema = 0x0, errstr = 0x0}, params = 0x0, forward = 0x500000000, vars = 0x7fffb80008d0, topvars = 0, sizevars = 32, frame = 1, use_views = 0, args = 0x500000000, argc = 0, argmax = 32, sym = 0x0, no_mitosis = 0, user_id = 3, role_id = 0, last_id = -1, rowcnt = -4294967296, timezone = 7200000, cache = 100,
caching = 0, history = 5, reply_size = -1, sizeheader = 0, debug = 0, emode = 0 '\000', emod = 0 '\000', session = 0x7fffb8003bb0, type = 0, pushdown = 5, label = 75, cascade_action = 0x0, opt_stats = {0, 0, 0, 5, 0, 0, 0, 0}, result_id = 0, results = 0x500000000}
(gdb)
## Comment 24568
Date: 2016-10-20 15:27:11 +0200
From: @sjoerdmullender
valgrind gives some worrying errors in the Jun2016 branch. It looks like freeVariables() accesses data beyond the end of the array. glb->stk isn't as long as mb->vtop expects.
## Comment 24573
Date: 2016-10-21 11:28:33 +0200
From: Bo Tang <<tangloner>>
Created attachment 485
another query for segmentation fault
> Attached file: [bug-7.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6081_bug-7.sql_485) (application/sql, 137 bytes)
> Description: another query for segmentation fault
## Comment 24574
Date: 2016-10-21 11:31:40 +0200
From: Bo Tang <<tangloner>>
For the later query, gdb backtrace shows:
0 0x00007ffff5d9b090 in __write_nocancel () from /lib64/libc.so.6
1 0x00007ffff79b2153 in socket_write (s=0x751370, buf=0x6bfe30, elmsize=1, cnt=26) at stream.c:2112
2 0x00007ffff79b4eca in bs_flush (ss=0x7323c0) at stream.c:3716
3 0x00007ffff79ae42e in mnstr_flush (s=0x7323c0) at stream.c:474
4 0x00007ffff7bcbc5a in mapi_execute_internal (hdl=0x1c503a60) at mapi.c:4166
5 0x00007ffff7bcbff9 in mapi_query (mid=0x750f30, cmd=0x47345f "CALL sys.settimeout(1)") at mapi.c:4217
6 0x000000000042178a in dut_monetdb::test (this=this@entry=0x6ab410,...) at monetdb.cc:217
7 0x0000000000411942 in main (argc=<optimized out>, argv=<optimized out>) at sqlsmith.cc:209
## Comment 24577
Date: 2016-10-21 16:23:07 +0200
From: Bo Tang <<tangloner>>
Created attachment 487
this query also triggered Segmentation fault (core dumped)
> Attached file: [bug-9.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6081_bug-9.sql_487) (application/sql, 1958 bytes)
> Description: this query also triggered Segmentation fault (core dumped)
## Comment 24587
Date: 2016-10-24 16:03:50 +0200
From: Bo Tang <<tangloner>>
Created attachment 488
one more query for segmentation fault
> Attached file: [bug-10.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6081_bug-10.sql_488) (application/sql, 285 bytes)
> Description: one more query for segmentation fault
## Comment 24647
Date: 2016-11-03 10:19:09 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [0a940b3f3f28](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0a940b3f3f28) 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=0a940b3f3f28](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0a940b3f3f28)
Changeset description:
fixed crash in bug #6081
## Comment 24650
Date: 2016-11-07 09:34:42 +0100
From: @sjoerdmullender
(In reply to MonetDB Mercurial Repository from comment 9)
> Changeset [0a940b3f3f28](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0a940b3f3f28) 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=0a940b3f3f28](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0a940b3f3f28)
>
> Changeset description:
>
> fixed crash in bug #6081
This does *not* fix the problem I referred to in comment 4.
## Comment 24651
Date: 2016-11-07 10:32:47 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [6c8b4094bb16](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=6c8b4094bb16) 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=6c8b4094bb16](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=6c8b4094bb16)
Changeset description:
Don't try to free the global stack before it was initialized.
This fixes bug #6081.
## Comment 24652
Date: 2016-11-07 10:35:20 +0100
From: @sjoerdmullender
(In reply to MonetDB Mercurial Repository from comment 11)
> Changeset [6c8b4094bb16](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=6c8b4094bb16) 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=6c8b4094bb16](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=6c8b4094bb16)
>
> Changeset description:
>
> Don't try to free the global stack before it was initialized.
> This fixes bug #6081.
This is actually a fix for comment 4, not for the calc.== undefined issue.
## Comment 24963
Date: 2017-02-03 14:56:23 +0100
From: @sjoerdmullender
None of the queries results in a crash or even warnings about calc.== in the Dec2016 branch.
## Comment 25131
Date: 2017-03-03 10:24:55 +0100
From: @sjoerdmullender
Dec2016-SP2 has been released, incorporating the fix.
| Segmentation fault (core dumped) | https://api.github.com/repos/MonetDB/MonetDB/issues/6081/comments | 0 | 2020-11-30T15:25:25Z | 2024-06-27T12:56:45Z | https://github.com/MonetDB/MonetDB/issues/6081 | 753,570,900 | 6,081 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-20 10:26:16 +0200
From: Bo Tang <<tangloner>>
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @njnes
Last updated: 2017-03-03 10:24:46 +0100
## Comment 24557
Date: 2016-10-20 10:26:16 +0200
From: Bo Tang <<tangloner>>
Created attachment 483
query for debug
sqlsmith triggered the following assertion:
mserver5: rel_bin.c:2391: rel2bin_project: Assertion `0' failed.
> Attached file: [bug-5.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6080_bug-5.sql_483) (application/sql, 1017 bytes)
> Description: query for debug
## Comment 24576
Date: 2016-10-21 16:17:50 +0200
From: Bo Tang <<tangloner>>
Created attachment 486
another query for this bug
> Attached file: [bug-8.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6080_bug-8.sql_486) (application/sql, 566 bytes)
> Description: another query for this bug
## Comment 24964
Date: 2017-02-03 15:02:21 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [5e21efb70081](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=5e21efb70081) 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=5e21efb70081](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=5e21efb70081)
Changeset description:
Added test for bug #6080.
## Comment 25008
Date: 2017-02-12 12:41:33 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [936301a9a4f3](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=936301a9a4f3) 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=936301a9a4f3](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=936301a9a4f3)
Changeset description:
fixed bug #6080, ie dead code elimination removed all columns.
## Comment 25009
Date: 2017-02-12 12:42:26 +0100
From: @njnes
fixed a problem in the deadcode optimizer
## Comment 25126
Date: 2017-03-03 10:24:46 +0100
From: @sjoerdmullender
Dec2016-SP2 has been released, incorporating the fix.
| mserver5: rel_bin.c:2391: rel2bin_project: Assertion `0' failed. | https://api.github.com/repos/MonetDB/MonetDB/issues/6080/comments | 0 | 2020-11-30T15:25:23Z | 2024-06-27T12:56:44Z | https://github.com/MonetDB/MonetDB/issues/6080 | 753,570,859 | 6,080 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-15 20:34:29 +0200
From: muesli4
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.23.13 (Jun2016-SP2)
CC: @mlkersten
Last updated: 2017-01-26 14:56:24 +0100
## Comment 24515
Date: 2016-10-15 20:34:29 +0200
From: muesli4
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0
Build Identifier:
I don't know whether it's directly related to the pushselect optimizer, but the following snippet only fails with it:
sql.init();
function f156() (v11:bat[:lng]);
v0:int := sql.mvc();
v1:bat[:oid] := sql.tid(v0, "sys", "customer");
v2:bat[:lng] := sql.bind(v0, "sys", "customer", "c_acctbal", 0:int);
(v3:bat[:oid], v4:bat[:lng]) := sql.bind(v0, "sys", "customer", "c_acctbal", 2:int);
v5:bat[:lng] := sql.bind(v0, "sys", "customer", "c_acctbal", 1:int);
v6:bat[:lng] := sql.delta(v2, v3, v4, v5);
v7:bat[:lng] := algebra.projection(v1, v6);
v10:bat[:oid] := algebra.subselect(v7, 700000:lng, nil:lng, false, false, false);
v11:bat[:lng] := algebra.projection(v10, v7);
v16:bat[:oid] := bat.mirror(v10);
v18:bat[:lng] := algebra.projection(v16, v11);
return v11;
end f156;
optimizer.pushselect("user", "f156");
v11:bat[:lng] := f156();
Reproducible: Always
### Steps to Reproduce:
1.Run the snippet
### Actual Results:
MonetDB crashes with a segfault.
Mercurial revision: [3b06c3df35f7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=3b06c3df35f7)
## Comment 24516
Date: 2016-10-15 20:35:21 +0200
From: muesli4
Created attachment 480
MAL Code that fails
> Attached file: [bug.mal](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6079_bug.mal_480) (application/octet-stream, 770 bytes)
> Description: MAL Code that fails
## Comment 24845
Date: 2016-12-21 23:23:10 +0100
From: @mlkersten
Added the test to the testsuite.
Added defensive code to avoid raising this assertion.
## Comment 24915
Date: 2017-01-26 14:56:24 +0100
From: @kutsurak
Fixed in version Dec2016-SP1.
| pushselect optimizer bug on MAL snippet | https://api.github.com/repos/MonetDB/MonetDB/issues/6079/comments | 0 | 2020-11-30T15:25:19Z | 2024-06-27T12:56:43Z | https://github.com/MonetDB/MonetDB/issues/6079 | 753,570,811 | 6,079 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-14 14:02:25 +0200
From: Bo Tang <<tangloner>>
To: SQL devs <<bugs-sql>>
Version: 11.23.13 (Jun2016-SP2)
CC: @njnes, @drstmane
Last updated: 2016-12-21 13:07:27 +0100
## Comment 24513
Date: 2016-10-14 14:02:25 +0200
From: Bo Tang <<tangloner>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36
Build Identifier:
sqlsmith triggered the following assertion:
rel_bin.c:2402: rel2bin_project: Assertion `0' failed.
Reproducible: Always
### Steps to Reproduce:
1. start mserver5 with database "tpch-1" (i.e., tpch dataset with scale factor 1)
2. run the attached query
### Actual Results:
mserver5 aborted
## Comment 24514
Date: 2016-10-14 14:03:08 +0200
From: Bo Tang <<tangloner>>
Created attachment 479
test query
> Attached file: [bug-4.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6078_bug-4.sql_479) (application/sql, 1013 bytes)
> Description: test query
## Comment 24524
Date: 2016-10-17 14:57:21 +0200
From: @drstmane
A virgin empty database is sufficient to reproduce the assertion; no TPC-H schema or data is required.
## Comment 24546
Date: 2016-10-19 14:22:16 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [ce980adad65b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ce980adad65b) 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=ce980adad65b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ce980adad65b)
Changeset description:
fixed bugs 6078, 6077 and 6076
All related to naming a table producing function.
## Comment 24549
Date: 2016-10-19 14:23:21 +0200
From: @njnes
fixed in jun2016
| rel_bin.c:2402: rel2bin_project: Assertion `0' failed. | https://api.github.com/repos/MonetDB/MonetDB/issues/6078/comments | 0 | 2020-11-30T15:25:16Z | 2024-06-27T12:56:42Z | https://github.com/MonetDB/MonetDB/issues/6078 | 753,570,763 | 6,078 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-13 13:35:44 +0200
From: Bo Tang <<tangloner>>
To: SQL devs <<bugs-sql>>
Version: 11.23.13 (Jun2016-SP2)
CC: @njnes, @drstmane
Last updated: 2016-12-21 13:08:02 +0100
## Comment 24507
Date: 2016-10-13 13:35:44 +0200
From: Bo Tang <<tangloner>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36
Build Identifier:
sqlsmith triggered the following assertion:
rel_optimizer.c:5444: rel_push_project_up: Assertion `e' failed.
Reproducible: Always
### Steps to Reproduce:
1. start mserver5 with database "tpch-1" (i.e., tpch dataset with scale factor 1)
2. run the above query
### Actual Results:
mserver5 aborted
## Comment 24508
Date: 2016-10-13 13:38:05 +0200
From: Bo Tang <<tangloner>>
Created attachment 477
the query triggered "rel_optimizer.c:5444: rel_push_project_up: Assertion `e' failed."
> Attached file: [bug-3.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6077_bug-3.sql_477) (application/sql, 1844 bytes)
> Description: the query triggered "rel_optimizer.c:5444: rel_push_project_up: Assertion `e' failed."
## Comment 24523
Date: 2016-10-17 14:54:31 +0200
From: @drstmane
To reproduce the assertion, only the TPC-H schema is requires, no TPC-H data is required.
## Comment 24545
Date: 2016-10-19 14:22:14 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [ce980adad65b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ce980adad65b) 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=ce980adad65b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ce980adad65b)
Changeset description:
fixed bugs 6078, 6077 and 6076
All related to naming a table producing function.
## Comment 24548
Date: 2016-10-19 14:23:02 +0200
From: @njnes
fixed in Jun2016
| mserver5: rel_optimizer.c:5444: rel_push_project_up: Assertion `e' failed. | https://api.github.com/repos/MonetDB/MonetDB/issues/6077/comments | 0 | 2020-11-30T15:25:13Z | 2024-06-27T12:56:41Z | https://github.com/MonetDB/MonetDB/issues/6077 | 753,570,728 | 6,077 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-13 13:22:50 +0200
From: Bo Tang <<tangloner>>
To: SQL devs <<bugs-sql>>
Version: 11.23.13 (Jun2016-SP2)
CC: @njnes, @drstmane
Last updated: 2016-12-21 13:08:00 +0100
## Comment 24505
Date: 2016-10-13 13:22:50 +0200
From: Bo Tang <<tangloner>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36
Build Identifier:
sqlsmith triggered the following assertion:
rel_optimizer.c:5426: rel_push_project_up: Assertion `e' failed.
Reproducible: Always
### Steps to Reproduce:
### Steps to Reproduce:
1. start mserver5 with database "tpch-1" (i.e., tpch dataset with sf 1)
2. run the attached query
### Actual Results:
mserver5 aborted
## Comment 24506
Date: 2016-10-13 13:24:51 +0200
From: Bo Tang <<tangloner>>
Created attachment 476
the query triggered "rel_optimizer.c:5426: rel_push_project_up: Assertion `e' failed."
> Attached file: [4.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6076_4.sql_476) (application/sql, 712 bytes)
> Description: the query triggered "rel_optimizer.c:5426: rel_push_project_up: Assertion `e' failed."
## Comment 24520
Date: 2016-10-17 14:40:43 +0200
From: @drstmane
Already the first query in the attachment triggers the assertion on an empty virgin database, i.e., no TPC-H database required.
## Comment 24522
Date: 2016-10-17 14:43:01 +0200
From: @drstmane
The second query in the attachment correctly (by MonetDB standards) triggers a syntax error:
syntax error, unexpected LIMIT, expecting UNION or EXCEPT or INTERSECT or ')' in: "select
(select typewidth from sys.storagemodelinput limit"
"limit" (and "offset"?) are not allowed in subqueries.
## Comment 24544
Date: 2016-10-19 14:22:10 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [ce980adad65b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ce980adad65b) 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=ce980adad65b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ce980adad65b)
Changeset description:
fixed bugs 6078, 6077 and 6076
All related to naming a table producing function.
## Comment 24547
Date: 2016-10-19 14:22:39 +0200
From: @njnes
fixed in jun2016
| rel_optimizer.c:5426: rel_push_project_up: Assertion `e' failed. | https://api.github.com/repos/MonetDB/MonetDB/issues/6076/comments | 0 | 2020-11-30T15:25:10Z | 2024-06-27T12:56:40Z | https://github.com/MonetDB/MonetDB/issues/6076 | 753,570,680 | 6,076 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-13 13:14:14 +0200
From: Bo Tang <<tangloner>>
To: GDK devs <<bugs-common>>
Version: 11.23.13 (Jun2016-SP2)
CC: @drstmane
Last updated: 2016-12-21 13:06:59 +0100
## Comment 24504
Date: 2016-10-13 13:14:14 +0200
From: Bo Tang <<tangloner>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36
Build Identifier:
sqlsmith triggered the following assertion:
gdk_calc.c:13113: BATcalcifthenelse_intern: Assertion `col2 != NULL' failed.
query details:
select
ref_17.progress as c0,
cast(coalesce(ref_17.tag,
ref_17.tag) as oid) as c1
from
sys.queue as ref_17
where false
limit 156;
select
(select event from sys.triggers limit 1 offset 5)
as c0,
ref_101.function_id as c1,
ref_89.s_nationkey as c2,
45 as c3,
(select value from sys.environment limit 1 offset 2)
as c4,
4 as c5,
ref_89.s_suppkey as c6,
cast(coalesce(ref_90.writes,
ref_90.majflt) as bigint) as c7,
ref_96.ps_availqty as c8,
(select id from tmp._tables limit 1 offset 1)
as c9,
ref_86.r_regionkey as c10,
ref_90.thread as c11,
(select table_id from tmp.keys limit 1 offset 4)
as c12,
ref_91.id as c13,
3 as c14,
6 as c15,
ref_90.event as c16,
(select table_id from sys.idxs limit 1 offset 2)
as c17,
(select commit_action from sys.tables limit 1 offset 5)
as c18,
cast(coalesce(ref_99.type_scale,
40) as int) as c19,
72 as c20,
ref_101.function_id as c21,
(select active from sys.sessions limit 1 offset 2)
as c22,
cast(coalesce((select typewidth from sys.storagemodelinput limit 1 offset 1)
,
ref_99.type_digits) as int) as c23,
ref_98.f_table_schema as c24,
ref_89.s_address as c25,
(select id from sys._tables limit 1 offset 5)
as c26,
(select l_returnflag from sys.lineitem limit 1 offset 4)
as c27
from
sys.region as ref_86
right join bam.sq as ref_87
inner join sys.keywords as ref_88
inner join sys.supplier as ref_89
left join sys.tracelog as ref_90
on (ref_89.s_nationkey = ref_90.event )
on (ref_88.keyword = ref_90.clk )
on (ref_87.ur = ref_90.stmt )
on (ref_86.r_regionkey = ref_87.ln )
inner join sys.objects as ref_91
inner join sys.partsupp as ref_96
inner join sys.keys as ref_97
inner join sys.geometry_columns as ref_98
on (ref_97.rkey = ref_98.srid )
on (ref_96.ps_partkey = ref_97.id )
on (ref_91.nr = ref_96.ps_partkey )
on (ref_90.clk = ref_98.f_table_schema )
inner join tmp._columns as ref_99
on (ref_97.rkey = ref_99.id )
inner join sys.systemfunctions as ref_101
on (ref_86.r_regionkey = ref_101.function_id )
where true
limit 39;
Reproducible: Always
### Steps to Reproduce:
1. start mserver5 with database "tpch-1" (i.e., tpch dataset with scale factor 1)
2. run the above query
### Actual Results:
mserver5 aborted
## Comment 24509
Date: 2016-10-13 13:44:58 +0200
From: Bo Tang <<tangloner>>
Created attachment 478
a more simple query for this bug
> Attached file: [bug-1.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6075_bug-1.sql_478) (application/sql, 224 bytes)
> Description: a more simple query for this bug
## Comment 24518
Date: 2016-10-17 14:32:27 +0200
From: @drstmane
Already the first query
select
ref_17.progress as c0,
cast(coalesce(ref_17.tag,
ref_17.tag) as oid) as c1
from
sys.queue as ref_17
where false
limit 156;
triggers the assertion on an empty virgin database.
## Comment 24519
Date: 2016-10-17 14:36:00 +0200
From: @drstmane
The second query triggers a syntax error:
syntax error, unexpected LIMIT, expecting UNION or EXCEPT or INTERSECT or ')' in: "select
(select event from sys.triggers limit"
## Comment 24521
Date: 2016-10-17 14:41:49 +0200
From: @drstmane
The syntax error is "correct" by MonetDB standards: "limit" (and "offset"?) are not allowed in subqueries.
## Comment 24525
Date: 2016-10-17 16:08:55 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [0f67d09dfca6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0f67d09dfca6) 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=0f67d09dfca6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0f67d09dfca6)
Changeset description:
Provide missing implementation for batcalc.ifthenelse for void columns.
This fixes bug #6075.
## Comment 24526
Date: 2016-10-17 16:09:12 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [65b10dd14c09](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=65b10dd14c09) 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=65b10dd14c09](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=65b10dd14c09)
Changeset description:
Added test for bug #6075.
## Comment 24527
Date: 2016-10-17 17:05:23 +0200
From: @sjoerdmullender
The assertion has been fixed. The syntax errors won't be.
| gdk_calc.c:13113: BATcalcifthenelse_intern: Assertion `col2 != NULL' failed. | https://api.github.com/repos/MonetDB/MonetDB/issues/6075/comments | 0 | 2020-11-30T15:25:08Z | 2024-06-27T12:56:39Z | https://github.com/MonetDB/MonetDB/issues/6075 | 753,570,662 | 6,075 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-13 12:44:34 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.23.13 (Jun2016-SP2)
CC: @njnes
Last updated: 2016-12-21 13:08:13 +0100
## Comment 24503
Date: 2016-10-13 12:44:34 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0
Build Identifier:
SQL command: SET ROLE <rolename>
fails to execute. The error msg is: Role (rolename) missing
Reproducible: Always
### Steps to Reproduce:
1. Start mserver5
2. Start mclient
3. Execute SQL Commands:
SELECT CURRENT_ROLE;
SELECT name FROM sys.auths;
SET ROLE public;
-- syntax error, unexpected PUBLIC, expecting '=' in: "set role public"
SET ROLE sysadmin;
-- Role (sysadmin) missing
CREATE ROLE r123;
SELECT name FROM sys.auths;
-- new role r123 is visible
SET ROLE r123;
-- Role (r123) missing
-- try some alternative SET ROLE syntax
SET ROLE 'r123';
-- syntax error, unexpected STRING, expecting '=' in: "set role 'r123'"
SET ROLE = r123;
-- Variable role unknown
SET CURRENT_ROLE r123;
-- syntax error, unexpected CURRENT_ROLE in: "set current_role"
SELECT CURRENT_ROLE;
DROP ROLE r123;
SELECT name FROM sys.auths;
SELECT CURRENT_ROLE;
### Actual Results:
bash-4.3$ mclient
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.24.0 (unreleased), 'demo'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>SELECT CURRENT_ROLE;
+--------------+
| single_value |
+==============+
| monetdb |
+--------------+
1 tuple (0.501ms)
sql>SELECT name FROM sys.auths;
+----------+
| name |
+==========+
| public |
| sysadmin |
| monetdb |
+----------+
3 tuples (0.742ms)
sql>
sql>SET ROLE public;
syntax error, unexpected PUBLIC, expecting '=' in: "set role public"
sql>SET ROLE sysadmin;
Role (sysadmin) missing
sql>
sql>CREATE ROLE r123;
operation successful (26.186ms)
sql>SELECT name FROM sys.auths;
+----------+
| name |
+==========+
| public |
| sysadmin |
| monetdb |
| r123 |
+----------+
4 tuples (1.839ms)
sql>SET ROLE r123;
Role (r123) missing
sql>SET ROLE 'r123';
syntax error, unexpected STRING, expecting '=' in: "set role 'r123'"
sql>SET ROLE = r123;
Variable role unknown
sql>SET CURRENT_ROLE r123;
syntax error, unexpected CURRENT_ROLE in: "set current_role"
sql>
sql>SELECT CURRENT_ROLE;
+--------------+
| single_value |
+==============+
| monetdb |
+--------------+
1 tuple (0.280ms)
sql>
sql>DROP ROLE r123;
operation successful (14.647ms)
sql>
sql>SELECT name FROM sys.auths;
+----------+
| name |
+==========+
| public |
| sysadmin |
| monetdb |
+----------+
3 tuples (1.759ms)
sql>SELECT CURRENT_ROLE;
+--------------+
| single_value |
+==============+
| monetdb |
+--------------+
1 tuple (0.321ms)
sql>
### Expected Results:
A successful setting/change of the current role.
## Comment 24517
Date: 2016-10-16 17:56:56 +0200
From: @njnes
See the Users/Role/schema tests for an example on how to create, grant and set role's. The errors may need some work, suggestions are welcome
| SET ROLE command does not work | https://api.github.com/repos/MonetDB/MonetDB/issues/6074/comments | 0 | 2020-11-30T15:25:05Z | 2024-06-27T12:56:38Z | https://github.com/MonetDB/MonetDB/issues/6074 | 753,570,636 | 6,074 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-10 16:23:46 +0200
From: @swingbit
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.23.7 (Jun2016-SP1)
CC: @mlkersten
Last updated: 2016-12-21 13:07:29 +0100
## Comment 24477
Date: 2016-10-10 16:23:46 +0200
From: @swingbit
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36
Build Identifier:
This is related to Bug #6072.
The output of this explain should be parsable in a MAL session, but it misses type information on a constant. Missing type information means that during parsing the type is guessed wrongly.
sql>set cache=false;
sql>\f raw
sql>explain select x.id from (select cast(id as double) as id from sys.functions) as x where x.id > 1;
% .explain table_name
% mal name
% clob type
% 61 length
function user.main():void;
barrier X_44 := language.dataflow();
X_20 := bat.new(nil:oid,nil:str);
X_28 := bat.append(X_20,"sys.x");
X_23 := bat.new(nil:oid,nil:str);
X_30 := bat.append(X_23,"id");
X_24 := bat.new(nil:oid,nil:str);
X_31 := bat.append(X_24,"double");
X_25 := bat.new(nil:oid,nil:int);
X_33 := bat.append(X_25,53);
X_27 := bat.new(nil:oid,nil:int);
X_35 := bat.append(X_27,0);
X_1 := sql.mvc();
X_5:bat[:int] := sql.bind(X_1,"sys","functions","id",0);
(C_8,r1_8) := sql.bind(X_1,"sys","functions","id",2);
X_11:bat[:int] := sql.bind(X_1,"sys","functions","id",1);
X_13 := sql.delta(X_5,C_8,r1_8,X_11);
X_14 := batcalc.dbl(X_13);
C_2:bat[:oid] := sql.tid(X_1,"sys","functions");
C_16 := algebra.thetasubselect(X_14,C_2,1,">");
X_18 := algebra.projection(C_16,X_14);
language.pass(X_14);
exit X_44;
sql.resultSet(X_28,X_30,X_31,X_33,X_35,X_18);
end user.main;
From here, we can already see that C_16 will fail, because X_14 is :bat[:dbl] and the constant is 1, which means 1:int
Here's the MAL session:
mal>sql.init();
mal>function user.main():void;
mal>barrier X_44 := language.dataflow();
mal> X_20 := bat.new(nil:oid,nil:str);
mal> X_28 := bat.append(X_20,"sys.x");
mal> X_23 := bat.new(nil:oid,nil:str);
mal> X_30 := bat.append(X_23,"id");
mal> X_24 := bat.new(nil:oid,nil:str);
mal> X_31 := bat.append(X_24,"double");
mal> X_25 := bat.new(nil:oid,nil:int);
mal> X_33 := bat.append(X_25,53);
mal> X_27 := bat.new(nil:oid,nil:int);
mal> X_35 := bat.append(X_27,0);
mal> X_1 := sql.mvc();
mal> X_5:bat[:int] := sql.bind(X_1,"sys","functions","id",0);
mal> (C_8,r1_8:bat[:int]) := sql.bind(X_1,"sys","functions","id",2);
mal> X_11:bat[:int] := sql.bind(X_1,"sys","functions","id",1);
mal> X_13 := sql.delta(X_5,C_8,r1_8,X_11);
mal> X_14 := batcalc.dbl(X_13);
mal> C_2:bat[:oid] := sql.tid(X_1,"sys","functions");
mal> C_16 := algebra.thetasubselect(X_14,C_2,1,">");
mal> X_18 := algebra.projection(C_16,X_14);
mal> language.pass(X_14);
mal>exit X_44;
mal> sql.resultSet(X_28,X_30,X_31,X_33,X_35,X_18);
mal>end user.main;
MAPI = (monetdb) /tmp/.s.monetdb.54500
QUERY = end user.main;
ERROR = !TypeException:user.main[19]:'algebra.thetasubselect' undefined in: C_16:any := algebra.thetasubselect(X_14:bat[:dbl],C_2:bat[:oid],1:int,">":str);
mal>
Indeed, constant 1 is re-parsed as i:int, when it was meant to be 1:dbl.
Notice that this is visible only when setting cache=false. Otherwise, the constant would be turned into a (correctly typed) function parameter A0:dbl.
Reproducible: Always
## Comment 24478
Date: 2016-10-11 19:28:18 +0200
From: @mlkersten
Fixed in default branch
## Comment 24479
Date: 2016-10-11 19:28:42 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [2539534aa3d1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2539534aa3d1) made by Martin Kersten <mk@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2539534aa3d1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2539534aa3d1)
Changeset description:
Fixing bug #6073
## Comment 24532
Date: 2016-10-18 11:51:17 +0200
From: @swingbit
I need to reopen it, because the fix was meant for Bug #6072 (which can be closed), not for this one.
## Comment 24633
Date: 2016-10-26 23:32:09 +0200
From: @mlkersten
Re-parsing the MAL output also requires that the signatures of the SQL parts are known. This requires importing their signature files, e.g. include sql;
Furthermore, a SQL environment should be set up to enable their execution.
## Comment 24648
Date: 2016-11-03 11:10:08 +0100
From: @swingbit
Martin, perhaps I'm not understanding well your last suggestion.
I used
include sql;
sql.init();
before defining the function, but that doesn't fix it.
Did you mean something different?
My impression is that constants are always printed with no type information.
Then type is guessed during parsing, but can fail (here, it should be 1:dbl but it is guessed as 1:int).
mal>include sql;
mal>sql.init();
mal>function user.main():void;
mal>barrier X_44 := language.dataflow();
mal> X_20 := bat.new(nil:oid,nil:str);
mal> X_28 := bat.append(X_20,"sys.x");
mal> X_23 := bat.new(nil:oid,nil:str);
mal> X_30 := bat.append(X_23,"id");
mal> X_24 := bat.new(nil:oid,nil:str);
mal> X_31 := bat.append(X_24,"double");
mal> X_25 := bat.new(nil:oid,nil:int);
mal> X_33 := bat.append(X_25,53);
mal> X_27 := bat.new(nil:oid,nil:int);
mal> X_35 := bat.append(X_27,0);
mal> X_1 := sql.mvc();
mal> X_5:bat[:int] := sql.bind(X_1,"sys","functions","id",0);
mal> (C_8,r1_8:bat[:int]) := sql.bind(X_1,"sys","functions","id",2);
mal> X_11:bat[:int] := sql.bind(X_1,"sys","functions","id",1);
mal> X_13 := sql.delta(X_5,C_8,r1_8,X_11);
mal> X_14 := batcalc.dbl(X_13);
mal> C_2:bat[:oid] := sql.tid(X_1,"sys","functions");
mal> C_16 := algebra.thetasubselect(X_14,C_2,1,">");
mal> X_18 := algebra.projection(C_16,X_14);
mal> language.pass(X_14);
mal>exit X_44;
mal> sql.resultSet(X_28,X_30,X_31,X_33,X_35,X_18);
mal>end user.main;
MAPI = (monetdb) /tmp/.s.monetdb.54500
QUERY = end user.main;
ERROR = !TypeException:user.main[19]:'algebra.thetasubselect' undefined in: C_16:any := algebra.thetasubselect(X_14:bat[:dbl],C_2:bat[:oid],1:int,">":str);
## Comment 24683
Date: 2016-11-13 23:21:35 +0100
From: @mlkersten
You are right. It is better to keep the type name around as well in most cases.
Enhanced the mal_listing routine to show it.
| Missing type information for constants in MAL explain | https://api.github.com/repos/MonetDB/MonetDB/issues/6073/comments | 0 | 2020-11-30T15:25:02Z | 2024-06-27T12:56:37Z | https://github.com/MonetDB/MonetDB/issues/6073 | 753,570,582 | 6,073 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-10 15:47:32 +0200
From: @swingbit
To: SQL devs <<bugs-sql>>
Version: 11.23.7 (Jun2016-SP1)
CC: martin.van.dinther, @njnes, qehy, sagarharish999, shawpolakcrax12, shery41, zihu
Last updated: 2020-11-26 15:31:54 +0100
## Comment 24476
Date: 2016-10-10 15:47:32 +0200
From: @swingbit
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36
Build Identifier:
* Got the explain of a trivial query:
sql>\f raw
sql>explain select name from sys.functions;
% .explain table_name
% mal name
% clob type
% 94 length
function user.s4_1():void;
X_32:void := querylog.define("explain select name from sys.functions;","default_pipe",21);
X_16 := bat.new(nil:oid,nil:str);
X_24 := bat.append(X_16,"sys.functions");
X_19 := bat.new(nil:oid,nil:str);
X_26 := bat.append(X_19,"name");
X_20 := bat.new(nil:oid,nil:str);
X_27 := bat.append(X_20,"varchar");
X_21 := bat.new(nil:oid,nil:int);
X_29 := bat.append(X_21,256);
X_23 := bat.new(nil:oid,nil:int);
X_31 := bat.append(X_23,0);
X_1 := sql.mvc();
C_2:bat[:oid] := sql.tid(X_1,"sys","functions");
X_5:bat[:str] := sql.bind(X_1,"sys","functions","name",0);
(C_8,r1_8) := sql.bind(X_1,"sys","functions","name",2);
X_11:bat[:str] := sql.bind(X_1,"sys","functions","name",1);
X_13 := sql.delta(X_5,C_8,r1_8,X_11);
X_14 := algebra.projection(C_2,X_13);
sql.resultSet(X_24,X_26,X_27,X_29,X_31,X_14);
end user.s4_1;
optimizer.mitosis()
optimizer.dataflow()
* Opened a MAL session, initialized sql, and pasted the function above:
mal>sql.init();
mal>function user.s4_1():void;
mal> X_32:void := querylog.define("explain select name from sys.functions;","default_pipe",21);
mal> X_16 := bat.new(nil:oid,nil:str);
mal> X_24 := bat.append(X_16,"sys.functions");
mal> X_19 := bat.new(nil:oid,nil:str);
mal> X_26 := bat.append(X_19,"name");
mal> X_20 := bat.new(nil:oid,nil:str);
mal> X_27 := bat.append(X_20,"varchar");
mal> X_21 := bat.new(nil:oid,nil:int);
mal> X_29 := bat.append(X_21,256);
mal> X_23 := bat.new(nil:oid,nil:int);
mal> X_31 := bat.append(X_23,0);
mal> X_1 := sql.mvc();
mal> C_2:bat[:oid] := sql.tid(X_1,"sys","functions");
mal> X_5:bat[:str] := sql.bind(X_1,"sys","functions","name",0);
mal> (C_8,r1_8) := sql.bind(X_1,"sys","functions","name",2);
mal> X_11:bat[:str] := sql.bind(X_1,"sys","functions","name",1);
mal> X_13 := sql.delta(X_5,C_8,r1_8,X_11);
mal> X_14 := algebra.projection(C_2,X_13);
mal> sql.resultSet(X_24,X_26,X_27,X_29,X_31,X_14);
mal>end user.s4_1;
MAPI = (monetdb) /tmp/.s.monetdb.54500
QUERY = end user.s4_1;
ERROR = !TypeException:user.s4_1[17]:'sql.delta' undefined in: X_13:any := sql.delta(X_5:bat[:str],C_8:bat[:oid],r1_8:bat[:any],X_11:bat[:str]);
mal>
The error is easy to find: sql.delta() expects r1_8 to be of type :bat[:str], but it gets :bat[:any] instead.
* If I fix it manually:
mal>function user.s4_1():void;
mal> X_32:void := querylog.define("explain select name from sys.functions;","default_pipe",21);
mal> X_16 := bat.new(nil:oid,nil:str);
mal> X_24 := bat.append(X_16,"sys.functions");
mal> X_19 := bat.new(nil:oid,nil:str);
mal> X_26 := bat.append(X_19,"name");
mal> X_20 := bat.new(nil:oid,nil:str);
mal> X_27 := bat.append(X_20,"varchar");
mal> X_21 := bat.new(nil:oid,nil:int);
mal> X_29 := bat.append(X_21,256);
mal> X_23 := bat.new(nil:oid,nil:int);
mal> X_31 := bat.append(X_23,0);
mal> X_1 := sql.mvc();
mal> C_2:bat[:oid] := sql.tid(X_1,"sys","functions");
mal> X_5:bat[:str] := sql.bind(X_1,"sys","functions","name",0);
mal> (C_8,r1_8:bat[:str]) := sql.bind(X_1,"sys","functions","name",2);
mal> X_11:bat[:str] := sql.bind(X_1,"sys","functions","name",1);
mal> X_13 := sql.delta(X_5,C_8,r1_8,X_11);
mal> X_14 := algebra.projection(C_2,X_13);
mal> sql.resultSet(X_24,X_26,X_27,X_29,X_31,X_14);
mal>end user.s4_1;
mal>
This works.
I am not sure whether the issue is only in how the type information is displayed by EXPLAIN, or if really isn't computed correctly.
Reproducible: Always
## Comment 24551
Date: 2016-10-19 14:30:05 +0200
From: @njnes
backported fix to Jun2016
| Bind to UPD delta column does not get/show type information in EXPLAIN | https://api.github.com/repos/MonetDB/MonetDB/issues/6072/comments | 0 | 2020-11-30T15:24:59Z | 2024-06-27T12:56:36Z | https://github.com/MonetDB/MonetDB/issues/6072 | 753,570,541 | 6,072 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-10 12:22:51 +0200
From: @bartscheers
To: SQL devs <<bugs-sql>>
Version: 11.23.7 (Jun2016-SP1)
CC: @njnes
Last updated: 2016-12-21 13:07:41 +0100
## Comment 24472
Date: 2016-10-10 12:22:51 +0200
From: @bartscheers
Created attachment 472
csv file with the data
Join two select queries, using a where clause from two different columns, fails when cast and floor is used.
> Attached file: [cat7and5.csv](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6071_cat7and5.csv_472) (text/csv, 45226 bytes)
> Description: csv file with the data
## Comment 24473
Date: 2016-10-10 12:23:46 +0200
From: @bartscheers
Created attachment 473
table definition
> Attached file: [create.catsrc.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6071_create.catsrc.sql_473) (application/sql, 191 bytes)
> Description: table definition
## Comment 24474
Date: 2016-10-10 12:24:18 +0200
From: @bartscheers
Created attachment 474
copy into to load the data
> Attached file: [load.catsrc.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6071_load.catsrc.sql_474) (application/sql, 82 bytes)
> Description: copy into to load the data
## Comment 24475
Date: 2016-10-10 12:25:23 +0200
From: @bartscheers
Created attachment 475
the buggy query
When uncommenting the clause around c2.zone, the query crashes the server
> Attached file: [bug_query.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6071_bug_query.sql_475) (application/sql, 1235 bytes)
> Description: the buggy query
## Comment 24481
Date: 2016-10-12 14:24:14 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [2ceeb49da970](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2ceeb49da970) 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=2ceeb49da970](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2ceeb49da970)
Changeset description:
Avoid division by zero.
This fixes bug #6071.
## Comment 24484
Date: 2016-10-12 19:00:57 +0200
From: @njnes
was fixed by sjoerd. Added a test for this
| where clause with cast and floor fails to sigsegv | https://api.github.com/repos/MonetDB/MonetDB/issues/6071/comments | 0 | 2020-11-30T15:24:56Z | 2024-06-27T12:56:35Z | https://github.com/MonetDB/MonetDB/issues/6071 | 753,570,509 | 6,071 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-06 17:48:39 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.23.7 (Jun2016-SP1)
CC: @mlkersten
Last updated: 2016-12-21 13:07:12 +0100
## Comment 24467
Date: 2016-10-06 17:48:39 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0
Build Identifier:
call "sys"."settimeout"(-9) is allowed currently but it should not be allowed.
Also it immediately results in a situation where every send SQL results in a
Error: Query aborted due to timeout
This makes the session useless for the application/user. This should not be possible.
Reproducible: Always
### Steps to Reproduce:
1. Start mserver5
2. Start mclient
3. Execute SQL queries:
SELECT "querytimeout" FROM "sys"."sessions"() WHERE "active";
CALL "sys"."settimeout"(9);
SELECT "querytimeout" FROM "sys"."sessions"() WHERE "active";
CALL "sys"."settimeout"(0);
SELECT "querytimeout" FROM "sys"."sessions"() WHERE "active";
CALL "sys"."settimeout"(-9);
SELECT "querytimeout" FROM "sys"."sessions"() WHERE "active";
### Actual Results:
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.24.0 (unreleased), 'demo'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>SELECT "querytimeout" FROM "sys"."sessions"() WHERE "active";
+--------------+
| querytimeout |
+==============+
| 0 |
+--------------+
1 tuple (1.189ms)
sql>
sql>CALL "sys"."settimeout"(9);
sql>SELECT "querytimeout" FROM "sys"."sessions"() WHERE "active";
+--------------+
| querytimeout |
+==============+
| 9 |
+--------------+
1 tuple (0.966ms)
sql>
sql>CALL "sys"."settimeout"(0);
sql>SELECT "querytimeout" FROM "sys"."sessions"() WHERE "active";
+--------------+
| querytimeout |
+==============+
| 0 |
+--------------+
1 tuple (0.802ms)
sql>
sql>CALL "sys"."settimeout"(-9);
Query aborted due to timeout
sql>SELECT "querytimeout" FROM "sys"."sessions"() WHERE "active";
Query aborted due to timeout
sql>
### Expected Results:
error msg "Illegal timeout value: -9" after: CALL "sys"."settimeout"(-9);
No setting or change of the querytimeout parameter of the current session, such that successive SQL statements are executed normally.
Potentially also
CALL "sys"."settimeout"(9, -10);
and
CALL "sys"."setsession"(-9);
should be protected against calling negative session timeouts.
## Comment 24468
Date: 2016-10-06 18:05:10 +0200
From: @mlkersten
I patched the default branch to protect against it.
## Comment 24469
Date: 2016-10-06 18:07:01 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [ba5ba134b9e2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ba5ba134b9e2) 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=ba5ba134b9e2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ba5ba134b9e2)
Changeset description:
Add test for bug #6070
## Comment 24470
Date: 2016-10-06 18:08:29 +0200
From: Martin van Dinther <<martin.van.dinther>>
The procedures:
-- control the query and session time out
create procedure sys.settimeout("query" bigint)
external name sql.settimeout;
create procedure sys.settimeout("query" bigint, "session" bigint)
external name sql.settimeout;
create procedure sys.setsession("timeout" bigint)
external name sql.setsession;
are created in file: 22_clients.sql
| setting negative session query timeout should not be possible/allowed | https://api.github.com/repos/MonetDB/MonetDB/issues/6070/comments | 0 | 2020-11-30T15:24:53Z | 2024-06-27T12:56:34Z | https://github.com/MonetDB/MonetDB/issues/6070 | 753,570,471 | 6,070 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-05 18:22:51 +0200
From: muesli4
To: SQL devs <<bugs-sql>>
Version: 11.23.7 (Jun2016-SP1)
CC: @njnes
Last updated: 2016-12-21 13:07:43 +0100
## Comment 24461
Date: 2016-10-05 18:22:51 +0200
From: muesli4
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0
Build Identifier:
The following query fails silently:
WITH t1(x) AS (
SELECT 0
FROM (values (0)) as v(x)
), t2(x) AS (
SELECT 0
FROM ( SELECT 0, 0, 0, 0, 0, 0, 0
UNION ALL
SELECT 1, 0, 0, 0, 0, 0, 0
) AS a23(x1, x2, x3, x4, x5, x6, x7)
)
SELECT 0 FROM t1, t2;
Reproducible: Always
### Steps to Reproduce:
1. Run the query.
2. Wonder that there is no output.
### Actual Results:
None.
### Expected Results:
There should be a result with cardinality 2.
It seems somehow related to the projection lists within the UNION ALL: Whenever I remove one of the zeroes (or change the 1 to a 0), the expected result appears.
Revision: http://dev.monetdb.org/hg/MonetDB/rev/08b99a61d03c
## Comment 24462
Date: 2016-10-05 18:23:52 +0200
From: muesli4
Created attachment 471
A reduced example showing the bug.
> Attached file: [bug3.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6069_bug3.sql_471) (application/sql, 289 bytes)
> Description: A reduced example showing the bug.
## Comment 24480
Date: 2016-10-11 20:04:21 +0200
From: muesli4
One thing I noticed, is that it only happens, when the amount of columns doesn't match with those specified in the schema in the from clause, but only if there are more than 6 columns. The following fails:
select 0 from (select 0, 0, 0, 0, 0, 0, 0 union all select 1, 0, 0, 0, 0, 0, 0) as t(a, b, c, d, e, f, g), (values (0)) as v(x);
While this query is perfectly fine:
select 0 from (select 0, 0, 0, 0, 0, 0 union all select 1, 0, 0, 0, 0, 0) as t(a, b, c, d, e, f), (values (0)) as v(x);
This is what the log file says for the already posted snippet:
2016-10-11 19:59:19 ERR test[7024]: could not find L17.L17
2016-10-11 19:59:19 ERR test[7024]: L10.L10
2016-10-11 19:59:19 ERR test[7024]: L11.L11
2016-10-11 19:59:19 ERR test[7024]: L12.L12
2016-10-11 19:59:19 ERR test[7024]: L13.L13
2016-10-11 19:59:19 ERR test[7024]: L14.L14
2016-10-11 19:59:19 ERR test[7024]: L15.L15
2016-10-11 19:59:19 ERR test[7024]: L16.L10
2016-10-11 19:59:19 ERR test[7024]: L16.L11
2016-10-11 19:59:19 ERR test[7024]: L16.L12
2016-10-11 19:59:19 ERR test[7024]: L16.L13
2016-10-11 19:59:19 ERR test[7024]: L16.L14
2016-10-11 19:59:19 ERR test[7024]: L16.L15
## Comment 24482
Date: 2016-10-12 18:57:21 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [8d48879598e2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=8d48879598e2) 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=8d48879598e2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=8d48879598e2)
Changeset description:
created simple fix for bug #6069, but lots of tests got new output (ie L.. changes)
## Comment 24483
Date: 2016-10-12 18:59:55 +0200
From: @njnes
resolved by properly naming al expressions
## Comment 24485
Date: 2016-10-12 19:02:45 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [3b06c3df35f7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=3b06c3df35f7) 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=3b06c3df35f7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=3b06c3df35f7)
Changeset description:
added test for bug #6069
| query with union all silently crashes | https://api.github.com/repos/MonetDB/MonetDB/issues/6069/comments | 0 | 2020-11-30T15:24:51Z | 2024-06-27T12:56:33Z | https://github.com/MonetDB/MonetDB/issues/6069 | 753,570,446 | 6,069 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-05 13:38:50 +0200
From: @eyalroz
To: Merovingian devs <<bugs-merovingian>>
Version: 11.23.7 (Jun2016-SP1)
Last updated: 2016-12-21 13:07:58 +0100
## Comment 24457
Date: 2016-10-05 13:38:50 +0200
From: @eyalroz
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0
Build Identifier:
I suggest the following:
diff -r [6dfd8ffb7ab2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=6dfd8ffb7ab2) gdk/gdk_bbp.c
--- a/gdk/gdk_bbp.c Wed Oct 05 12:38:10 2016 +0200
+++ b/gdk/gdk_bbp.c Wed Oct 05 13:37:01 2016 +0200
@@ -1210,7 +1210,10 @@
bbpversion != GDKLIBRARY_OLDWKB &&
bbpversion != GDKLIBRARY_INSERTED &&
bbpversion != GDKLIBRARY_HEADED) {
- GDKfatal("BBPinit: incompatible BBP version: expected 0%o, got 0%o.", GDKLIBRARY, bbpversion);
+ GDKfatal("BBPinit: incompatible BBP version: expected 0%o, got 0%o. "
+ "Database was likely created by a newer release or a development "
+ "version of the server, using an incompatible storage format." ,
+ GDKLIBRARY, bbpversion);
}
if (fgets(buf, sizeof(buf), fp) == NULL) {
GDKfatal("BBPinit: short BBP");
or an alternative wording of the error message which would be clear to people who do not know what the BBP version means.
Reproducible: Always
## Comment 24531
Date: 2016-10-18 11:47:12 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [88921c8c1d79](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=88921c8c1d79) 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=88921c8c1d79](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=88921c8c1d79)
Changeset description:
Elaborated error message for incompatible database version.
This fixes bug #6068.
| Error message about incompatible BBP version should be clearer | https://api.github.com/repos/MonetDB/MonetDB/issues/6068/comments | 0 | 2020-11-30T15:24:48Z | 2024-06-27T12:56:32Z | https://github.com/MonetDB/MonetDB/issues/6068 | 753,570,405 | 6,068 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-05 13:25:48 +0200
From: @eyalroz
To: Merovingian devs <<bugs-merovingian>>
Version: 11.23.7 (Jun2016-SP1)
CC: renalkoclok
Last updated: 2020-06-03 09:18:30 +0200
## Comment 24456
Date: 2016-10-05 13:25:48 +0200
From: @eyalroz
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0
Build Identifier:
Today I mistakenly tried to load a DB created by a newer (non-released) version of MonetDB, which failed because the file formats version (BBP) had changed. But - that's not why I'm reporting this issue. The point is that monetdbd told me:
monetdbd: internal error while starting mserver 'database 'tpch-sf-1' appears to shut itself down after starting, check monetdbd's logfile for possible hints', please refer to the logs
These are two messages about the same issue and there's some redundancy; but that's not much of an issue. monetdbd should have told me something like
please refer to /path/to/dbfarm/merovingian.log on host sofia.da.cwi.nl
now, inside the merovingian.log, I see:
2016-10-05 13:12:14 MSG merovingian[21034]: starting database 'tpch-sf-1', up min/avg/max: 0s/1w/4w, crash average: 0.00 0.30 0.13 (11-7=4)
2016-10-05 13:12:14 MSG tpch-sf-1[21047]: arguments: /ufs/eyalroz/opt/monetdb/bin/mserver5 --dbpath=/ufs/eyalroz/dbfarms/monetdb/tpch-sf-1 --set merovingian_uri=mapi:monetdb://sofia.da.cwi.nl:50000/tpch-sf-1 --set mapi_open=false --set mapi_port=0 --set mapi_usock=/ufs/eyalroz/dbfarms/monetdb/tpch-sf-1/.mapi.sock --set monet_vault_key=/ufs/eyalroz/dbfarms/monetdb/tpch-sf-1/.vaultkey --set gdk_nr_threads=1 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes
2016-10-05 13:12:14 MSG merovingian[21034]: database 'tpch-sf-1' (21047) has exited with exit status 1
2016-10-05 13:12:14 ERR control[21034]: !monetdbd: an internal error has occurred 'database 'tpch-sf-1' appears to shut itself down after starting, check monetdbd's logfile for possible hints'
2016-10-05 13:12:14 ERR merovingian[21034]: client error: database 'tpch-sf-1' appears to shut itself down after starting, check monetdbd's logfile for possible hints
2016-10-05 13:12:14 MSG merovingian[21034]: starting database 'tpch-sf-1', up min/avg/max: 0s/1w/4w, crash average: 0.00 0.30 0.13 (11-7=4)
2016-10-05 13:12:14 MSG tpch-sf-1[21049]: arguments: /ufs/eyalroz/opt/monetdb/bin/mserver5 --dbpath=/ufs/eyalroz/dbfarms/monetdb/tpch-sf-1 --set merovingian_uri=mapi:monetdb://sofia.da.cwi.nl:50000/tpch-sf-1 --set mapi_open=false --set mapi_port=0 --set mapi_usock=/ufs/eyalroz/dbfarms/monetdb/tpch-sf-1/.mapi.sock --set monet_vault_key=/ufs/eyalroz/dbfarms/monetdb/tpch-sf-1/.vaultkey --set gdk_nr_threads=1 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes
2016-10-05 13:12:14 MSG merovingian[21034]: database 'tpch-sf-1' (21049) has exited with exit status 1
2016-10-05 13:12:14 ERR control[21034]: !monetdbd: an internal error has occurred 'database 'tpch-sf-1' appears to shut itself down after starting, check monetdbd's logfile for possible hints'
2016-10-05 13:12:19 ERR merovingian[21034]: client error: database 'tpch-sf-1' appears to shut itself down after starting, check monetdbd's logfile for possible hints
again, ignoring redundancies, I don't get the actual error, but am again referred to some log file. It does not tell me which (I actually suspect the error does not appear in any log file); and I expect either a message such as the earlier one, referring to that supposed second file, or alternatively, the actual error message(s), which in my case were:
!FATAL: BBPinit: incompatible BBP version: expected 061033, got 061034.
but I only got it by running mserver5 myself, not by looking at the log files.
Reproducible: Always
## Comment 24965
Date: 2017-02-03 15:46:42 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [bd6c6a094340](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=bd6c6a094340) 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=bd6c6a094340](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bd6c6a094340)
Changeset description:
Mention name of logfile in message telling user to look in the logfile.
Also don't mention that the user should look in the logfile twice
(using a simple heuristic: if the message from monetdbd contains the
string "logfile", monetdb doesn't add a reference to the logfile).
This should fix at least part of bug #6067.
## Comment 24966
Date: 2017-02-03 15:49:26 +0100
From: @sjoerdmullender
When I try to replay the scenario, I do see a message about incompatible version numbers in the log file.
I fixed monetdbd to add the name of the logfile to the message it produces (note, it gives the value of the logfile property, which may be a relative path name) and I fixed monetdb to not add the message "please refer to the logfile" if the logfile was already mentioned in the message that it got from monetdbd.
## Comment 24973
Date: 2017-02-04 18:29:13 +0100
From: @eyalroz
(In reply to Sjoerd Mullender from comment 2)
> When I try to replay the scenario, I do see a message about incompatible
> version numbers in the log file.
Panos just told me the other day he sometimes experiences log messages being dropped - not appearing in merovingian.log for some reason - and that this has made him always debug by running mserver5 directly.
> I fixed monetdbd to add the name of the logfile to the message it produces
> (note, it gives the value of the logfile property, which may be a relative
> path name)
Relative to where? If it's relative to the CWD of the mserver5 process, maybe it's worth the trouble of printing that as well.
## Comment 27774
Date: 2020-06-03 09:18:30 +0200
From: @sjoerdmullender
The content of attachment 675 has been deleted for the following reason:
spam
| Error messages referring to logs should say which logs | https://api.github.com/repos/MonetDB/MonetDB/issues/6067/comments | 0 | 2020-11-30T15:24:45Z | 2024-06-28T07:07:23Z | https://github.com/MonetDB/MonetDB/issues/6067 | 753,570,387 | 6,067 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-05 11:25:29 +0200
From: @eyalroz
To: Merovingian devs <<bugs-merovingian>>
Version: 11.23.7 (Jun2016-SP1)
Last updated: 2018-08-31 17:20:15 +0200
## Comment 24454
Date: 2016-10-05 11:25:29 +0200
From: @eyalroz
Console log with the bug manifesting:
[eyalroz@sofia ~]$ monetdbd stop $DB_FARM
[eyalroz@sofia ~]$ monetdbd get port $DB_FARM
property value
port 50002
[eyalroz@sofia ~]$ monetdbd set port=50000 $DB_FARM
sending SIGHUP to monetdbd[21783] failed: No such process
so, monetdbd was trying to SIGHUP a db-farm-specific process which does not exist, as though it had "missed" the fact that I'd stopped the farm earlier.
## Comment 24967
Date: 2017-02-03 16:01:46 +0100
From: @sjoerdmullender
Is this still a problem? I can't reproduce it.
I did fix a problem (changesets [c786801bc515](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c786801bc515) and 8611d7d02523) where monetdbd was killed too quickly after a stop was initiated, and if that happens, the file containing the pid is left behind, meaning that the next interaction with monetdbd thinks there is still a daemon running.
| monetdbd tries to SIGHUP another, non-existing monetdbd process | https://api.github.com/repos/MonetDB/MonetDB/issues/6066/comments | 0 | 2020-11-30T15:24:42Z | 2024-06-27T12:56:30Z | https://github.com/MonetDB/MonetDB/issues/6066 | 753,570,343 | 6,066 |
[
"MonetDB",
"MonetDB"
] | Date: 2016-10-03 19:41:53 +0200
From: muesli4
To: SQL devs <<bugs-sql>>
Version: 11.23.7 (Jun2016-SP1)
CC: @njnes
Last updated: 2016-10-13 10:04:21 +0200
## Comment 24450
Date: 2016-10-03 19:41:53 +0200
From: muesli4
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0
Build Identifier:
Run this query:
WITH t0(so) AS (
SELECT ROW_NUMBER() OVER (ORDER BY v0 ASC) AS so
FROM (values (0)) as t(v0)
)
SELECT 1 AS k1, a3.so AS k2
FROM t0 AS a3
UNION ALL
SELECT 2 AS k2, a8.so AS k2
FROM t0 AS a8;
Executing the query results in the following error message (somehow the types of the append from the *union all* don't match):
TypeException:user.s2_1[23]:'bat.append' undefined in: bat.append(X_38:bat[:int],X_34:bat[:bte],true:bit);
Reproducible: Always
revision: http://dev.monetdb.org/hg/MonetDB/rev/5e7df26ea650
## Comment 24451
Date: 2016-10-03 19:42:32 +0200
From: muesli4
Created attachment 470
The problematic query
> Attached file: [test.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_6065_test.sql_470) (application/sql, 212 bytes)
> Description: The problematic query
## Comment 24453
Date: 2016-10-05 10:03:40 +0200
From: @njnes
added missing checks for duplicate names.
## Comment 24455
Date: 2016-10-05 12:59:49 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [e5e5c8649705](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e5e5c8649705) 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=e5e5c8649705](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e5e5c8649705)
Changeset description:
add test for bug #6065
## Comment 24458
Date: 2016-10-05 14:58:21 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [a2ba71b00ff7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a2ba71b00ff7) 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=a2ba71b00ff7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a2ba71b00ff7)
Changeset description:
fixes for bug #6065
## Comment 24497
Date: 2016-10-13 10:04:21 +0200
From: @sjoerdmullender
Jun2016-SP2 has been released.
| CTE with row number and union fails within MAL | https://api.github.com/repos/MonetDB/MonetDB/issues/6065/comments | 0 | 2020-11-30T15:24:39Z | 2024-06-27T12:56:29Z | https://github.com/MonetDB/MonetDB/issues/6065 | 753,570,297 | 6,065 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6064/comments | 0 | 2020-11-30T15:24:36Z | 2020-11-30T15:24:38Z | https://github.com/MonetDB/MonetDB/issues/6064 | 753,570,255 | 6,064 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6063/comments | 0 | 2020-11-30T15:24:34Z | 2020-11-30T15:24:35Z | https://github.com/MonetDB/MonetDB/issues/6063 | 753,570,215 | 6,063 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6062/comments | 0 | 2020-11-30T15:24:31Z | 2020-11-30T15:24:33Z | https://github.com/MonetDB/MonetDB/issues/6062 | 753,570,186 | 6,062 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6061/comments | 0 | 2020-11-30T15:24:29Z | 2020-11-30T15:24:30Z | https://github.com/MonetDB/MonetDB/issues/6061 | 753,570,144 | 6,061 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6060/comments | 0 | 2020-11-30T15:24:26Z | 2020-11-30T15:24:28Z | https://github.com/MonetDB/MonetDB/issues/6060 | 753,570,119 | 6,060 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6059/comments | 0 | 2020-11-30T15:24:24Z | 2020-11-30T15:24:25Z | https://github.com/MonetDB/MonetDB/issues/6059 | 753,570,088 | 6,059 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6058/comments | 0 | 2020-11-30T15:24:22Z | 2020-11-30T15:24:23Z | https://github.com/MonetDB/MonetDB/issues/6058 | 753,570,051 | 6,058 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6057/comments | 0 | 2020-11-30T15:24:18Z | 2020-11-30T15:24:20Z | https://github.com/MonetDB/MonetDB/issues/6057 | 753,570,007 | 6,057 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6056/comments | 0 | 2020-11-30T15:24:16Z | 2020-11-30T15:24:17Z | https://github.com/MonetDB/MonetDB/issues/6056 | 753,569,971 | 6,056 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6055/comments | 0 | 2020-11-30T15:24:13Z | 2020-11-30T15:24:15Z | https://github.com/MonetDB/MonetDB/issues/6055 | 753,569,941 | 6,055 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6054/comments | 0 | 2020-11-30T15:24:10Z | 2020-11-30T15:24:13Z | https://github.com/MonetDB/MonetDB/issues/6054 | 753,569,894 | 6,054 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6053/comments | 0 | 2020-11-30T15:24:09Z | 2020-11-30T15:24:10Z | https://github.com/MonetDB/MonetDB/issues/6053 | 753,569,873 | 6,053 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6052/comments | 0 | 2020-11-30T15:24:06Z | 2020-11-30T15:24:08Z | https://github.com/MonetDB/MonetDB/issues/6052 | 753,569,837 | 6,052 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6051/comments | 0 | 2020-11-30T15:24:03Z | 2020-11-30T15:24:05Z | https://github.com/MonetDB/MonetDB/issues/6051 | 753,569,795 | 6,051 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6050/comments | 0 | 2020-11-30T15:24:01Z | 2020-11-30T15:24:03Z | https://github.com/MonetDB/MonetDB/issues/6050 | 753,569,763 | 6,050 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6049/comments | 0 | 2020-11-30T15:23:59Z | 2020-11-30T15:24:01Z | https://github.com/MonetDB/MonetDB/issues/6049 | 753,569,726 | 6,049 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6048/comments | 0 | 2020-11-30T15:23:57Z | 2020-11-30T15:23:58Z | https://github.com/MonetDB/MonetDB/issues/6048 | 753,569,701 | 6,048 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6047/comments | 0 | 2020-11-30T15:23:54Z | 2020-11-30T15:23:56Z | https://github.com/MonetDB/MonetDB/issues/6047 | 753,569,669 | 6,047 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6046/comments | 0 | 2020-11-30T15:23:52Z | 2020-11-30T15:23:54Z | https://github.com/MonetDB/MonetDB/issues/6046 | 753,569,639 | 6,046 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6045/comments | 0 | 2020-11-30T15:23:50Z | 2020-11-30T15:23:51Z | https://github.com/MonetDB/MonetDB/issues/6045 | 753,569,603 | 6,045 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6044/comments | 0 | 2020-11-30T15:23:48Z | 2020-11-30T15:23:49Z | https://github.com/MonetDB/MonetDB/issues/6044 | 753,569,580 | 6,044 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6043/comments | 0 | 2020-11-30T15:23:45Z | 2020-11-30T15:23:47Z | https://github.com/MonetDB/MonetDB/issues/6043 | 753,569,549 | 6,043 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6042/comments | 0 | 2020-11-30T15:23:42Z | 2020-11-30T15:23:44Z | https://github.com/MonetDB/MonetDB/issues/6042 | 753,569,522 | 6,042 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6041/comments | 0 | 2020-11-30T15:23:40Z | 2020-11-30T15:23:42Z | https://github.com/MonetDB/MonetDB/issues/6041 | 753,569,491 | 6,041 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6040/comments | 0 | 2020-11-30T15:23:38Z | 2020-11-30T15:23:39Z | https://github.com/MonetDB/MonetDB/issues/6040 | 753,569,457 | 6,040 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6039/comments | 0 | 2020-11-30T15:23:36Z | 2020-11-30T15:23:37Z | https://github.com/MonetDB/MonetDB/issues/6039 | 753,569,429 | 6,039 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6038/comments | 0 | 2020-11-30T15:23:33Z | 2020-11-30T15:23:35Z | https://github.com/MonetDB/MonetDB/issues/6038 | 753,569,390 | 6,038 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6037/comments | 0 | 2020-11-30T15:23:30Z | 2020-11-30T15:23:31Z | https://github.com/MonetDB/MonetDB/issues/6037 | 753,569,344 | 6,037 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6036/comments | 0 | 2020-11-30T15:23:27Z | 2020-11-30T15:23:28Z | https://github.com/MonetDB/MonetDB/issues/6036 | 753,569,296 | 6,036 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6035/comments | 0 | 2020-11-30T15:23:24Z | 2020-11-30T15:23:26Z | https://github.com/MonetDB/MonetDB/issues/6035 | 753,569,251 | 6,035 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6034/comments | 0 | 2020-11-30T15:23:22Z | 2020-11-30T15:23:24Z | https://github.com/MonetDB/MonetDB/issues/6034 | 753,569,229 | 6,034 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6033/comments | 0 | 2020-11-30T15:23:20Z | 2020-11-30T15:23:22Z | https://github.com/MonetDB/MonetDB/issues/6033 | 753,569,188 | 6,033 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6032/comments | 0 | 2020-11-30T15:23:17Z | 2020-11-30T15:23:19Z | https://github.com/MonetDB/MonetDB/issues/6032 | 753,569,145 | 6,032 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6031/comments | 0 | 2020-11-30T15:23:14Z | 2020-11-30T15:23:16Z | https://github.com/MonetDB/MonetDB/issues/6031 | 753,569,108 | 6,031 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6030/comments | 0 | 2020-11-30T15:23:12Z | 2020-11-30T15:23:14Z | https://github.com/MonetDB/MonetDB/issues/6030 | 753,569,067 | 6,030 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6029/comments | 0 | 2020-11-30T15:23:10Z | 2020-11-30T15:23:11Z | https://github.com/MonetDB/MonetDB/issues/6029 | 753,569,033 | 6,029 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6028/comments | 0 | 2020-11-30T15:23:08Z | 2020-11-30T15:23:09Z | https://github.com/MonetDB/MonetDB/issues/6028 | 753,569,012 | 6,028 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6027/comments | 0 | 2020-11-30T15:23:06Z | 2020-11-30T15:23:07Z | https://github.com/MonetDB/MonetDB/issues/6027 | 753,568,991 | 6,027 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6026/comments | 0 | 2020-11-30T15:23:03Z | 2020-11-30T15:23:05Z | https://github.com/MonetDB/MonetDB/issues/6026 | 753,568,954 | 6,026 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6025/comments | 0 | 2020-11-30T15:23:01Z | 2020-11-30T15:23:02Z | https://github.com/MonetDB/MonetDB/issues/6025 | 753,568,927 | 6,025 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6024/comments | 0 | 2020-11-30T15:22:59Z | 2020-11-30T15:23:00Z | https://github.com/MonetDB/MonetDB/issues/6024 | 753,568,879 | 6,024 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6023/comments | 0 | 2020-11-30T15:22:57Z | 2020-11-30T15:22:58Z | https://github.com/MonetDB/MonetDB/issues/6023 | 753,568,857 | 6,023 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6022/comments | 0 | 2020-11-30T15:22:54Z | 2020-11-30T15:22:56Z | https://github.com/MonetDB/MonetDB/issues/6022 | 753,568,827 | 6,022 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6021/comments | 0 | 2020-11-30T15:22:52Z | 2020-11-30T15:22:54Z | https://github.com/MonetDB/MonetDB/issues/6021 | 753,568,811 | 6,021 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6020/comments | 0 | 2020-11-30T15:22:50Z | 2020-11-30T15:22:51Z | https://github.com/MonetDB/MonetDB/issues/6020 | 753,568,781 | 6,020 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6019/comments | 0 | 2020-11-30T15:22:48Z | 2020-11-30T15:22:49Z | https://github.com/MonetDB/MonetDB/issues/6019 | 753,568,743 | 6,019 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6018/comments | 0 | 2020-11-30T15:22:45Z | 2020-11-30T15:22:47Z | https://github.com/MonetDB/MonetDB/issues/6018 | 753,568,707 | 6,018 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6017/comments | 0 | 2020-11-30T15:22:43Z | 2020-11-30T15:22:44Z | https://github.com/MonetDB/MonetDB/issues/6017 | 753,568,678 | 6,017 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6016/comments | 0 | 2020-11-30T15:22:41Z | 2020-11-30T15:22:42Z | https://github.com/MonetDB/MonetDB/issues/6016 | 753,568,658 | 6,016 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6015/comments | 0 | 2020-11-30T15:22:39Z | 2020-11-30T15:22:40Z | https://github.com/MonetDB/MonetDB/issues/6015 | 753,568,621 | 6,015 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6014/comments | 0 | 2020-11-30T15:22:37Z | 2020-11-30T15:22:38Z | https://github.com/MonetDB/MonetDB/issues/6014 | 753,568,590 | 6,014 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6013/comments | 0 | 2020-11-30T15:22:34Z | 2020-11-30T15:22:36Z | https://github.com/MonetDB/MonetDB/issues/6013 | 753,568,553 | 6,013 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6012/comments | 0 | 2020-11-30T15:22:31Z | 2020-11-30T15:22:33Z | https://github.com/MonetDB/MonetDB/issues/6012 | 753,568,521 | 6,012 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T15:21:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/6011/comments | 0 | 2020-11-30T15:22:29Z | 2020-11-30T15:22:31Z | https://github.com/MonetDB/MonetDB/issues/6011 | 753,568,484 | 6,011 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.