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: 2004-03-23 09:15:52 +0100 From: @mlkersten To: @njnes Version: -- development Last updated: 2004-03-23 10:38:52 +0100 ## Comment 589 Date: 2004-03-23 21:15:52 +0100 From: @mlkersten CREATE TABLE union_test ( id INT, val1 VARCHAR(10), val2 VARCHAR(10) ); INSERT INTO union_test VALUES(1, 'abcdef','123456'); SELECT 'abc' AS c1, '123' AS c2 UNION ALL SELECT val1 AS c1, val2 AS c2 FROM union_test; Results in the message: MAPI = monetdb@localhost:45123 ACTION= mapi_get_row QUERY = SELECT 'abc' AS c1, '123' AS c2 ERROR = !ERROR: interpret: no matching MIL operator to 'access(str, int)'. !MAYBE YOU MEAN: ! access(BAT[any::1,any::2]) : int ! access(BAT[any::1,any::2], int) : BAT[any::1,any::2] !ERROR: append(param 1): evaluation error. !WARNING: BBPdecref: range error 89 Entering a non-supported area of the implementation. ## Comment 590 Date: 2004-03-23 22:38:52 +0100 From: @njnes Logged In: YES user_id=43556 bug is fixed 'cannot insert into single values ;-) ie create bats first' ## Comment 591 Date: 2005-10-06 14:49:32 +0200 From: @drstmane Logged In: YES user_id=572415 BugDay_2005-10-06: CLAIMED BY stmane BugDay_2005-10-06: TEST ADDED / SUCCESS sql/src/test/BugDay_2005-10-06_2.9.3/Tests/union_limitation.SF-921992.* ## Comment 592 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 921992 at http://sourceforge.net/support/tracker.php?aid=921992
SQL union limitation
https://api.github.com/repos/MonetDB/MonetDB/issues/110/comments
0
2020-11-30T08:05:24Z
2024-06-27T10:54:54Z
https://github.com/MonetDB/MonetDB/issues/110
753,252,597
110
[ "MonetDB", "MonetDB" ]
Date: 2004-03-23 09:08:08 +0100 From: @mlkersten To: @njnes Version: -- development Last updated: 2004-03-23 10:44:50 +0100 ## Comment 585 Date: 2004-03-23 21:08:08 +0100 From: @mlkersten CREATE TABLE insert_test ( id INT, txt VARCHAR(32) ); INSERT INTO insert_test VALUES(1, 'foo'); INSERT INTO insert_test VALUES(2, 'bar'); INSERT INTO insert_test SELECT 3, txt FROM insert_test WHERE id=2; The answer is: MAPI = monetdb@localhost:45123 ACTION= mapi_get_row QUERY = INSERT INTO insert_test SELECT 3, txt FROM insert_test WHERE id=2; ERROR = !ERROR: interpret: no matching MIL operator to 'append(BAT[void,lng], BAT[void,sht])'. A mix-up of types seems to occur. ## Comment 586 Date: 2004-03-23 22:44:49 +0100 From: @njnes Logged In: YES user_id=43556 added missing type check ## Comment 587 Date: 2005-10-06 14:41:53 +0200 From: @drstmane Logged In: YES user_id=572415 BugDay_2005-10-06: CLAIMED BY stmane BugDay_2005-10-06: TEST ADDED / SUCCESS sql/src/test/BugDay_2005-10-06_2.9.3/Tests/type_error_in_self-insert.SF-921985.* ## Comment 588 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 921985 at http://sourceforge.net/support/tracker.php?aid=921985
SQL type error in self-insert
https://api.github.com/repos/MonetDB/MonetDB/issues/109/comments
0
2020-11-30T08:05:22Z
2024-06-27T10:54:53Z
https://github.com/MonetDB/MonetDB/issues/109
753,252,562
109
[ "MonetDB", "MonetDB" ]
Date: 2004-03-23 08:58:00 +0100 From: @mlkersten To: @njnes Version: -- development Last updated: 2004-03-23 10:46:16 +0100 ## Comment 580 Date: 2004-03-23 20:58:00 +0100 From: @mlkersten CREATE TABLE null_1 ( id INT NOT NULL, text1 VARCHAR(32) NOT NULL, text2 VARCHAR(32) NOT NULL DEFAULT 'foo' ); INSERT INTO null_1 (id) VALUES(1); INSERT INTO null_1 (text1) VALUES('test'); will simply kill the server without leaving a trace of what happens ## Comment 581 Date: 2004-03-23 21:01:38 +0100 From: @mlkersten Logged In: YES user_id=490798 Another one, most likely in the same category: CREATE TABLE timestamp ( id INT, ts1 TIMESTAMP(8) NOT NULL, ts2 TIMESTAMP(8) ); INSERT INTO timestamp VALUES(1, NULL, NULL); INSERT INTO timestamp (id, ts1) VALUES(2, NULL); ## Comment 582 Date: 2004-03-23 22:46:16 +0100 From: @njnes Logged In: YES user_id=43556 missing defaults are now checked. ## Comment 583 Date: 2005-10-06 14:33:08 +0200 From: @drstmane Logged In: YES user_id=572415 BugDay_2005-10-06: CLAIMED BY stmane BugDay_2005-10-06: TEST ADDED / SUCCESS sql/src/test/BugDay_2005-10-06_2.9.3/Tests/inserts_with_defaults.SF-921977.* ## Comment 584 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 921977 at http://sourceforge.net/support/tracker.php?aid=921977
Insert crashes the server
https://api.github.com/repos/MonetDB/MonetDB/issues/108/comments
0
2020-11-30T08:05:19Z
2024-06-27T10:54:52Z
https://github.com/MonetDB/MonetDB/issues/108
753,252,529
108
[ "MonetDB", "MonetDB" ]
Date: 2004-03-23 08:00:34 +0100 From: @grobian To: @njnes Version: -- development Last updated: 2004-03-27 09:30:17 +0100 ## Comment 575 Date: 2004-03-23 20:00:34 +0100 From: @grobian Although my disk is far from full, Monet closes with a possible full disk error when I try to load the sql server module. gdb reveals the following: [New Thread 1080064960 (LWP 24440)] Monet Database Server V4.3.16_rc05 Copyright (c) 1993-2004, CWI. All rights reserved. compiled for i686-pc-linux-gnu/32bit; dynamically linked. monet>module(sql_server); Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1080064960 (LWP 24440)] 0x40138e27 in strPut (h=0x805f930, dst=0x8481268, v=0x41a65014 " deathrate was due to scurvy. See also the BOT (4392).") at gdk_atoms.mx:1506 1506 gdk_atoms.mx: No such file or directory. in gdk_atoms.mx Current language: auto; currently c (gdb) p v $1 = 0x41a65014 " deathrate was due to scurvy. See also the BOT (4392)." (gdb) p x $2 = 0x41c02fc0 <Address 0x41c02fc0 out of bounds> (gdb) p h->base $3 = 0x41ae3010 "x\224\020" (gdb) p l $4 = (var_t *) 0x41ae3730 (gdb) p *l $5 = 1179564 The bus error takes place a code loop to "/* search hash-table, if double-elimintation is still in place */" ## Comment 576 Date: 2004-03-23 20:45:35 +0100 From: @drstmane Logged In: YES user_id=572415 same comment as with http://sourceforge.net/support/tracker.php?aid=921673 "sudden death from SQL server": Mserver is (now) catches SIGSEGV (just like SIGBUS), and then says "!ERROR: Mserver internal error, please restart. Please make sure your disk is not full." (cf. src/gdk/gdk_utils.mx) Peter "fixed" this recently... ## Comment 577 Date: 2004-03-27 09:30:17 +0100 From: @njnes Logged In: YES user_id=43556 the problem is caused by a corrupt db. If you find the cause (sql script) which caused the corrupt db, we will try to fix this, ie but thats a different bug! ## Comment 578 Date: 2005-10-06 14:15:16 +0200 From: @drstmane Logged In: YES user_id=572415 BugDay_2005-10-06: CLAIMED BY stmane BugDay_2005-10-06: NO TEST / REDUNDANT loading module sql_server is tested in various places ## Comment 579 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 921937 at http://sourceforge.net/support/tracker.php?aid=921937
Full disk error on module(sql_server)
https://api.github.com/repos/MonetDB/MonetDB/issues/107/comments
0
2020-11-30T08:05:16Z
2024-06-28T07:36:24Z
https://github.com/MonetDB/MonetDB/issues/107
753,252,495
107
[ "MonetDB", "MonetDB" ]
Date: 2004-03-23 04:37:26 +0100 From: @menzowindhouwer To: Stefan Manegold &lt;<Stefan.Manegold>&gt; Version: -- development Last updated: 2004-03-23 10:31:47 +0100 ## Comment 571 Date: 2004-03-23 16:37:26 +0100 From: @menzowindhouwer The find command matches the nil heads of a void BAT, even while the seqbase is set. Example: monet>VAR b := new(void,str).seqbase(0@0); monet>b.insert(nil,"zero"); monet>b.print; ----------------- h tmp_29 name void str type ----------------- [ 0@0, "zero" ] monet>printf("oid(0) -> %s\n",str(b.find(oid(0)))); oid(0) -> zero monet>printf("oid(nil) -> %s\n",str(b.find(oid(nil)))); oid(nil) -> zero The second find call should fail! ## Comment 572 Date: 2004-03-23 22:31:47 +0100 From: @drstmane Logged In: YES user_id=572415 I didn't analyze it completely, but I suspect that artihmetics with oid_nil did cause overflows in BUNfndVOID macro. Anyway, BUNfndVOID now explicitly checks whether either the requested value or the seqbase is nil, and hence finds neither "nil" in a non-nil column nor non-nil's in a nil column. However, find() still finds "nil" on a void-column with seqbase nil (just like "select(nil)" finds all nil's). Question: Is this the way it should be ??? ## Comment 573 Date: 2005-10-06 14:07:54 +0200 From: @drstmane Logged In: YES user_id=572415 BugDay_2005-10-06: CLAIMED BY stmane BugDay_2005-10-06: TEST ADDED / SUCCESS MonetDB/tests/BugDay_2005-10-06_4.9.3/Tests/find_nil_in_void.SF-921814.* ## Comment 574 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 921814 at http://sourceforge.net/support/tracker.php?aid=921814
find(nil) matches any void head in BAT with seqbase
https://api.github.com/repos/MonetDB/MonetDB/issues/106/comments
0
2020-11-30T08:05:14Z
2024-06-27T10:54:50Z
https://github.com/MonetDB/MonetDB/issues/106
753,252,471
106
[ "MonetDB", "MonetDB" ]
Date: 2004-03-23 11:47:15 +0100 From: @sjoerdmullender To: @njnes Version: -- development Last updated: 2004-03-23 09:08:22 +0100 ## Comment 563 Date: 2004-03-23 11:47:15 +0100 From: @sjoerdmullender With the following query (from crash-me) the server crashes without any message: select 2 in (3,2,5,9,5,1) ; Using strace revealed that before the thread that read the statement does any other system calls, it gets a SEGFAULT. ## Comment 564 Date: 2004-03-23 14:15:45 +0100 From: @grobian Logged In: YES user_id=963970 I can add another: Executing query: SELECT null AS TABLE_CAT, schemas.name AS TABLE_SCHEM, tables.name AS TABLE_NAME, columns.name AS COLUMN_NAME, columns.type AS TYPE_NAME, columns.type_digits AS COLUMN_SIZE, columns.type_scale AS DECIMAL_DIGITS, 0 AS BUFFER_LENGTH, 10 AS NUM_PREC_RADIX, "null" AS nullable, null AS REMARKS, columns.default AS COLUMN_DEF, 0 AS SQL_DATA_TYPE, 0 AS SQL_DATETIME_SUB, 0 AS CHAR_OCTET_LENGTH, columns.number + 1 AS ORDINAL_POSITION, null AS SCOPE_CATALOG null AS SCOPE_SCHEMA, null AS SCOPE_TABLE FROM columns, tables, schemas WHERE columns.table_id = tables.id AND tables.schema_id = schemas.id java.sql.SQLException: java.io.IOException: Unexpected end of stream Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1165200176 (LWP 15329)] 0x418f1c7e in dlist_append_default (l=0x0, n=0x8d7c408) at sql_symbol.mx:353 353 sql_symbol.mx: No such file or directory. in sql_symbol.mx ## Comment 565 Date: 2004-03-23 16:38:58 +0100 From: @drstmane Logged In: YES user_id=572415 I'm not quite sure, whether this is related, but: Mserver is (now) supposed to catch SIGSEGV (just like SIGBUS), and the should say "!ERROR: Mserver internal error, please restart. Please make sure your disk is not full." (cf. src/gdk/gdk_utils.mx) Hence, the "silent crash" means that the signal handler does not work, or at least its output "vanishes" somewhere... ## Comment 566 Date: 2004-03-23 20:33:03 +0100 From: @njnes Logged In: YES user_id=43556 The fixed sql statement works in my current version check in will follow later today (there was a , missing ) SELECT null AS TABLE_CAT, schemas.name AS TABLE_SCHEM, tables.name AS TABLE_NAME, columns.name AS COLUMN_NAME, columns.type AS TYPE_NAME, columns.type_digits AS COLUMN_SIZE, columns.type_scale AS DECIMAL_DIGITS, 0 AS BUFFER_LENGTH, 10 AS NUM_PREC_RADIX, "null" AS nullable, null AS REMARKS, columns.default AS COLUMN_DEF, 0 AS SQL_DATA_TYPE, 0 AS SQL_DATETIME_SUB, 0 AS CHAR_OCTET_LENGTH, columns.number + 1 AS ORDINAL_POSITION, null AS SCOPE_CATALOG, null AS SCOPE_SCHEMA, null AS SCOPE_TABLE from schemas, tables, columns WHERE columns.table_id = tables.id AND tables.schema_id = schemas.id; ## Comment 567 Date: 2004-03-23 21:08:22 +0100 From: @njnes Logged In: YES user_id=43556 fixed. Crash and added implementation to really handle the query ## Comment 568 Date: 2004-03-24 09:30:21 +0100 From: @grobian Logged In: YES user_id=963970 The server doesn't crash anymore, but the query isn't handled correct at all. Opening new bug for it. ## Comment 569 Date: 2005-10-06 13:51:30 +0200 From: @drstmane Logged In: YES user_id=572415 BugDay_2005-10-06: CLAIMED BY stmane BugDay_2005-10-06: TEST ADDED / SUCCESS sql/src/test/BugDay_2005-10-06_2.9.3/Tests/CrashMe_SQL_server_crash-1.SF-921673.* sql/src/test/BugDay_2005-10-06_2.9.3/Tests/CrashMe_SQL_server_crash-2.SF-921673.* ## Comment 570 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 921673 at http://sourceforge.net/support/tracker.php?aid=921673
sudden death from SQL server
https://api.github.com/repos/MonetDB/MonetDB/issues/105/comments
0
2020-11-30T08:05:11Z
2024-06-27T10:54:49Z
https://github.com/MonetDB/MonetDB/issues/105
753,252,437
105
[ "MonetDB", "MonetDB" ]
Date: 2004-03-22 06:04:40 +0100 From: @sjoerdmullender To: SQL devs &lt;<bugs-sql>&gt; Version: 2.40.1 (Oct2010) [obsolete] CC: @romulogoncalves, @njnes, @drstmane Last updated: 2011-03-28 17:31:43 +0200 ## Comment 547 Date: 2004-03-22 18:04:40 +0100 From: @sjoerdmullender The attached file contains a query from the crash-me script that causes a SEGFAULT in the server. My guess is that there is a buffer overflow in sql_gencode. I'm looking into it. ## Comment 548 Date: 2004-03-22 20:09:12 +0100 From: @njnes Logged In: YES user_id=43556 A to large column name was generated. Column names are now protected, but a full audit (buffer overflow) of sql_gencode is needed. ## Comment 549 Date: 2005-10-06 12:34:49 +0200 From: @drstmane Logged In: YES user_id=572415 BugDay_2005-10-06: CLAIMED BY stmane BugDay_2005-10-06: TEST ADDED / FAILURE test (excl. stable.out) added as sql/src/test/BugDay_2005-10-06_2.9.3/Tests/huge_expression_and_column_name.SF-921173.* bug re-opened, as the segfault re-occurs (at least with MonetDB 4.9.3 + SQL 2.9.3 compiled with gcc 4.0.1 on my 64-bit Fedora Core sytem) It might very well be that we run out of stack space with a rather deep recursion...! ## Comment 550 Date: 2005-10-23 00:11:55 +0200 From: @njnes Logged In: YES user_id=43556 check for to big (recursion depth) queries is added. ## Comment 551 Date: 2005-10-23 13:57:33 +0200 From: @njnes Logged In: YES user_id=43556 check for to big (recursion depth) queries is added. ## Comment 552 Date: 2006-01-14 13:35:02 +0100 From: @drstmane Logged In: YES user_id=572415 re-opend as it segfauls on the same platforms as 1314982 "kill(0) causes SEGFAULT" https://sourceforge.net/tracker/index.php?func=detail&aid=1314982&group_id=56967&atid=482468 and 1292727 "Mserver segfault because of 'col_name'" https://sourceforge.net/tracker/index.php?func=detail&aid=1292727&group_id=56967&atid=482468 Fedora Core 4 (32-bit) http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/GNU.32.32.d-Fedora4/src_test_BugDay_2005-10-06_2.9.3/huge_expression_and_column_name.SF-921173.err.00.html Gentoo 1.6.13 (32-bit) http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/GNU.32.32.d-Gentoo1.6.13/src_test_BugDay_2005-10-06_2.9.3/huge_expression_and_column_name.SF-921173.err.00.html SuSE 9.3 (32-bit) http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/GNU.32.32.d-SuSE9.3/src_test_BugDay_2005-10-06_2.9.3/huge_expression_and_column_name.SF-921173.err.00.html SuSE 9ES (32-bit) http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/GNU.32.32.d-SuSE9ES/src_test_BugDay_2005-10-06_2.9.3/huge_expression_and_column_name.SF-921173.err.00.html ## Comment 553 Date: 2006-01-15 14:15:29 +0100 From: @drstmane Logged In: YES user_id=572415 Closed as the actual/original bug is fixed. The segfault on some platforms is file in this new report 1406591 "several tests cause segfault on the same subset of platforms" https://sourceforge.net/tracker/index.php?func=detail&aid=1406591&group_id=56967&atid=482468 ## Comment 554 Date: 2008-06-01 21:44:08 +0200 From: @drstmane Logged In: YES user_id=572415 Originator: NO Re-opened as the respective test fails again (still?). With M5 server (both default and "algebra" SQL compiler), only the output seems to differ (returns "NULL" instead of "2001"): http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests5103/GNU.64.64.d-Fedora8/src_test_BugDay_2005-10-06_2.9.3/huge_expression_and_column_name.SF-921173.out.00.html http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTestsG103/GNU.64.64.d-Fedora8/src_test_BugDay_2005-10-06_2.9.3/huge_expression_and_column_name.SF-921173.out.00.html With M4 server, the test triggers a segfault (at least on some architectures): http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests4103/GNU.64.64.d-Fedora8/src_test_BugDay_2005-10-06_2.9.3/huge_expression_and_column_name.SF-921173.err.00.html ## Comment 555 Date: 2008-06-02 09:13:45 +0200 From: @njnes Logged In: YES user_id=43556 Originator: NO The problem here is overflow detection. On gdk and m4/m5 level we need to introduce some overflow exceptions. ## Comment 556 Date: 2008-11-10 09:08:14 +0100 From: @mlkersten The overflow is caused by the SQL default to assume a tinyint type as argument. We cannot assume the compiler to be more clever. The result is an overflow which is correctly catched with a null. (provided tinyint is 0-255 ;)) ## Comment 557 Date: 2009-02-15 21:08:19 +0100 From: @drstmane test sql/src/test/BugDay_2005-10-06_2.9.3/Tests/huge_expression_and_column_name.SF-921173* has been disabled in the Feb2009 release branch as the bug won't be fixed, there. ## Comment 558 Date: 2009-08-13 18:40:04 +0200 From: @drstmane Should this test be disabled in the Aug2009 branch, again? cf. http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugDay_2005-10-06_2.9.3/huge_expression_and_column_name.SF-921173.out.00.html ## Comment 559 Date: 2009-08-14 14:02:52 +0200 From: @drstmane tagged subject ## Comment 560 Date: 2009-11-16 23:19:19 +0100 From: @drstmane test has been disabled in Nov2009 branch, only. ## Comment 561 Date: 2009-11-29 17:01:04 +0100 From: @njnes closed, we no longjmp out of the recursion. The overflow problem which we used to hit here (when we didn't crash) isn't fixed but is covered by the 'case overflow bug'. ## Comment 562 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 921173 at http://sourceforge.net/support/tracker.php?aid=921173 ## Comment 14385 Date: 2010-07-13 14:54:16 +0200 From: @sjoerdmullender *** Bug #2610 has been marked as a duplicate of this bug. *** ## Comment 14386 Date: 2010-07-13 15:00:20 +0200 From: @sjoerdmullender This crashes in the Jun2010 branch. ## Comment 14387 Date: 2010-07-13 15:04:31 +0200 From: @sjoerdmullender Looks like a double free (but of course it could be something entirely different): Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffdf49b710 (LWP 17101)] 0x00007fffe038582a in sa_destroy (sa=0x7fffd0007608) at /ufs/sjoerd/src/MonetDB/candidate/sql/src/common/sql_mem.mx:136 136 GDKfree(sa->blks[i]); (gdb) p sa $1 = (sql_allocator *) 0x7fffd0007608 (gdb) p *sa $2 = {size = 15842497851538791387, nr = 15842497851538791387, blks = 0xdbdbdbdbdbdbdbdb, used = 15842497851538791387} (gdb) bt 0 0x00007fffe038582a in sa_destroy (sa=0x7fffd0007608) at /ufs/sjoerd/src/MonetDB/candidate/sql/src/common/sql_mem.mx:136 1 0x00007fffe02ffb7b in cq_delete (clientid=1, q=0x7fffd03e3a08) at /ufs/sjoerd/src/MonetDB/candidate/sql/src/server/sql_qc.mx:117 2 0x00007fffe02ffc57 in qc_destroy (cache=0x7fffd00075a8) at /ufs/sjoerd/src/MonetDB/candidate/sql/src/server/sql_qc.mx:147 3 0x00007fffe031a425 in mvc_destroy (m=0x7fffd0005438) at /ufs/sjoerd/src/MonetDB/candidate/sql/src/server/sql_mvc.mx:753 4 0x00007fffe02d2739 in SQLexitClient (c=0x605b38) at /ufs/sjoerd/src/MonetDB/candidate/sql/src/backends/monet5/sql_scenario.mx:492 5 0x00007ffff7d22ee7 in runScenarioBody (c=0x605b38) at /ufs/sjoerd/src/MonetDB/candidate/MonetDB5/src/mal/mal_scenario.mx:670 6 0x00007ffff7d22f3d in runScenario (c=0x605b38) at /ufs/sjoerd/src/MonetDB/candidate/MonetDB5/src/mal/mal_scenario.mx:682 7 0x00007ffff7cd6e99 in MSserveClient (dummy=0x605b38) at /ufs/sjoerd/src/MonetDB/candidate/MonetDB5/src/mal/mal_session.mx:473 8 0x0000003a8d606a3a in start_thread () from /lib64/libpthread.so.0 9 0x0000003a8cade77d in clone () from /lib64/libc.so.6 10 0x0000000000000000 in ?? () (gdb) ## Comment 14847 Date: 2010-08-30 09:23:22 +0200 From: @sjoerdmullender The Jun2010-SP2 version has been released. ## Comment 14864 Date: 2010-08-30 17:01:49 +0200 From: @sjoerdmullender Changeset http://dev.monetdb.org/hg/MonetDB/rev/ea928da4ea87 fixed the latest incarnation of this bug. ## Comment 14865 Date: 2010-08-30 17:04:09 +0200 From: @sjoerdmullender Changeset [e4a025a9f189](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e4a025a9f189) 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=e4a025a9f189](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e4a025a9f189) Changeset description: Added changelog for bug #104. ## Comment 15163 Date: 2010-10-30 11:23:40 +0200 From: @drstmane Is this bug indeed fixed? The respective test does not trigger any crash or error anymore, but the result is (unexpectedly) NULL; cf., http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugDay_2005-10-06_2.9.3/huge_expression_and_column_name.SF-921173.out.00.html ## Comment 15258 Date: 2010-12-03 21:31:00 +0100 From: @njnes crash is fixed now (by the flattend stmt tree). Still a fix for the overflow is needed (but covered by the overflow bug report) ## Comment 15658 Date: 2011-03-28 17:31:43 +0200 From: @sjoerdmullender The Mar2011 version has been released.
SQL: extremely long and complex query causes SEGFAULT
https://api.github.com/repos/MonetDB/MonetDB/issues/104/comments
0
2020-11-30T08:05:06Z
2024-06-27T10:54:48Z
https://github.com/MonetDB/MonetDB/issues/104
753,252,382
104
[ "MonetDB", "MonetDB" ]
Date: 2004-03-21 10:00:40 +0100 From: @swingbit To: Stefan Manegold &lt;<Stefan.Manegold>&gt; Version: -- development Last updated: 2004-04-28 09:41:35 +0200 ## Comment 538 Date: 2004-03-21 22:00:40 +0100 From: @swingbit The html documentation about mil contains many links to modules documentation and all of them are broken. ## Comment 539 Date: 2004-03-21 23:16:57 +0100 From: @drstmane Logged In: YES user_id=572415 Thanks. This one is known. Fix pending --- once there is time ... ;-) ## Comment 540 Date: 2004-03-21 23:18:41 +0100 From: @mlkersten Logged In: YES user_id=490798 Correct. It reflects an old web infrastructure. Most have been changed already in the .../doc versions. Need to add Mserver and MapiClient at the Documentation level in the web, because it is often referred too. ## Comment 541 Date: 2004-03-22 14:12:44 +0100 From: @mlkersten Logged In: YES user_id=490798 Web site takes precedence at this stage A more thorough solution will be designed by Stefan for the sept release. ## Comment 542 Date: 2004-04-05 15:03:01 +0200 From: @MarcinZukowski Logged In: YES user_id=607094 In general, this thingie is useful: http://validator.w3.org/checklink?uri=monetdb.cwi. nl&summary=on&hide_type=all&recursive=on&depth=&check=Check Or perhaps, something similar executed locally? We could even perhaps use wget for that :) ## Comment 543 Date: 2004-04-28 09:40:59 +0200 From: @drstmane Logged In: YES user_id=572415 website and "make html" documentation are finally synced and fixed. ## Comment 544 Date: 2004-04-28 09:41:35 +0200 From: @drstmane Logged In: YES user_id=572415 forgot to close it ... ## Comment 545 Date: 2005-10-06 11:22:32 +0200 From: @drstmane Logged In: YES user_id=572415 BugDay_2005-10-06: CLAIMED BY stmane BugDay_2005-10-06: NO TEST / WEBSITE ## Comment 546 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 920640 at http://sourceforge.net/support/tracker.php?aid=920640
broken links in html documentation
https://api.github.com/repos/MonetDB/MonetDB/issues/103/comments
0
2020-11-30T08:05:03Z
2024-06-27T10:54:47Z
https://github.com/MonetDB/MonetDB/issues/103
753,252,349
103
[ "MonetDB", "MonetDB" ]
Date: 2004-03-21 08:40:32 +0100 From: @mlkersten To: Peter Boncz &lt;<boncz>&gt; Version: -- development Last updated: 2007-11-30 04:20:04 +0100 ## Comment 527 Date: 2004-03-21 20:40:32 +0100 From: @mlkersten Stress testing Mserver with SQL showed that when the disk fills up both Mserver and MapiClient simply stop without giving a warning. The underlying cause of the diskfiller are 1) maintaining logs too long 2) not garbage collecting intermediate bats. ## Comment 528 Date: 2004-03-21 21:58:05 +0100 From: @mlkersten Logged In: YES user_id=490798 The problem raised on leaving behind BATs behind in SQL has 1) disappeared or 2) is a side-effect of something else. I ran my tests from 1K .. 10M on an empty DB and there are no left-over bats anymore. In an earlier run tonight I noticed left-overs though, but these may have been caused by hitting the disk-limit wall in an earlier test. Upon system restart the transient BATs with lrefcnt>0 and refcnt==0 should be removed. I haven;t checked the code for this action. ## Comment 529 Date: 2004-03-22 14:16:37 +0100 From: @mlkersten Logged In: YES user_id=490798 Peter, check these remarks and make sure the BBP performs a proper re-init. ## Comment 530 Date: 2004-03-28 15:48:01 +0200 From: @mlkersten Logged In: YES user_id=490798 The situation has significantly improved. The DBtapestry test runs do not run into the disklimit. For the time being the report is closed. ## Comment 531 Date: 2005-10-06 11:18:24 +0200 From: @drstmane Logged In: YES user_id=572415 BugDay_2005-10-06: CLAIMED BY stmane BugDay_2005-10-06: NO TEST / POSTPONED - testing what happens in case of a fulll disk is hard to do automatically in Mtest - general check for left-over BATs should be added to Mtest itself - set priority to 9 to keep us reminded ## Comment 532 Date: 2005-11-06 10:50:30 +0100 From: @drstmane Logged In: YES user_id=572415 BugDay_2005-10-06: "left-overs" are now marked as "pending" ## Comment 533 Date: 2005-11-21 04:20:17 +0100 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; ---- Original comment by: sf-robot@users.sourceforge.net ---- Logged In: YES user_id=1312539 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ## Comment 534 Date: 2006-11-22 04:20:04 +0100 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; ---- Original comment by: sf-robot@users.sourceforge.net ---- Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 365 days (the time period specified by the administrator of this Tracker). ## Comment 535 Date: 2006-11-29 10:05:53 +0100 From: @drstmane Logged In: YES user_id=572415 Originator: NO over-ruling "sf-robot": re-set to "Pending" since adding a proper test has neither been done nor finally been discarded, yet. User (submitter) & developer (assignee), please check, again. ## Comment 536 Date: 2007-11-30 04:20:04 +0100 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; ---- Original comment by: sf-robot@users.sourceforge.net ---- Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 365 days (the time period specified by the administrator of this Tracker). ## Comment 537 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 920611 at http://sourceforge.net/support/tracker.php?aid=920611
Full disk error
https://api.github.com/repos/MonetDB/MonetDB/issues/102/comments
0
2020-11-30T08:04:59Z
2024-06-28T07:36:24Z
https://github.com/MonetDB/MonetDB/issues/102
753,252,318
102
[ "MonetDB", "MonetDB" ]
Date: 2004-03-21 07:30:35 +0100 From: @grobian To: @njnes Version: -- development Last updated: 2004-03-23 09:00:43 +0100 ## Comment 520 Date: 2004-03-21 19:30:35 +0100 From: @grobian Try to execute the following query: SELECT 'null' AS TABLE_CAT, schemas.name AS TABLE_SCHEM, tables.name AS TABLE_NAME, 'SYSTEM TABLE' AS TABLE_TYPE, '' AS REMARKS, 'null' AS TYPE_CAT, 'null' AS TYPE_SCHEM, 'null' AS TYPE_NAME, 'id' AS SELF_REFERENCING_COL_NAME, 'SYSTEM' AS REF_GENERATION FROM tables, schemas WHERE tables.schema_id = schemas.id AND tables.type = 1 UNION ALL SELECT 'null' AS TABLE_CAT, schemas.name AS TABLE_SCHEM, tables.name AS TABLE_NAME, 'TABLE' AS TABLE_TYPE, '' AS REMARKS, 'null' AS TYPE_CAT, 'null' AS TYPE_SCHEM, 'null' AS TYPE_NAME, 'id' AS SELF_REFERENCING_COL_NAME, 'SYSTEM' AS REF_GENERATION FROM tables, schemas WHERE tables.schema_id = schemas.id AND tables.type = 0 UNION ALL SELECT 'null' AS TABLE_CAT, schemas.name AS TABLE_SCHEM, tables.name AS TABLE_NAME, 'VIEW' AS TABLE_TYPE, tables.query AS REMARKS, 'null' AS TYPE_CAT, 'null' AS TYPE_SCHEM, 'null' AS TYPE_NAME, 'id' AS SELF_REFERENCING_COL_NAME, 'SYSTEM' AS REF_GENERATION FROM tables, schemas WHERE tables.schema_id = schemas.id AND tables.type = 2 results in: Monet Database Server V4.3.16_rc04 Copyright (c) 1993-2004, CWI. All rights reserved. compiled for i686-pc-linux-gnu/32bit; dynamically linked. monet>module(sql_server); monet>missing table name 45: st_const missing table name 45: st_const missing table name 45: st_const missing table name 45: st_const missing table name 45: st_const missing table name 45: st_const missing table name 45: st_const missing table name 45: st_const Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1165200176 (LWP 6297)] 0x418ddda1 in table_ref (sql=0x8537828, scp=0x85edf58, tableref=0x0) at sql_semantic.mx:248 248 sql_semantic.mx: No such file or directory. in sql_semantic.mx Current language: auto; currently c ## Comment 521 Date: 2004-03-21 20:12:17 +0100 From: @grobian Logged In: YES user_id=963970 the same problem occurs when executing select * from (select * from tables union select * from tables) as a the subselect itself executes fine, however when the subselect is extented with another union on the same table, the server crashes again. This behaviour makes me believe there is a problem with the intermediate resultsets, as the error is a segv caused by an -> operation on a variable 'tableref' which is null. ## Comment 522 Date: 2004-03-23 09:00:43 +0100 From: @njnes Logged In: YES user_id=43556 fixed, wrong UNION code path was taken (UNION JOIN instead of plain set UNION) ## Comment 523 Date: 2005-10-06 11:11:33 +0200 From: @drstmane Logged In: YES user_id=572415 BugDay_2005-10-06: CLAIMED BY stmane BugDay_2005-10-06: TEST ADDED / SUCCESS added test for second example as sql/src/test/BugDay_2005-10-06_2.9.3/Tests/UNION_JOIN_vs_plain_set_UNION-2.SF-920585.* BugDay_2005-10-06: RELEASED / REASSIGN to mr-meltdown or nielsnes: first example uses attribute "type" of table "tables" which does not exist any more ## Comment 524 Date: 2005-10-06 11:15:47 +0200 From: @grobian Logged In: YES user_id=963970 BugDay_2005-10-06: CLAIMED BY meltdown ## Comment 525 Date: 2005-10-06 11:37:52 +0200 From: @grobian Logged In: YES user_id=963970 BugDay_2005-10-06: TEST ADDED / SUCCESS converted tables.type into new istable and system equivalents. sql/src/test/BugDay_2005-10-06_2.9.3/Tests/UNION_JOIN_vs_plain_set_UNION-2.SF-920585.sql ## Comment 526 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 920585 at http://sourceforge.net/support/tracker.php?aid=920585
Possible intermediate result problem? WAS:crash on long quer
https://api.github.com/repos/MonetDB/MonetDB/issues/101/comments
0
2020-11-30T08:04:56Z
2024-06-27T10:54:45Z
https://github.com/MonetDB/MonetDB/issues/101
753,252,275
101
[ "MonetDB", "MonetDB" ]
Date: 2004-03-21 05:41:07 +0100 From: @grobian To: @njnes Version: -- development Last updated: 2004-03-22 08:14:27 +0100 ## Comment 515 Date: 2004-03-21 17:41:07 +0100 From: @grobian I tried a few things but it seems impossible to select a null value. both SELECT null AS some_value; and SELECT * FROM some_table WHERE some_col = null; fail with the error: !Identifier: null unknown or ambigious ## Comment 516 Date: 2004-03-22 14:19:45 +0100 From: @mlkersten Logged In: YES user_id=490798 This is not correct SQL, but something similar is standard SQL e.g. IS NULL ## Comment 517 Date: 2004-03-22 20:14:27 +0100 From: @njnes Logged In: YES user_id=43556 SELECT NULL is fixed. SELECT * FROM some_table WHERE bla IS NULL; works fine. ## Comment 518 Date: 2005-10-06 15:33:38 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: TEST ADDED / SUCCESS src/test/BugDay_2005-10-06_2.8/select_null.* ## Comment 519 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 920551 at http://sourceforge.net/support/tracker.php?aid=920551
select null impossible?
https://api.github.com/repos/MonetDB/MonetDB/issues/100/comments
0
2020-11-30T08:04:52Z
2024-06-27T10:54:45Z
https://github.com/MonetDB/MonetDB/issues/100
753,252,234
100
[ "MonetDB", "MonetDB" ]
Date: 2004-03-20 05:12:24 +0100 From: @drstmane To: Peter Boncz &lt;<boncz>&gt; Version: -- development Last updated: 2004-03-28 12:35:40 +0200 ## Comment 509 Date: 2004-03-20 17:12:24 +0100 From: @drstmane Since the changes on Thursday, March 18 2004, test tests/by_Peter/Tests/tst_mmap complains about "!WARNING: BATpropcheck: BAT aa was incorrectly marked sorted!". Haven't analyzed this any furtherm yet... ## Comment 510 Date: 2004-03-20 18:29:21 +0100 From: @njnes Logged In: YES user_id=43556 Seems the content of the bat got corrupt! Probably the wrong file got loaded/mmapped ## Comment 511 Date: 2004-03-24 19:33:40 +0100 From: @drstmane Logged In: YES user_id=572415 Peter recent changes seem to fix test tests/by_Peter/Tests/tst_mmap . Thanks! However, now test tests/by_Peter/Tests/tst_writestr fails as follows: 19:28:53 manegold@draco:~/Monet/4.3.16/MonetDB $ diff -c -I'^' /var/tmp/_4.3.16_PREFIX_MONET_GNU_32_d__/mTests/tests/by_Peter/tst_writestr.{stable,test}.out *** /var/tmp/_4.3.16_PREFIX_MONET_GNU_32_d__/mTests/tests/by_Peter/tst_writestr.stable.out 2004-03-18 15:51:03.000000000 +0100 --- /var/tmp/_4.3.16_PREFIX_MONET_GNU_32_d__/mTests/tests/by_Peter/tst_writestr.test.out 2004-03-24 19:18:48.000000000 +0100 *************** *** 50,75 **** ----------------------------------------- [ "theap.storage", "malloced" ] [ 1000000 ] ----------------------------------------- ! BAT: tmp_31 ! (str) (str) ----------------------------------------- [ "theap.storage", "private map" ] ! [ 1500000 ] ! ----------------------------------------- ! BAT: tmp_31 ! (str) (str) ! ----------------------------------------- ! [ "theap.storage", "private map" ] ! [ 2000000 ] ! ----------------------------------------- ! BAT: tmp_31 ! (str) (str) ! ----------------------------------------- ! [ "theap.storage", "private map" ] ! [ 2500000 ] ! 17:08:30 > ! 17:08:30 > Done. ! 17:08:30 > --- 47,61 ---- ----------------------------------------- [ "theap.storage", "malloced" ] [ 1000000 ] + !WARNING: BATpropcheck: BAT aa was incorrectly marked keyed! ----------------------------------------- ! t tmp_32 name ! str str type ----------------------------------------- [ "theap.storage", "private map" ] ! !ERROR: Mserver internal error, please restart. Please make sure your disk is not full. ! 19:18:48 > ! 19:18:48 > Done. ! 19:18:48 > 19:29:00 manegold@draco:~/Monet/4.3.16/MonetDB $ ## Comment 512 Date: 2004-03-28 00:35:40 +0100 From: @peterboncz Logged In: YES user_id=591107 this was caused by a heap leak that leaves a heap named X kying around, after the bat is deleted. then a new X.priv bat is craeted and at some point unloaded. There are then two files X (old) and X.priv (current), but the HEAPload gave X precedence. the leak was fixed, and also the way heapload treats .priv files (moving X.priv to X-es). see checkins in src/gdk from me on the 27th, 23:55 CET ## Comment 513 Date: 2005-10-06 15:28:48 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / REDUNDANT ## Comment 514 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 920100 at http://sourceforge.net/support/tracker.php?aid=920100
tst_mmap gives BATproperty error
https://api.github.com/repos/MonetDB/MonetDB/issues/99/comments
0
2020-11-30T08:04:49Z
2024-06-28T07:36:24Z
https://github.com/MonetDB/MonetDB/issues/99
753,252,198
99
[ "MonetDB", "MonetDB" ]
Date: 2004-03-19 04:20:49 +0100 From: @mlkersten To: @njnes Version: -- development Duplicates: #96 Last updated: 2010-05-04 11:14:56 +0200 ## Comment 506 Date: 2004-03-19 16:20:49 +0100 From: @mlkersten >create table z(w varchar(0)); >insert into z values('wrong'); >select * from z; w name varchar type 1 tuplecount 6 id [ "wrong" ] > What says the standard? In MySQL an empty string is inserted into the table, i.e. string is truncated. ## Comment 507 Date: 2005-10-06 15:28:06 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / DUPLICATE of 919542 ## Comment 508 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 919568 at http://sourceforge.net/support/tracker.php?aid=919568 Bug has invalid status, setting status to "NEW". Previous status was "DELETED". ## Comment 13980 Date: 2010-05-04 11:14:56 +0200 From: @grobian *** This bug has been marked as a duplicate of bug #96 ***
String length constraints
https://api.github.com/repos/MonetDB/MonetDB/issues/98/comments
0
2020-11-30T08:04:45Z
2024-06-28T07:36:23Z
https://github.com/MonetDB/MonetDB/issues/98
753,252,130
98
[ "MonetDB", "MonetDB" ]
Date: 2004-03-19 03:29:37 +0100 From: Giel &lt;<gieldn>&gt; To: @sjoerdmullender Version: -- development Last updated: 2004-03-22 02:21:10 +0100 ## Comment 501 Date: 2004-03-19 15:29:37 +0100 From: Giel &lt;<gieldn>&gt; The Python Mapi client doesn't handle the new \1\1 and \1\2 prompts well. This specifically manifests itself when commands are executed which return nothing, like assignments. I've made a new version which seems to work well. I've just sent it to Sjoerd for review. It's attached as well. ## Comment 502 Date: 2004-03-19 16:07:30 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 I commented on a few issues in private mail (before I saw this ;-). Apart from a few minor issues the new version seems to work. Giel, can you check the corrected file in? ## Comment 503 Date: 2004-03-22 14:21:10 +0100 From: @mlkersten Logged In: YES user_id=490798 Fixed, thanks to Giel ! ## Comment 504 Date: 2005-10-06 15:27:20 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / POSTPONED We should add tests for other (non-C and non-Java) versions of MapiClient.. ## Comment 505 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 919548 at http://sourceforge.net/support/tracker.php?aid=919548
Python Mapi client is out of date
https://api.github.com/repos/MonetDB/MonetDB/issues/97/comments
0
2020-11-30T08:04:42Z
2024-06-28T13:37:49Z
https://github.com/MonetDB/MonetDB/issues/97
753,252,098
97
[ "MonetDB", "MonetDB" ]
Date: 2004-03-19 03:19:14 +0100 From: @mlkersten To: @njnes Version: -- development Last updated: 2010-05-04 11:14:56 +0200 ## Comment 496 Date: 2004-03-19 15:19:14 +0100 From: @mlkersten >create table z(w varchar(0)); >insert into z values('wrong'); >select * from z; w name varchar type 1 tuplecount 6 id [ "wrong" ] > What says the standard? In MySQL an empty string is inserted into the table, i.e. string is truncated. ## Comment 497 Date: 2004-03-19 17:53:50 +0100 From: @grobian Logged In: YES user_id=963970 If you decide to be user-friendly here, and truncate, please fire a warning if you do so. ## Comment 498 Date: 2004-03-23 09:11:12 +0100 From: @njnes Logged In: YES user_id=43556 We now correctly require types to have a positive length/nr of digits etc Also we test if values match column types (ie lenght value <= length of type) ie the insert now gives a Error. This behaviour is inline with postgress. Mysql however does truncing and gives an error. ## Comment 499 Date: 2005-10-06 15:24:37 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: TEST ADDED / SUCCESS src/test/BugDay_2005-10-06_2.8/string_truncate.SF-919542.* ## Comment 500 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 919542 at http://sourceforge.net/support/tracker.php?aid=919542 ## Comment 13981 Date: 2010-05-04 11:14:56 +0200 From: @grobian *** Bug #98 has been marked as a duplicate of this bug. ***
String length constraints
https://api.github.com/repos/MonetDB/MonetDB/issues/96/comments
0
2020-11-30T08:04:39Z
2024-06-27T10:52:03Z
https://github.com/MonetDB/MonetDB/issues/96
753,252,057
96
[ "MonetDB", "MonetDB" ]
Date: 2004-03-19 03:17:36 +0100 From: @mlkersten To: @njnes Version: -- development Last updated: 2004-03-19 06:17:16 +0100 ## Comment 490 Date: 2004-03-19 15:17:36 +0100 From: @mlkersten >select 'a' 'a'; single_value name char type 1 tuplecount 4 id [ "aa" ] >select 'a' 'a'; single_value name char type 1 tuplecount 5 id [ "aa" ] In Mysql these statements work differently. The former interprets ' ' as an escaped quote and the second as a concatenation request. (semantics differ if there are characters between quotes. What is correct according to the standard) ## Comment 491 Date: 2004-03-19 15:25:20 +0100 From: @njnes Logged In: YES user_id=43556 both selects are the same so why expect different output. ## Comment 492 Date: 2004-03-19 17:44:41 +0100 From: @mlkersten Logged In: YES user_id=490798 On Fri, Mar 19, 2004 at 04:09:14PM +0100, Martin Kersten wrote: >> Maar wat zegt de standaard over <quote><quote>? >> is dat een escaped quote? Inderdaad is '' een escaped quote. Ik zal eens kijken of ik mijn string scanning nog trager kan krijgen. Niels >> >> Niels Nes wrote: >> > >>> >On Fri, Mar 19, 2004 at 03:26:26PM +0100, Martin Kersten wrote: >>> > >> >>>> >> >>> >>>>>> >>>>Comment By: Niels Nes (nielsnes) >>> >>>> >> >>>> >>Date: 2004-03-19 14:25 >>>> >> >>>> >>Message: >>>> >>Logged In: YES >>>> >>user_id=43556 >>>> >> >>>> >>both selects are the same so why expect different output. >>>> >> >>>> >>Niels, >>>> >>dat zijn ze niet. Het verschil is of je tussen >>>> >>de 'a' en 'a' een spatie opvoert. >>>> >>Dit levert in MySQL twee verschillende resultaten >>>> >>op, omdat de <quote><quote> wordt gezien als een >>>> >>escaped <qoute> en <quote><space><quote> als >>>> >>een string concatenatie. >>>> >> >>>> >>Wat zegt de standaard. >> >>> > >>> >De standaard zegt space is een seperator, ie >>> >bla bla == bla bla >>> > >>> >Dus dit is een bug in MySQL! >>> > >>> >Niels ## Comment 493 Date: 2004-03-19 18:17:16 +0100 From: @njnes Logged In: YES user_id=43556 both selects are the same so why expect different output. ## Comment 494 Date: 2005-10-06 15:13:10 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: TEST ADDED src/test/BugDay_2005-10-06_2.8/string_quotes.SF-919539.* ## Comment 495 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 919539 at http://sourceforge.net/support/tracker.php?aid=919539
Concatenate string input error
https://api.github.com/repos/MonetDB/MonetDB/issues/95/comments
0
2020-11-30T08:04:36Z
2024-06-28T13:37:48Z
https://github.com/MonetDB/MonetDB/issues/95
753,251,997
95
[ "MonetDB", "MonetDB" ]
Date: 2004-03-19 03:14:16 +0100 From: @mlkersten To: @mlkersten Version: -- development Last updated: 2004-03-26 11:43:38 +0100 ## Comment 484 Date: 2004-03-19 15:14:16 +0100 From: @mlkersten Using the 'latest' Monet for Windows. After closing the SQL client (cntrl-C or close window) and issueing a 'quit' in the server console, the latter hangs indefinitely. A following cntrl-c generated the 'recognition' message of an interrupt, but did not close the server. It has to killed with window-close followed by acceptance of the Windows request to terminate the process ## Comment 485 Date: 2004-03-23 14:39:31 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Works for me. Can you recheck? ## Comment 486 Date: 2004-03-26 15:11:02 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Assigned to Martin because this is waiting for an answer from him. ## Comment 487 Date: 2004-03-26 23:43:38 +0100 From: @mlkersten Logged In: YES user_id=490798 Problem disappeared with latest Windows installer ## Comment 488 Date: 2005-10-06 15:06:47 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / POSTPONED I don't know how to test this since this requires interactivity. ## Comment 489 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 919536 at http://sourceforge.net/support/tracker.php?aid=919536
Hanging processes
https://api.github.com/repos/MonetDB/MonetDB/issues/94/comments
0
2020-11-30T08:04:32Z
2024-06-27T10:52:01Z
https://github.com/MonetDB/MonetDB/issues/94
753,251,953
94
[ "MonetDB", "MonetDB" ]
Date: 2004-03-19 03:05:34 +0100 From: @mlkersten To: @njnes Version: -- development Last updated: 2004-03-23 09:08:55 +0100 ## Comment 480 Date: 2004-03-19 15:05:34 +0100 From: @mlkersten >create table t(i int); >insert into t values(null); >select * from t; i name int type 1 tuplecount 0 id [ nil ] Confusing use for the user. We should remap the nil ->null in the SQL setting. Ideally this should be done in the new ascii-io (tablet.mx) or temporarily in the mapi interfaces. ## Comment 481 Date: 2004-03-22 14:27:48 +0100 From: @mlkersten Logged In: YES user_id=490798 str("nil") could produce 'nil', which is confusing ## Comment 482 Date: 2005-10-06 15:04:20 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: TEST ADDED / SUCCESS src/test/BugDay_2005-10-06_2.8/nil_null.SF-919528.* ## Comment 483 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 919528 at http://sourceforge.net/support/tracker.php?aid=919528
SQL null <-> behavior
https://api.github.com/repos/MonetDB/MonetDB/issues/93/comments
0
2020-11-30T08:04:29Z
2024-06-27T10:51:59Z
https://github.com/MonetDB/MonetDB/issues/93
753,251,904
93
[ "MonetDB", "MonetDB" ]
Date: 2004-03-19 03:00:19 +0100 From: @mlkersten To: @njnes Version: -- development Last updated: 2004-03-19 10:00:27 +0100 ## Comment 476 Date: 2004-03-19 15:00:19 +0100 From: @mlkersten create table t(i int, s varchar); create table s(j int); select * from t cross join s; Crashes the server! ## Comment 477 Date: 2004-03-19 15:03:33 +0100 From: @mlkersten Logged In: YES user_id=490798 Monet Database Server V4.3.16_rc05 Copyright (c) 1993-2004, CWI. All rights reserved. compiled for i686-pc-linux-gnu/32bit; dynamically linked. monet>module(sql_server); monet>Mserver: /ufs/mk/opensource/sql/src/server/sql_mem.mx:93: sql_ref_dec: Assertion `r->refcnt > 0' failed. Aborted ## Comment 478 Date: 2005-10-06 14:52:38 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: TEST ADDED / SUCCESS src/test/BugDay_2005-10-06_2.8/cross_join-SF.919524.* ## Comment 479 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 919524 at http://sourceforge.net/support/tracker.php?aid=919524
SQL cross join crashes server
https://api.github.com/repos/MonetDB/MonetDB/issues/92/comments
0
2020-11-30T08:04:25Z
2024-06-27T10:51:58Z
https://github.com/MonetDB/MonetDB/issues/92
753,251,872
92
[ "MonetDB", "MonetDB" ]
Date: 2004-03-17 04:31:41 +0100 From: @mlkersten To: @njnes Version: -- development Last updated: 2004-03-23 09:02:17 +0100 ## Comment 472 Date: 2004-03-17 16:31:41 +0100 From: @mlkersten The following query (inspired by a discussion with Seidl) does not work create table tmp(i int); select i from tmp union select i from tmp; ## Comment 473 Date: 2004-03-23 09:02:17 +0100 From: @njnes Logged In: YES user_id=43556 UNION is added (more SQL features are feature requests ;-) ## Comment 474 Date: 2005-10-06 14:49:10 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: TEST ADDED / SUCCESS src/test/BugDay_2005-10-06_2.8/union-SF.918078.* ## Comment 475 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 918078 at http://sourceforge.net/support/tracker.php?aid=918078
Core SQL language
https://api.github.com/repos/MonetDB/MonetDB/issues/91/comments
0
2020-11-30T08:04:22Z
2024-06-27T10:51:57Z
https://github.com/MonetDB/MonetDB/issues/91
753,251,823
91
[ "MonetDB", "MonetDB" ]
Date: 2004-03-16 08:19:49 +0100 From: @njnes To: Peter Boncz &lt;<boncz>&gt; Version: -- development Last updated: 2004-03-17 05:09:51 +0100 ## Comment 468 Date: 2004-03-16 20:19:49 +0100 From: @njnes type conversions should fail instead of returning a nil value. Example sht("a"); now return nil but should simply give an error. ## Comment 469 Date: 2004-03-17 17:09:51 +0100 From: @peterboncz Logged In: YES user_id=591107 First, this is a feature request. If it is up to me, I would deny the request. Mostly because it is a matter of taste. It is pretty easy to check whether a conversion succeeds (isnil(src) || not(isnil(dst))). giving an error also has drawbacks (i.e. interrupts interpreting) sometimes, you just *have* to convert something and produce a result. In that case, a nil is a good way out. ## Comment 470 Date: 2005-10-06 14:44:32 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / REDUNDANT already tested in src/gdk/Tests/casts.* ## Comment 471 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 917526 at http://sourceforge.net/support/tracker.php?aid=917526
conversions should fail instead of return nil
https://api.github.com/repos/MonetDB/MonetDB/issues/90/comments
0
2020-11-30T08:04:19Z
2024-06-28T13:37:47Z
https://github.com/MonetDB/MonetDB/issues/90
753,251,790
90
[ "MonetDB", "MonetDB" ]
Date: 2004-03-16 04:47:14 +0100 From: @mlkersten To: Peter Boncz &lt;<boncz>&gt; Version: -- development Last updated: 2004-03-16 08:20:54 +0100 ## Comment 464 Date: 2004-03-16 16:47:14 +0100 From: @mlkersten On both Windows and Linux select 'a'+1; produces a nil and should have produced a type error select 1-'a' produces garbage on windows and a nil on linux followed by a server crash select true+1; crashes the server ## Comment 465 Date: 2004-03-16 20:16:47 +0100 From: @njnes Logged In: YES user_id=43556 sql crash is fixed. 1+'string' is correct sql (implicit cast of string to number). Problem is conversion of string to int/sht results in nil instead of error. sht("a");=> nil ## Comment 466 Date: 2005-10-06 14:40:43 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: TEST ADDED / SUCCESS src/test/BugDay_2005-10-06_2.8/mixed_type.SF-917372.* ## Comment 467 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 917372 at http://sourceforge.net/support/tracker.php?aid=917372
Elementary type errors crash server
https://api.github.com/repos/MonetDB/MonetDB/issues/89/comments
0
2020-11-30T08:04:16Z
2024-06-27T10:51:55Z
https://github.com/MonetDB/MonetDB/issues/89
753,251,751
89
[ "MonetDB", "MonetDB" ]
Date: 2004-03-16 12:58:13 +0100 From: Giel &lt;<gieldn>&gt; To: @njnes Version: -- development Last updated: 2004-03-16 01:51:08 +0100 ## Comment 459 Date: 2004-03-16 12:58:13 +0100 From: Giel &lt;<gieldn>&gt; After executing a printf statement which doesn't print a newline from within MapiClient doesn't give any result and makes the client unresponsive for any command. ## Comment 460 Date: 2004-03-16 13:51:08 +0100 From: @njnes Logged In: YES user_id=43556 bad news this is a feature of the line mode! ## Comment 461 Date: 2004-03-16 14:07:22 +0100 From: @mlkersten Logged In: YES user_id=490798 (Un)Fortunately this is a feature in the current Mapi.java environment. It may be more easier to solve in the new Mapi.mx, but probably at a high cost, because you have to flush in principle any character print ## Comment 462 Date: 2005-10-06 14:35:40 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / NOTABUG ## Comment 463 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 917258 at http://sourceforge.net/support/tracker.php?aid=917258
printf without newline locks MapiClient
https://api.github.com/repos/MonetDB/MonetDB/issues/88/comments
0
2020-11-30T08:04:13Z
2024-06-28T13:37:47Z
https://github.com/MonetDB/MonetDB/issues/88
753,251,712
88
[ "MonetDB", "MonetDB" ]
Date: 2004-03-16 12:55:12 +0100 From: @njnes To: Peter Boncz &lt;<boncz>&gt; Version: -- development Last updated: 2004-04-08 03:28:35 +0200 ## Comment 453 Date: 2004-03-16 12:55:12 +0100 From: @njnes Semijoin is still inconsistent with respect to nils. With other operators such as join nil != nil. Mil file to test nil problem is attached. ## Comment 454 Date: 2004-03-22 14:30:13 +0100 From: @mlkersten Logged In: YES user_id=490798 Consistency is of utmost importance. It should be solved as quickly as possible ## Comment 455 Date: 2004-03-24 23:05:24 +0100 From: @drstmane Logged In: YES user_id=572415 made some of our semijoin algorithms (binsemijoin, idxsemijoin, revsemijoin) "nil-aware", i.e., nil does no lnoger match with nil. unfortunately, this requires some more checks ("if"s) in loops... still to do: the default case of [sk]intersect! extended the semijoin test to force usage of different algorithms. ## Comment 456 Date: 2004-04-08 15:28:35 +0200 From: @drstmane Logged In: YES user_id=572415 Peter maded intersect and diff nil-aware. ## Comment 457 Date: 2005-10-06 14:32:57 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: ALREADY IN TESTWEB src/gdk/Tests/semijoin.* ## Comment 458 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 917255 at http://sourceforge.net/support/tracker.php?aid=917255
semijoin nil == nil
https://api.github.com/repos/MonetDB/MonetDB/issues/87/comments
0
2020-11-30T08:04:10Z
2024-06-27T10:51:53Z
https://github.com/MonetDB/MonetDB/issues/87
753,251,669
87
[ "MonetDB", "MonetDB" ]
Date: 2004-03-15 04:34:40 +0100 From: @swingbit To: GDK devs &lt;<bugs-common>&gt; Version: -- development Last updated: 2004-03-15 07:56:27 +0100 ## Comment 446 Date: 2004-03-15 16:34:40 +0100 From: @swingbit integers from -25 to 24 var a := bat(void, int,50).seqbase(0@0).rename("a"); var i := -25; while(i < 25) a.insert(nil, (i :+= 1)); reverse sort and split into 2 chunks a := a.sort_rev.reverse.mark(0@0).reverse; VAR sliced := a.rangesplit(2); sliced.fetch(0).print; sliced.fetch(1).print; If you look at the two chunks, they are mixed up. If original values aren't ordered (but still negative and positive) is even worse... ## Comment 447 Date: 2004-03-15 17:22:33 +0100 From: @drstmane Logged In: YES user_id=572415 I just added a respective test-script (took just 5 minutes ;-). IMHO the output (cf. tests/BugsViaSourgeforce/Tests/ID.916699.stable.out) is correct. Roberto, what do you mean by "mixed up"? ## Comment 448 Date: 2004-03-15 18:57:37 +0100 From: @swingbit Logged In: YES user_id=883451 I would expect the result of sliced.fetch(0).print; and sliced.fetch(1).print; to be swapped! Why the first chunk of tuples is in the first bat and the second chunk is in the first bat? What's strange is that it seems to be related to the values. Even worse with this: var a := bat(void, int,50).seqbase(0@0).rename("a"); var i := -25; while(i < 25) { a.insert(nil, i); i :+= 1; }; ugly way to shuffle a little bit var b:=new(void, int).seqbase(0@0).insert(a.sample(10)).insert(a.sample(10)).insert(a.sample(10)).insert(a.sample(10)).insert(a.sample(10)); b:=b.reverse.mark(0@0).reverse; sliced.fetch(0).print; sliced.fetch(1).print; Now, you will get negative numbers in the first chunk! There's something that looks at the tail values.... ## Comment 449 Date: 2004-03-15 19:35:47 +0100 From: @drstmane Logged In: YES user_id=572415 Well, what you get is the lower range in the first bat (sliced.fetch(0)) and the higer range in the second bat (sliced.fetch(1)). That's just what rangesplit is supposed to do. Yes, it is of course related to the values, that's way it is called "rangesplit" and not "slice" ;-) Yes, if you split a dense range of 50 values from -24 to 25 in two ranges, you get one with 25 negative numbers (-24,...,-1,0) and one with 25 positive numbers (1,...,25) ;-) Yes, something looks at the tail, and that "something" is called "rangesplit" ;-) monet>help("rangesplit"); COMMAND: rangesplit(BAT[any::1,any::2], int) : BAT[any::2,BAT] MODULE: algebra COMPILED: by adm on Sat Mar 13 15:13:58 2004 Split a BAT on *tail* column in 'ranges' equally sized consecutive ranges. Returns a recursive BAT, containing the fragments in the tail, the higher-bound of the range in the head. The higher bound of the last range is 'nil'. monet> Does this convince you? ;-) If so, you may close (reject?) this "bug report" yourself. ;-) ## Comment 450 Date: 2004-03-15 19:56:27 +0100 From: @swingbit Logged In: YES user_id=883451 > Yes, it is of course related to the values, that's way it is called "rangesplit" and not "slice" ;-) I see... :)) Well, I have to admit that looking at the help "equally sized consecutive ranges" triggered my attention more than "on tail". So, yes, I really thought that was a different function that it actually is. I'm closing (rejecting) this bug report (a right bug report on a non-existing functionality) my self ;-) ## Comment 451 Date: 2005-10-06 14:30:00 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: ALREADY IN TESTWEB tests/BugsViaSourgeforce/Tests/ID.916699.* ## Comment 452 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 916699 at http://sourceforge.net/support/tracker.php?aid=916699 The original assignee of this bug does not have an account here. Reassigning to the default assignee for the component, bugs-common@monetdb.org. Previous assignee was nobody@users.sourceforge.net.
rangesplit mixes rows...
https://api.github.com/repos/MonetDB/MonetDB/issues/86/comments
0
2020-11-30T08:04:07Z
2024-06-28T13:37:46Z
https://github.com/MonetDB/MonetDB/issues/86
753,251,640
86
[ "MonetDB", "MonetDB" ]
Date: 2004-03-15 03:32:32 +0100 From: Alex van Ballegooij &lt;<bally>&gt; To: Stefan Manegold &lt;<Stefan.Manegold>&gt; Version: -- development Duplicates: #84 Last updated: 2010-05-04 11:11:56 +0200 ## Comment 442 Date: 2004-03-15 15:32:32 +0100 From: Alex van Ballegooij &lt;<bally>&gt; ->print(bat(void,int).seqbase(0@0).insert(nil,1)); ----------------- h tmp_33 name void int type ----------------- [ 0@0, 1 ] ->table(bat(void,int).seqbase(0@0).insert(nil,1)); --------- tmp_33 name --------- [ 1 ] Note that column types are *not* displayed by the table command. External tools (e.g. Mknife) may depend on such meta-data. ## Comment 443 Date: 2004-03-15 16:49:43 +0100 From: @drstmane Logged In: YES user_id=572415 deleted duplicate entry ## Comment 444 Date: 2005-10-06 14:28:35 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / DUPLICATE of 916648. ## Comment 445 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 916660 at http://sourceforge.net/support/tracker.php?aid=916660 Bug has invalid status, setting status to "NEW". Previous status was "DELETED". ## Comment 13974 Date: 2010-05-04 11:11:56 +0200 From: @grobian *** This bug has been marked as a duplicate of bug #84 ***
Table header from
https://api.github.com/repos/MonetDB/MonetDB/issues/85/comments
0
2020-11-30T08:04:04Z
2024-06-28T13:37:45Z
https://github.com/MonetDB/MonetDB/issues/85
753,251,598
85
[ "MonetDB", "MonetDB" ]
Date: 2004-03-15 03:18:34 +0100 From: Alex van Ballegooij &lt;<bally>&gt; To: @njnes Version: -- development Last updated: 2010-05-04 11:11:56 +0200 ## Comment 432 Date: 2004-03-15 15:18:34 +0100 From: Alex van Ballegooij &lt;<bally>&gt; ->print(bat(void,int).seqbase(0@0).insert(nil,1)); ----------------- h tmp_33 name void int type ----------------- [ 0@0, 1 ] ->table(bat(void,int).seqbase(0@0).insert(nil,1)); --------- tmp_33 name --------- [ 1 ] Note that column types are *not* displayed by the table command. External tools (e.g. Mknife) may depend on such meta-data. ## Comment 433 Date: 2004-03-16 13:02:51 +0100 From: @njnes Logged In: YES user_id=43556 Could be simply fixed by using the 'printhead' argument (FALSE->TRUE). Any body objects to this simple change, ie. was there a reason why table don't print the header! ## Comment 434 Date: 2004-03-16 13:13:20 +0100 From: @njnes Logged In: YES user_id=43556 Wrong remark!! The printhead if afcouse the there to enable/disable head column printing. Anyway based on having this head column the 'types' are printed or not. ## Comment 435 Date: 2004-03-16 13:49:42 +0100 From: @njnes Logged In: YES user_id=43556 Wrong remark!! The printhead if afcouse the there to enable/disable head column printing. Anyway based on having this head column the 'types' are printed or not. ## Comment 436 Date: 2004-03-16 14:03:21 +0100 From: @mlkersten Logged In: YES user_id=490798 Indeed. Mknife should receive the type information Now many MILinfo command cast it to string. I am in favor. ## Comment 437 Date: 2004-03-17 13:39:48 +0100 From: Alex van Ballegooij &lt;<bally>&gt; Logged In: YES user_id=594789 I have no clue why "table" does not print the types while it does print the rest of the header (ascii-art and column names). So i do not think it is a matter of enabling/disabling header output: the header IS there in the output from "table", it's just incomplete. I assume that this is because type information has been added to the "print" command relatively recently and this change has simply not been propagated to the table command. But I could be wrong. In any case, currently the workaround is to output tables (sets of aligned void bats) with "print", this does work but generates quite a bit of overhead by explicitly inlcuding the (useless) void column in the output. ## Comment 438 Date: 2004-03-17 13:55:49 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 When I try it now with the current RC branch I get this. Where is the problem? monet>print(bat(void,int).seqbase(0@0).insert(nil,1)); ----------------- h tmp_29 name void int type ----------------- [ 0@0, 1 ] monet>table(bat(void,int).seqbase(0@0).insert(nil,1)); --------- tmp_29 name int type --------- [ 1 ] ## Comment 439 Date: 2004-03-17 14:25:48 +0100 From: Alex van Ballegooij &lt;<bally>&gt; Logged In: YES user_id=594789 *checking*,... You're right, must be fixed then. ## Comment 440 Date: 2005-10-06 14:27:54 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: TEST ADDED / SUCCESS tests/BugDay_2005-10-06_4.8/table_type.SF-916648.* ## Comment 441 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 916648 at http://sourceforge.net/support/tracker.php?aid=916648 ## Comment 13975 Date: 2010-05-04 11:11:56 +0200 From: @grobian *** Bug #85 has been marked as a duplicate of this bug. ***
Table header from
https://api.github.com/repos/MonetDB/MonetDB/issues/84/comments
0
2020-11-30T08:04:01Z
2024-06-27T10:51:50Z
https://github.com/MonetDB/MonetDB/issues/84
753,251,554
84
[ "MonetDB", "MonetDB" ]
Date: 2004-03-15 01:10:56 +0100 From: @sjoerdmullender To: @sjoerdmullender Version: -- development Last updated: 2004-03-15 01:28:53 +0100 ## Comment 428 Date: 2004-03-15 13:10:56 +0100 From: @sjoerdmullender When compiled on Windows with VC .NET, the following simple script hangs: commit; commit; ## Comment 429 Date: 2004-03-15 13:28:53 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 It was mostly Peter who figured this out. Three bugs conspired together to cause the hang. The first bug is that TMcommit called BBPlock, but didn't always call BBPunlock. In particular, if the call to BBPsync failed, the unlock was skipped. This resulted in a second call to TMcommit hanging. The second bug is that BBPsync in certain circumstances returned failure, even though the essential part of the operation, the renaming of BAKDIR to DELDIR, succeeded. In particular, if removing DELDIR failed, or if creating a new BAKDIR failed, or if moving BBP.dir from BATDIR to BAKDIR failed, BBPsync would return failure. None of those later failures is serious. The third bug, which triggered the above bugs, is that aparently in Visual Studio .NET it is a failure if rmdir and mkdir are called with a path that ends in \. ## Comment 430 Date: 2005-10-06 14:16:42 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: TEST ADDED / SUCCESS src/test/BugDay_2005-10-06_2.8/Tests/Attic/double_commit.* ## Comment 431 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 916584 at http://sourceforge.net/support/tracker.php?aid=916584
tests hang on Windows with VC .NET
https://api.github.com/repos/MonetDB/MonetDB/issues/83/comments
0
2020-11-30T08:03:58Z
2024-06-27T10:51:49Z
https://github.com/MonetDB/MonetDB/issues/83
753,251,503
83
[ "MonetDB", "MonetDB" ]
Date: 2004-03-14 03:21:26 +0100 From: @drstmane To: @sjoerdmullender Version: -- development Last updated: 2004-03-15 02:09:57 +0100 ## Comment 424 Date: 2004-03-14 15:21:26 +0100 From: @drstmane Apparently, the new MAPI (both with MIL & SQL) has the following BUG: When an error occurs in a statement that follows a (sequence of) comment- or empty-lines, the "QUERY" given in the error message is the first on the comment-/empty-lines instead of the actual statement that failed. See MonetDB test src/monet/Tests/modrefcnt2-is in Current testing later today: http://monetdb.cwi.nl/TestWeb/Current/MonetDB/MonetDB/.mTests103/GNU_32-d_Linux2.4.20-20.9perfctrsmp/src_monet/modrefcnt2-is.err.00.html or in Stable testing tomorrow morning: http://monetdb.cwi.nl/TestWeb/Stable/MonetDB/MonetDB/.mTests103/GNU_32-d_Linux2.4.20-20.9perfctrsmp/src_monet/modrefcnt2-is.err.00.html Also, see SQL tests src/tests/Tests/{decimal,marcin2,marcin3} in Stable testing tomorrow morning: http://monetdb.cwi.nl/TestWeb/Stable/sql/sql/.mTests103/GNU_32-d_Linux2.4.20-20.9perfctrsmp/src_test/decimal.err.00.html http://monetdb.cwi.nl/TestWeb/Stable/sql/sql/.mTests103/GNU_32-d_Linux2.4.20-20.9perfctrsmp/src_test/marcin2.err.00.html http://monetdb.cwi.nl/TestWeb/Stable/sql/sql/.mTests103/GNU_32-d_Linux2.4.20-20.9perfctrsmp/src_test/marcin3.err.00.html ## Comment 425 Date: 2004-03-15 14:09:57 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 This is the result of the desire to limit the number of reallocs done in the code. The MAPI library only remembers the argument to the first call of a sequence of mapi_qery_part calls (and only up to 512 bytes of that argument). The server wants one complete query, so prompted for more after it saw just a comment. The fix is to not ask for more (PROMPT2) after a comment, but to "execute" the comment and ask for a new query (PROMPT1). This was a 1 bit(!) change. ## Comment 426 Date: 2005-10-06 14:10:20 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / REDUNDANT See the tests mentioned in the report. ## Comment 427 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 916033 at http://sourceforge.net/support/tracker.php?aid=916033
Wrong "QUERY=" in MAPI error messages
https://api.github.com/repos/MonetDB/MonetDB/issues/82/comments
0
2020-11-30T08:03:55Z
2024-06-27T10:51:48Z
https://github.com/MonetDB/MonetDB/issues/82
753,251,482
82
[ "MonetDB", "MonetDB" ]
Date: 2004-03-13 08:44:38 +0100 From: @mlkersten To: GDK devs &lt;<bugs-common>&gt; Version: -- development Duplicates: #78 Last updated: 2010-05-04 10:54:25 +0200 ## Comment 420 Date: 2004-03-13 08:44:38 +0100 From: @mlkersten c:= new(int,int,-5000); !ERROR: Mserver internal error, please restart. Please make sure your disk is not full. This behaves like a FATAL error instead of ERROR (which would permit continuation) ## Comment 421 Date: 2004-03-13 09:23:44 +0100 From: @mlkersten Logged In: YES user_id=490798 Accidental duplicate entry. ## Comment 422 Date: 2005-10-06 13:57:02 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: DUPLICATE of 915339. ## Comment 423 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 915480 at http://sourceforge.net/support/tracker.php?aid=915480 The original assignee of this bug does not have an account here. Reassigning to the default assignee for the component, bugs-common@monetdb.org. Previous assignee was nobody@users.sourceforge.net. Bug has invalid status, setting status to "NEW". Previous status was "DELETED". ## Comment 13968 Date: 2010-05-04 10:54:25 +0200 From: @grobian *** This bug has been marked as a duplicate of bug #78 ***
Internal error
https://api.github.com/repos/MonetDB/MonetDB/issues/81/comments
0
2020-11-30T08:03:51Z
2024-06-28T13:37:45Z
https://github.com/MonetDB/MonetDB/issues/81
753,251,440
81
[ "MonetDB", "MonetDB" ]
Date: 2004-03-13 07:48:25 +0100 From: @drstmane To: Menzo Windhouwer &lt;<windhouw>&gt; Version: -- development Last updated: 2004-03-17 05:10:34 +0100 ## Comment 412 Date: 2004-03-13 07:48:25 +0100 From: @drstmane While it seems to work fine with Java-1.3, handling/printing of utf-8 characters seem to be broken with Java-1.4 --- or vice versa, but the tests currectly fail with Java-1.4. cf. http://monetdb.cwi.nl/TestWeb/Stable/MonetDB/MonetDB/.mTests103/GNU_32-d_Linux2.4.20-20.9perfctrsmp/src_mapi/utf_8_JAVA.out.00.html Menzo, I assigned this to you since you added the respective test; of course, you may forward this report, in case you think someone else has to take care instead ;-) ## Comment 413 Date: 2004-03-15 11:42:55 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 My guess is, this is a problem with the LANG et al. environment settings. ## Comment 414 Date: 2004-03-15 13:08:48 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 To elaborate on my previous remark, what I think is happening (without actually havng checked any of this :-) is the following: Remember that Java is fully Unicode-aware. The Java MAPI library (correctly) sets the socket connection with the server to be in UTF-8 mode. The data transferred to and from the server is thus correct. The data that comes back from the server is printed to standard output (either file or terminal, depending on the way the client was called). The mode of the standard output is determined by the settings of the LANG and various LC_* environment variables. When running interactively (even if running RunMtest/make check) these settings are usually some UTF-8-aware locale, but when run from the test script (or on spin which sets LANG=C) they are not, and so the Java runtime engine translates the original UTF-8 sequence to Latin-1 upon output. In other words, the Java engine does the right thing. The only thing wrong (I think) is the environment which should set the LANG environment variable. I assign this to Stefan since I think it's a testing issue. ## Comment 415 Date: 2004-03-15 15:07:34 +0100 From: @menzowindhouwer Logged In: YES user_id=572977 The LANG variable in my Fedora Core 1 installation is set to "en_US.UTF-8". However, this doesn't seem to effect the encoding of Java's System.out ... it stays 8859-1. Hence, my fix with hardcoding (for MapiClient) the desired UTF-8 encoding. ## Comment 416 Date: 2004-03-15 19:31:04 +0100 From: @menzowindhouwer Logged In: YES user_id=572977 A very small sample program shows that System.out indeed responds to the setting of LANG. Howerver, at the moment I've been able to reproduce this behaviour in Mapi(Client) ... ## Comment 417 Date: 2004-03-17 17:10:34 +0100 From: @drstmane Logged In: YES user_id=572415 Fixed by Menzo: - fixed code - use of proper LANGuage/LOCALE settings ## Comment 418 Date: 2005-10-06 13:55:50 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: ALREADY IN TESTWEB src/mapi/Tests/utf_8_JAVA.* ## Comment 419 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 915469 at http://sourceforge.net/support/tracker.php?aid=915469
utf-8 handling/printing broken with Java-1.4
https://api.github.com/repos/MonetDB/MonetDB/issues/80/comments
0
2020-11-30T08:03:48Z
2024-06-27T10:51:46Z
https://github.com/MonetDB/MonetDB/issues/80
753,251,413
80
[ "MonetDB", "MonetDB" ]
Date: 2004-03-13 07:33:46 +0100 From: @drstmane To: @njnes Version: -- development Last updated: 2004-03-13 12:46:11 +0100 ## Comment 408 Date: 2004-03-13 07:33:46 +0100 From: @drstmane On all 64bit Linux variants that we test, "rangespilt(b,1);" fails as follows: print(rangesplit(b,1)); !WARNING: rangesplit: delivering 0 instead of 1 fragments !ERROR: Mserver internal error, please restart. Please make sure your disk is not full. cf. test tests/BugsViaSourgeforce/Tests/ID.914935, e.g., http://monetdb.cwi.nl/TestWeb/Stable/MonetDB/MonetDB/.mTests103/GNU_64-d_Linux2.4.18-e.25smp/tests_BugsViaSourgeforce/ID.914935.out.00.html Since I added this test only yesterday, I do not know, whether this problem is new or old. ## Comment 409 Date: 2004-03-13 09:44:27 +0100 From: @drstmane Logged In: YES user_id=572415 Assigned to Peter, as he's not subscribed to the monetdb-bugs list ;-) Maybe someone has an idea, what might be wrong; otherwise I'll have a look next week. ## Comment 410 Date: 2005-10-06 13:52:15 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: ALREADY IN TESTWEB / REDUNDANT tests/BugsViaSourgeforce/Tests/ID.914935.* ## Comment 411 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 915462 at http://sourceforge.net/support/tracker.php?aid=915462
rangespilt(b,1); fails on 64-bit Linux
https://api.github.com/repos/MonetDB/MonetDB/issues/79/comments
0
2020-11-30T08:03:46Z
2024-06-27T10:51:45Z
https://github.com/MonetDB/MonetDB/issues/79
753,251,361
79
[ "MonetDB", "MonetDB" ]
Date: 2004-03-12 11:59:24 +0100 From: @mlkersten To: @njnes Version: -- development Last updated: 2010-05-04 10:54:25 +0200 ## Comment 403 Date: 2004-03-12 23:59:24 +0100 From: @mlkersten c:= new(int,int,-5000); !ERROR: Mserver internal error, please restart. Please make sure your disk is not full. This behaves like a FATAL error instead of ERROR (which would permit continuation) ## Comment 404 Date: 2004-03-13 00:17:32 +0100 From: @drstmane Logged In: YES user_id=572415 AFAIR, this is Peter's solution to BUG #911326: "Bus error on full disk"; see also http://cvs.sourceforge.net/viewcvs.py/monetdb/MonetDB/src/gdk/gdk_utils.mxrev1.88 http://cvs.sourceforge.net/viewcvs.py/monetdb/MonetDB/src/gdk/gdk_utils.mx?r1=1.87&r2=1.88 and http://monetdb.cwi.nl/TestWeb/Stable/MonetDB/MonetDB/.mTests103/GNU_32-d_Linux2.4.20-20.9perfctrsmp/tests_BugsViaSourgeforce/ID.914159.out.00.html ## Comment 405 Date: 2004-03-13 10:14:59 +0100 From: @njnes Logged In: YES user_id=43556 -50000 is wrongly cast to size_t giving a almost 4gb bat! Fix awaiting testing ## Comment 406 Date: 2005-10-06 13:50:13 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: TEST ADDED / SUCCESS tests/BugDay_2005-10-06_4.8/negative_size.SF-915339.* ## Comment 407 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 915339 at http://sourceforge.net/support/tracker.php?aid=915339 ## Comment 13969 Date: 2010-05-04 10:54:25 +0200 From: @grobian *** Bug #81 has been marked as a duplicate of this bug. ***
Internal error
https://api.github.com/repos/MonetDB/MonetDB/issues/78/comments
0
2020-11-30T08:03:43Z
2024-06-27T10:51:44Z
https://github.com/MonetDB/MonetDB/issues/78
753,251,320
78
[ "MonetDB", "MonetDB" ]
Date: 2004-03-12 04:13:58 +0100 From: @menzowindhouwer To: Stefan Manegold &lt;<Stefan.Manegold>&gt; Version: -- development Last updated: 2004-03-12 05:19:44 +0100 ## Comment 398 Date: 2004-03-12 16:13:58 +0100 From: @menzowindhouwer CVS checkin mails for some parts of the xml CVS module get the wrong subject, i.e. [Monetdb-checkins] instead of [Monetdb-xml-checkins] The parts of the xml CVS module infected by this contain MonetDB in their path, i.e. xm/src/saxophone/java/MonetDB/... ## Comment 399 Date: 2004-03-12 16:23:58 +0100 From: @drstmane Logged In: YES user_id=572415 This is most probably caused by the fact that cvs does substring reg.exp. matching in loginfo. I guess, we could fix it by preceeding all line in commitinfo with "^" to alway match the beginning of a sting and hence the directory(-path). Haven't tried it, yet ... ## Comment 400 Date: 2004-03-12 17:19:44 +0100 From: @drstmane Logged In: YES user_id=572415 Ensured that cvs matches modules in loginfo on prefixes by preceeding all module names (i.e., reg.exp.) by '^'. ## Comment 401 Date: 2005-10-06 13:45:28 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / CVS REPOSITORY ## Comment 402 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 915049 at http://sourceforge.net/support/tracker.php?aid=915049
CVS checkin mails get wrong subject
https://api.github.com/repos/MonetDB/MonetDB/issues/77/comments
0
2020-11-30T08:03:40Z
2024-06-27T10:51:43Z
https://github.com/MonetDB/MonetDB/issues/77
753,251,288
77
[ "MonetDB", "MonetDB" ]
Date: 2004-03-12 02:49:03 +0100 From: @MarcinZukowski To: Peter Boncz &lt;<boncz>&gt; Version: -- development Last updated: 2004-03-18 08:30:52 +0100 ## Comment 392 Date: 2004-03-12 14:49:03 +0100 From: @MarcinZukowski While loading TPCH data the following assertion triggered: Mserver: /ufs/marcin/monet/MonetDB/Linux/../src/gdk/gdk_bat.mx: 1377: make_readonly: Assertion `p' failed. To repeat the bug, do the following: - create tpch data with SF-1 - run tpch.mil (attached) Interestingly, it only happens when trying to load lots of data from lineitem. On my machine, when I changed 6001215 to 4000000 it worked (may be machine-specific?). Also checked on spin, works just fine. ## Comment 393 Date: 2004-03-13 08:36:40 +0100 From: @njnes Logged In: YES user_id=43556 data gets loaded via ascii_io into memory bats. These are marked STORE_MMAP in make_persistent (mil proc of ascii_io) using BATmmap. This only gets activated after a reload ?? Somehow the reload as STORE_MMAP succeeds but didn't create a .priv file. ## Comment 394 Date: 2004-03-14 16:06:50 +0100 From: Johan List &lt;<biglebowski>&gt; Logged In: YES user_id=573481 I have the same problem, on Spin. It is a rather large table of (int,str). The table I refer to below is created in C, with BATnew and made persistent. All inserts are done with BUNins, tables are committed after insertion and unloaded (with unload). >var l := [length](word_index); load word_index DESCload 36 HEAPload (36.buns,storage=3,offset=0,free=295992792,size=352059392 ) = 1432265084 move bat/36.buns.priv bat/36.buns = 0 (0ms) move bat/36.buns bat/36.buns.priv = 0 (1ms) GDKload: name=36, ext=buns.priv, mode 3 mmap(NULL, 0, chunk 352059392, mod 3074, tpe 0, path bat/36.buns.priv, 0) = 0x59e96000 HEAPload (36.theap,storage=0,offset=0,free=8950052,size=9563460) = 1432265084 GDKload: name=36, ext=theap, mode 0 read(dst 0x6ee56010, n_expected 8950052, fd 9) = 8950052 HEAPload (40.buns.priv,storage=1,offset=0,free=0,size=296026112) = - 72515583 GDKload: name=40, ext=buns.priv, mode 1 mmap(NULL, 0, chunk 296026112, mod 3074, tpe 0, path bat/40.buns.priv, 0) = 0x6f775000 ADDED FILENAME 40.buns.priv BATsetaccess(make_readonly) rename (bat/40.buns.priv,bat/40.buns) = 0 BATmmap(tmp_40,1,0,0,0,0) > var word_index_cleaned := l.select(int(3), int(25)); HEAPload (43.buns.priv,storage=1,offset=0,free=0,size=260505600) = - 72515583 GDKload: name=43, ext=buns.priv, mode 1 mmap(NULL, 0, chunk 260505600, mod 3074, tpe 0, path bat/43.buns.priv, 0) = 0x811c5000 HEAPsave (43.buns,storage=1,offset=0,free=260505600,size=260505600 ) GDKsave: name=43, ext=buns, mode 1 MT_msync(buf 0x811c5000, size 260505600, MMAP_SYNC) = 0 munmap(base=0x811c5000, size=260505600) = 0 HEAPload (43.buns,storage=1,offset=0,free=260505600,size=312606720 ) = 1439401776 move bat/43.buns.priv bat/43.buns = 0 (1ms) GDKload: name=43, ext=buns, mode 1 mmap(NULL, 0, chunk 312606720, mod 3074, tpe 0, path bat/43.buns, 0) = 0x811c5000 ADDED FILENAME 43.buns Mserver: /data/home/jalist/Monet/MonetDB/src/gdk/gdk_bat.m x:1379: make_readonly: Assertion `p' failed. Aborted ---- I put in the ADDED FILENAME myself to see what happened but I have no clue. :/ ## Comment 395 Date: 2004-03-18 08:30:52 +0100 From: @njnes Logged In: YES user_id=43556 fixed, now also HEAPextend adds .priv. ## Comment 396 Date: 2005-10-06 13:43:54 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / TOO LARGE This bug requires lots of data to test. ## Comment 397 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 914985 at http://sourceforge.net/support/tracker.php?aid=914985
Assertion triggered in make_persistent
https://api.github.com/repos/MonetDB/MonetDB/issues/76/comments
0
2020-11-30T08:03:37Z
2024-06-27T10:51:42Z
https://github.com/MonetDB/MonetDB/issues/76
753,251,247
76
[ "MonetDB", "MonetDB" ]
Date: 2004-03-12 01:07:27 +0100 From: @swingbit To: Stefan Manegold &lt;<Stefan.Manegold>&gt; Version: -- development Last updated: 2004-03-12 06:02:38 +0100 ## Comment 388 Date: 2004-03-12 13:07:27 +0100 From: @swingbit [algebra module] rangesplit(BAT[any::1,any::2], int) : BAT[any::2,BAT] --- Using a.rangesplit(0) doesn't make sense of course... we are not interested in having 0 chunks from a bat. But doing that Monet just quit with "Floating point exception", instead of reporting an error on wrong parameters. ## Comment 389 Date: 2004-03-12 18:02:38 +0100 From: @drstmane Logged In: YES user_id=572415 make rangesplit (and hashsplit) fail "safely" (i.e., GDKerror), in case the number of requested ranges is less than 1. also, adjust too large number of ranges to number of tuples and issue an appropriate warning. ## Comment 390 Date: 2005-10-06 13:35:36 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: ALREADY IN TESTWEB tests/BugsViaSourgeforce/Tests/ID.914935* ## Comment 391 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 914935 at http://sourceforge.net/support/tracker.php?aid=914935
rangesplit() fp exception on 0 chuncks
https://api.github.com/repos/MonetDB/MonetDB/issues/75/comments
0
2020-11-30T08:03:34Z
2024-06-27T10:51:41Z
https://github.com/MonetDB/MonetDB/issues/75
753,251,208
75
[ "MonetDB", "MonetDB" ]
Date: 2004-03-11 09:58:25 +0100 From: @drstmane To: Stefan Manegold &lt;<Stefan.Manegold>&gt; Version: -- development Last updated: 2004-03-12 07:40:28 +0100 ## Comment 383 Date: 2004-03-11 21:58:25 +0100 From: @drstmane I just noticed, that (apperently not only ;-) I overlooked the some more bugs, that "sneaked-in" with Peter's yesterday's changes: On 64-bit Linux, tests src/modules/plain/Tests/aggr* & src/modules/Tests/decimal fail with: "!ERROR: Mserver internal error, please restart. Please make sure your disk is not full." My apologies for not checking the TestWeb any better before propagating Peter's yesterday's changes to the release branch! Unfortunately, it's now too late to undo the propagation, hence I make this a high-priority bug report. (PS: If we're *very lucky*, my fix in gdk_storage might also fix this one...) ## Comment 384 Date: 2004-03-11 22:03:14 +0100 From: @drstmane Logged In: YES user_id=572415 Same bug occurs with test src/modules/plain/Tests/monettime on SunOS5.8 GNU-64 ## Comment 385 Date: 2004-03-12 07:40:28 +0100 From: @drstmane Logged In: YES user_id=572415 Indeed, we are "very lucky": My last fix in src/gdk/gdk_storage (adding paratheses around conditional expression) do not only fix http://sourceforge.net/support/tracker.php?aid=914387, but also this one... ;-) ## Comment 386 Date: 2005-10-06 13:32:57 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: ALREADY IN TESTWEB ## Comment 387 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 914447 at http://sourceforge.net/support/tracker.php?aid=914447
"Mserver internal error, please restart." on Linux
https://api.github.com/repos/MonetDB/MonetDB/issues/74/comments
0
2020-11-30T08:03:30Z
2024-06-27T10:51:41Z
https://github.com/MonetDB/MonetDB/issues/74
753,251,158
74
[ "MonetDB", "MonetDB" ]
Date: 2004-03-11 09:42:23 +0100 From: @drstmane To: @njnes Version: -- development Last updated: 2004-03-23 10:56:17 +0100 ## Comment 375 Date: 2004-03-11 21:42:23 +0100 From: @drstmane Peter's last change in gdk_utils (see below) just made me realize the following: Using macro "HW_Linux" to detect whether we are compiling on Linux is not "a good idea", since this macro is only defined in case configure (i.e., conf/monet.m4) finds the proper libraries for hardware counter support. In other places (see below), we use macro "LINUX", but it appears that this is (most probably) some legacy, since neither gcc nor icc seem to define this, and I didn't find any other place where "LINUX" is defined. (I do vaguely recall, though, that there used to be a "-DLINUX" in acient Monet Makefiles...). Both, gcc and icc do define "linux", "__linux", and "__linux__". I assigned this to Peter, but I'll have a look at this problem, too, and maybe Niels and/or Sjoerd could help as well. I'm just too tired, now, to check and fix this. We should then also check some (all?) other system-detections macros, especially "IRIX"... -------- Index: gdk_utils.mx =================================================================== RCS file: /cvsroot/monetdb/MonetDB/src/gdk/gdk_utils.mx,v retrieving revision 1.90 retrieving revision 1.91 diff -u -d -r1.90 -r1.91 --- gdk_utils.mx 11 Mar 2004 15:45:29 -0000 1.90 +++ gdk_utils.mx 11 Mar 2004 16:38:44 -0000 1.91 @@ -381,9 +381,11 @@ size_t GDKvm_heapsize(void) { ifdef _CYGNUS_H_ return ((size_t) (96<<20)); -else +elif defined(HW_Linux) struct mallinfo m = MT_mallinfo(); return GDKmem_heapsize() + m.hblkhd; +else + return GDKmem_heapsize(); endif } -------- -------- 21:37:37 manegold@draco:~/Monet/4.3/MonetDB $ cvsfiles | xargs grep LINUX ./src/gdk/gdk_utils.mx:elif defined(LINUX) ./src/testing/Mtimeout.c:if defined(LINUX) ./src/tools/Mserver.mx:ifndef LINUX ./src/tools/Mserver.mx:ifndef LINUX ./src/modules/plain/alarm.mx:if !(defined(LINUX) || defined(WIN32) || defined(CYGWIN32) || defined(__MACH__)) ./src/modules/plain/tcpip.mx:if !(defined(LINUX) || defined(WIN32)) 21:38:20 manegold@draco:~/Monet/4.3/MonetDB $ -------- ## Comment 376 Date: 2004-03-11 21:44:27 +0100 From: @drstmane Logged In: YES user_id=572415 sorry, forgot to set "group" and "Category"... ## Comment 377 Date: 2004-03-12 21:25:58 +0100 From: @njnes Logged In: YES user_id=43556 LINUX macro's are all gone But there are still sgi,AIX,__MACH__ and WIN32 macros which need to be looked at and cleanup (these are unlike the LINUX macro still used). One remaining IRIX (also not set) macro in ddbench is left in because the otherwise activated prefetch code hasn't been tested in a while. And prefetching is only implemented for IRIX and should be done for all archs. ## Comment 378 Date: 2004-03-12 23:10:08 +0100 From: @drstmane Logged In: YES user_id=572415 "__MACH__" are all OK (i.e., defined by compiler and used in right places). "_AIX" seem to be OK (defined by compiler and usage seesm to be OK). "AIX" need to be checked (defined? needed?); occur in src/mapi/mapi.mx and src/modules/plain/tcpip.mx; cf. http://cvs.sourceforge.net/viewcvs.py/monetdb/MonetDB/src/mapi/mapi.mx?r1=1.20&r2=1.21 and http://cvs.sourceforge.net/viewcvs.py/monetdb/MonetDB/src/modules/plain/tcpip.mx?r1=1.17&r2=1.18 "__sgi" occur together with "AIX" (see above) (seems to be defined by compiler, but I'm not sure, whether is it (still) needed everywhere). "SOLARIS" need to be checked (defined?, needed?) (in src/monet/monet_interpreter.mx, src/tools/Mserver.mx, src/modules/contrib/mprof.mx). What about the "OSVER" that is only used together with "SOLARIS"??? Also to be checked: "CYGWIN32" in src/mel/mel.mx & src/utils/Mx/prefixMxFile.c vs. "__CYGWIN32__" in src/monet/monet_parse.mx & src/testing/Mlimit.c "WIN32" vs. "NATIVE_WIN32" in various places/files; "NATIVE_WIN32" is defined in NT/winconfig.h; "WIN32" is defined in configure.ag, covering apparently both native Windows & Cygwin. ## Comment 379 Date: 2004-03-13 17:54:56 +0100 From: @drstmane Logged In: YES user_id=572415 A short update for tha logs: "CYGWIN32" has been removed by Niels. "SOLARIS" has been removed by Stefan. I cannot check "AIX", since I have no access to any AIX machine (anymore). [Pretty much action for a low-priority bug ;-)] ## Comment 380 Date: 2004-03-23 22:56:17 +0100 From: @njnes Logged In: YES user_id=43556 removed most IRIX (sgi), Solaris, Linux, MACH, AIX and CYGWIN conditionals are removed remaining IRIX is just there keep old code out remaining _AIX are needed (pragma alloca and strange library names) remaining __MACH__ is needed because of broken include files (lockf) remaining are WIN32 and NATIVE_WIN32 which are all needed but may slowly be removed infavour of feature tests ## Comment 381 Date: 2005-10-06 13:31:56 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / COMPILATION ## Comment 382 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 914435 at http://sourceforge.net/support/tracker.php?aid=914435
Inconsistent or/and incorrect(?) use of macros for Linux
https://api.github.com/repos/MonetDB/MonetDB/issues/73/comments
0
2020-11-30T08:03:27Z
2024-06-28T13:37:44Z
https://github.com/MonetDB/MonetDB/issues/73
753,251,127
73
[ "MonetDB", "MonetDB" ]
Date: 2004-03-11 09:31:13 +0100 From: @sjoerdmullender To: @sjoerdmullender Version: -- development Last updated: 2004-03-15 02:27:59 +0100 ## Comment 371 Date: 2004-03-11 21:31:13 +0100 From: @sjoerdmullender bootstrap complains about old versions of autoconf/automake/libtool when they are in fact missing. bootstrap should check for this condition separately and give a clear error message and exit. Furthermore, when libtool is missing, bootstrap continues and a later configure then fails with all sorts of strange error messages. ## Comment 372 Date: 2004-03-15 14:27:59 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Added checks to bootstrap. ## Comment 373 Date: 2005-10-06 13:30:36 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / COMPILATION ## Comment 374 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 914423 at http://sourceforge.net/support/tracker.php?aid=914423
Error message when autoconf etc. missing not clear
https://api.github.com/repos/MonetDB/MonetDB/issues/72/comments
0
2020-11-30T08:03:25Z
2024-06-27T10:51:38Z
https://github.com/MonetDB/MonetDB/issues/72
753,251,096
72
[ "MonetDB", "MonetDB" ]
Date: 2004-03-11 08:47:28 +0100 From: @drstmane To: Stefan Manegold &lt;<Stefan.Manegold>&gt; Version: -- development Last updated: 2004-03-11 08:54:21 +0100 ## Comment 367 Date: 2004-03-11 20:47:28 +0100 From: @drstmane After yesterdays' check-ins, test src/modules/contrib/Tests/salgebra fails, complaining twice about "!WARNING: Inconsistency in clusterhash repository..." [Sorry Peter, couldn't resist ;-)] ## Comment 368 Date: 2004-03-11 20:54:21 +0100 From: @drstmane Logged In: YES user_id=572415 I just realized that my debugging attempt brought me closer to the solution that I had thought: Apparently, compilers do interpret the following lines differently: j = off + (probe==cnt)?i:(rand() % MIN(16384,cnt)) ; j = off + ((probe==cnt)?i:(rand() % MIN(16384,cnt))); [Peter, now that I found and fixed the problem, I realize this might have been the very line I saw on your screen earlier today, right? Well, anyway, now it'\''s fixed and I can propagate your yesterday'\''s fixes to the release branch...] ## Comment 369 Date: 2005-10-06 13:29:58 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: ALREADY IN TESTWEB ## Comment 370 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 914387 at http://sourceforge.net/support/tracker.php?aid=914387
test salgebra fails after yesterday's changes
https://api.github.com/repos/MonetDB/MonetDB/issues/71/comments
0
2020-11-30T08:03:22Z
2024-06-27T10:51:37Z
https://github.com/MonetDB/MonetDB/issues/71
753,251,059
71
[ "MonetDB", "MonetDB" ]
Date: 2004-03-11 04:16:27 +0100 From: @drstmane To: @sjoerdmullender Version: -- development Last updated: 2004-03-11 06:24:47 +0100 ## Comment 363 Date: 2004-03-11 16:16:27 +0100 From: @drstmane In the Current/Head/Development branch, yesterday's changes make compilation of gdk_utils fail on Windows: cl -GF -W3 -MD -nologo -Zi -G6 -I. -I.\..\.. -IC:\Pthreads\include -DHAVE_CONFIG_H -I.\..\..\..\src\gdk "-I..\common" -IC:\Pthreads\include -I.\..\..\..\src\gdk "-I..\common" -IC:\Pthreads\include -DL gdk_utils.c .\..\..\..\src\gdk\gdk_utils.mx(266) : error C2065: 'SIGBUS' : undeclared identifier .\..\..\..\src\gdk\gdk_utils.mx(1366) : warning C4018: '>' : signed/unsigned mismatch NMAKE : fatal error U1077: 'cl' : return code '0x2' Stop. NMAKE : fatal error U1077: 'cd' : return code '0x2' Stop. NMAKE : fatal error U1077: 'cd' : return code '0x2' Stop. NMAKE : fatal error U1077: 'C:\PROGRA~1\MICROS~2\VC98\BIN\NMAKE.EXE' : return code '0x2' Stop. ## Comment 364 Date: 2004-03-11 18:24:47 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Fixed at about the same time this bug was reported. ## Comment 365 Date: 2005-10-06 13:27:29 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / COMPILATION ## Comment 366 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 914194 at http://sourceforge.net/support/tracker.php?aid=914194
gdk_utils does not compile on Windows
https://api.github.com/repos/MonetDB/MonetDB/issues/70/comments
0
2020-11-30T08:03:19Z
2024-06-27T10:51:36Z
https://github.com/MonetDB/MonetDB/issues/70
753,251,025
70
[ "MonetDB", "MonetDB" ]
Date: 2004-03-11 03:29:00 +0100 From: @MarcinZukowski To: @njnes Version: -- development Last updated: 2004-03-14 09:24:45 +0100 ## Comment 359 Date: 2004-03-11 15:29:00 +0100 From: @MarcinZukowski While doing too much copy-paste I got a segfault. The code is (also attached) PROC crash() { print($t); } crash(); It's obviously incorrect code, but it shouldn't segfault. ps. money_for_cookies :+= 1; ## Comment 360 Date: 2004-03-12 23:17:39 +0100 From: @drstmane Logged In: YES user_id=572415 Doesn't see to crash anymore, but now complains about "!ERROR: Mserver internal error, please restart. Please make sure your disk is not full." (see respective test in TestWeb as of tomorrow morning) Is that what we want? ## Comment 361 Date: 2005-10-06 13:26:25 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: ALREADY IN TESTWEB tests/BugsViaSourgeforce/Tests/ID.914159* ## Comment 362 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 914159 at http://sourceforge.net/support/tracker.php?aid=914159
Incorrect $t/$h use in MIL crashes Mserver
https://api.github.com/repos/MonetDB/MonetDB/issues/69/comments
0
2020-11-30T08:03:16Z
2024-06-27T10:51:36Z
https://github.com/MonetDB/MonetDB/issues/69
753,250,988
69
[ "MonetDB", "MonetDB" ]
Date: 2004-03-11 03:23:52 +0100 From: @swingbit To: Peter Boncz &lt;<boncz>&gt; Version: -- development Last updated: 2004-03-14 09:46:50 +0100 ## Comment 354 Date: 2004-03-11 15:23:52 +0100 From: @swingbit Running the code below, bbp goes crazy, giving either this error !ERROR: BBPdecref(a) does not have pointer fixes. or stopping with this assertion Mserver: /export/scratch1/roberto/Monet/src/MonetDB/src/gdk/gdk_bbp.mx:1254: BBPdescriptor: Assertion `BBP[(((int)(i))>0?((int)(i)):-((int)(i)))].refs' failed. Or, sometimes it just crashes.... The lock mechanism shouldn't be needed, as we're only reading from some persistent bats. The problem seems related to reading from views. ------------------------------------ if (not(view_bbp_name.reverse.exist("a"))) { commit; var a := bat(void,dbl,1000000).rename("a"); var i := 0; while(i < 1000000) a.insert(nil,dbl(i :+= 1)); a.seqbase(0@0).access(BAT_READ).persists(true); commit; } PROC g(): void := { VAR i := 0; VAR b1, b2, b3, b4; WHILE(i < 1000) { VAR j := 0; WHILE(j < 1000) { All these lines create a view on 'a' b1 := a.slice(0,100).reverse.mark(0@0).reverse; b2 := a.slice(0,100).reverse.mark(0@0).reverse; b3 := a.slice(0,100).reverse.mark(0@0).reverse; b4 := a.slice(0,100).reverse.mark(0@0).reverse; j :+= 1; } printf("%d %d\n", threadid(), i); i :+= 1; } } threadcnt(1); {| g(); g(); |} threadcnt(-1); ## Comment 355 Date: 2004-03-12 22:38:51 +0100 From: @drstmane Logged In: YES user_id=572415 Peter, Roberto, could (one of) you please check, whether Peter's fix (see below) does indeed fix this bug, and if so, close this bug report; I'm not sure whether the test that I just added is sufficient, since I had to reduce some numbers to get an execution time that is reasonalbe for testing... Thanks in advance! =================================================================== 2004/03/12 - boncz: src/monet/monet_interpreter.mx Fix for a bug reported by Roberto todae (crash in a paralell batloop that is in a while-loop) what happened here is that on the last iteration, if there are less than N items, the MIL tree is hacked by the parloop code to hide some children (for those statements where there is no data). This hack should be undone afterwards, so the expanded tree that contains a MIL parblock, stays in sane state, as itis re-used if the batloop itself is in some other loop. =================================================================== ## Comment 356 Date: 2004-03-14 21:46:50 +0100 From: @peterboncz Logged In: YES user_id=591107 a race condition has been fixed in BBPshare/BBPunshare it only triggers when under extreme stress, when BBPtrim is done on each malloc. this extreme stress was used by the mem_cursize GDK counter becomining nagative, and hence >4G (so the system thinks its overloaded and starts BBPtrimming like mad to no avail). so there is a new system now that once in a while corrects mem_cursize using allinfo information. background: mem_cursize is updated without locks because it is done on each malloc/free for performance reason. The downside is that on parallel execution the statistics become incorrect (gradually). ## Comment 357 Date: 2005-10-06 13:25:44 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: ALREADY IN TESTWEB tests/BugsViaSourgeforce/Tests/ID.914155* ## Comment 358 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 914155 at http://sourceforge.net/support/tracker.php?aid=914155
parallel execution problem (is 1st euro mine?)
https://api.github.com/repos/MonetDB/MonetDB/issues/68/comments
0
2020-11-30T08:03:14Z
2024-06-28T13:37:43Z
https://github.com/MonetDB/MonetDB/issues/68
753,250,947
68
[ "MonetDB", "MonetDB" ]
Date: 2004-03-11 02:21:48 +0100 From: @mlkersten To: @njnes Version: -- development Last updated: 2004-03-12 10:55:27 +0100 ## Comment 351 Date: 2004-03-11 14:21:48 +0100 From: @mlkersten On Linux you can start multiple Mservers against the same database with possible dissastrous effect. ## Comment 352 Date: 2005-10-06 13:23:58 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: TEST ADDED / SUCCESStests/BugDay_2005-10-06_4.8/multiple_servers.SF-914113* ## Comment 353 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 914113 at http://sourceforge.net/support/tracker.php?aid=914113
Multiple Mservers
https://api.github.com/repos/MonetDB/MonetDB/issues/67/comments
0
2020-11-30T08:03:11Z
2024-06-27T10:51:34Z
https://github.com/MonetDB/MonetDB/issues/67
753,250,913
67
[ "MonetDB", "MonetDB" ]
Date: 2004-03-07 09:01:50 +0100 From: @mlkersten To: Stefan Manegold &lt;<Stefan.Manegold>&gt; Version: -- development Last updated: 2004-03-08 07:02:41 +0100 ## Comment 346 Date: 2004-03-07 21:01:50 +0100 From: @mlkersten The changes in GDKmalloc arena conflicts with Valgrind. After setting 'gdk_alloc_map=no' and using a default compiled Mserver an assertion error is raised upon starting valgrind. This complicates debugging. monet>mk@orion::~/opensource/MonetDB/Linux/etc> valgrind Mserver ==12400== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux. ==12400== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward. ==12400== Using valgrind-2.0.0, a program supervision framework for x86-linux. ==12400== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward. ==12400== Estimated CPU clock rate is 1399 MHz ==12400== For more details, rerun with: -v ==12400== Mserver: /ufs/mk/opensource/MonetDB/src/gdk/gdk_utils.mx:829: GDKmallocmax: Assertion `(((size_t) s)&4) == 0' failed. Aborted ## Comment 347 Date: 2004-03-07 21:28:54 +0100 From: @drstmane Logged In: YES user_id=572415 from conf/monet.conf.in: -------- gdk_alloc_map=yes for 32 bit systems try claim 3G of (virtual) memory set to "no" to run Mserver with valgrind; also, you need to tell valgrind to use 8-byte alignment, hence: "valgrind --alignment=8 Mserver --set gdk_alloc_map=no ..." -------- From my last checkin to conf/monet.conf.in: -------- to run Mserver with valgrind, you now need to tel valgrind to use 8-byte alignment: "valgrind --alignment=8 Mserver --set gdk_alloc_map=no ..." furthermore, you also need to patch src/gdk/gdk_system.mx as follows, first: ======== --- src/gdk/gdk_system.mx 28 Jan 2004 20:42:41 -0000 1.56 +++ src/gdk/gdk_system.mx 2 Mar 2004 17:42:22 -0000 @@ -359,8 +359,8 @@ process (i.e. with all its threads) is replaced by the new program. If this new program does nothing, other than exit, we effectively exit the server. - */ execl(s ? "/bin/false" : "/bin/true", s ? "false" : "true", (char *) 0); + */ endif exit(s); } ======== I also just added a respective note to HowToStart. Sorry for the delay... ## Comment 348 Date: 2004-03-08 19:02:41 +0100 From: @drstmane Logged In: YES user_id=572415 see "HowToStart" for hints how to run Mserver with valgrind on Linux ## Comment 349 Date: 2005-10-06 13:07:18 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / DOCUMENTATION ## Comment 350 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 911559 at http://sourceforge.net/support/tracker.php?aid=911559
Assertion raised by valgrind
https://api.github.com/repos/MonetDB/MonetDB/issues/66/comments
0
2020-11-30T08:03:08Z
2024-06-28T13:37:43Z
https://github.com/MonetDB/MonetDB/issues/66
753,250,878
66
[ "MonetDB", "MonetDB" ]
Date: 2004-03-07 05:57:02 +0100 From: @drstmane To: @sjoerdmullender Version: -- development Last updated: 2004-03-22 02:35:17 +0100 ## Comment 337 Date: 2004-03-07 17:57:02 +0100 From: @drstmane On Linux, making 1000 (smack01) resp. 1234 (ManyMapiClients) MAPI conections in a row from either a C program (smack01) or a python script (manyMapiClients) takes about 50 to 59 seconds (i.e., just below 1 minute), while it take atmost half as long on other platforms with usually slower hardware (cf., http://monetdb.cwi.nl/TestWeb/Current/MonetDB/MonetDB/.mTests03/times.html or http://monetdb.cwi.nl/TestWeb/Current/MonetDB/MonetDB/.mTests103/times.html ). I'm not sure, whether this is a bug in our code, or just a "feature" of Linux, respectively its very socket implementation ... ## Comment 338 Date: 2004-03-07 20:16:35 +0100 From: @mlkersten Logged In: YES user_id=490798 The response time on Linux is in line with what we observed in Aug 03, i.e. ca 16 connections/second. At the same time on M-5 ca 60 connects/second were possible. It is indicative of unnecessary process thread creation/destroy in M4.3 for clients. ## Comment 339 Date: 2004-03-07 20:38:36 +0100 From: @mlkersten Logged In: YES user_id=490798 It is not necessarilly the number of processes, but the amount of initialization required to start a client. In M4 this is quite expensive. ## Comment 340 Date: 2004-03-07 22:02:49 +0100 From: @drstmane Logged In: YES user_id=572415 the point I tried to make it not (only) a general performance issue, but (mainly) a Linux issue: Hardware: C1.5.7: winxp.ins.cwi.nl, PentiumIII, 500 MHz D7.2.0: monet.cs.umass.edu, PowerPC, ? MHz I646.5: medusa.cwi.nl, R10/12k, 250/300 MHz L2.4.20: draco.ins.cwi.nl, Athlon XP, 1400 MHz L2.4.21: titan03.inf.uni-konstanz.de, Pentium 4 XEON, 2200 MHz L2.4.18: titan.ins.cwi.nl, Itanium 2, 1300 MHz L2.4.24: spin.project.cwi.nl, Opteron 242, 1600 MHz S5.8: apps.cwi.nl, UltraSPARC II, 450 MHz W5.0: win2000.ins.cwi.nl, PentiumIII, 450 MHz a: src/mapi/Tests/manyMapiClients.MAPI.py: 1234 client connects, time in seconds b: src/mapi/examples/C/Tests/smack01.c: 1000 client connects, time in seconds c: src/mapi/Tests/manyMapiClients.MAPI.py: 1234 client connects, connections per second d: src/mapi/examples/C/Tests/smack01.c: 1000 client connects, connections per second a b c d W5.0 ntv32d 10.936 31.215 112 32 S5.8 GNU64d 16:135 13.320 77 77 I646.5 ntv64d 21.229 17.665 58 56 C1.5.7 GNU32s 22.816 22.813 54 44 D7.2.0 GNU32d 40:474 37.755 30 26 L2.4.20 GNU32d 51.550 65.053 24 15 L2.4.21 GNU32d 54.955 64.724 22 16 L2.4.18 GNU64d 51.930 81.389 24 12 L2.4.24 GNU64d 50.534 42.339 24 24 L2.4.20 ntv32d 51.400 66.165 24 15 L2.4.24 ntv32d 50:793 53.790 24 19 L2.4.18 ntv64d 51.936 81.163 24 12 ## Comment 341 Date: 2004-03-09 09:03:23 +0100 From: @njnes Logged In: YES user_id=43556 investigating if this caused by linux(kernel/glibc?) or MonetDB ## Comment 342 Date: 2004-03-18 17:24:41 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 The attached file contains two small programs to measure the time it takes to make multiple connections. By using some preprocessor defines various options can be tested. The result of testing lots of different combinations is that the time it takes to make 1000 connections on Linux varies from 0 (occasionally), 3 or 4 (quite often) to sometimes over 60 seconds, and I have even seen much longer than that. On Irix I have never seen anything larger than a few seconds. I think we're dealing with a Linux kernel problem here. (Tested mostly on RedHat 9, but also a little on Fedora Core 1). ## Comment 343 Date: 2004-03-22 14:35:16 +0100 From: @mlkersten Logged In: YES user_id=490798 Nothing much we can do ## Comment 344 Date: 2005-10-06 13:04:34 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / REDUNDANT This is basically already tested with src/mapi/examples/C/Tests/smack01*. ## Comment 345 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 911474 at http://sourceforge.net/support/tracker.php?aid=911474
slow MAPI connections on Linux
https://api.github.com/repos/MonetDB/MonetDB/issues/65/comments
0
2020-11-30T08:03:05Z
2024-06-28T13:37:42Z
https://github.com/MonetDB/MonetDB/issues/65
753,250,837
65
[ "MonetDB", "MonetDB" ]
Date: 2004-03-07 11:50:51 +0100 From: @mlkersten To: Peter Boncz &lt;<boncz>&gt; Version: -- development Last updated: 2014-09-16 12:37:54 +0200 ## Comment 326 Date: 2004-03-07 11:50:51 +0100 From: @mlkersten A full disk caused a bus error in Mserver while running an experiment to create a 'huge' table of 40M elements using the DBtapestry program. the latest portion of the BBP dir might indicate where action was missing, i.e. the first: -rw-r--r-- 1 mk ins 0 Mar 7 11:40 568.buns.priv -rw-r--r-- 1 mk ins 335609857 Mar 7 11:39 549.buns -rw-r--r-- 1 mk ins 335609857 Mar 7 11:39 568.buns -rw-r--r-- 1 mk ins 335609857 Mar 7 11:35 548.buns -rw-r--r-- 1 mk ins 180 Mar 7 11:31 540.buns -rw-r--r-- 1 mk ins 756 Mar 7 11:31 540.desc -rw-r--r-- 1 mk ins 180 Mar 7 11:31 541.buns -rw-r--r-- 1 mk ins 756 Mar 7 11:31 541.desc -rw-r--r-- 1 mk ins 180 Mar 7 11:31 542.buns -rw-r--r-- 1 mk ins 756 Mar 7 11:31 542.desc -rw-r--r-- 1 mk ins 180 Mar 7 11:31 543.buns -rw-r--r-- 1 mk ins 756 Mar 7 11:31 543.desc -rw-r--r-- 1 mk ins 180 Mar 7 11:31 544.buns -rw-r--r-- 1 mk ins 756 Mar 7 11:31 544.desc -rw-r--r-- 1 mk ins 756 Mar 7 11:31 560.desc -rw-r--r-- 1 mk ins 335609857 Mar 7 11:29 560.buns.priv -rw-r--r-- 1 mk ins 125829124 Mar 7 11:27 557.buns -rw-r--r-- 1 mk ins 125829124 Mar 7 11:26 553.buns -rw-r--r-- 1 mk ins 251723777 Mar 7 11:25 555.buns -rw-r--r-- 1 mk ins 251723777 Mar 7 11:24 547.bun ## Comment 327 Date: 2004-03-07 14:24:44 +0100 From: @mlkersten Logged In: YES user_id=490798 running the tests on db1 did not cause problems. A second trial on Orion of runMILTapestry caused the system to 'hang' while processing 30M tuples. ## Comment 328 Date: 2004-03-09 07:19:52 +0100 From: @mlkersten Logged In: YES user_id=490798 running the tests on db1 did not cause problems. A second trial on Orion of runMILTapestry caused the system to 'hang' while processing 30M tuples. ## Comment 329 Date: 2004-03-14 21:36:00 +0100 From: @peterboncz Logged In: YES user_id=591107 what simply happened is that you ran out of disk space. memorymapped areas on files with holes, intantiate memory pages on the fly as they are written into. if that is not possible, you get a BUSERR signal. so the crash is normal and justified (you have consumed simply too much resources to be able to continue). the fix is to catch the signal and give an error message and quit. ## Comment 330 Date: 2005-10-06 13:01:50 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / POSTPONED - testing what happens in case of a fulll disk is hard to do automatically in Mtest - general check for left-over BATs should be added to Mtest itself - set priority to 9 to keep us reminded ## Comment 331 Date: 2005-11-06 10:48:05 +0100 From: @drstmane Logged In: YES user_id=572415 BugDay_2005-10-06: "left-overs" are now marked as "pending" ## Comment 332 Date: 2005-11-21 04:20:16 +0100 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; ---- Original comment by: sf-robot@users.sourceforge.net ---- Logged In: YES user_id=1312539 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ## Comment 333 Date: 2006-11-22 04:20:04 +0100 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; ---- Original comment by: sf-robot@users.sourceforge.net ---- Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 365 days (the time period specified by the administrator of this Tracker). ## Comment 334 Date: 2006-11-29 10:05:48 +0100 From: @drstmane Logged In: YES user_id=572415 Originator: NO over-ruling "sf-robot": re-set to "Pending" since adding a proper test has neither been done nor finally been discarded, yet. User (submitter) & developer (assignee), please check, again. ## Comment 335 Date: 2007-11-30 04:20:04 +0100 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; ---- Original comment by: sf-robot@users.sourceforge.net ---- Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 365 days (the time period specified by the administrator of this Tracker). ## Comment 336 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 911326 at http://sourceforge.net/support/tracker.php?aid=911326 ## Comment 19868 Date: 2014-07-03 17:36:33 +0200 From: MonetDB Mercurial Repository &lt;<hg>&gt; Changeset [45acd0d7a20a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=45acd0d7a20a) 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=45acd0d7a20a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=45acd0d7a20a) Changeset description: Use posix_fallocate if available to extend files. Using this function will ensure that disk blocks are allocated, so when the file is the memory mapped and the memory then written to, we should never get a Bus Error because the disk is full. This hopefully fixes bug #64, bug #3202, and bug #3507, and possibly also bug #3502. ## Comment 20160 Date: 2014-09-16 12:37:54 +0200 From: MonetDB Mercurial Repository &lt;<hg>&gt; Changeset [ed3146037fea](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ed3146037fea) 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=ed3146037fea](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ed3146037fea) Changeset description: Fix 64 bits prefix
Bus error on full disk
https://api.github.com/repos/MonetDB/MonetDB/issues/64/comments
0
2020-11-30T08:03:01Z
2024-06-27T10:51:31Z
https://github.com/MonetDB/MonetDB/issues/64
753,250,805
64
[ "MonetDB", "MonetDB" ]
Date: 2004-03-07 09:09:55 +0100 From: @mlkersten To: @njnes Version: -- development Last updated: 2006-12-04 07:02:54 +0100 ## Comment 318 Date: 2004-03-07 09:09:55 +0100 From: @mlkersten Start Mserver and two separate MapiClients for SQL Client 1: create table tmp(i int); commit; Client 2: select * from tables; -- sees tmp Client 1: drop table tmp; commit: Client 2: select * from tables; -- still sees tmp Client 2: select * from tmp; -- works Client 2: commit; --> segmentation fault I noticed that such multi-client sessions could cause more difficult situations, e.g. hanging server (difficult to reproduce) ## Comment 319 Date: 2005-10-06 12:59:26 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / POSTPONED This needs to MapiClient processes that do things in a synchronized fashion. This is currently not possible in Mtest. ## Comment 320 Date: 2005-11-06 10:47:23 +0100 From: @drstmane Logged In: YES user_id=572415 BugDay_2005-10-06: "left-overs" are now marked as "pending" ## Comment 321 Date: 2005-11-21 04:20:16 +0100 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; ---- Original comment by: sf-robot@users.sourceforge.net ---- Logged In: YES user_id=1312539 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ## Comment 322 Date: 2006-11-22 04:20:04 +0100 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; ---- Original comment by: sf-robot@users.sourceforge.net ---- Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 365 days (the time period specified by the administrator of this Tracker). ## Comment 323 Date: 2006-11-29 10:05:41 +0100 From: @drstmane Logged In: YES user_id=572415 Originator: NO over-ruling "sf-robot": re-set to "Pending" since adding a proper test has neither been done nor finally been discarded, yet. User (submitter) & developer (assignee), please check, again. ## Comment 324 Date: 2006-12-04 18:58:57 +0100 From: @mlkersten Logged In: YES user_id=490798 Originator: YES The test now runs correctly (on M5) ## Comment 325 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 911269 at http://sourceforge.net/support/tracker.php?aid=911269
Concurrency conflict in catalog
https://api.github.com/repos/MonetDB/MonetDB/issues/63/comments
0
2020-11-30T08:02:58Z
2024-06-27T10:51:30Z
https://github.com/MonetDB/MonetDB/issues/63
753,250,772
63
[ "MonetDB", "MonetDB" ]
Date: 2004-03-02 11:39:39 +0100 From: @drstmane To: Peter Boncz &lt;<boncz>&gt; Version: -- development Last updated: 2004-03-02 06:49:11 +0100 ## Comment 314 Date: 2004-03-02 11:39:39 +0100 From: @drstmane Since the changes made on Monday Feb 23 (Peter, Niels, Sjoerd), test "tests/by_peter/Tests/GNATS-2736.milM" fails with "Mserver: /var/tmp/monet.GNU_32-d.25863/MonetDB/src/gdk/gdk_utils.mx:871: GDKfree: Assertion `(size&2) == 0' failed." This usually indecates, that there in an attempt to free non-allocated or already freed memory. This seems to be confirmed by a similar problem reported by Agustin Schapira from UMass at Amherst: ======== After running our script, when we get to a line that reads: var_887:=[>=]({count}(var_489.select("associate producer"),var_491), [max]({histogram}(var_489))).select(true); Monet crashes with the following messages: Monet Database Server V4.3.15 Copyright (c) 1993-2004, CWI. All rights reserved. compiled for powerpc-apple-darwin7.2.0/32bit; dynamically linked. server listening on port 45678 monet> *** malloc[23405]: Deallocation of a pointer not malloced: 0x6c98b0; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug *** malloc[23405]: error for object 0x6c98b0: Incorrect checksum for freed object - object was probably modified after being freed; break at szone_error *** malloc[23405]: Deallocation of a pointer not malloced: 0x6d3200; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug gdk_utils.mx:871: failed assertion `(size&2) == 0' Abort We call this MIL sentence several times in our code --it works most of the time, but it eventually fails. The BATs themselves aren't all that big: 1,500 and 250 rows respectively! I don't know how to set the MallocHelp variable to give you more debug info; is this an environment variable, or do I have to re-compile the code? By the way, this happens on OS X, on the latest release of 4.3.15 (as of today). ======== ## Comment 315 Date: 2004-03-02 18:49:11 +0100 From: @peterboncz Logged In: YES user_id=591107 BUGFIX [ 908219 ] [most probabaly] freeing non-allocated or already freed mem this fixes the crash in tests/by_peter/Tests/GNATS-2736.milM it may not fix the other problem mentioned in the bug report (amherst crash). cause was the tricky sharing of heaps in pump on the temporary result bat. this was not undone fully before freeing this temporary bat, leading to a free of the h->filename of the base BAT. ## Comment 316 Date: 2005-10-06 12:52:38 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: ALREADY IN TESTWEB tests/by_peter/Tests/GNATS-2736.* ## Comment 317 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 908219 at http://sourceforge.net/support/tracker.php?aid=908219
[most probabaly] freeing non-allocated or already freed mem
https://api.github.com/repos/MonetDB/MonetDB/issues/62/comments
0
2020-11-30T08:02:56Z
2024-06-28T13:37:42Z
https://github.com/MonetDB/MonetDB/issues/62
753,250,741
62
[ "MonetDB", "MonetDB" ]
Date: 2004-03-01 07:25:20 +0100 From: @drstmane To: Peter Boncz &lt;<boncz>&gt; Version: -- development Last updated: 2004-03-04 12:38:49 +0100 ## Comment 311 Date: 2004-03-01 19:25:20 +0100 From: @drstmane Since recent changes, the tests "tests/by_Peter/Tests/tst_mmap.milM" and "tests/by_Peter/Tests/tst_writestr.milM" do fail with a segfault in gdk_atom:strPut() line 1504: "if (GDK_STRCMP(v, x) == 0) {". Debugging revealed, that line 1503: "str x = (str) (h->base + *l + sizeof(var_t));" yields an "Address out of bounds". Logs of the debug sessions are available in the attached file. ## Comment 312 Date: 2005-10-06 12:51:24 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: ALREADY IN TESTWEB tests/by_Peter/Tests/tst_mmap.*, tests/by_Peter/Tests/tst_writestr.* ## Comment 313 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 907740 at http://sourceforge.net/support/tracker.php?aid=907740
tests tst_mmap & tst_writestr segfault in gdk_atom:strPu
https://api.github.com/repos/MonetDB/MonetDB/issues/61/comments
0
2020-11-30T08:02:54Z
2024-06-27T10:51:28Z
https://github.com/MonetDB/MonetDB/issues/61
753,250,716
61
[ "MonetDB", "MonetDB" ]
Date: 2004-02-27 02:40:33 +0100 From: @grobian To: @njnes Version: -- development Last updated: 2006-01-14 01:48:36 +0100 ## Comment 299 Date: 2004-02-27 14:40:33 +0100 From: @grobian Using the --dump flag of the MapiClient command creates SQL, but PRIMARY KEY and FOREIGN KEY relations are not in the CREATE TABLE statement. When trying to import the dumped SQL into Monet again, the following happens: (pictor:~) % MapiClient -uxxx -Pxxx -lsql < createfull.sql MAPI = monetdb@localhost:45123 ACTION= mapi_get_row QUERY = COPY 150000 RECORDS INTO a FROM stdin USING DELIMITERS '\t'; ERROR = !ERROR: read error !ERROR: mvc_import_table_wrap: operation failed. Broken pipe ## Comment 300 Date: 2004-03-19 13:52:42 +0100 From: @grobian Logged In: YES user_id=963970 The --dump operation is broken at the moment: % bin/MapiClient -uxxx -Pxxx -lsql -D CREATE TABLE voyages ( MAPI = monetdb@localhost:45123 ACTION= mapi_get_row QUERY = select name,type,type_digits,type_scale,null,default from columns c,tables t where c.table_id = t.id and 'voyages' = t.name order by c.number; ERROR = !Only single column names supported in order by CREATE TABLE seafarers ( MAPI = monetdb@localhost:45123 ACTION= mapi_get_row QUERY = select name,type,type_digits,type_scale,null,default from columns c,tables t where c.table_id = t.id and ERROR = !Only single column names supported in order by etc etc etc. Is there a reason why only single column names are supported in the order by clause at the moment? ## Comment 301 Date: 2004-03-19 13:59:24 +0100 From: @njnes Logged In: YES user_id=43556 mr-meldown Is there a reason why only single column names are supported in the order by clause at the moment? sql99 specs ## Comment 302 Date: 2004-03-19 15:21:02 +0100 From: @njnes Logged In: YES user_id=43556 mr-meldown Is there a reason why only single column names are supported in the order by clause at the moment? sql99 specs ## Comment 303 Date: 2004-03-27 14:39:45 +0100 From: @grobian Logged In: YES user_id=963970 a dump now can successfully be restored. (like one should expect) Adding SQL create syntax for primary, unique and foreign keys is on my todo list. (currently only the data and views are dumped) ## Comment 304 Date: 2004-05-09 16:20:19 +0200 From: @grobian Logged In: YES user_id=963970 I won't fix the problem (for now). JdbcClient does something alike, but suffers from a problem (dependancy tree of foreign key relations) I will first solve in Java before even thinking of a C implementation. ## Comment 305 Date: 2005-10-06 16:05:37 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: TEST ADDED / SUCCESS src/test/BugDay_2005-10-06_2.8/MapiClient-dump.SF-905851.* ## Comment 306 Date: 2005-12-20 23:47:14 +0100 From: @drstmane Logged In: YES user_id=572415 re-opened as the respective test fails; cf. e.g.: http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/GNU.64.64.d-Fedora4/src_test_BugDay_2005-10-06_2.8/MapiClient-dump.SF-905851.out.00.html ## Comment 307 Date: 2005-12-30 16:18:25 +0100 From: @drstmane Logged In: YES user_id=572415 The test seems to fail since Dec 13 2005; hence, it might be related to changes made on Dec 12 2005. ## Comment 308 Date: 2006-01-14 13:26:30 +0100 From: @drstmane Logged In: YES user_id=572415 Test seems to work fine, again, after code changes made on Jan 10 and/or Jan 11 2006. Can this be closed, again? ## Comment 309 Date: 2006-01-14 13:48:36 +0100 From: @grobian Logged In: YES user_id=963970 test runs fine again, closing bug. ## Comment 310 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 905851 at http://sourceforge.net/support/tracker.php?aid=905851
MapiClient dump / restore issues
https://api.github.com/repos/MonetDB/MonetDB/issues/60/comments
0
2020-11-30T08:02:51Z
2024-06-28T13:37:41Z
https://github.com/MonetDB/MonetDB/issues/60
753,250,677
60
[ "MonetDB", "MonetDB" ]
Date: 2004-02-27 01:14:40 +0100 From: @drstmane To: @sjoerdmullender Version: -- development Last updated: 2004-03-04 09:09:55 +0100 ## Comment 293 Date: 2004-02-27 01:14:40 +0100 From: @drstmane [This bug was originally reported by Matthew Cornell of UMass at Amherst.] (At least on Linux and CYGWIN, haven't tested native Windows, yet,) The MIL parser apparently cannot handle Windows-style "CRLF" linebreaks, or at least not "CR" (Ctrl-M) of it (see below). Sjoerd, feel free to hand-over this bug-report to Niels/Peter/... in case you think it's better take care of by either one of them ;-) 01:00:47 manegold@draco:~/Monet/4.3/MonetDB $ cat -v /tmp/hello.mil print("hello"); 01:00:50 manegold@draco:~/Monet/4.3/MonetDB $ cat -v /tmp/hello-M.mil print("hello");^M 01:00:52 manegold@draco:~/Monet/4.3/MonetDB $ MapiClient < /tmp/hello.mil [ "hello" ] 01:00:55 manegold@draco:~/Monet/4.3/MonetDB $ MapiClient < /tmp/hello-M.mil MAPI = anonymous@localhost:50000 ACTION= mapi_get_row QUERY = print("hello"); "RROR = !ERROR: "print("hello"); ! ^ ! can't help you here, sorry. 01:00:59 manegold@draco:~/Monet/4.3/MonetDB $ MapiClient /tmp/hello.mil print("hello"); [ "hello" ] mil> \q 01:01:29 manegold@draco:~/Monet/4.3/MonetDB $ MapiClient /tmp/hello-M.mil print("hello"); MAPI = anonymous@localhost:50000 ACTION= mapi_get_row QUERY = print("hello"); "RROR = !ERROR: "print("hello"); ! ^ ! can't help you here, sorry. mil> \q 01:01:36 manegold@draco:~/Monet/4.3/MonetDB $ Mserver < /tmp/hello.mil Monet Database Server V4.3.15 Copyright (c) 1993-2004, CWI. All rights reserved. compiled for i686-pc-linux-gnu/32bit; dynamically linked. monet>[ "hello" ] monet>01:01:57 manegold@draco:~/Monet/4.3/MonetDB $ Mserver < /tmp/hello-M.mil Monet Database Server V4.3.15 Copyright (c) 1993-2004, CWI. All rights reserved. compiled for i686-pc-linux-gnu/32bit; dynamically linked. "onet>!ERROR: "print("hello"); ! ^ ! can't help you here, sorry. monet>01:02:01 manegold@draco:~/Monet/4.3/MonetDB $ Mserver /tmp/hello.mil Monet Database Server V4.3.15 Copyright (c) 1993-2004, CWI. All rights reserved. compiled for i686-pc-linux-gnu/32bit; dynamically linked. [ "hello" ] monet>quit; quit; 01:02:09 manegold@draco:~/Monet/4.3/MonetDB $ Mserver /tmp/hello-M.mil Monet Database Server V4.3.15 Copyright (c) 1993-2004, CWI. All rights reserved. compiled for i686-pc-linux-gnu/32bit; dynamically linked. "ERROR: "print("hello"); ! ^ ! can't help you here, sorry. monet>quit; quit; 01:02:17 manegold@draco:~/Monet/4.3/MonetDB $ ## Comment 294 Date: 2004-02-27 10:53:29 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Fixed by normalizing all line endings before data is given to the parser. We now recognize Unix, Windows and Mac line endings (LF, CRLF, and CR respectively). Before CR was elided only on Windows, and only when reading in "line mode" (i.e. not from MAPI). ## Comment 295 Date: 2004-03-04 18:51:05 +0100 From: @drstmane Logged In: YES user_id=572415 Re-opened this bug-report as the the problem still (again?) occurs in one case, namely if a mil-srcipt with Ctrl-M (CR, ^M) is given to Mserver on the commandline; all other cases seem to work, now: 18:49:19 manegold@draco:~/Monet/4.3/MonetDB $ cat -v /tmp/hello-M.mil print("hello");^M 18:49:23 manegold@draco:~/Monet/4.3/MonetDB $ Mserver /tmp/hello-M.mil Monet Database Server V4.3.16-rc03 Copyright (c) 1993-2004, CWI. All rights reserved. compiled for i686-pc-linux-gnu/32bit; dynamically linked. "ERROR: "print("hello"); ! ^ ! can't help you here, sorry. monet>quit; quit; 18:49:31 manegold@draco:~/Monet/4.3/MonetDB $ Mserver < /tmp/hello-M.mil Monet Database Server V4.3.16-rc03 Copyright (c) 1993-2004, CWI. All rights reserved. compiled for i686-pc-linux-gnu/32bit; dynamically linked. monet>[ "hello" ] 18:49:35 manegold@draco:~/Monet/4.3/MonetDB $ MapiClient /tmp/hello-M.mil [ "hello" ] >\q 18:49:55 manegold@draco:~/Monet/4.3/MonetDB $ MapiClient </tmp/hello-M.mil [ "hello" ] 18:49:58 manegold@draco:~/Monet/4.3/MonetDB $ ## Comment 296 Date: 2004-03-04 21:09:55 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Re-closed the report. There was a totally unrelated piece of code that read in modules and files mentioned on the command line. This code now also deals with \r. ## Comment 297 Date: 2005-10-06 11:49:03 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: ALREADY IN TESTWEB tests/BugsViaSourgeforce/ID.905495c.* tests/BugsViaSourgeforce/ID.905495s.* ## Comment 298 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 905495 at http://sourceforge.net/support/tracker.php?aid=905495
MIL parser cannot handle Ctrl-M (CR)
https://api.github.com/repos/MonetDB/MonetDB/issues/59/comments
0
2020-11-30T08:02:48Z
2024-06-27T10:51:25Z
https://github.com/MonetDB/MonetDB/issues/59
753,250,649
59
[ "MonetDB", "MonetDB" ]
Date: 2004-02-26 04:12:31 +0100 From: @menzowindhouwer To: GDK devs &lt;<bugs-common>&gt; Version: -- development Last updated: 2004-03-02 06:56:18 +0100 ## Comment 290 Date: 2004-02-26 16:12:31 +0100 From: @menzowindhouwer If you use RETURN within a WHILE loop, it doesn't exit the PROC, but breaks only out of the loop. Example (also in the attached file): 8<----- PROC test() := { WHILE (true) { print("good"); RETURN; } print("bad"); } test; 8<----- Results in: [ "good" ] [ "bad" ] ## Comment 291 Date: 2005-10-06 11:41:54 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: TEST ADDED / SUCCESS tests/BugDay_2005-10-06_4.8/return_in_while.SF-905116.* ## Comment 292 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 905116 at http://sourceforge.net/support/tracker.php?aid=905116 The original assignee of this bug does not have an account here. Reassigning to the default assignee for the component, bugs-common@monetdb.org. Previous assignee was nobody@users.sourceforge.net.
RETURN within WHILE breaks the loop instead of the PROC
https://api.github.com/repos/MonetDB/MonetDB/issues/58/comments
0
2020-11-30T08:02:46Z
2024-06-28T13:37:40Z
https://github.com/MonetDB/MonetDB/issues/58
753,250,620
58
[ "MonetDB", "MonetDB" ]
Date: 2004-02-25 08:46:31 +0100 From: @mlkersten To: @sjoerdmullender Version: -- development Last updated: 2004-03-24 04:20:45 +0100 ## Comment 285 Date: 2004-02-25 08:46:31 +0100 From: @mlkersten Consider the following actions: >Mserver monet>module(sql_server); monet> CNTRL-D System will not shutdown while a quit() command is implied ## Comment 286 Date: 2004-03-22 14:38:22 +0100 From: @mlkersten Logged In: YES user_id=490798 A solution is needed, see also the Windows report on this issue. 919536 ## Comment 287 Date: 2004-03-24 16:20:45 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Fixed by simulating input of "quit();" upon encountering end of file. See log for revision 1.57.2.4 of monet_client.mx. ## Comment 288 Date: 2005-10-06 11:23:02 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: TEST ADDED/SUCCESS src/test/BugDay_2005-10-06_2.8/mserver_exit_at_EOF-SQ.904042.* ## Comment 289 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 904042 at http://sourceforge.net/support/tracker.php?aid=904042
exit Mserver upon cntrl-d
https://api.github.com/repos/MonetDB/MonetDB/issues/57/comments
0
2020-11-30T08:02:43Z
2024-06-27T10:51:23Z
https://github.com/MonetDB/MonetDB/issues/57
753,250,594
57
[ "MonetDB", "MonetDB" ]
Date: 2004-02-25 08:21:23 +0100 From: @mlkersten To: @njnes Version: -- development Last updated: 2006-12-04 03:51:26 +0100 ## Comment 272 Date: 2004-02-25 08:21:23 +0100 From: @mlkersten The script below is a snippet of a larger program where the table called tapestry has been filled with a few million elements. Problem: the delete operation marks the tuples as being removed, but the associated space is not reclaimed. This is correct for persistent tables, but not for temporary ones. create table tmp(int i, int j); insert into tmp select * from tapestry; delete from tmp; insert into tmp select * from tapestry; ## Comment 273 Date: 2004-05-11 16:25:05 +0200 From: @mlkersten Logged In: YES user_id=490798 Partial solution? you can detect that the end-result of a temporary table is empty, which means you can throw away everything and re-create an empty one. ## Comment 274 Date: 2004-05-11 17:16:01 +0200 From: @grobian Logged In: YES user_id=963970 CREATE TEMPORARY TABLE tmp(int i, int j) perhaps? That could suggest some different behaviour on updates/deletes/inserts. Only side constraint is that a temporary table will stop existing when the associated connection/session is closed. ## Comment 275 Date: 2004-05-11 17:26:21 +0200 From: @njnes Logged In: YES user_id=43556 real TEMPORARY tables exist and are cleanup at the end. They also do not need 'update' bats. Problem is that deletes are implemented as 'mark deleted', where mark deleted equals table bat insert all deleted values and nilify all values in the columns. So clearly the temp tables aren't optimal too. ## Comment 276 Date: 2004-05-11 17:46:15 +0200 From: @njnes Logged In: YES user_id=43556 for temp and just created tables a delete all (delete from x), will simply clear all values. ## Comment 277 Date: 2005-10-06 11:30:36 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / POSTPONED - testing what happens in case of a fulll disk is hard to do automatically in Mtest - general check for left-over BATs should be added to Mtest itself - set priority to 9 to keep us reminded ## Comment 278 Date: 2005-11-06 10:46:26 +0100 From: @drstmane Logged In: YES user_id=572415 BugDay_2005-10-06: "left-overs" are now marked as "pending" ## Comment 279 Date: 2005-11-21 04:20:16 +0100 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; ---- Original comment by: sf-robot@users.sourceforge.net ---- Logged In: YES user_id=1312539 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ## Comment 280 Date: 2006-11-22 04:20:05 +0100 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; ---- Original comment by: sf-robot@users.sourceforge.net ---- Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 365 days (the time period specified by the administrator of this Tracker). ## Comment 281 Date: 2006-11-29 10:06:50 +0100 From: @drstmane Logged In: YES user_id=572415 Originator: NO over-ruling "sf-robot": re-set to "Pending" since adding a proper test has neither been done nor finally been discarded, yet. User (submitter) & developer (assignee), please check, again. ## Comment 282 Date: 2006-12-04 15:51:26 +0100 From: @njnes Logged In: YES user_id=43556 Originator: NO Writing a script for checking the size of a column after a clear call isn't possible (at least not easy). So we will not create a test script for this. ## Comment 283 Date: 2006-12-04 18:01:35 +0100 From: @mlkersten Logged In: YES user_id=490798 Originator: YES No test included. ## Comment 284 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 904025 at http://sourceforge.net/support/tracker.php?aid=904025
Dealing with temporary tables
https://api.github.com/repos/MonetDB/MonetDB/issues/56/comments
0
2020-11-30T08:02:41Z
2024-06-27T10:51:22Z
https://github.com/MonetDB/MonetDB/issues/56
753,250,560
56
[ "MonetDB", "MonetDB" ]
Date: 2004-02-22 09:57:57 +0100 From: @mlkersten To: @njnes Version: -- development Last updated: 2006-12-04 03:49:00 +0100 ## Comment 264 Date: 2004-02-22 09:57:57 +0100 From: @mlkersten BATs are currently removed only at the end of a session. Also for those associated with temporary SQL tables that have been explicitly dropped during the session. This may cause severe space overhead. Solution: check in the 'drop table' command if the BAT had a persistent status, otherwise immediately release the resources. ## Comment 265 Date: 2005-10-06 11:30:13 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / POSTPONED - testing what happens in case of a fulll disk is hard to do automatically in Mtest - general check for left-over BATs should be added to Mtest itself - set priority to 9 to keep us reminded ## Comment 266 Date: 2005-11-06 10:45:44 +0100 From: @drstmane Logged In: YES user_id=572415 BugDay_2005-10-06: "left-overs" are now marked as "pending" ## Comment 267 Date: 2005-11-21 04:20:16 +0100 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; ---- Original comment by: sf-robot@users.sourceforge.net ---- Logged In: YES user_id=1312539 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ## Comment 268 Date: 2006-11-22 04:20:05 +0100 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; ---- Original comment by: sf-robot@users.sourceforge.net ---- Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 365 days (the time period specified by the administrator of this Tracker). ## Comment 269 Date: 2006-11-29 10:06:43 +0100 From: @drstmane Logged In: YES user_id=572415 Originator: NO over-ruling "sf-robot": re-set to "Pending" since adding a proper test has neither been done nor finally been discarded, yet. User (submitter) & developer (assignee), please check, again. ## Comment 270 Date: 2006-12-04 15:49:00 +0100 From: @njnes Logged In: YES user_id=43556 Originator: NO added leaks directory of tests. These now test for leaking bats within a session and over sessions (with server restart). ## Comment 271 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 902051 at http://sourceforge.net/support/tracker.php?aid=902051
SQL transactions
https://api.github.com/repos/MonetDB/MonetDB/issues/55/comments
0
2020-11-30T08:02:38Z
2024-06-27T10:51:22Z
https://github.com/MonetDB/MonetDB/issues/55
753,250,528
55
[ "MonetDB", "MonetDB" ]
Date: 2004-02-22 09:36:36 +0100 From: @mlkersten To: @njnes Version: -- development Last updated: 2007-02-02 09:29:25 +0100 ## Comment 254 Date: 2004-02-22 09:36:36 +0100 From: @mlkersten Currently the log with changes to the BATs are retained forever, i.e. until the database owner explicitly removes the files. At least a warning should be issued at server restart to checkpoint the database and cleanup. Likewise, redoing the log file may take several minutes, about which the user should be warned with a message. To guard against a full disk, a separate thread or process (Mguardian?) should initiate checkpoints where appropriate and/or compress the log file. In the meantime, sql_server module should provide the following operations: sqlLogStatus() - summarizes available logs and disk space sqlCheckpoint("backup location")- to safe DB sqlCompact() - to remove all log records without persistent bat ## Comment 255 Date: 2004-05-07 23:00:12 +0200 From: @njnes Logged In: YES user_id=43556 a log manager thread is now added. This thread check every minute if there were changes, if so the bats are made persistent and a commit is done, after which the log files are discarded (removed) ## Comment 256 Date: 2005-10-06 11:29:51 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: CLAIMED BY sjoerd BugDay_2005-10-06: NO TEST / POSTPONED - testing what happens in case of a fulll disk is hard to do automatically in Mtest - general check for left-over BATs should be added to Mtest itself - set priority to 9 to keep us reminded ## Comment 257 Date: 2005-11-06 10:44:52 +0100 From: @drstmane Logged In: YES user_id=572415 BugDay_2005-10-06: "left-overs" are now maked as "pending" ## Comment 258 Date: 2005-11-21 04:20:15 +0100 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; ---- Original comment by: sf-robot@users.sourceforge.net ---- Logged In: YES user_id=1312539 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ## Comment 259 Date: 2006-11-22 04:20:05 +0100 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; ---- Original comment by: sf-robot@users.sourceforge.net ---- Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 365 days (the time period specified by the administrator of this Tracker). ## Comment 260 Date: 2006-11-29 10:06:36 +0100 From: @drstmane Logged In: YES user_id=572415 Originator: NO over-ruling "sf-robot": re-set to "Pending" since adding a proper test has neither been done nor finally been discarded, yet. User (submitter) & developer (assignee), please check, again. ## Comment 261 Date: 2006-12-04 18:51:32 +0100 From: @mlkersten Logged In: YES user_id=490798 Originator: YES Original submitter accepts the resolution. ## Comment 262 Date: 2007-02-02 09:29:25 +0100 From: @njnes Logged In: YES user_id=43556 Originator: NO A test for a log running out of diskspace may cause other problems (the OS may have problems with this), so stable output will be hard. Therefor we don't add a test!. ## Comment 263 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 902043 at http://sourceforge.net/support/tracker.php?aid=902043
Log manager
https://api.github.com/repos/MonetDB/MonetDB/issues/54/comments
0
2020-11-30T08:02:35Z
2024-06-27T10:51:21Z
https://github.com/MonetDB/MonetDB/issues/54
753,250,484
54
[ "MonetDB", "MonetDB" ]
Date: 2004-02-19 12:42:21 +0100 From: @mlkersten To: @njnes Version: -- development Last updated: 2004-02-25 03:44:42 +0100 ## Comment 249 Date: 2004-02-19 12:42:21 +0100 From: @mlkersten Following script shows Monet errors on syntactic correct statements and possibly a problem with 'insert into' after a deletion of all tuples in a table [mk@orion experiments]$ MapiClient -port 45123 -u monetdb -P monetdb -l sql sql> create table RKB( head int(9) unique, tail int(9)); sql> create table RKA( head int(9) unique, tail int(9)); sql> create table tapestry( a0 int(9) unique, a1 int(9)); sql> insert into RKA values(0,0); sql> insert into RKA values(1,360); sql> insert into RKA values(1023,864); sql> insert into RKB ---> select head+0, tail+0 ---> from RKA; sql> update RKB set tail=(tail*37) % 1024; sql> update RKB set tail=(tail*7) % 1024; sql> insert into tapestry ---> select R0.head, R0.tail ---> from RKB R0; sql> drop table _tmp; !Drop Table, table _tmp unknown sql> create table _tmp( a0 int(9) unique, a1 int(9)); sql> insert into _tmp select * from tapestry where a1>=0 and a1 <=1; sql> delete from _tmp; sql> insert into _tmp select * from tapestry where a1>=0 and a1 <=1; !ERROR: interpret: no matching MIL operator to 'uselect(BAT[void,int], BAT[void,int], BAT[void,int], bit, bit)'. !MAYBE YOU MEAN: ! uselect(BAT[any::1,any::2], any::2) : BAT[any::1,void] ! uselect(BAT[any::1,any::2], any::2, any::2, bit, bit) : BAT[any::1,void] ! uselect(BAT[any::1,any::2], any::2, any::2) : BAT[any::1,void] !ERROR: interpret: no matching MIL operator to 'uselect(BAT[void,int], BAT[void,int], BAT[void,int], bit, bit)'. !MAYBE YOU MEAN: ! uselect(BAT[any::1,any::2], any::2) : BAT[any::1,void] ! uselect(BAT[any::1,any::2], any::2, any::2, bit, bit) : BAT[any::1,void] ! uselect(BAT[any::1,any::2], any::2, any::2) : BAT[any::1,void] sql> delete from _tmp; ## Comment 250 Date: 2004-02-19 12:49:22 +0100 From: @drstmane Logged In: YES user_id=572415 probably the same "a0", "a1" / namespace problem as in 900198 "SQL select error" Stefan. ## Comment 251 Date: 2004-02-25 03:44:42 +0100 From: @drstmane Logged In: YES user_id=572415 Name-space bug has been fixed by Niels. Related optimizer bug has been fixed by Stefan. ## Comment 252 Date: 2005-10-06 10:40:48 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06:: ALREADY IN TESTWEB: src/test/bugs/insert_update_arith-bug-sf-900206.sql ## Comment 253 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 900206 at http://sourceforge.net/support/tracker.php?aid=900206
SQL 'delete from _tmp' error
https://api.github.com/repos/MonetDB/MonetDB/issues/53/comments
0
2020-11-30T08:02:32Z
2024-06-27T10:51:20Z
https://github.com/MonetDB/MonetDB/issues/53
753,250,438
53
[ "MonetDB", "MonetDB" ]
Date: 2004-02-19 12:35:52 +0100 From: @mlkersten To: @njnes Version: -- development Last updated: 2004-02-25 03:44:01 +0100 ## Comment 244 Date: 2004-02-19 12:35:52 +0100 From: @mlkersten The script below returns an empty set on the second select create table tst( a0 int unique, a1 int); insert into tst values(1,1); insert into tst values(2,2); select * from tst; select * from tst where a1>=0 and a1 <=3; ## Comment 245 Date: 2004-02-19 12:48:06 +0100 From: @drstmane Logged In: YES user_id=572415 found it (though not solved, yet): with attributes 'b0,b1' instead of 'a0,a1', it works fine: ======== sql> create table tst2( b0 int unique, b1 int); sql> insert into tst2 values(1,1); sql> insert into tst2 values(2,2); sql> select * from tst2; b0, b1 name int, intyp name 2, tuplecount 18, id [ 1, 1 ] [ 2, 2 ] sql> select * from tst2 where b0>=0 and b1<=3; b0, b1 name int, int type 2, tuplecount 19, id [ 1, 1 ] [ 2, 2 ] ======== seem that the column names "a0" & "a1" clash with variable/parameter names used in the procs that SQL generates for the queries: ======== sql> set explain="mil"; sql> select * from tst2 where b0>=0 and b1<=3; statement name string type 23 tuplecount 20 id [ "a0 := sht(\"0\");" ] [ "a1 := sht(\"3\");" ] [ "{" ] [ "var s8 := mvc_bind(myc, \"sys\", \"tst2\", \"b0\", 0); tst2" ] [ "var s10 := a0;" ] [ "var s9 := lng(s10);" ] [ "var s7 := s8.uselect(s9, lng(nil));" ] [ "var s12 := mvc_bind(myc, \"sys\", \"tst2\", \"b1\", 0); tst2" ] [ "var s14 := a1;" ] [ "var s13 := lng(s14);" ] [ "var s11 := s12.uselect(lng(nil), s13);" ] [ "var s6 := semijoin(s7, s11);" ] [ "var s15 := oid(\"0@0\");" ] [ "var s5 ark(s6, s15);" ] [ "var s4 := s5.reverse;" ] [ "var s3 4.join(s8);" ] [ "var s16 := s4.join(s12);" ] [ "var s1 := mvc_result_table(myc, 2, s3);" ] [ "mvc_result_column(myc, \"b0\", \"int\", 19, 0, s3);" ] [ "mvc_result_column(myc, \"b1\", \"int\", 19, 0, s16);" ] [ "mvc_export_result(myc, Output, s1);" ] [ "mvc_export_table(myc, Output, s1, 0, int(reply_size));" ] [ "}" ] sql> select * from tst where a1>=0 and a1 <=3; statement name string type 17 tuplecount 21 id [ "a0 := sht(\"0\");" ] [ "a1 := sht(\"3\");" ] [ "{" ] [ "var s7 := mvc_bind(myc, \"sys\", \"tst\", \"a1\", 0); tst" ] [ "var s8 := mvc_bind(myc, \"sys\", \"tst\", \"a0\", 0); tst" ] [ "var s6 := s7.uselect(s8, s7, TRUE, TRUE);" ] [ "var s9 := oid(\"0@0\");" ] [ "var s5 := mark(s6, s9);" ] [ "var s4 := s5.reverse;" ] [ "var s3 := s4.join(s8);" ] [ "var s10 := s4.join(s7);" ] [ "var s1 := mvc_result_table(myc, 2, s3);" ] [ "mvc_result_column(myc, \"a0\", \"int\", 19, 0, s3);" ] [ "mvc_result_column(myc, \"a1\", \"int\", 19, 0, s10);" ] [ "mvc_export_result(myc, Output, s1);" ] [ "mvc_export_table(myc, Output, s1, 0, int(reply_size));" ] [ "}" ] sql> ========= well, now it's Niels' turn ;-) BTW, I expect similar problems in case someone names his tables of columns s0, s1, s2, ... |-( in other words, we need something like separate namespaces... Stefan. ## Comment 246 Date: 2004-02-25 03:44:01 +0100 From: @drstmane Logged In: YES user_id=572415 Name-space bug has been fixed by Niels. Related optimizer bug has been fixed by Stefan. ## Comment 247 Date: 2005-10-06 10:36:08 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: Done. test script available as src/test/bugs/create_insert_select-bug-sf-900198.sql ## Comment 248 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 900198 at http://sourceforge.net/support/tracker.php?aid=900198
SQL select error
https://api.github.com/repos/MonetDB/MonetDB/issues/52/comments
0
2020-11-30T08:02:28Z
2024-06-27T10:51:19Z
https://github.com/MonetDB/MonetDB/issues/52
753,250,391
52
[ "MonetDB", "MonetDB" ]
Date: 2004-02-18 02:59:21 +0100 From: Giel &lt;<gieldn>&gt; To: Peter Boncz &lt;<boncz>&gt; Version: -- development Last updated: 2004-03-14 09:50:07 +0100 ## Comment 240 Date: 2004-02-18 14:59:21 +0100 From: Giel &lt;<gieldn>&gt; When multiplexing a procedure which multiplexes an erronous procedure, execution of the second multiplexor halts without any output. An example: b := new(int, int); b.insert(1, 1); b.insert(2, 2); PROC multi1(int i) := { [multi2](b); return(i); } erronous procedure PROC multi2(int i) := { b.find(10); return(i); } When the erronous procedure is multiplexed ([multi2](b)), an error is displayed. When the wrapping procedure is multiplexed ([multi1](b)), the execution of multi2 is stopped after the error, without any warnings. The command terminates normally. ## Comment 241 Date: 2004-03-14 21:50:07 +0100 From: @peterboncz Logged In: YES user_id=591107 this is a feature an erroneous multiplex on a large BAT may generate millions of errors. ## Comment 242 Date: 2005-10-06 10:30:42 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 BugDay_2005-10-06: Done test script added as tests/BugDay_2005-10-06_4.8/erroneous_multiplex.SF-899586.milS Note: It seems a change of heart has taken place since this bug was closed. The call to [multi1](b) now *does* produce an error. ## Comment 243 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 899586 at http://sourceforge.net/support/tracker.php?aid=899586
Nested multiplexing suppresses errors
https://api.github.com/repos/MonetDB/MonetDB/issues/51/comments
0
2020-11-30T08:02:25Z
2024-06-28T13:37:40Z
https://github.com/MonetDB/MonetDB/issues/51
753,250,342
51
[ "MonetDB", "MonetDB" ]
Date: 2004-02-17 09:14:51 +0100 From: @mlkersten To: Peter Boncz &lt;<boncz>&gt; Version: -- development Last updated: 2004-02-17 10:12:07 +0100 ## Comment 236 Date: 2004-02-17 09:14:51 +0100 From: @mlkersten Expression handling is assymetric in parameter passing monet>s:=string("hello",0,2); monet>print(s); [ "he" ] monet>s:=string("hello",0,2+1); monet>print(s); [ "hel" ] monet>s:=string("hello",0,5-1); !ERROR: "s:=string("hello",0,5-1);" ! ^ ! can't help you here, sorry. monet>s:= string("hello",0, (5-1)); !ERROR: "s:= string("hello",0, (5-1));" ! ^ ! can't help you here, sorry. monet>s:= string("hello",0, 5 -1); !ERROR: "s:= string("hello",0, 5 -1);" ! ^ ! can't help you here, sorry. ## Comment 237 Date: 2004-02-17 09:20:19 +0100 From: @mlkersten Logged In: YES user_id=490798 The user should use a space between - and 1 to avoid the lexical analyser to recognize it as a -1 token, which would lead to a syntax error. ## Comment 238 Date: 2005-10-06 15:40:42 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST exists BugReports/Tests/no.062.milS ## Comment 239 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 898543 at http://sourceforge.net/support/tracker.php?aid=898543
Lex handling (-1)
https://api.github.com/repos/MonetDB/MonetDB/issues/50/comments
0
2020-11-30T08:02:22Z
2024-06-28T13:38:23Z
https://github.com/MonetDB/MonetDB/issues/50
753,250,305
50
[ "MonetDB", "MonetDB" ]
Date: 2004-02-10 10:36:57 +0100 From: @mlkersten To: Stefan Manegold &lt;<Stefan.Manegold>&gt; Version: -- development Last updated: 2004-03-23 08:49:34 +0100 ## Comment 232 Date: 2004-02-10 22:36:57 +0100 From: @mlkersten The selectivity estimates for tables with >100K elements and a selectivity factor > 20% are severely hampered by the table realloc strategy. Solution. For all (larger) tables take the time to get some basic statistics, e.g. the min/max or possibly a coarse histogram. Use this information to obtain a better estimate of the result size. requires patches to gdk_batop/GDK_select* [source: Cracker experiments] ## Comment 233 Date: 2004-03-23 08:49:34 +0100 From: @drstmane Logged In: YES user_id=572415 converted to RFE 921586 ## Comment 234 Date: 2005-10-06 15:37:42 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST / NO TEST Is a performance problem ## Comment 235 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 894704 at http://sourceforge.net/support/tracker.php?aid=894704
Selectivity estimates (=> RFE #921586)
https://api.github.com/repos/MonetDB/MonetDB/issues/49/comments
0
2020-11-30T08:02:19Z
2024-06-28T13:38:22Z
https://github.com/MonetDB/MonetDB/issues/49
753,250,276
49
[ "MonetDB", "MonetDB" ]
Date: 2004-02-04 03:50:44 +0100 From: @grobian To: GDK devs &lt;<bugs-common>&gt; Version: -- development Last updated: 2004-03-11 08:53:20 +0100 ## Comment 229 Date: 2004-02-04 15:50:44 +0100 From: @grobian When using the Xeport command to achieve (the next) block from the server with multiple connections, the server seems to crash with a segmentation fault. I haven't been able to get this when using only one connection. The problem also doesn't appear when using multiple connections that do not issue Xeport. ## Comment 230 Date: 2005-10-06 15:49:17 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST / SUCCESS Tested by jdbc test Test_Cautocommit ## Comment 231 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 890471 at http://sourceforge.net/support/tracker.php?aid=890471 The original assignee of this bug does not have an account here. Reassigning to the default assignee for the component, bugs-common@monetdb.org. Previous assignee was nobody@users.sourceforge.net.
MAPI Xexport in multithreaded use gives segmentation error
https://api.github.com/repos/MonetDB/MonetDB/issues/48/comments
0
2020-11-30T08:02:16Z
2024-06-27T10:51:14Z
https://github.com/MonetDB/MonetDB/issues/48
753,250,238
48
[ "MonetDB", "MonetDB" ]
Date: 2004-01-08 06:54:47 +0100 From: @drstmane To: @sjoerdmullender Version: -- development Last updated: 2004-02-05 06:58:46 +0100 ## Comment 223 Date: 2004-01-08 18:54:47 +0100 From: @drstmane OS + compiler: RedHat Linux 9 (Kernel 2.4.20), gcc 3.2.2 & icc 7.1 SuSE Linux 8.1 (Kernel 2.4.21), gcc 3.2 Since 12.12.2003, the test src/mapi/Tests/manyMapiClients and src/mapi/examples/C/Tests/smack01 show very instable behaviour in the above systems, mostly crashing on assertions in stream, or running into a timeout. On 11.12.2003, there were no test result. Until 10.12.2003, the tests seem to have run fine. Hence, the problems might be related to some changes on 10.12.2003 and/or 11.12.2003. I have no idea, yet(?), what's is actually going wrong and/or what might have caused the problems. Strangely, 64-bit Linux (Red Hat Linux Advanced Workstation 2.1, Kernel 2.4.18, gcc 3.3.1/icc 7.1 & Debian 3.0, Kernel 2.4.23, gcc 3.3.2) seem to work fine on these tests... ## Comment 224 Date: 2004-01-16 10:46:07 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Is this resolved with my hack in MT_global_exit? ## Comment 225 Date: 2004-01-16 14:03:05 +0100 From: @drstmane Logged In: YES user_id=572415 No, unfortunately, the problem is still there, at least on RedHat Linux 9 (Kernel 2.4.20), gcc 3.2.2 & icc 7.1; it seem to have "disappeared" on SuSE Linux 8.1 (Kernel 2.4.21), gcc 3.2, though. See the TestWeb for details: http://monetdb.cwi.nl/TestWeb/Current/MonetDB/MonetDB/.mTests103/index.html ## Comment 226 Date: 2004-02-05 18:58:45 +0100 From: @drstmane Logged In: YES user_id=572415 The problem seems to have been fixed by the recent changes in the MAPI-stream/-socket handling. ## Comment 227 Date: 2005-10-06 15:34:52 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST exists Test exists as smack01 ## Comment 228 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 873203 at http://sourceforge.net/support/tracker.php?aid=873203
instable MAPI on 32-bit Linux
https://api.github.com/repos/MonetDB/MonetDB/issues/47/comments
0
2020-11-30T08:02:13Z
2024-06-27T10:51:13Z
https://github.com/MonetDB/MonetDB/issues/47
753,250,210
47
[ "MonetDB", "MonetDB" ]
Date: 2003-12-28 05:44:33 +0100 From: @mlkersten To: Peter Boncz &lt;<boncz>&gt; Version: -- development Last updated: 2004-01-06 10:47:11 +0100 ## Comment 218 Date: 2003-12-28 17:44:33 +0100 From: @mlkersten The following one-liner script when ran against MapiClient (and from Mcockpit) caused the server to hang on an internal Flex error. Perhaps related to the recent changes made by Peter in the parser? Module loaded (sql_server2) ------------------Input--------- VAR name := nil; IF (view_bbp_name.reverse.exist("address_name")) { name := bat("address_name");} ELSE { name := new(oid,str); name.rename("address_name"); name.persists(true);} --------- Mserver response------------ fatal flex scanner internal error -- end of buffer missed ## Comment 219 Date: 2004-01-06 15:02:45 +0100 From: @drstmane Logged In: YES user_id=572415 Tests MonetDB/tests/BugsViaSourgeforce/Tests/ID.866700 and sql/src/test/Tests/ID.866700 try but fail to reproduce the bug. Are the tests wrong, or has the bug been fixed? Stefan ## Comment 220 Date: 2004-01-06 22:47:11 +0100 From: @mlkersten Logged In: YES user_id=490798 Problem occurs in MapiClient sending malicious statements due to array overflow. Not critical anymore ## Comment 221 Date: 2005-10-06 15:34:18 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST exists tests/BugsViaSourgeforce/Tests/ID.866700.milC ## Comment 222 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 866700 at http://sourceforge.net/support/tracker.php?aid=866700
Flex internal error
https://api.github.com/repos/MonetDB/MonetDB/issues/46/comments
0
2020-11-30T08:02:10Z
2024-06-28T13:38:21Z
https://github.com/MonetDB/MonetDB/issues/46
753,250,169
46
[ "MonetDB", "MonetDB" ]
Date: 2003-12-18 11:12:09 +0100 From: Manfred Stienstra &lt;<dwerg>&gt; To: @sjoerdmullender Version: -- development Last updated: 2004-01-16 10:44:32 +0100 ## Comment 210 Date: 2003-12-18 11:12:09 +0100 From: Manfred Stienstra &lt;<dwerg>&gt; The following error: monet_interpreter.mx: In function `interpret_batcast': monet_interpreter.mx:1306: warning: dereferencing type-punned pointer will break strict-aliasing rules make[4]: *** [monet_interpreter.lo] Error 1 With the following version of gcc: Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/specs Configured with: /var/tmp/portage/gcc-3.3.2-r4/work/gcc-3.3.2/configure --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/3.3 --includedir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3/info --enable-shared --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu --with-system-zlib --enable-languages=c,c++,f77,objc --enable-threads=posix --enable-long-long --disable-checking --enable-cstdio=stdio --enable-clocale=generic --enable-__cxa_atexit --enable-version-specific-runtime-libs --with-gxx-include-dir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/include/g++-v3 --with-local-prefix=/usr/local --enable-shared --disable-nls --disable-multilib Thread model: posix gcc version 3.3.2 20031201 (Gentoo Linux 3.3.2-r4, propolice) ## Comment 211 Date: 2003-12-18 11:31:15 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 There is already code in configure to deal with gcc 3.3.X for this very problem. The code triggers on CC=gcc and gcc --version producing 3.3.X. So, what *exactly* is your CC variable set to? If it isn't *exactly* "gcc", you need to add -Wno-strict-aliasing yourself. ## Comment 212 Date: 2003-12-18 11:50:18 +0100 From: Manfred Stienstra &lt;<dwerg>&gt; Logged In: YES user_id=100227 dwerg@ack] monetdb) echo $CC gcc It looks like it didn't work because I had CFLAGS set to -O3 -march=athlon-xp -pipe ## Comment 213 Date: 2003-12-18 12:51:56 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Does this mean you figured out how to get it to work? Can the bug be closed then? Did you set CFLAGS at compile time or at configure time? If the former I can see how that overrides the definition of CFLAGS in the Makefiles, and how you then lost the -Wno-strict-aliasing flag. ## Comment 214 Date: 2003-12-18 16:28:57 +0100 From: Manfred Stienstra &lt;<dwerg>&gt; Logged In: YES user_id=100227 Yes, it's working now. But the CFLAGS were set at configure time. ## Comment 215 Date: 2004-01-16 10:44:32 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Closing, since I think this issue was basically pilot error. Perhaps the configure process needs even better documentation, but that would be a different bug report. ## Comment 216 Date: 2005-10-06 15:30:35 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TESTed by COMPILATION ## Comment 217 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 862156 at http://sourceforge.net/support/tracker.php?aid=862156
gcc 3.3.2 gives error during compile
https://api.github.com/repos/MonetDB/MonetDB/issues/45/comments
0
2020-11-30T08:02:07Z
2024-06-28T13:38:21Z
https://github.com/MonetDB/MonetDB/issues/45
753,250,123
45
[ "MonetDB", "MonetDB" ]
Date: 2003-12-04 09:37:52 +0100 From: @mlkersten To: @njnes Version: -- development Last updated: 2003-12-05 11:09:31 +0100 ## Comment 206 Date: 2003-12-04 21:37:52 +0100 From: @mlkersten De volgende query: SELECT * FROM a LEFT JOIN b ON a.var1 = b.id WHERE a.var1 = 'aJan'; via de Mapi.java zorgt dat de mapi eeuwig blijft hangen, en Msql geeft als uitvoer: SQL ERROR -1 4: (1) parse error at token (306): join in statement: select * from a left join in: SELECT * FROM a LEFT JOIN b ON a.var1 = b.id WHERE a.var1 = 'aJan'; Postgres geeft op deze query wel gewoon resultaten terug. Ondersteund Monet geen joins?!? ## Comment 207 Date: 2003-12-05 11:09:31 +0100 From: @njnes Logged In: YES user_id=43556 fixed in cvs scoping bug where a.* failed parser now assumes OUTER when it only findes LEFT/RIGHT/FULL ## Comment 208 Date: 2005-10-06 15:30:11 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST exists Test exists as src/test/bugs/foreignkey_leftjoin-bug-sf-854312.sql ## Comment 209 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 854312 at http://sourceforge.net/support/tracker.php?aid=854312
SQL feature missing
https://api.github.com/repos/MonetDB/MonetDB/issues/44/comments
0
2020-11-30T08:02:04Z
2024-06-27T10:51:10Z
https://github.com/MonetDB/MonetDB/issues/44
753,250,083
44
[ "MonetDB", "MonetDB" ]
Date: 2003-12-04 08:11:27 +0100 From: @mlkersten To: Peter Boncz &lt;<boncz>&gt; Version: -- development Last updated: 2003-12-11 06:37:20 +0100 ## Comment 201 Date: 2003-12-04 08:11:27 +0100 From: @mlkersten After running the script below for the 3rd time the server crashes in vfprintf after an infinite recursive module load, TBL_loadmodule line 1582 This test generates an array in the same way the RAM frontend would. The array is filled with color values, to produce a pretty picture in the SpatialView visualization. it requires the color, array, and, mmath modules to be loaded: module("color","array","mmath"); { var width := 40; var height := 30; var x_axis := grid(height,width,1,0); var y_axis := grid(1,height,width,0); var r := [abs]([int]([*]([sin]([/]([dbl](x_axis),dbl (width)/(2.0LL*M_PI))),255 .0LL))); var g := [abs]([int]([*]([sin]([/]([dbl](y_axis),dbl (height)/(2.0LL*M_PI))),25 5.0LL))); var b := [abs]([int]([*]([sin]([/]([dbl]([+] (x_axis,y_axis)),dbl(width+height) /(2.0LL*M_PI))),255.0LL))); var values := [rgb](r,g,b); Note this should be 'table', not 'print', but at present monet doesnt produce column types in the table output, hence we revert back to the plain print funciton. print(x_axis,y_axis,values); } drop("color"); drop("array"); drop("mmath"); ## Comment 202 Date: 2003-12-11 16:37:34 +0100 From: @drstmane Logged In: YES user_id=572415 Added test tests/BugsViaSourgeforce/Tests/ID.853867 in CVS. This test *successfully* runs the script 10 times (one Mserver, 10 different MapiClient sessions) without any problems. Might the bug be fixed by now? Or didn't I understand the bug report correctly? Stefan ## Comment 203 Date: 2003-12-11 18:37:20 +0100 From: @mlkersten Logged In: YES user_id=490798 The problem has been fixed by PB. It appeared to be a bug when you enter a single line statement including a module load and drop, where the module loaded also included a MIL block. it required a patch in the MIL parser. ## Comment 204 Date: 2005-10-06 15:28:09 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST / SUCCESS Test added as tests/BugDay_2005-10-06_4.9.3/Tests/Recursive_module_load.SF-853867 ## Comment 205 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 853867 at http://sourceforge.net/support/tracker.php?aid=853867
Recursive module load error
https://api.github.com/repos/MonetDB/MonetDB/issues/43/comments
0
2020-11-30T08:02:01Z
2024-06-28T13:38:20Z
https://github.com/MonetDB/MonetDB/issues/43
753,250,052
43
[ "MonetDB", "MonetDB" ]
Date: 2003-12-03 04:50:19 +0100 From: @drstmane To: Jens Teubner &lt;<teubner>&gt; Version: -- development Last updated: 2003-12-03 06:55:00 +0100 ## Comment 197 Date: 2003-12-03 16:50:19 +0100 From: @drstmane System: RedHat Linux 9, gcc-3.2.2, Sleepycat/BerkeleyDB-4.1.25 While Jens' new check for the correct signature of DB->open seems to work fine, the actual DB->open call fails on the above system when call pf-shred on an -f0.01 XMark document: manegold@draco:~/XMark $ pf-shred -v f-0.01 !ERROR: could not open DB `nsloc_dbXikeSk': Invalid argument After switching off the BerkeleyDB support/usage (configure --without-berkeleydb), it runs fine: manegold@draco:~/XMark $ pf-shred -v f-0.01 document size (serialized) 1161615 byte(s) document size (encoded) 1883248 byte(s), ~ 1.6x larger document depth 12 document nodes 1 + element nodes 17131 + attribute nodes 3917 + text nodes 31088 + comment nodes 0 + processing instruction nodes 0 = nodes 52137 encoding time 12s 148ms 476us [233us/node] Could it be that a null-pointer is no good default value for the DB_TXN parameter of BerkeleyDB-4.1.25's DB->open? ## Comment 198 Date: 2003-12-03 18:55:00 +0100 From: Jens Teubner &lt;<teubner>&gt; Logged In: YES user_id=731390 pf-shred has used the DB_TRUNCATE flag in the DB->open() call. In some versions of BerkeleyDB this will working with previously created empty files (as they had been created using mkstemp). BerkeleyDB 4. 1.25 returns the above error in that case. pf-shred will now create a temporary _directory_ and create database files using DB->open() with the DB_CREATE flag. ## Comment 199 Date: 2005-10-06 15:10:06 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TESTed by configure/COMPILATION ## Comment 200 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 853367 at http://sourceforge.net/support/tracker.php?aid=853367
BerkeleyDB support/usage broken in pf-shred
https://api.github.com/repos/MonetDB/MonetDB/issues/42/comments
0
2020-11-30T08:01:58Z
2024-06-27T10:51:08Z
https://github.com/MonetDB/MonetDB/issues/42
753,250,017
42
[ "MonetDB", "MonetDB" ]
Date: 2003-12-03 02:02:19 +0100 From: @sjoerdmullender To: @njnes Version: -- development Last updated: 2004-03-09 09:01:44 +0100 ## Comment 193 Date: 2003-12-03 14:02:19 +0100 From: @sjoerdmullender Martin wrote (14 Oct 2003): The way SQL clients are started implies that they effectively run as DBA threads on the server. This means that once a person can 'circumvent' the SQL protection scheme, he has access to everything. We have to think about alternative schemes. ## Comment 194 Date: 2004-03-09 09:01:44 +0100 From: @njnes Logged In: YES user_id=43556 grant/revoke and create/drop users had been implemented (testing is still needed) ## Comment 195 Date: 2005-10-06 15:09:05 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: NO TEST ## Comment 196 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 853263 at http://sourceforge.net/support/tracker.php?aid=853263
SQL authentication
https://api.github.com/repos/MonetDB/MonetDB/issues/41/comments
0
2020-11-30T08:01:55Z
2024-06-28T13:38:19Z
https://github.com/MonetDB/MonetDB/issues/41
753,249,971
41
[ "MonetDB", "MonetDB" ]
Date: 2003-12-03 10:08:53 +0100 From: @arjan To: @njnes Version: -- development Last updated: 2003-12-03 06:17:47 +0100 ## Comment 189 Date: 2003-12-03 10:08:53 +0100 From: @arjan latest (last night) checkout, using the queries below: CREATE TABLE aap (id BLOB); COMMIT; DROP TABLE aap; CREATE TABLE aap (id BLOB); Crashes the server: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 49156 (LWP 965)] 0x4484db71 in validate_tables (s=0x8b452b8, os=0x83bfbc8) at sql_mvc.mx:2270 2270 for (o = t->columns.set->h, p = ot->columns.set- >h; Current language: auto; currently c (gdb) bt 0 0x4484db71 in validate_tables (s=0x8b452b8, os=0x83bfbc8) at sql_mvc.mx:2270 1 0x4484dc78 in validate (tr=0x8b38b10) at sql_mvc.mx:2313 2 0x4484de53 in mvc_commit (m=0x8b38ad8, chain=0, name=0x8bc5fb0 "") at sql_mvc.mx:2368 3 0x447fd531 in mvc_commit_wrap (res=0x8b1a1e8, m=0x0, chain=0x0, name=0x0) at sql_server.mx:295 4 0x447facfb in mvc_commit_wrap_unpack608413784 (argc=4, argv=0x8bcd788) at sql_server.glue.c:170 5 0x400369dd in interpret (stk=49, lt=0x81f0bc8, res=0xbf3fb844) at monet_interpreter.mx:960 6 0x400399be in interpret_assignment (stk=49, lt=0x81ec5b0, res=0xbf3fb844) at monet_interpreter.mx:1417 7 0x400358ba in interpret (stk=49, lt=0x81ec5b0, res=0xbf3fb844) at monet_interpreter.mx:589 8 0x40039cdd in interpret_seqblock (stk=49, lt=0x81eee28, res=0xbf3fb844, scope=1) at monet_interpreter.mx:1462 9 0x40035926 in interpret (stk=48, lt=0x81eee28, res=0xbf3fb844) at monet_interpreter.mx:596 10 0x40036e60 in interpret (stk=48, lt=0x81eba98, res=0xbf3fb844) at monet_interpreter.mx:946 11 0x447feb06 in backend_interpret (procstk=0, name=0x0, args=0x0) at sql_session.mx:199 ---Type <return> to continue, or q <return> to quit--- 12 0x447fef1c in sqlexecute (be=0x8bc4530, out=0x8b39248, stk=4) at sql_session.mx:348 13 0x447ff925 in sqlclient (stk=4, lt=0x2000, res=0xbf3ffa84) at sql_session.mx:526 14 0x40035f66 in interpret (stk=4, lt=0x81e9bf0, res=0xbf3ffa84) at monet_interpreter.mx:681 15 0x400452b0 in handleRequest (t=0x404deb5c, q=0x8b45d78, res=0xbf3ffa84) at monet_queue.mx:503 16 0x400456f0 in doRequest (t=0x404deb5c, preference=0x0) at monet_queue.mx:527 17 0x400801ea in monetInterpreter (status=0xbf7fd290) at monet_process.mx:115 18 0x404f2e31 in pthread_start_thread () from /lib/libpthread.so.0 19 0x404f2eaf in pthread_start_thread_event () from /lib/libpthread.so.0 20 0x4071930a in clone () from /lib/libc.so.6 ## Comment 190 Date: 2003-12-03 18:17:47 +0100 From: @njnes Logged In: YES user_id=43556 users of blobs needed to load the blob module this is now allways done by sql_server module ## Comment 191 Date: 2005-10-06 15:07:52 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST exists Test exists as src/test/big-example.sql ## Comment 192 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 853148 at http://sourceforge.net/support/tracker.php?aid=853148
Mserver segfault (module sql_server)
https://api.github.com/repos/MonetDB/MonetDB/issues/40/comments
0
2020-11-30T08:01:52Z
2024-06-27T10:51:06Z
https://github.com/MonetDB/MonetDB/issues/40
753,249,929
40
[ "MonetDB", "MonetDB" ]
Date: 2003-12-02 07:46:25 +0100 From: Manfred Stienstra &lt;<dwerg>&gt; To: @sjoerdmullender Version: -- development Last updated: 2003-12-02 08:02:53 +0100 ## Comment 185 Date: 2003-12-02 19:46:25 +0100 From: Manfred Stienstra &lt;<dwerg>&gt; For some time now the sql cvs HEAD doesn't bootstrap because of permission problems. It works when run as root, but not as a user. I've attached the bootstrap output. ## Comment 186 Date: 2003-12-02 20:02:53 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 The bootstrap process normally removes and recreates a bunch of files. If you first run bootstrap as root and then as non-root, the second run can't remove the files that were created during the first run, and then can't overwrite them, giving the error you saw. The solution: remove everything and start over, this time as non-root. ## Comment 187 Date: 2005-10-06 15:06:36 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TESTed by bootstrap ## Comment 188 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 852790 at http://sourceforge.net/support/tracker.php?aid=852790
bootstrap doesn't work because of permission errors
https://api.github.com/repos/MonetDB/MonetDB/issues/39/comments
0
2020-11-30T08:01:49Z
2024-06-28T13:38:19Z
https://github.com/MonetDB/MonetDB/issues/39
753,249,894
39
[ "MonetDB", "MonetDB" ]
Date: 2003-12-02 04:15:32 +0100 From: @swingbit To: GDK devs &lt;<bugs-common>&gt; Version: -- development Last updated: 2003-12-02 04:57:22 +0100 ## Comment 181 Date: 2003-12-02 16:15:32 +0100 From: @swingbit To properly describe this bug a monospace font is required. Thus, I enclose a text file as attachment. ## Comment 182 Date: 2003-12-02 16:57:22 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Fixed in CVS. ## Comment 183 Date: 2005-10-06 15:05:55 +0200 From: @njnes Logged In: YES user_id=43556 ugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST / SUCCES Test added as tests/BugDay_2005-10-06_4.9.3/Tests/Confusing_error.SF-852659.milC ## Comment 184 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 852659 at http://sourceforge.net/support/tracker.php?aid=852659 The original assignee of this bug does not have an account here. Reassigning to the default assignee for the component, bugs-common@monetdb.org. Previous assignee was nobody@users.sourceforge.net.
Confusing error report in Mapi
https://api.github.com/repos/MonetDB/MonetDB/issues/38/comments
0
2020-11-30T08:01:47Z
2024-06-27T10:45:28Z
https://github.com/MonetDB/MonetDB/issues/38
753,249,862
38
[ "MonetDB", "MonetDB" ]
Date: 2003-12-01 04:58:44 +0100 From: @swingbit To: @njnes Version: -- development Last updated: 2003-12-02 09:27:59 +0100 ## Comment 177 Date: 2003-12-01 16:58:44 +0100 From: @swingbit Trying to create 2 BATs with the same name, monet> a := new(int, int).rename("a"); monet> b := new(int, int).rename("a"); leads to an error like: !ERROR: rename(<tmp_177>,a): operation failed when these commands are issued from Mserver console. Trying to do the same from MapiClient causes it to hang on the second "rename". So far I haven't found the same behaviour on other "wrong" commands. ## Comment 178 Date: 2003-12-02 09:27:59 +0100 From: @njnes Logged In: YES user_id=43556 fixed by adding newlines to mil ERROR statements ## Comment 179 Date: 2005-10-06 15:00:14 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST / SUCCESS Test added as tests/BugDay_2005-10-06_4.9.3/Tests/MapiClient_hang_on_rename.SF-852148.milC ## Comment 180 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 852148 at http://sourceforge.net/support/tracker.php?aid=852148
MapiClient hangs on "wrong" rename
https://api.github.com/repos/MonetDB/MonetDB/issues/37/comments
0
2020-11-30T08:01:43Z
2024-06-27T10:45:27Z
https://github.com/MonetDB/MonetDB/issues/37
753,249,830
37
[ "MonetDB", "MonetDB" ]
Date: 2003-12-01 03:32:51 +0100 From: @swingbit To: MonetDB4 devs &lt;<bugs-monetdb4>&gt; Version: -- development Last updated: 2003-12-01 10:44:39 +0100 ## Comment 171 Date: 2003-12-01 15:32:51 +0100 From: @swingbit Mserver crashes when module sql_server is loaded and a Mapi session is closed by "quit" command. This is the way to reproduce de bug: 1) [server side] bash$ Mserver monet>module(sql_server); 2) [client side] bash$ MapiClient mil> quit; now, either issue the "quit" command at server side or repeat step 2). In both cases, Mserver crashes with a segmentation fault. ## Comment 172 Date: 2003-12-01 17:15:06 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 I can't reproduce this. If I start Mserver/sql_server in one window and MapiClient in another and type quit; to MapiClient I get: mil> quit; MAPI = anonymous@localhost:50000 ACTION= mapi_fetch_line QUERY = quit; ERROR = Lost connection with server mil> In other words, the connection is lost, but MapiClient still lives. If I then type quit; to Mserver, it just exits without any error messages. And if instead I just start a new MapiClient and type quit to it, it gives the same message. ## Comment 173 Date: 2003-12-01 21:15:10 +0100 From: @swingbit Logged In: YES user_id=883451 Yes, I was running a very early 4.3.14 release. After an update the problem disappeared, so it was solved in between. ## Comment 174 Date: 2003-12-01 22:44:38 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Closed since nothing more to do. ## Comment 175 Date: 2005-10-06 14:54:00 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST exists Any MapiClient test will do ## Comment 176 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 852098 at http://sourceforge.net/support/tracker.php?aid=852098 The original assignee of this bug does not have an account here. Reassigning to the default assignee for the component, bugs-monetdb4@monetdb.org. Previous assignee was nobody@users.sourceforge.net.
Mserver segfault with module sql_server
https://api.github.com/repos/MonetDB/MonetDB/issues/36/comments
0
2020-11-30T08:01:41Z
2024-06-27T10:45:26Z
https://github.com/MonetDB/MonetDB/issues/36
753,249,789
36
[ "MonetDB", "MonetDB" ]
Date: 2003-11-28 01:43:45 +0100 From: @drstmane To: @njnes Version: -- development Last updated: 2003-12-02 12:11:49 +0100 ## Comment 167 Date: 2003-11-28 13:43:45 +0100 From: @drstmane Platform: INS-1 test system "win2000" OS: WindowsNT5.0 (aka Windows2000) Compiler: MSVC++6.0 On Windows, Msql crashes --- just like the C-MapiClient (see bug report 838893) --- with: Assertion failed: !s->errnr, file .\..\..\..\src\common\stream.mx, line 873 Here's a detailed session: ======== Mserver: ---------- D:\TmpDir\StM>Mserver --set monet_mod_path=D:\TmpDir\StM\MonetDB\NT\lib\MonetDB;D:\TmpDir\StM\sql\NT\lib\MonetDB --set sql_port=55555 D:\TmpDir\StM\sql\NT\lib\MonetDB\sql_server.mil Mserver --set monet_mod_path=D:\TmpDir\StM\MonetDB\NT\lib\MonetDB;D:\TmpDir\StM\sql\NT\lib\MonetDB --set sql_port=55555 D:\TmpDir\StM\sql\NT\lib\MonetDB\sql_server.mil Monet Database Server V4.3.15 Copyright (c) 1993-2003, CWI. All rights reserved. compiled for i686-pc-win32/32bit; dynamically linked. monet>clients; clients; ------------------------------------------------------------------------------------------------------------------------- client name login tree name int str str str type ------------------------------------------------------------------------------------------------------------------------- [ 0, "adm", "no asctime in WIN32", "clients()" ] [ 2, "adm", "no asctime in WIN32", "mapi_listen(int(find(<monet_environment>,\"sql_port\")),5,\"SQLclient\")" ] [ 3, "adm", "no asctime in WIN32", "mapi_listen(int(find(<monet_environment>,\"mapi_port\")),5,\"\")" ] monet>Assertion failed: !s->errnr, file .\..\..\..\src\common\stream.mx, line 889 abnormal program termination D:\TmpDir\StM> ======== Msql: ------ D:\TmpDir\StM>Msql -umonetdb -Pmonetdb --port=55555 Msql -umonetdb -Pmonetdb --port=55555 Assertion failed: !s->errnr, file .\..\..\..\src\common\stream.mx, line 873 abnormal program termination D:\TmpDir\StM> ======== See also the sql tests in the test web. ## Comment 168 Date: 2003-12-02 12:11:49 +0100 From: @drstmane Logged In: YES user_id=572415 Recent changes in (a.o. in stream.mx) seem to have fixed this bug. I can now successfully connect and disconnect with Msql on Windows. Any errors still in the test web are different errors and need a different bug report. ## Comment 169 Date: 2005-10-06 14:41:59 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST exists Examples are any sql test on windows ## Comment 170 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 850726 at http://sourceforge.net/support/tracker.php?aid=850726
Msql crashed on Windows
https://api.github.com/repos/MonetDB/MonetDB/issues/35/comments
0
2020-11-30T08:01:37Z
2024-06-27T10:45:25Z
https://github.com/MonetDB/MonetDB/issues/35
753,249,746
35
[ "MonetDB", "MonetDB" ]
Date: 2003-11-27 10:46:39 +0100 From: @menzowindhouwer To: Peter Boncz &lt;<boncz>&gt; Version: -- development CC: martin.van.dinther Last updated: 2014-04-18 18:14:01 +0200 ## Comment 162 Date: 2003-11-27 10:46:39 +0100 From: @menzowindhouwer when a script (or a command line) is parsed module commands are recognized and the modules are loaded while the MIL is parsed. When the module contains the definition of an ADT a variable containing the ADT index is created. This variable should be available already, as the MIL commands following the module load may refer to it. In the current Monet version this variable isn't available, so 'module(url);VAR u := new(void,url);' fails as the variable 'url' is unknown ... !WARNING: interpret: convert identifier 'url' to string. !ERROR: interpret: no matching MIL operator to 'new(int, str)'. !MAYBE YOU MEAN: ! new(int, int, lng) : BAT[any,any] ! new(int, int, int) : BAT[any,any] ! new(int, int) : BAT[any,any] See the test src/monet/Tests/modADTvar.milM ## Comment 163 Date: 2003-11-27 10:56:33 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Assigned to Peter. ## Comment 164 Date: 2003-12-11 00:12:18 +0100 From: @drstmane Logged In: YES user_id=572415 Bug has been fixed by Martin's and Sjoerd's recent changes in the interpreter. ## Comment 165 Date: 2005-10-06 14:40:15 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST / SUCCESS Test added as tests/BugDay_2005-10-06_4.9.3/Tests/monet_daemon.SF-623743.milS ## Comment 166 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 850137 at http://sourceforge.net/support/tracker.php?aid=850137 ## Comment 19763 Date: 2014-04-18 18:14:01 +0200 From: @mlkersten *** Bug #3475 has been marked as a duplicate of this bug. ***
ADT var not available
https://api.github.com/repos/MonetDB/MonetDB/issues/34/comments
0
2020-11-30T08:01:34Z
2024-06-27T10:45:24Z
https://github.com/MonetDB/MonetDB/issues/34
753,249,699
34
[ "MonetDB", "MonetDB" ]
Date: 2003-11-26 11:42:03 +0100 From: Manfred Stienstra &lt;<dwerg>&gt; To: @njnes Version: -- development Last updated: 2003-12-03 06:44:44 +0100 ## Comment 154 Date: 2003-11-26 23:42:03 +0100 From: Manfred Stienstra &lt;<dwerg>&gt; I was trying to get some php code to run on the MonetDB sql server, for this I created the following table: CREATE TABLE news ( id mediumint, content text, user_id int, date datetime, PRIMARY KEY (id) ); After this I inserted the following: INSERT INTO news (id, content, user_id, date) VALUES (1, 'dwerg.net word volwassen, er is eindelijk content en het voicemail archief begint al aardig vol te lopen. De commentaar en rating code voor de voicemails is ook al vrij aardig aan het vorderen. Dus dat beloofd nog wat.\r\n<br /><br />\r\nMja, het is dat ik veel te veel tijd heb en het helemaal verkeerd indeel dat het allemaal nogal lang duurt, maar in principe is het nog maar een uurtje of 6 werk om het goed te krijgen. Zoals je kan zien heb ik bij de voicemails al wat leuke knopjes gezet, en het aantal voicemails dat je in 1 keer ziet verhoogd naar 15. Poepoe.\r\n<br /><br />\r\nHet is me allemaal wat...\r\n<br /><br />\r\nMuziek: Air', 1, '2002-02-22 00:21:00'); This went terribly wrong. See the attached file for MonetDB output. ## Comment 155 Date: 2003-11-27 00:01:06 +0100 From: @njnes Logged In: YES user_id=43556 Not reproducable on current version with simple Msql frontend. Using MapiClient (sql_server2) the insert fails as multiline queries aren't supported. ## Comment 156 Date: 2003-11-27 00:07:51 +0100 From: Manfred Stienstra &lt;<dwerg>&gt; Logged In: YES user_id=100227 Do you mean the create table? My php code strips newlines, so this query works from the php code. So the actual query would be: CREATE TABLE news (id mediumint,content text,user_id int,date datetime,PRIMARY KEY (id)); ## Comment 157 Date: 2003-12-02 14:13:49 +0100 From: @njnes Logged In: YES user_id=43556 could you attach a single sql file with create and insert statements which have this affect? ## Comment 158 Date: 2003-12-03 18:44:44 +0100 From: @njnes Logged In: YES user_id=43556 fix in cvs ## Comment 159 Date: 2005-10-06 14:28:17 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST / SUCCESS New test added src/tests/news.sql ## Comment 160 Date: 2005-10-06 14:30:45 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST / SUCCESS New test added in src/tests/news.sql ## Comment 161 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 849920 at http://sourceforge.net/support/tracker.php?aid=849920
Crash on insert
https://api.github.com/repos/MonetDB/MonetDB/issues/33/comments
0
2020-11-30T08:01:31Z
2024-06-27T10:45:23Z
https://github.com/MonetDB/MonetDB/issues/33
753,249,647
33
[ "MonetDB", "MonetDB" ]
Date: 2003-11-26 12:58:10 +0100 From: @arjan To: @njnes Version: -- development Last updated: 2003-12-05 12:28:02 +0100 ## Comment 149 Date: 2003-11-26 00:58:10 +0100 From: @arjan While inserting about 30MB BLOB data doing a COMMIT after each insert, the server crashes. The blob data rotates in size from 100kb to 10MB. I have attached a bzip2'd file with the queries. gdb Backtrace: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 49156 (LWP 1069)] 0x4484a81f in void_insert_delta (b=0x0, u=0x8ee1ff0) at sql_mvc.mx:393 393 assert( b->batCacheid != u->batCacheid); Current language: auto; currently c (gdb) bt 0 0x4484a81f in void_insert_delta (b=0x0, u=0x8ee1ff0) at sql_mvc.mx:393 1 0x44851c4f in rollforward_update_table (tr=0x8c54750, ft=0x86b8328, tt=0x8c35dd8) at sql_mvc.mx:2144 2 0x44851099 in rollforward_changeset_updates (tr=0x8c54750, fs=0x87a0220, 1970-01-01 01:00:00 +0100x8392340, b=0x8392328, rollforward_updates=0x44851700 <rollforward_update_table>, rollforward_creates=0x448513d0 <rollforward_create_table>, rollforward_deletes=0x448515d0 <rollforward_drop_table>, fd=0x4484dee0 <table_dup>) at sql_mvc.mx:1948 3 0x44851cff in rollforward_update_schema (tr=0x724, fs=0x87a0208, 1970-01-01 01:00:00 +0100x0) at sql_mvc.mx:2234 4 0x44851099 in rollforward_changeset_updates (tr=0x8c54750, fs=0x8c54768, 1970-01-01 01:00:00 +0100x8392300, b=0x0, rollforward_updates=0x44851ca0 <rollforward_update_schema>, rollforward_creates=0x448516b0 <rollforward_create_schema>, rollforward_deletes=0x44851670 <rollforward_drop_schema>, fd=0x4484e090 <schema_dup>) at sql_mvc.mx:1948 5 0x44851d6e in rollforward_trans (tr=0x0) at sql_mvc.mx:2244 6 0x448520da in mvc_commit (m=0x8c54718, chain=0, name=0x8b0d2d0 "") at sql_mvc.mx:2365 7 0x44802531 in mvc_commit_wrap (res=0x0, m=0x724, chain=0x724, name=0x724 <Address 0x724 out of bounds>) at sql_server.mx:295 8 0x447ffcfb in mvc_commit_wrap_unpack859484421 (argc=4, argv=0x8502268) at sql_server.glue.c:170 9 0x40036a0d in interpret (stk=75, lt=0x8501d70, res=0xbf3fb844) at monet_interpreter.mx:934 10 0x400399ee in interpret_assignment (stk=75, lt=0x8501ca0, res=0xbf3fb844) at monet_interpreter.mx:1384 11 0x400358ea in interpret (stk=75, lt=0x8501ca0, res=0xbf3fb844) at monet_interpreter.mx:564 12 0x40039d0d in interpret_seqblock (stk=75, lt=0x8393810, res=0xbf3fb844, scope=1) at monet_interpreter.mx:1428 13 0x40035956 in interpret (stk=74, lt=0x8393810, res=0xbf3fb844) at monet_interpreter.mx:571 14 0x40036e90 in interpret (stk=74, lt=0x84fdfd8, res=0xbf3fb844) at monet_interpreter.mx:920 15 0x44803a76 in backend_interpret (procstk=1828, name=0x724 <Address 0x724 out of bounds>, args=0x0) at sql_session.mx:194 16 0x44803e8c in sqlexecute (be=0x8d06df0, out=0x8c54690, stk=4) at sql_session.mx:343 17 0x44804845 in sqlclient (stk=4, lt=0x0, res=0x0) at sql_session.mx:515 18 0x40035f96 in interpret (stk=4, lt=0x81ea9c0, res=0xbf3ffa84) at monet_interpreter.mx:656 19 0x400452e0 in handleRequest (t=0x404dfbfc, q=0x8c616e0, res=0xbf3ffa84) at monet_queue.mx:503 20 0x40045720 in doRequest (t=0x404dfbfc, preference=0x0) ---Type <return> to continue, or q <return> to quit--- at monet_queue.mx:527 ## Comment 150 Date: 2003-12-02 14:17:55 +0100 From: @njnes Logged In: YES user_id=43556 Could you try the latest sql/monet version. Last couple of days lots of memory leaks have been fixed. I could however not reproduce the error message with the bla.sql file. ## Comment 151 Date: 2003-12-05 12:28:02 +0100 From: @njnes Logged In: YES user_id=43556 fixed in cvs ## Comment 152 Date: 2005-10-06 15:51:01 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST / NO TEST Problem occurs with large input data, this will make our cvs checkouts too slow ## Comment 153 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 849327 at http://sourceforge.net/support/tracker.php?aid=849327
Mserver segfault in insert_delta
https://api.github.com/repos/MonetDB/MonetDB/issues/32/comments
0
2020-11-30T08:01:27Z
2024-06-27T10:45:22Z
https://github.com/MonetDB/MonetDB/issues/32
753,249,610
32
[ "MonetDB", "MonetDB" ]
Date: 2003-11-25 03:34:22 +0100 From: @arjan To: GDK devs &lt;<bugs-common>&gt; Version: -- development Last updated: 2003-11-25 03:42:11 +0100 ## Comment 144 Date: 2003-11-25 15:34:22 +0100 From: @arjan BLOBs did work in the SQL layer, until I submitted a segfault while inserting a large blob. This segfault was reportedly fixed, but with the most recent CVS the SQL layer crashes on inserting a very simple blob tuple in the database: create table test ( x blob, y int); -- (table creation is ok) insert into test values( blob "(5:11 FC E2 A0 0A)", 1); -- inserting this tuple crashes the server with the following message: Mserver: sql_atom.mx:141: atom_general: Assertion a->data.vtype >= 0' failed. ** GDB backtrace: ** Mserver: sql_atom.mx:141: atom_general: Assertion `a->data.vtype >= 0' failed. Program received signal SIGABRT, Aborted. [Switching to Thread 49156 (LWP 7179)] 0x4066c561 in kill () from /lib/libc.so.6 (gdb) bt 0 0x4066c561 in kill () from /lib/libc.so.6 1 0x404f6741 in pthread_kill () from /lib/libpthread.so.0 2 0x404f6a4b in raise () from /lib/libpthread.so.0 3 0x4066c314 in raise () from /lib/libc.so.6 4 0x4066d828 in abort () from /lib/libc.so.6 5 0x40665a5f in __assert_fail () from /lib/libc.so.6 6 0x44823de0 in atom_general (tpe=0x404ff000, val=0x8bc76e0 "(5:11 FC E2 A0 0A)") at sql_atom.mx:133 7 0x448408bb in sqlparse (parm=0x8bbc2b0) at sql_parser.y:1902 8 0x447ffbd4 in sqlexecute (be=0x8bc0730, out=0x8b1afd0, stk=4) at sql_session.mx:244 9 0x44800845 in sqlclient (stk=4, lt=0x404fccf4, res=0x2000) at sql_session.mx:515 10 0x40035f96 in interpret (stk=4, lt=0x81e97b0, res=0xbf3ffa84) at monet_interpreter.mx:656 11 0x400452e0 in handleRequest (t=0x404dfbfc, q=0x8b27fa8, res=0xbf3ffa84) at monet_queue.mx:503 12 0x40045720 in doRequest (t=0x404dfbfc, preference=0x0) at monet_queue.mx:527 13 0x4008021a in monetInterpreter (status=0xbf7fd290) at monet_process.mx:115 14 0x404f3e31 in pthread_start_thread () from /lib/libpthread.so.0 15 0x404f3eaf in pthread_start_thread_event () from /lib/libpthread.so.0 16 0x4071a30a in clone () from /lib/libc.so.6 ## Comment 145 Date: 2003-11-25 15:37:28 +0100 From: @arjan Logged In: YES user_id=20087 hmm, it seems the 'blob' column never gets created in the table: Msql> create table test ( x blob, y int); Msql> Msql> select * from test; ----- | y | ----- SQL no Rows affected ## Comment 146 Date: 2003-11-25 15:42:11 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 BLOB support is marginal. In order to get at least some BLOB support in the SQL server, *before* loading the module sql_server, *first* load module blob (i.e. execute module(blob); module(sql_server);). ## Comment 147 Date: 2005-10-06 14:18:23 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST / SUCCESS Test added in src/benchmarks/blob/ ## Comment 148 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 848988 at http://sourceforge.net/support/tracker.php?aid=848988 The original assignee of this bug does not have an account here. Reassigning to the default assignee for the component, bugs-common@monetdb.org. Previous assignee was nobody@users.sourceforge.net.
BLOB support broken (again)
https://api.github.com/repos/MonetDB/MonetDB/issues/31/comments
0
2020-11-30T08:01:23Z
2024-06-28T13:38:18Z
https://github.com/MonetDB/MonetDB/issues/31
753,249,564
31
[ "MonetDB", "MonetDB" ]
Date: 2003-11-12 06:32:50 +0100 From: Jens Teubner &lt;<teubner>&gt; To: @sjoerdmullender Version: -- development Last updated: 2003-12-12 12:41:09 +0100 ## Comment 139 Date: 2003-11-12 18:32:50 +0100 From: Jens Teubner &lt;<teubner>&gt; On a system with perfctr libraries available and GCC 3.2.3, configure complains checking libperfctr.h usability... no checking libperfctr.h presence... yes configure: WARNING: libperfctr.h: present but cannot be compiled configure: WARNING: libperfctr.h: check for missing prerequisite headers? configure: WARNING: libperfctr.h: proceeding with the preprocessor's result configure: WARNING: ------------------------------------ configure: WARNING: Report this to bug-autoconf@gnu. org. configure: WARNING: ------------------------------------ checking for libperfctr.h... yes Building Monet then fails. libperfctr.h uses `inline', although this is not defined in ANSI C. The Monet configure script should check for the `inline' keyword and define it to empty, if `inline' is not allowed. This is done in configure with AC_C_INLINE, but later on, compiler switches become more restrictive, and `inline' is no longer allowed. From config.log: configure:11308: gcc -c -g -O2 -ansi -std=c99 -D_POSIX_SOURCE -D_POSIX_C_SOURCE=199506L -D_XOPEN_SOURCE=500 -Wall -W -I/usr/src/linux-2.4. 20/include conftest.c >&5 In file included from /opt/gcc-3.2.3/include/linux/perfctr.h:9, from /usr/local/include/libperfctr.h:10, from configure:11369: /opt/gcc-3.2.3/include/asm/perfctr.h:55: syntax error before "unsigned" /opt/gcc-3.2.3/include/asm/perfctr.h:61: syntax error before "unsigned" /opt/gcc-3.2.3/include/asm/perfctr.h:66: syntax error before "int" /opt/gcc-3.2.3/include/asm/perfctr.h:71: syntax error before "unsigned" /opt/gcc-3.2.3/include/asm/perfctr.h:76: syntax error before "unsigned" /opt/gcc-3.2.3/include/asm/perfctr.h:81: syntax error before "unsigned" configure:11311: $? = 1 configure: failed program was: [...] | include <libperfctr.h> configure:11327: result: no ## Comment 140 Date: 2003-12-02 11:11:35 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 I just checked in a new version of configure.ag (1.82) on the HEAD branch that hopefully fixes this bug. Can you test? ## Comment 141 Date: 2003-12-12 12:41:09 +0100 From: Jens Teubner &lt;<teubner>&gt; Logged In: YES user_id=731390 Not reproducable after Sjoerd's changes. ## Comment 142 Date: 2005-10-06 13:52:26 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TESTed by COMPILATION ## Comment 143 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 840847 at http://sourceforge.net/support/tracker.php?aid=840847
libperfctr.h and ANSI C (inline)
https://api.github.com/repos/MonetDB/MonetDB/issues/30/comments
0
2020-11-30T08:01:20Z
2024-06-27T10:45:20Z
https://github.com/MonetDB/MonetDB/issues/30
753,249,528
30
[ "MonetDB", "MonetDB" ]
Date: 2003-11-12 05:22:46 +0100 From: Jens Teubner &lt;<teubner>&gt; To: Stefan Manegold &lt;<Stefan.Manegold>&gt; Version: -- development Last updated: 2003-11-27 09:14:10 +0100 ## Comment 135 Date: 2003-11-12 17:22:46 +0100 From: Jens Teubner &lt;<teubner>&gt; Build on SuSE 8.1 fails when --enable-optimize is set. $ ./configure --prefix=/somewhere/MonetDB-4.3.14c --enable-optimize ... $ make make all-recursive make[1]: Entering directory `/local_tmp/teubner2/MonetDB-4.3. 14c' Making all in src make[2]: Entering directory `/local_tmp/teubner2/MonetDB-4.3. 14c/src' Making all in utils make[3]: Entering directory `/local_tmp/teubner2/MonetDB-4.3. 14c/src/utils' Making all in Mx make[4]: Entering directory `/local_tmp/teubner2/MonetDB-4.3. 14c/src/utils/Mx' gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I. -O2 -Wall -W -O6 -fomit-frame-pointer -finline-functions -malign-loops=4 -malign-jumps=4 -malign-functions=4 -fexpensive-optimizations -funroll-all-loops -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -Werror-implicit-function-declaration -Werror -Wno-format -Wno-sign-compare -Wno-unused -DUNIX -DMX_CXX_SUFFIX=\"cc\" -c `test -f 'Mx.c' || echo './'`Mx.c cc1: warnings being treated as errors cc1: warning: -malign-loops is obsolete, use -falign-loops cc1: warning: -malign-jumps is obsolete, use -falign-jumps cc1: warning: -malign-functions is obsolete, use -falign-functions make[4]: *** [Mx.o] Error 1 make[4]: Leaving directory `/local_tmp/teubner2/MonetDB-4.3. 14c/src/utils/Mx' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/local_tmp/teubner2/MonetDB-4.3. 14c/src/utils' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/local_tmp/teubner2/MonetDB-4.3. 14c/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/local_tmp/teubner2/MonetDB-4.3. 14c' make: *** [all] Error 2 Compiler version is GCC 3.2 (coming with SuSE 8.1). Incorrectly detected by configure? Stefan has an account on our system. So he might want to reproduce the problem himself here. Just log in to titan02.inf. uni-konstanz.de. Under /local_tmp you can create as much data as you like. Just untar 4.3.14c, run bootstrap and configure as above. The make process fails at the first source file. Without --enable-optimize everything's fine. ## Comment 136 Date: 2003-11-27 21:14:10 +0100 From: @drstmane Logged In: YES user_id=572415 fixed conf/monet.m4 in main branch: fixed extraction of the pure (GCC-) version number from `$CC --version`: trailing characters are optional. GCC 3.2 on SuSE Linux 8.1 requires "-D_XOPEN_SOURCE=600" instead of "-D_XOPEN_SOURCE=500" to define "__USE_XOPEN2K" in /usr/include/features.h and hence activate the prototype of gethostname in /usr/include/unistd.h . Users of Monet_4-3-14_c that experienced the above problem should apply the attached patch to conf/monet.m4 and re-compile MonetDB (i.e., bootstrap, configure, make, make install). ## Comment 137 Date: 2005-10-06 13:51:50 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TESTed by COMPILATION ## Comment 138 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 840797 at http://sourceforge.net/support/tracker.php?aid=840797
Build on SuSE 8.1 fails with --enable-optimize
https://api.github.com/repos/MonetDB/MonetDB/issues/29/comments
0
2020-11-30T08:01:16Z
2024-06-27T10:45:19Z
https://github.com/MonetDB/MonetDB/issues/29
753,249,483
29
[ "MonetDB", "MonetDB" ]
Date: 2003-11-09 08:09:05 +0100 From: @drstmane To: @sjoerdmullender Version: -- development Last updated: 2003-12-02 11:42:41 +0100 ## Comment 131 Date: 2003-11-09 20:09:05 +0100 From: @drstmane Platform: INS-1 test system "win2000" OS: WindowsNT5.0 (aka Windows2000) Compiler: MSVC++6.0 On Windows, the C-MapiClient and the C-Mapi examples fail with "Assertion failed: !s->errnr, file .\..\..\..\src\common\stream.mx, line 777" or "Assertion failed: !s->errnr, file .\..\..\..\src\common\stream.mx, line 793" or "!ERROR mapi_reconnect: : No error" See tests src/mapi/Tests/monet_BATs src/mapi/examples/C/Tests/* src/monet/Tests/modrefcnt2 src/monet/Tests/monet_mod_cnt-copy_C src/tools/Tests/client src/tools/Tests/multiClientSeq The MapiClient.py seem to work fine, though. See test src/mapi/Tests/manyMapiClients Thanks to Marco Dekker (mmdekker@science.uva.nl) for reporting this bug (via mail to monet@cwi.nl). My apologies for not watching the test output carefully enough to detect this bug immediately when it occurred... Sjoerd, I assigned this to you to have at least a first look; if necessary, you may of course consult Martin and/or Niels. ## Comment 132 Date: 2003-12-02 11:42:41 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Recent changes in mapi seem to have fixed this bug. I can now successfully connect and disconnect a MapiClient on Windows. Any errors still in the test web are different errors and need a different bug report. ## Comment 133 Date: 2005-10-06 13:51:14 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST exists Test exists as src/mapi/Tests/monet_BATs src/mapi/examples/C/Tests/* src/monet/Tests/modrefcnt2 src/monet/Tests/monet_mod_cnt-copy_C src/tools/Tests/client src/tools/Tests/multiClientSeq ## Comment 134 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 838893 at http://sourceforge.net/support/tracker.php?aid=838893
C-Mapi does not work on Windows
https://api.github.com/repos/MonetDB/MonetDB/issues/28/comments
0
2020-11-30T08:01:13Z
2024-06-27T10:45:18Z
https://github.com/MonetDB/MonetDB/issues/28
753,249,421
28
[ "MonetDB", "MonetDB" ]
Date: 2003-11-07 03:47:07 +0100 From: Jens Teubner &lt;<teubner>&gt; To: @sjoerdmullender Version: -- development Last updated: 2004-03-14 09:32:02 +0100 ## Comment 125 Date: 2003-11-07 15:47:07 +0100 From: Jens Teubner &lt;<teubner>&gt; Well, I don't know if this is really worth being fixed, but at least you should be aware of it: javac fails here with /usr/lib/java/bin/javac -d . -classpath "" mapi/MapiException. java mapi/Mapi.java MapiClient.java mapi/Mapi.java:115: Package java.awt not found in import. import java.awt.*; ^ mapi/Mapi.java:116: Class java.applet.Applet not found in import. import java.applet.Applet; ^ ... and some more classes ... We have Blackdown Java 1.1.8v1 here (coming with SuSE 7.3). The classpath given on the command line seems to override the system default classpaths. If I compile without the classpath switch (/usr/lib/java/bin/javac -d . mapi/MapiException.java ...), everything works fine. In src/mapi/examples/java I had to add the system classpath to the classpath on the command line (/usr/lib/java/lib/classes.zip here). With Sun JDK 1.4.2, everything works fine, also with Sun JDK 1. 3.1. ## Comment 126 Date: 2004-03-14 09:32:02 +0100 From: @njnes Logged In: YES user_id=43556 it works with sun jdk 1.3 and 1.4! 1.1.18v1 is too old! ## Comment 127 Date: 2004-03-14 21:53:36 +0100 From: @njnes Logged In: YES user_id=43556 it works with sun jdk 1.3 and 1.4! 1.1.18v1 is too old! ## Comment 128 Date: 2004-03-15 20:25:48 +0100 From: @njnes Logged In: YES user_id=43556 it works with sun jdk 1.3 and 1.4! 1.1.18v1 is too old! ## Comment 129 Date: 2005-10-06 13:50:25 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TESTed by COMPILATION also the java compilation is tested by the nightly builds, we do however limit the number of supported java versions to 1.4.2 and up (currently) ## Comment 130 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 837915 at http://sourceforge.net/support/tracker.php?aid=837915
Java Classpath
https://api.github.com/repos/MonetDB/MonetDB/issues/27/comments
0
2020-11-30T08:01:10Z
2024-06-28T13:38:17Z
https://github.com/MonetDB/MonetDB/issues/27
753,249,382
27
[ "MonetDB", "MonetDB" ]
Date: 2003-11-07 02:07:58 +0100 From: Jens Teubner &lt;<teubner>&gt; To: @sjoerdmullender Version: -- development Last updated: 2003-11-07 02:38:08 +0100 ## Comment 121 Date: 2003-11-07 14:07:58 +0100 From: Jens Teubner &lt;<teubner>&gt; When compiling Monet 4.3.14c with GCC 2.95, glibc 2.2.5 (SuSE 8.0), compilation fails with gcc -DHAVE_CONFIG_H -I. -I. -I../../../.. -I. -I../../../common -I. /../../../common -O2 -Wall -W -O6 -fomit-frame-pointer -finline-functions -malign-loops=4 -malign-jumps=4 -malign-functions=4 -fexpensive-optimizations -funroll-all-loops -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -Werror-implicit-function-declaration -Werror -Wno-format -Wno-sign-compare -Wno-unused -D_REENTRANT -c Mapi.c -fPIC -DPIC -o Mapi.lo Mapi.mx: In function `mapi_store_bind': Mapi.mx:2392: implicit declaration of function `strtof' The manpage to strtof tells to include stdlib.h when using strtof. Monet's configure script checks for existence and declaration of strtof and produces two definitions in config.h: HAVE_STRTOF and HAVE_DECL_STRTOF (first one set, second not). In Mapi.mx, only HAVE_STRTOF is checked for, but not HAVE_DECL_STRTOF. ## Comment 122 Date: 2003-11-07 14:38:08 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Apply the attached diff (in the top-level directory of MonetDB: patch -p0 < Mapi-diff) to fix this problem. The problem is actually that strtof is defined in the C99 standard, but not in any earlier standards. GCC-2.95 does not know about C99, so it can't be told to compile according to that standard, and so it compiles according to the older C89 standard, and hence does not recognize strtof. ## Comment 123 Date: 2005-10-06 13:49:03 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TESTed by COMPILATION configure takes care of this ## Comment 124 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 837849 at http://sourceforge.net/support/tracker.php?aid=837849
Use of undeclared function: strtof
https://api.github.com/repos/MonetDB/MonetDB/issues/26/comments
0
2020-11-30T08:01:07Z
2024-06-27T10:45:16Z
https://github.com/MonetDB/MonetDB/issues/26
753,249,350
26
[ "MonetDB", "MonetDB" ]
Date: 2003-11-02 03:11:12 +0100 From: @drstmane To: @njnes Version: -- development Last updated: 2003-11-06 12:49:43 +0100 ## Comment 117 Date: 2003-11-02 15:11:12 +0100 From: @drstmane When an error is detected, Msql echos the whole remainder of the current SQL script instead of just the very command that did fail. See test src/tests/Tests/marcin3. (This becomes a big problem when table create fails during testing and a subsequent script containing n (hundreds/thousands) inserts (one per line) into this table. Msql then generates m = n * (n-1) / 2 lines of error output. This can be huge and fill disks ...) ## Comment 118 Date: 2003-11-06 00:49:43 +0100 From: @drstmane Logged In: YES user_id=572415 bug has been fixed by Niels ## Comment 119 Date: 2005-10-06 13:48:24 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: NO TEST added Reasons 'Msql is gone', many SQL insert tests exists with multiple errors ## Comment 120 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 834550 at http://sourceforge.net/support/tracker.php?aid=834550
error messages too long
https://api.github.com/repos/MonetDB/MonetDB/issues/25/comments
0
2020-11-30T08:01:03Z
2024-06-27T10:45:15Z
https://github.com/MonetDB/MonetDB/issues/25
753,249,299
25
[ "MonetDB", "MonetDB" ]
Date: 2003-10-29 11:39:24 +0100 From: @swingbit To: GDK devs &lt;<bugs-common>&gt; Version: -- development Duplicates: #23 Last updated: 2010-05-04 10:52:59 +0200 ## Comment 113 Date: 2003-10-29 11:39:24 +0100 From: @swingbit I had some strange results running the example coming with the distribution, sample0.java, which basically writes 2 rows [ John, 23 ] [ Mary, 23 ] and then retrieves them. The result is John is null Mary is null ^^^^ I also got many of these warnings (trace is on): "Unrecognized header tag " It seems like it get confused trying to decode the header lines. The C version works fine on this example. ## Comment 114 Date: 2003-10-30 13:04:59 +0100 From: @drstmane Logged In: YES user_id=572415 delete as it appeared twice (see 832266) ## Comment 115 Date: 2005-12-20 01:11:44 +0100 From: @drstmane Logged In: YES user_id=572415 BugDay: stmane: NO TEST / DUPLICATE ## Comment 116 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 832271 at http://sourceforge.net/support/tracker.php?aid=832271 The original assignee of this bug does not have an account here. Reassigning to the default assignee for the component, bugs-common@monetdb.org. Previous assignee was nobody@users.sourceforge.net. Bug has invalid status, setting status to "NEW". Previous status was "DELETED". ## Comment 13966 Date: 2010-05-04 10:52:59 +0200 From: @grobian *** This bug has been marked as a duplicate of bug #23 ***
header decoding in Java Mapi
https://api.github.com/repos/MonetDB/MonetDB/issues/24/comments
0
2020-11-30T08:01:00Z
2024-06-28T13:38:16Z
https://github.com/MonetDB/MonetDB/issues/24
753,249,274
24
[ "MonetDB", "MonetDB" ]
Date: 2003-10-29 11:27:46 +0100 From: @swingbit To: @mlkersten Version: -- development Last updated: 2010-05-04 10:52:59 +0200 ## Comment 106 Date: 2003-10-29 11:27:46 +0100 From: @swingbit I had some strange results running the example coming with the distribution, sample0.java, which basically writes 2 rows [ John, 23 ] [ Mary, 23 ] and then retrieves them. The result is John is null Mary is null ^^^^ I also got many of these warnings (trace is on): "Unrecognized header tag " It seems like it get confused trying to decode the header lines. The C version works fine on this example. ## Comment 107 Date: 2003-11-05 12:59:58 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Assigned to Martin. ## Comment 108 Date: 2003-12-02 11:47:19 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Is this still an issue? ## Comment 109 Date: 2003-12-02 12:34:36 +0100 From: @swingbit Logged In: YES user_id=883451 It works fine now. ## Comment 110 Date: 2003-12-02 13:09:08 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Closing. ## Comment 111 Date: 2005-10-06 13:46:22 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST exists Test exists as src/mapi/examples/java/Tests/sample* ## Comment 112 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 832266 at http://sourceforge.net/support/tracker.php?aid=832266 ## Comment 13967 Date: 2010-05-04 10:52:59 +0200 From: @grobian *** Bug #24 has been marked as a duplicate of this bug. ***
header decoding in Java Mapi
https://api.github.com/repos/MonetDB/MonetDB/issues/23/comments
0
2020-11-30T08:00:57Z
2024-06-27T10:45:13Z
https://github.com/MonetDB/MonetDB/issues/23
753,249,233
23
[ "MonetDB", "MonetDB" ]
Date: 2003-10-14 05:30:45 +0200 From: @drstmane To: Peter Boncz &lt;<boncz>&gt; Version: -- development Last updated: 2004-03-04 02:53:08 +0100 ## Comment 102 Date: 2003-10-14 17:30:45 +0200 From: @drstmane This bug has been reported by Tim Ruhl from DD: When creating an xtables-histogram on a view BAT and then removing the view BAT, the respective histogram accellerator BAT does not get removed. See the respective test in tests/BugsViaSourgeforce/Tests/ for details. ## Comment 103 Date: 2004-03-04 14:53:08 +0100 From: @drstmane Logged In: YES user_id=572415 Has been fixed by Peter. Thanks, Peter! ## Comment 104 Date: 2005-10-06 13:41:54 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST exists Test exists as tests/BugsViaSourgeforce/Tests/ID.823516.milM ## Comment 105 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 823516 at http://sourceforge.net/support/tracker.php?aid=823516
BAT leak in xtables with histogram on view
https://api.github.com/repos/MonetDB/MonetDB/issues/22/comments
0
2020-11-30T08:00:54Z
2024-06-27T10:45:12Z
https://github.com/MonetDB/MonetDB/issues/22
753,249,202
22
[ "MonetDB", "MonetDB" ]
Date: 2003-10-03 07:19:19 +0200 From: @drstmane To: Stefan Manegold &lt;<Stefan.Manegold>&gt; Version: -- development Duplicates: #20 Last updated: 2010-05-04 11:11:10 +0200 ## Comment 98 Date: 2003-10-03 19:19:19 +0200 From: @drstmane [ Peter, this is not to "urge" you, but purely for the "bookkeeping"! ] ( Sure, other volantiers are welcome to have a look and fix the bug ;-) (most probably) since Peter's "DD-sync", the output of test no.089 in tests/BugReports/Tests differs from the stable output; see attached file for details. Apparently, abort now has no immediate impact on a persistent unloaded bat, i.e., the inserted BUN is still present in the BAT after the abort. After quitting and restarting the server, however, the BUN is correcly gone. I guess, this is not correct. The inserted BUN should be gone right after the abort. PS: Peter's DDsync is wrapped in CVS-tags "BeforePetersDDsync" & "AfterPetersDDsync" ## Comment 99 Date: 2003-10-03 23:52:04 +0200 From: @drstmane Logged In: YES user_id=572415 delete bug report, as it somehow appears twice, now ... !?? ## Comment 100 Date: 2005-12-20 01:11:54 +0100 From: @drstmane Logged In: YES user_id=572415 BugDay: stmane: NO TEST / DUPLICATE ## Comment 101 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 817305 at http://sourceforge.net/support/tracker.php?aid=817305 Bug has invalid status, setting status to "NEW". Previous status was "DELETED". ## Comment 13972 Date: 2010-05-04 11:11:10 +0200 From: @grobian *** This bug has been marked as a duplicate of bug #20 ***
abort does not work as expected
https://api.github.com/repos/MonetDB/MonetDB/issues/21/comments
0
2020-11-30T08:00:51Z
2024-06-28T13:38:16Z
https://github.com/MonetDB/MonetDB/issues/21
753,249,161
21
[ "MonetDB", "MonetDB" ]
Date: 2003-10-02 06:54:28 +0200 From: @drstmane To: Peter Boncz &lt;<boncz>&gt; Version: -- development Last updated: 2010-05-04 11:11:10 +0200 ## Comment 93 Date: 2003-10-02 18:54:28 +0200 From: @drstmane [ Peter, this is not to "urge" you, but purely for the "bookkeeping"! ] ( Sure, other volantiers are welcome to have a look and fix the bug ;-) (most probably) since Peter's "DD-sync", the output of test no.089 in tests/BugReports/Tests differs from the stable output; see attached file for details. Apparently, abort now has no immediate impact on a persistent unloaded bat, i.e., the inserted BUN is still present in the BAT after the abort. After quitting and restarting the server, however, the BUN is correcly gone. I guess, this is not correct. The inserted BUN should be gone right after the abort. PS: Peter's DDsync is wrapped in CVS-tags "BeforePetersDDsync" & "AfterPetersDDsync" ## Comment 94 Date: 2003-10-04 10:36:48 +0200 From: @drstmane Logged In: YES user_id=572415 An extended version of test tests/BugReports/Tests/no.089 shows that only saved/unloaded BATs do not get aborted correctly; on unsaved/hot BATs abort seems to work correctly. Given this, it is obvious, that the following patch --- i.e., removing the check, whether a BAT is "dirty" before calling "BATundo()" in "TMabort()"; this check has been added by Peter's DDsync --- would fix this problem. ======== diff -u -r1.21 gdk_tm.mx --- src/gdk/gdk_tm.mx 5 Sep 2003 18:42:56 -0000 1.21 +++ src/gdk/gdk_tm.mx 4 Oct 2003 08:33:21 -0000 @@ -149,11 +149,9 @@ if (b == NULL) continue; BBPfix(i); - if (BATdirty(b)) { - /* BUN move-backes need a real BAT! */ - b = BBPdescriptor(i); - BATundo(b); - } + /* BUN move-backes need a real BAT! */ + b = BBPdescriptor(i); + BATundo(b); if (BBP_status(i)&BBPDELETED) { BBP_status_on(i, BBPEXISTING, "TMabort"); if (b->batPersistence != PERSISTENT) ======== I have not checked this in, yet, as I'm not sure, whether the "if (BATdirty(b))" has been added "byt accident" or for some good reason, which I don't see, yet... I hope, this helps to fix the bug. Stefan ## Comment 95 Date: 2003-10-10 08:43:49 +0200 From: @drstmane Logged In: YES user_id=572415 fixed a DDImerge bug (cf. SF bug report 816672): TMabort needs to undo changes not only in "dirty" BATs (BATdirty()), but also in BATs with "diffs" (DELTAdirty()), i.e., saved/unloaded/swapped-out BATs with differences that haven't been commit, yet. Thanks to Niels for the tip where to look. Actually, I guess, in the DELTAdirty()-case, we do not even have to load the BAT and apply the BATundo, but could rather "simply" discard the delta and revive the backup; however, I don't know (yet) how to do this, hence we stick with the current solution for the time being --- it should be correct though it might not be the most efficient way... Also extended the respective test (tests/BugReports/Tests/no.089 Peter (or Niels) could (one of) you eventually comfirm, that my fix is actually correct? Thanks! ## Comment 96 Date: 2005-10-06 13:39:46 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST exists Test exists as tests/BugReports/Tests/no.089.mil ## Comment 97 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 816672 at http://sourceforge.net/support/tracker.php?aid=816672 ## Comment 13973 Date: 2010-05-04 11:11:10 +0200 From: @grobian *** Bug #21 has been marked as a duplicate of this bug. ***
abort does not work as expected
https://api.github.com/repos/MonetDB/MonetDB/issues/20/comments
0
2020-11-30T08:00:48Z
2024-06-27T10:45:09Z
https://github.com/MonetDB/MonetDB/issues/20
753,249,131
20
[ "MonetDB", "MonetDB" ]
Date: 2003-10-02 06:44:33 +0200 From: @drstmane To: Stefan Manegold &lt;<Stefan.Manegold>&gt; Version: -- development Last updated: 2003-12-18 10:59:14 +0100 ## Comment 88 Date: 2003-10-02 18:44:33 +0200 From: @drstmane [ Peter, this is not to "urge" you, but purely for the "bookkeeping"! ] ( Sure, other volantiers are welcome to have a look and fix the bug ;-) Since Peter's "DD-sync", test src/modules/plain/Tests/xtables test seems to hang (busily!). A short look in gdb seems to indicate, that the "orderby" sub-test spends *very much* time in lines 272-278 of gdk_qsort.mx: ======== if (swap_cnt == 0) { /* Switch to insertion sort */ for (pm = (char *) a + buf->width; pm < (char *) a + MULT_WIDTH(n); pm += buf->width) for (pl = pm; pl > (char *) a && @2_@3_@4E(pl, pl - buf->width); pl -= buf->width) @1_SWAP(@3, pl, pl - buf->width); return; } ======== I had no time, yet, to check any further, bu maybe this helps locating and fixing the bug ... PS: Peter's DDsync is wrapped in CVS-tags "BeforePetersDDsync" & "AfterPetersDDsync" ## Comment 89 Date: 2003-10-02 18:46:26 +0200 From: @drstmane Logged In: YES user_id=572415 Ups, I forgot the following: I ran the xtables test outside Mtest, i.e., without time limit: ======== time Mserver src/modules/plain/Tests/xtables.milM > /tmp/xtables.out real 542m20.442s user 541m26.220s sys 0m12.490s ======== hence, it eventually finished after 9 hours (!) on my machine (non-optimized Mserver), and the output is indeed as expected (i.e., correct). ## Comment 90 Date: 2003-12-18 22:59:14 +0100 From: @drstmane Logged In: YES user_id=572415 I finally managed to locate and fix a couple of more bugs in GDKqsort[_rev], that sneaked in when "reverse" (decending) sorting was introduced --- they were "very well hidden" ... |-( Stefan ## Comment 91 Date: 2005-10-06 13:36:24 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST exists Test exists as ./src/modules/plain/Tests/xtables.milM ## Comment 92 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 816667 at http://sourceforge.net/support/tracker.php?aid=816667
xtables test hangs / takes 9 hours
https://api.github.com/repos/MonetDB/MonetDB/issues/19/comments
0
2020-11-30T08:00:46Z
2024-06-27T10:45:08Z
https://github.com/MonetDB/MonetDB/issues/19
753,249,092
19
[ "MonetDB", "MonetDB" ]
Date: 2003-10-02 06:24:20 +0200 From: @drstmane To: Stefan Manegold &lt;<Stefan.Manegold>&gt; Version: -- development Last updated: 2003-10-03 11:40:17 +0200 ## Comment 83 Date: 2003-10-02 18:24:20 +0200 From: @drstmane (most probably) since the CWI_DDI_merge, decimal(0) and decimal("0") incorreclty return nil on SunOS compiled with the native SUNWspro compiler, both, with -g and -O3: ======== Monet Database Server V4.3.13 Copyright (c) 1993-2003, CWI. All rights reserved. compiled for sparc-sun-solaris2.8/32bit; dynamically linked. monet>module(decimal); monet>decimal("0").print; [ nil ] monet>decimal(0).print; [ nil ] monet>decimal("1").print; [ 1 ] monet>decimal(1).print; [ 1 ] monet> ======== Sorry, that I didn't notice this earlier. (Assigned to Sjoerd, as I assigned my last CWI_DDI_merge related bug-report to Peter; either might take care, unless someone else volantiers ;-) ## Comment 84 Date: 2003-10-02 18:27:07 +0200 From: @drstmane Logged In: YES user_id=572415 PS: See also tests src/modules/plain/Tests/decimal src/modules/plain/Tests/aggr src/modules/plain/Tests/aggrX3 ## Comment 85 Date: 2003-10-03 23:40:17 +0200 From: @drstmane Logged In: YES user_id=572415 fix for bug-report 816653 "decimal(0) = nil on SunOS-native": Sun's native C compiler seems to treat bit-fields as unsigned, even if they are declared as "int", hence, the 16-bit "scale" element of the "decimal" struct didn't work as expected. Unfortunately, the compiler doesn't give any worning, and I found no switch to either enable signed bit-fields or force an appropiate warning. Solution: I added a macro define SCALE(d) ((int)(sht)((d)->scale)) scale that casts scale to a "sht" (signed short int), first, and thus, the highest bit gets interpreted as sign. Also added another decimal test used for debugging. ## Comment 86 Date: 2005-10-06 13:35:40 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST exists Test exists as ./src/modules/plain/Tests/decimal_debug.milM ## Comment 87 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 816653 at http://sourceforge.net/support/tracker.php?aid=816653
decimal(0) = nil on SunOS-native
https://api.github.com/repos/MonetDB/MonetDB/issues/18/comments
0
2020-11-30T08:00:43Z
2024-06-27T10:45:07Z
https://github.com/MonetDB/MonetDB/issues/18
753,249,064
18
[ "MonetDB", "MonetDB" ]
Date: 2003-09-30 11:01:08 +0200 From: @drstmane To: Peter Boncz &lt;<boncz>&gt; Version: -- development Last updated: 2004-03-17 05:48:11 +0100 ## Comment 77 Date: 2003-09-30 23:01:08 +0200 From: @drstmane Scenario: ======== An Mserver is started, loads a module (lock) that defines an atom (lock), an a transient BAT ("test") is created with that atom in the global scope. A first client connects, also (re-)loads the same module (lock) and prints the global BAT "test". Fine so far. The first client quits, again. Then, a second client connects, and tried to print the global BAT "test", but that *fails*, complaining about a BAT with *illegal* types. The respective module (lock), however, is still there with correct reference count of 1. (cf. test src/monet/Tests/modrefcnt2) History: ====== The bug seems to have sneaked in during the CWI_DDI_merge on August 6, 2003; since then, the test show a difference in the output. However, the differences disappeared with Peter's DD-sync, when the wrong error messages were incorrectly approved. ## Comment 78 Date: 2003-10-10 16:25:25 +0200 From: @drstmane Logged In: YES user_id=572415 Update: According to Peter, the current behavior is the desired one, i.e., clients are not supposed to see any modules that have been loaded in the global/adm context after the mapi-listener has been started. Hence, the error messages about the "illegal type" "lock" are indeed correct. However, for the sake of consistency (and not to confuse the user), other commands should stick to these rules, too, e.g., "loaded" should only show modules that are indeed loaded by the very client (or by adm before the mapi-listener was started), "sigs" should only work for such modules, and what about commands like "proc" and "vars", and all the "monet_*" BATs ...??? Here's still some work TODO ... ! ## Comment 79 Date: 2004-03-04 00:51:26 +0100 From: @peterboncz Logged In: YES user_id=591107 this appears to be a feature request rather than a bug report everythings works OK according to my book (module loads are client-specific) there is a distinction between 'logical module load' (i.e. things are entered in the client-specific ADT,acc,command parsing tables), and 'physical module load' (the loading of the .so, and execution of initialization scripts) what could be bothering is that the MIL procs 'loaded' and 'sigs' report on the physical status rather than the logical status. that may be confusing to some users. ## Comment 80 Date: 2004-03-17 17:48:11 +0100 From: @peterboncz Logged In: YES user_id=591107 was now fixed: loaded is client specific the othr issues - sigs: while not consistent, the current complaint is that sigs only works when the module is already loadd, so enforcing this should not have priority - vars: is stackbased and can thus *is* client-specific the 'proc' remark I do not understand. If you mean 'procs' to my best knowledge it is client-specific already. ## Comment 81 Date: 2005-10-06 13:33:16 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST exists Test exists as modrefcnt2 ## Comment 82 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 815433 at http://sourceforge.net/support/tracker.php?aid=815433
Bug in module/atom ref-counting, cf. test modrefcnt2
https://api.github.com/repos/MonetDB/MonetDB/issues/17/comments
0
2020-11-30T08:00:40Z
2024-06-28T13:38:15Z
https://github.com/MonetDB/MonetDB/issues/17
753,249,033
17
[ "MonetDB", "MonetDB" ]
Date: 2003-09-23 10:12:27 +0200 From: @mlkersten To: @mlkersten Version: -- development Last updated: 2003-12-21 10:53:44 +0100 ## Comment 71 Date: 2003-09-23 22:12:27 +0200 From: @mlkersten When starting Mserver --daemon=yes the user is forced to give an initialization file. This is too strict and can be dropped. ## Comment 72 Date: 2003-09-24 18:45:20 +0200 From: @drstmane Logged In: YES user_id=572415 Just a stupid(?) question: What can I do with an Mserver in daemon-mode that doesn't get any init/startup script? Such an Mserver has neither a console nor any mapi or other remote access facilities, hence it's very lonely and not very useful ... Thus, requiring either a console (monet_daemon=no) as a script (e.g., to start Mapi or SQL support) is IMHO not too strict, but rather healthy. Actually, it could/should(?) be even stricter as now an empty script avoid the warning an silently starts a very lonely and useless Mserver-daemon... ;-) Mserver --set monet_daemon=yes <monet-prefix>/lib/MonetDB/mapi.mil or Mserver --set monet_daemon=yes <sql-prefix>/lib/MonetDB/sql_server.mil IMHO solves the problem: Mserver get a script, and the user get a useful Mserver-daemon. ## Comment 73 Date: 2003-12-03 14:16:41 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Assigned to Martin since he should answer Stefan's questions. ## Comment 74 Date: 2003-12-21 10:53:44 +0100 From: @mlkersten Logged In: YES user_id=490798 it is considered a feature. A server should explicitly tell what frontends to support ## Comment 75 Date: 2005-10-06 13:31:32 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: NO TEST (bug invalid) ## Comment 76 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 811366 at http://sourceforge.net/support/tracker.php?aid=811366
Remove initscript constraint
https://api.github.com/repos/MonetDB/MonetDB/issues/16/comments
0
2020-11-30T08:00:38Z
2024-06-28T13:38:14Z
https://github.com/MonetDB/MonetDB/issues/16
753,248,989
16
[ "MonetDB", "MonetDB" ]
Date: 2003-03-11 05:25:05 +0100 From: Jens Teubner &lt;<teubner>&gt; To: Stefan Manegold &lt;<Stefan.Manegold>&gt; Version: -- development Last updated: 2003-03-31 01:32:28 +0200 ## Comment 65 Date: 2003-03-11 17:25:05 +0100 From: Jens Teubner &lt;<teubner>&gt; The function type() returns an integer value, representing the type of its argument and works correctly. The functions head() and tail() should do the same for the head or tail of a BAT, respectively. But they do not return an integer as specified in the online help. They return a string representation of the type. >x := new (oid, int); >x.type.print; [ 4 ] >x.head.print; [ "oid" ] >"head".help; PROC: head(BAT[any,any]) : int MODULE: sys COMPILED: by boncz on Mar 22 1998 Get head-type as an int ## Comment 66 Date: 2003-03-30 18:12:23 +0200 From: @drstmane Logged In: YES user_id=572415 The functions head() and tail() are indeed supposed to return the respective column types of a BAT as string. I fixed the help-message accordingly. The respective functions to get the head-/tail-column type as integer are htype() and ttype(). ## Comment 67 Date: 2003-03-31 13:32:28 +0200 From: @drstmane Logged In: YES user_id=572415 for the sake of completeness: set proper Resolution, Category, & Group. btw: the latter should read "MonetDB 4.3.X", there is no "MonetDB 4.7.X" (yet?) ... ## Comment 68 Date: 2005-10-04 17:51:25 +0200 From: @drstmane Logged In: YES user_id=572415 BugDay_2005-10-06: Claimed. ## Comment 69 Date: 2005-10-04 18:05:56 +0200 From: @drstmane Logged In: YES user_id=572415 BugDay_2005-10-06: Done: test script added as tests/BugDay_2005-10-06_4.9.3/Tests/return_types_of_head_and_tail.SF-701641.* ## Comment 70 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 701641 at http://sourceforge.net/support/tracker.php?aid=701641
Return types of head() and tail() do not match description
https://api.github.com/repos/MonetDB/MonetDB/issues/15/comments
0
2020-11-30T08:00:35Z
2024-06-27T10:45:04Z
https://github.com/MonetDB/MonetDB/issues/15
753,248,960
15
[ "MonetDB", "MonetDB" ]
Date: 2003-02-26 11:37:03 +0100 From: @sjoerdmullender To: Peter Boncz &lt;<boncz>&gt; Version: -- development Last updated: 2003-08-30 12:10:04 +0200 ## Comment 61 Date: 2003-02-26 11:37:03 +0100 From: @sjoerdmullender In radix.mx, function rearrange_chunks there is code that passes an int second argument to BUNindex which is then cast to BUN by the macro. The module uses ints in many places where it should probably use size_t, ptrdiff_t or oid instead to get the required range. But in this case the use of an integral type is questionable for an other reason as well. BINindex calculates the index of the BUN in the BAT. So the argument should be a BUN in the BAT. But the argument seems to be an offset already. Maybe what is meant here is just arg/BUNsize to get the BUN index? ## Comment 62 Date: 2003-08-30 12:10:04 +0200 From: @sjoerdmullender Logged In: YES user_id=43607 Seems to be fixed. ## Comment 63 Date: 2005-10-06 13:30:30 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST / COMPILATION ## Comment 64 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 693537 at http://sourceforge.net/support/tracker.php?aid=693537
radix.mx: cast to pointer from integer of different size
https://api.github.com/repos/MonetDB/MonetDB/issues/14/comments
0
2020-11-30T08:00:33Z
2024-06-27T10:43:14Z
https://github.com/MonetDB/MonetDB/issues/14
753,248,916
14
[ "MonetDB", "MonetDB" ]
Date: 2003-01-31 10:19:00 +0100 From: @sjoerdmullender To: @sjoerdmullender Version: -- development Last updated: 2009-10-02 06:07:48 +0200 ## Comment 55 Date: 2003-01-31 10:19:00 +0100 From: @sjoerdmullender The tests of the isnan / isinf / finite functions on Windows give incorrect results. The reason (or in any case, one reason) is that the method used to obtain a NaN doesn't work on Windows. The test uses log(-1.0) to obtain a NaN, however this doesn't seem to do the trick. Use the attached program to obtain the below results: Cygwin: + ./a.exe 0 0: isnan 0 isinf 0 finite 1 fpclassify 2 [0000000000000000](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0000000000000000) NAN NaN: isnan 1 isinf 0 finite 0 fpclassify 0 000000000000f87f z/z NaN: isnan 1 isinf 0 finite 0 fpclassify 0 000000000000f8ff log(-1.0) -Inf: isnan 0 isinf 1 finite 0 fpclassify 1 000000000000f0ff pow(2.0, 5000.0) Inf: isnan 0 isinf 1 finite 0 fpclassify 1 000000000000f07f pow(-2.0, 5001.0) -Inf: isnan 0 isinf 1 finite 0 fpclassify 1 000000000000f0ff Native Windows: C:\Documents and Settings\sjoerd\My Documents>x.exe 0 0: isnan 0 isinf 0 finite 1 fpclassify 64 [0000000000000000](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0000000000000000) z/z -1.IND: isnan 1 isinf 0 finite 0 fpclassify 2 000000000000f8ff log(-1.0) -1.IND: isnan 1 isinf 0 finite 0 fpclassify 2 000000000000f8ff pow(2.0, 5000.0) 1.INF: isnan 0 isinf 1 finite 0 fpclassify 512 000000000000f07f pow(-2.0, 5001.0) -1.INF: isnan 0 isinf -1 finite 0 fpclassify 4 000000000000f0ff ## Comment 56 Date: 2003-01-31 10:22:28 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 I did attacht the file, and I did check the checkmark, but somehow the file was still not attached. Bloody Windows or bloody Mozilla? ## Comment 57 Date: 2004-03-11 08:54:44 +0100 From: @njnes Logged In: YES user_id=43556 windows short comming ## Comment 58 Date: 2005-10-06 13:29:17 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST exists Test exists as src/modules/plain/Tests/mmath.milM ## Comment 59 Date: 2009-10-02 18:07:43 +0200 From: @sjoerdmullender The test output has long since been changed because the method used to produce the NaNs produces a range error instead. If I create a NaN in C and use that to test the mmath function isnan() it correctly reports that the value is a NaN. Therefore I now close this bug. ## Comment 60 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 678034 at http://sourceforge.net/support/tracker.php?aid=678034
NaN / Inf test on Windows give wrong result
https://api.github.com/repos/MonetDB/MonetDB/issues/13/comments
0
2020-11-30T08:00:30Z
2024-06-27T10:43:13Z
https://github.com/MonetDB/MonetDB/issues/13
753,248,884
13
[ "MonetDB", "MonetDB" ]
Date: 2003-01-24 04:16:41 +0100 From: @sjoerdmullender To: @sjoerdmullender Version: -- development Last updated: 2003-01-29 01:12:27 +0100 ## Comment 49 Date: 2003-01-24 16:16:41 +0100 From: @sjoerdmullender When dropping certain modules you get a crash (core dump) on IRIX. Try e.g. "module(enum);drop(enum);". The problem is caused by the fact that some modules use other modules as library and at the same time load the other module. When the module (e.g. enum) is loaded, the system loads the dependant shared libraries (in this case lib_streams.so) automatically. The module initialization code then loads that same module (through the MEL USE statement). This causes the second module to be loaded again by the system. This double loading confuses the system no end. Various solutions are possible, but first an inventory needs to be made of which modules depend on which other modules at the C level. Possible solutions are: - Partition the set of modules into groups that have interdependencies at the C level. Each group is linked into a single .so file with multiple names (hard or symbolic links). When a module is loaded, find the file, and then check, using the stat information of the file, whether it has already been loaded. If so, use the previously created handle. - Disallow inter-module dependencies at the C level. Each module is standalone. If multiple modules need the same functionality, the code should be put into a shared library that is used by all of these modules. Implicitly loaded shared object files work fine. - Disallow inter-module dependencies at the C level. If a module needs functionality from another module, it can only be accessed through indirection through the module handle, not by virtue of being linked together. ## Comment 50 Date: 2003-01-24 16:50:48 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 The following dependencies cuurrently exist (gleaned from Makefile.am): enum depends on streams salgebra depends on algebra tpcd depends on cluster unix depends on blob vector depends on mmath qt depends on uchr, bitvector, stats ddbench depends on xtables, streams, enum The following actually cause a crash when you just load and drop the module: ddbench, enum, qt, unix. ## Comment 51 Date: 2003-01-27 14:36:53 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 By not linking modules with other modules I found the following real dependencies: unix depends on blob (TYPE_blob); ddbench depends on enum (enum_chktpe); qt depends on stats (stats_report). ## Comment 52 Date: 2003-01-29 13:12:27 +0100 From: @sjoerdmullender Logged In: YES user_id=43607 Fixed. The before tag is Monet_4-3-7_BeforeModuleDependencyFix, the after tag is Monet_4-3-7_AfterModuleDependencyFix. ## Comment 53 Date: 2005-10-06 13:27:04 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST exists This bug is tested by the availability tests ## Comment 54 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 674057 at http://sourceforge.net/support/tracker.php?aid=674057
crash on IRIX when dropping certain modules
https://api.github.com/repos/MonetDB/MonetDB/issues/12/comments
0
2020-11-30T08:00:26Z
2024-06-28T13:38:13Z
https://github.com/MonetDB/MonetDB/issues/12
753,248,844
12
[ "MonetDB", "MonetDB" ]
Date: 2002-11-22 05:08:39 +0100 From: Maurice van Keulen &lt;<mvankeulen>&gt; To: Stefan Manegold &lt;<Stefan.Manegold>&gt; Version: -- development Last updated: 2002-11-22 07:37:38 +0100 ## Comment 46 Date: 2002-11-22 17:08:39 +0100 From: Maurice van Keulen &lt;<mvankeulen>&gt; Sporadically, a bug in "kintersect" is haunting me. The result of the operation is not correct. I finally managed to construct an example that reproduces the bug. The attached file contains two exported bats and a small script that imports them and performs a kintersect. The result should be empty, but somehow one element ends up in the result anyway. To make the bug visible, I try to look up the elements of the result in one of the operands of kintersect. Since it is an intersection, those values should always be there, shouldn't they? Monet Database Server V4.3.6 Copyright (c) 1993-2002, CWI. All rights reserved. compiled for i686-suse-linux/32bit; dynamically linked. monet>dr:="/local_tmp"; monet>b:=new(oid,str); monet>b.import(dr + "/b.export.txt"); monet>c:=new(oid,void); monet>c.import(dr + "/c.export.txt"); monet>d:=c.kintersect(b); monet>d@batloop { b.find($h).print; } !ERROR: CMDfind: value not found. !ERROR: CMDfind: operation failed. !ERROR: print(param 1): evaluation error. ## Comment 47 Date: 2005-10-06 13:26:02 +0200 From: @njnes Logged In: YES user_id=43556 BugDay_2005-10-06: Claimed by niels BugDay_2005-10-06: TEST exists Test exists as tests/BugsViaSourgeforce/Tests/ID.642351.milS ## Comment 48 Date: 2010-05-04 09:32:09 +0200 From: Pseudo user for Sourceforge import &lt;<sfimport>&gt; This bug was previously known as tracker item 642351 at http://sourceforge.net/support/tracker.php?aid=642351
Bug in kintersect
https://api.github.com/repos/MonetDB/MonetDB/issues/11/comments
0
2020-11-30T08:00:23Z
2024-06-27T10:43:12Z
https://github.com/MonetDB/MonetDB/issues/11
753,248,811
11