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: 2011-10-23 16:43:29 +0200
From: karlis <<k.vitols>>
To: clients devs <<bugs-clients>>
Version: 11.5.9 (Aug2011-SP3) [obsolete]
Last updated: 2012-01-26 15:32:08 +0100
## Comment 16459
Date: 2011-10-23 16:43:29 +0200
From: karlis <<k.vitols>>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
Build Identifier:
I have installed latest (as of 23.10.2011) server and client version of MonetDB on WIndows XP (also tried on Windows server 2003).
I try to retrieve data from MonetDB database - voc schema (that was created using "getting started guide"), using various SQLs:
select * from invoices;
select number, trip, invoice from invoices;
select count(*) from invoices;
All of these queries work, if I run them via MonetDB client. However, if I use a tool that connects via ODBC, then I always get generic error: ODBC error state: HYC00 code: 0 message: [MonetDB][ODBC Driver 11.5.3]Optional feature not implemented. Extended fetch failed.
I've tried 2 different tools and both say the same [MoneDB ... ] error - seems that tools parse this and give different errors regarding what exactly fails.
I must note, though, that ODBC does not fail completely. I managed to reverse engineer (fetch list of tables and table columns), which means that connection via ODBC has been successful to MonetDB using credentials I've entered.
Reproducible: Always
### Steps to Reproduce:
1. Establish ODBC connection to getting started database "VOC".
2. Run SQL "select count(*) from invoices;"
### Actual Results:
error: ... HYC00 code: 0 message: [MonetDB][ODBC Driver 11.5.3] ...
### Expected Results:
I'd expect to receive numeric output in the given example from the query.
## Comment 16460
Date: 2011-10-24 14:52:15 +0200
From: @sjoerdmullender
Fetching data works fine for me, so there must be something else going on.
Can you please create a log (see below) and attach it to this bug report.
To create a log, you need to start the application that uses the MonetDB ODBC driver with an extra environment variable. Probably the easiest way to do that is to start a cmd window (Start -> Run... -> cmd.exe) and in that window type
set ODBCDEBUG=C:\....\odbc.log
and then start your application from this window.
The bit after the = should be the absolute pathname of a file you can write to. After the application is done it should contain a log of the complete interaction with the driver. Before attaching the file, please make sure it doesn't contain any sensitive information.
Instead of attaching, you can also send the file directly to me.
## Comment 16461
Date: 2011-10-24 17:32:43 +0200
From: karlis <<k.vitols>>
Created attachment 82
ODBC log
In the log you will see 2 activities I performed via Oracle Business Intelligence - Administrator tool. First activity was to get rowcount (select count(*)...) and the other was to retrieve data.
> Attached file: [odbc.log](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2910_odbc.log_82) (text/plain, 5634 bytes)
> Description: ODBC log
## Comment 16462
Date: 2011-10-24 21:37:14 +0200
From: @sjoerdmullender
I analyzed the log (thanks, they're really helpful) and saw that the problem is with the call SQLSetStmtOption(hdl, SQL_CONCURRENCY, SQL_CONCUR_READ_ONLY). Three times the application tries this call, and since this option is not implemented, the driver returns an error "Optional feature not implemented". In all three cases the application then immediately closes the connection.
I'm just reading up on the option. The application is just telling the driver that the cursors are going to be used read-only. Since that is not a problem (read-write cursors are not supported, read-only cursors shouldn't pose any problem), this is an option we *can* support. I will fix that for the next release. (It's too late for the Aug2011-SP2 release which is undergoing final testing.)
I'm changing the summary.
## Comment 16463
Date: 2011-10-24 21:46:21 +0200
From: @sjoerdmullender
Changeset [942ca37cb3e3](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=942ca37cb3e3) 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=942ca37cb3e3](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=942ca37cb3e3)
Changeset description:
ODBC: Implemented SQLSetStmtAttr(..., SQL_ATTR_CONCURRENCY, SQL_CONCUR_READ_ONLY).
This should fix bug #2910.
## Comment 16464
Date: 2011-10-24 22:05:20 +0200
From: karlis <<k.vitols>>
Created attachment 83
Another ODBC log
I attach another ODBC log file - just in case, you find it useful.. I have made 4 differenct calls from SAP Business Objects designer: 1) two calls via ODBC 2.x driver trying to retrieve select count(*) ... and select * ....;. 2) two calls via ODBC 3.x driver trying to retrieve select count (*) ... and select * from ... .
> Attached file: [odbc2.log](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2910_odbc2.log_83) (text/plain, 7839 bytes)
> Description: Another ODBC log
## Comment 16465
Date: 2011-10-25 16:04:01 +0200
From: @sjoerdmullender
(In reply to comment 5)
> Created attachment 83 [details]
> Another ODBC log
The errors in this log are all
[MonetDB][ODBC Driver 11.5.3]Syntax error or access violation
This is a generic error when the query fails. I see that the queries all use the table "passengers". Could it be that that table is not available in the "sys" schema (perhaps just in the "voc" schema)? If so, the queries should refer to "voc"."passengers" (with or without the quotes).
I will change the driver to provide the error message from the server to the application (instead of the generic message) with the same error code.
## Comment 16652
Date: 2011-12-14 16:53:19 +0100
From: @sjoerdmullender
I'm closing this report. A number of issues with the ODBC driver have been fixed recently in the upcoming (Dec2011) release that had to do with the problem described in the description and first few comments. I have tested the driver against the Oracle Business Intelligence tool (both online and offline) and the driver and server now seem to be working.
There has not been a reply to comment 6, but I suspect that if there is a bug there, it's different from the original bug.
## Comment 16834
Date: 2012-01-26 15:32:08 +0100
From: @sjoerdmullender
The Dec2011 version has been release, so declaring this bug as FIXED.
| SQLSetStmtOption(..., SQL_CONCURRENCY, SQL_CONCUR_READ_ONLY) should be allowed | https://api.github.com/repos/MonetDB/MonetDB/issues/2910/comments | 0 | 2020-11-30T11:47:11Z | 2024-06-27T11:53:35Z | https://github.com/MonetDB/MonetDB/issues/2910 | 753,409,354 | 2,910 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-10-20 13:55:04 +0200
From: Viktor Rosenfeld <<24hesk>>
To: SQL devs <<bugs-sql>>
Version: 11.5.3 (Aug2011-SP1) [obsolete]
CC: @mlkersten
Last updated: 2011-10-26 13:22:03 +0200
## Comment 16449
Date: 2011-10-20 13:55:04 +0200
From: Viktor Rosenfeld <<24hesk>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1
Build Identifier:
The query log feature as described in [1] is broken. Queries run when history is true show an error message and not the expected result. This problem persists after history is set back to false for some queries and not for others.
[1] http://www.monetdb.org/Documentation/Cookbooks/SQLrecipies/History
Reproducible: Always
### Steps to Reproduce:
1. Start mclient
2. set history = true;
3. select 1;
### Actual Results:
invalid/unknown response from server, ignoring output
? = 0:0 profiler.setFootprintFlag();
? = 0:0 profiler.setMemoryFlag();
? = 0:0 inblock := profiler.getDiskReads();
? = 0:0 oublock := profiler.getDiskWrites();
? = 0:0 xtime := alarm.usec();
(remaining output omitted, use \fraw to examine in detail)
### Expected Results:
single value 1
Pasted below is a log demonstrating the errors.
$ mclient -d demo -u monetdb
password:
Welcome to mclient, the MonetDB/SQL interactive terminal (Aug2011-SP1)
Database: MonetDB v11.5.3, 'demo'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>call resetHistory();
sql>set history=true;
sql>select 1;
invalid/unknown response from server, ignoring output
? = 0:0 profiler.setFootprintFlag();
? = 0:0 profiler.setMemoryFlag();
? = 0:0 inblock := profiler.getDiskReads();
? = 0:0 oublock := profiler.getDiskWrites();
? = 0:0 xtime := alarm.usec();
(remaining output omitted, use \fraw to examine in detail)
sql>select * from querylog;
invalid/unknown response from server, ignoring output
? = 0:0 profiler.setFootprintFlag();
? = 0:0 profiler.setMemoryFlag();
? = 0:0 inblock := profiler.getDiskReads();
? = 0:0 oublock := profiler.getDiskWrites();
? = 0:0 xtime := alarm.usec();
(remaining output omitted, use \fraw to examine in detail)
sql>set history=false;
invalid/unknown response from server, ignoring output
? = 0:0 profiler.setFootprintFlag();
? = 0:0 profiler.setMemoryFlag();
? = 0:0 inblock := profiler.getDiskReads();
? = 0:0 oublock := profiler.getDiskWrites();
? = 0:0 xtime := alarm.usec();
(remaining output omitted, use \fraw to examine in detail)
sql>select 1;
invalid/unknown response from server, ignoring output
? = 0:0 profiler.setFootprintFlag();
? = 0:0 profiler.setMemoryFlag();
? = 0:0 inblock := profiler.getDiskReads();
? = 0:0 oublock := profiler.getDiskWrites();
? = 0:0 xtime := alarm.usec();
(remaining output omitted, use \fraw to examine in detail)
sql>select * from querylog;
+---------+-------------+---------+-------------+------+------+-------------+-------------+-----------+------+--------+
| id | defined | name | query | pars | opti | ctime | arguments | execute | resu | foot |>
: : : : : e : mize : : : : lt : :>
+=========+=============+=========+=============+======+======+=============+=============+===========+======+========+
| 1006155 | 2011-10-20 | monetdb | select 1; | 609 | 356 | 2011-10-20 | user.s4_1(= | 5 | 24 | 0 |
: : 11:53:03.00 : : : : : 11:53:03.00 : 1); : : : :
: : 0000 : : : : : 0000 : : : : :
| 1006265 | 2011-10-20 | monetdb | select * fr | 662 | 1748 | 2011-10-20 | user.s5_1() | 2748 | 97 | 206498 |
: : 11:53:06.00 : : om querylog : : : 11:53:06.00 : ; : : : :
: : 0000 : : ; : : : 0000 : : : : :
| 1006570 | 2011-10-20 | monetdb | set history | 187 | 492 | 2011-10-20 | user.s6_1() | 166133530 | 0 | 0 |
: : 11:53:11.00 : : =false; : : : 11:53:11.00 : ; : : : :
: : 0000 : : : : : 0000 : : : : :
| 1006155 | 2011-10-20 | monetdb | select 1; | 609 | 356 | 2011-10-20 | user.s4_1(= | 11 | 49 | 0 |
: : 11:53:03.00 : : : : : 11:53:12.00 : 1); : : : :
: : 0000 : : : : : 0000 : : : : :
+---------+-------------+---------+-------------+------+------+-------------+-------------+-----------+------+--------+
4 tuples (11.588ms) !4 columns dropped!
note: to disable dropping columns and/or truncating fields use \w-1
sql>
## Comment 16450
Date: 2011-10-20 15:07:37 +0200
From: @mlkersten
The output you see is the debugger trace information.
A patch is pending.
## Comment 16451
Date: 2011-10-20 16:39:38 +0200
From: @mlkersten
Changeset [97580c62c2b8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=97580c62c2b8) 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=97580c62c2b8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=97580c62c2b8)
Changeset description:
Fix for bug #2909
Check if we are in debugging mode, before dumping
the trace information.
## Comment 16452
Date: 2011-10-20 16:41:23 +0200
From: @mlkersten
fixed using minor patch in mal_interpreter.
## Comment 16454
Date: 2011-10-20 17:12:44 +0200
From: @mlkersten
Changeset [4fd414abd988](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4fd414abd988) 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=4fd414abd988](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4fd414abd988)
Changeset description:
Fix for bug #2909
Check if we are in debugging mode, before dumping
the trace information.
(transplanted from 97580c62c2b8654096a66350d9de564c49f20410)
## Comment 16457
Date: 2011-10-20 17:32:36 +0200
From: @sjoerdmullender
Changeset [86e4f56d87bf](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=86e4f56d87bf) 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=86e4f56d87bf](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=86e4f56d87bf)
Changeset description:
Added test for bug #2909.
## Comment 17381
Date: 2012-06-26 09:43:39 +0200
From: @drstmane
Changeset [8d4d1a6c3440](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=8d4d1a6c3440) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=8d4d1a6c3440](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=8d4d1a6c3440)
Changeset description:
opt_history.c: fixed typo in changeset [7f20c97e8ce3](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=7f20c97e8ce3) "Optimizer de-mx step"
Found by test sql/test/BugTracker-2011/Tests/history.Bug-2909.sql (!)
| query result is not displayed when history = true | https://api.github.com/repos/MonetDB/MonetDB/issues/2909/comments | 0 | 2020-11-30T11:47:08Z | 2024-06-27T11:53:34Z | https://github.com/MonetDB/MonetDB/issues/2909 | 753,409,319 | 2,909 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-10-19 15:38:05 +0200
From: @sjoerdmullender
To: SQL devs <<bugs-sql>>
Version: 11.5.3 (Aug2011-SP1) [obsolete]
Last updated: 2011-10-26 13:22:04 +0200
## Comment 16443
Date: 2011-10-19 15:38:05 +0200
From: @sjoerdmullender
The query that the ODBC driver generates for the call to SQLTables with catalog="", schema="", table name="%", table type="TABLE" results in an error with lots of MAL code in the error message.
The actual query that is used is:
select cast(null as varchar(1)) as table_cat, s."name" as table_schem, t."name" as table_name, case when t."type" = 0 and t."system" = false and t."temporary" = 0 then cast('TABLE' as varchar(20)) when t."type" = 0 and t."system" = true and t."temporary" = 0 then cast('SYSTEM TABLE' as varchar(20)) when t."type" = 1 then cast('VIEW' as varchar(20)) when t."type" = 0 and t."system" = false and t."temporary" = 1 then cast('LOCAL TEMPORARY' as varchar(20)) else cast('INTERNAL TABLE TYPE' as varchar(20)) end as table_type, cast('' as varchar(1)) as remarks from sys."schemas" s, sys."tables" t where s."id" = t."schema_id" and t."name" like '%' and (1 = 0 or (t."type" = 0 and t."system" = false and t."temporary" = 0)) order by table_type, table_schem, table_name;
The output is:
TypeException:user.s2_1[33]:'algebra.markT' undefined in: _72:any := algebra.markT(_71:bit, _67:oid)
TypeException:user.s2_1[72]:'algebra.kunion' undefined in: _125:any := algebra.kunion(_124:bat[:oid,:oid], _72:any)
TypeException:user.s2_1[73]:'algebra.markT' undefined in: _126:any := algebra.markT(_125:any, _66:oid)
TypeException:user.s2_1[74]:'bat.reverse' undefined in: _127:any := bat.reverse(_126:any)
TypeException:user.s2_1[75]:'algebra.leftjoin' undefined in: _128:any := algebra.leftjoin(_127:any, _63:bat[:oid,:int])
TypeException:user.s2_1[76]:'bat.reverse' undefined in: _129:any := bat.reverse(_128:any)
TypeException:user.s2_1[88]:'algebra.join' undefined in: _146:any := algebra.join(_145:bat[:oid,:int], _129:any)
TypeException:user.s2_1[89]:'algebra.markT' undefined in: _147:any := algebra.markT(_146:any, _57:oid)
TypeException:user.s2_1[90]:'bat.reverse' undefined in: _148:any := bat.reverse(_147:any)
TypeException:user.s2_1[91]:'algebra.leftjoin' undefined in: _149:any := algebra.leftjoin(_148:any, _56:bat[:oid,:str])
TypeException:user.s2_1[110]:'algebra.markT' undefined in: _175:any := algebra.markT(_174:bit, _170:oid)
TypeException:user.s2_1[173]:'algebra.kunion' undefined in: _258:any := algebra.kunion(_257:bat[:oid,:oid], _175:any)
TypeException:user.s2_1[174]:'algebra.markT' undefined in: _259:any := algebra.markT(_258:any, _169:oid)
TypeException:user.s2_1[175]:'bat.reverse' undefined in: _260:any := bat.reverse(_259:any)
TypeException:user.s2_1[176]:'algebra.leftjoin' undefined in: _261:any := algebra.leftjoin(_260:any, _168:bat[:oid,:int])
TypeException:user.s2_1[177]:'bat.reverse' undefined in: _262:any := bat.reverse(_261:any)
TypeException:user.s2_1[178]:'algebra.join' undefined in: _263:any := algebra.join(_145:bat[:oid,:int], _262:any)
TypeException:user.s2_1[179]:'algebra.markT' undefined in: _264:any := algebra.markT(_263:any, _155:oid)
TypeException:user.s2_1[180]:'bat.reverse' undefined in: _265:any := bat.reverse(_264:any)
TypeException:user.s2_1[181]:'algebra.leftjoin' undefined in: _266:any := algebra.leftjoin(_265:any, _56:bat[:oid,:str])
TypeException:user.s2_1[183]:'bat.append' undefined in: _270:any := bat.append(_267:bat[:oid,:str], _266:any, _271:bit)
TypeException:user.s2_1[184]:'bat.append' undefined in: _272:any := bat.append(_270:any, _149:any, _271:bit)
TypeException:user.s2_1[185]:'algebra.project' undefined in: _273:any := algebra.project(_272:any, _33:str)
TypeException:user.s2_1[201]:'algebra.leftjoin' undefined in: _294:any := algebra.leftjoin(_127:any, _95:bat[:oid,:str])
TypeException:user.s2_1[203]:'bat.reverse' undefined in: _296:any := bat.reverse(_146:any)
TypeException:user.s2_1[204]:'algebra.markT' undefined in: _297:any := algebra.markT(_296:any, _295:oid)
TypeException:user.s2_1[205]:'bat.reverse' undefined in: _298:any := bat.reverse(_297:any)
TypeException:user.s2_1[206]:'algebra.leftjoin' undefined in: _299:any := algebra.leftjoin(_298:any, _294:any)
TypeException:user.s2_1[213]:'algebra.leftjoin' undefined in: _306:any := algebra.leftjoin(_260:any, _207:bat[:oid,:str])
TypeException:user.s2_1[215]:'bat.reverse' undefined in: _309:any := bat.reverse(_263:any)
TypeException:user.s2_1[216]:'algebra.markT' undefined in: _310:any := algebra.markT(_309:any, _307:oid)
TypeException:user.s2_1[217]:'bat.reverse' undefined in: _311:any := bat.reverse(_310:any)
TypeException:user.s2_1[218]:'algebra.leftjoin' undefined in: _312:any := algebra.leftjoin(_311:any, _306:any)
TypeException:user.s2_1[220]:'bat.append' undefined in: _316:any := bat.append(_313:bat[:oid,:str], _312:any, _317:bit)
TypeException:user.s2_1[221]:'bat.append' undefined in: _318:any := bat.append(_316:any, _299:any, _317:bit)
TypeException:user.s2_1[237]:'algebra.leftjoin' undefined in: _340:any := algebra.leftjoin(_127:any, _105:bat[:oid,:sht])
TypeException:user.s2_1[238]:'algebra.leftjoin' undefined in: _341:any := algebra.leftjoin(_298:any, _340:any)
TypeException:user.s2_1[248]:'algebra.leftjoin' undefined in: _351:any := algebra.leftjoin(_260:any, _350:bat[:oid,:sht])
TypeException:user.s2_1[249]:'algebra.leftjoin' undefined in: _352:any := algebra.leftjoin(_311:any, _351:any)
TypeException:user.s2_1[251]:'bat.append' undefined in: _356:any := bat.append(_353:bat[:oid,:sht], _352:any, _357:bit)
TypeException:user.s2_1[252]:'bat.append' undefined in: _358:any := bat.append(_356:any, _341:any, _357:bit)
TypeException:user.s2_1[268]:'algebra.leftjoin' undefined in: _382:any := algebra.leftjoin(_127:any, _378:bat[:oid,:bit])
TypeException:user.s2_1[269]:'algebra.leftjoin' undefined in: _383:any := algebra.leftjoin(_298:any, _382:any)
TypeException:user.s2_1[282]:'algebra.leftjoin' undefined in: _399:any := algebra.leftjoin(_260:any, _398:bat[:oid,:bit])
TypeException:user.s2_1[283]:'algebra.leftjoin' undefined in: _400:any := algebra.leftjoin(_311:any, _399:any)
TypeException:user.s2_1[285]:'bat.append' undefined in: _404:any := bat.append(_401:bat[:oid,:bit], _400:any, _405:bit)
TypeException:user.s2_1[286]:'bat.append' undefined in: _406:any := bat.append(_404:any, _383:any, _405:bit)
TypeException:user.s2_1[302]:'algebra.leftjoin' undefined in: _428:any := algebra.leftjoin(_127:any, _119:bat[:oid,:int])
TypeException:user.s2_1[303]:'algebra.project' undefined in: _429:any := algebra.project(_428:any, _426:bte)
TypeException:user.s2_1[304]:'algebra.leftjoin' undefined in: _430:any := algebra.leftjoin(_298:any, _429:any)
TypeException:user.s2_1[312]:'algebra.leftjoin' undefined in: _439:any := algebra.leftjoin(_260:any, _252:bat[:oid,:int])
TypeException:user.s2_1[313]:'algebra.project' undefined in: _440:any := algebra.project(_439:any, _437:bte)
TypeException:user.s2_1[314]:'algebra.leftjoin' undefined in: _441:any := algebra.leftjoin(_311:any, _440:any)
TypeException:user.s2_1[316]:'bat.append' undefined in: _445:any := bat.append(_442:bat[:oid,:bte], _441:any, _446:bit)
TypeException:user.s2_1[317]:'bat.append' undefined in: _447:any := bat.append(_445:any, _430:any, _446:bit)
TypeException:user.s2_1[403]:'group.refine' undefined in: _559:any := group.refine(_558:bat[:oid,:str], _272:any)
TypeException:user.s2_1[404]:'group.refine' undefined in: _560:any := group.refine(_559:any, _318:any)
TypeException:user.s2_1[405]:'algebra.markT' undefined in: _561:any := algebra.markT(_560:any, _274:oid)
TypeException:user.s2_1[406]:'bat.reverse' undefined in: _562:any := bat.reverse(_561:any)
TypeException:user.s2_1[407]:'algebra.leftjoin' undefined in: _563:any := algebra.leftjoin(_562:any, _273:any)
TypeException:user.s2_1[410]:'algebra.leftjoin' undefined in: _568:any := algebra.leftjoin(_562:any, _272:any)
TypeException:user.s2_1[413]:'algebra.leftjoin' undefined in: _573:any := algebra.leftjoin(_562:any, _318:any)
TypeException:user.s2_1[415]:'algebra.leftjoin' undefined in: _576:any := algebra.leftjoin(_562:any, _557:bat[:oid,:str])
TypeException:user.s2_1[422]:'algebra.project' undefined in: _587:any := algebra.project(_272:any, _584:str)
TypeException:user.s2_1[423]:'algebra.leftjoin' undefined in: _588:any := algebra.leftjoin(_562:any, _587:any)
SQLException:SQLengine:Program contains errors
## Comment 16444
Date: 2011-10-19 16:01:01 +0200
From: @sjoerdmullender
The problem disappears when the last conjunct is rewritten to
(t."type" = 0 and t."system" = false and t."temporary" = 0)
i.e. removing the 1 = 0 part. This was there to ease generation of the query.
## Comment 16445
Date: 2011-10-19 16:06:11 +0200
From: @sjoerdmullender
Changeset [1cf953b04968](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1cf953b04968) 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=1cf953b04968](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=1cf953b04968)
Changeset description:
Remove the "1 = 0 or" part of the generated conjunct for SQLTables.
By removing this part, the SQLTables query works.
This works around the problem in bug #2908.
## Comment 16448
Date: 2011-10-20 09:15:14 +0200
From: @sjoerdmullender
Changeset [cd853280fc14](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=cd853280fc14) 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=cd853280fc14](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=cd853280fc14)
Changeset description:
Added changelog message for bug #2908.
## Comment 16453
Date: 2011-10-20 17:07:21 +0200
From: @njnes
Changeset [9cc9850043c1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=9cc9850043c1) 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=9cc9850043c1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9cc9850043c1)
Changeset description:
fixed bug #2908, handle predicate in relselect properly
## Comment 16455
Date: 2011-10-20 17:27:05 +0200
From: @sjoerdmullender
Changeset [8fc79f20d6ef](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=8fc79f20d6ef) 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=8fc79f20d6ef](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=8fc79f20d6ef)
Changeset description:
Changed test for bug #2908 so that it also works in isolation.
## Comment 16456
Date: 2011-10-20 17:28:36 +0200
From: @sjoerdmullender
It looks like the bug is now really fixed.
| SQL query produces error with MAL statements | https://api.github.com/repos/MonetDB/MonetDB/issues/2908/comments | 0 | 2020-11-30T11:47:05Z | 2024-06-27T11:53:33Z | https://github.com/MonetDB/MonetDB/issues/2908 | 753,409,282 | 2,908 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-10-16 13:15:56 +0200
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @njnes
Last updated: 2011-10-16 13:35:16 +0200
## Comment 16433
Date: 2011-10-16 13:15:56 +0200
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
Build Identifier:
Superfluous information enters the catalog table.
Reproducible: Always
### Steps to Reproduce:
1. select * from functions where name ='shrink';
2.
3.
## Comment 16434
Date: 2011-10-16 13:33:05 +0200
From: @mlkersten
Referring to a request on the user list, it might be helpful to add a column in the function table with a documentation line
## Comment 16435
Date: 2011-10-16 13:35:16 +0200
From: @njnes
This simply is the comment before the actual function definition.
| Copyright ends up in function table | https://api.github.com/repos/MonetDB/MonetDB/issues/2907/comments | 0 | 2020-11-30T11:47:02Z | 2024-06-28T13:19:17Z | https://github.com/MonetDB/MonetDB/issues/2907 | 753,409,257 | 2,907 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-10-14 08:34:15 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 11.5.3 (Aug2011-SP1) [obsolete]
CC: @arjenpdevries, @njnes
Last updated: 2011-10-26 13:22:01 +0200
## Comment 16408
Date: 2011-10-14 08:34:15 +0200
From: @drstmane
Created attachment 80
mserver5 GDB log
client:
create table MyTable (a int);
alter table MyTable set read only;
server:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe86a1700 (LWP 29097)]
0x00007fffe8b88990 in rel_alter_table (sql=0x7fffdc005470, qname=0x7fffdc0faca0, te=0x0) at /net/rig.ins.cwi.nl/export/scratch0/manegold/Monet/HG/Aug2011/source/MonetDB/sql/server/rel_schema.c:1064
1064 if (nt && te->token == SQL_DROP_CONSTRAINT) {
(gdb) li
1059 node *n;
1060 sql_rel *res = NULL, *r;
1061 sql_table *nt = dup_sql_table(sql->sa, t);
1062 sql_exp ** updates, *e;
1063
1064 if (nt && te->token == SQL_DROP_CONSTRAINT) {
1065 dlist *l = te->data.lval;
1066 char *kname = l->h->data.sval;
1067 int drop_action = l->h->next->data.i_val;
1068
(gdb) p nt
$1 = (sql_table *) 0x7fffdc0fad90
(gdb) p *nt
$2 = {base = {wtime = 0, rtime = 0, flag = 1, id = 5663, name = 0x7fffdc0faeb0 "mytable"}, type = 0, system = 0 '\000', persistence = SQL_DECLARED_TABLE, commit_action = CA_COMMIT, readonly = 0 '\000', query = 0x0,
sz = 1024, pkey = 0x0, columns = {sa = 0x7fffdc0add90, destroy = 0, set = 0x7fffdc0faf40, dset = 0x0, nelm = 0x0}, idxs = {sa = 0x7fffdc0add90, destroy = 0, set = 0x0, dset = 0x0, nelm = 0x0}, keys = {
sa = 0x7fffdc0add90, destroy = 0, set = 0x0, dset = 0x0, nelm = 0x0}, triggers = {sa = 0x7fffdc0add90, destroy = 0, set = 0x0, dset = 0x0, nelm = 0x0}, tables = {sa = 0x0, destroy = 0, set = 0x0, dset = 0x0,
nelm = 0x0}, drop_action = 0, cleared = 0, data = 0x0, s = 0x0}
(gdb) p te
$3 = (symbol *) 0x0
Complete mserver5 GDB log is attached.
> Attached file: [mserver5-gdb-log](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2906_mserver5-gdb-log_80) (application/octet-stream, 5544 bytes)
> Description: mserver5 GDB log
## Comment 16411
Date: 2011-10-14 08:53:19 +0200
From: @njnes
Changeset [ea91b0fa9614](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ea91b0fa9614) 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=ea91b0fa9614](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ea91b0fa9614)
Changeset description:
fixed crash / bug #2906.
## Comment 16412
Date: 2011-10-14 08:53:51 +0200
From: @njnes
fixed, ie we check for te != NULL (again) now
## Comment 16420
Date: 2011-10-14 09:31:17 +0200
From: @drstmane
Changeset [ab3cecd81a13](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ab3cecd81a13) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ab3cecd81a13](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ab3cecd81a13)
Changeset description:
added test for bug #2906
| "ALTER TABLE mytable SET READ ONLY" results in server segfault | https://api.github.com/repos/MonetDB/MonetDB/issues/2906/comments | 0 | 2020-11-30T11:46:59Z | 2024-06-27T11:53:31Z | https://github.com/MonetDB/MonetDB/issues/2906 | 753,409,230 | 2,906 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-10-14 08:21:23 +0200
From: @drstmane
To: Documentation maintainers <<bugs-docs>>
Version: unspecified
CC: @arjenpdevries
Last updated: 2011-10-17 17:24:35 +0200
## Comment 16406
Date: 2011-10-14 08:21:23 +0200
From: @drstmane
The syntax under http://www.monetdb.org/Documentation/SQLreference/Authorisation in incorrect.
The identifiers must not be given in (single) quotes.
## Comment 16415
Date: 2011-10-14 08:59:32 +0200
From: @grobian
the syntax once WAS correct, see also the note at the end of the page:
Note the use of double and single quotes at the various places. It is important to use the right quotes.
Correct usage of quotes:
CREATE USER "voc" WITH PASSWORD 'passwd' NAME 'VOC set' SCHEMA "sys";
CREATE SCHEMA "voc" AUTHORIZATION "voc";
ALTER USER "voc" SET SCHEMA "voc";
## Comment 16440
Date: 2011-10-17 17:24:35 +0200
From: @sjoerdmullender
I updated the web page.
| Authorisation syntax incorrect | https://api.github.com/repos/MonetDB/MonetDB/issues/2905/comments | 0 | 2020-11-30T11:46:57Z | 2024-06-27T11:53:30Z | https://github.com/MonetDB/MonetDB/issues/2905 | 753,409,195 | 2,905 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-10-13 16:27:28 +0200
From: @bartscheers
To: SQL devs <<bugs-sql>>
Version: 11.5.3 (Aug2011-SP1) [obsolete]
CC: @njnes, @drstmane
Last updated: 2011-10-26 13:22:03 +0200
## Comment 16405
Date: 2011-10-13 16:27:28 +0200
From: @bartscheers
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
Build Identifier:
After creating and starting new database testing, and altering the
user, schema, password and authorization to testing, a (simple) UDF is created in the testing schema. Single calls work, but when called in batch simultaneous one or more TypeExceptions are thrown.
Reproducible: Always
### Steps to Reproduce:
1. Create schema as in bug #2903.
2. Create in testing schema UD SQL function:
CREATE FUNCTION rad(d DOUBLE) RETURNS DOUBLE BEGIN RETURN d * PI() / 180; END;
3. Init db by executing select 1;
4. %> for i in `seq 50`; do DOTMONETDBFILE=.testing mclient -dtesting -s"SELECT rad(55.81689);" & done
### Actual Results:
Several exceptions like:
TypeException:user.s1_17[4]:'user.rad' undefined in: _7:any := user.rad(_6:dbl)
SQLException:SQLengine:Program contains errors
### Expected Results:
50 times:
+------------------------+
| rad_single_value |
+========================+
| 0.97418850872349771 |
+------------------------+
1 tuple
See also bug #2903
## Comment 16409
Date: 2011-10-14 08:46:17 +0200
From: @njnes
Changeset [08e5fe124329](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=08e5fe124329) 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=08e5fe124329](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=08e5fe124329)
Changeset description:
fix for bug #2904. We now always cleanup the function list as M5 doesn't cache
and functions anymore.
## Comment 16410
Date: 2011-10-14 08:46:45 +0200
From: @njnes
fixed by always cleanup the sql function list.
## Comment 16414
Date: 2011-10-14 08:56:19 +0200
From: @njnes
*** Bug #2902 has been marked as a duplicate of this bug. ***
## Comment 16423
Date: 2011-10-14 10:14:28 +0200
From: @drstmane
re-opened to remind us that we should consider adding a test.
## Comment 16424
Date: 2011-10-14 10:23:01 +0200
From: @grobian
Just an insight from release-engineering point of view. When this bug isn't closed/nextrelease, it won't show up (automatically) on the list of closed bugs for the next release. Since this will go unnoticed for sure, it means this bug isn't listed where it is, and with the current automation, will be reported as fixed for the release afterwards (assuming it'll be closed by then).
So how about using the Keywords field to add a status like NEEDSTEST or something, such that the bug itself can remain closed?
## Comment 16425
Date: 2011-10-14 11:25:56 +0200
From: @drstmane
That would indeed be an option.
I just noticed, that closed bug with request for more information, feedback, or validation by the original reported "vanish" unnoticed, because they do no longer appear as open bugs.
in general, we would need three major categories:
- open (and that includes open but needs more info)
- fixed, but still needs feedback, info, validation, test, etc.
- closed and done.
## Comment 16427
Date: 2011-10-14 12:54:05 +0200
From: @njnes
the test of both bugs is the same (the schema part doens't make a difference), ie only one needs a test.
## Comment 16429
Date: 2011-10-14 13:00:57 +0200
From: @drstmane
is there a test for bug #2902 (which is marked as dublicate of this one), then?
## Comment 16437
Date: 2011-10-17 14:21:54 +0200
From: @sjoerdmullender
Test was added.
## Comment 16438
Date: 2011-10-17 14:27:15 +0200
From: @sjoerdmullender
Changeset [f1b05d742f8f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f1b05d742f8f) 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=f1b05d742f8f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f1b05d742f8f)
Changeset description:
Added test for bug #2904.
| TypeException after calling UDF in other than sys schema (when it is initialised) | https://api.github.com/repos/MonetDB/MonetDB/issues/2904/comments | 0 | 2020-11-30T11:46:54Z | 2024-06-27T11:53:29Z | https://github.com/MonetDB/MonetDB/issues/2904 | 753,409,164 | 2,904 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-10-13 15:46:24 +0200
From: @bartscheers
To: SQL devs <<bugs-sql>>
Version: 11.5.3 (Aug2011-SP1) [obsolete]
CC: @njnes
Last updated: 2011-10-14 08:27:37 +0200
## Comment 16404
Date: 2011-10-13 15:46:24 +0200
From: @bartscheers
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
Build Identifier:
After creating and starting new (empty) database testing, and altering the user, schema, password and authorization to testing, the 10_math.sql functions, f.ex. radians(), can not be called from within the testing schema.
Reproducible: Always
### Steps to Reproduce:
1. monetdb create (and then) start testing
2. %> mclient -dtesting
ALTER USER "monetdb" RENAME TO "testing";
ALTER USER SET PASSWORD 'testing' USING OLD PASSWORD 'monetdb';
CREATE SCHEMA "testing" AUTHORIZATION "testing";
ALTER USER "testing" SET SCHEMA "testing";
3. Create dotmonetdbfile in pwd with correct user/pw
4. %> DOTMONETDBFILE=.testing mclient -dtesting -s"SELECT RADIANS(55.81689);"
### Actual Results:
SELECT: no such unary operator 'radians(decimal)'
### Expected Results:
+------------------------+
| radians_single_value |
+========================+
| 0.97418850872349771 |
+------------------------+
1 tuple
## Comment 16407
Date: 2011-10-14 08:27:37 +0200
From: @njnes
These functions are created using create function and therefor not build in. These should be used within the sys schema or a fully qualified name should be used.
| 10_math.sql functions not found in other than sys schema | https://api.github.com/repos/MonetDB/MonetDB/issues/2903/comments | 0 | 2020-11-30T11:46:51Z | 2024-06-28T13:19:17Z | https://github.com/MonetDB/MonetDB/issues/2903 | 753,409,125 | 2,903 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-10-13 15:33:37 +0200
From: @bartscheers
To: SQL devs <<bugs-sql>>
Version: 11.5.3 (Aug2011-SP1) [obsolete]
CC: @njnes
Duplicates: #2904
Last updated: 2011-10-14 08:56:19 +0200
## Comment 16403
Date: 2011-10-13 15:33:37 +0200
From: @bartscheers
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
Build Identifier:
After creating an empty database and executing "sys" functions via several mclients at same time, errors occur saying no such unary operator radians(decimal).
Reproducible: Always
### Steps to Reproduce:
1. create start release (empty) database
2. %> for i in `seq 50`; do mclient -dtesting -s"SELECT RADIANS(55.81689);" & done;
3.
### Actual Results:
Except for one all return ERROR MESSAGES: SELECT: no such unary operator 'radians(decimal)'
### Expected Results:
50 times:
+------------------------+
| radians_single_value |
+========================+
| 0.97418850872349771 |
+------------------------+
1 tuple
Maybe related to bugs 2864, 2875 ?
## Comment 16413
Date: 2011-10-14 08:56:19 +0200
From: @njnes
fixed
*** This bug has been marked as a duplicate of bug #2904 ***
| Empty database not initialised correctly | https://api.github.com/repos/MonetDB/MonetDB/issues/2902/comments | 0 | 2020-11-30T11:46:48Z | 2024-06-28T13:19:16Z | https://github.com/MonetDB/MonetDB/issues/2902 | 753,409,091 | 2,902 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-10-12 13:10:34 +0200
From: Evert Rol <<evert.astro>>
To: clients devs <<bugs-clients>>
Version: 11.5.3 (Aug2011-SP1) [obsolete]
CC: @drstmane
Last updated: 2011-10-26 13:22:01 +0200
## Comment 16395
Date: 2011-10-12 13:10:34 +0200
From: Evert Rol <<evert.astro>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_1) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1
Build Identifier:
While not specified, most Python DB APIs use the same keywords in the connect() function. These are also suggested in footnote 1 of the Python DB API specification (PEP 249):
dsn Data source name as string
user User name as string (optional)
password Password as string (optional)
host Hostname (optional)
database Database name (optional)
Currently, the monetdb DB API uses username instead of user, and hostname instead of host.
Use of the 'user' and 'host' keywords will make the DB API more compatible with existing Python DB APIs and the suggested guideline.
Reproducible: Always
I guess it would be trivial to have both user and username, and both host and hostname allowed, for backwards compatibility.
## Comment 16396
Date: 2011-10-12 13:13:19 +0200
From: @grobian
yup, agree on that. Would you mind creating a patch?
## Comment 16397
Date: 2011-10-12 14:37:26 +0200
From: Evert Rol <<evert.astro>>
Created attachment 79
Suggested patch
Attached patch works for me, but has not (yet) been thoroughly tested.
(NB: I don't have access to the repo, so filenames at top of patch are incorrect; in case of blindly applying this patch ;-)
> Attached file: [connections.py.patch](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2901_connections.py.patch_79) (text/plain, 1650 bytes)
> Description: Suggested patch
## Comment 16398
Date: 2011-10-12 14:42:01 +0200
From: @grobian
LGTM.
Do you intend to test it a bit further?
## Comment 16399
Date: 2011-10-12 17:59:24 +0200
From: Evert Rol <<evert.astro>>
Not really.
It's used in a practical use case, which serves as the most important test for me.
I did test for the various variants of user/username and host/hostname (including both, to test the precedence); if wanted, I can include that test in the unit test (I think that's a single Python file, from what I could find).
Other than that, I felt the change was trivial enough to not overly bother with it (famous last words).
## Comment 16400
Date: 2011-10-12 18:25:29 +0200
From: @grobian
I concur, but your comment 2 suggested you'd know how to test it better. Consider it applied.
## Comment 16401
Date: 2011-10-12 18:32:39 +0200
From: @grobian
bah, forgot bugref in commit:
http://dev.monetdb.org/hg/MonetDB/rev/2dd92bb63b34
## Comment 16419
Date: 2011-10-14 09:22:49 +0200
From: @drstmane
Would it be possible to also add a test for this one?
## Comment 16422
Date: 2011-10-14 10:14:11 +0200
From: @drstmane
re-opened to remind us that we should consider adding a test
## Comment 16439
Date: 2011-10-17 14:54:27 +0200
From: Evert Rol <<evert.astro>>
Created attachment 81
Unit test patch
Not the most pretty test, but this should test various combinations of user/username and host/hostname.
I've assumed runtests.py serves as the unit test for the Python client.
> Attached file: [runtests.patch](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2901_runtests.patch_81) (text/plain, 2875 bytes)
> Description: Unit test patch
## Comment 16446
Date: 2011-10-19 17:19:05 +0200
From: @sjoerdmullender
Changeset [1045c895ec9e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1045c895ec9e) 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=1045c895ec9e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=1045c895ec9e)
Changeset description:
Added test for bug #2901.
## Comment 16447
Date: 2011-10-19 17:20:18 +0200
From: @sjoerdmullender
I added a test.
I didn't use Evert's test since we don't actually use those unit tests.
| Make keyword arguments in Python DB API connect() function more standard | https://api.github.com/repos/MonetDB/MonetDB/issues/2901/comments | 0 | 2020-11-30T11:46:45Z | 2024-06-27T11:53:26Z | https://github.com/MonetDB/MonetDB/issues/2901 | 753,409,057 | 2,901 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-10-12 12:07:15 +0200
From: @swingbit
To: SQL devs <<bugs-sql>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @njnes
Last updated: 2011-10-26 13:22:04 +0200
## Comment 16394
Date: 2011-10-12 12:07:15 +0200
From: @swingbit
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.81 Safari/535.2
Build Identifier:
The SQL function rand(i int) (the version with seed!) is mapped to the MAL function srand, which maps in turn to this C function:
str
MATHsrandint(int *seed)
{
srand(*seed);
return MAL_SUCCEED;
}
Therefore, the SQL function returns NULL.
While this could be the expected behaviour in MAL (to return void), I don't think it is expected to return NULL in SQL.
What I would expect from the SQL call rand(100) is a call to srand(100) followed by a call to rand(), with its return valued passed to SQL.
Reproducible: Always
### Steps to Reproduce:
1. select rand(100),rand();
2.
3.
### Actual Results:
+----------------------------------------------------------------------------------+------------+
| rand_single_value | rand |
+==================================================================================+============+
| null | 1804289383 |
+----------------------------------------------------------------------------------+------------+
### Expected Results:
+------------+------------+
| rand | rand |
+============+============+
| 1804289383 | 846930886 |
+------------+------------+
## Comment 16416
Date: 2011-10-14 09:02:26 +0200
From: @njnes
fixed by adding the combined srand/rand function
## Comment 16417
Date: 2011-10-14 09:08:37 +0200
From: @njnes
Changeset [26cb61b1604b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=26cb61b1604b) 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=26cb61b1604b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=26cb61b1604b)
Changeset description:
fixes for bug #2900
add sqlrand which maps to srand + rand call.
## Comment 16418
Date: 2011-10-14 09:20:28 +0200
From: @drstmane
Changeset [2615851abad6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2615851abad6) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2615851abad6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2615851abad6)
Changeset description:
added test for bug #2900
| rand(int) should not return NULL | https://api.github.com/repos/MonetDB/MonetDB/issues/2900/comments | 0 | 2020-11-30T11:46:41Z | 2024-06-27T11:53:25Z | https://github.com/MonetDB/MonetDB/issues/2900 | 753,409,032 | 2,900 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-10-11 14:11:46 +0200
From: @grobian
To: SQL devs <<bugs-sql>>
Version: 11.5.7 (Aug2011-SP2) [obsolete]
Duplicates: #2834
Last updated: 2011-10-26 14:09:46 +0200
## Comment 16392
Date: 2011-10-11 14:11:46 +0200
From: @grobian
When a large amount of prepared statements are created, the server at some point (seems to be around ~18-23) restarts the counter id from 0 again, causing conflicts with applications holding pointers to the old id (and hence performing EXECs with incompatible or missing arguments).
Perhaps this is caused by parallel connections creating prepared statements as well.
## Comment 16467
Date: 2011-10-26 11:15:52 +0200
From: @grobian
This is likely caused by concurrent connections performing schema updates.
## Comment 16468
Date: 2011-10-26 14:09:46 +0200
From: @grobian
I realised this bug is the same as 2834
*** This bug has been marked as a duplicate of bug #2834 ***
| Server emits duplicate prepared statement ids | https://api.github.com/repos/MonetDB/MonetDB/issues/2899/comments | 0 | 2020-11-30T11:46:39Z | 2024-06-28T13:19:15Z | https://github.com/MonetDB/MonetDB/issues/2899 | 753,409,002 | 2,899 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-10-07 11:00:21 +0200
From: Evert Rol <<evert.astro>>
To: SQL devs <<bugs-sql>>
Version: 11.5.3 (Aug2011-SP1) [obsolete]
CC: @njnes
Last updated: 2011-10-26 13:22:01 +0200
## Comment 16385
Date: 2011-10-07 11:00:21 +0200
From: Evert Rol <<evert.astro>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1
Build Identifier:
When running a select with a double "order by" on a large table (200000 records for a table with 2 int columns) and the second ordering is 'DESC', the query fails with a TypeException error 'mat.refine_reverse' undefined.
Interestingly, during an mclient session, when one stepwise increases the size of the table, the problem does not occur or only at an even larger number of records, which seems because of an optimisation (caching) mechanism.
Restarting the mclient session causes the bug to reappear.
Reproducible: Always
### Steps to Reproduce:
Create a table with 200000 records in it and 2 columns.
sql>\d t
CREATE TABLE "tkp"."t" (
"i" int,
"j" int
);
sql>select count(*) from t;
+--------+
| L4 |
+========+
| 200000 |
+--------+
1 tuple
Run a query, ordering on both columns:
sql>select * from t where i < 10 order by i asc, j desc;
TypeException:user.s0_1[76]:'mat.refine_reverse' undefined in: (_173:bat[:void,:oid], _174:bat[:void,:bte]) := mat.refine_reverse(_168:bat[:void,:int], _169:bat[:void,:bte], _175:bat[:oid,:int], _176:bat[:oid,:int], _177:bat[:oid,:int])
SQLException:SQLengine:Program contains errors
sql>
(Note: the where clause is not necessary, but with the aforementioned optimisation/caching result, is probably prudent.)
### Actual Results:
TypeException:user.s0_1[76]:'mat.refine_reverse' undefined in: (_173:bat[:void,:oid], _174:bat[:void,:bte]) := mat.refine_reverse(_168:bat[:void,:int], _169:bat[:void,:bte], _175:bat[:oid,:int], _176:bat[:oid,:int], _177:bat[:oid,:int])
SQLException:SQLengine:Program contains errors
### Expected Results:
+------+--------+
| i | j |
+======+========+
| 1 | 199999 |
| 2 | 199998 |
| 3 | 199997 |
| 4 | 199996 |
| 5 | 199995 |
| 6 | 199994 |
| 7 | 199993 |
| 8 | 199992 |
| 9 | 199991 |
+------+--------+
9 tuples (2.748ms)
This occurs on Aug2011-SP1 and Oct2010 (11.5.3 and 5.22.3); for the Aug2011-SP1, this occurs on Linux and OS X. The OS X build has asserts enabled, though no assert appears.
## Comment 16421
Date: 2011-10-14 09:31:51 +0200
From: @njnes
fixed by renaming mat.refine_rev into mat.refine_reverse (similar to the group.refine and group.refine_reverse)
Added test to missing_refine_reverse.
## Comment 16430
Date: 2011-10-14 13:02:18 +0200
From: @njnes
Changeset [67224c43085a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=67224c43085a) 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=67224c43085a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=67224c43085a)
Changeset description:
fix bug #2898 (by renaming refine_rev into refine_reverse)
| order by for multiple (two) columns fails for large tables when second ordering is 'desc': "mat.refine_reverse' undefined" | https://api.github.com/repos/MonetDB/MonetDB/issues/2898/comments | 0 | 2020-11-30T11:46:36Z | 2024-06-27T11:53:23Z | https://github.com/MonetDB/MonetDB/issues/2898 | 753,408,981 | 2,898 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-10-06 11:43:05 +0200
From: Rémy Chibois <<rchibois>>
To: clients devs <<bugs-clients>>
Version: 11.5.3 (Aug2011-SP1) [obsolete]
Last updated: 2011-10-26 13:22:02 +0200
## Comment 16382
Date: 2011-10-06 11:43:05 +0200
From: Rémy Chibois <<rchibois>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_1) AppleWebKit/534.48.3 (KHTML, like Gecko) Version/5.1 Safari/534.48.3
Build Identifier:
Subroutine Mapi::get block does not check return value from sysread, which, depending on the current read context, time and socket data availability, may not return the requested number of bytes (actually less). This happens rarely when connecting to a server located on the same computer, but rather frequently when using a remote server, essentially because network latency is higher
Reproducible: Always
### Steps to Reproduce:
1. Use the following snippet:
====
!/usr/bin/env perl
use strict;
use warnings;
$|++;
use DBI();
my $dbh = DBI->connect(
'dbi:monetdb:host=a_remote_host;database=a_db', 'monetdb', 'monetdb'
);
my $query = qq{
SELECT
*
FROM
some_table
};
my $sth = $dbh->prepare($query);
$sth->execute;
my $r = $sth->fetchall_arrayref();
$dbh->disconnect();
====
2. You should observe random warnings and corrupt data
### Actual Results:
Lots of warnings from Mapi.pm because read blocks are incomplete
### Expected Results:
Correct data
## Comment 16383
Date: 2011-10-06 11:44:54 +0200
From: Rémy Chibois <<rchibois>>
Created attachment 78
Patch handling short reads as well as read errors
This patch adds an additional method to Mapi.pm in order to handle short reads and read errors
> Attached file: [Mapi.pm-short_read.patch](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2897_Mapi.pm-short_read.patch_78) (text/plain, 1174 bytes)
> Description: Patch handling short reads as well as read errors
## Comment 16384
Date: 2011-10-06 11:47:49 +0200
From: Rémy Chibois <<rchibois>>
(Previous patch is against Mapi.pm from MonetDB-11.5.3)
## Comment 16386
Date: 2011-10-07 16:17:12 +0200
From: @sjoerdmullender
Changeset [61f3aed5a5ab](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=61f3aed5a5ab) 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=61f3aed5a5ab](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=61f3aed5a5ab)
Changeset description:
Added test for bug #2897.
Unfortunately (?) the test doesn't fail because we test within a
single system.
## Comment 16387
Date: 2011-10-07 16:22:31 +0200
From: Rémy Chibois <<rchibois>>
Changeset [76662f0c364c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=76662f0c364c) made by Rémy Chibois <rchibois@gmail.com> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=76662f0c364c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=76662f0c364c)
Changeset description:
perl: make sure blocks are completely read.
Fixed bug #2897 where slow (network) reads could cause blocks to not be
fully read in one go, causing errors in the subsequent use of those
blocks.
## Comment 16388
Date: 2011-10-07 16:24:51 +0200
From: @sjoerdmullender
The patch has been applied (thanks for the report and the patch).
| Mapi.pm: short reads not handled when reading blocks from server | https://api.github.com/repos/MonetDB/MonetDB/issues/2897/comments | 0 | 2020-11-30T11:46:33Z | 2024-06-27T11:53:22Z | https://github.com/MonetDB/MonetDB/issues/2897 | 753,408,949 | 2,897 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-10-06 00:51:16 +0200
From: Mark Kerzner <<mark.kerzner>>
To: Documentation maintainers <<bugs-docs>>
Version: unspecified
CC: mark.kerzner
Last updated: 2011-12-27 11:58:53 +0100
## Comment 16380
Date: 2011-10-06 00:51:16 +0200
From: Mark Kerzner <<mark.kerzner>>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110921 Ubuntu/10.04 (lucid) Firefox/3.6.23
Build Identifier:
This page, http://www.monetdb.org/Documentation/Cookbooks/SQLrecipies/BinaryBulkLoad says the following
create table Tmp( i int, f float, t date, s string);
copy into Tmp from ('file_i', 'file_f', 'file_t', 'file_s');
However, the "s string" part of it does not work - string binary load is not implement. Since there is currently no plans to implement string load, the documentation should be corrected.
The problem is that this is misleading, and I started on the project that now I see I cannot finish as planned.
Reproducible: Always
## Comment 16647
Date: 2011-12-09 10:56:49 +0100
From: @sjoerdmullender
The problem has been addressed in changeset [4e1b9cfdc907](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4e1b9cfdc907) The solution is not optimal, but strings can be attached using the syntax given in the documentation.
The fix is in the Dec2011 branch.
## Comment 16648
Date: 2011-12-09 10:59:32 +0100
From: @sjoerdmullender
I added a comment to the documentation about availability of the feature.
## Comment 16649
Date: 2011-12-09 11:00:45 +0100
From: @sjoerdmullender
I hope the fixes are sufficient. If not, please reopen.
## Comment 16651
Date: 2011-12-09 16:35:15 +0100
From: Mark Kerzner <<mark.kerzner>>
That works perfectly for me. However, I still have a couple questions.
1. "Not optimal" from the architectural point of view, or not optimal for performance? Is it closer to bulk load or to regular ASCII load?
2. Is it part of the distribution, or do I still need to build it myself?
Thank you.
## Comment 16698
Date: 2011-12-27 11:58:53 +0100
From: @sjoerdmullender
(In reply to comment 4)
> That works perfectly for me. However, I still have a couple questions.
>
> 1. "Not optimal" from the architectural point of view, or not optimal for
> performance? Is it closer to bulk load or to regular ASCII load?
"Not optimal" in the sense that the data is copied, unlike for other types. So it is indeed more like bulk load, at least for the string columns.
> 2. Is it part of the distribution, or do I still need to build it myself?
It's in the Dec2011 and default branches. These have not yet been released.
We don't recommend you using the default branch, but you could try to compile the Dec2011 branch.
>
> Thank you.
| Binary bulk loads page gives a string load example, but it is not implemented | https://api.github.com/repos/MonetDB/MonetDB/issues/2896/comments | 0 | 2020-11-30T11:46:31Z | 2024-06-27T11:53:21Z | https://github.com/MonetDB/MonetDB/issues/2896 | 753,408,921 | 2,896 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-10-06 00:45:19 +0200
From: @mlkersten
To: clients devs <<bugs-clients>>
Version: 11.5.9 (Aug2011-SP3) [obsolete]
Last updated: 2011-12-09 11:05:35 +0100
## Comment 16379
Date: 2011-10-06 00:45:19 +0200
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
Build Identifier:
Assertion is triggered in mclient
Reproducible: Always
### Steps to Reproduce:
1. consider the query saved in file x:
set optimizer='default';
select count(*)
from tables;
### Actual Results:
2.mclient -d sf1 <x
SQLException:optimizer:Optimizer 'default' pipeline does not exist, use default pipe instead
mclient: /ufs/mk/current//package/clients/mapilib/mapi.c:1483: close_result: Assertion `hdl->active != result' failed.
Aborted
## Comment 16381
Date: 2011-10-06 08:23:11 +0200
From: @grobian
sjoerd, this is exactly the thing I was talking about yesterday :)
## Comment 16390
Date: 2011-10-10 16:00:08 +0200
From: @grobian
This is a mapi problem caused by random garbage sent to the client (library), which gets lost. Hard to fix.
## Comment 16492
Date: 2011-10-28 09:28:12 +0200
From: @sjoerdmullender
I cannot reproduce this at all.
Did you start the server in any particular way? Do you have debugging enabled in some way?
## Comment 16650
Date: 2011-12-09 11:05:35 +0100
From: @sjoerdmullender
I'm closing this as "works for me" since that is what it does.
If you have a more detailed way of reproducing the error, please reopen and elaborate.
| Assertion triggered from SQL | https://api.github.com/repos/MonetDB/MonetDB/issues/2895/comments | 0 | 2020-11-30T11:46:28Z | 2024-06-28T13:19:14Z | https://github.com/MonetDB/MonetDB/issues/2895 | 753,408,895 | 2,895 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-10-05 09:52:51 +0200
From: @bartscheers
To: SQL devs <<bugs-sql>>
Version: 11.5.3 (Aug2011-SP1) [obsolete]
CC: @njnes, @drstmane
Last updated: 2011-10-26 13:22:00 +0200
## Comment 16371
Date: 2011-10-05 09:52:51 +0200
From: @bartscheers
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
Build Identifier:
No initial cast of integer to double, but implicit in re-execuion after double is involved in calculation. After client reconnection, re-execution does not cast integer.
Reproducible: Always
### Steps to Reproduce:
create table t1 (i int, d double);
insert into t1 values (1,1.0),(2,2.0),(3,3.0),(4,4.0);
select * from t1;
select i,1/(i-1) from t1 where i > 1;
select i,1/(i-1.0) from t1 where i > 1;
select i,1/(i-1) from t1 where i > 1;
\q
reconnect
select i,1/(i-1) from t1 where i > 1;
### Actual Results:
The same query gives different results:
sql> select i,1/(i-1) from t1 where i > 1;
+------+----------------------+
| i | sql_div_single_value |
+======+======================+
| 2 | 1 |
| 3 | 0 |
| 4 | 0 |
+------+----------------------+
sql> select i,1/(i-1) from t1 where i > 1;
+------+-----------------------+
| i | sql_div_single_value |
+======+=======================+
| 2 | 1.000 |
| 3 | 0.500 |
| 4 | 0.333 |
+------+-----------------------+
### Expected Results:
Same query should produce identical results
## Comment 16372
Date: 2011-10-05 12:34:56 +0200
From: @sjoerdmullender
A simpler way to reproduce the problem (without client restart):
create table t1 (i int, d double);
insert into t1 values (1,1.0),(2,2.0),(3,3.0),(4,4.0);
select i,1/(i-1) from t1 where i > 1;
select i,1/(i-1.0) from t1 where i > 1;
select i,1/(i-1) from t1 where i > 1;
The first and third selects are identical but give different results.
## Comment 16373
Date: 2011-10-05 12:37:54 +0200
From: @drstmane
running both queries with TRACE (first Q1, then Q2, then Q1, again) suggest
that
query caching is the "problem":
Q1: select i,1/(i-1) from t1 where i > 1;
is cached in a MAL function.
Q2: select i,1/(i-1.0) from t1 where i > 1;
does not match the cached plan/MAL function (probably because double is not a
subtype of int); hence, it's translated and cache in a new plan/MAL function.
Then, calling Q1 again matched the second plan (probably because int is a
subtype of double), and thus calls the second MAL function with
double-semantics, rather than the more-specific first one with int-semantics
(I'm actually not sure, whether the first plan is indeed still there ...).
## Comment 16374
Date: 2011-10-05 12:38:37 +0200
From: @drstmane
client restart empties the query cache.
## Comment 16375
Date: 2011-10-05 12:40:48 +0200
From: @sjoerdmullender
Changeset [c159291245ff](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c159291245ff) 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=c159291245ff](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c159291245ff)
Changeset description:
Added test for bug #2894.
I'm not sure whether the first or third select gives the right
answer. I've chosen the third for now.
## Comment 16376
Date: 2011-10-05 13:48:50 +0200
From: @drstmane
I'm not completely sure, but I would not be surprised if the standard SQl semantics requires to stil to integer arithmetic if only integer columns and literals are involved. If so, each execution of the first variant of the query (with integer literal) should result in the pure integer result while each execution of the second variant (with decimal/double literal) should return the respective result using decimal/double arithmetic. This could be achieved by "simply" making the cache matching more strict, i.e., not matching cached plans with super-type parameters if these have different semantics/arithmetic.
## Comment 16402
Date: 2011-10-13 08:01:48 +0200
From: @drstmane
Changeset [44f8c57e32bf](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=44f8c57e32bf) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=44f8c57e32bf](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=44f8c57e32bf)
Changeset description:
fixed stable output of test for bug #2894
as it IMHO should be:
the query with integer constants yields an integer result,
the query with decimal constants yields a decimal result;
the test still fails, i.e., the bug is still to be fixed.
## Comment 16426
Date: 2011-10-14 12:52:45 +0200
From: @njnes
fixed by no longer casting int's to double in the query cache.
## Comment 16431
Date: 2011-10-14 13:02:19 +0200
From: @njnes
Changeset [54c3db74703a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=54c3db74703a) 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=54c3db74703a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=54c3db74703a)
Changeset description:
fixed bug #2894
make sure we don't cast int's to double on queries.
| No consistent behavior of implicit cast of integer to double | https://api.github.com/repos/MonetDB/MonetDB/issues/2894/comments | 0 | 2020-11-30T11:46:26Z | 2024-06-27T11:53:19Z | https://github.com/MonetDB/MonetDB/issues/2894 | 753,408,860 | 2,894 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-10-03 16:21:26 +0200
From: Evert Rol <<evert.astro>>
To: SQL devs <<bugs-sql>>
Version: 11.5.3 (Aug2011-SP1) [obsolete]
CC: @njnes
Last updated: 2011-10-05 16:53:35 +0200
## Comment 16370
Date: 2011-10-03 16:21:26 +0200
From: Evert Rol <<evert.astro>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1
Build Identifier:
A division by zero ArithmeticException occurs when two expressions are OR-ed together in a WHERE clause, even when (through a subquery/subtable) there should be no division by zero.
This may be related to bug #2887 (which was fixed in Aug2011-SP1), but in this case there is no CASE statement.
Reproducible: Always
### Steps to Reproduce:
Following test shows success and failures on simple table, through the mclient:
create table catalog ( n int );
insert into catalog values (1);
insert into catalog values (2);
select * from catalog;
select * from catalog where n > 1;
select t.n from (select * from catalog where n > 1) as t;
select t.n from (select * from catalog where n > 1) as t where 1/(t.n-1) > 0;
select t.n from (select * from catalog where n > 1) as t where t.n/(t.n-1) > 0;
select t.n from (select * from catalog where n > 1) as t where 1/(t.n-1) > 0 and t.n/(t.n-1) > 0;
select t.n from (select * from catalog where n > 1) as t where t.n/(t.n-1) > 0 and 1/(t.n-1) > 0;
select t.n from (select * from catalog where n > 1) as t where t.n/(t.n-1) > 0 or 1/(t.n-1) > 0;
select t.n from (select * from catalog where n > 1) as t where 1/(t.n-1) > 0 or t.n/(t.n-1) > 0;
### Actual Results:
For the above demonstration, the last 2 statements will fail with a 'division by zero', while I expect that t.n can never be 1.
Also, I found that depending on the order of the two comparisons, I get one or two (identical) errors; hence the examples with switched order.
The actual exception:
ArithmeticException:batcalc./:Division by zero
### Expected Results:
No ArithmeticException.
mclient -d testing -u monetdb -H
password:
Welcome to mclient, the MonetDB/SQL interactive terminal (Aug2011-SP1)
Database: MonetDB v11.5.3, 'testing'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>
## Comment 16377
Date: 2011-10-05 16:52:02 +0200
From: @njnes
Changeset [0da61133a6a0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0da61133a6a0) 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=0da61133a6a0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0da61133a6a0)
Changeset description:
Make sure a simple x > 0 is handled before complex selection expressions with functions. This works around the problem of division by zero (but that realy isn't sql's fault). No a Bug #2893.
## Comment 16378
Date: 2011-10-05 16:53:35 +0200
From: @njnes
Made sure this special case works as expected. In general however there is no way (except case statements) to work around division by zero. SQL expects the data to be correct.
| ArithmeticException Division by zero with OR in WHERE statement, where it should be excluded | https://api.github.com/repos/MonetDB/MonetDB/issues/2893/comments | 0 | 2020-11-30T11:46:23Z | 2024-06-28T13:19:14Z | https://github.com/MonetDB/MonetDB/issues/2893 | 753,408,834 | 2,893 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-10-01 09:01:31 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 11.5.1 (Aug2011) [obsolete]
Last updated: 2011-10-01 20:49:39 +0200
## Comment 16364
Date: 2011-10-01 09:01:31 +0200
From: @drstmane
Test sql/test/BugTracker-2009/Tests/rollback_bug.sql started failing somewhere between changeset [4dbd0d7e7e97](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4dbd0d7e7e97) and changeset [8328cd141b78;](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=8328cd141b78;) cf.,
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=41881:8328cd141b78,41856:4dbd0d7e7e97&module=sql&targets=GNU-Fedora-x86_64-propcheck&order=platform,arch,compiler&diff
I.e., any of these commits seems to have caused the failing:
http://monetdb.cwi.nl/testweb/logs/41881:8328cd141b78/incoming_commits
## Comment 16365
Date: 2011-10-01 16:22:39 +0200
From: @drstmane
The changeset that introduces the problem appears to be changeset [cc4dd0565659](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=cc4dd0565659)
http://dev.monetdb.org/hg/MonetDB/rev/cc4dd0565659
The problem is, that the original error that triggers the transaction abort is no longer displayed.
## Comment 16366
Date: 2011-10-01 16:24:53 +0200
From: @grobian
let me look at it later
## Comment 16368
Date: 2011-10-01 20:44:00 +0200
From: @grobian
hehe, no, looking closely at the test, my ghost-fix actually also here fixed another "ghost". The error message that is now missing, was a repetition (e.g. leftover) of the previous error.
IOW it just needs to be approved.
## Comment 16369
Date: 2011-10-01 20:49:06 +0200
From: @grobian
Changeset [28a18721bb66](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=28a18721bb66) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=28a18721bb66](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=28a18721bb66)
Changeset description:
rollback_bug test: approve, bug #2892
| test sql/test/BugTracker-2009/Tests/rollback_bug.sql fails since recently | https://api.github.com/repos/MonetDB/MonetDB/issues/2892/comments | 0 | 2020-11-30T11:46:20Z | 2024-06-27T11:53:17Z | https://github.com/MonetDB/MonetDB/issues/2892 | 753,408,798 | 2,892 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-09-28 10:41:58 +0200
From: Rémy Chibois <<rchibois>>
To: clients devs <<bugs-clients>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @drstmane
Last updated: 2012-01-26 15:31:59 +0100
## Comment 16333
Date: 2011-09-28 10:41:58 +0200
From: Rémy Chibois <<rchibois>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_1) AppleWebKit/534.48.3 (KHTML, like Gecko) Version/5.1 Safari/534.48.3
Build Identifier:
In the current implementation, MapiPP.pm fetches all results from a query which could result in high memory consumption, if not exhaust.
Fetching results only when needed would allow processing large result sets.
Reproducible: Always
### Steps to Reproduce:
1. Use the following snippet on a large table (millions of rows)
=====
!/usr/bin/env perl
use strict;
use warnings;
$|++;
use DBI();
my $dbh = DBI->connect(
'dbi:monetdb:database=big_db', 'monetdb', 'monetdb'
);
my $query = qq{
SELECT
*
FROM
big_table
};
my $sth = $dbh->prepare($query);
$sth->execute;
my $r = $sth->fetchall_arrayref();
print scalar(@{$r}) . " rows\n";
$dbh->disconnect();
=====
### Actual Results:
While functioning correctly if there's enough RAM, MapiPP.pm fetches all results before returning control to DBI.
### Expected Results:
Nearly instant return from $sth->execute() and progressive fetch when calling $sth->fetchall_arrayref(), which can also be used to fetch batch of rows if used as:
=====
Iterate over result set by batches of 10000 rows
while (my $rows = $sth->fetchall_arrayref(undef, 10000)) {
}
=====
You'll find attached a patch against current MapiPP.pm (from MonetDB-11.5.3) which tries to implement progressive fetch.
## Comment 16334
Date: 2011-09-28 10:42:52 +0200
From: Rémy Chibois <<rchibois>>
Created attachment 77
Patch implementing progressive fetch of results
> Attached file: [MapiPP.pm-progressive_fetch.patch](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2891_MapiPP.pm-progressive_fetch.patch_77) (text/plain, 1174 bytes)
> Description: Patch implementing progressive fetch of results
## Comment 16335
Date: 2011-09-28 11:00:36 +0200
From: @grobian
How does this affect moving with the cursor in both directions? Or does DBD not support this?
## Comment 16336
Date: 2011-09-28 11:13:57 +0200
From: Rémy Chibois <<rchibois>>
As far as I can tell, there's no direct support for SQL's CURSOR in DBI/DBD, apart from using database (possibly specific) statements like:
=====
$dbh->do("DECLARE my_cursor CURSOR FOR SELECT...");
and then issuing:
while (...) {
my $sth = $dbh->prepare("FETCH 10000 FROM my_cursor");
$sth->execute();
use $sth->fetch*
}
=====
So, for me, DBI/DBD "fetch" is a forward only operation.
## Comment 16339
Date: 2011-09-28 13:08:07 +0200
From: Rémy Chibois <<rchibois>>
Changeset [f584fadb4847](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f584fadb4847) made by R?my Chibois <rchibois@gmail.com> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f584fadb4847](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f584fadb4847)
Changeset description:
MapiPP: fetch results progressively, bug #2891
In the current implementation, MapiPP.pm fetches all results from a
query which could result in high memory consumption, if not exhaust.
Fetching results only when needed allows processing large result sets.
## Comment 16340
Date: 2011-09-28 13:08:48 +0200
From: @grobian
Thanks, I applied your patch in the current development branch.
## Comment 16558
Date: 2011-11-14 11:02:39 +0100
From: @drstmane
See also bug #2931.
## Comment 16573
Date: 2011-11-26 16:23:08 +0100
From: @grobian
This change makes the code fail. It must be fixed before Dec2011 release, or else it has to be reverted.
## Comment 16575
Date: 2011-11-26 16:23:33 +0100
From: @grobian
*** Bug #2931 has been marked as a duplicate of this bug. ***
## Comment 16576
Date: 2011-11-26 16:45:29 +0100
From: Rémy Chibois <<rchibois>>
Could you please tell me what's failing ?
## Comment 16577
Date: 2011-11-26 16:46:48 +0100
From: @grobian
see bug #2931.
I'm currently working on a fix, which I think I can finish shortly.
## Comment 16578
Date: 2011-11-27 10:40:43 +0100
From: @grobian
Changeset [3ee6b959a958](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=3ee6b959a958) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=3ee6b959a958](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=3ee6b959a958)
Changeset description:
MonetDB-CLI: fix MAL server interaction
Since the progressive fetching enhancement from bug #2891, retrieving
results from a MAL server failed, because the progressive code relies on
the metadata headers as sent by the SQL server. In case we detect a
result without these metadata headers, fall back to the old buffered way
of reading, such that the total tuple count is available.
This fixes the failing MAL perl_dbi (malsample.pl) test.
## Comment 16579
Date: 2011-11-27 10:41:58 +0100
From: @grobian
ok, fixed the regression now by just prefetching the results for non-SQL answers.
## Comment 16820
Date: 2012-01-26 15:31:59 +0100
From: @sjoerdmullender
The Dec2011 version has been release, so declaring this bug as FIXED.
| Make MapiPP.pm fetch results progressively | https://api.github.com/repos/MonetDB/MonetDB/issues/2891/comments | 0 | 2020-11-30T11:46:18Z | 2024-06-27T11:53:16Z | https://github.com/MonetDB/MonetDB/issues/2891 | 753,408,778 | 2,891 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-09-26 15:56:49 +0200
From: Joris Slob <<jorisslob>>
To: SQL devs <<bugs-sql>>
Version: 11.5.3 (Aug2011-SP1) [obsolete]
CC: @njnes
Last updated: 2011-10-26 13:22:05 +0200
## Comment 16329
Date: 2011-09-26 15:56:49 +0200
From: Joris Slob <<jorisslob>>
User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1
Build Identifier:
For the following table:
CREATE TABLE "sys"."facts" (
"subject" CHAR(8192),
"predicate" CHAR(8192),
"object" CHAR(8192)
);
With 10M rows a query posed like this:
SELECT COUNT(DISTINCT(predicate)) from facts;
takes 4.5s
While a query posed like this:
SELECT COUNT(*) FROM (SELECT DISTINCT(predicate) from facts) AS b;
takes 142ms
I asked about this on the mailing list and they said I should file a bug report, because it is probably the optimisers taking a wrong turn.
======================
Additional information
======================
PLAN SELECT COUNT(DISTINCT(predicate)) from facts;
+-------------------------------------------------------------------------------+
| rel |
+===============================================================================+
| project ( |
| | group by ( |
| | | table(sys.facts) [ facts.subject, facts.predicate, facts.%TID% NOT NULL ] |
| | ) [ ] [ sys.count unique no nil (facts.predicate) as L4 ] |
| ) [ L4 ] |
+-------------------------------------------------------------------------------+
PLAN SELECT COUNT(*) FROM (SELECT DISTINCT(predicate) from facts) AS b;
+------------------------------------------------------------------+
| rel |
+==================================================================+
| project ( |
| | group by ( |
| | | distinct project ( |
| | | | table(sys.facts) [ facts.predicate, facts.%TID% NOT NULL ] |
| | | ) [ facts.predicate as b.predicate ] |
| | ) [ ] [ sys.count() NOT NULL as L5 ] |
| ) [ L5 NOT NULL ] |
+------------------------------------------------------------------+
EXPLAIN SELECT COUNT(DISTINCT(predicate)) from facts;
+---------------------------------------------------------------------------------------------------------------------------+
| mal |
+===========================================================================================================================+
| function user.s2_1{autoCommit=true}():void; |
| X_17 := nil:wrd; |
| barrier X_61 := language.dataflow(); |
| X_2 := sql.mvc(); |
| X_44:bat[:oid,:str] := sql.bind(X_2,"sys","facts","predicate",0,0,2); |
| X_48 := algebra.selectNotNil(X_44); |
| X_39:bat[:oid,:str] := sql.bind(X_2,"sys","facts","predicate",2,0,2); |
| X_50 := algebra.kdifference(X_48,X_39); |
| X_46 := algebra.selectNotNil(X_39); |
| X_52 := algebra.kunion(X_50,X_46); |
| X_6:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","facts",1); |
| X_9 := bat.reverse(X_6); |
| X_54 := algebra.kdifference(X_52,X_9); |
| X_55 := bat.reverse(X_54); |
| X_45:bat[:oid,:str] := sql.bind(X_2,"sys","facts","predicate",0,1,2); |
| X_49 := algebra.selectNotNil(X_45); |
| X_43:bat[:oid,:str] := sql.bind(X_2,"sys","facts","predicate",2,1,2); |
| X_51 := algebra.kdifference(X_49,X_43); |
| X_47 := algebra.selectNotNil(X_43); |
| X_53 := algebra.kunion(X_51,X_47); |
| X_57 := bat.reverse(X_53); |
| X_10:bat[:oid,:str] := sql.bind(X_2,"sys","facts","predicate",1); |
| X_11 := algebra.selectNotNil(X_10); |
| X_58 := bat.reverse(X_11); |
| X_14 := mat.pack(X_55,X_57,X_58); |
| X_15 := algebra.kunique(X_14); |
| X_16 := bat.reverse(X_15); |
| X_17 := aggr.count(X_16); |
| exit X_61; |
| sql.exportValue(1,"sys.facts","L6","wrd",32,0,6,X_17,""); |
| end s2_1; |
+---------------------------------------------------------------------------------------------------------------------------+
EXPLAIN SELECT COUNT(*) FROM (SELECT DISTINCT(predicate) from facts) AS b;
+---------------------------------------------------------------------------------------------------------------------------+
| mal |
+===========================================================================================================================+
| function user.s3_1{autoCommit=true}():void; |
| X_17 := nil:wrd; |
| barrier X_71 := language.dataflow(); |
| X_2 := sql.mvc(); |
| X_44:bat[:oid,:str] := sql.bind(X_2,"sys","facts","predicate",0,0,2); |
| X_39:bat[:oid,:str] := sql.bind(X_2,"sys","facts","predicate",2,0,2); |
| X_46 := algebra.kdifference(X_44,X_39); |
| X_48 := algebra.kunion(X_46,X_39); |
| X_6:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","facts",1); |
| X_9 := bat.reverse(X_6); |
| X_50 := algebra.kdifference(X_48,X_9); |
| (X_51,X_52) := group.done(X_50); |
| X_57 := bat.mirror(X_51); |
| X_59 := algebra.leftjoin(X_57,X_50); |
| X_45:bat[:oid,:str] := sql.bind(X_2,"sys","facts","predicate",0,1,2); |
| X_43:bat[:oid,:str] := sql.bind(X_2,"sys","facts","predicate",2,1,2); |
| X_47 := algebra.kdifference(X_45,X_43); |
| X_49 := algebra.kunion(X_47,X_43); |
| (X_53,X_54) := group.done(X_49); |
| X_60 := bat.mirror(X_53); |
| X_62 := algebra.leftjoin(X_60,X_49); |
| X_10:bat[:oid,:str] := sql.bind(X_2,"sys","facts","predicate",1); |
| (X_55,X_56) := group.done(X_10); |
| X_63 := bat.mirror(X_55); |
| X_65 := algebra.leftjoin(X_63,X_10); |
| X_66 := mat.pack(X_59,X_62,X_65); |
| (ext30,grp28) := group.done(X_66); |
| X_15 := bat.mirror(ext30); |
| X_68 := algebra.leftjoin(X_15,X_50); |
| X_69 := algebra.leftjoin(X_15,X_49); |
| X_70 := algebra.leftjoin(X_15,X_10); |
| X_67 := mat.pack(X_68,X_69,X_70); |
| X_16 := algebra.leftjoin(X_15,X_67); |
| X_17 := aggr.count(X_16); |
| exit X_71; |
| sql.exportValue(1,"sys.b","L7","wrd",32,0,6,X_17,""); |
| end s3_1; |
+---------------------------------------------------------------------------------------------------------------------------+
Reproducible: Always
### Steps to Reproduce:
1. Start mclient with the database with the table described in the details.
2. Execute the queries (as stated in the details).
3. Compare the time it takes.
### Actual Results:
Query 1
+------+
| L4 |
+======+
| 277 |
+------+
1 tuple (4.5s)
Query 2
+------+
| L5 |
+======+
| 277 |
+------+
1 tuple (141.970ms)
### Expected Results:
I hoped that the two queries would be answered in the same time.
mclient, the MonetDB interactive terminal (Aug2011)
support for command-line editing compiled-in
MonetDB 5 server v11.5.1 "Aug2011" (32-bit, 32-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2011 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 1.0GiB available memory, 2 available cpu cores
Libraries:
libpcre: 7.8 2008-09-05 (compiled with 7.8)
openssl: OpenSSL 0.9.8k 25 Mar 2009 (compiled with OpenSSL 0.9.8k 25 Mar 2009)
libxml2: 2.7.6 (compiled with 2.7.6)
Compiled by: root@dev.monetdb.org (i486-pc-linux-gnu)
Compilation: gcc -O3 -fomit-frame-pointer -pipe -Wall
Linking : /usr/bin/ld -Wl,-Bsymbolic-functions
## Comment 16341
Date: 2011-09-28 14:22:30 +0200
From: @njnes
checked in a fix in Aug2011, please test.
## Comment 16358
Date: 2011-09-30 11:26:32 +0200
From: @sjoerdmullender
Please reopen if you still encounter issues.
| Slow execution of COUNT in combination with DISTINCT | https://api.github.com/repos/MonetDB/MonetDB/issues/2890/comments | 0 | 2020-11-30T11:46:15Z | 2024-06-27T11:53:15Z | https://github.com/MonetDB/MonetDB/issues/2890 | 753,408,742 | 2,890 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-09-20 11:39:58 +0200
From: Rémy Chibois <<rchibois>>
To: clients devs <<bugs-clients>>
Version: 11.5.1 (Aug2011) [obsolete]
Last updated: 2011-09-30 10:58:43 +0200
## Comment 16311
Date: 2011-09-20 11:39:58 +0200
From: Rémy Chibois <<rchibois>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_1) AppleWebKit/534.48.3 (KHTML, like Gecko) Version/5.1 Safari/534.48.3
Build Identifier:
When using DBI's fetchall_arrayref on a large result set (which spans multiple Mapi blocks), Mapi.pm's getBlock subroutine is erasing the initial count property (set on line 302 for selects) with the next block line count (line 287). That is:
--> query sent to server
--> getBlock called to fetch first reply (reply of type "1", for "initial" I presume...)
----> line 297, count property set to line count in block
----> line 302, count property set to query result line count
--> processing of rows in that block
--> getBlock called to fetch second/next reply block (reply of type "6", for "subsequent" I presume)
----> line 297, what was set in 302 is erased with the second block line count
----> as the reply is not of type "1", the total count is lost, and getReply is confused about when to stop
Reproducible: Always
### Steps to Reproduce:
1. Set-up a sample database with some data that would not fit in a single reply block size
(my db has 60 columns et 50001 rows, mostly text and numbers, for a flat TSV size of 20MB)
2. Use the following Perl script:
==============
!/usr/bin/env perl
use strict;
use warnings;
$|++;
use DBI();
my $dbh = DBI->connect(
'dbi:monetdb:database=testdb', 'monetdb', 'monetdb'
);
my $query = qq{
SELECT
*
FROM
sample_table
};
my $sth = $dbh->prepare($query);
$sth->execute;
Here we tell DBI to fetch at most 10000 lines (out of 50001 available)
my $r = $sth->fetchall_arrayref(undef, 10000);
Print "200 rows" in my case, should print "10000 rows"
print scalar(@{$r}) . " rows\n";
$dbh->disconnect();
==============
### Actual Results:
200 rows
### Expected Results:
10000 rows
Naively commenting out line 287 seems to solve this issue, but I haven't looked everywhere else if the count property is used in other ways
## Comment 16323
Date: 2011-09-23 21:13:46 +0200
From: @grobian
I think this is slightly better:
diff --git a/clients/perl/Mapi.pm b/clients/perl/Mapi.pm
--- a/clients/perl/Mapi.pm
+++ b/clients/perl/Mapi.pm
@@ -284,9 +284,9 @@ sub getBlock {
my @chars = split(//, $header);
$self->{id} = -1;
- $self->{count} = scalar(@{$self->{lines}});
+ $self->{count} = -1;
$self->{nrcols} = -1;
- $self->{replysize} = $self->{count};
+ $self->{replysize} = scalar(@{$self->{lines}});
$self->{active} = 0;
$self->{skip} = 0; next+skip is current result row
$self->{next} = 0; all done
That is, I don't see the need to set count to the number of returned rows, but the replysize might be necessary. I'll commit this patch, feedback appreciated.
## Comment 16324
Date: 2011-09-23 21:15:27 +0200
From: @grobian
the self->{count} should of course only be removed, not set to -1
## Comment 16325
Date: 2011-09-23 21:20:27 +0200
From: @grobian
Changeset [7dc06e743f7c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=7dc06e743f7c) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7dc06e743f7c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7dc06e743f7c)
Changeset description:
Mapi.pm: don't overwrite count for continuation blocks
As suggested by R?my Chibois, don't always just overwrite the count
field, since it may wipe out the correct value for mapi continuation
blocks (with larger results). Bug #2889
## Comment 16326
Date: 2011-09-23 21:21:52 +0200
From: @grobian
Not closing, should add a test first
## Comment 16330
Date: 2011-09-27 16:19:32 +0200
From: @grobian
Changeset [58ba9e3940e6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=58ba9e3940e6) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=58ba9e3940e6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=58ba9e3940e6)
Changeset description:
add test for bug #2889
Thanks R?my Chibois for his initial test snippet
## Comment 16331
Date: 2011-09-27 17:27:30 +0200
From: @grobian
Changeset [688922b03344](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=688922b03344) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=688922b03344](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=688922b03344)
Changeset description:
test DBD-bug-2889.pl: increase output sent to client
Make sure we trigger the block problem by sending all columns to the
client instead of just one.
## Comment 16348
Date: 2011-09-30 10:58:43 +0200
From: @grobian
Released in Aug2011-SP1
| Mapi::getBlock is erasing query count on second call | https://api.github.com/repos/MonetDB/MonetDB/issues/2889/comments | 0 | 2020-11-30T11:46:11Z | 2024-06-27T11:53:14Z | https://github.com/MonetDB/MonetDB/issues/2889 | 753,408,708 | 2,889 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-09-19 22:21:27 +0200
From: @grobian
To: SQL devs <<bugs-sql>>
Version: 11.5.1 (Aug2011) [obsolete]
Last updated: 2011-09-30 10:58:46 +0200
## Comment 16305
Date: 2011-09-19 22:21:27 +0200
From: @grobian
Testing stops with defunct processes (mserver5?) repeatedly in Aug2011 and default branches on all combinations on sparc (s32, s48, s64) for test/null/null_in_case.sql. As a result, everything hangs for eternity, since Python apparently doesn't receive/handle the signal its child crashed/cored.
As a result, entire testing blocks until the appropriate preap or kills of Mtest.py are done on the build sun.
## Comment 16306
Date: 2011-09-20 09:45:46 +0200
From: @sjoerdmullender
I think the null_in_case test is probably a red herring.
The very first sql test already ends in a timeout, as do many other tests (at least on GNU-Solaris-sparc).
## Comment 16310
Date: 2011-09-20 11:15:20 +0200
From: @grobian
Very well possible. However, after hours (and even days) of waiting, all testing runs always hang at this particular test.
## Comment 16312
Date: 2011-09-20 21:22:50 +0200
From: @sjoerdmullender
Changeset [9d839b4fd018](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=9d839b4fd018) 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=9d839b4fd018](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9d839b4fd018)
Changeset description:
When clearing variables also clear eolife field.
Not clearing the field could cause a bogus dependency in the dataflow
scheduler which in turn could cause a circular dependecy among
instructions.
This fixes bug #2865 and the server timeouts of bug #2888.
(The problem that Mtest.py has with all the hanging servers is not
solved but may not be a problem anymore.)
## Comment 16314
Date: 2011-09-21 11:08:39 +0200
From: @sjoerdmullender
Changeset [02c039857104](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=02c039857104) 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=02c039857104](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=02c039857104)
Changeset description:
Add assertions about inter-instruction dependencies.
Instructions should only depend on earlier instructions.
These asserts would probably have made finding the problem with bugs
2865 and 2888 a lot easier...
## Comment 16353
Date: 2011-09-30 10:58:46 +0200
From: @grobian
Released in Aug2011-SP1
| test/null/null_in_case.sql hangs server | https://api.github.com/repos/MonetDB/MonetDB/issues/2888/comments | 0 | 2020-11-30T11:46:09Z | 2024-06-27T11:53:13Z | https://github.com/MonetDB/MonetDB/issues/2888 | 753,408,691 | 2,888 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-09-19 18:06:59 +0200
From: Alfred Nordman <<alfred.nordman>>
To: SQL devs <<bugs-sql>>
Version: 11.3.7 (Apr2011-SP2) [obsolete]
CC: @njnes
Last updated: 2011-09-30 10:58:43 +0200
## Comment 16303
Date: 2011-09-19 18:06:59 +0200
From: Alfred Nordman <<alfred.nordman>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.163 Safari/535.1
Build Identifier:
Server returns division by zero, even though it should not divide at 0.
Reproducible: Always
### Steps to Reproduce:
Create table t (c int);
Insert into t values (0);
select min (case when "c" = 0 then 4 else 3/c end) from t;
drop table t;
### Actual Results:
ArithmeticException:batcalc./:Division by zero
### Expected Results:
a result set of one row, with the value 4
MonetDB 5 server v11.3.1 "Apr2011" (64-bit, 64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2011 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 8.0GiB available memory
Libraries:
libpcre: 8.10 2010-06-25
openssl: OpenSSL 1.0.0a 1 Jun 2010
libxml2: 2.7.7
Compiled by: sjoerd@LAB03 (x86_64-pc-winnt)
Compilation: cl -GF -W3 -wd4273 -wd4102 -MD -nologo -Ox
Linking : cl -GF -W3 -wd4273 -wd4102 -MD -nologo -Ox
"C:\Program Files\MonetDB\MonetDB5\bin\mserver5.exe" --set "prefix=C:\Program Files\MonetDB\MonetDB5" --set "exec_prefix=C:\Program Files\MonetDB\MonetDB5" "--dbfarm=C:\Users\Rjacober\AppData\Roaming\MonetDB5\dbfarm"
## Comment 16304
Date: 2011-09-19 20:11:31 +0200
From: @sjoerdmullender
Bug #2822 is very similar, but that one has been fixed.
## Comment 16307
Date: 2011-09-20 10:15:10 +0200
From: @njnes
only case expressions in projections where correctly rewritten for div by zero problems. Now also group by is handled.
## Comment 16308
Date: 2011-09-20 10:15:26 +0200
From: @njnes
added test div_by_zero.Bug-2887.sql
## Comment 16309
Date: 2011-09-20 10:21:02 +0200
From: @njnes
Changeset [0c1fd1092f5d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0c1fd1092f5d) 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=0c1fd1092f5d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0c1fd1092f5d)
Changeset description:
fixed bug #2887, also rel_groupby is now rewritten for case/div by zero problems.
## Comment 16349
Date: 2011-09-30 10:58:43 +0200
From: @grobian
Released in Aug2011-SP1
| Division by zero error, when should not divide at 0 | https://api.github.com/repos/MonetDB/MonetDB/issues/2887/comments | 0 | 2020-11-30T11:46:06Z | 2024-06-27T11:53:12Z | https://github.com/MonetDB/MonetDB/issues/2887 | 753,408,661 | 2,887 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-09-19 16:33:28 +0200
From: @sjoerdmullender
To: clients devs <<bugs-clients>>
Version: 11.11.7 (Jul2012-SP1)
CC: @hannesmuehleisen
Last updated: 2013-01-22 09:29:14 +0100
## Comment 16300
Date: 2011-09-19 16:33:28 +0200
From: @sjoerdmullender
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.22) Gecko/20110906 Fedora/3.6.22-1.fc14 Firefox/3.6.22
Build Identifier:
The test for bug #2885 shows that the Perl driver emits a warning about the catalog parameter not being used. There are in fact several places in clients/perl/DBD/monetdb.pm where this message is generated.
Do we really need this?
Reproducible: Always
### Steps to Reproduce:
1.Mtest.py -p sql test/BugTracker-2011 perl-table_info.Bug-2885
2.examine error output.
### Actual Results:
DBD::monetdb::db table_info warning: Catalog parameter '' ignored at .../sql/test/BugTracker-2011/Tests/perl-table_info.Bug-2885.pl line 12.
### Expected Results:
No such message.
## Comment 17655
Date: 2012-08-24 14:50:24 +0200
From: @sjoerdmullender
Jul2012-SP1 has been released.
## Comment 18060
Date: 2012-11-27 13:45:11 +0100
From: @hannesmuehleisen
Perl client has been updated to only accept an empty catalog name and not throw a warning message (changeset 46007:b2c3569ac520), test case for bug (sql/test/BugTracker-2011/Tests/perl-table_info.Bug-2885.pl) has been updated, now as follows:
my $sth = $dbh->table_info('', '%', '%'); must not write to stderr
my $sth2 = $dbh->table_info('foo', '%', '%'); has to write to stderr for violating the "empty catalog name" rule
## Comment 18189
Date: 2012-11-28 13:45:05 +0100
From: @hannesmuehleisen
Changeset [ac0fb4766f46](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ac0fb4766f46) made by Hannes Muehleisen <hannes@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ac0fb4766f46](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ac0fb4766f46)
Changeset description:
Update for test case sql/test/BugTracker-2011/Tests/perl-table_info.Bug-2885.pl - Bug #2886
## Comment 18191
Date: 2012-11-28 13:45:09 +0100
From: @hannesmuehleisen
Changeset [092bbe1f3ee6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=092bbe1f3ee6) made by Hannes Muehleisen <hannes@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=092bbe1f3ee6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=092bbe1f3ee6)
Changeset description:
Update for test case sql/test/BugTracker-2011/Tests/perl-table_info.Bug-2885.pl - Bug #2886 - Approved outputs
## Comment 18374
Date: 2013-01-22 09:29:14 +0100
From: @sjoerdmullender
Oct2012-SP3 has been released.
| warning: Catalog parameter '' ignored | https://api.github.com/repos/MonetDB/MonetDB/issues/2886/comments | 0 | 2020-11-30T11:46:03Z | 2024-06-27T11:53:11Z | https://github.com/MonetDB/MonetDB/issues/2886 | 753,408,616 | 2,886 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-09-16 19:53:03 +0200
From: Rémy Chibois <<rchibois>>
To: clients devs <<bugs-clients>>
Version: 11.5.1 (Aug2011) [obsolete]
Last updated: 2011-09-30 10:58:46 +0200
## Comment 16291
Date: 2011-09-16 19:53:03 +0200
From: Rémy Chibois <<rchibois>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_1) AppleWebKit/534.48.3 (KHTML, like Gecko) Version/5.1 Safari/534.48.3
Build Identifier:
When requesting database tables information through a database handle:
$dbh->table_info('', '%', '%)
The DBD::monetdb::db::monetdb_table_info subroutine issues an incorrect query to list schemas and tables (resulting in an error an no results)
I found the query to be:
==========
select cast( null as varchar( 128 ) ) as table_cat
, s."name" as table_schem
, t."name" as table_name
, case
when t."istable" = true and t."system" = false and t."temporary" = 0 then cast('TABLE' as varchar( 254 ) )
when t."istable" = true and t."system" = true and t."temporary" = 0 then cast('SYSTEM TABLE' as varchar( 254 ) )
when t."istable" = true and t."system" = false and t."temporary" = 1 then cast('LOCAL TEMPORARY' as varchar( 254 ) )
when t."istable" = false then cast('VIEW' as varchar( 254 ) )
else cast('INTERNAL TABLE TYPE' as varchar( 254 ) )
end as table_type
, cast( null as varchar( 254 ) ) as remarks
from sys."schemas" s
, sys."tables" t
where t."schema_id" = s."id"
==========
This query fails because there's no (more) column "istable" in "sys.tables".
Reproducible: Always
### Steps to Reproduce:
The following snippet will reproduce the error:
===========
!/usr/bin/env perl
use strict;
use warnings;
$|++;
use DBI();
my $dbh = DBI->connect('dbi:monetdb:database=testdb', 'monetdb', 'monetdb');
my $sth = $dbh->table_info('', '%', '%');
===========
### Actual Results:
DBD::monetdb::db table_info failed: SELECT: no such column 't.istable' at /opt/local/lib/perl5/vendor_perl/5.12.3/darwin-thread-multi-2level/MonetDB/CLI/MapiPP.pm line 120
### Expected Results:
Table and schemas information as per DBI specs.
## Comment 16292
Date: 2011-09-17 11:02:13 +0200
From: Rémy Chibois <<rchibois>>
Created attachment 74
Proposed patch to fix table type match
> Attached file: [DBD-monetdb-table-type.patch](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2885_DBD-monetdb-table-type.patch_74) (text/plain, 870 bytes)
> Description: Proposed patch to fix table type match
## Comment 16295
Date: 2011-09-19 10:27:36 +0200
From: @sjoerdmullender
Changeset [4eafa029d4c9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4eafa029d4c9) 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=4eafa029d4c9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4eafa029d4c9)
Changeset description:
Fixed DBD::monetdb table_info and tabletype_info.
This fixes bug #2885. With thanks to Rémy Chibois.
## Comment 16299
Date: 2011-09-19 16:28:08 +0200
From: @sjoerdmullender
Changeset [a2d6c9a4fb34](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a2d6c9a4fb34) 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=a2d6c9a4fb34](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a2d6c9a4fb34)
Changeset description:
Added test for bug #2885.
## Comment 16301
Date: 2011-09-19 16:34:31 +0200
From: @sjoerdmullender
Seems to work now.
## Comment 16327
Date: 2011-09-24 18:05:19 +0200
From: @drstmane
Changeset [2f69e26d0fb6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2f69e26d0fb6) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2f69e26d0fb6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2f69e26d0fb6)
Changeset description:
added filter to ignore path name
in error message of test for bug #2885
(sql/test/BugTracker-2011/Tests/perl-table_info.Bug-2885.pl)
## Comment 16354
Date: 2011-09-30 10:58:46 +0200
From: @grobian
Released in Aug2011-SP1
## Comment 16391
Date: 2011-10-10 16:28:05 +0200
From: @sjoerdmullender
Changeset [a0e7a98f0051](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a0e7a98f0051) 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=a0e7a98f0051](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a0e7a98f0051)
Changeset description:
Improve filter pattern.
This way sql test/BugTracker-2011 perl-table_info.Bug-2885 also
reports success on Windows.
This is the same fix as changeset [ae36d70ba744](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ae36d70ba744) applied to a different
filter.
## Comment 18188
Date: 2012-11-28 13:45:05 +0100
From: @hannesmuehleisen
Changeset [ac0fb4766f46](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ac0fb4766f46) made by Hannes Muehleisen <hannes@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ac0fb4766f46](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ac0fb4766f46)
Changeset description:
Update for test case sql/test/BugTracker-2011/Tests/perl-table_info.Bug-2885.pl - Bug #2886
## Comment 18190
Date: 2012-11-28 13:45:09 +0100
From: @hannesmuehleisen
Changeset [092bbe1f3ee6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=092bbe1f3ee6) made by Hannes Muehleisen <hannes@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=092bbe1f3ee6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=092bbe1f3ee6)
Changeset description:
Update for test case sql/test/BugTracker-2011/Tests/perl-table_info.Bug-2885.pl - Bug #2886 - Approved outputs
| DBD::monetdb table_info error | https://api.github.com/repos/MonetDB/MonetDB/issues/2885/comments | 0 | 2020-11-30T11:45:59Z | 2024-06-27T11:53:10Z | https://github.com/MonetDB/MonetDB/issues/2885 | 753,408,592 | 2,885 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-09-16 19:43:21 +0200
From: Rémy Chibois <<rchibois>>
To: clients devs <<bugs-clients>>
Version: 11.5.1 (Aug2011) [obsolete]
Last updated: 2011-09-30 10:58:44 +0200
## Comment 16289
Date: 2011-09-16 19:43:21 +0200
From: Rémy Chibois <<rchibois>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_1) AppleWebKit/534.48.3 (KHTML, like Gecko) Version/5.1 Safari/534.48.3
Build Identifier:
Using those two modules, a lot of warnings about incorrect syntax pop up.
Also, GetInfo.pm uses an incorrect number of arguments while trying to sprintf a version string.
Please find below a patch trying to solve these problems:
===================
diff -Nur -x '*.am' -x '*.in' -x '*.msc' -x README -x '*Tests*' perl/DBD/monetdb/GetInfo.pm perl-patches/DBD/monetdb/GetInfo.pm
--- perl/DBD/monetdb/GetInfo.pm 2011-09-01 15:11:32.000000000 +0200
+++ perl-patches/DBD/monetdb/GetInfo.pm 2011-09-16 19:13:16.000000000 +0200
@@ -22,7 +22,7 @@
my $sql_driver = 'monetdb';
my $sql_ver_fmt = '%02d.%02d.%04d'; ODBC version string: ..
-my $sql_driver_ver = sprintf $sql_ver_fmt, split(/\./, $DBD::monetdb::VERSION);
+my $sql_driver_ver = sprintf $sql_ver_fmt, split(/\./, $DBD::monetdb::VERSION), 0;
my @Keywords = qw(
BOOLEAN
diff -Nur -x '*.am' -x '*.in' -x '*.msc' -x README -x '*Tests*' perl/Mapi.pm perl-patches/Mapi.pm
--- perl/Mapi.pm 2011-09-01 15:11:33.000000000 +0200
+++ perl-patches/Mapi.pm 2011-09-16 19:14:16.000000000 +0200
@@ -25,8 +25,8 @@
sub pass_chal {
my ($passwd, @challenge) = @_;
- if (@challenge[2] == 9) {
- my $pwhash = @challenge[5];
+ if ($challenge[2] == 9) {
+ my $pwhash = $challenge[5];
if ($pwhash eq 'SHA512') {
$passwd = sha512_hex($passwd);
} elsif ($pwhash eq 'SHA256') {
@@ -39,33 +39,33 @@
warn "unsupported password hash: ".$pwhash;
return;
}
- } elsif (@challenge[2] == 8) {
+ } elsif ($challenge[2] == 8) {
can leave passwd cleartext
} else {
- warn "unsupported protocol version: ".@challenge[2];
+ warn "unsupported protocol version: ".$challenge[2];
return;
}
- my @cyphers = split(/,/, @challenge[3]);
+ my @cyphers = split(/,/, $challenge[3]);
my $chal;
foreach (@cyphers) {
if ($_ eq 'SHA512') {
- $chal = "{$_}".sha512_hex($passwd.@challenge[0]);
+ $chal = "{$_}".sha512_hex($passwd.$challenge[0]);
last;
} elsif ($_ eq 'SHA256') {
- $chal = "{$_}".sha256_hex($passwd.@challenge[0]);
+ $chal = "{$_}".sha256_hex($passwd.$challenge[0]);
last;
} elsif ($_ eq 'SHA1') {
- $chal = "{$_}".sha1_hex($passwd.@challenge[0]);
+ $chal = "{$_}".sha1_hex($passwd.$challenge[0]);
last;
} elsif ($_ eq 'MD5') {
- $chal = "{$_}".md5_hex($passwd.@challenge[0]);
+ $chal = "{$_}".md5_hex($passwd.$challenge[0]);
last;
}
}
if (!$chal) {
we assume v8's "plain"
- $chal = "{plain}".$passwd.@challenge[0];
+ $chal = "{plain}".$passwd.$challenge[0];
}
return $chal;
@@ -118,7 +118,7 @@
$self->{socket}->close;
print "Following redirect: $prompt\n" if ($self->{trace});
my @tokens = split(/[\n\/:\?]+/, $prompt); dirty, but it's Perl anyway
- return new Mapi(@tokens[3], @tokens[4], $user, $passwd, $lang, @tokens[5], $trace);
+ return new Mapi($tokens[3], $tokens[4], $user, $passwd, $lang, $tokens[5], $trace);
} elsif ($prompt =~ /^\^mapi:merovingian:\/\/proxy/) {
proxied redirect
do {
@@ -240,7 +240,7 @@
my $row = $self->{lines}[$self->{next}++];
my @chars = split(//, $row);
- if (@chars[0] eq '!') {
+ if ($chars[0] eq '!') {
$self->error($row);
my $i = 1;
while ($self->{lines}[$i] =~ '!') {
@@ -249,11 +249,11 @@
}
$self->{active} = 0;
return -1
- } elsif (@chars[0] eq '&') {
+ } elsif ($chars[0] eq '&') {
not expected
- } elsif (@chars[0] eq '%') {
+ } elsif ($chars[0] eq '%') {
header line
- } elsif (@chars[0] eq '[') {
+ } elsif ($chars[0] eq '[') {
row result
$self->{row} = $row;
if ($self->{nrcols} < 0) {
@@ -261,13 +261,13 @@
$self->{nrcols}++;
}
$self->{active} = 1;
- } elsif (@chars[0] eq '=') {
+ } elsif ($chars[0] eq '=') {
xml result line
$self->{row} = substr($row, 1); skip =
$self->{active} = 1;
- } elsif (@chars[0] eq '^') {
+ } elsif ($chars[0] eq '^') {
^ redirect, ie use different server
- } elsif (@chars[0] eq '') {
+ } elsif ($chars[0] eq '') {
warnings etc, skip, and return what follows
return $self->getRow;
}
@@ -293,9 +293,9 @@
$self->{offset} = 0;
$self->{hdrs} = [];
- if (@chars[0] eq '&') {
- if (@chars[1] eq '1' || @chars[1] eq 6) {
- if (@chars[1] eq '1') {
+ if ($chars[0] eq '&') {
+ if ($chars[1] eq '1' || $chars[1] eq 6) {
+ if ($chars[1] eq '1') {
&1 id result-count nr-cols rows-in-this-block
my ($dummy,$id,$cnt,$nrcols,$replysize) = split(' ', $header);
$self->{id} = $id;
@@ -321,7 +321,7 @@
$self->{row} = $self->{lines}[$self->{next}++];
$self->{active} = 1;
- } elsif (@chars[1] eq '2') { updates
+ } elsif ($chars[1] eq '2') { updates
my ($dummy,$cnt) = split(' ', $header);
$self->{count} = $cnt;
$self->{nrcols} = 1;
@@ -329,16 +329,16 @@
$self->{row} = "" . $cnt;
$self->{next} = $cnt; all done
return -2;
- } elsif (@chars[1] eq '3') { transaction
+ } elsif ($chars[1] eq '3') { transaction
nothing todo
- } elsif (@chars[1] eq '4') { auto_commit
+ } elsif ($chars[1] eq '4') { auto_commit
my ($dummy,$ac) = split(' ', $header);
if ($ac eq 't') {
$self->{auto_commit} = 1;
} else {
$self->{auto_commit} = 0;
}
- } elsif (@chars[1] eq '5') { prepare
+ } elsif ($chars[1] eq '5') { prepare
my ($dummy,$id,$cnt,$nrcols,$replysize) = split(' ', $header);
TODO parse result, rows (type, digits, scale)
$self->{count} = $cnt;
===================
Reproducible: Always
### Steps to Reproduce:
1. Connect to database using DBI (e.g.: code from "perldoc DBD::monetdb")
2. Issue a: $dbh->table_info('', '%', '%');
## Comment 16290
Date: 2011-09-16 19:45:17 +0200
From: Rémy Chibois <<rchibois>>
(my apologies for the inline patch)
## Comment 16293
Date: 2011-09-17 11:09:26 +0200
From: Rémy Chibois <<rchibois>>
Created attachment 75
Proposed patch to fix syntax and sprintf warnings
Added patch as attachment
> Attached file: [MonetDB-11.5.1-MonetDB-CLI.patch](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2884_MonetDB-11.5.1-MonetDB-CLI.patch_75) (text/plain, 5411 bytes)
> Description: Proposed patch to fix syntax and sprintf warnings
## Comment 16296
Date: 2011-09-19 10:27:37 +0200
From: @sjoerdmullender
Changeset [4c0e28fea94d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4c0e28fea94d) 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=4c0e28fea94d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4c0e28fea94d)
Changeset description:
Perl: Fixed a bunch of syntax errors.
This fixes bug #2884. With thanks to Rémy Chibois.
## Comment 16302
Date: 2011-09-19 16:37:50 +0200
From: @sjoerdmullender
The test for bug #2885 is also a test for this bug.
## Comment 16351
Date: 2011-09-30 10:58:44 +0200
From: @grobian
Released in Aug2011-SP1
| Mapi.pm and GetInfo.pm syntax fixes for array usage | https://api.github.com/repos/MonetDB/MonetDB/issues/2884/comments | 0 | 2020-11-30T11:45:56Z | 2024-06-27T11:53:09Z | https://github.com/MonetDB/MonetDB/issues/2884 | 753,408,564 | 2,884 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-09-15 15:45:55 +0200
From: @sjoerdmullender
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @mlkersten, @yzchang
Blocker for: #2882
Last updated: 2012-11-27 14:44:10 +0100
## Comment 16225
Date: 2011-09-15 15:45:55 +0200
From: @sjoerdmullender
Created attachment 73
trace of last insert query
On a multicore system, dataflow can cause that the subject query inserts more into the table than it should.
Using mserver5 --forcemito do:
create table t (i int);
insert into t values (1);
insert into t (select * from t);
insert into t (select * from t);
After these queries there should be 4 elements in t, but I get 6. The reason is that the insertions table is appended to first (assignment to X_44 in trace) before that same table is used to find old inserted values that have to be copied (assignment to X_9 in trace).
> Attached file: [@2](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2883_@2_73) (application/octet-stream, 2187 bytes)
> Description: trace of last insert query
## Comment 16227
Date: 2011-09-15 23:39:42 +0200
From: @mlkersten
The cause are the multiple mitosis plans, who each
insert the tuples. All updates should be collected
in a temporary BAT before being inserted into the persistent version.
## Comment 16228
Date: 2011-09-16 10:13:42 +0200
From: @sjoerdmullender
Changeset [7e2a2426e682](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=7e2a2426e682) 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=7e2a2426e682](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7e2a2426e682)
Changeset description:
Partial transplant of changeset [fbe3bda547b2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=fbe3bda547b2) .
This fixes bug #2883.
## Comment 16286
Date: 2011-09-16 15:48:57 +0200
From: @sjoerdmullender
Changeset [c22ffd42d642](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c22ffd42d642) 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=c22ffd42d642](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c22ffd42d642)
Changeset description:
Added changelog entries for bug #2882 and bug #2883.
## Comment 16287
Date: 2011-09-16 15:49:50 +0200
From: @sjoerdmullender
The bug has been fixed. No separate test is needed since the test for bug #2882 covers this issue as well.
## Comment 16297
Date: 2011-09-19 15:00:18 +0200
From: @grobian
Could this fix be the cause of orphans on intel Darwin, and complete defunct processes on Solaris? (I just manually killed Python/Mtest, it doesn't seem to reap its childeren correctly)
## Comment 16350
Date: 2011-09-30 10:58:44 +0200
From: @grobian
Released in Aug2011-SP1
## Comment 18090
Date: 2012-11-27 14:44:10 +0100
From: @yzchang
Covered by the test for bug #2882:
sql/test/BugTracker-2011/Tests/delete-large-table.Bug-2882.sql
| insert into t (select * from t) bogus in multithreaded execution | https://api.github.com/repos/MonetDB/MonetDB/issues/2883/comments | 0 | 2020-11-30T11:45:53Z | 2024-06-27T11:53:08Z | https://github.com/MonetDB/MonetDB/issues/2883 | 753,408,532 | 2,883 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-09-14 17:55:17 +0200
From: seriousman
To: SQL devs <<bugs-sql>>
Version: 11.5.1 (Aug2011) [obsolete]
Depends on: #2883
Last updated: 2011-09-30 10:58:45 +0200
## Comment 16219
Date: 2011-09-14 17:55:17 +0200
From: seriousman
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110816 Fedora/3.6.20-1.fc14 Firefox/3.6.20
Build Identifier:
I have some problems for deleting reccords on a table of 20000000 rows.
I've created a table 'test' and inserted in one operation 20000000 rows on this table.
There is only one column in this table : 'id' and values are 'BIGINT' from 1 to 20000000.
When I delete first row of the table 'test' it work, but when I try to delete the last reccord, it seem the delete did not work:
I try to insert data on other table with 'order by desc' and it's the opposite (can't delete value 1).
Reproducible: Always
### Steps to Reproduce:
1.create table test(id bigint);
2.insert into test(id) SELECT ROW_NUMBER () OVER () FROM bigtable limit 20000000; (generate a serie of BIGINT from 1 to 20000000)
3.delete from test where id = 1;
4.delete from test where id = 20000000;
### Actual Results:
select count(*) from test
19999999 rows
### Expected Results:
select count(*) from test
19999998 rows
I never encounter this problem on table with less of 2 millions reccords.
I try to insert 1 million reccord step by step, the bug appear at 2 million (nearly).
Sometimes, after fews manipulations on data (insert/delete), the problem disapear but appear again when I stop and restart the database.
I think it's related to the BAT files and transaction process, but I need some specific information in order to know what to do to solve this bug.
## Comment 16223
Date: 2011-09-15 10:19:28 +0200
From: @sjoerdmullender
I can reproduce the problem in the Aug2011 branch.
A select * from test where id = {1, 20000000}; (two individual queries) do give the expected results before and after the deletes: one value before, no value after.
The query
select * from test where id in (1, 20000000);
gives an unexpected result: the value 20000000.
## Comment 16224
Date: 2011-09-15 11:04:56 +0200
From: @sjoerdmullender
Changeset [08a38dbbbd3f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=08a38dbbbd3f) 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=08a38dbbbd3f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=08a38dbbbd3f)
Changeset description:
Added test for bug #2882.
This test runs fine when running single threaded.
It results in a timeout and totally bogus results when running
multi-threaded.
## Comment 16226
Date: 2011-09-15 15:47:09 +0200
From: @sjoerdmullender
The test that I checked in fails among other reasons because of bug #2883.
## Comment 16277
Date: 2011-09-16 15:10:39 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 16285
Date: 2011-09-16 15:48:57 +0200
From: @sjoerdmullender
Changeset [c22ffd42d642](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c22ffd42d642) 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=c22ffd42d642](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c22ffd42d642)
Changeset description:
Added changelog entries for bug #2882 and bug #2883.
## Comment 16288
Date: 2011-09-16 15:50:52 +0200
From: @sjoerdmullender
Changeset [88185cfea41c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=88185cfea41c) fixes the problem.
## Comment 16352
Date: 2011-09-30 10:58:45 +0200
From: @grobian
Released in Aug2011-SP1
| Delete of some records don't work on Monetdb | https://api.github.com/repos/MonetDB/MonetDB/issues/2882/comments | 0 | 2020-11-30T11:45:50Z | 2024-06-27T11:53:07Z | https://github.com/MonetDB/MonetDB/issues/2882 | 753,408,493 | 2,882 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-09-14 16:32:45 +0200
From: seriousman
To: SQL devs <<bugs-sql>>
Version: 11.3.7 (Apr2011-SP2) [obsolete]
Last updated: 2011-09-14 17:53:01 +0200
## Comment 16218
Date: 2011-09-14 16:32:45 +0200
From: seriousman
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.22) Gecko/20110905 Ubuntu/10.10 (maverick) Firefox/3.6.22
Build Identifier:
test
Reproducible: Always
### Steps to Reproduce:
test
### Actual Results:
test
### Expected Results:
test
test
| title test | https://api.github.com/repos/MonetDB/MonetDB/issues/2881/comments | 0 | 2020-11-30T11:45:48Z | 2024-06-28T13:20:02Z | https://github.com/MonetDB/MonetDB/issues/2881 | 753,408,466 | 2,881 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-09-14 15:06:10 +0200
From: @sjoerdmullender
To: SQL devs <<bugs-sql>>
Version: 11.5.1 (Aug2011) [obsolete]
Last updated: 2011-09-14 15:06:26 +0200
## Comment 16216
Date: 2011-09-14 15:06:10 +0200
From: @sjoerdmullender
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110816 Fedora/3.6.20-1.fc14 Firefox/3.6.20
Build Identifier:
this is a test, please ignore
Reproducible: Always
### Steps to Reproduce:
1.enter details
2.click on submit
3.
### Actual Results:
to be verified
### Expected Results:
bug entered.
| test, please ignore | https://api.github.com/repos/MonetDB/MonetDB/issues/2880/comments | 0 | 2020-11-30T11:45:45Z | 2024-06-28T13:20:02Z | https://github.com/MonetDB/MonetDB/issues/2880 | 753,408,439 | 2,880 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-09-13 12:59:32 +0200
From: andrij.usov
To: SQL devs <<bugs-sql>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @mlkersten, @njnes
Last updated: 2011-09-30 10:58:46 +0200
## Comment 16214
Date: 2011-09-13 12:59:32 +0200
From: andrij.usov
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0.2) Gecko/20100101 Firefox/6.0.2
Build Identifier:
DB dump and the SQL Query
-------------------------
Query:
SELECT M_1.VC_4 AS V_1, M_1.VC_3 AS V_2, M_1.VC_1 AS V_3, M_1.VC_2 AS V_4
FROM
( SELECT COALESCE(T_2.o, T_4.o) AS VC_1, COALESCE(T_3.o, T_5.o) AS VC_2, T_1.o AS VC_3, T_1.s AS VC_4
FROM
( SELECT *
FROM Triples AS T_1
WHERE ( T_1.p = '<http://example/p>' )
) AS T_1
LEFT OUTER JOIN
Triples AS T_2
INNER JOIN
Triples AS T_3
ON ( T_2.p = '<http://example/q1>'
AND T_3.p = '<http://example/q2>'
AND T_2.s = T_3.s )
ON ( T_1.o = T_2.s )
LEFT OUTER JOIN
Triples AS T_4
INNER JOIN
Triples AS T_5
ON ( T_4.p = '<http://example/q2>'
AND T_5.p = '<http://example/q2>'
AND T_4.s = T_5.s )
ON ( T_1.o = T_4.s
AND ( ( T_2.o IS NULL ) OR ( T_2.o = T_4.o ) )
AND ( ( T_3.o IS NULL ) OR ( T_3.o = T_5.o ) ) )
) AS M_1;
---------------------------------
DB dump:
CREATE TABLE triples (
s varchar(255),
p varchar(255),
o varchar(255),
PRIMARY KEY (s, p, o)
);
INSERT INTO triples (s, p, o) VALUES
('<http://example/a>', '<http://example/q1>', '<http://example/z11>'),
('<http://example/a>', '<http://example/q1>', '<http://example/z12>'),
('<http://example/a>', '<http://example/q2>', '<http://example/z21>'),
('<http://example/a>', '<http://example/q2>', '<http://example/z22>'),
('<http://example/b>', '<http://example/q2>', '<http://example/y21>'),
('<http://example/b>', '<http://example/q2>', '<http://example/y22>'),
('<http://example/c>', '<http://example/r>', '<http://example/rr>'),
('<http://example/x>', '<http://example/p>', '<http://example/a>'),
('<http://example/x>', '<http://example/p>', '<http://example/b>'),
('<http://example/x>', '<http://example/p>', '<http://example/c>');
Reproducible: Always
### Steps to Reproduce:
1. Load DB Dump
2. Run SQL query
3. Enjoy
### Actual Results:
5 Rows:
<http://example/x> <http://example/b> <http://example/y21> <http://example/y21>
<http://example/x> <http://example/b> <http://example/y21> <http://example/y22>
<http://example/x> <http://example/b> <http://example/y22> <http://example/y21>
<http://example/x> <http://example/b> <http://example/y22> <http://example/y22>
<http://example/x> <http://example/c> <null> <null>
### Expected Results:
9 Rows:
<http://example/x> <http://example/a> <http://example/z11> <http://example/z21>
<http://example/x> <http://example/a> <http://example/z11> <http://example/z22>
<http://example/x> <http://example/a> <http://example/z12> <http://example/z21>
<http://example/x> <http://example/a> <http://example/z12> <http://example/z22>
<http://example/x> <http://example/b> <http://example/y21> <http://example/y21>
<http://example/x> <http://example/b> <http://example/y21> <http://example/y22>
<http://example/x> <http://example/b> <http://example/y22> <http://example/y21>
<http://example/x> <http://example/b> <http://example/y22> <http://example/y22>
<http://example/x> <http://example/c> NULL NULL
## Comment 16215
Date: 2011-09-14 14:51:54 +0200
From: @mlkersten
It looks like an operator priority issue in combination with presumed interpretation semantics.
In general, the join order and nesting should not affect the outcome.
The best way forward is to simply split the query into multiple easier pieces.
If my hypothesis is correct, then a fix will be included in the next bug-fix release.
## Comment 16217
Date: 2011-09-14 15:11:55 +0200
From: andrij.usov
(In reply to comment 1)
> It looks like an operator priority issue in combination with presumed
> interpretation semantics.
> In general, the join order and nesting should not affect the outcome.
> The best way forward is to simply split the query into multiple easier pieces.
> If my hypothesis is correct, then a fix will be included in the next bug-fix
> release.
The query has been automatically produced by a framework. It is impossible to significantly modify it without re-developing large parts of this framework.
## Comment 16220
Date: 2011-09-14 18:29:00 +0200
From: @mlkersten
The please inform us and the community, which general available framework you have been using to generate these queries. As you can imagine, a bug resulting from an open-source and widely used package receives more attention.
## Comment 16221
Date: 2011-09-14 19:53:55 +0200
From: @njnes
seems a bug in the outer join with 'or'
## Comment 16222
Date: 2011-09-14 20:41:37 +0200
From: andrij.usov
(In reply to comment 3)
> The please inform us and the community, which general available framework you
> have been using to generate these queries. As you can imagine, a bug resulting
> from an open-source and widely used package receives more attention.
We are trying integrate Jena (Semantic Web framework for Java) (http://jena.sourceforge.net/).
## Comment 16282
Date: 2011-09-16 15:10:41 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 16294
Date: 2011-09-17 12:53:13 +0200
From: @mlkersten
MonetDB is not integrated (yet) with Jena. We appreciate if you take the lead and run the SDB test set to assess what features are missing and/or related bugs.
The outcome will be judged on impact and scheduled appropriately for resolution.
## Comment 16298
Date: 2011-09-19 16:01:37 +0200
From: @sjoerdmullender
Changeset [248294d05358](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=248294d05358) 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=248294d05358](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=248294d05358)
Changeset description:
Added test for bug #2879.
## Comment 16328
Date: 2011-09-25 10:55:31 +0200
From: @njnes
fixed the implementation of outerjoins
## Comment 16355
Date: 2011-09-30 10:58:46 +0200
From: @grobian
Released in Aug2011-SP1
| A SELECT query fails to produce some results | https://api.github.com/repos/MonetDB/MonetDB/issues/2879/comments | 0 | 2020-11-30T11:45:42Z | 2024-06-27T11:53:04Z | https://github.com/MonetDB/MonetDB/issues/2879 | 753,408,397 | 2,879 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-09-13 12:32:37 +0200
From: @grobian
To: SQL devs <<bugs-sql>>
Version: 11.3.7 (Apr2011-SP2) [obsolete]
Last updated: 2011-09-13 12:43:21 +0200
## Comment 16209
Date: 2011-09-13 12:32:37 +0200
From: @grobian
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en; rv:1.9.2.22) Gecko/20110908 Camino/2.1b2 (like Firefox/3.6.22)
Build Identifier:
Some people from Fraunhofer claim our bugzilla doesn't allow to attach files. Let's see.
Reproducible: Always
### Steps to Reproduce:
1. file a bug #2. upload sql script
3. upload screenshots ( :( )
### Actual Results:
apparently it doesn't work
### Expected Results:
it just works as expected
I'm just trying to find problems here. We've had other people attaching files to bugs in the past, so I don't expect any problem.
## Comment 16210
Date: 2011-09-13 12:37:40 +0200
From: @grobian
Created attachment 71
80KiB png image
This is an image, e.g. binary attachment of 1.2MiB.
> Attached file: [SOMAL-class.PNG](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2878_SOMAL-class.PNG_71) (image/png, 74304 bytes)
> Description: 80KiB png image
## Comment 16211
Date: 2011-09-13 12:38:57 +0200
From: @grobian
Created attachment 72
an XSLT sheet
a text attachment
> Attached file: [sf2bz.xslt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2878_sf2bz.xslt_72) (application/octet-stream, 8082 bytes)
> Description: an XSLT sheet
## Comment 16212
Date: 2011-09-13 12:39:33 +0200
From: @grobian
Comment on attachment 71
80KiB png image
correction, 1.2MiB is too much for a binary file, so I had to pick another image.
## Comment 16213
Date: 2011-09-13 12:41:22 +0200
From: @grobian
Attaching files works like a charm for me.
| attachment test, please ignore | https://api.github.com/repos/MonetDB/MonetDB/issues/2878/comments | 0 | 2020-11-30T11:45:39Z | 2024-06-28T13:20:01Z | https://github.com/MonetDB/MonetDB/issues/2878 | 753,408,366 | 2,878 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-09-09 14:41:18 +0200
From: @sjoerdmullender
To: SQL devs <<bugs-sql>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @njnes
Last updated: 2011-09-30 10:58:47 +0200
## Comment 16202
Date: 2011-09-09 14:41:18 +0200
From: @sjoerdmullender
This table definition causes a failed assertion:
create table t (
c interval hour to second default interval '1:00:00' hour to second
);
mserver5: sql/server/sql_atom.c:329: atom2sql: Assertion `a->data.vtype == 13' failed.
## Comment 16203
Date: 2011-09-09 14:48:38 +0200
From: @sjoerdmullender
This works:
create table t (
c interval hour to second default 3600
);
and that is also basically what msqldump produces.
## Comment 16204
Date: 2011-09-11 13:04:24 +0200
From: @njnes
Changeset [e43ef2096b48](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e43ef2096b48) 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=e43ef2096b48](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e43ef2096b48)
Changeset description:
fixed crash in atom2sql, see bug #2877
## Comment 16205
Date: 2011-09-11 13:05:45 +0200
From: @njnes
crash is fixed. But both versions will now insert incorrect intervals into the c column. (3600 * the required value)
## Comment 16316
Date: 2011-09-21 12:43:57 +0200
From: @sjoerdmullender
Changeset [9b531a83053d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=9b531a83053d) 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=9b531a83053d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9b531a83053d)
Changeset description:
Added test for bug #2877.
## Comment 16317
Date: 2011-09-21 16:16:59 +0200
From: @sjoerdmullender
Changeset [e45a31dccee5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e45a31dccee5) 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=e45a31dccee5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e45a31dccee5)
Changeset description:
Fixed a bunch of interrelated problems with default interval values.
The value that is stored in the default column of the sys.columns
table for an interval column is the number of units in the right-most
field of the interval (i.e. minutes in an INTERVAL DAY TO MINUTE). So
make sure we multiply the value with the factor for that right-most
field when inserting into a table.
Also, we now declare the global SQL variable current_timezone as an
INTERVAL HOUR TO SECOND.
This fixes bug #2877.
## Comment 16356
Date: 2011-09-30 10:58:47 +0200
From: @grobian
Released in Aug2011-SP1
| assertion failed when creating table with default interval | https://api.github.com/repos/MonetDB/MonetDB/issues/2877/comments | 0 | 2020-11-30T11:45:36Z | 2024-06-27T11:53:02Z | https://github.com/MonetDB/MonetDB/issues/2877 | 753,408,337 | 2,877 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-09-08 15:34:51 +0200
From: @skinkie
To: MonetDB5 devs <<bugs-monetdb5>>
Version: -- development
CC: @yzchang
Last updated: 2012-11-27 14:46:16 +0100
## Comment 16201
Date: 2011-09-08 15:34:51 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.24 Safari/535.1
Build Identifier:
Usually I see a "Segmentation Fault" which results in wondering what query actually resulted in this fault. Wouldn't it be helpful to add a Segmentation Fault handler, so it would actually print out a backtrace, when gdb is not connected?
The implementation seems to be trivial; and could be very helpful with finding rare bugs;
http://stackoverflow.com/questions/77005/how-to-generate-a-stacktrace-when-my-gcc-c-app-crashes
Reproducible: Always
## Comment 17908
Date: 2012-11-07 19:41:31 +0100
From: @grobian
we accept patches (properly guarded because this isn't "trivial" on all platforms that we support)
## Comment 18091
Date: 2012-11-27 14:46:16 +0100
From: @yzchang
No possible to add test for this bug
| Implement segv handler, to automatically backtrace (a development build) | https://api.github.com/repos/MonetDB/MonetDB/issues/2876/comments | 0 | 2020-11-30T11:45:34Z | 2024-06-28T13:40:47Z | https://github.com/MonetDB/MonetDB/issues/2876 | 753,408,310 | 2,876 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-09-05 16:08:55 +0200
From: @sjoerdmullender
To: SQL devs <<bugs-sql>>
Version: 11.5.7 (Aug2011-SP2) [obsolete]
CC: @njnes
Last updated: 2011-11-22 13:55:54 +0100
## Comment 16183
Date: 2011-09-05 16:08:55 +0200
From: @sjoerdmullender
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110816 Fedora/3.6.20-1.fc14 Firefox/3.6.20
Build Identifier:
The database is not properly initialized in certain situations. See below.
Reproducible: Always
### Steps to Reproduce:
1.start mserver5 with new (i.e. not yet existing) database
2.stop mserver5
3.start mserver5 again with same database
4.connect to mserver5 with mclient
5.dump database with \D
### Actual Results:
Non-empty database:
START TRANSACTION;
SET SCHEMA "sys";
CREATE FUNCTION env () RETURNS TABLE( name varchar(1024), value varchar(2048)) EXTERNAL NAME sql.sql_environment;
CREATE FUNCTION var() RETURNS TABLE( name varchar(1024)) EXTERNAL NAME sql.sql_variables;
CREATE FUNCTION db_users () RETURNS TABLE( name varchar(2048)) EXTERNAL NAME sql.db_users;
COMMIT;
### Expected Results:
Empty database:
START TRANSACTION;
COMMIT;
When mclient connects, the server executes the function SQLinitClient(). This function uses the global variable SQLnewcatalog to determine whether to execute the "createdb" scripts. The variable is ultimately initialized by the call to logger_funcs.log_isnew(). The second time the server is run, log_isnew() says that it is not new anymore, causing createdb to be skipped.
## Comment 16206
Date: 2011-09-11 13:08:13 +0200
From: @njnes
We could verify (using a query on the base tables) if initialisation is done.
For example simply check for some default function should be enough.
## Comment 16479
Date: 2011-10-27 10:59:18 +0200
From: @sjoerdmullender
Changeset [4751ff65d8e8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4751ff65d8e8) 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=4751ff65d8e8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4751ff65d8e8)
Changeset description:
Execute initialization code when sys.systemfunctions does not exist.
This fixes bug #2875.
## Comment 16480
Date: 2011-10-27 13:10:44 +0200
From: @sjoerdmullender
Changeset [129f02da694c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=129f02da694c) 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=129f02da694c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=129f02da694c)
Changeset description:
Added test for bug #2875.
## Comment 16481
Date: 2011-10-27 13:11:07 +0200
From: @sjoerdmullender
Bug is fixed.
## Comment 16565
Date: 2011-11-22 13:55:54 +0100
From: @grobian
Fixed in Aug2011-SP3
| incomplete database initialization | https://api.github.com/repos/MonetDB/MonetDB/issues/2875/comments | 0 | 2020-11-30T11:45:31Z | 2024-06-27T11:53:00Z | https://github.com/MonetDB/MonetDB/issues/2875 | 753,408,273 | 2,875 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-09-04 14:07:44 +0200
From: @sjoerdmullender
To: SQL devs <<bugs-sql>>
Version: 11.7.5 (Dec2011) [obsolete]
Last updated: 2011-12-08 16:42:08 +0100
## Comment 16182
Date: 2011-09-04 14:07:44 +0200
From: @sjoerdmullender
When upgrading from, say, the Aug2011 branch to the current default branch, second interval values have to be multiplied by 1000 since the columns now contain milliseconds instead of seconds.
## Comment 16636
Date: 2011-12-08 16:39:45 +0100
From: @sjoerdmullender
Changeset [f2b586f1fb51](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f2b586f1fb51) 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=f2b586f1fb51](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f2b586f1fb51)
Changeset description:
Fixed second interval upgrade code.
This fixes bug #2874.
## Comment 16637
Date: 2011-12-08 16:42:08 +0100
From: @sjoerdmullender
Changeset [95bc181cd423](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=95bc181cd423) was the first part of the fix for this bug, changeset [f2b586f1fb51](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f2b586f1fb51) completed the fix.
No test since we can't test upgrades yet.
| database conversion needed for second interval types | https://api.github.com/repos/MonetDB/MonetDB/issues/2874/comments | 0 | 2020-11-30T11:45:28Z | 2024-06-27T11:52:59Z | https://github.com/MonetDB/MonetDB/issues/2874 | 753,408,234 | 2,874 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-30 23:43:26 +0200
From: @yzchang
To: SQL devs <<bugs-sql>>
Version: 11.5.3 (Aug2011-SP1) [obsolete]
Last updated: 2012-01-26 15:31:55 +0100
## Comment 16179
Date: 2011-08-30 23:43:26 +0200
From: @yzchang
Some queries envovling time values with precision produce wrong results.
$ mserver5 --set mapi_port=50001
MonetDB 5 server v11.3.8
This is an unreleased version
Serving database 'demo', using 4 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 7.749 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2011 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:50001/
MonetDB/GIS module loaded
MonetDB/SQL module loaded
> SQL catalog created, loading sql scripts once
>
sql>create table t (tm time);
operation successful
sql>insert into t values ('20:04:04.847');
1 affected row (1.176ms)
sql>select tm + interval '0' second from t;
+-----------------+
| sql_add_tm |
+=================+
| 20:04:04.847000 |
+-----------------+
1 tuple (1.673ms)
-- The result should be: 20:04:04
-- since the default precision of TIME is 0
sql>select tm + interval '0.333' second(5) from t;
+-----------------+
| sql_add_tm |
+=================+
| 20:04:04.847000 |
+-----------------+
1 tuple (1.669ms)
-- should be: 20:04:04.333000
sql>select time '20:04:04.847' - time '20:04:04.947';
+----------------------+
| sql_sub_single_value |
+======================+
| 00:00:00.847000 |
+----------------------+
1 tuple (0.771ms)
-- should be: [000000000000](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=000000000000)
sql>select time(5) '20:04:04.947' - time(5) '20:04:04.847';
+----------------------+
| sql_sub_single_value |
+======================+
| 00:00:00.947000 |
+----------------------+
1 tuple (0.944ms)
-- should be: 00:00:00.100000
## Comment 16180
Date: 2011-08-30 23:53:01 +0200
From: @yzchang
Changeset [f2acd8b59d7a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f2acd8b59d7a) made by Jennie Zhang <y.zhang@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f2acd8b59d7a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f2acd8b59d7a)
Changeset description:
Added test for bug #2873
## Comment 16181
Date: 2011-08-31 18:56:29 +0200
From: @njnes
Changeset [2d9beef3e6f5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2d9beef3e6f5) 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=2d9beef3e6f5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2d9beef3e6f5)
Changeset description:
changes/fixes
interval seconds now stores milli - seconds
handle sub-second fractions
TIME, TIMESTAMP and INTERVAL (second) have time precision
time defaults to 0 (ie not smaller than seconds)
timestamp and interval default to 6 but monet only supports 3 (ie allways
3 zero's at the end)
fixes bug #2873 and old feature request 2415
## Comment 16270
Date: 2011-09-16 15:10:36 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 16389
Date: 2011-10-07 16:32:33 +0200
From: @sjoerdmullender
Niels implemented a fix for the next release.
## Comment 16814
Date: 2012-01-26 15:31:55 +0100
From: @sjoerdmullender
The Dec2011 version has been release, so declaring this bug as FIXED.
| SQL: time with precision | https://api.github.com/repos/MonetDB/MonetDB/issues/2873/comments | 0 | 2020-11-30T11:45:25Z | 2024-06-27T11:52:58Z | https://github.com/MonetDB/MonetDB/issues/2873 | 753,408,196 | 2,873 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-26 21:52:39 +0200
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
CC: @yzchang
Last updated: 2012-11-27 14:47:04 +0100
## Comment 16169
Date: 2011-08-26 21:52:39 +0200
From: @drstmane
While working fine on all other platforms,
test monetdb5/mal/Tests/pithole on 64-bit Windows when compiled with icc:
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=41607:701c0fa97235&module=monetdb5&targets=Int-WindowsXP-i386-propcheck,Mic-Windows2008-i386-propcheck-installer,Int-Windows2008-x86_64-propcheck-oid32,Int-Windows7-x86_64-propcheck,Mic-Windows2008-x86_64-propcheck-installer&order=platform,arch,compiler
http://monetdb.cwi.nl/testweb/tests/41607:701c0fa97235/Int-Windows2008-x86_64-propcheck-oid32/monetdb5/mTests/mal/pithole.out.diff.html
http://monetdb.cwi.nl/testweb/tests/41607:701c0fa97235/Int-Windows7-x86_64-propcheck/monetdb5/mTests/mal/pithole.out.diff.html
## Comment 16171
Date: 2011-08-26 21:57:28 +0200
From: @drstmane
In fact out 64-bit Windows machines are multi-core when the 32-bit one is single-core.
## Comment 16318
Date: 2011-09-21 17:21:23 +0200
From: @sjoerdmullender
The stackdepth check is (mal_interpreter.mx):
if (stk->calldepth > 256)
However, the icc-compiled version already crashes with stk->calldepth == 62.
The reason is probably because the Intel compiler allocates variables differently on the stack than do other compilers. For instance, if you have two blocks in a function that both declare local variables and that are not nested in each other (e.g.: { int i; ...} ... { int j; ...}) then icc on Windows will allocate space for both (sets of) variables, whereas other compilers will reuse the same stack space. This causes programs that are compiled with icc to run through their available stack space more quickly.
## Comment 17442
Date: 2012-07-11 12:44:51 +0200
From: @drstmane
While it still occured with the last Apr2012 nightly test run
(http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=44501:b490b640b431&module=monetdb5&targets=&order=platform,arch,compiler)
the problem does not appear with the Jul2012 branch / feature release, anymore:
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=44556:bccc66e2bdff&module=monetdb5&targets=&order=platform,arch,compiler
## Comment 17479
Date: 2012-07-17 13:54:30 +0200
From: @grobian
problem never occurred in any release
## Comment 18092
Date: 2012-11-27 14:47:04 +0100
From: @yzchang
This is about existing tests
| test monetdb5/mal/Tests/pithole fails with icc on 64-bit multi-threaded Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/2872/comments | 0 | 2020-11-30T11:45:23Z | 2024-06-27T11:52:57Z | https://github.com/MonetDB/MonetDB/issues/2872 | 753,408,158 | 2,872 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-24 09:15:58 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 11.5.1 (Aug2011) [obsolete]
Last updated: 2011-09-28 10:23:24 +0200
## Comment 16160
Date: 2011-08-24 09:15:58 +0200
From: @drstmane
When compiled with 32-bit using Clang on 64-bit Fedora,
several TPCH tests fail due to wrong arithmetics
and several other tests hang/timeout;
cf.,
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=41544:4b3e3e10e76f&module=sql&targets=Cla-Fedora-i386-propcheck,GNU-Fedora-i386-propcheck&order=platform,arch,compiler&diff
## Comment 16332
Date: 2011-09-28 10:23:24 +0200
From: @sjoerdmullender
Problem in clang, i.e. we can't do anything about it.
| wrong arithmetics and timeout with 32-bit Clang on 64-bit Fedora | https://api.github.com/repos/MonetDB/MonetDB/issues/2871/comments | 0 | 2020-11-30T11:45:20Z | 2024-06-28T13:20:00Z | https://github.com/MonetDB/MonetDB/issues/2871 | 753,408,113 | 2,871 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-24 07:58:37 +0200
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.7.5 (Dec2011) [obsolete]
CC: @njnes, @yzchang
Last updated: 2012-11-27 14:47:35 +0100
## Comment 16159
Date: 2011-08-24 07:58:37 +0200
From: @drstmane
While working fine when run single-threaded,
tests
sql/test/BugTracker-2009/Tests/lost_update.SF-2790020
sql/test/leaks/Tests/check0
fail when run multi-threaded.
## Comment 16343
Date: 2011-09-28 15:25:46 +0200
From: @njnes
this seems fixed?
## Comment 16441
Date: 2011-10-18 14:10:30 +0200
From: @drstmane
sql/test/BugTracker-2009/Tests/lost_update.SF-2790020 ssems to work fine, now.
sql/test/leaks/Tests/check0 still shows differences and seems to be(have) non-deterministic.
## Comment 16554
Date: 2011-11-13 09:46:45 +0100
From: @njnes
the leaks test uses direct access on the bbp. The operations done on the bbp do not have a global lock (ie we get 3 bats out as results out of the bbp functions, in the mean time the bbp changes..).
This basically requires a bbp table function on mal level.
## Comment 17017
Date: 2012-02-28 07:39:55 +0100
From: @drstmane
Both tests appear to work fine, now, also in multi-threaded cases.
## Comment 18093
Date: 2012-11-27 14:47:35 +0100
From: @yzchang
This is about existing tests
| tests sql/test/BugTracker-2009/Tests/lost_update.SF-2790020 & sql/test/leaks/Tests/check0 fail multi-threaded (only) | https://api.github.com/repos/MonetDB/MonetDB/issues/2870/comments | 0 | 2020-11-30T11:45:17Z | 2024-06-28T13:20:00Z | https://github.com/MonetDB/MonetDB/issues/2870 | 753,408,073 | 2,870 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-24 07:53:05 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 11.5.1 (Aug2011) [obsolete]
Last updated: 2011-09-16 15:04:29 +0200
## Comment 16157
Date: 2011-08-24 07:53:05 +0200
From: @drstmane
Several SQL test appear to crash the server on "algol" (Windows2008) and "gans" (WindowsXP), while working fine on "lab03" (Windows7).
Or is the pattern that "lab03" runs 64-bit with 32-bit OIDs, while "algol" & "gans" run 64-bit with 64-bit OIDs or 32-bit with 32-bit OIDs?
cf., e.g.,
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=41544:4b3e3e10e76f&module=sql&targets=Int-WindowsXP-i386-propcheck,Mic-Windows2008-i386-propcheck-installer,Int-Windows7-x86_64-propcheck-oid32,Mic-Windows7-x86_64-propcheck-oid32-installer,Int-Windows2008-x86_64-propcheck,Mic-Windows2008-x86_64-propcheck-installer&order=platform,arch,compiler
## Comment 16162
Date: 2011-08-25 22:02:47 +0200
From: @drstmane
Swapping targets x86_64-propcheck & x86_64-propcheck-oid32 between algol & lab03 confirms that the pattern is indeed that the tests cause a MonetDB server crash on "algol" (Windows2008) and "gans" (WindowsXP), while working fine on "lab03" (Windows7) --- independently of BIT and OID settings; cf.,
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=41593:ab2ce99c5b12&module=sql&targets=Int-WindowsXP-i386-propcheck,Mic-Windows2008-i386-propcheck-installer,Int-Windows2008-x86_64-propcheck-oid32,Mic-Windows7-x86_64-propcheck-oid32-installer,Int-Windows7-x86_64-propcheck,Mic-Windows2008-x86_64-propcheck-installer&order=platform,arch,compiler
## Comment 16164
Date: 2011-08-26 08:36:02 +0200
From: @drstmane
It appears that all tests that crash on algol (Windows2008) and gans (WindowsXP), but work fine on lab03 (Windows7),
contain a "LIKE" predicate in the query, i.e.,
there crashes might be related to evaluating LIKE predicates.
Do we use some external library like PCRE for this?
(I cannot tell, whether there are tests with a LIKE predicate that do work fine also on algol (Windows2008) and gans (WindowsXP).)
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=41593:ab2ce99c5b12&module=sql&targets=Int-WindowsXP-i386-propcheck,Mic-Windows2008-i386-propcheck-installer,Int-Windows2008-x86_64-propcheck-oid32,Mic-Windows7-x86_64-propcheck-oid32-installer,Int-Windows7-x86_64-propcheck,Mic-Windows2008-x86_64-propcheck-installer&order=platform,arch,compiler&diff
## Comment 16166
Date: 2011-08-26 08:39:41 +0200
From: @drstmane
See also bug #2868.
## Comment 16167
Date: 2011-08-26 11:37:27 +0200
From: @sjoerdmullender
Changeset [f00e5a515b79](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f00e5a515b79) 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=f00e5a515b79](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f00e5a515b79)
Changeset description:
Deal properly with "free"ing NULL pointers.
We use pcre_study() to improve matching. When we're done, we free the
result of pcre_study() using a call to my_pcre_free().
pcre_study() may return NULL if no state is needed for optimization of
the search pattern. Since we just pass the result of pcre_study()
around to other pcre functions, we don't really care about the result,
but we do have to free the memory by calling my_pcre_free.
However, my_pcre_free couldn't deal with NULL pointers, which caused a
crash.
We now check for NULL pointers in my_pcre_free.
This fixes bug #2869.
## Comment 16168
Date: 2011-08-26 21:47:04 +0200
From: @drstmane
Testing confirms the fix.
## Comment 16232
Date: 2011-09-16 15:04:29 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| SQL tests with "LIKE" crash on Windows2008 & WindowsXP while working fine on Windows7 | https://api.github.com/repos/MonetDB/MonetDB/issues/2869/comments | 0 | 2020-11-30T11:45:15Z | 2024-06-27T11:52:54Z | https://github.com/MonetDB/MonetDB/issues/2869 | 753,408,038 | 2,869 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-24 07:36:47 +0200
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @yzchang
Last updated: 2012-11-27 14:48:07 +0100
## Comment 16155
Date: 2011-08-24 07:36:47 +0200
From: @drstmane
While working fine on all non-Windows platforms,
tests monetdb5/mal/Tests/tst285 & monetdb5/mal/Tests/pithole
fail on some (though not all) Windows platforms
(I cannot recognized a clear pattern):
cf., e.g.,
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=41544:4b3e3e10e76f&module=monetdb5&targets=Int-WindowsXP-i386-propcheck,Mic-Windows2008-i386-propcheck-installer,Int-Windows7-x86_64-propcheck-oid32,Mic-Windows7-x86_64-propcheck-oid32-installer,Int-Windows2008-x86_64-propcheck,Mic-Windows2008-x86_64-propcheck-installer&order=platform,arch,compiler
## Comment 16163
Date: 2011-08-25 23:03:55 +0200
From: @drstmane
The patterns are as follows:
test monetdb5/mal/Tests/tst285 fails on "algol" (Windows2008) and "gans" (WindowsXP); see also bug #2869
test monetdb5/mal/Tests/pithole fails with Intel compiler (icc)
## Comment 16165
Date: 2011-08-26 08:39:21 +0200
From: @drstmane
test monetdb5/mal/Tests/tst285
uses
z1:= batstr.like_uselect(b,"%hel%");
and
z2:= pcre.uselect(".*[ly].*", b);
suggesting that LIKE / PCRE is indeed the problem;
see also bug #2869
## Comment 16170
Date: 2011-08-26 21:53:32 +0200
From: @drstmane
Changeset [f00e5a515b79](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f00e5a515b79) fixes test monetdb5/mal/Tests/tst285.
Test monetdb5/mal/Tests/pithole is filed as bug #2872.
## Comment 16229
Date: 2011-09-16 15:04:28 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 18094
Date: 2012-11-27 14:48:07 +0100
From: @yzchang
This is about existing tests.
| tests tst285 & pithole fail on some Windows platforms | https://api.github.com/repos/MonetDB/MonetDB/issues/2868/comments | 0 | 2020-11-30T11:45:12Z | 2024-06-27T11:52:53Z | https://github.com/MonetDB/MonetDB/issues/2868 | 753,408,014 | 2,868 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-24 07:33:57 +0200
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @yzchang
Last updated: 2012-11-27 14:48:32 +0100
## Comment 16154
Date: 2011-08-24 07:33:57 +0200
From: @drstmane
While working fine on all other nightly testing platforms,
the following three monetdb5 (MAL) tests fail on all multi-threaded Windows platforms:
monetdb5/modules/mal/Tests/remote99
monetdb5/tests/mapi/Tests/smack01
monetdb5/tests/mapi/Tests/smack01-slow
cf., e.g.,
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=41544:4b3e3e10e76f&module=monetdb5&targets=Int-WindowsXP-i386-propcheck,Mic-Windows2008-i386-propcheck-installer,Int-Windows7-x86_64-propcheck-oid32,Mic-Windows7-x86_64-propcheck-oid32-installer,Int-Windows2008-x86_64-propcheck,Mic-Windows2008-x86_64-propcheck-installer&order=platform,arch,compiler
## Comment 16156
Date: 2011-08-24 07:45:54 +0200
From: @drstmane
The same appears to hold for the following SQL tests:
sql/test/Tests/big-example
sql/test/mapi/Tests/smack01
sql/test/Skyserver/Tests/Skyserver_v6
## Comment 16342
Date: 2011-09-28 15:08:09 +0200
From: @sjoerdmullender
The problem has nothing to do with MonetDB and everything with Windows.
It also has nothing to do with the number of threads in the server or the number of cores in the system.
The problem is hostname resolution.
On gans, the Windows "/etc/hosts" file contains an entry
127.0.0.1 localhost
and therefore lookup is fast.
On lab03 we didn't have such an entry, so there lookup took exactly 1 second (some deliberate slowdown to prevent DoS attacks?). If we add the entry, lookup is fast.
On algol we did have the entry for 127.0.0.1, but in addition we had
::1 localhost
This also resulted in one lookup per second. Removing this entry also speeds things up.
My guess is, next time these tests will be fast.
## Comment 16344
Date: 2011-09-29 09:30:22 +0200
From: @sjoerdmullender
The following tests now work:
monetdb5/tests/mapi/Tests/smack01
monetdb5/tests/mapi/Tests/smack01-slow
sql/test/mapi/Tests/smack01
The following tests still time out on the two big Windows boxes:
monetdb5/modules/mal/Tests/remote99
sql/test/Tests/big-example
sql/test/Skyserver/Tests/Skyserver_v6
## Comment 16345
Date: 2011-09-29 12:37:16 +0200
From: @sjoerdmullender
Disabling IPv6 does wonders with these tests.
See http://support.microsoft.com/kb/929852 for information on how to disable IPv6. Basically, edit/add the key (DWORD 32)HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TCPIP6\Parameters\ -> DisabledComponents and set the value to (hexadecimal) ffffffff. Then finish by rebooting.
## Comment 16346
Date: 2011-09-30 09:32:29 +0200
From: @sjoerdmullender
This was fixed by disabling IPv6 on the Windows machines. The extra entry for localhost in the hosts file was a red herring.
## Comment 18095
Date: 2012-11-27 14:48:32 +0100
From: @yzchang
This is about existing tests.
| tests remote99, smack01 & smack01-slow hang (timeout) on multi-threaded Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/2867/comments | 0 | 2020-11-30T11:45:10Z | 2024-06-27T11:52:52Z | https://github.com/MonetDB/MonetDB/issues/2867 | 753,407,989 | 2,867 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-24 07:25:20 +0200
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @mlkersten, @yzchang
Last updated: 2012-11-27 14:48:51 +0100
## Comment 16153
Date: 2011-08-24 07:25:20 +0200
From: @drstmane
Test monetdb5/optimizer/Tests/dataflow.mal fails on all Windows & Solaris platforms of nightly testing, while working fine on all other platforms; cf., e.g.,
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=41503:fa813932a753&module=monetdb5&targets=GNU-Solaris-sparc,GNU-Solaris-sparcv9-oid32,GNU-Solaris-sparcv9,Int-WindowsXP-i386-propcheck,Mic-Windows2008-i386-propcheck-installer,Int-Windows7-x86_64-propcheck-oid32,Mic-Windows7-x86_64-propcheck-oid32-installer,Int-Windows2008-x86_64-propcheck,Mic-Windows2008-x86_64-propcheck-installer&order=platform,arch,compiler
## Comment 16158
Date: 2011-08-24 07:53:42 +0200
From: @mlkersten
The point select is different between the two tests. This may indicate that the random number generator produced different results. Test expanded with explicit random seed.
## Comment 16161
Date: 2011-08-24 22:38:34 +0200
From: @drstmane
Unfortunately, seeding the random number generator does not help; cf.,
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=41578:0dc2371c2a9c&module=monetdb5&targets=GNU-Solaris-sparc,GNU-Solaris-sparcv9-oid32,GNU-Solaris-sparcv9,Int-WindowsXP-i386-propcheck,Mic-Windows2008-i386-propcheck-installer,Int-Windows7-x86_64-propcheck-oid32,Mic-Windows7-x86_64-propcheck-oid32-installer,Int-Windows2008-x86_64-propcheck,Mic-Windows2008-x86_64-propcheck-installer&order=platform,arch,compiler
Apparently, the random number generators on Solaris & Windows work differently than on other systems.
If despite the different random numbers and different behavior still tests what it's intended to test, we could consider approving specific output for Windows & Solaris (hope the behavior will remain deterministic over time).
Otherwise, we should consider redesigning the test without using mmath.rand().
## Comment 16178
Date: 2011-08-27 22:44:55 +0200
From: @drstmane
The test now appears to work fine on all platforms.
## Comment 16234
Date: 2011-09-16 15:04:31 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 18096
Date: 2012-11-27 14:48:51 +0100
From: @yzchang
This is about existing tests.
| test monetdb5/optimizer/Tests/dataflow.mal fails on all Windows & Solaris (only) | https://api.github.com/repos/MonetDB/MonetDB/issues/2866/comments | 0 | 2020-11-30T11:45:07Z | 2024-06-27T11:52:51Z | https://github.com/MonetDB/MonetDB/issues/2866 | 753,407,957 | 2,866 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-22 21:22:14 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @mlkersten
Last updated: 2011-09-30 10:58:41 +0200
## Comment 16139
Date: 2011-08-22 21:22:14 +0200
From: @drstmane
When staring a 2-threaded mserver5 (e.g., on a 2-core machine or with --set gdk_nr_threads=2) with --forcemito (as Mtest.py does by default) on a virgin (empty, not yet existing) database,
the server appears to deadlock on the first SQL client (mclient [-lsql]) connect,
e.g., possibly during SQL catalog creation or alike.
It works fine without --forcemito, or single-threaded (--set gdk_nr_threads=1), or with more than 2 threads (also on a 2-core machine), or with MAL (mclient -lmal).
This might be the cause of the first test per directory timing out on our only two 2-core machines: "machoke" & "macbeth".
## Comment 16140
Date: 2011-08-22 21:25:03 +0200
From: @drstmane
The same happens on my dual-core x86_64 laptop running 64-bit Fedora 15;
macbeth runs Gentoo on dual-core PowerPC;
machoke runs FreeBSD on dual-core x86_64.
## Comment 16141
Date: 2011-08-22 21:31:51 +0200
From: @drstmane
This problem did not occur in the Apr2011 branch.
## Comment 16142
Date: 2011-08-22 21:58:04 +0200
From: @drstmane
Created attachment 66
GDB log
The attached GDB log shows that 3 threads, one "DFLOWscheduler", two "runDFLOWworker" appear to be hanging on the same MT_sema_down() (-> sem_wait()) in
1 0x00007ffff6ceca38 in q_dequeue (q=0x7fffdc1b43d8) at /net/rig.ins.cwi.nl/export/scratch0/manegold/Monet/HG/Aug2011/source/MonetDB/monetdb5/mal/mal_interpreter.mx:853
853 MT_sema_down(&q->s, "q_dequeue");
(gdb) li
848 static void *
849 q_dequeue(queue *q)
850 {
851 void *r = NULL;
852
853 MT_sema_down(&q->s, "q_dequeue");
854 MT_lock_set(&q->l, "q_dequeue");
855 assert(q->last > 0);
856 /* LIFO favors garbage collection */
857 r = q->data[--q->last];
> Attached file: [gdb.log](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2865_gdb.log_66) (text/plain, 16359 bytes)
> Description: GDB log
## Comment 16143
Date: 2011-08-23 11:30:45 +0200
From: @drstmane
The very same problem also occurs with the latest default branch
(1f711d88786c 41529 default tip).
## Comment 16144
Date: 2011-08-23 11:39:02 +0200
From: @drstmane
(At least) since this obscures our nightly testing, I consider this a "major" problem with "high" priority.
## Comment 16145
Date: 2011-08-23 16:57:53 +0200
From: @drstmane
Please note that the two worker thread semwait in a q_dequeue from the same empty "todo" queue, and the scheduler thread semwaits in a q_dequeue from the empty "done" queue, while no (other) thread is doing any work, let alone inserting anything in either of these empty queues.
## Comment 16146
Date: 2011-08-23 21:16:11 +0200
From: @grobian
it seems that exactly these two machines show also a large amount of orphan proceses (mserver5's) left behind after testing
## Comment 16147
Date: 2011-08-23 21:29:40 +0200
From: @mlkersten
Most likely a double execution of the same instruction (sql.bind), because the two workers do not use a lock around the list of pending instructions.
This potentially means that a worker and the scheduler, or two workers are picking the same instruction for execution.
The code fragment where it happens is localized using gdb, break in DFLOW scheduler and using MDBlist(cntxt,mb,0,0) to localize where execution is.
X_88:bat[:oid,:str] := sql.bind(X_1,"sys","_tables","name",0,0,2);
X_104 := algebra.uselect(X_88,"callhistory":str);
X_86:bat[:oid,:str] := sql.bind(X_1,"sys","_tables","name",2,0,2);
## Comment 16148
Date: 2011-08-23 22:35:38 +0200
From: @mlkersten
Aside from the small chance of concurrency conflict, it turns out that sql.init() was called twice. Both use the same MAL plan and the first execution correctly terminates. The second call hangs immediately upon entering the first dataflow block.
The second call of sql.init() was triggered by --dbinit="sql.start();", after removing it from the command line, all worked well (with some additional locks
around the shared structures)
## Comment 16149
Date: 2011-08-23 22:44:22 +0200
From: @mlkersten
For completeness, the dataflow scheduler thinks the last bind is the next instruction to be executed.
(gdb) call MDBlist(fs[0].cntxt, flow->status[0].mb,0,0)
function user.main():void;
X_11 := nil:bat[:oid,:oid];
X_43 := nil:int;
X_197 := nil:wrd;
X_191 := nil:bat[:oid,:bit];
barrier X_204 := language.dataflow();
X_1 := sql.mvc();
X_88:bat[:oid,:str] := sql.bind(X_1,"sys","_tables","name",0,0,2);
X_104 := algebra.uselect(X_88,"queryhistory":str);
X_86:bat[:oid,:str] := sql.bind(X_1,"sys","_tables","name",2,0,2);
the structures have been protected now with the global mal_contextlock, which did not resolve the issue, pointing into the direction of an error during the erroneous double sql.init.
## Comment 16150
Date: 2011-08-24 00:16:30 +0200
From: @drstmane
At the risk of causing more confusion rather than contributing useful information, but maybe this might be relevant and/or helpful:
- neither Mtest.py nor I use --dbinit="sql.start();", i.e., the problem also occurs without
- in my case, SQLinitEnvironment() (the implementation of sql.init()) is not executed at all before the server deadlocks
- my MonetDB does not show any MAL code:
Breakpoint 1, DFLOWscheduler (flow=0x7fffdc1abd68) at /net/rig.ins.cwi.nl/export/scratch0/manegold/Monet/HG/Aug2011/source/MonetDB/monetdb5/mal/mal_interpreter.mx:1254
1254 {
Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.6-1.fc14.1.x86_64 cyrus-sasl-lib-2.1.23-12.fc14.x86_64 geos-3.2.1-3.fc14.x86_64 glibc-2.12.90-21.x86_64 keyutils-libs-1.2-6.fc12.x86_64 krb5-libs-1.8.4-2.fc14.x86_64 libcom_err-1.41.12-6.fc14.x86_64 libcurl-7.21.0-8.fc14.x86_64 libgcc-4.5.1-4.fc14.x86_64 libidn-1.18-1.fc14.x86_64 libselinux-2.0.96-6.fc14.1.x86_64 libssh2-1.2.4-1.fc14.x86_64 libstdc++-4.5.1-4.fc14.x86_64 libxml2-2.7.7-3.fc14.x86_64 ncurses-libs-5.7-9.20100703.fc14.x86_64 nspr-4.8.8-1.fc14.x86_64 nss-3.12.10-1.fc14.x86_64 nss-softokn-freebl-3.12.10-1.fc14.x86_64 nss-util-3.12.10-1.fc14.x86_64 openldap-2.4.23-4.fc14.x86_64 openssl-1.0.0d-1.fc14.x86_64 pcre-8.10-1.fc14.x86_64 readline-6.1-2.fc14.x86_64 zlib-1.2.5-2.fc14.x86_64
(gdb) n
1255 int queued = 0, oldq = 0, last;
(gdb)
1256 int i,pc = 0;
(gdb)
1261 int todo = flow->stop - flow->start;
(gdb)
1262 str ret = MAL_SUCCEED;
(gdb)
1263 FlowStatus fs, f = 0;
(gdb)
1265 if (todo == 0)
(gdb)
1268 fs = flow->status;
(gdb)
1275 if (fs[0].cntxt->flags & timerFlag)
(gdb) call MDBlist(fs[0].cntxt, flow->status[0].mb,0,0)
$1 = 0x0
(gdb)
## Comment 16172
Date: 2011-08-27 00:53:26 +0200
From: @drstmane
For what it's worth:
On both a 4 core machine (my desktop) and a 12 core machine (scilens12),
the deadlocks repeatedly occur when mserver5 is started with --forcemito and
2, 5, 6, 7, 9, 12, 13, 14, 15, 16, 17, 21, 22, 23 threads;
while everything seems to work fine when mserver5 is started with --forcemito and
1, 3, 4, 8, 10, 11, 18, 19, 20, 24 threads.
## Comment 16173
Date: 2011-08-27 01:01:07 +0200
From: @drstmane
(the 12-core machine is scilens08, not scilens12)
## Comment 16174
Date: 2011-08-27 08:09:34 +0200
From: @mlkersten
It consistently hangs on reading the file 15_history.sql
## Comment 16175
Date: 2011-08-27 08:38:48 +0200
From: @mlkersten
The system hangs on any of the update statements in 15_history.sql during database creation stage. Taking the update statements out and immediately applying them after the scripts have been loaded does not give rise to the
reported problem.
It all points towards a race condition in the SQL catalog initalization.
## Comment 16176
Date: 2011-08-27 09:41:25 +0200
From: @drstmane
Nice catch. Thanks!
This patch seems to work as a temporary and local work-around:
diff -r [816d0923209e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=816d0923209e) sql/sql/15_history.sql
--- a/sql/sql/15_history.sql Sat Aug 27 08:15:25 2011 +0200
+++ b/sql/sql/15_history.sql Sat Aug 27 09:37:55 2011 +0200
@@ -23,6 +23,13 @@
-- Whenever a query is compiled and added to the cache, it is also entered
-- into the 'queryHistory' table using a hardwired call to 'keepQuery'.
+-- Temporary and locally disable mitosis to prevent yet undiscoved deadlock;
+-- cf., bug #2865 (http://bugs.monetdb.org/show_bug.cgi?id=2865)
+declare dft_opt string;
+set dft_opt = ( select optimizer );
+set optimizer = 'no_mitosis_pipe';
+-- cf., `set optimizer = dft_opt` at the end of this script
+
create table queryHistory(
id wrd primary key,
defined timestamp, -- when entered into the cache
@@ -110,4 +117,7 @@
delete from queryHistory;
end;
+-- cf., top of this script
+set optimizer = dft_opt;
+
-- set history=true;
## Comment 16177
Date: 2011-08-27 21:27:29 +0200
From: @drstmane
Changeset [0f8fa1998fee](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0f8fa1998fee) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0f8fa1998fee](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0f8fa1998fee)
Changeset description:
disable mitosis in 15_history.sql to prevent yet undiscoved deadlock;
this is merely a temporary local work-around for nightly testing
until bug #2865 is eventually fixed
## Comment 16313
Date: 2011-09-20 21:22:50 +0200
From: @sjoerdmullender
Changeset [9d839b4fd018](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=9d839b4fd018) 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=9d839b4fd018](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9d839b4fd018)
Changeset description:
When clearing variables also clear eolife field.
Not clearing the field could cause a bogus dependency in the dataflow
scheduler which in turn could cause a circular dependecy among
instructions.
This fixes bug #2865 and the server timeouts of bug #2888.
(The problem that Mtest.py has with all the hanging servers is not
solved but may not be a problem anymore.)
## Comment 16315
Date: 2011-09-21 11:08:39 +0200
From: @sjoerdmullender
Changeset [02c039857104](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=02c039857104) 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=02c039857104](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=02c039857104)
Changeset description:
Add assertions about inter-instruction dependencies.
Instructions should only depend on earlier instructions.
These asserts would probably have made finding the problem with bugs
2865 and 2888 a lot easier...
## Comment 16347
Date: 2011-09-30 10:58:41 +0200
From: @grobian
Released in Aug2011-SP1
| mserver5 --set gdk_nr_threads=2 --forcemito: deadlock during first SQL client connect on virgin (empty) DB | https://api.github.com/repos/MonetDB/MonetDB/issues/2865/comments | 0 | 2020-11-30T11:45:03Z | 2024-06-27T11:52:50Z | https://github.com/MonetDB/MonetDB/issues/2865 | 753,407,919 | 2,865 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-21 22:46:40 +0200
From: @sjoerdmullender
To: SQL devs <<bugs-sql>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @njnes
Last updated: 2011-08-22 08:46:48 +0200
## Comment 16122
Date: 2011-08-21 22:46:40 +0200
From: @sjoerdmullender
Recompile from scratch with current version (changeset cba704276ac9), no dbfarm/demo directory.
Start mserver5.
Start mclient.
Observe crash.
This is serious and needs to be fixed with the highest priority.
Debug excerpt:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe7b62700 (LWP 12811)]
0x00007fffe80a4694 in list_find_name (l=0xe0d878,
name=0xdbdbdbdbdbdbdbdb <Address 0xdbdbdbdbdbdbdbdb out of bounds>)
at /home/sjoerd/src/MonetDB/candidate/sql/storage/sql_catalog.c:39
39 if (name[0] == b->name[0] && strcmp(name, b->name) == 0) {
(gdb) p name
$1 = 0xdbdbdbdbdbdbdbdb <Address 0xdbdbdbdbdbdbdbdb out of bounds>
(gdb) bt
0 0x00007fffe80a4694 in list_find_name (l=0xe0d878,
name=0xdbdbdbdbdbdbdbdb <Address 0xdbdbdbdbdbdbdbdb out of bounds>)
at /home/sjoerd/src/MonetDB/candidate/sql/storage/sql_catalog.c:39
1 0x00007fffe80a463a in cs_find_name (cs=0xe0d4e8,
name=0xdbdbdbdbdbdbdbdb <Address 0xdbdbdbdbdbdbdbdb out of bounds>)
at /home/sjoerd/src/MonetDB/candidate/sql/storage/sql_catalog.c:26
2 0x00007fffe80a4b33 in find_sql_table_node (s=0xe0d4c8,
tname=0xdbdbdbdbdbdbdbdb <Address 0xdbdbdbdbdbdbdbdb out of bounds>, id=-1)
at /home/sjoerd/src/MonetDB/candidate/sql/storage/sql_catalog.c:159
3 0x00007fffe80a4b97 in find_sql_table (s=0xe0d4c8,
tname=0xdbdbdbdbdbdbdbdb <Address 0xdbdbdbdbdbdbdbdb out of bounds>)
at /home/sjoerd/src/MonetDB/candidate/sql/storage/sql_catalog.c:167
4 0x00007fffe8020fb1 in mvc_bind_table (m=0x7fffd8005468, s=0xe0d4c8,
tname=0xdbdbdbdbdbdbdbdb <Address 0xdbdbdbdbdbdbdbdb out of bounds>)
at /home/sjoerd/src/MonetDB/candidate/sql/server/sql_mvc.c:620
5 0x00007fffe7f9e2b8 in create_table_or_view (sql=0x7fffd8005468,
sname=0x7fffd8007c78 "sys", t=0x7fffd8177c98, temp=0)
at /home/sjoerd/src/MonetDB/candidate/sql/backends/monet5/sql.mx:1806
6 0x00007fffe7fa0620 in SQLcatalog (cntxt=0x606578, mb=0x7fffd80488a8,
stk=0x7fffd815d088, pci=0x7fffd815d418)
at /home/sjoerd/src/MonetDB/candidate/sql/backends/monet5/sql.mx:2298
7 0x00007ffff6cc9235 in runMALsequence (cntxt=0x606578, mb=0x7fffd80488a8,
startpc=1, stoppc=0, stk=0x7fffd815d088, env=0x0, pcicaller=0x0)
at /home/sjoerd/src/MonetDB/candidate/monetdb5/mal/mal_interpreter.mx:2066
8 0x00007ffff6cbc0e0 in runMAL (cntxt=0x606578, mb=0x7fffd80488a8,
startpc=1, mbcaller=0x0, env=0x0, pcicaller=0x0)
at /home/sjoerd/src/MonetDB/candidate/monetdb5/mal/mal_interpreter.mx:333
9 0x00007fffe7f8b995 in SQLstatementIntern (c=0x606578, expr=0x7fffd80075f8,
nme=0x7fffe80c2051 "sql.init", execute=1, output=0 '\000')
at /home/sjoerd/src/MonetDB/candidate/sql/backends/monet5/sql_scenario.c:695
10 0x00007fffe7f8ae92 in SQLinitClient (c=0x606578)
at /home/sjoerd/src/MonetDB/candidate/sql/backends/monet5/sql_scenario.c:453
11 0x00007ffff6c9e0b6 in runPhase (c=0x606578, phase=5)
at /home/sjoerd/src/MonetDB/candidate/monetdb5/mal/mal_scenario.c:541
12 0x00007ffff6c9e189 in runScenarioBody (c=0x606578)
at /home/sjoerd/src/MonetDB/candidate/monetdb5/mal/mal_scenario.c:575
13 0x00007ffff6c9e4a8 in runScenario (c=0x606578)
at /home/sjoerd/src/MonetDB/candidate/monetdb5/mal/mal_scenario.c:620
14 0x00007ffff6c9f5b2 in MSserveClient (dummy=0x606578)
at /home/sjoerd/src/MonetDB/candidate/monetdb5/mal/mal_session.c:467
15 0x000000372a407b31 in start_thread () from /lib64/libpthread.so.0
16 0x0000003729cdfd2d in clone () from /lib64/libc.so.6
## Comment 16123
Date: 2011-08-21 23:14:40 +0200
From: @njnes
fixed by reverting the leak fixes for the plans
## Comment 16130
Date: 2011-08-22 08:46:48 +0200
From: @grobian
(bug should not show up on any release notes list, since the code in question was never released)
| crash on first connect with fresh database | https://api.github.com/repos/MonetDB/MonetDB/issues/2864/comments | 0 | 2020-11-30T11:45:01Z | 2024-06-27T11:52:49Z | https://github.com/MonetDB/MonetDB/issues/2864 | 753,407,885 | 2,864 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-21 09:15:59 +0200
From: @mlkersten
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.9.7 (Apr2012-SP2) [obsolete]
CC: @yzchang
Last updated: 2012-11-27 14:50:34 +0100
## Comment 16116
Date: 2011-08-21 09:15:59 +0200
From: @mlkersten
Compared to the Apr2011 there is more memory leakage.
A few 'harmless' leakages where known. It seems that at least the alloca removal was incomplete in terms of freeing stack administration space (tst912)
tst016.test.valgrind.err:==19684== 48 bytes in 1 blocks are definitely lost in loss record 2,224 of 4,095
tst041.test.valgrind.err:==19864== 24 bytes in 1 blocks are definitely lost in loss record 738 of 4,097
tst041.test.valgrind.err:==19864== 32 bytes in 1 blocks are definitely lost in loss record 1,478 of 4,097
tst041.test.valgrind.err:==19864== 48 bytes in 2 blocks are definitely lost in loss record 2,226 of 4,097
tst061.test.valgrind.err:==19994== 24 bytes in 1 blocks are definitely lost in loss record 738 of 4,095
tst2500.test.valgrind.err:==20516== 32 bytes in 1 blocks are definitely lost in loss record 1,480 of 4,109
tst2500.test.valgrind.err:==20516== 32 bytes in 1 blocks are definitely lost in loss record 1,481 of 4,109
tst2500.test.valgrind.err:==20516== 32 bytes in 1 blocks are definitely lost in loss record 1,482 of 4,109
tst2500.test.valgrind.err:==20516== 32 bytes in 1 blocks are definitely lost in loss record 1,483 of 4,109
tst2500.test.valgrind.err:==20516== 48 bytes in 1 blocks are definitely lost in loss record 2,232 of 4,109
tst2500.test.valgrind.err:==20516== 48 bytes in 1 blocks are definitely lost in loss record 2,233 of 4,109
tst2501.test.valgrind.err:==20522== 32 bytes in 1 blocks are definitely lost in loss record 1,480 of 4,109
tst2501.test.valgrind.err:==20522== 32 bytes in 1 blocks are definitely lost in loss record 1,481 of 4,109
tst2501.test.valgrind.err:==20522== 32 bytes in 1 blocks are definitely lost in loss record 1,482 of 4,109
tst2501.test.valgrind.err:==20522== 32 bytes in 1 blocks are definitely lost in loss record 1,483 of 4,109
tst2501.test.valgrind.err:==20522== 48 bytes in 1 blocks are definitely lost in loss record 2,232 of 4,109
tst2501.test.valgrind.err:==20522== 48 bytes in 1 blocks are definitely lost in loss record 2,233 of 4,109
tst2502.test.valgrind.err:==20529== 32 bytes in 1 blocks are definitely lost in loss record 1,480 of 4,109
tst2502.test.valgrind.err:==20529== 32 bytes in 1 blocks are definitely lost in loss record 1,481 of 4,109
tst2502.test.valgrind.err:==20529== 32 bytes in 1 blocks are definitely lost in loss record 1,482 of 4,109
tst2502.test.valgrind.err:==20529== 32 bytes in 1 blocks are definitely lost in loss record 1,483 of 4,109
tst2502.test.valgrind.err:==20529== 48 bytes in 1 blocks are definitely lost in loss record 2,232 of 4,109
tst2502.test.valgrind.err:==20529== 48 bytes in 1 blocks are definitely lost in loss record 2,233 of 4,109
tst2503.test.valgrind.err:==20538== 32 bytes in 1 blocks are definitely lost in loss record 1,480 of 4,109
tst2503.test.valgrind.err:==20538== 32 bytes in 1 blocks are definitely lost in loss record 1,481 of 4,109
tst2503.test.valgrind.err:==20538== 48 bytes in 1 blocks are definitely lost in loss record 2,230 of 4,109
tst2503.test.valgrind.err:==20538== 160 bytes in 5 blocks are definitely lost in loss record 3,239 of 4,109
tst2503.test.valgrind.err:==20538== 160 bytes in 5 blocks are definitely lost in loss record 3,240 of 4,109
tst2503.test.valgrind.err:==20538== 240 bytes in 5 blocks are definitely lost in loss record 3,344 of 4,109
tst2505.test.valgrind.err:==20551== 64 bytes in 2 blocks are definitely lost in loss record 2,584 of 4,106
tst2505.test.valgrind.err:==20551== 64 bytes in 2 blocks are definitely lost in loss record 2,585 of 4,106
tst2505.test.valgrind.err:==20551== 96 bytes in 2 blocks are definitely lost in loss record 2,923 of 4,106
tst2506.test.valgrind.err:==20557== 64 bytes in 2 blocks are definitely lost in loss record 2,584 of 4,109
tst2506.test.valgrind.err:==20557== 64 bytes in 2 blocks are definitely lost in loss record 2,585 of 4,109
tst2506.test.valgrind.err:==20557== 96 bytes in 2 blocks are definitely lost in loss record 2,923 of 4,109
tst2510.test.valgrind.err:==20570== 32 bytes in 1 blocks are definitely lost in loss record 1,480 of 4,113
tst2510.test.valgrind.err:==20570== 32 bytes in 1 blocks are definitely lost in loss record 1,481 of 4,113
tst2510.test.valgrind.err:==20570== 48 bytes in 1 blocks are definitely lost in loss record 2,231 of 4,113
tst2560.test.valgrind.err:==20614== 48 bytes in 1 blocks are definitely lost in loss record 2,241 of 4,144
tst2560.test.valgrind.err:==20614== 48 bytes in 1 blocks are definitely lost in loss record 2,242 of 4,144
tst2560.test.valgrind.err:==20614== 80 bytes in 1 blocks are definitely lost in loss record 2,750 of 4,144
tst2560.test.valgrind.err:==20614== 96 bytes in 2 blocks are definitely lost in loss record 2,935 of 4,144
tst2560.test.valgrind.err:==20614== 96 bytes in 2 blocks are definitely lost in loss record 2,936 of 4,144
tst2560.test.valgrind.err:==20614== 160 bytes in 2 blocks are definitely lost in loss record 3,256 of 4,144
tst2570.test.valgrind.err:==20627== 64 bytes in 2 blocks are definitely lost in loss record 2,582 of 4,112
tst2570.test.valgrind.err:==20627== 64 bytes in 2 blocks are definitely lost in loss record 2,583 of 4,112
tst2570.test.valgrind.err:==20627== 64 bytes in 2 blocks are definitely lost in loss record 2,584 of 4,112
tst2570.test.valgrind.err:==20627== 64 bytes in 2 blocks are definitely lost in loss record 2,585 of 4,112
tst2570.test.valgrind.err:==20627== 96 bytes in 2 blocks are definitely lost in loss record 2,917 of 4,112
tst2570.test.valgrind.err:==20627== 96 bytes in 2 blocks are definitely lost in loss record 2,918 of 4,112
tst285.test.valgrind.err:==20704== 128 bytes in 1 blocks are definitely lost in loss record 3,038 of 4,096
tst300.test.valgrind.err:==20727== 56 bytes in 1 blocks are definitely lost in loss record 2,382 of 4,108
tst303.test.valgrind.err:==20759== 56 bytes in 1 blocks are definitely lost in loss record 2,376 of 4,088
tst304.test.valgrind.err:==20765== 32 bytes in 1 blocks are definitely lost in loss record 1,479 of 4,106
tst304.test.valgrind.err:==20765== 80 bytes in 2 blocks are definitely lost in loss record 2,735 of 4,106
tst305.test.valgrind.err:==20779== 32 bytes in 1 blocks are definitely lost in loss record 1,481 of 4,106
tst305.test.valgrind.err:==20779== 80 bytes in 2 blocks are definitely lost in loss record 2,735 of 4,106
tst3060.test.valgrind.err:==20786== 24 bytes in 1 blocks are definitely lost in loss record 742 of 4,114
tst606.test.valgrind.err:==20976== 1,496 (56 direct, 1,440 indirect) bytes in 1 blocks are definitely lost in loss record 3,865 of 4,126
tst620.test.valgrind.err:==21022== 24 bytes in 1 blocks are definitely lost in loss record 733 of 4,110
tst620.test.valgrind.err:==21022== 24 bytes in 1 blocks are definitely lost in loss record 734 of 4,110
tst654.test.valgrind.err:==21035== 24 bytes in 1 blocks are definitely lost in loss record 730 of 4,085
tst654.test.valgrind.err:==21035== 24 bytes in 1 blocks are definitely lost in loss record 731 of 4,085
tst654.test.valgrind.err:==21035== 24 bytes in 1 blocks are definitely lost in loss record 732 of 4,085
tst654.test.valgrind.err:==21035== 48 bytes in 2 blocks are definitely lost in loss record 2,215 of 4,085
tst654.test.valgrind.err:==21035== 48 bytes in 2 blocks are definitely lost in loss record 2,216 of 4,085
tst654.test.valgrind.err:==21035== 168 bytes in 7 blocks are definitely lost in loss record 3,255 of 4,085
tst655.test.valgrind.err:==21042== 48 bytes in 2 blocks are definitely lost in loss record 2,216 of 4,087
tst655.test.valgrind.err:==21042== 48 bytes in 2 blocks are definitely lost in loss record 2,217 of 4,087
tst912.test.valgrind.err:==21433== 192 bytes in 4 blocks are definitely lost in loss record 3,320 of 4,181
tst912.test.valgrind.err:==21433== 192 bytes in 4 blocks are definitely lost in loss record 3,321 of 4,181
tst912.test.valgrind.err:==21433== 320 bytes in 4 blocks are definitely lost in loss record 3,484 of 4,181
tst912.test.valgrind.err:==21433== 520,752 bytes in 10,849 blocks are definitely lost in loss record 4,175 of 4,181
tst912.test.valgrind.err:==21433== 520,848 bytes in 10,851 blocks are definitely lost in loss record 4,176 of 4,181
tst912.test.valgrind.err:==21433== 856,160 bytes in 10,702 blocks are definitely lost in loss record 4,179 of 4,181
## Comment 16117
Date: 2011-08-21 11:23:22 +0200
From: @mlkersten
Most fixed by patching mal_interpreter.mx and mal_factories.
## Comment 16118
Date: 2011-08-21 11:34:40 +0200
From: @mlkersten
The leakage report for M5 is back to 'normal'
The leaks below have been known for a long time, but not considered urgent.
Some may even disappear soon, when the functionality attached is dropped
(e.g. tablet formatting at server side)
tst016.test.valgrind.err:==11401== 48 bytes in 1 blocks are definitely lost in loss record 130 of 362
tst041.test.valgrind.err:==11524== 24 bytes in 1 blocks are definitely lost in loss record 74 of 364
tst041.test.valgrind.err:==11524== 32 bytes in 1 blocks are definitely lost in loss record 113 of 364
tst041.test.valgrind.err:==11524== 48 bytes in 2 blocks are definitely lost in loss record 132 of 364
tst061.test.valgrind.err:==11613== 24 bytes in 1 blocks are definitely lost in loss record 74 of 362
tst285.test.valgrind.err:==12169== 128 bytes in 1 blocks are definitely lost in loss record 191 of 383
tst300.test.valgrind.err:==12183== 56 bytes in 1 blocks are definitely lost in loss record 149 of 382
tst303.test.valgrind.err:==12209== 56 bytes in 1 blocks are definitely lost in loss record 143 of 362
tst304.test.valgrind.err:==12213== 32 bytes in 1 blocks are definitely lost in loss record 114 of 380
tst304.test.valgrind.err:==12213== 80 bytes in 2 blocks are definitely lost in loss record 160 of 380
tst305.test.valgrind.err:==12222== 32 bytes in 1 blocks are definitely lost in loss record 116 of 380
tst305.test.valgrind.err:==12222== 80 bytes in 2 blocks are definitely lost in loss record 160 of 380
tst3060.test.valgrind.err:==12229== 24 bytes in 1 blocks are definitely lost in loss record 78 of 388
tst606.test.valgrind.err:==12370== 1,496 (56 direct, 1,440 indirect) bytes in 1 blocks are definitely lost in loss record 277 of 400
tst620.test.valgrind.err:==12397== 24 bytes in 1 blocks are definitely lost in loss record 69 of 386
tst620.test.valgrind.err:==12397== 24 bytes in 1 blocks are definitely lost in loss record 70 of 386
tst654.test.valgrind.err:==12406== 24 bytes in 1 blocks are definitely lost in loss record 66 of 368
tst654.test.valgrind.err:==12406== 24 bytes in 1 blocks are definitely lost in loss record 67 of 368
tst654.test.valgrind.err:==12406== 24 bytes in 1 blocks are definitely lost in loss record 68 of 368
tst654.test.valgrind.err:==12406== 48 bytes in 2 blocks are definitely lost in loss record 126 of 368
tst654.test.valgrind.err:==12406== 48 bytes in 2 blocks are definitely lost in loss record 127 of 368
tst654.test.valgrind.err:==12406== 168 bytes in 7 blocks are definitely lost in loss record 176 of 368
tst655.test.valgrind.err:==12410== 48 bytes in 2 blocks are definitely lost in loss record 127 of 370
tst655.test.valgrind.err:==12410== 48 bytes in 2 blocks are definitely lost in loss record 128 of 370
## Comment 16458
Date: 2011-10-20 18:52:58 +0200
From: @mlkersten
The Dec2011 report on memory leaks
tst016.test.valgrind.err:==22997== 56 bytes in 1 blocks are definitely lost in loss record 129 of 390
tst041.test.valgrind.err:==23172== 32 bytes in 1 blocks are definitely lost in loss record 79 of 392
tst041.test.valgrind.err:==23172== 40 bytes in 1 blocks are definitely lost in loss record 122 of 392
tst041.test.valgrind.err:==23172== 64 bytes in 2 blocks are definitely lost in loss record 148 of 392
tst061.test.valgrind.err:==23290== 32 bytes in 1 blocks are definitely lost in loss record 79 of 390
tst300.test.valgrind.err:==24215== 64 bytes in 1 blocks are definitely lost in loss record 152 of 410
tst303.test.valgrind.err:==24242== 64 bytes in 1 blocks are definitely lost in loss record 146 of 390
tst304.test.valgrind.err:==24246== 40 bytes in 1 blocks are definitely lost in loss record 123 of 408
tst304.test.valgrind.err:==24246== 96 bytes in 2 blocks are definitely lost in loss record 191 of 408
tst305.test.valgrind.err:==24255== 40 bytes in 1 blocks are definitely lost in loss record 125 of 408
tst305.test.valgrind.err:==24255== 96 bytes in 2 blocks are definitely lost in loss record 191 of 408
tst3060.test.valgrind.err:==24259== 32 bytes in 1 blocks are definitely lost in loss record 83 of 416
tst606.test.valgrind.err:==24391== 1,608 (64 direct, 1,544 indirect) bytes in 1 blocks are definitely lost in loss record 295 of 428
tst654.test.valgrind.err:==24430== 32 bytes in 1 blocks are definitely lost in loss record 71 of 396
tst654.test.valgrind.err:==24430== 32 bytes in 1 blocks are definitely lost in loss record 72 of 396
tst654.test.valgrind.err:==24430== 32 bytes in 1 blocks are definitely lost in loss record 73 of 396
tst654.test.valgrind.err:==24430== 64 bytes in 2 blocks are definitely lost in loss record 142 of 396
tst654.test.valgrind.err:==24430== 64 bytes in 2 blocks are definitely lost in loss record 143 of 396
tst654.test.valgrind.err:==24430== 224 bytes in 7 blocks are definitely lost in loss record 201 of 396
tst655.test.valgrind.err:==24436== 64 bytes in 2 blocks are definitely lost in loss record 144 of 398
tst655.test.valgrind.err:==24436== 64 bytes in 2 blocks are definitely lost in loss record 145 of 398
## Comment 17489
Date: 2012-07-17 14:43:26 +0200
From: @grobian
Martin reports: "back to normal"
We need to watch this more closely, though.
## Comment 18097
Date: 2012-11-27 14:50:34 +0100
From: @yzchang
Not possible to add a test for this bug
| Memory leakage report | https://api.github.com/repos/MonetDB/MonetDB/issues/2863/comments | 0 | 2020-11-30T11:44:57Z | 2024-06-28T13:19:59Z | https://github.com/MonetDB/MonetDB/issues/2863 | 753,407,846 | 2,863 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-17 14:26:12 +0200
From: @grobian
To: SQL devs <<bugs-sql>>
Version: 11.3.7 (Apr2011-SP2) [obsolete]
CC: @njnes, @skinkie
Last updated: 2012-02-29 10:34:23 +0100
## Comment 16109
Date: 2011-08-17 14:26:12 +0200
From: @grobian
% cat xsight-dump-device-table.sql
START TRANSACTION;
CREATE TABLE "device" (
"deviceid" int,
"parentdeviceid" int,
CONSTRAINT "device_pk" PRIMARY KEY ("deviceid")
);
COPY 2 RECORDS INTO "device" FROM stdin USING DELIMITERS '\t','\n','"';
2 NULL
23 2
ALTER TABLE "device" ADD CONSTRAINT "device_device_fk" FOREIGN KEY ("parentdeviceid") REFERENCES "device" ("deviceid");
--COMMIT;
% mclient xsight xsight-dump-device-table.sql
auto commit mode: off
operation successful
2 affected rows
SQLException:assert:UPDATE: FOREIGN KEY constraint 'device.device_device_fk' violated
This used to work, and it works fine if the constraint is there from the start and inserts are being used.
A dump/restore of such table hence fails.
## Comment 16110
Date: 2011-08-18 12:46:31 +0200
From: @grobian
copy-n-npasta
START TRANSACTION;
CREATE TABLE "device" (
"deviceid" int,
"parentdeviceid" int,
CONSTRAINT "device_pk" PRIMARY KEY ("deviceid")
);
COPY 2 RECORDS INTO "device" FROM stdin USING DELIMITERS ',','\n','"';
2,NULL
23,2
ALTER TABLE "device" ADD CONSTRAINT "device_device_fk" FOREIGN KEY ("parentdeviceid") REFERENCES "device" ("deviceid");
--COMMIT;
## Comment 16124
Date: 2011-08-22 00:01:52 +0200
From: @njnes
Changeset [98fdeb1daa49](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=98fdeb1daa49) 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=98fdeb1daa49](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=98fdeb1daa49)
Changeset description:
fixed bug #2862
was a name resolution problem. Now we use unique 'table' name for
the refered table.
## Comment 16125
Date: 2011-08-22 00:05:07 +0200
From: @njnes
fixed. The join between non-null values and full referenced columns was done
incorrect. This is solve by using unique names for this join.
## Comment 16129
Date: 2011-08-22 08:17:22 +0200
From: @drstmane
We should consider adding a test (also) for this one.
## Comment 16136
Date: 2011-08-22 16:41:13 +0200
From: @drstmane
Changeset [fa813932a753](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=fa813932a753) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fa813932a753](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fa813932a753)
Changeset description:
added tests for bug #2852 & bug #2862
## Comment 16242
Date: 2011-09-16 15:04:35 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 16841
Date: 2012-01-29 00:46:56 +0100
From: @skinkie
It seems to be back in HEAD.
| foreign key self references cause violation upon alter table add constraint... | https://api.github.com/repos/MonetDB/MonetDB/issues/2862/comments | 0 | 2020-11-30T11:44:54Z | 2024-06-27T11:52:47Z | https://github.com/MonetDB/MonetDB/issues/2862 | 753,407,821 | 2,862 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-16 13:31:13 +0200
From: @grobian
To: SQL devs <<bugs-sql>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @njnes, @drstmane
Last updated: 2020-11-12 15:03:54 +0100
## Comment 16108
Date: 2011-08-16 13:31:13 +0200
From: @grobian
1. take an empty database
2. as monetdb monetdb create in the system schema a table foo
3. use \d, and don't see foo
mclient executes for \d the simple and trivial query:
SELECT "name", CAST("type" AS VARCHAR(30)) AS "type", "system", "sname", "ntype" FROM (SELECT "o"."name", (CASE "o"."system" WHEN true THEN 'SYSTEM ' ELSE '' END || CASE "o"."type" WHEN 0 THEN 'TABLE' WHEN 1 THEN 'VIEW' ELSE '' END) AS "type", "o"."system", "s"."name" AS "sname", CASE "o"."type" WHEN 0 THEN 1 WHEN 1 THEN 2 ELSE 0 END AS "ntype" FROM "sys"."_tables" "o", "sys"."schemas" "s" WHERE "o"."schema_id" = "s"."id" AND "s"."name" = "current_schema" AND "o"."name" LIKE '%' AND "o"."type" IN (0, 1) UNION SELECT "o"."name", 'SEQUENCE' AS "type", false AS "system", "s"."name" AS "sname", 4 AS "ntype" FROM "sys"."sequences" "o", "sys"."schemas" "s" WHERE "o"."schema_id" = "s"."id" AND "s"."name" = "current_schema" AND "o"."name" LIKE '%' UNION SELECT "o"."name", (CASE WHEN "sf"."function_id" IS NOT NULL THEN 'SYSTEM ' ELSE '' END || 'FUNCTION') AS "type", CASE WHEN "sf"."function_id" IS NULL THEN false ELSE true END AS "system", "s"."name" AS "sname", 8 AS "ntype" FROM "sys"."functions" "o" LEFT JOIN "sys"."systemfunctions" "sf" ON "o"."id" = "sf"."function_id", "sys"."schemas" "s" WHERE "o"."schema_id" = "s"."id" AND "s"."name" = "current_schema" AND "o"."name" LIKE '%' UNION SELECT NULL AS "name", (CASE WHEN "o"."name" LIKE 'sys' THEN 'SYSTEM ' ELSE '' END || 'SCHEMA') AS "type", CASE WHEN "o"."name" LIKE 'sys' THEN true ELSE false END AS "system", "o"."name" AS "sname", 16 AS "ntype" FROM "sys"."schemas" "o" WHERE "o"."name" LIKE '%' ) AS "all" WHERE "ntype" & 3 > 0 AND "system" = false ORDER BY "system", "name";
This query returns nothing, while it should. When modifying the query's last part (the WHERE-clause) to remove either one of the two AND-ed conditions, the query does return tuples, including those tuples which do not match the filter condition of the removed condition.
This is a regression over Apr2011 that must be fixed prior Aug2011 release.
## Comment 16111
Date: 2011-08-19 16:20:25 +0200
From: @njnes
Changeset [33dc8ccd7e65](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=33dc8ccd7e65) 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=33dc8ccd7e65](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=33dc8ccd7e65)
Changeset description:
fixed bug #2861 (accum operations should reset the sort flag)
## Comment 16112
Date: 2011-08-19 16:21:38 +0200
From: @njnes
fixed bug in accum operators (reset sorting flag)
## Comment 16127
Date: 2011-08-22 08:16:49 +0200
From: @drstmane
We should consider adding a test (also) for this one.
## Comment 16131
Date: 2011-08-22 10:09:27 +0200
From: @grobian
Changeset [cb638fc742d8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=cb638fc742d8) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=cb638fc742d8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=cb638fc742d8)
Changeset description:
tests: add script for bug #2861
## Comment 16132
Date: 2011-08-22 10:10:04 +0200
From: @grobian
test added
closing as fixed since this bug never appeared in a released version
## Comment 28260
Date: 2020-11-12 15:03:54 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [1e0da235507d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1e0da235507d) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=1e0da235507d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=1e0da235507d)
Changeset description:
Converted mclient-lsql-d.Bug-2861 test
| mclient's \d no longer returns non-system tables due to SQL AND clause | https://api.github.com/repos/MonetDB/MonetDB/issues/2861/comments | 0 | 2020-11-30T11:44:51Z | 2024-06-27T11:52:46Z | https://github.com/MonetDB/MonetDB/issues/2861 | 753,407,793 | 2,861 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-14 11:28:57 +0200
From: Rémy Chibois <<rchibois>>
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.3.7 (Apr2011-SP2) [obsolete]
CC: @yzchang
Last updated: 2012-11-27 14:58:04 +0100
## Comment 16104
Date: 2011-08-14 11:28:57 +0200
From: Rémy Chibois <<rchibois>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7) AppleWebKit/534.48.3 (KHTML, like Gecko) Version/5.1 Safari/534.48.3
Build Identifier:
/etc/init.d/monetdb5-sql declares "PIDFILE=/var/run/monetdb/$NAME.pid" with "NAME" being "monetdb"
When monetdb daemon starts, it creates a pid file "/var/run/monetdb/merovingian.pid", hence when the script tests daemon's correct startup or status, it fails.
Changing the declaration to "PIDFILE=/var/run/monetdb/merovingian.pid" seems to solve this.
Reproducible: Always
### Steps to Reproduce:
1. Install MonetDB:
sudo apt-get install monetdb5-sql monetdb-client
2. Modify /etc/default/monetdb5-sql:
STARTUP="yes"
3. Start MonetDB
/etc/init.d/monetdb5-sql start
### Actual Results:
Starting MonetDB SQL server: ERROR, monetdbd didn't start
### Expected Results:
Starting MonetDB SQL server: monetdbd.
==== mserver5 --version
MonetDB 5 server v11.3.7 "Apr2011-SP2" (64-bit, 64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2011 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 3.9GiB available memory, 4 available cpu cores
Libraries:
libpcre: 8.12 2011-01-15 (compiled with 8.12)
openssl: OpenSSL 0.9.8o 01 Jun 2010 (compiled with OpenSSL 0.9.8o 01 Jun 2010)
libxml2: 2.7.8 (compiled with 2.7.8)
Compiled by: root@ottar.ins.cwi.nl (x86_64-pc-linux-gnu)
Compilation: gcc -O2 -O6 -fomit-frame-pointer -finline-functions -falign-loops=4 -falign-jumps=4 -falign-functions=4 -fexpensive-optimizations -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -ftree-vectorize
Linking : /usr/bin/ld -m elf_x86_64 -Wl,-Bsymbolic-functions
==== snippet from merovingian.log
2011-08-14 11:21:00 MSG merovingian[25261]: Merovingian 1.4 (Apr2011-SP2) starting
2011-08-14 11:21:00 MSG merovingian[25261]: monitoring dbfarm /var/monetdb5/dbfarm
2011-08-14 11:21:05 MSG merovingian[25261]: accepting connections on TCP socket 0.0.0.0:50000
2011-08-14 11:21:05 MSG merovingian[25261]: accepting connections on UNIX domain socket /tmp/.s.monetdb.50000
2011-08-14 11:21:10 MSG discovery[25261]: listening for UDP messages on 0.0.0.0:50000
2011-08-14 11:21:10 MSG control[25261]: accepting connections on UNIX domain socket /tmp/.s.merovingian.50001
2011-08-14 11:21:15 MSG control[25261]: accepting connections on TCP socket 0.0.0.0:50001
2011-08-14 11:21:15 MSG discovery[25261]: new neighbour phoenix (phoenix.expandium.com)
2011-08-14 11:21:15 MSG discovery[25261]: new database mapi:monetdb://phoenix:50000/expand (ttl=660s)
2011-08-14 11:21:15 MSG discovery[25261]: registered neighbour phoenix:50001
## Comment 16105
Date: 2011-08-14 11:40:48 +0200
From: @sjoerdmullender
Changeset [a4fe06e6ebfe](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a4fe06e6ebfe) 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=a4fe06e6ebfe](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a4fe06e6ebfe)
Changeset description:
Fix name of PID file for monetdbd.
This fixes bug #2860.
## Comment 16107
Date: 2011-08-15 11:11:24 +0200
From: @sjoerdmullender
This is fixed in the Aug2011 branch.
## Comment 16248
Date: 2011-09-16 15:04:37 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 18102
Date: 2012-11-27 14:58:04 +0100
From: @yzchang
Not possible to add test to this bug
| /etc/init.d/monetdb5-sql uses incorrect PIDFILE to test if monetdb is running | https://api.github.com/repos/MonetDB/MonetDB/issues/2860/comments | 0 | 2020-11-30T11:44:49Z | 2024-06-27T11:52:45Z | https://github.com/MonetDB/MonetDB/issues/2860 | 753,407,758 | 2,860 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-13 12:56:02 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @njnes
Last updated: 2011-09-16 15:04:37 +0200
## Comment 16100
Date: 2011-08-13 12:56:02 +0200
From: @drstmane
ERROR = !SQLException:sql.prepare:wrong number of arguments for prepared statement: 35, expected 0
http://monetdb.cwi.nl/testweb/tests/41338:3fefa57b67c0/GNU-Fedora-x86_64-propcheck-assert/sql/mTests/test/BugTracker/large_prepare.SF-1363729.err.diff.html
ERROR = !SQLException:sql.prepare:wrong number of arguments for prepared statement: 38, expected 0
http://monetdb.cwi.nl/testweb/tests/41338:3fefa57b67c0/GNU-Fedora-x86_64-propcheck-assert/sql/mTests/test/BugTracker/large_prepare_2.SF-1363729.err.diff.html
ERROR = !SQLException:sql.prepare:wrong number of arguments for prepared statement: 3, expected 0
http://monetdb.cwi.nl/testweb/tests/41338:3fefa57b67c0/GNU-Fedora-x86_64-propcheck-assert/sql/mTests/test/BugTracker/decimal_prepare.SF-1655818.err.diff.html
ERROR = !SQLException:sql.prepare:wrong number of arguments for prepared statement: 1, expected 0
http://monetdb.cwi.nl/testweb/tests/41338:3fefa57b67c0/GNU-Fedora-x86_64-propcheck-assert/sql/mTests/test/BugTracker-2010/prepare_stmt.Bug-2533.Bug-2534.err.diff.html
## Comment 16103
Date: 2011-08-13 20:21:36 +0200
From: @njnes
the is caused by the extra initialization code of 'mclient'. It now sets the time zone. This shifts the used statiement ids.
## Comment 16106
Date: 2011-08-14 17:35:55 +0200
From: @drstmane
Transplanted changesets [04fcde4fc3b0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=04fcde4fc3b0) & [d6e32a17f424](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=d6e32a17f424) from default branch to Aug2011 branch.
## Comment 16246
Date: 2011-09-16 15:04:37 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| prepare statement tests fail with number of arguments mismatch | https://api.github.com/repos/MonetDB/MonetDB/issues/2859/comments | 0 | 2020-11-30T11:44:45Z | 2024-06-27T11:52:44Z | https://github.com/MonetDB/MonetDB/issues/2859 | 753,407,729 | 2,859 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-13 12:25:35 +0200
From: @drstmane
To: buildtools devs <<bugs-buildtools>>
Version: 11.21.19 (Jul2015-SP4)
CC: hoffman9417calvin, @yzchang
Last updated: 2019-12-18 03:33:48 +0100
## Comment 16099
Date: 2011-08-13 12:25:35 +0200
From: @drstmane
The use of configure conditionals on Windows does not seem to be complete and consistent:
Some conditionals appear not to be used at all on Windows:
$ for i in `grep COND MonetDB/configure.ag | sed 's|^AM_CONDITIONAL(\([^,]*\),.*$|\1|' | sort -u` ; do grep $i TestTools/* MonetDB/NT/* MonetDB/buildtools/doc/* >/dev/null || echo $i ; done
ENABLE_CRACKERS
ENABLE_DATACELL
HAVE_ANT
HAVE_DEVELOPER
HAVE_JAVAMEROCONTROL
Some conditionals appear not to be used in all Windows-related places:
Not in MonetDB/NT/:
$ for i in `grep COND MonetDB/configure.ag | sed 's|^AM_CONDITIONAL(\([^,]*\),.*$|\1|' | sort -u` ; do grep $i MonetDB/NT/* >/dev/null || echo $i ; done
ENABLE_CRACKERS
ENABLE_DATACELL
HAVE_ANT
HAVE_DEVELOPER
HAVE_GDK
HAVE_GEOM
HAVE_JAVAMEROCONTROL
HAVE_TESTING
Not in MonetDB/buildtools/doc/:
$ for i in `grep COND MonetDB/configure.ag | sed 's|^AM_CONDITIONAL(\([^,]*\),.*$|\1|' | sort -u` ; do grep $i MonetDB/buildtools/doc/* >/dev/null || echo $i ; done
BITS32
BITS64
CROSS_COMPILING
DOCTOOLS
ENABLE_CRACKERS
ENABLE_DATACELL
HAVE_ANT
HAVE_DEVELOPER
HAVE_GDK
HAVE_JAVAMEROCONTROL
HAVE_ODBC
HAVE_RUBYGEM
HAVE_SPHINXCLIENT
NATIVE_WIN32
NOT_WIN32
PROFILING
Not in TestTools/:
$ for i in `grep COND MonetDB/configure.ag | sed 's|^AM_CONDITIONAL(\([^,]*\),.*$|\1|' | sort -u` ; do grep $i TestTools/* >/dev/null || echo $i ; done BITS32
BITS64
CROSS_COMPILING
DOCTOOLS
ENABLE_CRACKERS
ENABLE_DATACELL
HAVE_ANT
HAVE_DEVELOPER
HAVE_JAVAMEROCONTROL
HAVE_RAPTOR
HAVE_SPHINXCLIENT
PROFILING
## Comment 16126
Date: 2011-08-22 07:50:56 +0200
From: @drstmane
Code has been fixed by changsets [747b6deb5a02](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=747b6deb5a02) [441064113a4e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=441064113a4e) [9aeccfbabe43](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=9aeccfbabe43) [26b944c161e1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=26b944c161e1) [d915ee788ef5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=d915ee788ef5) [358ae2dd1d97](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=358ae2dd1d97) [e133f277958d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e133f277958d) [406f48810840](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=406f48810840) [e7e56558851f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e7e56558851f) [6afb0a0a5176](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=6afb0a0a5176) [17ebb52e97e3](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=17ebb52e97e3) [e909fc7edac1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e909fc7edac1)
Documentation in buildtools/doc/*.rst still needs to be checked and updated:
$ for i in `grep AM_CONDITIONAL configure.ag | sed 's|^AM_CONDITIONAL(\([^,]*\),.*$|\1|' | sort -u` ; do grep --color -w $i buildtools/doc/*rst || echo "-> $i <-" ; done
-> BITS32 <-
-> BITS64 <-
-> CROSS_COMPILING <-
-> DOCTOOLS <-
-> ENABLE_CRACKERS <-
-> ENABLE_DATACELL <-
-> HAVE_ANT <-
-> HAVE_DEVELOPER <-
-> HAVE_GDK <-
buildtools/doc/windowsbuild.rst:- ``HAVE_GEOM=1`` - include the geom component;
buildtools/doc/HowToRelease.rst: HAVE_JAVA=1 HAVE_JAVAJDBC=1 HAVE_PYTHON=1 HAVE_PCRE=1
buildtools/doc/HowToRelease.rst: HAVE_MONETDB5=1 HAVE_JAVA=1 HAVE_JAVAJDBC=1 HAVE_PYTHON=1 HAVE_PCRE=1
buildtools/doc/windowsbuild.rst:- ``HAVE_JAVA=1`` - include the java component (only use if Java and
buildtools/doc/HowToRelease.rst: HAVE_JAVA=1 HAVE_JAVAJDBC=1 HAVE_PYTHON=1 HAVE_PCRE=1
buildtools/doc/HowToRelease.rst: HAVE_MONETDB5=1 HAVE_JAVA=1 HAVE_JAVAJDBC=1 HAVE_PYTHON=1 HAVE_PCRE=1
-> HAVE_JAVAMEROCONTROL <-
buildtools/doc/windowsbuild.rst:call ``nmake`` with the extra parameter ``HAVE_LIBBZ2=1``.
buildtools/doc/windowsbuild.rst:call ``nmake`` with the extra parameter ``HAVE_LIBZ=1``.
buildtools/doc/HowToRelease.rst: HAVE_MONETDB5=1 HAVE_PERL=1``
buildtools/doc/HowToRelease.rst: HAVE_MONETDB5=1 HAVE_JAVA=1 HAVE_JAVAJDBC=1 HAVE_PYTHON=1 HAVE_PCRE=1
buildtools/doc/windowsbuild.rst:- ``HAVE_MONETDB5=1`` - include the MonetDB5 component;
-> HAVE_ODBC <-
buildtools/doc/HowToRelease.rst: HAVE_JAVA=1 HAVE_JAVAJDBC=1 HAVE_PYTHON=1 HAVE_PCRE=1
buildtools/doc/HowToRelease.rst: HAVE_MONETDB5=1 HAVE_JAVA=1 HAVE_JAVAJDBC=1 HAVE_PYTHON=1 HAVE_PCRE=1
buildtools/doc/HowToRelease.rst: HAVE_MONETDB5=1 HAVE_PERL=1``
buildtools/doc/HowToRelease.rst: HAVE_PERL=1``
buildtools/doc/windowsbuild.rst:clients component with the additional ``nmake`` flags ``HAVE_PERL=1``.
buildtools/doc/windowsbuild.rst:- ``HAVE_PERL=1`` - Perl is available.
buildtools/doc/HowToRelease.rst: HAVE_JAVA=1 HAVE_JAVAJDBC=1 HAVE_PYTHON=1 HAVE_PCRE=1
buildtools/doc/HowToRelease.rst: HAVE_MONETDB5=1 HAVE_JAVA=1 HAVE_JAVAJDBC=1 HAVE_PYTHON=1 HAVE_PCRE=1
buildtools/doc/windowsbuild.rst:- ``HAVE_PYTHON=1`` - include the python component;
buildtools/doc/windowsbuild.rst:- ``HAVE_RAPTOR=1`` - the raptor library is available;
-> HAVE_RUBYGEM <-
-> HAVE_SPHINXCLIENT <-
buildtools/doc/windowsbuild.rst:- ``HAVE_SQL=1`` - include the sql component;
buildtools/doc/windowsbuild.rst:- ``HAVE_TESTING=1`` - include the testing component;
-> NATIVE_WIN32 <-
-> NOT_WIN32 <-
-> PROFILING <-
(
TestTools set these when calling nmake:
HAVE_ANT HAVE_GDK HAVE_GEOM HAVE_ICONV HAVE_JAVA HAVE_JAVAJDBC HAVE_JAVAMEROCONTROL HAVE_LIBBZ2 HAVE_LIBZ HAVE_MONETDB5 HAVE_ODBC HAVE_OPENSSL HAVE_PCRE HAVE_PERL HAVE_PYTHON HAVE_RUBYGEM HAVE_SQL HAVE_TESTING NDEBUG DEBUG MONET_OID32
)
## Comment 17660
Date: 2012-08-24 14:53:33 +0200
From: @sjoerdmullender
Jul2012-SP1 has been released.
## Comment 17910
Date: 2012-11-07 19:45:23 +0100
From: @grobian
didn't we clean up the howtobuild thing recently?
## Comment 18108
Date: 2012-11-27 15:15:25 +0100
From: @yzchang
Not possible to add a test for this bug. Maybe also not necessary, since it's a compilation issue.
## Comment 27488
Date: 2019-12-18 03:33:48 +0100
From: hoffman9417calvin
Shouldn't this be marked as fixed already? https://www.maxvisits.com/
| use of configure conditionals on Windows not complete and consistent | https://api.github.com/repos/MonetDB/MonetDB/issues/2858/comments | 0 | 2020-11-30T11:44:43Z | 2024-06-28T07:19:40Z | https://github.com/MonetDB/MonetDB/issues/2858 | 753,407,702 | 2,858 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-13 12:04:51 +0200
From: @drstmane
To: buildtools devs <<bugs-buildtools>>
Version: 11.5.1 (Aug2011) [obsolete]
Last updated: 2011-09-16 15:04:33 +0200
## Comment 16098
Date: 2011-08-13 12:04:51 +0200
From: @drstmane
Conditional HAVE_LIBXML2 is no longer used by configure.ag, since we now do require libxml2 to build MonetDB.
However, on Windows the conditional is still used:
.../TestTools $ hg locate | xargs grep --color HAVE_LIBXML2
MdoWin.bat:nmake /nologo "MAKE_INCLUDEFILE=%MAKE_INCLUDEFILE%" "prefix=%WPREFIX_PATH%" bits=%bits% HAVE_GDK=1 HAVE_GEOM=1 HAVE_ICONV=1 HAVE_JAVA=1 HAVE_JAVAJDBC=1 HAVE_LIBBZ2=1 HAVE_LIBXML2=1 HAVE_LIBZ=1 HAVE_MONETDB5=1 HAVE_ODBC=1 HAVE_OPENSSL=1 HAVE_PCRE=1 HAVE_PERL=1 HAVE_PHP=1 HAVE_PYTHON=1 HAVE_RUBYGEM=1 HAVE_SQL=1 HAVE_TESTING=1 %*
.../MonetDB $ hg locate | xargs grep --color HAVE_LIBXML2
NT/monetdb_config.h.in:/* undef HAVE_LIBXML2 */
NT/monetdb_config.h.in:ifdef HAVE_LIBXML2
NT/rules.msc:!IFDEF HAVE_LIBXML2
NT/rules.msc:libxml2_CFLAGS = -DHAVE_LIBXML2 "-I$(LIBXML2)\include" $(zlib_CFLAGS) $(ICONV_CFLAGS)
NT/rules.msc:!IFDEF HAVE_LIBXML2
NT/rules.msc:HAVE_LIBXML2_FALSE=^
NT/rules.msc: "HAVE_LIBXML2_FALSE=$(HAVE_LIBXML2_FALSE)" \
buildtools/doc/HowToRelease.rst: HAVE_MONETDB5=1 HAVE_PERL=1 HAVE_LIBXML2=1 HAVE_MONETDB5_XML=1``
buildtools/doc/HowToRelease.rst: HAVE_PERL=1 HAVE_LIBXML2=1 HAVE_MONETDB5_XML=1``
buildtools/doc/windowsbuild.rst:- ``HAVE_LIBXML2=1`` - the libxml2 library is available;
## Comment 16114
Date: 2011-08-20 11:48:54 +0200
From: @drstmane
Changeset [9aeccfbabe43](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=9aeccfbabe43) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9aeccfbabe43](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9aeccfbabe43)
Changeset description:
removed obsolete HAVE_LIBXML2 also on Windows
libxml2 is mandatory for compiling MonetDB(5)
(at least) as of Apr2011;
hence, we remove the obsolete HAVE_LIBXML2
conditional and macro (also) on Windows.
This fixes bug #2857.
## Comment 16115
Date: 2011-08-20 11:52:01 +0200
From: @drstmane
Fixed in Aug2011 branch.
No test possible/required.
## Comment 16237
Date: 2011-09-16 15:04:33 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| obsolete conditional HAVE_LIBXML2 still used on Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/2857/comments | 0 | 2020-11-30T11:44:40Z | 2024-06-27T11:52:42Z | https://github.com/MonetDB/MonetDB/issues/2857 | 753,407,678 | 2,857 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-13 10:52:50 +0200
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @yzchang
Last updated: 2012-11-27 14:54:07 +0100
## Comment 16097
Date: 2011-08-13 10:52:50 +0200
From: @drstmane
Test monetdb5/optimizer/Tests/dataflow fails;
the output appears to be polluted with profiling output; cf.,
http://monetdb.cwi.nl/testweb/tests/41338:3fefa57b67c0/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/optimizer/dataflow.out.diff.html
Please check, whether the profiling output can be avoided without compromizing the tests original intention.
## Comment 16101
Date: 2011-08-13 14:08:56 +0200
From: @drstmane
Changeset [4af45f140b0f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4af45f140b0f) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4af45f140b0f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4af45f140b0f)
Changeset description:
approved stable output according to changeset [e2984d191b6a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e2984d191b6a)
this fixes bug #2856
## Comment 16251
Date: 2011-09-16 15:04:39 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 18098
Date: 2012-11-27 14:54:07 +0100
From: @yzchang
This is about existing tests.
| test monetdb5/optimizer/Tests/dataflow fails | https://api.github.com/repos/MonetDB/MonetDB/issues/2856/comments | 0 | 2020-11-30T11:44:37Z | 2024-06-27T11:52:41Z | https://github.com/MonetDB/MonetDB/issues/2856 | 753,407,644 | 2,856 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-13 10:49:16 +0200
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @mlkersten, @yzchang
Last updated: 2012-11-27 14:55:15 +0100
## Comment 16096
Date: 2011-08-13 10:49:16 +0200
From: @drstmane
Test monetdb5/modules/mal/Tests/inspect00 fails; cf. e.g.,
http://monetdb.cwi.nl/testweb/tests/41338:3fefa57b67c0/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/modules/mal/inspect00.out.diff.html
Please check, whether this is a severe failure, or whether the output changes
are correct and intended, and hence, the new output needs to be approved.
## Comment 16119
Date: 2011-08-21 18:23:41 +0200
From: @mlkersten
The stack admin was not properly propagated. Fixed.
## Comment 16250
Date: 2011-09-16 15:04:38 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 18100
Date: 2012-11-27 14:55:15 +0100
From: @yzchang
This is about an existing test
| test monetdb5/modules/mal/Tests/inspect00 fails | https://api.github.com/repos/MonetDB/MonetDB/issues/2855/comments | 0 | 2020-11-30T11:44:35Z | 2024-06-27T11:52:40Z | https://github.com/MonetDB/MonetDB/issues/2855 | 753,407,622 | 2,855 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-12 12:45:33 +0200
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: 11.7.7 (Dec2011-SP1) [obsolete]
CC: @drstmane
Duplicates: #2526
Last updated: 2012-03-15 18:17:21 +0100
## Comment 16090
Date: 2011-08-12 12:45:33 +0200
From: @mlkersten
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110621 Fedora/3.6.18-1.fc14 Firefox/3.6.18
Build Identifier:
sql> set avgtemp =
more> (select average(value)
more> from datacell.temperature , datacell.alarms
more> where datacell.temperature.tag > now() - interval '2' minute
more> and datacell.temperature.area = datacell.alarms.area );
TODO: column names of level >= 3
Reproducible: Always
## Comment 16091
Date: 2011-08-12 13:20:03 +0200
From: @drstmane
(temporary) work-around: use aliases:
set avgtemp =
(select average(value)
from datacell.temperature as dc_temp, datacell.alarms as dc_alarms
where dc_temp.tag > now() - interval '2' minute
and dc_temp.area = dc_alarms.area );
## Comment 16092
Date: 2011-08-12 13:21:30 +0200
From: @drstmane
simplified test:
sql>select count(sys.tables.name) from sys.tables;
TODO: column names of level >= 3
sql>select count(st.name) from sys.tables as st;
+------+
| L4 |
+======+
| 33 |
+------+
1 tuple (2.834ms)
## Comment 17085
Date: 2012-03-15 18:17:21 +0100
From: @sjoerdmullender
*** This bug has been marked as a duplicate of bug #2526 ***
| Complete column name denotations | https://api.github.com/repos/MonetDB/MonetDB/issues/2854/comments | 0 | 2020-11-30T11:44:32Z | 2024-06-28T07:23:13Z | https://github.com/MonetDB/MonetDB/issues/2854 | 753,407,594 | 2,854 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-09 14:27:17 +0200
From: @sjoerdmullender
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @mlkersten, @njnes, renalkoclok, @yzchang
Last updated: 2020-06-03 09:21:16 +0200
## Comment 16088
Date: 2011-08-09 14:27:17 +0200
From: @sjoerdmullender
mserver5 says:
mserver5: sql/storage/bat/bat_storage.c:815: dup_delta: Assertion `bat->ibid' failed.
Aborted
This is a blocker for a release.
## Comment 16093
Date: 2011-08-13 10:26:08 +0200
From: @mlkersten
The latest patch does not guarantee smooth transition without rebuilding Apr2011 sf100 instance.
MonetDB/GIS module loaded
MonetDB/SQL module loaded
!mvc_init: unable to create system tables
!SQLException:SQLinit:Catalogue initialization failed
!ERROR: Incompatible database version 051100, this server supports version 051101
!ERROR: Please move away /export/scratch0/mk/dbfarm/sf100/sql_logs/sql/ and its corresponding dbfarm.
MonetDB/SQL module loaded
!mvc_init: unable to create system tables
!MALException:setScenario:Scenario not initialized 'sql'
!ERROR: Incompatible database version 051100, this server supports version 051101
!ERROR: Please move away /export/scratch0/mk/dbfarm/sf100/sql_logs/sql/ and its corresponding dbfarm.
## Comment 16095
Date: 2011-08-13 10:43:21 +0200
From: @mlkersten
The last message was a result of a read-only database.
Please check for this and announce to remove --readonly it before upgrade.
Upgrade of april database worked, but toke quite some time
## Comment 16102
Date: 2011-08-13 16:41:54 +0200
From: @njnes
For readonly (and other restricted catalogs) we don't have upgrade functions. So its probably best to make the error message in gdk_logger.c include this information (ie cannot upgrade because of missing upgrade functions)
## Comment 16137
Date: 2011-08-22 19:54:32 +0200
From: @sjoerdmullender
Perhaps check_version in gdk_logger should call logger_fatal() instead of GDKerror(). Then it would exit there and then. That will stop the cascade of error messages that we get now. The only thing is, the logger doesn't (and cannot) know that the database was started with --readonly.
In any case, this is really a different bug. The bug as it was originally has been fixed.
## Comment 16428
Date: 2011-10-14 12:55:52 +0200
From: @njnes
The leftover part of this bug, is more a feature request
## Comment 17672
Date: 2012-08-24 14:55:52 +0200
From: @sjoerdmullender
Jul2012-SP1 has been released.
## Comment 18122
Date: 2012-11-27 15:33:30 +0100
From: @yzchang
Not possible to add test for this.
## Comment 27779
Date: 2020-06-03 09:21:16 +0200
From: @sjoerdmullender
The content of attachment 680 has been deleted for the following reason:
spam
| Give proper error message when starting database that needs upgrade with --readonly | https://api.github.com/repos/MonetDB/MonetDB/issues/2853/comments | 0 | 2020-11-30T11:44:29Z | 2024-06-28T13:40:46Z | https://github.com/MonetDB/MonetDB/issues/2853 | 753,407,559 | 2,853 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-07 17:06:11 +0200
From: Alfred Nordman <<alfred.nordman>>
To: SQL devs <<bugs-sql>>
Version: 11.3.7 (Apr2011-SP2) [obsolete]
CC: @njnes, @drstmane
Last updated: 2011-09-16 15:04:37 +0200
## Comment 16087
Date: 2011-08-07 17:06:11 +0200
From: Alfred Nordman <<alfred.nordman>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.107 Safari/535.1
Build Identifier:
SQL statement with case division and embedded functions compiles about 2 minutes on my computer. If I change "/" to "*" everything is executed immediately.
Reproducible: Always
### Steps to Reproduce:
1.CREATE TABLE t (c INT);
2.INSERT INTO t VALUES (0);
3.explain SELECT
COALESCE(
COALESCE("c" /
CASE
WHEN COALESCE("c" , 0) = 0
THEN
NULL
END
, 0) - COALESCE("c" /
CASE
WHEN "c" = 0
THEN
NULL
END
,0)
, 0)
FROM
t
;
### Actual Results:
Very long compilation time. It looks like generated MAL code is not correct
### Expected Results:
I guess that this script must be compiled immediately
I managed to simplify my initial script which hanged the computer to this test case. Further simplifications lead to immediate execution.
The result of this script does not have any sense it is only test sample
## Comment 16113
Date: 2011-08-19 16:29:20 +0200
From: @njnes
fixed. The long execution time was caused by recusive inplace modifing the relational tree
## Comment 16128
Date: 2011-08-22 08:17:06 +0200
From: @drstmane
We should consider adding a test (also) for this one.
## Comment 16135
Date: 2011-08-22 16:41:13 +0200
From: @drstmane
Changeset [fa813932a753](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=fa813932a753) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fa813932a753](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fa813932a753)
Changeset description:
added tests for bug #2852 & bug #2862
## Comment 16247
Date: 2011-09-16 15:04:37 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| Query with CASE and nested functions results in very long execution | https://api.github.com/repos/MonetDB/MonetDB/issues/2852/comments | 0 | 2020-11-30T11:44:27Z | 2024-06-27T11:52:37Z | https://github.com/MonetDB/MonetDB/issues/2852 | 753,407,531 | 2,852 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-05 22:04:09 +0200
From: @sjoerdmullender
To: Merovingian devs <<bugs-merovingian>>
Version: 11.3.7 (Apr2011-SP2) [obsolete]
Last updated: 2011-09-16 15:04:40 +0200
## Comment 16080
Date: 2011-08-05 22:04:09 +0200
From: @sjoerdmullender
The error message in the log file is:
2011-08-05 21:48:38 ERR merovingian[3555]: unable to open '/var/monetdb5/dbfarm//var/run/monetdb/merovingian.pid' for writing: No such file or directory
The file that it couldn't open was actually /var/run/monetdb/merovingian.pid
## Comment 16084
Date: 2011-08-06 16:31:20 +0200
From: @grobian
Changeset [c83dea3bb8e5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c83dea3bb8e5) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c83dea3bb8e5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c83dea3bb8e5)
Changeset description:
merovingian: fix inversed logic for pidfile error message
Solves bug #2851. Not fixing on Apr2011 branch, as it is a too minor
issue to warrant a SP3.
## Comment 16085
Date: 2011-08-06 16:31:55 +0200
From: @grobian
fixed for the Aug2011 release
## Comment 16252
Date: 2011-09-16 15:04:40 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| Incorrect error message when pidfile cannot be opened | https://api.github.com/repos/MonetDB/MonetDB/issues/2851/comments | 0 | 2020-11-30T11:44:24Z | 2024-06-27T11:52:36Z | https://github.com/MonetDB/MonetDB/issues/2851 | 753,407,499 | 2,851 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-05 22:02:29 +0200
From: @sjoerdmullender
To: Merovingian devs <<bugs-merovingian>>
Version: 11.3.7 (Apr2011-SP2) [obsolete]
Last updated: 2011-09-16 15:04:33 +0200
## Comment 16079
Date: 2011-08-05 22:02:29 +0200
From: @sjoerdmullender
On Fedora 15, /var/run is on a tmpfs file system. This means that the directory is completely empty when the system starts. Moreover, the directory is owned by root and has mode 755. This means that monetdbd cannot create the /var/run/monetdb5 directory (not that is tries) and cannot open the pidfile that is supposed to be located there.
On Fedora 15 and later we should not create /var/run/monetdb in the RPM. Instead we should probably use the tmpfiles.d(5) mechanism.
## Comment 16081
Date: 2011-08-05 22:10:37 +0200
From: @grobian
hmm, can't the init script assure the directory exists?
## Comment 16082
Date: 2011-08-06 11:15:38 +0200
From: @sjoerdmullender
(In reply to comment 1)
> hmm, can't the init script assure the directory exists?
Not is you don't use the script ;) .
This is needed if you want to run monetdbd as a normal user.
## Comment 16083
Date: 2011-08-06 12:02:29 +0200
From: @grobian
$ monetdbd create $HOME/my/place
$ monetdbd start $HOME/my/place
perhaps "default" should no longer work, or start issuing a warning.
## Comment 16086
Date: 2011-08-06 19:12:36 +0200
From: @sjoerdmullender
Changeset [b6d94077ee3a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b6d94077ee3a) 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=b6d94077ee3a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b6d94077ee3a)
Changeset description:
Add tmpfiles.d configuration file to create /var/run/monetdb.
This fixes bug #2850.
## Comment 16089
Date: 2011-08-09 14:30:05 +0200
From: @sjoerdmullender
It seems to work now, both after a fresh install and after a reboot.
Since this is hard to test automatically, there is no test.
## Comment 16238
Date: 2011-09-16 15:04:33 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| monetdbd cannot open pidfile on Fedora 15 | https://api.github.com/repos/MonetDB/MonetDB/issues/2850/comments | 0 | 2020-11-30T11:44:21Z | 2024-06-27T11:52:35Z | https://github.com/MonetDB/MonetDB/issues/2850 | 753,407,478 | 2,850 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-03 09:27:39 +0200
From: Tim Ruhl <<timruhl>>
To: SQL devs <<bugs-sql>>
Version: 11.3.7 (Apr2011-SP2) [obsolete]
CC: @njnes
Last updated: 2011-09-16 15:04:34 +0200
## Comment 16065
Date: 2011-08-03 09:27:39 +0200
From: Tim Ruhl <<timruhl>>
User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/534.30 (KHTML, like Gecko) Ubuntu/11.04 Chromium/12.0.742.112 Chrome/12.0.742.112 Safari/534.30
Build Identifier:
Using multi-column constraints causes the data in the table to become corrupted. Of each constraint one column is affected and always the same column. I've tried reordering the columns in the table create, changing the column order in the constraint, and changing the column that gets a duplicate value, but in all cases it always was the same column that got corrupted data.
Reproducible: Always
### Steps to Reproduce:
Run the following script
DROP TABLE "portmapping";
CREATE TABLE "portmapping" (
"id" int NOT NULL AUTO_INCREMENT,
"port" int NOT NULL,
"type" int NOT NULL,
"appname" varchar(25) NOT NULL,
"description" varchar(255) DEFAULT NULL,
CONSTRAINT "port" UNIQUE ("port","type"),
CONSTRAINT "appname" UNIQUE ("appname","type"),
PRIMARY KEY ("id")
) ;
-- duplicate port and appname
INSERT INTO "portmapping" VALUES (2,1,1,'name','test');
INSERT INTO "portmapping" VALUES (3,1,2,'name','test');
-- duplicate type
INSERT INTO "portmapping" VALUES (4,5,1,'x','test');
INSERT INTO "portmapping" VALUES (5,5,1,'y','test');
-- unique records
INSERT INTO "portmapping" VALUES (6,7,1,'z1','test');
INSERT INTO "portmapping" VALUES (7,8,2,'z2','test');
SELECT * FROM "portmapping";
### Actual Results:
+------+-------+------+---------+-------------+
| id | port | type | appname | description |
+======+=======+======+=========+=============+
| 2 | 1 | 1 | name | test |
| 3 | 2049 | 2 | 6��
| test |
| 4 | 1 | 1 | name | test |
| 5 | 2050 | 1 | 5��
| test |
| 6 | 5 | 1 | x | test |
| 7 | 10241 | 2 | �,/ | test |
+------+-------+------+---------+-------------+
6 tuples
### Expected Results:
Expected results should be as when the constraint clauses are removed from the table create statement in the script.
+------+------+------+---------+-------------+
| id | port | type | appname | description |
+======+======+======+=========+=============+
| 2 | 1 | 1 | name | test |
| 3 | 1 | 2 | name | test |
| 4 | 5 | 1 | x | test |
| 5 | 5 | 1 | y | test |
| 6 | 7 | 1 | z1 | test |
| 7 | 8 | 2 | z2 | test |
+------+------+------+---------+-------------+
6 tuples
tim@tim-E6510$ mserver5 --version
MonetDB 5 server v11.3.7 "Apr2011-SP2" (32-bit, 32-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2011 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 3.8GiB available memory, 4 available cpu cores
Libraries:
libpcre: 8.12 2011-01-15 (compiled with 8.12)
openssl: OpenSSL 0.9.8o 01 Jun 2010 (compiled with OpenSSL 0.9.8o 01 Jun 2010)
libxml2: 2.7.8 (compiled with 2.7.8)
Compiled by: root@ottar.ins.cwi.nl (i686-pc-linux-gnu)
Compilation: gcc -O2 -O6 -fomit-frame-pointer -finline-functions -falign-loops=4 -falign-jumps=4 -falign-functions=4 -fexpensive-optimizations -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -ftree-vectorize
Linking : /usr/bin/ld -Wl,-Bsymbolic-functions
## Comment 16066
Date: 2011-08-03 10:00:13 +0200
From: @sjoerdmullender
When assertions are enabled in the server, it crashes with:
mserver5: .../monetdb5/modules/atoms/str.mx:1658: strLength: Assertion `l <2147483647' failed.
Aborted
## Comment 16067
Date: 2011-08-03 10:16:14 +0200
From: @sjoerdmullender
Interesting: if you change the names of the constraints (which in your example are the same as the name of some of the columns), then the query works.
## Comment 16068
Date: 2011-08-03 18:41:01 +0200
From: @njnes
fixed by accessing idx columns using unique names (ie prefixed by '%')
## Comment 16070
Date: 2011-08-03 19:10:46 +0200
From: @njnes
Changeset [a7c28593a171](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a7c28593a171) 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=a7c28593a171](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a7c28593a171)
Changeset description:
added test for bug #2849
## Comment 16240
Date: 2011-09-16 15:04:34 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| Multi-column constraints cause data corruption | https://api.github.com/repos/MonetDB/MonetDB/issues/2849/comments | 0 | 2020-11-30T11:44:18Z | 2024-06-27T11:52:34Z | https://github.com/MonetDB/MonetDB/issues/2849 | 753,407,443 | 2,849 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-08-01 18:22:30 +0200
From: matthieu.guamis
To: SQL devs <<bugs-sql>>
Version: 11.3.7 (Apr2011-SP2) [obsolete]
CC: matthieu.guamis
Last updated: 2011-09-16 15:04:30 +0200
## Comment 16064
Date: 2011-08-01 18:22:30 +0200
From: matthieu.guamis
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; fr; rv:1.9.2.18) Gecko/20110628 Ubuntu/10.10 (maverick) Firefox/3.6.18
Build Identifier:
Main query result is "funny" when using a column name as alias of a subquery containing a CASE WHEN. Query returns content of the subquery but when alias name is set to anything else, it works as expected.
Reproducible: Always
### Steps to Reproduce:
sql>create table t (id char(1));
operation successful
sql>insert into t values ('a');
1 affected row (5.336ms)
sql>insert into t values ('b');
1 affected row (0.292ms)
sql>insert into t values ('c');
1 affected row (0.275ms)
sql>SELECT CASE WHEN id = 'a' THEN 'x' ELSE 'y' END AS id FROM t;
+-------------------------------------------------------+
| id |
+=======================================================+
| x |
| y |
| y |
+-------------------------------------------------------+
3 tuples (0.522ms)
OK!
sql>select * from ( SELECT CASE WHEN id = 'a' THEN 'x' ELSE 'y' END AS othercolnamealias FROM t) as req;
+-------------------------------------------------------+
| othercolnamealias |
+=======================================================+
| x |
| y |
| y |
+-------------------------------------------------------+
3 tuples (0.550ms)
OK!
sql>select * from ( SELECT CASE WHEN id = 'a' THEN 'x' ELSE 'y' END AS id FROM t) as req;
+------+
| id |
+======+
| a |
| b |
| c |
+------+
3 tuples (0.341ms)
OUPS!
## Comment 16071
Date: 2011-08-04 15:31:19 +0200
From: @sjoerdmullender
This seems to have been fixed in the Aug2011 branch.
## Comment 16072
Date: 2011-08-04 15:38:22 +0200
From: @sjoerdmullender
Changeset [b86cc28166e9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b86cc28166e9) 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=b86cc28166e9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b86cc28166e9)
Changeset description:
Added test for bug #2848.
## Comment 16073
Date: 2011-08-04 15:39:44 +0200
From: @sjoerdmullender
Fixed in the Aug2011 release.
## Comment 16233
Date: 2011-09-16 15:04:30 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| Problem when reusing column name as CASE... WHEN alias in subquery | https://api.github.com/repos/MonetDB/MonetDB/issues/2848/comments | 0 | 2020-11-30T11:44:16Z | 2024-06-27T11:52:33Z | https://github.com/MonetDB/MonetDB/issues/2848 | 753,407,410 | 2,848 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-29 17:17:58 +0200
From: Simon Brodt <<simon.brodt>>
To: SQL devs <<bugs-sql>>
Version: 11.3.7 (Apr2011-SP2) [obsolete]
CC: @njnes, @drstmane
Last updated: 2011-09-16 15:04:35 +0200
## Comment 16058
Date: 2011-07-29 17:17:58 +0200
From: Simon Brodt <<simon.brodt>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Build Identifier:
SELECT statement throws str_cast exception "too long for type (var)char(12)" but there are only CLOB or BIGINT attributes involved in the table definition and the query.
Reproducible: Always
### Steps to Reproduce:
sql>CREATE SCHEMA "testschema";
operation successful
sql>CREATE TABLE "testschema"."test" (
more> "type" CHARACTER LARGE OBJECT NOT NULL,
more> "output" CHARACTER LARGE OBJECT NOT NULL,
more> "output_min_time_value_1" BIGINT
more>);
operation successful
sql>INSERT INTO "testschema"."test" VALUES ('OUTPUT','greet__person','3');
1 affected row (2.633ms)
sql>SELECT "output_min_time_value_1" FROM "testschema"."test" WHERE "type" = 'OUTPUT' AND "output" = 'greet_person' ;
SQLException:str_cast:value too long for type (var)char(12)
### Actual Results:
SQLException
### Expected Results:
3
## Comment 16059
Date: 2011-07-29 17:47:54 +0200
From: @sjoerdmullender
I can reproduce this.
However, the expected result with the given query would be an empty table.
If I use the correct number of underscores (2) in the select query, I get the expected result of 3.
## Comment 16060
Date: 2011-07-29 18:10:34 +0200
From: @drstmane
Problem here is that the literal in the query (here: 'greet_person' is used as reference for the string length, and then casting the (longer) value from table ('greet__person') to that shorter length fails.
In fact, I wonder why that cast is required at all to compare two strings ...
Probably there is a good reason that I just don't see, yet; however, there should not be on overflow exception; rather when the string from the table is longer than the string literal, the equality comparison is known to yield false ...
## Comment 16061
Date: 2011-07-29 18:18:51 +0200
From: Simon Brodt <<simon.brodt>>
Try this sequence:
CREATE SCHEMA "testschema";
CREATE TABLE "testschema"."test" (
"type" CHARACTER LARGE OBJECT NOT NULL,
"output" CHARACTER LARGE OBJECT NOT NULL,
"output_min_time_value_1" BIGINT
);
INSERT INTO "testschema"."test" VALUES ('INPUT','see_person','3');
INSERT INTO "testschema"."test" VALUES ('WORKING','greet_person','3');
INSERT INTO "testschema"."test" VALUES ('OUTPUT','greet_person','3');
SELECT "output_min_time_value_1" FROM "testschema"."test" WHERE "type" = 'OUTPUT' AND "output" = 'greet_person' ;
## Comment 16062
Date: 2011-08-01 17:28:42 +0200
From: @sjoerdmullender
Changeset [0db7113f62eb](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0db7113f62eb) 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=0db7113f62eb](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0db7113f62eb)
Changeset description:
Added test for bug #2847.
## Comment 16063
Date: 2011-08-01 17:33:00 +0200
From: @sjoerdmullender
It's a SQL bug.
## Comment 16069
Date: 2011-08-03 18:42:13 +0200
From: @njnes
fixed. The supertype function now properly returns teh super type of 2
string types (where one has no length contraints)
## Comment 16243
Date: 2011-09-16 15:04:35 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| SELECT statement throws str_cast exception | https://api.github.com/repos/MonetDB/MonetDB/issues/2847/comments | 0 | 2020-11-30T11:44:13Z | 2024-06-27T11:52:32Z | https://github.com/MonetDB/MonetDB/issues/2847 | 753,407,377 | 2,847 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-29 16:49:14 +0200
From: Simon Brodt <<simon.brodt>>
To: SQL devs <<bugs-sql>>
Version: 11.5.3 (Aug2011-SP1) [obsolete]
Last updated: 2012-01-26 15:32:06 +0100
## Comment 16054
Date: 2011-07-29 16:49:14 +0200
From: Simon Brodt <<simon.brodt>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Build Identifier:
\d command fails if the schema is provided explicitly like in
\d "testschema"."test"
Reproducible: Always
### Steps to Reproduce:
sql>CREATE TABLE "test" (id INT);
operation successful
sql>\d "test"
CREATE TABLE "sys"."test" (
"id" INTEGER
);
sql>\d "sys"."test"
table sys"."test does not exist
sql>CREATE SCHEMA "testschema";
operation successful
sql>CREATE TABLE "testschema"."test" (id INT);
operation successful
sql>\d "testschema"."test"
table testschema"."test does not exist
### Actual Results:
table does not exist
### Expected Results:
description of table
## Comment 16055
Date: 2011-07-29 16:52:30 +0200
From: @grobian
this currently is expected behaviour:
\d[Stvsfn]+ object
Describe the given object in the database using SQL statements
that reconstruct the object. The same specifiers as above can
be used, following the same rules. When no specifiers are
given, vt is assumed. The object can be given with or without a
schema, separated by a dot. The object name can contain the
wildcard characters * and _ that represent zero or more, and
exactly one character respectively. An object name is converted
to lowercase, unless the object name is quoted by double quotes
("). Examples of this, are e.g. *.mytable, tabletype* or
"myschema.FOO". Note that wildcard characters do not work in
quoted objects.
## Comment 16056
Date: 2011-07-29 16:59:08 +0200
From: Simon Brodt <<simon.brodt>>
oh, sorry
## Comment 16057
Date: 2011-07-29 17:01:16 +0200
From: @grobian
It's kind of odd behaviour, so I consider it an enhancement to allow quoting of arbitrary parts of the string passed to \d
## Comment 16278
Date: 2011-09-16 15:10:40 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 16393
Date: 2011-10-11 16:05:55 +0200
From: @grobian
http://dev.monetdb.org/hg/MonetDB/rev/c31533943a6b
Implemented this feature for the next feature release.
## Comment 16831
Date: 2012-01-26 15:32:06 +0100
From: @sjoerdmullender
The Dec2011 version has been release, so declaring this bug as FIXED.
| \d command fails if the schema is provided explicitly | https://api.github.com/repos/MonetDB/MonetDB/issues/2846/comments | 0 | 2020-11-30T11:44:10Z | 2024-06-27T11:52:31Z | https://github.com/MonetDB/MonetDB/issues/2846 | 753,407,341 | 2,846 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-22 12:24:01 +0200
From: Evert Rol <<evert.astro>>
To: SQL devs <<bugs-sql>>
Version: 11.3.7 (Apr2011-SP2) [obsolete]
CC: evert.astro, @njnes
Last updated: 2011-09-16 15:04:32 +0200
## Comment 15980
Date: 2011-07-22 12:24:01 +0200
From: Evert Rol <<evert.astro>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.122 Safari/534.30
Build Identifier:
monetdb (mclient) hangs if an insert using a select statement is executed. This only happens when there is a foreign key constraint.
Use case example:
<SQL>
CREATE TABLE table1 (
tablename VARCHAR(50) NOT NULL,
PRIMARY KEY (tablename)
);
CREATE TABLE table2 (
table1_name VARCHAR(50) NOT NULL,
FOREIGN KEY (table1_name) REFERENCES table1 (tablename)
);
insert into table1 (tablename) values ('A');
insert into table2 (table1_name) values ('A');
-- Things go wrong here:
insert into table2 (table1_name) select 'A';
</SQL>
The process hangs indefinitely, and if the database is not stopped (ie, the mclient may be escaped by ctrl-C, but the server still continues to run), the process will eat up all CPU time and, in my case, overheat and shut down my macbook :-(.
There are no useful entries in the log file related to this.
On Linux (Ubuntu 11.04, 64 bit, through a VM on OS X), this bug shows up as well, but then the mclient quits with a '!Connection terminated' in the logfile. I have not checked if the background server process hangs indefinitely.
The bug does not show up in an older version (specifically, the Oct2010 release).
Reproducible: Always
### Steps to Reproduce:
1. Create a database
2. Use the client to access the database (via SQL)
3. Execute the following SQL:
CREATE TABLE table1 (
tablename VARCHAR(50) NOT NULL,
PRIMARY KEY (tablename)
);
CREATE TABLE table2 (
table1_name VARCHAR(50) NOT NULL,
FOREIGN KEY (table1_name) REFERENCES table1 (tablename)
);
insert into table1 (tablename) values ('A');
insert into table2 (table1_name) values ('A');
-- Things go wrong here:
insert into table2 (table1_name) select 'A';
### Actual Results:
On OS X: hangs indefinitely
On Linux: mclient abruptly terminates, without explanation.
### Expected Results:
Would have expected to insert a value into the table.
$> mserver5 --version
MonetDB 5 server v11.3.3 "Apr2011-SP1" (64-bit, 64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2011 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 8.0GiB available memory, 8 available cpu cores
Libraries:
libpcre: 8.12 2011-01-15 (compiled with 8.12)
openssl: OpenSSL 0.9.8l 5 Nov 2009 (compiled with OpenSSL 1.0.0d 8 Feb 2011)
libxml2: 2.7.3 (compiled with 2.7.3)
Compiled by: (x86_64-apple-darwin10.8.0)
Compilation: gcc -g -O2
Linking : /usr/libexec/gcc/i686-apple-darwin10/4.2.1/ld
## Comment 15981
Date: 2011-07-22 13:06:10 +0200
From: @sjoerdmullender
When assertions are enabled, one goes off:
sql/server/rel_exp.c:279: exp_column: Assertion `cname' failed.
## Comment 15982
Date: 2011-07-22 15:38:32 +0200
From: Evert Rol <<evert.astro>>
I mentioned Oct2010 as a working version; Mar2011 (v11.1.1) does not have the bug either, and works fine.
But Apr2011SP2 (v11.3.5) does have the bug as well.
## Comment 15984
Date: 2011-07-25 16:52:14 +0200
From: @njnes
Changeset [d06c28c1ad30](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=d06c28c1ad30) 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=d06c28c1ad30](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=d06c28c1ad30)
Changeset description:
add test for bug #2845
## Comment 15985
Date: 2011-07-25 16:53:24 +0200
From: @njnes
Changeset [343d84ba2ede](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=343d84ba2ede) 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=343d84ba2ede](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=343d84ba2ede)
Changeset description:
fixed bug #2845. Name (label) unnamed atom expression
## Comment 16047
Date: 2011-07-29 11:03:53 +0200
From: @sjoerdmullender
Apr2011-SP2 has been released.
## Comment 16236
Date: 2011-09-16 15:04:32 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| INSERT INTO fails (hangs) when values are derived from SELECT, in combination with a FOREIGN KEY constraint | https://api.github.com/repos/MonetDB/MonetDB/issues/2845/comments | 0 | 2020-11-30T11:44:07Z | 2024-06-27T11:52:30Z | https://github.com/MonetDB/MonetDB/issues/2845 | 753,407,299 | 2,845 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-19 19:15:36 +0200
From: @grobian
To: SQL devs <<bugs-sql>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
Last updated: 2011-07-29 10:52:43 +0200
## Comment 15975
Date: 2011-07-19 19:15:36 +0200
From: @grobian
sql>ALTER USER SET PASSWORD 'anders' USING OLD PASSWORD 'monetdb';
SQLException:sql.catalog:ALTER USER: no such user '�'
i.e. garbage, it should see the current user instead.
## Comment 15976
Date: 2011-07-19 19:37:39 +0200
From: @grobian
Changeset [0f9f5c7b727c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0f9f5c7b727c) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0f9f5c7b727c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0f9f5c7b727c)
Changeset description:
sql_alter_user: recognise str_nil as NULL
After ALTER USER statements have been made to go through a MAL program,
the user argument no longer would be NULL, but nil:str. As such, the
current user (== NULL) was no longer found, making it impossible to
change the password for the administrator (== monetdb) password.
Accept str_nil as alternative for NULL, fixes bug #2844.
## Comment 15977
Date: 2011-07-19 19:38:57 +0200
From: @grobian
per comment 1
## Comment 16006
Date: 2011-07-29 10:52:43 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| ALTER USER SET PASSWORD doesn't recognise username | https://api.github.com/repos/MonetDB/MonetDB/issues/2844/comments | 0 | 2020-11-30T11:44:04Z | 2024-06-27T11:52:29Z | https://github.com/MonetDB/MonetDB/issues/2844 | 753,407,278 | 2,844 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-19 09:12:52 +0200
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @yzchang
Last updated: 2012-11-27 14:55:56 +0100
## Comment 15970
Date: 2011-07-19 09:12:52 +0200
From: @drstmane
On Fedora 14 with gcc,
testing a 64-bit monetdb5 built with 32-bit OIDs crashes with
09:06:55> modules/mal/remote06.mal (<=60,60,60) ...python: /builddir/build/BUILD/Python-2.7/Objects/fileobject.c:2200: readahead_get_line_skip: Assertion `skip+len < 2147483647' failed.
Aborted
Nightly testing suggests that this (or a similar) problem occurs on Linux (with gcc, clang & icc) and on Windows (only with icc, not with MSVC):
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=40828:dd94de13cf35&targets=Cla-Fedora-x86_64-propcheck-oid32&module=monetdb5&nocondense
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=40828:dd94de13cf35&targets=GNU-Fedora-x86_64-propcheck-oid32&module=monetdb5&nocondense
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=40828:dd94de13cf35&targets=Int-Fedora-x86_64-propcheck-oid32&module=monetdb5&nocondense
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=40828:dd94de13cf35&targets=Int-Windows7-x86_64-propcheck-oid32&module=monetdb5&nocondense
However, nightly testing does not clearly indicate that the or how testing crashed:
http://monetdb.cwi.nl/testweb/web/status.php?branch=Aug2011&n=5&order=platform%2Carch%2Ccompiler&submit=refresh
## Comment 15971
Date: 2011-07-19 10:11:54 +0200
From: @grobian
Your links seem dead, so I can't check the details. Python crashes here, which is no good, but I fear the process just continues, or in some other way doesn't return with a bad exit code.
## Comment 15972
Date: 2011-07-19 11:21:10 +0200
From: @grobian
Fixed now, it appears to be a timeout, which results in the assertion on peppy.
## Comment 15973
Date: 2011-07-19 11:35:17 +0200
From: @drstmane
It also appears that at least on my Fedora 14 destop, test monetdb5/modules/mal/Tests/remote06.mal generated >= 6GB output (mostly errors / exceptions) when run with a 64-bit ABI, 32-bit OID MonetDB ...
... but maybe that should become a separate bug report ...
## Comment 15974
Date: 2011-07-19 11:37:48 +0200
From: @grobian
Yep it should. The following commit will make the Python crash go away:
http://dev.monetdb.org/hg/MonetDB/rev/25f8b4d0afce
## Comment 18101
Date: 2012-11-27 14:55:56 +0100
From: @yzchang
This is about existing tests.
| testing 64-bit with 32-bit OIDs crashes (on Linux & Windows) | https://api.github.com/repos/MonetDB/MonetDB/issues/2843/comments | 0 | 2020-11-30T11:44:02Z | 2024-06-27T11:52:28Z | https://github.com/MonetDB/MonetDB/issues/2843 | 753,407,247 | 2,843 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-18 12:37:42 +0200
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @mlkersten
Last updated: 2011-09-16 15:04:38 +0200
## Comment 15967
Date: 2011-07-18 12:37:42 +0200
From: @drstmane
Tests monetdb5/optimizer/Tests/dataflow{,3,4} lack stable output; cf., e.g.,
http://monetdb.cwi.nl/testweb/tests/40815:0d7c7c8ec081/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/optimizer/dataflow.out.diff.html
http://monetdb.cwi.nl/testweb/tests/40815:0d7c7c8ec081/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/optimizer/dataflow.err.diff.html
http://monetdb.cwi.nl/testweb/tests/40815:0d7c7c8ec081/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/optimizer/dataflow3.out.diff.html
http://monetdb.cwi.nl/testweb/tests/40815:0d7c7c8ec081/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/optimizer/dataflow3.err.diff.html
http://monetdb.cwi.nl/testweb/tests/40815:0d7c7c8ec081/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/optimizer/dataflow4.out.diff.html
http://monetdb.cwi.nl/testweb/tests/40815:0d7c7c8ec081/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/optimizer/dataflow4.err.diff.html
(I activated these tests only recently, triggered by changeset [d4efa02489c7;](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=d4efa02489c7;) cf.
http://dev.monetdb.org/hg/MonetDB/rev/d4efa02489c7 )
## Comment 16052
Date: 2011-07-29 13:21:01 +0200
From: @sjoerdmullender
There is now a stable output for dataflow3 since changeset [37eb3b538625](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=37eb3b538625)
dataflow4 was removed in changeset [a8b289f8ab93](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a8b289f8ab93)
## Comment 16249
Date: 2011-09-16 15:04:38 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| Tests monetdb5/optimizer/Tests/dataflow{,3,4} lack stable output | https://api.github.com/repos/MonetDB/MonetDB/issues/2842/comments | 0 | 2020-11-30T11:43:59Z | 2024-06-27T11:52:27Z | https://github.com/MonetDB/MonetDB/issues/2842 | 753,407,222 | 2,842 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-18 12:31:02 +0200
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @mlkersten
Last updated: 2011-09-16 15:04:40 +0200
## Comment 15966
Date: 2011-07-18 12:31:02 +0200
From: @drstmane
Tests monetdb5/optimizer/Tests/inline0{2,3,6} fail; cf. e.g.,
http://monetdb.cwi.nl/testweb/tests/40815:0d7c7c8ec081/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/optimizer/inline02.out.diff.html
http://monetdb.cwi.nl/testweb/tests/40815:0d7c7c8ec081/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/optimizer/inline03.out.diff.html
http://monetdb.cwi.nl/testweb/tests/40815:0d7c7c8ec081/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/optimizer/inline06.out.diff.html
Please check, whether this is a severe failure, or whether the output changes are correct and intended, and hence, the new output needs to be approved.
## Comment 16094
Date: 2011-08-13 10:34:31 +0200
From: @drstmane
"Interestingly", these tests appear to work fine on Windows, though; cf.,
http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=41338:3fefa57b67c0&order=platform,arch,compiler&targets=Cla-Fedora-i386-propcheck,Cla-Fedora-x86_64-propcheck-oid32,Cla-Fedora-x86_64-propcheck,GNU-Darwin-i386-propcheck,GNU-Darwin-powerpc,GNU-Darwin-x86_64-propcheck,GNU-Fedora-i386-propcheck,GNU-Fedora-x86_64-dist-rpm,GNU-Fedora-x86_64-propcheck-assert,GNU-Fedora-x86_64-propcheck-oid32,GNU-Fedora-x86_64-propcheck,GNU-Gentoo-powerpc-propcheck,GNU-Solaris-sparc,GNU-Solaris-sparcv9-oid32,GNU-Solaris-sparcv9,GNU-Ubuntu-i386-propcheck,Int-Fedora-x86_64-propcheck-oid32,Int-Fedora-x86_64-propcheck,Int-Windows2008-x86_64-propcheck,Int-Windows7-x86_64-propcheck-oid32,Int-WindowsXP-i386-propcheck,Mic-Windows2008-i386-propcheck-installer,Mic-Windows2008-x86_64-propcheck-installer,Mic-Windows7-x86_64-propcheck-oid32-installer&module=monetdb5
## Comment 16133
Date: 2011-08-22 11:05:26 +0200
From: @mlkersten
Fixed by ensuring proper type checking first.
## Comment 16254
Date: 2011-09-16 15:04:40 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| Tests monetdb5/optimizer/Tests/inline0{2,3,6} fail | https://api.github.com/repos/MonetDB/MonetDB/issues/2841/comments | 0 | 2020-11-30T11:43:56Z | 2024-06-27T11:52:26Z | https://github.com/MonetDB/MonetDB/issues/2841 | 753,407,187 | 2,841 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-18 12:29:38 +0200
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @mlkersten
Last updated: 2011-09-16 15:04:36 +0200
## Comment 15965
Date: 2011-07-18 12:29:38 +0200
From: @drstmane
Test monetdb5/optimizer/Tests/reorder01 fails; cf. e.g.,
http://monetdb.cwi.nl/testweb/tests/40815:0d7c7c8ec081/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/optimizer/reorder01.out.diff.html
Please check, whether this is a severe failure, or whether the output changes are correct and intended, and hence, the new output needs to be approved.
## Comment 16120
Date: 2011-08-21 18:30:07 +0200
From: @mlkersten
Affected by reorder implementation 40480:0b0cba05f046
## Comment 16244
Date: 2011-09-16 15:04:36 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| Test monetdb5/optimizer/Tests/reorder01 fails | https://api.github.com/repos/MonetDB/MonetDB/issues/2840/comments | 0 | 2020-11-30T11:43:53Z | 2024-06-27T11:52:25Z | https://github.com/MonetDB/MonetDB/issues/2840 | 753,407,158 | 2,840 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-18 12:27:20 +0200
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @mlkersten
Last updated: 2011-09-16 15:04:29 +0200
## Comment 15964
Date: 2011-07-18 12:27:20 +0200
From: @drstmane
Test monetdb5/optimizer/Tests/inlineFunction2 fails; cf. e.g.,
http://monetdb.cwi.nl/testweb/tests/40815:0d7c7c8ec081/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/optimizer/inlineFunction2.out.diff.html
Please check, whether this is a severe failure, or whether the output changes are correct and intended, and hence, the new output needs to be approved.
## Comment 16134
Date: 2011-08-22 11:06:10 +0200
From: @mlkersten
Fixed after ensuring type checking the MAL code first.
## Comment 16231
Date: 2011-09-16 15:04:29 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| test monetdb5/optimizer/Tests/inlineFunction2 fails | https://api.github.com/repos/MonetDB/MonetDB/issues/2839/comments | 0 | 2020-11-30T11:43:50Z | 2024-06-27T11:52:24Z | https://github.com/MonetDB/MonetDB/issues/2839 | 753,407,133 | 2,839 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-18 09:41:26 +0200
From: Alfred Nordman <<alfred.nordman>>
To: SQL devs <<bugs-sql>>
Version: 11.3.7 (Apr2011-SP2) [obsolete]
CC: alfred.nordman, @njnes
Last updated: 2011-09-16 15:04:36 +0200
## Comment 15963
Date: 2011-07-18 09:41:26 +0200
From: Alfred Nordman <<alfred.nordman>>
Entering the following SQL sequence doesn't return a result:
CREATE TABLE t (c int);
INSERT INTO t VALUES (1);
SELECT CASE WHEN CASE t.c WHEN 3 THEN TRUE ELSE FALSE END THEN 5 ELSE 7 END FROM t;
Instead, a message is printed:
"Predicate CASE 42: time to implement some more"
## Comment 15990
Date: 2011-07-27 20:19:48 +0200
From: @njnes
implemented the fallback for 'value expression' which are used as logical predicates, ie compute value and compare with true. Added test recursive_case.Bug-2838.sql
## Comment 15991
Date: 2011-07-27 20:31:03 +0200
From: @njnes
Changeset [a8f20d4e65ff](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a8f20d4e65ff) 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=a8f20d4e65ff](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a8f20d4e65ff)
Changeset description:
fix for Bug #2838 (ie handle case expression in condition part of a
case expression)
## Comment 16046
Date: 2011-07-29 11:03:53 +0200
From: @sjoerdmullender
Apr2011-SP2 has been released.
## Comment 16245
Date: 2011-09-16 15:04:36 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| Nested case results in message: "Predicate CASE 42: time to implement some more" | https://api.github.com/repos/MonetDB/MonetDB/issues/2838/comments | 0 | 2020-11-30T11:43:47Z | 2024-06-27T11:52:23Z | https://github.com/MonetDB/MonetDB/issues/2838 | 753,407,108 | 2,838 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-12 16:31:57 +0200
From: cdxxxx
To: SQL devs <<bugs-sql>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
CC: @njnes
Last updated: 2011-07-29 10:52:41 +0200
## Comment 15935
Date: 2011-07-12 16:31:57 +0200
From: cdxxxx
MonetDB5-SQL-Installer-x86_64-OID64-20110516.msi on Windows 7 x64
Script 1:
CREATE USER "SYSDBA" WITH PASSWORD 'masterkey' NAME 'SYSDBA' SCHEMA "sys";
CREATE SCHEMA "oe" AUTHORIZATION "SYSDBA";
ALTER USER "SYSDBA" SET SCHEMA "oe";
Script 2:
CREATE FUNCTION xtest(a integer) RETURNS TABLE(b integer) BEGIN RETURN TABLE(SELECT NULL); END;
Steps:
1) Launch server with clean DB
2) Launch mclient 1 with default user/password
3) Execute script 1 with client 1, do not close
4) Launch mclient 2 with user=SYSDBA password=masterkey (defined in script 1)
5) Execute script 2 with client 2, then \q
6) Press enter into client 1, observe server crash
Console windows:
Server:
c:\Program Files\MonetDB\MonetDB5>rmdir /S /Q d:\db\MonetDB5
c:\Program Files\MonetDB\MonetDB5>mkdir d:\db\MonetDB5
c:\Program Files\MonetDB\MonetDB5>setlocal&&SET APPDATA=d:\db\MonetDB5&& MSQLServer.bat --dbname=oetest&&endlocal
MonetDB 5 server v11.3.3 "Apr2011-SP1"
Serving database 'oetest', using 4 threads
Compiled for x86_64-pc-winnt/64bit with 64bit OIDs dynamically linked
Found 3.749 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2011 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/SQL module loaded
> SQL catalog created, loading sql scripts once
c:\Program Files\MonetDB\MonetDB5>
Client 1:
c:\Program Files\MonetDB\MonetDB5>mclient -d oetest
user(win32):monetdb
password:
Welcome to mclient, the MonetDB/SQL interactive terminal (Apr2011-SP1)
Database: MonetDB v11.3.3, 'oetest'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>CREATE USER "SYSDBA" WITH PASSWORD 'masterkey' NAME 'SYSDBA' SCHEMA "sys";
operation successful
sql>CREATE SCHEMA "oe" AUTHORIZATION "SYSDBA";
operation successful
sql>ALTER USER "SYSDBA" SET SCHEMA "oe";
operation successful
sql>
sql>
MAPI = monetdb@localhost:50000
ACTION= read_line
ERROR = !Connection terminated
Press any key to continue . . .
c:\Program Files\MonetDB\MonetDB5>
Client 2:
c:\Program Files\MonetDB\MonetDB5>mclient -d oetest -u SYSDBA
password:
Welcome to mclient, the MonetDB/SQL interactive terminal (Apr2011-SP1)
Database: MonetDB v11.3.3, 'oetest'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>CREATE FUNCTION xtest(a integer) RETURNS TABLE(b integer) BEGIN RETURN TABLE(SELECT NULL); END;
operation successful
sql>\q
c:\Program Files\MonetDB\MonetDB5>
## Comment 15936
Date: 2011-07-12 16:51:01 +0200
From: @sjoerdmullender
Also fails on Linux.
## Comment 15943
Date: 2011-07-13 22:00:00 +0200
From: @njnes
Changeset [f8bc98881e9d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f8bc98881e9d) 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=f8bc98881e9d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f8bc98881e9d)
Changeset description:
fixed Bug #2837 Server terminates after CREATE FUNCTION in multi-user scenario
(ie backported protection against empty list of tables)
## Comment 16002
Date: 2011-07-29 10:52:41 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| Server terminates after CREATE FUNCTION in multi-user scenario | https://api.github.com/repos/MonetDB/MonetDB/issues/2837/comments | 0 | 2020-11-30T11:43:44Z | 2024-06-27T11:52:22Z | https://github.com/MonetDB/MonetDB/issues/2837 | 753,407,083 | 2,837 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-11 19:10:08 +0200
From: @sjoerdmullender
To: buildtools devs <<bugs-buildtools>>
Version: 11.3.7 (Apr2011-SP2) [obsolete]
Last updated: 2011-09-16 15:04:29 +0200
## Comment 15934
Date: 2011-07-11 19:10:08 +0200
From: @sjoerdmullender
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0
Build Identifier:
At least on Fedora 15, if you have valgrind-devel installed, compilation fails with the default configure flags. The error is:
gdk/gdk_utils.mx: In function 'GDKmmap':
gdk/gdk_utils.mx:1436:3: error: variable '_qzz_res' set but not used [-Werror=unused-but-set-variable]
gdk/gdk_utils.mx: In function 'GDKmunmap':
gdk/gdk_utils.mx:1451:2: error: variable '_qzz_res' set but not used [-Werror=unused-but-set-variable]
cc1: all warnings being treated as errors
The reason is that the VALGRIND_MALLOCLIKE_BLOCK and VALGRIND_FREELIKE_BLOCK macros contain variables that are assigned to but never otherwise used. Unfortunately this is not something we can fix in our code.
Options are: remove the valgrind-specific code (the only thing it does is provide a better stack trace); or use less strict compilation flags when compiling gdk_utils.
Reproducible: Always
## Comment 15983
Date: 2011-07-25 10:59:27 +0200
From: @sjoerdmullender
Changeset [6f076133eeb0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=6f076133eeb0) 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=6f076133eeb0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=6f076133eeb0)
Changeset description:
Don't look for valgrind by default.
This should do for fixing bug #2836. It is up to the person
configuring MonetDB to use less strict compiler flags when including
valgrind support.
## Comment 16018
Date: 2011-07-29 10:58:18 +0200
From: @sjoerdmullender
Apr2011-SP2 has been released.
## Comment 16053
Date: 2011-07-29 13:22:59 +0200
From: @sjoerdmullender
This has been "fixed" in the sense that by default valgrind support is not enabled anymore. If you want valgrind support, you have to enable it, and you have to disable "strict" compilation.
## Comment 16230
Date: 2011-09-16 15:04:29 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| compilation fails when --with-valgrind in effect | https://api.github.com/repos/MonetDB/MonetDB/issues/2836/comments | 0 | 2020-11-30T11:43:41Z | 2024-06-27T11:52:21Z | https://github.com/MonetDB/MonetDB/issues/2836 | 753,407,054 | 2,836 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-08 11:53:57 +0200
From: Simon Brodt <<simon.brodt>>
To: SQL devs <<bugs-sql>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
CC: @njnes
Last updated: 2011-07-29 10:52:46 +0200
## Comment 15923
Date: 2011-07-08 11:53:57 +0200
From: Simon Brodt <<simon.brodt>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Build Identifier:
A UNIQUE constraint on an attribute that references another table is not enforced.
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE "test"."test" ("id" INT PRIMARY KEY );
CREATE TABLE "test"."test2" ("ref" INT REFERENCES "test"."test" , CONSTRAINT "unique" UNIQUE ("ref") );
INSERT INTO "test"."test" VALUES ('0');
INSERT INTO "test"."test2" VALUES ('0');
INSERT INTO "test"."test2" VALUES ('0');
### Actual Results:
Two equal tuples in the database.
### Expected Results:
Insertion error when attempting to insert the second tuple.
## Comment 15925
Date: 2011-07-08 12:40:23 +0200
From: @grobian
confirmed, most likely the unique isn't respected because the foreign key
## Comment 15927
Date: 2011-07-08 14:21:43 +0200
From: @grobian
It works when created as follows:
create table test (id int primary key);
create table test2 (id int unique references sys.test);
insert into test values (1);
insert into test2 values (1);
insert into test2 values (1);
SQLException:assert:INSERT INTO: UNIQUE constraint 'test2.test2_id_unique' violated
insert into test2 values (2);
SQLException:assert:INSERT INTO: FOREIGN KEY constraint 'test2.test2_id_fkey' violated
the following create statement also works correctly:
CREATE TABLE "test3" (
"id" INTEGER,
CONSTRAINT "test3_id_unique" UNIQUE ("id"),
CONSTRAINT "test3_id_fkey" FOREIGN KEY ("id") REFERENCES "sys"."test" ("id")
);
If the two constraints are swapped in order (like the original bug) then the unique check appears to be skipped.
## Comment 15940
Date: 2011-07-13 19:26:37 +0200
From: @njnes
Changeset [6cc71eb539a4](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=6cc71eb539a4) 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=6cc71eb539a4](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=6cc71eb539a4)
Changeset description:
fix bug #2835 in checking ukeys
## Comment 15941
Date: 2011-07-13 21:37:10 +0200
From: @njnes
bug consisted of 2 problems 1) single column keys (with columns equal to some other key constrained), weren't created
inserting index values for multiple indices failed .
both are resolved
## Comment 15942
Date: 2011-07-13 21:54:43 +0200
From: @njnes
Changeset [aaf264c72b6e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=aaf264c72b6e) 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=aaf264c72b6e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=aaf264c72b6e)
Changeset description:
fix bug #2835 in checking ukeys
(transplanted from 6cc71eb539a4d8e5fa3b7bb442d68ab647d1f7ad)
## Comment 15952
Date: 2011-07-17 14:16:56 +0200
From: @drstmane
Changeset [a4f1b7cdc6e9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a4f1b7cdc6e9) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a4f1b7cdc6e9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a4f1b7cdc6e9)
Changeset description:
added test for bug #2835
## Comment 16012
Date: 2011-07-29 10:52:46 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| UNIQUE Constraint is not enforced | https://api.github.com/repos/MonetDB/MonetDB/issues/2835/comments | 0 | 2020-11-30T11:43:38Z | 2024-06-27T11:52:20Z | https://github.com/MonetDB/MonetDB/issues/2835 | 753,407,018 | 2,835 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-08 10:47:53 +0200
From: Simon Brodt <<simon.brodt>>
To: clients devs <<bugs-clients>>
Version: 11.7.5 (Dec2011) [obsolete]
Last updated: 2012-03-02 13:35:13 +0100
## Comment 15913
Date: 2011-07-08 10:47:53 +0200
From: Simon Brodt <<simon.brodt>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Build Identifier:
After executing any DDL statement any PreparedStatement that was created before becomes invalid. In case of a SELECT statement this results in a SQLException "Query did not produce a result set" when calling the executeQuery() method.
In case of a UPDATE/DELETE/INSERT statement the statement seems to be executed correctly, but ist has no effect in the database and the returned update count is -1.
Sometimes both errors also occur spontaneously, i.e. without executing a DDL before.
Reproducible: Always
### Steps to Reproduce:
1.Prepare any DML statement
2. Execute any DDL statement
3. Execute previously prepared DML statement
Example are included in the attached JUnit files (2.-4. test method).
### Actual Results:
SELECT statement: SQLException "Query did not produce a result set"
UPDATE/DELETE/INSERT statement: update count -1 ; no effect in the database
### Expected Results:
SELECT statement: ResultSet
UPDATE/DELETE/INSERT statement: update count >= 0 ; effect in the database if update count > 0
See the attached file
## Comment 15914
Date: 2011-07-08 10:49:19 +0200
From: Simon Brodt <<simon.brodt>>
Created attachment 65
JUnit Test for reproducing the bug
Test methods 2-4 reproduce the bug.
> Attached file: [MonetDB.java](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2834_MonetDB.java_65) (text/plain, 3726 bytes)
> Description: JUnit Test for reproducing the bug
## Comment 15924
Date: 2011-07-08 12:35:07 +0200
From: @grobian
This is expected behaviour. DDL statements invalidate all prepared statements (because their correctness cannot be guaranteed). The bug here is that the server doesn't tell you your prepared handle is invalid.
## Comment 15926
Date: 2011-07-08 12:49:56 +0200
From: Simon Brodt <<simon.brodt>>
(In reply to comment 2)
> This is expected behaviour. DDL statements invalidate all prepared statements
> (because their correctness cannot be guaranteed). The bug here is that the
> server doesn't tell you your prepared handle is invalid.
That's fine with me, too.
Probably calling any execute method on the prepared statement should result in an exception then.
After fixing this issue, could you plese tell me how to recognize such an exception? (e.g. SQLState)
## Comment 16016
Date: 2011-07-29 10:57:51 +0200
From: @sjoerdmullender
Apr2011-SP2 has been released.
## Comment 16257
Date: 2011-09-16 15:07:28 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 16469
Date: 2011-10-26 14:09:46 +0200
From: @grobian
*** Bug #2899 has been marked as a duplicate of this bug. ***
## Comment 16470
Date: 2011-10-26 14:28:24 +0200
From: @grobian
Changeset [a9ec95c08325](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a9ec95c08325) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a9ec95c08325](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a9ec95c08325)
Changeset description:
query cache: keep last ID when renewing the cache
For bug #2834 (and 2899), make sure that we do not return the same id
on a connection to a client twice. When a scheme update is performed,
the query cache and prepared statements are destroyed. This is done for
all connected clients. Since clients cannot know that someone else
invalidated their prepared statements, the client must have a means to
figure out that the handle is invalid (or in the worst case, doesn't
belong to the query it thinks it belongs to).
We simply keep the id before we empty the cache, and put it back in
place again, such that the client always sees an incrementing counter.
| Prepared Statements fail after independent DDL statements (and sometimes spontaneously) | https://api.github.com/repos/MonetDB/MonetDB/issues/2834/comments | 0 | 2020-11-30T11:43:35Z | 2024-06-27T11:52:19Z | https://github.com/MonetDB/MonetDB/issues/2834 | 753,406,987 | 2,834 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-07 15:35:47 +0200
From: Simon Brodt <<simon.brodt>>
To: clients devs <<bugs-clients>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
Last updated: 2011-07-29 10:52:47 +0200
## Comment 15905
Date: 2011-07-07 15:35:47 +0200
From: Simon Brodt <<simon.brodt>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Build Identifier:
When the getMoreResults() Method on a java.sql.Statement instance is called and no result is available, then a NullPointerExceptuion is thrown instead of returning false.
Reproducible: Always
### Steps to Reproduce:
1. Start the monetDB SQL Server with database demo and login user=monetdb, password=monetdb (jdbc driver version = 1.20)
2. execute the first test in JUnit test class provided under Additional Information
3.
### Actual Results:
NullPointerException
### Expected Results:
false
package monetdb;
import static org.junit.Assert.*;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
import org.junit.After;
import org.junit.Before;
import org.junit.Test;
public class MonetDB {
Connection db_connection;
@Before
public void setUp() throws Exception {
nl.cwi.monetdb.jdbc.MonetDriver.getDriverVersion();
this.db_connection = DriverManager.getConnection("jdbc:monetdb://localhost/demo", "monetdb", "monetdb");
Statement s = this.db_connection.createStatement();
}
@Test
public void nullPointerExceptionOnGetMoreResults() throws SQLException{
Statement s = this.db_connection.createStatement();
assertTrue(s.getMoreResults());
}
@Test
public void robustnessOfPreparedStatements1() throws SQLException{
Statement s = this.db_connection.createStatement();
try{ s.execute("DROP SCHEMA \"test\";"); } catch(SQLException e){}
PreparedStatement p = this.db_connection.prepareStatement("SELECT 0;");
ResultSet r;
r = p.executeQuery();
s.execute("CREATE SCHEMA \"test\";");
r = p.executeQuery();
}
@Test
public void robustnessOfPreparedStatements2() throws SQLException{
Statement s = this.db_connection.createStatement();
try{ s.execute("DROP SCHEMA \"test\";"); } catch(SQLException e){}
s.execute("CREATE SCHEMA \"test\";");
PreparedStatement p = this.db_connection.prepareStatement("SELECT 0;");
ResultSet r;
r = p.executeQuery();
s.execute("CREATE TABLE \"test\".\"test\" (\"id\" INT);");
r = p.executeQuery();
}
@Test
public void robustnessOfPreparedStatements3() throws SQLException{
Statement s = this.db_connection.createStatement();
try{ s.execute("DROP SCHEMA \"test\";"); } catch(SQLException e){}
s.execute("CREATE SCHEMA \"test\";");
s.execute("CREATE TABLE \"test\".\"test\" (\"id\" INT);");
PreparedStatement p = this.db_connection.prepareStatement("INSERT INTO \"test\".\"test\" VALUES ('0');");
int updateCount;
updateCount = p.executeUpdate();
assertEquals(1, updateCount);
s.execute("CREATE TABLE \"test\".\"test2\" (\"id\" INT);");
updateCount = p.executeUpdate();
assertEquals(1, updateCount);
}
@Test(expected=SQLException.class)
public void uniquenessConstraint() throws SQLException{
Statement s = this.db_connection.createStatement();
try{ s.execute("DROP SCHEMA \"test\";"); } catch(SQLException e){}
s.execute("CREATE SCHEMA \"test\";");
s.execute("CREATE TABLE \"test\".\"test\" (\"id\" INT PRIMARY KEY );");
s.execute("CREATE TABLE \"test\".\"test2\" (\"ref\" INT REFERENCES \"test\".\"test\" , \"name\" CLOB, CONSTRAINT \"unique\" UNIQUE (\"ref\", \"name\") );");
int updateCount;
updateCount = s.executeUpdate("INSERT INTO \"test\".\"test\" VALUES ('0');");
assertEquals(1, updateCount);
updateCount = s.executeUpdate("INSERT INTO \"test\".\"test2\" VALUES ('0', 'hello');");
assertEquals(1, updateCount);
updateCount = s.executeUpdate("INSERT INTO \"test\".\"test2\" VALUES ('0', 'hello');");
}
@After
public void cleanUp() throws Exception {
Statement s = this.db_connection.createStatement();
try{ s.execute("DROP SCHEMA \"test\";"); } catch(SQLException e){}
this.db_connection.close();
}
}
## Comment 15906
Date: 2011-07-07 15:37:46 +0200
From: Simon Brodt <<simon.brodt>>
Created attachment 64
JUnit Test for reproducing the bug
> Attached file: [MonetDB.java](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2833_MonetDB.java_64) (application/octet-stream, 3547 bytes)
> Description: JUnit Test for reproducing the bug
## Comment 15907
Date: 2011-07-07 15:56:31 +0200
From: @grobian
do you have a stacktrace at hand, perhaps?
## Comment 15912
Date: 2011-07-07 19:41:30 +0200
From: Simon Brodt <<simon.brodt>>
(In reply to comment 2)
> do you have a stacktrace at hand, perhaps?
I added the following main method to the class:
public static void main(final String[] args) throws Exception{
MonetDB monetDB = new MonetDB();
monetDB.setUp();
monetDB.nullPointerExceptionOnGetMoreResults();
}
The produced Exception has the following stacktrace
Exception in thread "main" java.lang.NullPointerException
at nl.cwi.monetdb.jdbc.MonetStatement.getMoreResults(MonetStatement.java:772)
at nl.cwi.monetdb.jdbc.MonetStatement.getMoreResults(MonetStatement.java:749)
at monetdb.MonetDB.nullPointerExceptionOnGetMoreResults(MonetDB.java:36)
at monetdb.MonetDB.main(MonetDB.java:135)
Is this what you need?
## Comment 15915
Date: 2011-07-08 11:12:45 +0200
From: @grobian
Yes, thanks. The problem here is that you call getMoreResults() while you didn't ever run any query. The API docs don't give me any hint on to what to do in this case, but it feels like this is more of an error than it is "there are no results" to me.
## Comment 15916
Date: 2011-07-08 11:21:19 +0200
From: Simon Brodt <<simon.brodt>>
(In reply to comment 4)
> Yes, thanks. The problem here is that you call getMoreResults() while you
> didn't ever run any query. The API docs don't give me any hint on to what to
> do in this case, but it feels like this is more of an error than it is "there
> are no results" to me.
The error also occurs if you execute a statement and then call the method twice.
The JDBC API says that:
There are no more results when the following is true:
// stmt is a Statement object
((stmt.getMoreResults(current) == false) && (stmt.getUpdateCount() == -1))
Returns:
true if the next result is a ResultSet object; false if it is an update count or >>there are no more results<<
If the statement was never executed there just are no more reults, i.e. the Method should return false.
A NullointerExcetion should defnitly be wrong.
One could consider a SQLException but Im quite sure this is not in accordance with the API specification.
## Comment 15918
Date: 2011-07-08 11:26:23 +0200
From: @grobian
(In reply to comment 5)
> The error also occurs if you execute a statement and then call the method
> twice.
Odd, this is the primary use-case of this function, and e.g. JdbcClient works that way. Are you calling it unconditional, after the conditional you quoted below evaluated to true?
> If the statement was never executed there just are no more reults, i.e. the
> Method should return false.
You could consider it that way, yes.
> A NullointerExcetion should defnitly be wrong.
Fully agree.
> One could consider a SQLException but Im quite sure this is not in accordance
> with the API specification.
the API doesn't suggest this is the way to go, indeed
## Comment 15919
Date: 2011-07-08 11:34:03 +0200
From: Simon Brodt <<simon.brodt>>
> The error also occurs if you execute a statement and then call the method
> twice.
Sorry, seems that this is not correct. Thought I had tested this.
## Comment 15920
Date: 2011-07-08 11:47:02 +0200
From: @grobian
I created a testcase here to call getMoreResults() on an empty statement, but it doesn't crash at all here :/
## Comment 15921
Date: 2011-07-08 11:49:40 +0200
From: @grobian
Sorry, I can. Logic error here while testing.
## Comment 15922
Date: 2011-07-08 11:52:37 +0200
From: @grobian
Changeset [bac87d4ed683](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=bac87d4ed683) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bac87d4ed683](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bac87d4ed683)
Changeset description:
Statement: fix getMoreResults() NullPointerException on unitialised Statement
Return false from Statement.getMoreResults() instead of a
NullPointerException when no query has been performed on the Statement
yet, bug #2833
## Comment 16015
Date: 2011-07-29 10:52:47 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| NullPointerException when calling getMoreResults() on Statement without a query executed | https://api.github.com/repos/MonetDB/MonetDB/issues/2833/comments | 0 | 2020-11-30T11:43:33Z | 2024-06-27T11:52:18Z | https://github.com/MonetDB/MonetDB/issues/2833 | 753,406,959 | 2,833 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-07 11:07:57 +0200
From: cdxxxx
To: SQL devs <<bugs-sql>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
Last updated: 2011-07-29 10:52:43 +0200
## Comment 15903
Date: 2011-07-07 11:07:57 +0200
From: cdxxxx
MonetDB5-SQL-Installer-x86_64-OID64-20110516.msi on Windows 7 x64
Script:
create table blobtest(b blob);
insert into blobtest values(cast('00' as blob));
update blobtest set b=cast(cast(b as text)||cast(b as text) as blob);
Result:
Client console:
Welcome to mclient, the MonetDB/SQL interactive terminal (Apr2011-SP1)
Database: MonetDB v11.3.3, 'oetest'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>create table blobtest(b blob);
operation successful
sql>insert into blobtest values(cast('00' as blob));
1 affected row (12.894ms)
sql>update blobtest set b=cast(cast(b as text)||cast(b as text) as blob);
MAPI = monetdb@localhost:50000
ACTION= read_line
QUERY = update blobtest set b=cast(cast(b as text)||cast(b as text) as blob);
ERROR = !Connection terminated
Press any key to continue . . .
Server console:
c:\Program Files\MonetDB\MonetDB5>rmdir /S /Q d:\db\MonetDB5
c:\Program Files\MonetDB\MonetDB5>mkdir d:\db\MonetDB5
c:\Program Files\MonetDB\MonetDB5>setlocal&&SET APPDATA=d:\db\MonetDB5&&MSQLServer.bat --dbname=oetest&&endlocal
MonetDB 5 server v11.3.3 "Apr2011-SP1"
Serving database 'oetest', using 4 threads
Compiled for x86_64-pc-winnt/64bit with 64bit OIDs dynamically linked
Found 3.749 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2011 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/SQL module loaded
> SQL catalog created, loading sql scripts once
c:\Program Files\MonetDB\MonetDB5>
## Comment 15908
Date: 2011-07-07 17:50:13 +0200
From: @sjoerdmullender
Changeset [fc0f336bbc42](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=fc0f336bbc42) 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=fc0f336bbc42](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fc0f336bbc42)
Changeset description:
Added test for bug #2832.
## Comment 15909
Date: 2011-07-07 17:50:14 +0200
From: @sjoerdmullender
Changeset [bcdf2606e893](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=bcdf2606e893) 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=bcdf2606e893](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bcdf2606e893)
Changeset description:
Fix for bug #2832.
The cast code needs to differentiate between varsized and non-varsized
data types.
## Comment 15910
Date: 2011-07-07 17:53:18 +0200
From: @sjoerdmullender
The bug is fixed in the Apr2011 branch.
The problem was specifically with BLOBs.
## Comment 16005
Date: 2011-07-29 10:52:43 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| Server terminates upon UPDATE | https://api.github.com/repos/MonetDB/MonetDB/issues/2832/comments | 0 | 2020-11-30T11:43:30Z | 2024-06-27T11:52:17Z | https://github.com/MonetDB/MonetDB/issues/2832 | 753,406,936 | 2,832 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-04 23:41:25 +0200
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @njnes
Last updated: 2011-07-29 10:52:42 +0200
## Comment 15888
Date: 2011-07-04 23:41:25 +0200
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20100101 Firefox/5.0
Build Identifier:
Crash during query analysis. Assertion fires.
Reproducible: Always
### Steps to Reproduce:
create schema lrbm;
CREATE TABLE lrbm.accident(carid1 integer, carid2 integer, firstMinute integer, lastMinute integer, dir integer, seg integer, pos integer);
CREATE TABLE lrbm.statistics(dir int,seg int,time_minute int,numvehicles int,lav float,toll int,accident int,accidentSeg int);
UPDATE lrbm.statistics
SET toll = 0, accident = 1
WHERE EXISTS(
SELECT acc.seg
FROM lrbm.accident AS acc
WHERE acc.dir = statistics.dir AND
acc.firstMinute + 1 <= statistics.time_minute AND
acc.lastMinute + 1 >= statistics.time_minute AND
(
(
(acc.dir = 0) AND
(acc.seg >= statistics.seg) AND
(acc.seg <= statistics.seg + 4)
)
OR
(
(acc.dir <> 0) AND
(acc.seg <= statistics.seg) AND
(acc.seg >= statistics.seg - 4)
)
)
);
### Actual Results:
assertion error in
3 0x00007fffe86157bd in rel_join_add_exp (sa=0x134db48, rel=0x1353dc8, e=0x1353f58) at /ufs/mk/current//package/sql/server/rel_select.c:559
## Comment 15900
Date: 2011-07-06 10:10:00 +0200
From: @njnes
improved assert (fixes crash)
## Comment 15953
Date: 2011-07-17 14:52:13 +0200
From: @drstmane
Changeset [46246a2dc026](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=46246a2dc026) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=46246a2dc026](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=46246a2dc026)
Changeset description:
added test for bug #2831
## Comment 16003
Date: 2011-07-29 10:52:42 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| Crash in query analysis | https://api.github.com/repos/MonetDB/MonetDB/issues/2831/comments | 0 | 2020-11-30T11:43:28Z | 2024-06-27T11:52:16Z | https://github.com/MonetDB/MonetDB/issues/2831 | 753,406,911 | 2,831 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-04 12:47:29 +0200
From: @bartscheers
To: SQL devs <<bugs-sql>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
CC: @njnes, @drstmane
Last updated: 2011-07-29 10:52:36 +0200
## Comment 15883
Date: 2011-07-04 12:47:29 +0200
From: @bartscheers
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.2.17) Gecko/20110428 Fedora/3.6.17-1.fc14 Firefox/3.6.17
Build Identifier:
Trying to use floor function failed:
select floor(30.-0.025);
and also:
select 30. - 0.025;
with message: ERROR = !SQLException:convert:too many digits (5 > 3)
Reproducible: Always
### Steps to Reproduce:
1. select 30. - 0.025;
2.
3.
### Actual Results:
ERROR = !SQLException:convert:too many digits (5 > 3)
### Expected Results:
29.975
workaround possible :
select cast(30. as double) - 0.025;
## Comment 15911
Date: 2011-07-07 18:08:22 +0200
From: @sjoerdmullender
Also an issue on the Apr2011 branch.
## Comment 15917
Date: 2011-07-08 11:23:38 +0200
From: @drstmane
It seems that the function that decimals to scaled integers is called with incorrect parameters, i.e., ignoring the number of digits of the original value;
in this case,
calc.sht(0,30:bte,3,3);
should be replaced by
calc.sht(0,30:bte,5,3);
30 shifted by 3 digits to the left (*1000) results in 5 digits, not in 3 digits.
sql>plan select 30. - 0.025;
+----------------------------------------------------------------+
| rel |
+================================================================+
| [ sql_sub(convert(30 from decimal(2) to decimal(3,3)), 25) ] |
+----------------------------------------------------------------+
1 tuple (0.513ms)
sql>explain select 30. - 0.025;
+--------------------------------------------------------------------------+
| mal |
+==========================================================================+
| function user.s1_1{autoCommit=true}():void; |
| _4 := calc.sht(0,30:bte,3,3); |
| _8 := calc.-(_4,25:sht); |
| sql.exportValue(1,".","sql_sub_single_value","decimal",4,3,8,_8,""); |
| end s1_1; |
+--------------------------------------------------------------------------+
5 tuples (1.253ms)
sql>trace select 30. - 0.025;
SQLException:convert:too many digits (5 > 3)
sql>debug select 30. - 0.025;
mdb> mdb.start();
mdb>n
mdb> user.s0_1(30,25:sht);
mdb>
mdb> _5 := calc.sht(0,A0=30,3,3);
mdb>
ERROR: SQLException:convert:too many digits (5 > 3)
ERROR: SQLException:convert:too many digits (5 > 3)
SQLException:convert:too many digits (5 > 3)
mdb>
## Comment 15946
Date: 2011-07-13 22:37:52 +0200
From: @njnes
corrected coercion to supertype of left and right
## Comment 15993
Date: 2011-07-29 10:52:36 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| select 30.0 - 0.025; conversion to decimal type gives error | https://api.github.com/repos/MonetDB/MonetDB/issues/2830/comments | 0 | 2020-11-30T11:43:25Z | 2024-06-27T11:52:15Z | https://github.com/MonetDB/MonetDB/issues/2830 | 753,406,873 | 2,830 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-07-03 15:52:52 +0200
From: james.hutchby
To: clients devs <<bugs-clients>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
Last updated: 2011-07-29 10:52:42 +0200
## Comment 15879
Date: 2011-07-03 15:52:52 +0200
From: james.hutchby
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Build Identifier:
Thanks for the great python library!
I noticed a minor issue on line 240 of mapi2.py; logging.debug is used, rather than logger.debug.
I'm using python-monetdb-1.0.tar.gz.
Reproducible: Always
## Comment 15880
Date: 2011-07-03 20:55:35 +0200
From: @sjoerdmullender
Changeset [8269b6cab44d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=8269b6cab44d) 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=8269b6cab44d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=8269b6cab44d)
Changeset description:
Use logger.debug instead of logging.debug.
This fixes bug #2829.
## Comment 15881
Date: 2011-07-03 20:56:34 +0200
From: @sjoerdmullender
mapi3.py had the same problem.
Thanks for noticing.
## Comment 16004
Date: 2011-07-29 10:52:42 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| logging issue | https://api.github.com/repos/MonetDB/MonetDB/issues/2829/comments | 0 | 2020-11-30T11:43:22Z | 2024-06-27T11:52:14Z | https://github.com/MonetDB/MonetDB/issues/2829 | 753,406,843 | 2,829 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-06-30 00:46:56 +0200
From: Philippe <<philippe.hanrigou>>
To: clients devs <<bugs-clients>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
Last updated: 2011-09-16 15:04:31 +0200
## Comment 15860
Date: 2011-06-30 00:46:56 +0200
From: Philippe <<philippe.hanrigou>>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_8; en-us) AppleWebKit/533.21.1 (KHTML, like Gecko) Version/5.0.5 Safari/533.21.1
Build Identifier:
Due to another bug our MonetDB ends up with a crashed database on a regular basis. As a consequence we realized that in this situation our entire application server would go down even for workloads not related to MonetDB. This is because any request to MonetDB via Java (JDBC or not) would hand forever on a read (sample stack trace included below).
This is because java sockets have an infinite timeout by default. It would be great if you guys gave an option for the client API to customize the socket timeout at the driver level. It would provide better recovery and stability to any java client. For Example, here is a patch that solved the problem for us:
diff -r a3349ca90986 java/src/nl/cwi/monetdb/jdbc/MonetConnection.java
--- a/java/src/nl/cwi/monetdb/jdbc/MonetConnection.java Tue Jun 28 11:35:22 2011 -0700
+++ b/java/src/nl/cwi/monetdb/jdbc/MonetConnection.java Tue Jun 28 15:06:44 2011 -0700
@@ -118,6 +118,9 @@
/** Whether or not BLOB is mapped to BINARY within the driver */
private final boolean blobIsBinary;
+ /** SO_TIMEOUT for the underlying java.net.Socket */
+ private final int socketTimeoutInMillis;
+
/**
* Constructor of a Connection for MonetDB. At this moment the
* current implementation limits itself to storing the given host,
@@ -149,7 +152,16 @@
boolean debug = Boolean.valueOf(props.getProperty("debug")).booleanValue();
String hash = props.getProperty("hash");
blobIsBinary = Boolean.valueOf(props.getProperty("treat_blob_as_binary")).booleanValue();
-
+ int timeout = 0;
+ String timeoutStr = props.getProperty("socket_timeout");
+ if (null != timeoutStr) {
+ try {
+ timeout = Integer.parseInt(timeoutStr);
+ } catch (NumberFormatException e) {
+ addWarning("Invalid socket timeout " + timeoutStr + ", defaulting to 0");
+ }
+ }
+ this.socketTimeoutInMillis = timeout;
// check input arguments
if (hostname == null || hostname.trim().equals(""))
throw new IllegalArgumentException("hostname should not be null or empty");
@@ -169,6 +181,7 @@
commandTempl = new String[3]; // pre, post, sep
server = new MapiSocket();
+ server.setSoTimeout(socketTimeoutInMillis);
if (hash != null) server.setHash(hash);
if (database != null) server.setDatabase(database);
diff -r a3349ca90986 java/src/nl/cwi/monetdb/mcl/net/MapiSocket.java
--- a/java/src/nl/cwi/monetdb/mcl/net/MapiSocket.java Tue Jun 28 11:35:22 2011 -0700
+++ b/java/src/nl/cwi/monetdb/mcl/net/MapiSocket.java Tue Jun 28 15:06:44 2011 -0700
@@ -119,6 +119,9 @@
/** A short in two bytes for holding the block size in bytes */
private byte[] blklen = new byte[2];
+ /** SO_TIMEOUT value for the underlying java.net.Socket */
+ private int socketTimeoutInMillis = 0;
+
/**
* Constructs a new MapiSocket.
*/
@@ -203,7 +206,7 @@
* @throws MCLParseException if bogus data is received
* @throws MCLException if an MCL related error occurs
*/
- public List connect(String host, int port, String user, String pass)
+ public List connect(String host, int port, String user, String pass)
throws IOException, MCLParseException, MCLException
{
// Wrap around the internal connect that needs to know if it
@@ -212,7 +215,7 @@
}
private List connect(String host, int port, String user, String pass,
- boolean makeConnection)
+ boolean makeConnection)
throws IOException, MCLParseException, MCLException
{
if (ttl-- <= 0)
@@ -223,6 +226,7 @@
// set nodelay, as it greatly speeds up small messages (like we
// often do)
con.setTcpNoDelay(true);
+ con.setSoTimeout(socketTimeoutInMillis);
fromMonet = new BlockInputStream(con.getInputStream());
toMonet = new BlockOutputStream(con.getOutputStream());
@@ -584,6 +588,22 @@
}
/**
+ * Set the SO_TIMEOUT on the underlying Java socket using java.net.SocketsetSoTimeout.
+ * Useful to avoid consuming client threads blocked on read when the MonetDB database
+ * is in a crashed state.
+ *
+ * The option must be enabled prior to entering the blocking operation to have effect.
+ *
+ * @see http://download.oracle.com/javase/1.4.2/docs/api/java/net/Socket.htmlsetSoTimeout(int)
+ *
+ * @param timeout The specified timeout, in milliseconds. A timeout
+ * of zero is interpreted as an infinite timeout.
+ */
+ public void setSoTimeout(int socketTimeoutInMillis) {
+ this.socketTimeoutInMillis = socketTimeoutInMillis;
+ }
+
+ /**
* Returns the mapi protocol version used by this socket. The
* protocol version depends on the server being used. Users of the
* MapiSocket should check this version to act appropriately.
@@ -678,7 +698,7 @@
// write the actual block
out.write(block, 0, writePos);
-
+
if (debug) {
if (last) {
logTd("write final block: " + writePos + " bytes");
======== Sample Stack trace of a "hanging" read =============
"pool-4-thread-29" prio=10 tid=0x00007f3119335000 nid=0x3f4e sleeping[0x00007f3120aa6000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
- locked <0x00000007bd1c3590> (a java.io.BufferedInputStream)
at nl.cwi.monetdb.mcl.net.MapiSocket$BlockInputStream._read(MapiSocket.java:782)
at nl.cwi.monetdb.mcl.net.MapiSocket$BlockInputStream.readBlock(MapiSocket.java:829)
at nl.cwi.monetdb.mcl.net.MapiSocket$BlockInputStream.read(MapiSocket.java:901)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
- locked <0x00000007a33916a0> (a java.io.InputStreamReader)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
- locked <0x00000007a33916a0> (a java.io.InputStreamReader)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at nl.cwi.monetdb.mcl.io.BufferedMCLReader.readLine(BufferedMCLReader.java:109)
at nl.cwi.monetdb.mcl.net.MapiSocket.connect(MapiSocket.java:239)
at nl.cwi.monetdb.mcl.net.MapiSocket.connect(MapiSocket.java:211)
at nl.cwi.monetdb.jdbc.MonetConnection.<init>(MonetConnection.java:203)
at nl.cwi.monetdb.jdbc.MonetDriver.connect(MonetDriver.java:159)
at java.sql.DriverManager.getConnection(DriverManager.java:582)
at java.sql.DriverManager.getConnection(DriverManager.java:154)
at clojure.contrib.sql.internal$get_connection.invoke(internal.clj:85)
at clojure.contrib.sql.internal$with_connection_STAR_.invoke(internal.clj:102)
Reproducible: Always
### Steps to Reproduce:
1. Crash a MonetDB database
2. Have a Java client try to access the database
3. Client hangs forever and consume threads (or at least a very long time) even if the database is recovered
### Actual Results:
Thread blocked forever on a read
### Expected Results:
Exception or error message after some configurable timeout option
## Comment 15861
Date: 2011-06-30 08:18:04 +0200
From: @grobian
Your patch looks ok to me, apart from the indentation. Could you please use tabs, and attach your patch so that I can apply it? Thanks in advance!
## Comment 15863
Date: 2011-06-30 20:43:31 +0200
From: Philippe <<philippe.hanrigou>>
Created attachment 62
Patch to add customizable socket timeout for the Java API
Cleaned up patch to use tabs
> Attached file: [monetdb-add-java-timeout.diff](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2828_monetdb-add-java-timeout.diff_62) (text/plain, 4521 bytes)
> Description: Patch to add customizable socket timeout for the Java API
## Comment 15864
Date: 2011-06-30 21:31:18 +0200
From: @grobian
Thanks, I cannot fix this in the Apr2011 branch, since this is more a feature than a (bug)fix.
## Comment 15865
Date: 2011-06-30 21:31:43 +0200
From: @grobian
Changeset [d9f7d6285c63](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=d9f7d6285c63) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=d9f7d6285c63](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=d9f7d6285c63)
Changeset description:
JDBC: add so_timeout Driver property
On case the server locks up, the JDBC remains "hanging" too, waiting for
the server to send something. When the so_timeout property is set, a
timeout for this can be set, such that the read eventually breaks, and
the caller (application) can continue.
Based on original patch by Philippe Hanrigou in bug #2828
## Comment 16235
Date: 2011-09-16 15:04:31 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| No Socket Timeout: MonetDB Java client hangs forever on reads and consume threads when the database is crashed | https://api.github.com/repos/MonetDB/MonetDB/issues/2828/comments | 0 | 2020-11-30T11:43:19Z | 2024-06-27T11:52:13Z | https://github.com/MonetDB/MonetDB/issues/2828 | 753,406,806 | 2,828 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-06-29 16:29:35 +0200
From: Milena Ivanova <<M.Ivanova>>
To: clients devs <<bugs-clients>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
Last updated: 2011-07-29 10:52:41 +0200
## Comment 15859
Date: 2011-06-29 16:29:35 +0200
From: Milena Ivanova <<M.Ivanova>>
When stethoscope listens to multiple servers using a pattern, the <module.function> filter is set incorrectly:
1)
stethoscope -umonetdb -Pmonetdb -p50500 -d "tent*" +stb "octopus.*"
-- connection with server mapi:monetdb://palu.ins.cwi.nl:50500/tent1 is [1]
-- connection with server mapi:monetdb://palu.ins.cwi.nl:50500/tent2 is [2]
...
-- [1] opened UDP profile stream for palu.ins.cwi.nl:50010
-- [2] opened UDP profile stream for palu.ins.cwi.nl:50011
-- [1] profiler.setFilter("octopus","*");
-- [2] profiler.setFilter("*","octopus");
2)
stethoscope -umonetdb -Pmonetdb -p50500 -d "tent*" +stb "remote.get"
...
-- [2] profiler.setFilter("remote","get");
-- [1] profiler.setFilter("*","remote");
## Comment 15870
Date: 2011-07-01 15:53:26 +0200
From: @grobian
Changeset [ae0c67221196](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ae0c67221196) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ae0c67221196](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ae0c67221196)
Changeset description:
stethoscope: properly set mod.fcn filter for all connections
Fix for bug #2827, when multiple targets are used, the filter would not
be correct for all but the first connection to set the filter. This
obviously was caused by sharing the same buffer and modifying it. We
now copy the buffer before modifying it.
## Comment 16001
Date: 2011-07-29 10:52:41 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| Incorrect filter setting when listening to several servers | https://api.github.com/repos/MonetDB/MonetDB/issues/2827/comments | 0 | 2020-11-30T11:43:16Z | 2024-06-27T11:52:12Z | https://github.com/MonetDB/MonetDB/issues/2827 | 753,406,772 | 2,827 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-06-24 15:45:25 +0200
From: @bartscheers
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @mlkersten
Last updated: 2011-07-29 10:52:44 +0200
## Comment 15853
Date: 2011-06-24 15:45:25 +0200
From: @bartscheers
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.2.17) Gecko/20110428 Fedora/3.6.17-1.fc14 Firefox/3.6.17
Build Identifier:
Function used in where clause iterates over column and slows down performance
Reproducible: Always
### Steps to Reproduce:
1. create table tab (d double);
2. insert into tab values (1.0),(2.0),(3.0),(4.0),(5.0);
3. create function func(f real) returns real begin return log10(f); end;
4. explain select * from tab where func(d) > 1;
+------------------------------------------------------------------------------+
| mal |
+==============================================================================+
| function user.s2_1{autoCommit=true}():void; |
| _2 := sql.mvc(); |
| barrier _48 := language.dataflow(); |
| _10:bat[:oid,:dbl] := sql.bind(_2,"sys","tab","d",0); |
| _8:bat[:oid,:dbl] := sql.bind(_2,"sys","tab","d",2); |
| _12 := algebra.kdifference(_10,_8); |
| _13 := algebra.kunion(_12,_8); |
| _5:bat[:oid,:dbl] := sql.bind(_2,"sys","tab","d",1); |
| _14 := algebra.kunion(_13,_5); |
| _15:bat[:oid,:oid] := sql.bind_dbat(_2,"sys","tab",1); |
| _16 := bat.reverse(_15); |
| _17 := algebra.kdifference(_14,_16); |
| _18 := batcalc.flt(_17); |
| exit _48; |
| _54 := bat.new(nil:oid,nil:flt); |
| barrier (_57,_58,_59) := bat.newIterator(_18); |
| _61 := user.func(_59); |
| bat.insert(_54,_58,_61); |
| redo (_57,_58,_59) := bat.hasMoreElements(_18); |
| exit (_57,_58,_59); |
| _18 := nil:BAT; |
| _19:bat[:oid,:flt] := _54; |
| barrier _51 := language.dataflow(); |
| _22 := algebra.thetauselect(_19,1:flt,">"); |
| _24 := algebra.markT(_22,0@0:oid); |
| _25 := bat.reverse(_24); |
| _26 := algebra.leftjoin(_25,_14); |
| exit _51; |
| _27 := sql.resultSet(1,1,_26); |
| sql.rsColumn(_27,"sys.tab","d":str,"double",53,0,_26); |
| _33 := io.stdout(); |
| sql.exportResult(_33,_27); |
| end s2_1; |
+------------------------------------------------------------------------------+
### Actual Results:
For larger table contents this gets too slow.
## Comment 15854
Date: 2011-06-24 23:39:55 +0200
From: @mlkersten
The inline optimizer has been patched to compile simple arithmetic functions
into their BAT equivalent. Not all calc/mtime/mmath/str operations have their BAT
equivalent yet. It should remove the performance degradation caused by the iterator in many cases.
## Comment 15857
Date: 2011-06-26 14:35:33 +0200
From: @mlkersten
Problem located. The system injects a sql.mvc() call in each SQL function, which was marked as potentially side-effect prone. This, in combination with looking also at the optimizer pipe to determine side-effects, was resolved in the opt_support.mx file.
## Comment 15957
Date: 2011-07-17 15:27:48 +0200
From: @drstmane
Changeset [465740af8349](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=465740af8349) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=465740af8349](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=465740af8349)
Changeset description:
added test for bug #2826
## Comment 16008
Date: 2011-07-29 10:52:44 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
## Comment 17572
Date: 2012-07-25 15:47:33 +0200
From: @drstmane
Changeset [93446c850c0a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=93446c850c0a) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=93446c850c0a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=93446c850c0a)
Changeset description:
func_iter_vs_bulk.Bug-2826: use sequential pipeline to ensure deterministic output
also on multi-core systems
This fixes bug #3132.
## Comment 17630
Date: 2012-08-19 10:37:04 +0200
From: @drstmane
Changeset [69254a78c7aa](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=69254a78c7aa) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=69254a78c7aa](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=69254a78c7aa)
Changeset description:
func_iter_vs_bulk.Bug-2826: updated stable output after rechent checkin(s)
| sql function iterates instead of bulk processing | https://api.github.com/repos/MonetDB/MonetDB/issues/2826/comments | 0 | 2020-11-30T11:43:13Z | 2024-06-27T11:52:11Z | https://github.com/MonetDB/MonetDB/issues/2826 | 753,406,741 | 2,826 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-06-23 15:30:35 +0200
From: Gunnar Schröder <<gunnar.schroeder>>
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
CC: @drstmane
Last updated: 2011-07-29 10:52:47 +0200
## Comment 15852
Date: 2011-06-23 15:30:35 +0200
From: Gunnar Schröder <<gunnar.schroeder>>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Build Identifier:
The SQL-Statement "Insert into ... select distinct ..." and some "Insert into ... select ... group by ..." statements fail.
Reproducible: Always
### Steps to Reproduce:
create table table1 (user_id integer, item_id integer);
create table table2 (user_id integer, item_id integer, primary key(user_id, item_id));
insert into table1 values (1,1);
INSERT INTO table2(user_id,item_id)
SELECT DISTINCT USER_ID, ITEM_ID
FROM table1;
delete from table2;
insert into table1 values (1,1);
SELECT DISTINCT USER_ID, ITEM_ID
FROM table1;
INSERT INTO table2(user_id,item_id)
SELECT DISTINCT USER_ID, ITEM_ID
FROM table1;
drop table table1;
drop table table2;
### Actual Results:
Fails with exception:
MALException:mkey.bulk_rotate_xor_hash:operation failed Left operand not writeable
### Expected Results:
Successful insert operation was expected.
Besides distinct this problem applies also to some group by constructs.
## Comment 15902
Date: 2011-07-06 19:03:49 +0200
From: @drstmane
Changeset [b69c9f900572](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b69c9f900572) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b69c9f900572](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b69c9f900572)
Changeset description:
fixed bug #2825:
since changeset [1c689400661e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1c689400661e) bulk_rotate_xor_hash() has side-effect free, i.e.,
produces a new result BAT instead of modifying its first input in place;
thus, the first (left) operand may well be read-only (or a view).
Removed the obsolete check that raised a false exception.
Added test in sql/test/BugTracker-2011/Tests/mkey-bulk_rotate_xor_hash.Bug-2825.*
## Comment 16014
Date: 2011-07-29 10:52:47 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| "Insert into ... select distinct ..." fails with MALException:mkey.bulk_rotate_xor_hash:operation | https://api.github.com/repos/MonetDB/MonetDB/issues/2825/comments | 0 | 2020-11-30T11:43:10Z | 2024-06-27T11:52:10Z | https://github.com/MonetDB/MonetDB/issues/2825 | 753,406,703 | 2,825 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-06-20 12:09:35 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @mlkersten
Last updated: 2011-06-25 00:37:40 +0200
## Comment 15851
Date: 2011-06-20 12:09:35 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.24 Safari/535.1
Build Identifier:
As from the mailinglist presented was;
CREATE FUNCTION isInRangexy(x DECIMAL(10,7), y DECIMAL(10,7)) RETURNS BOOL
BEGIN ATOMIC
IF x > 50 AND y < 50 THEN
RETURN true;
ELSE
RETURN false;
END IF;
END
Martin's suggestion;
CREATE FUNCTION isInRangexy(x DECIMAL(10,7), y DECIMAL(10,7)) RETURNS BOOL
BEGIN ATOMIC
RETURN x > 50 AND y < 50;
END
Define an optimiser that can recognise the simple patterns in if-then(-else), return true else return false (or its inverse). Optimise the function to represent the return (constraint) or return not (constraint).
Reproducible: Always
## Comment 15855
Date: 2011-06-24 23:46:26 +0200
From: @mlkersten
This suggestion is dropped. At the MAL level such an analysis is hardly possible, due to the covert channels it may induce. Instead, this is simple programmers knowledge.
A related bug #2826 covers it for scalar expressions.
## Comment 15856
Date: 2011-06-25 00:37:40 +0200
From: @skinkie
(In reply to comment 1)
> This suggestion is dropped. At the MAL level such an analysis is hardly
> possible, due to the covert channels it may induce. Instead, this is simple
> programmers knowledge.
When done at SQL level, similar to optimisations for count(*) with a crossproduct, it is not difficult to do?
| Function optimiser/rewrite mechanism for simple true else false | https://api.github.com/repos/MonetDB/MonetDB/issues/2824/comments | 0 | 2020-11-30T11:43:07Z | 2024-06-28T13:40:45Z | https://github.com/MonetDB/MonetDB/issues/2824 | 753,406,666 | 2,824 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-06-14 18:18:48 +0200
From: Simon Brodt <<simon.brodt>>
To: SQL devs <<bugs-sql>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
Last updated: 2011-07-29 10:52:36 +0200
## Comment 15847
Date: 2011-06-14 18:18:48 +0200
From: Simon Brodt <<simon.brodt>>
This query throws an MAL exception:
SELECT * FROM (SELECT 0 AS "value") AS row WHERE row.value = (SELECT 0) AND row.value = 0;
TypeException:user.s1_2[15]:'bat.reverse' undefined in: _22:any := bat.reverse(_21:bte)
TypeException:user.s1_2[29]:'algebra.join' undefined in: _38:any := algebra.join(_37:bat[:oid,:void], _22:any)
SQLException:SQLengine:Program contains errors
This equivalent query performs correctly:
SELECT * FROM (SELECT 0 AS "value") AS row WHERE row.value = 0 AND row.value =(SELECT 0);
## Comment 15848
Date: 2011-06-17 14:27:53 +0200
From: @njnes
Changeset [7ec5c5f4f8c7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=7ec5c5f4f8c7) 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=7ec5c5f4f8c7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7ec5c5f4f8c7)
Changeset description:
fixed bug #2823 MAL exeption on SQL query with subquery in the where part
We shouldn't have select statements in the semijoin join expression list.
## Comment 15849
Date: 2011-06-17 15:57:32 +0200
From: @njnes
Changeset [dbe413ad56aa](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=dbe413ad56aa) 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=dbe413ad56aa](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=dbe413ad56aa)
Changeset description:
fixed bug #2823 MAL exeption on SQL query with subquery in the where part
We shouldn't have select statements in the semijoin join expression list.
(transplanted from 7ec5c5f4f8c7d73d0c63e801dd7b70429ecbd0a1)
## Comment 15850
Date: 2011-06-17 16:00:23 +0200
From: @grobian
You can use tonight's nightly installer to verify the issue has been fixed for you. Thanks!
## Comment 15956
Date: 2011-07-17 15:19:15 +0200
From: @drstmane
Changeset [21d0c851f315](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=21d0c851f315) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=21d0c851f315](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=21d0c851f315)
Changeset description:
added test for bug #2823
## Comment 15992
Date: 2011-07-29 10:52:36 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| MAL exeption on SQL query with subquery in the where part | https://api.github.com/repos/MonetDB/MonetDB/issues/2823/comments | 0 | 2020-11-30T11:43:05Z | 2024-06-27T11:52:08Z | https://github.com/MonetDB/MonetDB/issues/2823 | 753,406,638 | 2,823 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-06-13 15:25:58 +0200
From: Alfred Nordman <<alfred.nordman>>
To: SQL devs <<bugs-sql>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
CC: @njnes
Last updated: 2011-07-29 10:52:45 +0200
## Comment 15845
Date: 2011-06-13 15:25:58 +0200
From: Alfred Nordman <<alfred.nordman>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Build Identifier:
Having a CASE statement with a division and an additional arithmetic operation, when there's a 0 value in a column, results in a division by zero ArithmeticException.
Removing the additional arithmetic operation while keeping the division, makes the query produce the correct results.
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE t (c INT);
INSERT INTO t VALUES (0);
SELECT CASE WHEN (c = 0) THEN 0 ELSE (c / c + 1) END FROM t;
### Actual Results:
ArithmeticException:batcalc./:Division by zero
### Expected Results:
+-----------------------+
| ifthenelse_isnull_=_c |
+=======================+
| 0 |
+-----------------------+
MonetDB 5 server v11.3.3 "Apr2011-SP1" (64-bit, 32-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2011 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 8.0GiB available memory
Libraries:
libpcre: 8.10 2010-06-25
openssl: OpenSSL 1.0.0a 1 Jun 2010
libxml2: 2.7.7
Compiled by: sjoerd@LAB03 (x86_64-pc-winnt)
Compilation: cl -GF -W3 -wd4273 -wd4102 -MD -nologo -Ox
Linking : cl -GF -W3 -wd4273 -wd4102 -MD -nologo -Ox
## Comment 15878
Date: 2011-07-02 14:09:02 +0200
From: @njnes
Changeset [5e65f282eeab](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=5e65f282eeab) 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=5e65f282eeab](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=5e65f282eeab)
Changeset description:
handle div-zero protection recusively fixes bug #2822
## Comment 15954
Date: 2011-07-17 15:01:22 +0200
From: @drstmane
Changeset [b26f389978e4](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b26f389978e4) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b26f389978e4](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b26f389978e4)
Changeset description:
added test for bug #2822
## Comment 16010
Date: 2011-07-29 10:52:45 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| A query with CASE and division results in ArithmeticException | https://api.github.com/repos/MonetDB/MonetDB/issues/2822/comments | 0 | 2020-11-30T11:43:01Z | 2024-06-27T11:52:07Z | https://github.com/MonetDB/MonetDB/issues/2822 | 753,406,597 | 2,822 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-06-13 07:46:53 +0200
From: ramaK <<ramakumar_rk>>
To: SQL devs <<bugs-sql>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
CC: @njnes, @drstmane
Last updated: 2011-07-29 10:52:39 +0200
## Comment 15843
Date: 2011-06-13 07:46:53 +0200
From: ramaK <<ramakumar_rk>>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110422 Ubuntu/10.10 (maverick) Firefox/3.6.17
Build Identifier:
On a server started with "--single-user" option, trying to run any select query with group by on Multiple columns crashes the server (segmentation fault). Observed similar behaviour while trying to create Index on a table.
Reproducible: Always
### Steps to Reproduce:
1.Start server with "sudo mserver5 --dbfarm='/home/user/work/tmp/data/test' --single-user"
2.start mclient
3.create a simple table and fire a select query with group by on multiple columns
>create table test ( market_size int not null, market int not null, state int not null);
>select count(*) from test group by market_size, state;
### Actual Results:
server crashes (segmentation fault)
### Expected Results:
The select query should fetch the results without crashing the server
1. Same query works properly when "--single-user" option is not used while starting the server
2. Bug exists both in Linux and Windows (did not try on any other OS)
3. complete version information
MonetDB 5 server v11.3.3 "Apr2011-SP1" (64-bit, 64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2011 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 3.9GiB available memory, 2 available cpu cores
Libraries:
libpcre: 8.02 2010-03-19 (compiled with 8.02)
openssl: OpenSSL 0.9.8o 01 Jun 2010 (compiled with OpenSSL 0.9.8o 01 Jun 2010)
libxml2: 2.7.7 (compiled with 2.7.7)
Compiled by: root@ottar.ins.cwi.nl (x86_64-pc-linux-gnu)
Compilation: gcc -Wall -O6 -fomit-frame-pointer -finline-functions -falign-loops=4 -falign-jumps=4 -falign-functions=4 -fexpensive-optimizations -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -ftree-vectorize
Linking : /usr/bin/ld -m elf_x86_64 -Wl,-Bsymbolic-functions
## Comment 15844
Date: 2011-06-13 10:12:14 +0200
From: @drstmane
The problem appears to be a not (correcly) initialized store_funcs.sorted_col .
sql_trans_is_sorted() tries to call store_funcs.sorted_col(), but that is NULL
(see below).
I haven't found, yet, where / why store_funcs.sorted_col is not (correctly) initialized in --single-user mode (only) ...
========
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe7ba8700 (LWP 6422)]
0x0000000000000000 in ?? ()
Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.6-1.fc14.1.x86_64 cfitsio-3.250-5.fc14.x86_64 cyrus-sasl-lib-2.1.23-12.fc14.x86_64 geos-3.2.1-3.fc14.x86_64 glibc-2.12.90-21.x86_64 keyutils-libs-1.2-6.fc12.x86_64 krb5-libs-1.8.2-10.fc14.x86_64 libcom_err-1.41.12-6.fc14.x86_64 libcurl-7.21.0-6.fc14.x86_64 libgcc-4.5.1-4.fc14.x86_64 libidn-1.18-1.fc14.x86_64 libselinux-2.0.96-6.fc14.1.x86_64 libssh2-1.2.4-1.fc14.x86_64 libstdc++-4.5.1-4.fc14.x86_64 libxml2-2.7.7-3.fc14.x86_64 ncurses-libs-5.7-9.20100703.fc14.x86_64 nspr-4.8.8-1.fc14.x86_64 nss-3.12.10-1.fc14.x86_64 nss-softokn-freebl-3.12.10-1.fc14.x86_64 nss-util-3.12.10-1.fc14.x86_64 openldap-2.4.23-4.fc14.x86_64 openssl-1.0.0d-1.fc14.x86_64 pcre-8.10-1.fc14.x86_64 readline-6.1-2.fc14.x86_64 zlib-1.2.5-2.fc14.x86_64
(gdb) bt
0 0x0000000000000000 in ?? ()
1 0x00007fffe868615c in sql_trans_is_sorted (tr=0x7fffd8018208, col=0x7fffd806cb68) at /ufs/manegold/_/scratch0/Monet/HG/Apr2011/source/MonetDB/sql/storage/store.c:4153
2 0x00007fffe861545e in mvc_is_sorted (m=0x7fffd8005468, col=0x7fffd806cb68) at /ufs/manegold/_/scratch0/Monet/HG/Apr2011/source/MonetDB/sql/server/sql_mvc.c:1210
3 0x00007fffe8649cb2 in score_gbe (sql=0x7fffd8005468, rel=0x7fffd80f7cc8, e=0x7fffd80f7b88) at /ufs/manegold/_/scratch0/Monet/HG/Apr2011/source/MonetDB/sql/server/rel_optimizer.c:2619
4 0x00007fffe8649eec in rel_groupby_order (changes=0x7fffe7ba7acc, sql=0x7fffd8005468, rel=0x7fffd80f7cc8) at /ufs/manegold/_/scratch0/Monet/HG/Apr2011/source/MonetDB/sql/server/rel_optimizer.c:2647
5 0x00007fffe864d75c in rewrite (sql=0x7fffd8005468, rel=0x7fffd80f7cc8, rewriter=0x7fffe8649de5 <rel_groupby_order>, has_changes=0x7fffe7ba7bbc) at /ufs/manegold/_/scratch0/Monet/HG/Apr2011/source/MonetDB/sql/server/rel_optimizer.c:3880
6 0x00007fffe864d693 in rewrite (sql=0x7fffd8005468, rel=0x7fffd80f7d78, rewriter=0x7fffe8649de5 <rel_groupby_order>, has_changes=0x7fffe7ba7bbc) at /ufs/manegold/_/scratch0/Monet/HG/Apr2011/source/MonetDB/sql/server/rel_optimizer.c:3865
7 0x00007fffe864dd18 in _rel_optimizer (sql=0x7fffd8005468, rel=0x7fffd80f7d78, level=0) at /ufs/manegold/_/scratch0/Monet/HG/Apr2011/source/MonetDB/sql/server/rel_optimizer.c:4024
8 0x00007fffe864de93 in rel_optimizer (sql=0x7fffd8005468, rel=0x7fffd80f7d78) at /ufs/manegold/_/scratch0/Monet/HG/Apr2011/source/MonetDB/sql/server/rel_optimizer.c:4059
9 0x00007fffe85845d1 in sql_symbol2stmt (c=0x7fffd8005468, sym=0x7fffd80f77b8) at /ufs/manegold/_/scratch0/Monet/HG/Apr2011/source/MonetDB/sql/backends/monet5/sql.mx:1500
10 0x00007fffe85e5e8c in SQLparser (c=0x606098) at /ufs/manegold/_/scratch0/Monet/HG/Apr2011/source/MonetDB/sql/backends/monet5/sql_scenario.mx:1316
11 0x00007ffff6d35a45 in runPhase (c=0x606098, phase=1) at /ufs/manegold/_/scratch0/Monet/HG/Apr2011/source/MonetDB/monetdb5/mal/mal_scenario.mx:604
12 0x00007ffff6d35b7d in runScenarioBody (c=0x606098) at /ufs/manegold/_/scratch0/Monet/HG/Apr2011/source/MonetDB/monetdb5/mal/mal_scenario.mx:645
13 0x00007ffff6d35e04 in runScenario (c=0x606098) at /ufs/manegold/_/scratch0/Monet/HG/Apr2011/source/MonetDB/monetdb5/mal/mal_scenario.mx:682
14 0x00007ffff6d36e02 in MSserveClient (dummy=0x606098) at /ufs/manegold/_/scratch0/Monet/HG/Apr2011/source/MonetDB/monetdb5/mal/mal_session.mx:486
15 0x0000003d95606d5b in start_thread () from /lib64/libpthread.so.0
16 0x0000003d94ae4a7d in clone () from /lib64/libc.so.6
(gdb) up
1 0x00007fffe868615c in sql_trans_is_sorted (tr=0x7fffd8018208, col=0x7fffd806cb68) at /ufs/manegold/_/scratch0/Monet/HG/Apr2011/source/MonetDB/sql/storage/store.c:4153
4153 if (col && store_funcs.sorted_col(tr, col))
(gdb) li
4148 }
4149
4150 int
4151 sql_trans_is_sorted( sql_trans *tr, sql_column *col )
4152 {
4153 if (col && store_funcs.sorted_col(tr, col))
4154 return 1;
4155 return 0;
4156 }
4157
(gdb) p tr
$1 = (sql_trans *) 0x7fffd8018208
(gdb) p *tr
$2 = {name = 0x0, stime = 7, rtime = 0, wtime = 0, schema_number = 0, schema_updates = 0, status = 0, dropped = 0x0, schemas = {sa = 0x0, destroy = 0x7fffe86768cd <schema_destroy>, set = 0x7fffd8087808, dset = 0x0, nelm = 0x0}, parent = 0xef4ee8, stk = 0}
(gdb) p col
$3 = (sql_column *) 0x7fffd806cb68
(gdb) p *col
$4 = {base = {wtime = 0, rtime = 0, flag = 0, id = 5655, name = 0x7fffd806cbe8 "market_size"}, type = {type = 0xe661a8, digits = 32, scale = 0, comp_type = 0x0}, colnr = 0, null = 0 '\000', def = 0x0, unique = 0 '\000', drop_action = 0, storage_type = 0x0, sorted = 0, t = 0x7fffd806c6e8,
data = 0x7fffd806cc18}
(gdb) p store_funcs
$5 = {bind_col = 0x7fffe869449a <bind_col>, bind_idx = 0x7fffe869457f <bind_idx>, bind_del = 0x7fffe8694664 <bind_del>, append_col = 0x7fffe8695055 <append_col>, append_idx = 0x7fffe8695127 <append_idx>, update_col = 0x7fffe8694c4a <update_col>, update_idx = 0x7fffe8694d44 <update_idx>,
delete_tab = 0x7fffe8695384 <delete_tab>, count_col = 0x7fffe8695508 <count_col>, count_idx = 0x7fffe8695526 <count_idx>, sorted_col = 0, create_col = 0x7fffe86957b2 <create_col>, create_idx = 0x7fffe8695a48 <create_idx>, create_del = 0x7fffe8695cc2 <create_del>, dup_col = 0x7fffe8696089 <dup_col>,
dup_idx = 0x7fffe86960f4 <dup_idx>, dup_del = 0x7fffe869615f <dup_del>, destroy_col = 0x7fffe8696415 <destroy_col>, destroy_idx = 0x7fffe86964ab <destroy_idx>, destroy_del = 0x7fffe8696541 <destroy_del>, clear_col = 0x7fffe86966f6 <clear_col>, clear_idx = 0x7fffe8696736 <clear_idx>,
clear_del = 0x7fffe8696776 <clear_del>, log_create_col = 0x7fffe8695966 <log_create_col>, log_create_idx = 0x7fffe8695be0 <log_create_idx>, log_create_del = 0x7fffe8695e82 <log_create_del>, log_destroy_col = 0x7fffe869647f <log_destroy_col>, log_destroy_idx = 0x7fffe8696515 <log_destroy_idx>,
log_destroy_del = 0x7fffe86965b1 <log_destroy_del>, snapshot_create_col = 0x7fffe86959d7 <snapshot_create_col>, snapshot_create_idx = 0x7fffe8695c51 <snapshot_create_idx>, snapshot_create_del = 0x7fffe8695f38 <snapshot_create_del>, snapshot_destroy_col = 0, snapshot_destroy_idx = 0,
snapshot_destroy_del = 0, snapshot_table = 0x7fffe86972cf <snapshot_table>, log_table = 0x7fffe8696ded <log_table>, update_table = 0x7fffe8696845 <update_table>, gtrans_update = 0, gtrans_minmax = 0, col_ins = 0, col_upd = 0, idx_ins = 0, idx_upd = 0, del = 0}
(gdb) p store_funcs.sorted_col
$6 = (sorted_col_fptr) 0 <===== !!!
^
!
(gdb)
=========
## Comment 15858
Date: 2011-06-29 14:57:50 +0200
From: @sjoerdmullender
(In reply to comment 1)
> The problem appears to be a not (correcly) initialized store_funcs.sorted_col .
>
> sql_trans_is_sorted() tries to call store_funcs.sorted_col(), but that is NULL
> (see below).
>
> I haven't found, yet, where / why store_funcs.sorted_col is not (correctly)
> initialized in --single-user mode (only) ...
store_funcs is initialized in store_init (sql/storage/store.c) which calls different functions to do the real initialization depending on flags such as --single-user. In the case of --single-user, su_storage_init() is called which indeed fails to initialize the sorted_col field. The other initialization functions do initialize the field.
Since this is a SQL problem I changed the product.
## Comment 15876
Date: 2011-07-02 10:42:24 +0200
From: @njnes
initialisation is now fixed.
## Comment 15998
Date: 2011-07-29 10:52:39 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| segmentation fault when a select query (with group by) is run on server with "--single-user" option | https://api.github.com/repos/MonetDB/MonetDB/issues/2821/comments | 0 | 2020-11-30T11:42:58Z | 2024-06-27T11:52:06Z | https://github.com/MonetDB/MonetDB/issues/2821 | 753,406,551 | 2,821 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-06-12 01:21:51 +0200
From: Philippe <<philippe.hanrigou>>
To: GDK devs <<bugs-common>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
CC: gburd, philippe.hanrigou
Last updated: 2011-07-29 10:52:39 +0200
## Comment 15841
Date: 2011-06-12 01:21:51 +0200
From: Philippe <<philippe.hanrigou>>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_7; en-us) AppleWebKit/533.21.1 (KHTML, like Gecko) Version/5.0.5 Safari/533.21.1
Build Identifier:
On a fully loaded database (4.6G on a machine with 8G of RAM), I run a "data refresh script" consisting in a series of DELETE/COPY INTO statements. The server then crash because of a SIGSEGV and leaves the database in a crashed state that cannot be recovered.
The SIGSEGV is deterministic and always triggered by the same DELETE statement:
delete from \"20789445e300fa1e535f3027d5d63dc9_sessions\" where session_start between 1280361600000 and 1280447999999;
triggered on line 498 of gdk_setop.mx:
HASHloop@4(ri, r->H->hash, s2, h) {
The problem seems to be with `r->H->hash` whose value is 0x0
I have no idea of where r->H->hash should have been set, or how to
push the investigation further. Any help would be greatly appreciated.
I have included below a capture of my gdb session which will provide
more information.
--------------------- gdb session --------------------
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fd9acbb7700 (LWP 3270)]
0x00007fd9b974c8e8 in BATins_kdiff (bn=0x24daa0c8, l=0x1dd47858, r=0x37498ea0) at gdk_setop.mx:498
498 HASHloop@4(ri, r->H->hash, s2, h) {
(gdb)
(gdb) bt
0 0x00007fd9b974c8e8 in BATins_kdiff (bn=0x24daa0c8, l=0x1dd47858, r=0x37498ea0) at gdk_setop.mx:498
1 0x00007fd9b9760865 in BATkdiff (l=0x1dd47858, r=0x37498ea0) at gdk_setop.mx:827
2 0x00007fd9ba8be632 in CMDkdiff (result=0x7fd9acbb6838, left=0x1dd47858, right=0x37498ea0) at algebra.mx:1586
3 0x00007fd9ba8cebce in ALGkdiff (result=0x24ad2ec8, lid=0x24ad2e98, rid=0x24ad2c28) at algebra.mx:3018
4 0x00007fd9ba1aa5da in DFLOWstep (t=0x21bd2c8, fs=0x7fd9acfb7de0) at mal_interpreter.mx:2058
5 0x00007fd9ba1afee3 in runDFLOWworker (t=0x21bd2c8) at mal_interpreter.mx:1174
6 0x00007fd9b6e0c971 in start_thread () from /lib/libpthread.so.0
7 0x00007fd9b6b6892d in clone () from /lib/libc.so.6
8 0x0000000000000000 in ?? ()
(gdb) info threads
6 Thread 0x7fd9acfb9700 (LWP 4846) 0x00007fd9b6e12da0 in sem_wait () from /lib/libpthread.so.0
5 Thread 0x7fd9ad3bb700 (LWP 3266) 0x00007fd9b6b612c3 in select () from /lib/libc.so.6
4 Thread 0x7fd9ad1ba700 (LWP 3267) 0x00007fd9b6b612c3 in select () from /lib/libc.so.6
3 Thread 0x7fd9acdb8700 (LWP 3269) 0x00007fff89fff818 in gettimeofday ()
* 2 Thread 0x7fd9acbb7700 (LWP 3270) 0x00007fd9b974c8e8 in BATins_kdiff (bn=0x24daa0c8, l=0x1dd47858, r=0x37498ea0) at gdk_setop.mx:498
1 Thread 0x7fd9bb3b1720 (LWP 3263) 0x00007fd9b6b612c3 in select () from /lib/libc.so.6
(gdb) thread 6
[Switching to thread 6 (Thread 0x7fd9acfb9700 (LWP 4846))]0 0x00007fd9b6e12da0 in sem_wait () from /lib/libpthread.so.0
(gdb) bt
0 0x00007fd9b6e12da0 in sem_wait () from /lib/libpthread.so.0
1 0x00007fd9ba1a5b3f in q_dequeue (q=0x1eaca38) at mal_interpreter.mx:960
2 0x00007fd9ba1b0a6c in DFLOWscheduler (flow=0x25e1c38) at mal_interpreter.mx:1385
3 0x00007fd9ba1b1c07 in runMALdataflow (cntxt=0x606898, mb=0x275f9a48, startpc=2, stoppc=59, stk=0x24ad2af8, env=0x0, pcicaller=0x409cad8) at mal_interpreter.mx:1583
4 0x00007fd9bacb47e0 in MALstartDataflow (cntxt=0x606898, mb=0x275f9a48, stk=0x24ad2af8, pci=0x409cad8) at language.mx:268
5 0x00007fd9ba192333 in runMALsequence (cntxt=0x606898, mb=0x275f9a48, startpc=1, stoppc=0, stk=0x24ad2af8, env=0x0, pcicaller=0x0) at mal_interpreter.mx:2168
6 0x00007fd9ba1866ec in callMAL (cntxt=0x606898, mb=0x275f9a48, env=0x7fd9acfb8c80, argv=0x7fd9acfb8c40, debug=0 '\000') at mal_interpreter.mx:429
7 0x00007fd9ad435c9f in SQLexecutePrepared (c=0x606898, be=0x278fefc8, q=0x18c31ce8) at sql_scenario.mx:1490
8 0x00007fd9ad435f12 in SQLengineIntern (c=0x606898, be=0x278fefc8) at sql_scenario.mx:1543
9 0x00007fd9ad436441 in SQLengine (c=0x606898) at sql_scenario.mx:1652
10 0x00007fd9ba1d9114 in runPhase (c=0x606898, phase=4) at mal_scenario.mx:604
11 0x00007fd9ba1d92eb in runScenarioBody (c=0x606898) at mal_scenario.mx:655
12 0x00007fd9ba1d94d3 in runScenario (c=0x606898) at mal_scenario.mx:682
13 0x00007fd9ba1da40d in MSserveClient (dummy=0x606898) at mal_session.mx:486
14 0x00007fd9b6e0c971 in start_thread () from /lib/libpthread.so.0
15 0x00007fd9b6b6892d in clone () from /lib/libc.so.6
16 0x0000000000000000 in ?? ()
(gdb) frame 7
7 0x00007fd9ad435c9f in SQLexecutePrepared (c=0x606898, be=0x278fefc8, q=0x18c31ce8) at sql_scenario.mx:1490
1490 ret= callMAL(c, mb, &glb, argv, (m->emod & mod_debug?'n':0));
(gdb) print *q
$1 = {next = 0x4ec3398, type = 2, sa = 0x1b6bf468, s = 0x2426b268, params = 0x2427a878, paramlen = 2, stk = 615328504, code = 0x1b77a958, id = 58, key = 5856,
codestring = 0x20083678 "delete from \"20789445e300fa1e535f3027d5d63dc9_sessions\" where session_start between 1280361600000 and 1280447999999;", name = 0x39bc698 "s58_1", count = 18}
(gdb)
(gdb) thread 2
[Switching to thread 2 (Thread 0x7fd9acbb7700 (LWP 3270))]0 0x00007fd9b974c8e8 in BATins_kdiff (bn=0x24daa0c8, l=0x1dd47858, r=0x37498ea0) at gdk_setop.mx:498
498 HASHloop@4(ri, r->H->hash, s2, h) {
(gdb) l
493 BATloop(l, p1, q1) {
494 h = BUNh@2(li, p1);
495 t = BUNtail(li, p1);
496 ins = TRUE;
497 if (@6) /* check for not-nil (nils don't match anyway) */
498 HASHloop@4(ri, r->H->hash, s2, h) {
499 if (EQUAL@5(t, BUNtail(ri, s2))) {
500 HIT@1(h, t);
501 ins = FALSE;
502 break;
(gdb) p ri
$14 = {b = 0x37498ea0, hvid = 0, tvid = 0}
(gdb) p s2
$15 = 9223372036854775807
(gdb) p h
$16 = (ptr) 0x7fd9acbb3f88
(gdb) p r->H->hash
$17 = (Hash *) 0x0
(gdb) p *r->H
$18 = {id = 0x7fd9b9c48f7f "t", width = 8, type = 7 '\a', shift = 3 '\003', sorted = 0 '\000', varsized = 0, key = 0, dense = 0, nonil = 1, nil = 0, unused = 0, align = 0,
nosorted_rev = 0, nokey = {0, 0}, nosorted = 0, nodense = 182, seq = 0, heap = {maxsize = 157280, free = 137000, size = 157280, base = 0x15c6b2b8 "",
filename = 0x374990d8 "12/40/124015.tail", storage = 0 '\000', copied = 0, hashash = 0, forcemap = 0, newstorage = 0 '\000', dirty = 0 '\000', parentid = 0}, vheap = 0x0, hash = 0x0,
props = 0x0}
(gdb) p *r
$19 = {batCacheid = -43021, H = 0x37498f58, T = 0x37498ec8, P = 0x37498fe8, U = 0x37499000}
Structure of the table:
sql>\d "20789445e300fa1e535f3027d5d63dc9_sessions"
CREATE TABLE "reporting"."20789445e300fa1e535f3027d5d63dc9_sessions" (
"session_start" BIGINT,
"session_id" CHAR(51),
"the_day" CHAR(10),
"cart" BOOLEAN,
"purchased" BOOLEAN,
"merchant_total_dollars" INTEGER,
"co_total_dollars" INTEGER,
"baseline_dollars" INTEGER,
"billing_baseline_dollars" INTEGER,
"promo_determination" VARCHAR(20),
"session_enabled" BOOLEAN,
"co_enabled" BOOLEAN,
"co_managed" BOOLEAN,
"promo" VARCHAR(100),
"sushi" VARCHAR(100),
"url_referrer" VARCHAR(1024)
);
The "refresh script" consist in something like:
-- for each day:
-- for each merchant
DELETE FROM "<merchant_id>_sessions" WHERE session_start BETWEEN <start of day timestamp> AND <end of day timestamp>;
COPY INTO "<merchant_id>_sessions" FROM STDIN USING DELIMITERS '\\t','\\n';
... (up to 8000 session rows for this merchant and day)
This is my poor man's way of simulating upserts.
Reproducible: Always
### Steps to Reproduce:
1. Load the database with data
2. Run the "refresh script" consisting in a series on DELETE/COPY INTO statements. Alternatively, I can also crash the server by only running the DELETE statements on a loaded database.
3. SIGSEGV
I could provide a dump of the database and a copy of the refresh script which I run with mclient. These are fairly big files though (about 4G each) and contain confidential data. So I would rather not post them in a public forum.
### Actual Results:
Server crash (SIGSEGV) then database in a crashed state that cannot be recovered (crashes every time you start it).
### Expected Results:
Absence of server crash and healthy database
The crash is deterministic on Linux and always happen on the same spot. However:
- The crash does not happen if I run the same "refresh script" against an empty database. It only crashes when I run it against a loaded database.
- When I try to reproduce the bug on OS X, the server experiences a problem on the exact same spot, but there is no SIGSEGV, the server just seem to be "stuck" with a high CPU usage (system, not user strangely).
## Comment 15842
Date: 2011-06-12 01:24:35 +0200
From: Philippe <<philippe.hanrigou>>
This is happening on a production database and delaying our complete adoption of MonetDB for our analytics platform. So any patch or workaround would be greatly appreciated.
## Comment 15862
Date: 2011-06-30 12:37:08 +0200
From: @sjoerdmullender
(In reply to comment 0)
> I could provide a dump of the database and a copy of the refresh script which I
> run with mclient. These are fairly big files though (about 4G each) and contain
> confidential data. So I would rather not post them in a public forum.
Can you make the data available to me? You can contact me directly at sjoerd@acm.org.
## Comment 15867
Date: 2011-07-01 10:00:16 +0200
From: @sjoerdmullender
With Philippe's data I can reproduce the problem.
## Comment 15868
Date: 2011-07-01 14:53:18 +0200
From: @sjoerdmullender
Changeset [ffabd521cfbf](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ffabd521cfbf) 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=ffabd521cfbf](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ffabd521cfbf)
Changeset description:
Declare sql.delete as an "unsafe" function.
This fixes bug #2820.
The problem was that sql.delete was executed in parallel with a call
to algebra.kdifference on the same table. While the kdiff was
executing, delete deleted the hash table that kdiff was using, causing
the latter to crash.
## Comment 15869
Date: 2011-07-01 14:55:40 +0200
From: @sjoerdmullender
It looks like the bug has been nailed.
Philippe, can you test this and reopen if it still fails?
## Comment 15875
Date: 2011-07-02 00:48:04 +0200
From: Philippe <<philippe.hanrigou>>
Sjoerd, thanks for the fix. Did you manage to successfully run my entire population script after applying your patch though?
After applying the fix the crash does not happen so quickly but I can still consistently crash the database using the procedure previously described.
Am I missing something?
## Comment 15882
Date: 2011-07-04 12:42:07 +0200
From: @sjoerdmullender
(In reply to comment 6)
> Sjoerd, thanks for the fix. Did you manage to successfully run my entire
> population script after applying your patch though?
I hadn't since it took so long. This morning I tried, but the 164GB I had available on the database partition wasn't enough to complete the script. The population-script ran for almost 2 1/2 hours before the server quit due to lack of available disk space.
> After applying the fix the crash does not happen so quickly but I can still
> consistently crash the database using the procedure previously described.
>
> Am I missing something?
How much disk space do yo have available, and how long does it take before you get a crash?
## Comment 15899
Date: 2011-07-06 10:09:36 +0200
From: @sjoerdmullender
Changeset [9139c6f09ed2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=9139c6f09ed2) 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=9139c6f09ed2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9139c6f09ed2)
Changeset description:
Check result of operation.
Yet another problem related to bug #2820.
## Comment 15928
Date: 2011-07-09 10:40:57 +0200
From: @sjoerdmullender
Changeset [9894d99d7604](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=9894d99d7604) 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=9894d99d7604](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9894d99d7604)
Changeset description:
If the logger fails, it's a fatal error.
This should fix a crash related to bug #2820.
## Comment 15929
Date: 2011-07-09 10:40:58 +0200
From: @sjoerdmullender
Changeset [e6864601d4ab](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e6864601d4ab) 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=e6864601d4ab](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e6864601d4ab)
Changeset description:
Fix for appending string heaps.
When appending string heaps, append after the "free" instead of the
"size" of the heap. The "size" may be much larger than the actual
used area of the heap (which is indicated with "free"), so appending
after it may result in large holes in the string heap.
This fix should finally resolve bug #2820 since we now no longer need
more than 1.5 TB of disk space to run the update queries.
## Comment 15930
Date: 2011-07-09 10:45:59 +0200
From: @sjoerdmullender
I have now been able to run the complete test set. My last fix reduced the required amount of available disk space for running the test from over 1.5 TB (i.e., that was not enough to run the test) to less than 10 GB. This means that I didn't run out of disk space anymore. Running out of disk space was the major cause of crashes after the first fix.
## Comment 15997
Date: 2011-07-29 10:52:39 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| SIGSEGV in BATins_kdiff triggered by a DELETE statement | https://api.github.com/repos/MonetDB/MonetDB/issues/2820/comments | 0 | 2020-11-30T11:42:55Z | 2024-06-27T11:52:05Z | https://github.com/MonetDB/MonetDB/issues/2820 | 753,406,517 | 2,820 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-06-10 20:28:23 +0200
From: @grobian
To: Documentation maintainers <<bugs-docs>>
Version: unspecified
CC: @mlkersten, @drstmane
Last updated: 2011-07-29 10:52:44 +0200
## Comment 15838
Date: 2011-06-10 20:28:23 +0200
From: @grobian
http://www.monetdb.org/Documentation/Cookbooks/ServerMgmt/ResourceLimits
The text on this page is vague. In particular the 32-bits major cause is not understandable to me, so I doubt for the average (windows) user.
## Comment 15839
Date: 2011-06-10 21:04:04 +0200
From: @drstmane
A potential source for a full explanation of MonetDB resource (as in memory / address space) limitation can be found here:
http://sourceforge.net/mailarchive/message.php?msg_id=24807067
## Comment 15840
Date: 2011-06-10 22:29:13 +0200
From: @mlkersten
That page can (is) deleted, because there was already another page
http://www.monetdb.org/Documentation/UserGuide/resources
## Comment 16007
Date: 2011-07-29 10:52:44 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| make text readable | https://api.github.com/repos/MonetDB/MonetDB/issues/2819/comments | 0 | 2020-11-30T11:42:52Z | 2024-06-27T11:52:04Z | https://github.com/MonetDB/MonetDB/issues/2819 | 753,406,492 | 2,819 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-06-05 22:35:41 +0200
From: Martin Weindel <<mw-monetdb>>
To: clients devs <<bugs-clients>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
Last updated: 2011-07-29 10:52:45 +0200
## Comment 15833
Date: 2011-06-05 22:35:41 +0200
From: Martin Weindel <<mw-monetdb>>
User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.71 Safari/534.24
Build Identifier:
If you call MonetConnection.setReadOnly(boolean) and autocommit is turned off, a SQLException is thrown.
As this call of setReadOnly is done be a framework I'm using, I cannot avoid it easily.
Reproducible: Always
### Steps to Reproduce:
1. getConnection()
2. call MonetConnection.setAutoCommit(false)
3. call MonetConnection.setReadOnly(false)
The understanding of setReadOnly/isReadOnly in MonetConnection seems to be a little odd to me, if I read its JavaDoc: "MonetDB doesn't support writable ResultSets, hence an SQLWarning is generated if attempted to set to false here."
But setReadOnly has nothing to do with resultsets directly.
The JDBC specification does not specify this method explicitly, but the JavaDoc of java.lang.Connection says "Puts this connection in read-only mode as a hint to the driver to enable database optimizations.", and more importantly: "Throws:
SQLException - SQLException if a database access error occurs or this method is called on a closed connection"
This means:
1. Calling setReadOnly is only a hint and should not throw an exception on normal circumstances
2. MonetConnection should behave like may others JDBC drivers and just ignore the call of setReadOnly (you can check if the connection is closed if you want to be perfect specification conform)
3. isReadOnly should return false and not true as in MonetConnection, as the connection to the MonetDB can still execute write statements.
## Comment 15834
Date: 2011-06-06 10:57:40 +0200
From: @grobian
Thank you for your concise report.
You get an exception, because of this phrase in the Javadoc:
Note: This method cannot be called during a transaction.
I understand that the framework you use does not expect this, so I'm lenient towards changing this behaviour, essentially ignoring the note.
## Comment 15835
Date: 2011-06-06 11:20:41 +0200
From: @grobian
Changeset [318b2593135b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=318b2593135b) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=318b2593135b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=318b2593135b)
Changeset description:
JDBC: don't throw an exception from setReadOnly
Bug #2818, don't throw an exception from Connection.setReadOnly when
autocommit is disabled. Since setReadOnly is not implemented at all
anyway, don't make it throw exceptions that may upset frameworks that
call these methods just to be sure.
## Comment 15836
Date: 2011-06-06 11:20:42 +0200
From: @grobian
Changeset [ccf366781fc3](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ccf366781fc3) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ccf366781fc3](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ccf366781fc3)
Changeset description:
JDBC: properly advertise Connection read-only mode
JDBC's Connection read-only mode appears to be just a hint to the driver
to enable certain optimisations, if possible. It has nothing to do with
being able to write to the database (or make modifications). Hence, a
Connection with MonetDB is never read-only, and setReadOnly should only
emit a warning when called with true.
Thanks to Martin Weindel for pointing this out in bug #2818.
## Comment 15837
Date: 2011-06-06 11:21:43 +0200
From: @grobian
The next release should include the fixes you need. Thanks.
## Comment 16009
Date: 2011-07-29 10:52:45 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| JDBC: exception on calling Connection.setReadOnly | https://api.github.com/repos/MonetDB/MonetDB/issues/2818/comments | 0 | 2020-11-30T11:42:49Z | 2024-06-27T11:52:03Z | https://github.com/MonetDB/MonetDB/issues/2818 | 753,406,469 | 2,818 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-06-04 23:03:01 +0200
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: 11.3.7 (Apr2011-SP2) [obsolete]
CC: @njnes, @drstmane
Last updated: 2011-09-16 15:04:40 +0200
## Comment 15832
Date: 2011-06-04 23:03:01 +0200
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Build Identifier:
Operator resolution issue. User defined function in specific schema not found.
Reproducible: Always
### Steps to Reproduce:
create schema datacell;
create table datacell.basket_X(
id integer auto_increment,
tag timestamp default now(),
payload integer
);
create function datacell.basket_X()
returns table (id integer, tag timestamp, payload integer)
begin
return select * from datacell.basket_X;
end;
select * from datacell.basket_X();
### Actual Results:
!SELECT: no such operator 'basket_x'
## Comment 15846
Date: 2011-06-13 22:33:46 +0200
From: @mlkersten
Problem is fixed in the default.
## Comment 15958
Date: 2011-07-17 15:44:27 +0200
From: @drstmane
Changeset [bed1350dc1be](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=bed1350dc1be) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bed1350dc1be](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bed1350dc1be)
Changeset description:
added test for bug #2817
## Comment 15959
Date: 2011-07-17 16:06:06 +0200
From: @drstmane
Re-opened as
(1)
it still fails as originally reported in Apr2011 branch
(admittedly, it has never been fixed there)
(2)
it causes a server crash (segfault) in Aug2011 branch
## Comment 15960
Date: 2011-07-17 16:14:39 +0200
From: @drstmane
crash also occurs in default branch
## Comment 15987
Date: 2011-07-27 17:29:54 +0200
From: @njnes
Changeset [bec5a1fb7ba9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=bec5a1fb7ba9) 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=bec5a1fb7ba9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bec5a1fb7ba9)
Changeset description:
fixes for bug #2817, keep 'generated types' in schema sys.
Put function in passed schema (not in the current schema).
## Comment 15989
Date: 2011-07-27 20:02:13 +0200
From: @njnes
test is now running also on the april branch
## Comment 16049
Date: 2011-07-29 11:03:54 +0200
From: @sjoerdmullender
Apr2011-SP2 has been released.
## Comment 16253
Date: 2011-09-16 15:04:40 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| Failed to find a table producing function | https://api.github.com/repos/MonetDB/MonetDB/issues/2817/comments | 0 | 2020-11-30T11:42:45Z | 2024-06-27T11:52:02Z | https://github.com/MonetDB/MonetDB/issues/2817 | 753,406,422 | 2,817 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-06-01 12:55:58 +0200
From: Alfred Nordman <<alfred.nordman>>
To: SQL devs <<bugs-sql>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
CC: @njnes
Last updated: 2011-07-02 10:45:24 +0200
## Comment 15831
Date: 2011-06-01 12:55:58 +0200
From: Alfred Nordman <<alfred.nordman>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Build Identifier:
When a query has a 2-level nesting with a UNION ALL inside, an alias and an outer GROUP BY operations, no result is being returned.
Removing the GROUP BY or the UNION ALL or the first table alias makes the query return the correct result.
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE t (c INT);
INSERT INTO t VALUES (1);
SELECT outtab.c
FROM (SELECT intab.c
FROM (SELECT t.c
FROM t) intab
UNION ALL
SELECT t.c
FROM t) outtab
GROUP BY outtab.c;
### Actual Results:
sql>
### Expected Results:
+------+
| c |
+======+
| 1 |
+------+
1 tuple (2.575ms)
sql>
MonetDB 5 server v11.3.3 "Apr2011-SP1" (64-bit, 32-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2011 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 8.0GiB available memory
Libraries:
libpcre: 8.10 2010-06-25
openssl: OpenSSL 1.0.0a 1 Jun 2010
libxml2: 2.7.7
Compiled by: sjoerd@LAB03 (x86_64-pc-winnt)
Compilation: cl -GF -W3 -wd4273 -wd4102 -MD -nologo -Ox
Linking : cl -GF -W3 -wd4273 -wd4102 -MD -nologo -Ox
## Comment 15877
Date: 2011-07-02 10:45:24 +0200
From: @njnes
cannot reproduce this bug. May have been changed by other recent changes.
## Comment 15955
Date: 2011-07-17 15:19:14 +0200
From: @drstmane
Changeset [83139e46ae17](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=83139e46ae17) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=83139e46ae17](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=83139e46ae17)
Changeset description:
added test for bug #2816
| No results are returned for a nested SELECT with UNION ALL and outer GROUP query | https://api.github.com/repos/MonetDB/MonetDB/issues/2816/comments | 0 | 2020-11-30T11:42:42Z | 2024-06-28T07:23:12Z | https://github.com/MonetDB/MonetDB/issues/2816 | 753,406,384 | 2,816 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-05-23 11:30:19 +0200
From: George Garbis <<ggarbis>>
To: SQL devs <<bugs-sql>>
Version: -- development
CC: charnik, @yzchang
Last updated: 2016-06-23 10:24:08 +0200
## Comment 15829
Date: 2011-05-23 11:30:19 +0200
From: George Garbis <<ggarbis>>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Build Identifier:
I create a table with geometries and insert 2 points with different SRID.
When i ask for these SRID i get the same (0) for every point.
Also, if i ask whether these points overlap i don't get the right result.
I get 'true' while the points are totally different, considering their reference systems.
Reproducible: Always
### Steps to Reproduce:
1. sql>create table geom(id int, g geometry);
2. sql>insert into geom values(1, GeomFromText('POINT(100 100)', 4326));
3. sql>insert into geom values(2, GeomFromText('POINT(100 100)', 27700));
4. sql>select id, srid(g) from geom;
5. sql>select equals(g1.g, g2.g) from geom g1, geom g2 where g1.id=1 and g2.id=2;
### Actual Results:
Results of steps 4 and 5 are:
4.
+------+--------+
| id | srid_g |
+======+========+
| 2 | 0 |
| 1 | 0 |
+------+--------+
5.
+-----------------+
| overlaps_g |
+============+
| true |
+------------+
### Expected Results:
Results of steps 4 and 5 are supposed to be:
4.
4.
+------+--------+
| id | srid_g |
+======+========+
| 2 | 27700 |
| 1 | 4326 |
+------+--------+
5.
+-----------------+
| overlaps_g |
+============+
| false |
+------------+
I have noticed that function wkbFromText (in file geom/monetdb5/geom.mx), which is used in SQL functions GeomFromText, PointFromText e.t.c., returns a wkb datatype (defined in geom/lib/libgeom.mx) which has not any field for srid.
Is srid stored somewhere else (e.g. as metadata of a geometry collumn)?
## Comment 15866
Date: 2011-07-01 09:56:41 +0200
From: @sjoerdmullender
It seems there is no support for storing the SRID into the database. For some reason the GET function was implemented, but since no value is stored, it always returns 0.
## Comment 16041
Date: 2011-07-29 11:00:06 +0200
From: @sjoerdmullender
Apr2011-SP2 has been released.
## Comment 16280
Date: 2011-09-16 15:10:40 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 17684
Date: 2012-08-24 14:56:00 +0200
From: @sjoerdmullender
Jul2012-SP1 has been released.
## Comment 18121
Date: 2012-11-27 15:30:20 +0100
From: @yzchang
No test for feature request
## Comment 22028
Date: 2016-04-11 12:24:34 +0200
From: @sjoerdmullender
The upcoming Jun2016 release (whether or not it'll arrive in June 2016) will have support for SRID.
| No SRID support | https://api.github.com/repos/MonetDB/MonetDB/issues/2815/comments | 0 | 2020-11-30T11:42:39Z | 2024-06-27T11:52:00Z | https://github.com/MonetDB/MonetDB/issues/2815 | 753,406,345 | 2,815 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-05-19 15:28:28 +0200
From: George Garbis <<ggarbis>>
To: SQL devs <<bugs-sql>>
Version: 11.3.7 (Apr2011-SP2) [obsolete]
CC: charnik
Last updated: 2011-09-16 15:04:35 +0200
## Comment 15823
Date: 2011-05-19 15:28:28 +0200
From: George Garbis <<ggarbis>>
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.24 (KHTML, like Gecko) Ubuntu/10.10 Chromium/11.0.696.65 Chrome/11.0.696.65 Safari/534.24
Build Identifier:
If i run a SQL/GIS function (e.g. mbr) and this function take null as argument the SQL front end throws exception instead of returning a null value.
Thus, user doesn't get any results only because of one null value in geometry column.
An execution scenario demonstrating this problem is:
sql>create table geom(id int, g Geometry);
sql>insert into geom values(1, GeomFromText('POINT(4 5)', 0));
sql>insert into geom values(2, GeomFromText('POLYGON((0 0, 10 0, 0 10, 0 0))', 0));
sql>insert into geom values(3, null);
sql>select id, mbr(g) from geom where id=1 or id=2;
+------+-----------------------------------------------+
| id | mbr_g |
+======+===============================================+
| 1 | BOX (4.000000 5.000000, 4.000000 5.000000) |
| 2 | BOX (0.000000 0.000000, 10.000000 10.000000) |
+------+-----------------------------------------------+
2 tuples
sql>select id, mbr(g) from geom where;
MALException:geom.mbr:Failed to create mbr
Reproducible: Always
The same happens with almost every GIS function.
I think that it is more useful if a null value is returned and a ternary logic(true, false, unknown) is used in boolean functions (as defined by 'OpenGIS® Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option')
## Comment 15826
Date: 2011-05-20 11:02:55 +0200
From: @grobian
this requires some patching of the geom module to recognise null values and return unknown early in the process
## Comment 15893
Date: 2011-07-05 14:34:15 +0200
From: @sjoerdmullender
Changeset [ca87abd89c7d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ca87abd89c7d) 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=ca87abd89c7d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ca87abd89c7d)
Changeset description:
Added test for bug #2814.
## Comment 15894
Date: 2011-07-05 14:34:16 +0200
From: @sjoerdmullender
Changeset [802e11e14bd5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=802e11e14bd5) 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=802e11e14bd5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=802e11e14bd5)
Changeset description:
Added nil test to geom.mbr() call.
This fixes bug #2814.
## Comment 15895
Date: 2011-07-05 14:34:53 +0200
From: @sjoerdmullender
A null test has been added.
## Comment 15901
Date: 2011-07-06 11:03:16 +0200
From: George Garbis <<ggarbis>>
Created attachment 63
Sql script that checks every function if given null argument
Thanks for the fix, but this problem appears in almost every GIS function.
I uploaded a script that demonstrates the problem in every function.
> Attached file: [FunctionsThatThrowNullException.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2814_FunctionsThatThrowNullException.sql_63) (text/plain, 4558 bytes)
> Description: Sql script that checks every function if given null argument
## Comment 15931
Date: 2011-07-11 15:09:31 +0200
From: @sjoerdmullender
Changeset [40197cae30c1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=40197cae30c1) 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=40197cae30c1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=40197cae30c1)
Changeset description:
Added test from the attachment to bug #2814.
## Comment 15932
Date: 2011-07-11 15:09:33 +0200
From: @sjoerdmullender
Changeset [0f3d56f8d7da](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0f3d56f8d7da) 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=0f3d56f8d7da](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0f3d56f8d7da)
Changeset description:
Test for nil and null.
This makes that the attachment from bug #2814 runs without crashing the
server.
## Comment 15933
Date: 2011-07-11 17:11:20 +0200
From: @sjoerdmullender
I am closing this again since I added NULL and NIL checks to the code and the test you attached (thanks!) runs without crashing. Feel free to reopen if there is still a problem.
I don't really like the fact that you get errors for certain operations involving nil, but that cannot be changed in the Apr2011 branch (interface change). It could possibly be changed for a feature release. This would be a different bug/enhancement, though.
## Comment 15986
Date: 2011-07-26 14:26:20 +0200
From: George Garbis <<ggarbis>>
Sorry for opening this again but I am a bit confused.
I compiled the code of changeset [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0f3d56f8d7da](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0f3d56f8d7da) and while running the test script I, still, get the same exceptions.
Am I doing something wrong?
Saying 'runs without crashing' do you mean that you got rid of the exceptions?
## Comment 16036
Date: 2011-07-29 11:00:04 +0200
From: @sjoerdmullender
Apr2011-SP2 has been released.
## Comment 16050
Date: 2011-07-29 12:55:25 +0200
From: @sjoerdmullender
Changeset [62013099714d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=62013099714d) 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=62013099714d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=62013099714d)
Changeset description:
Implemented NULL checks in the geom module.
Now when given NULL as input, the module functions return NULL instead
of an exception.
This fixes bug #2814.
## Comment 16051
Date: 2011-07-29 12:58:46 +0200
From: @sjoerdmullender
The test now runs without generating exceptions.
Note that the fix is in the Aug2011 branch.
## Comment 16241
Date: 2011-09-16 15:04:35 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
| Throws exception if a SQL/GIS takes argument null | https://api.github.com/repos/MonetDB/MonetDB/issues/2814/comments | 0 | 2020-11-30T11:42:36Z | 2024-06-27T11:51:59Z | https://github.com/MonetDB/MonetDB/issues/2814 | 753,406,306 | 2,814 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-05-17 23:08:07 +0200
From: @yzchang
To: SQL devs <<bugs-sql>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
CC: @njnes
Last updated: 2011-07-29 10:52:38 +0200
## Comment 15817
Date: 2011-05-17 23:08:07 +0200
From: @yzchang
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.17) Gecko/20110420 Firefox/3.6.17
Build Identifier:
Building the SQL catalog will succeed even if an SQL script in lib/monetdb5/createdb contains (syntax) error. No error/warning message is given. The catalog just doesn't contain the tables, functions, etc created by the SQL scripts in lib/monetdb5/createdb This happens both in the Mar2011 and default branches. Shouldn't mserver5 refuse building the catalog if an error occurs and exit?
Reproducible: Always
## Comment 15820
Date: 2011-05-18 15:11:41 +0200
From: @njnes
Changeset [32900f6cf506](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=32900f6cf506) 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=32900f6cf506](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=32900f6cf506)
Changeset description:
redirect error from create scripts back to the first client
fixed bug #2813
## Comment 15821
Date: 2011-05-18 15:12:40 +0200
From: @njnes
Changeset [9cbe3f5bba0e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=9cbe3f5bba0e) 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=9cbe3f5bba0e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9cbe3f5bba0e)
Changeset description:
merge fix for bug #2813
## Comment 15996
Date: 2011-07-29 10:52:38 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| SQL: catalog is built even error has occurred | https://api.github.com/repos/MonetDB/MonetDB/issues/2813/comments | 0 | 2020-11-30T11:42:34Z | 2024-06-27T11:51:58Z | https://github.com/MonetDB/MonetDB/issues/2813 | 753,406,278 | 2,813 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-05-17 03:03:15 +0200
From: me.anonimous
To: SQL devs <<bugs-sql>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
CC: @njnes
Last updated: 2011-07-29 10:52:40 +0200
## Comment 15814
Date: 2011-05-17 03:03:15 +0200
From: me.anonimous
User-Agent: Opera/9.80 (Windows NT 6.1; U; en) Presto/2.8.131 Version/11.10
Build Identifier:
While sub-query run well in the WHERE clause, they don't seem to run in the FROM clause.
I can't change how the client software ships the query [through JDBC], so suggesting re-writting it is not an option for me.
In addition, the latter form has the advantage of being able to "join" on multiple conditions in an efficient manner.
BTW, I'm running tests against other dBs (Lucid, MySSQL, MSSQL), none of them has problems with the latter query.
I'm using the data from this article:
http://type-exit.org/adventures-with-open-source-bi/2011/03/taking-luciddb-for-a-test-drive/
BTW, I had a _very_ hard time loading the file, in fact could not load the last record. No other DB had that issue. If you know why, please notify about that as well (not related to the bug at all, the query works perfect with 999999 records, but very intriguing)
Reproducible: Always
### Steps to Reproduce:
1. Load the data table from above described link
2. try to run the query where the sub-query is in the FROM clause, e.g.:
SELECT
SUM(PRICE) as PRICE,
ITEM,
CATEGORY,
CITY,
REGION,
COUNTRY
FROM
(SELECT MAX(price) as MAXPRICE FROM SALESMART) T,
SALESMART S
WHERE T.MAXPRICE = S.PRICE
GROUP BY
ITEM,
CATEGORY,
CITY,
REGION,
COUNTRY;
3. nothing happens
### Actual Results:
I get NOTHING when I try it, no error, no warning, no syntax control...
### Expected Results:
The same result as when running a subquery in the WHERE clause, e.g.:
SELECT
SUM(PRICE) as PRICE,
ITEM,
CATEGORY,
CITY,
REGION,
COUNTRY
FROM SALESMART S
WHERE S.PRICE IN (SELECT MAX(price) as MAXPRICE FROM SALESMART)
GROUP BY
ITEM,
CATEGORY,
CITY,
REGION,
COUNTRY;
MonetDB 5 server v11.3.1 "Apr2011"
Serving database 'demo', using 2 threads
Compiled for x86_64-pc-winnt/64bit with 64bit OIDs dynamically linked
Found 3.936 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2011 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Listening for connection requests on mapi:monetdb://cfc-T61:50000/
MonetDB/SQL module loaded
## Comment 15815
Date: 2011-05-17 14:03:32 +0200
From: @njnes
Changeset [a8b6988671d1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a8b6988671d1) 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=a8b6988671d1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a8b6988671d1)
Changeset description:
fixed bug #2812
a join with a table and a simple aggregate (single value case) was incorrectly
rewriten in the sql optimizer (because the expression wasn't recognized as a
join expression).
## Comment 15816
Date: 2011-05-17 14:05:07 +0200
From: @njnes
fixed. There is indeed a small difference in handling the aggregate in the from or in the in list. The from case hit a bug in recognizing a join expression (in the sql optimizer). This was fixed. Added a test to 2011 bugtracker.
## Comment 15824
Date: 2011-05-19 18:34:03 +0200
From: me.anonimous
(In reply to comment 2)
> fixed. There is indeed a small difference in handling the aggregate in the from
> or in the in list. The from case hit a bug in recognizing a join expression (in
> the sql optimizer). This was fixed. Added a test to 2011 bugtracker.
Excellent, thanks for your amazingly quick response!
If I want to test this, where would I be able to find a nightly build (or equivalent)? Does the SP1 version of May 17 (http://dev.monetdb.org/downloads/testing/Windows/Apr2011-SP1/) contain that fix?
Thanks again!
## Comment 15825
Date: 2011-05-19 18:40:46 +0200
From: @grobian
unfortunately not, but can you try the nightlies instead?
http://monetdb.cwi.nl/testing/projects/monetdb/testweb/web/40259:b0180df2a35a/
## Comment 16000
Date: 2011-07-29 10:52:40 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| Subqueries in FROM clause not accepted | https://api.github.com/repos/MonetDB/MonetDB/issues/2812/comments | 0 | 2020-11-30T11:42:31Z | 2024-06-27T11:51:57Z | https://github.com/MonetDB/MonetDB/issues/2812 | 753,406,244 | 2,812 |
[
"MonetDB",
"MonetDB"
] | Date: 2011-05-16 11:46:58 +0200
From: George Garbis <<ggarbis>>
To: SQL devs <<bugs-sql>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
CC: charnik, @njnes
Last updated: 2015-05-08 10:28:47 +0200
## Comment 15806
Date: 2011-05-16 11:46:58 +0200
From: George Garbis <<ggarbis>>
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.24 (KHTML, like Gecko) Ubuntu/10.10 Chromium/11.0.696.65 Chrome/11.0.696.65 Safari/534.24
Build Identifier:
Giving the query above mserver allocates the whole memory and it is killed by OS when both RAM and SAWP are full.
Even if query is prefixed with EXPLAIN or PLAN the problem still occurs
query.sql:
PLAN SELECT DISTINCT
h3.obj,
CASE
WHEN u_ENDPOINT.value IS NOT NULL THEN u_ENDPOINT.value
WHEN l_ENDPOINT.value IS NOT NULL THEN l_ENDPOINT.value
WHEN ll_ENDPOINT.value IS NOT NULL THEN ll_ENDPOINT.value
WHEN lu_ENDPOINT.value IS NOT NULL THEN lu_ENDPOINT.value
END
FROM
triples t0
INNER JOIN triples h1 ON (h1.pred = 21 AND h1.obj = 42 AND h1.subj = t0.subj)
INNER JOIN triples h2 ON (h2.pred = 5 AND h2.subj = t0.subj)
INNER JOIN triples h3 ON (h3.pred = 20 AND h3.subj = t0.subj)
INNER JOIN triples i4 ON (i4.pred = 28 AND i4.subj = h2.obj)
INNER JOIN triples c5 ON (c5.pred = 8 AND c5.subj = h2.obj)
INNER JOIN triples h6 ON (h6.pred = 11 AND h6.subj = c5.obj)
INNER JOIN triples h7 ON (h7.subj = 50 AND h7.pred = 11 )
LEFT JOIN uri_values u_PROPERTYTYPE ON (u_PROPERTYTYPE.id = i4.obj)
LEFT JOIN long_uri_values lu_PROPERTYTYPE ON (lu_PROPERTYTYPE.id = i4.obj)
LEFT JOIN label_values l_PROPERTYTYPE ON (l_PROPERTYTYPE.id = i4.obj)
LEFT JOIN long_label_values ll_PROPERTYTYPE ON (ll_PROPERTYTYPE.id = i4.obj)
LEFT JOIN geo_values l_SERVICEREGIONGEO ON (l_SERVICEREGIONGEO.id = h6.obj)
LEFT JOIN long_label_values ll_SERVICEREGIONGEO ON (ll_SERVICEREGIONGEO.id = h6.obj)
LEFT JOIN geo_values l_SOLENTGEO ON (l_SOLENTGEO.id = h7.obj)
LEFT JOIN long_label_values ll_SOLENTGEO ON (ll_SOLENTGEO.id = h7.obj)
LEFT JOIN uri_values u_ENDPOINT ON (u_ENDPOINT.id = h3.obj)
LEFT JOIN label_values l_ENDPOINT ON (l_ENDPOINT.id = h3.obj)
LEFT JOIN long_label_values ll_ENDPOINT ON (ll_ENDPOINT.id = h3.obj)
LEFT JOIN long_uri_values lu_ENDPOINT ON (lu_ENDPOINT.id = h3.obj)
WHERE
t0.pred = 2
AND t0.obj = 3
AND (
CASE WHEN NOT(u_PROPERTYTYPE.value IS NULL AND lu_PROPERTYTYPE.value IS NOT NULL AND lu_PROPERTYTYPE.value IS NULL ) AND NOT(u_PROPERTYTYPE.value IS NULL AND lu_PROPERTYTYPE.value IS NULL ) THEN
CASE WHEN u_PROPERTYTYPE.value IS NOT NULL THEN u_PROPERTYTYPE.value
WHEN lu_PROPERTYTYPE.value IS NOT NULL THEN lu_PROPERTYTYPE.value
END
WHEN NOT(l_PROPERTYTYPE.value IS NULL AND ll_PROPERTYTYPE.value IS NOT NULL AND ll_PROPERTYTYPE.value IS NULL ) AND NOT(l_PROPERTYTYPE.value IS NULL AND ll_PROPERTYTYPE.value IS NULL ) THEN
CASE WHEN l_PROPERTYTYPE.value IS NOT NULL THEN l_PROPERTYTYPE.value
WHEN ll_PROPERTYTYPE.value IS NOT NULL THEN ll_PROPERTYTYPE.value
END
END = 'example1'
OR
CASE WHEN NOT(u_PROPERTYTYPE.value IS NULL AND lu_PROPERTYTYPE.value IS NOT NULL AND lu_PROPERTYTYPE.value IS NULL ) AND NOT(u_PROPERTYTYPE.value IS NULL AND lu_PROPERTYTYPE.value IS NULL ) THEN
CASE WHEN u_PROPERTYTYPE.value IS NOT NULL THEN u_PROPERTYTYPE.value
WHEN lu_PROPERTYTYPE.value IS NOT NULL THEN lu_PROPERTYTYPE.value
END
WHEN NOT(l_PROPERTYTYPE.value IS NULL AND ll_PROPERTYTYPE.value IS NOT NULL AND ll_PROPERTYTYPE.value IS NULL ) AND NOT(l_PROPERTYTYPE.value IS NULL AND ll_PROPERTYTYPE.value IS NULL ) THEN
CASE WHEN l_PROPERTYTYPE.value IS NOT NULL THEN l_PROPERTYTYPE.value
WHEN ll_PROPERTYTYPE.value IS NOT NULL THEN ll_PROPERTYTYPE.value
END
END = 'example2'
)
AND (Within(l_SERVICEREGIONGEO.strdfgeo,l_SOLENTGEO.strdfgeo))
;
schema.sql:
CREATE TABLE geo_values (
id integer NOT NULL,
strdfgeo geometry
);
CREATE TABLE label_values (
id integer NOT NULL,
value character varying(255) NOT NULL
);
CREATE TABLE long_label_values (
id integer NOT NULL,
value text NOT NULL
);
CREATE TABLE long_uri_values (
id integer NOT NULL,
value text NOT NULL
);
CREATE TABLE triples (
ctx integer NOT NULL,
subj integer NOT NULL,
pred integer NOT NULL,
obj integer NOT NULL,
expl boolean NOT NULL,
interval_start timestamp,
interval_end timestamp
);
CREATE TABLE uri_values (
id integer NOT NULL,
value character varying(255) NOT NULL
);
Reproducible: Always
### Steps to Reproduce:
1. Create a db (e.g. monetdb create testDB)
2. Release the db (e.g. monetdb release testDB)
3. Create the attached schema (e.g. mclient -d testDB < schema.sql)
4. Run the attached query (e.g. mclient -d testDB < query.sql)
### Actual Results:
MAPI = (monetdb) /tmp/.s.monetdb.50000
ACTION= read_line
QUERY = PLAN SELECT DISTINCT
h3.obj,
CASE
WHEN u_ENDPOINT.value IS NOT NULL THEN u_ENDPOINT.value
WHEN l_ENDPOINT.value IS NOT NULL THEN l_ENDPOINT.value
WHEN ll_ENDPOINT.value IS NOT NULL THEN ll_ENDPOINT.value
WHEN lu_ENDPOINT.value IS NOT NULL THEN lu_ENDPOINT.value
END
FROM
triples t0
INNER JOIN triples h1 ON (h1.pred = 21 AND h1.obj = 42 AND h1.subj = t0.subj)
INNER JOIN triples h2 ON (h2.pred = 5 AND h2.subj = t0.subj)
INNER JOIN triples h3 ON (h3.pred = 20 AND h3.subj = t0.subj)
ERROR = !Connection terminated
### Expected Results:
The execution plan of the query
## Comment 15818
Date: 2011-05-18 14:32:22 +0200
From: @njnes
Changeset [98aa97822a61](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=98aa97822a61) 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=98aa97822a61](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=98aa97822a61)
Changeset description:
improved handling of push_select_down / push_down_exp
We now only go through the tree once (topdown).
This solves bug #2811.
## Comment 15819
Date: 2011-05-18 14:32:23 +0200
From: @njnes
Changeset [3cfb9218aa1c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=3cfb9218aa1c) 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=3cfb9218aa1c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=3cfb9218aa1c)
Changeset description:
added test for bug #2811
## Comment 15999
Date: 2011-07-29 10:52:40 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
## Comment 20854
Date: 2015-05-08 10:28:47 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [4d8cbe4e597c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4d8cbe4e597c) made by Foteini Alvanaki <foteini.alvanaki@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4d8cbe4e597c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4d8cbe4e597c)
Changeset description:
crash_in_push_exp_down.Bug-2811 updated
| mserver crashes | https://api.github.com/repos/MonetDB/MonetDB/issues/2811/comments | 0 | 2020-11-30T11:42:28Z | 2024-06-27T11:51:56Z | https://github.com/MonetDB/MonetDB/issues/2811 | 753,406,221 | 2,811 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.