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: 2007-12-04 01:54:48 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-06-06 12:44:20 +0200
## Comment 8516
Date: 2007-12-04 13:54:48 +0100
From: @romulogoncalves
I created a new user:
CREATE USER "voc" WITH PASSWORD 'voc' NAME 'VOC_EXPLORER' SCHEMA "sys";
CREATE SCHEMA "voc" AUTHORIZATION "voc";
ALTER USER "voc" SET SCHEMA "voc";
I alter the password user:
alter user "voc" with password 'new';
And then I start a mclient:
/mclient -lsql -uvoc
Password:new
the mserver crashes:
>mserver5: /ufs/goncalve/MonetDB/MonetDB5/src/mal/mal_authorize.mx:328: AUTHcheckCredentials: Assertion `q != 9223372036854775807LL' failed.
Program received signal SIGABRT, Aborted.
[Switching to Thread 1090525504 (LWP 30871)]
0x00000039b4c30065 in raise () from /lib64/libc.so.6
(gdb)
Regards,
Romulo
## Comment 8517
Date: 2008-01-08 15:09:59 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
If I do the following patch on MonetDB5
[goncalve@amelia mal]$ cvs diff
cvs diff: Diffing .
Index: mal_authorize.mx
===================================================================
RCS file: /cvsroot/monetdb/MonetDB5/src/mal/mal_authorize.mx,v
retrieving revision 1.55
diff -u -r1.55 mal_authorize.mx
--- mal_authorize.mx 4 Dec 2007 14:31:38 -0000 1.55
+++ mal_authorize.mx 8 Jan 2008 14:07:20 -0000
@@ -627,7 +627,7 @@
p = BUNfnd(pass, &id);
assert (p != BUN_NONE);
passi = bat_iterator(pass);
- BUNinplace(pass, p, BUNhead(passi, p), hash, FALSE);
+ BUNinplace(pass, p, BUNhead(passi, p), hash, TRUE);
GDKfree(hash);
AUTHcommit();
cvs diff: Diffing Tests
cvs diff: Diffing Tests/performanceTests
[goncalve@amelia mal]$
This crash is gone.
I ask to the God father of the authorization model if he aggrees with this change?
If yes I will check in, create and approve test, and close the bug.
Regards,
Romulo
## Comment 8518
Date: 2008-01-08 15:37:10 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
problems here are:
1) I couldn't reproduce
2) Niels and I got stuck last year after finding that BUNinplace simply did the insert, but the insert finally got lost on a restart.
Debugging/fixing 2) is way beyond my expertise, time limitations and aspirations.
## Comment 8519
Date: 2008-01-08 16:01:46 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
Well, the problem is back if I restart the Mserver.
I will not commit the changes and I will leave this bug open.
## Comment 8520
Date: 2008-02-16 22:25:16 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
We used BUNinplace(b, p, BUNhead(), v, FALSE). In these cases BUNinplace can fall back to delete/insert, which means that the value to which BUNhead points could change. Now we use local variables instead.
A test should still be added.
## Comment 8521
Date: 2008-05-29 16:34:08 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
There is a test at:
sql/src/test/BugTracker/Tests/set_a_new_user_password.SF-1844050.py
with additional files:
set_a_new_user_password.SF-1844050_create_user.sql
set_a_new_user_password.SF-1844050_drop_user.sql
set_a_new_user_password.SF-1844050_select.sql
Romulo
## Comment 8522
Date: 2008-05-29 16:36:09 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
The bug is working in the stable branch, but not in the current cvs branch.
So, it will remain open...
Romulo
## Comment 8523
Date: 2008-06-06 12:44:19 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
The last problem with this bug was that in the test the second server started to quickly after the first
wasn't completely stopped. An extra delay solved this. So I'll now close this.
## Comment 8524
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1844050 at http://sourceforge.net/support/tracker.php?aid=1844050
| Set a new user password... | https://api.github.com/repos/MonetDB/MonetDB/issues/1510/comments | 0 | 2020-11-30T09:44:20Z | 2024-06-27T11:27:22Z | https://github.com/MonetDB/MonetDB/issues/1510 | 753,321,578 | 1,510 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-12-03 04:32:54 +0100
From: @grobian
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2007-12-04 02:30:45 +0100
## Comment 8511
Date: 2007-12-03 16:32:54 +0100
From: @grobian
Currently no nightly tarballs are being generated for the geom and java modules. Please add them. I suggest to make them available as:
MonetDB-geom
MonetDB-java
(filing as bug, because this disallows the monetdb-install.sh script to install Java related stuff for the current branch, whereas it used to do this, which is a regression)
## Comment 8512
Date: 2007-12-03 18:05:34 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Made last night's MonetDB-geom-{0_latest,0.1.3{,-20071203}}.tar.gz & MonetDB-java-{0_latest,1.7.1{,-20071203}}.tar.gz available by hand in the usual location(s).
Added some missing symbolic links to have the TestTools make them available automatically as of tomorrow morning.
## Comment 8513
Date: 2007-12-03 18:30:54 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
thanks!
## Comment 8514
Date: 2007-12-04 14:30:45 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Nightly built source tarballs of MonetDB-java & MonetDB-geom are now automaitcally available at
http://monetdb.cwi.nl/testing/projects/monetdb/Current/.DailyBuilds./0_latest/SourceTarBalls/
## Comment 8515
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1843414 at http://sourceforge.net/support/tracker.php?aid=1843414
| nightly builds: make geom and java repos available | https://api.github.com/repos/MonetDB/MonetDB/issues/1509/comments | 0 | 2020-11-30T09:44:18Z | 2024-06-27T11:27:21Z | https://github.com/MonetDB/MonetDB/issues/1509 | 753,321,543 | 1,509 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-12-02 06:30:20 +0100
From: mharrison <<matt_harrison>>
To: @njnes
Version: -- development
Last updated: 2007-12-02 08:36:09 +0100
## Comment 8506
Date: 2007-12-02 06:30:20 +0100
From: mharrison <<matt_harrison>>
The following bulk load fails
CREATE TABLE bulk (
num SMALLINT NOT NULL,
name VARCHAR(30) NOT NULL,
PRIMARY KEY (num)
);
/tmp/bulk2.csv
5536|'5536'
53605|'53605'
COPY 2 RECORDS INTO bulk FROM '/tmp/bulk2.csv' USING DELIMITERS '|', '\n';
Here's the error message:
!SQLException:assert:INSERT INTO: NOT NULL constraint violated for column bulk.num
I have 2 suggestions:
1. If there is a cause of the constraint failure, print it. In this case, the PK is a smallint and the value exceeds 32767. When I try and manually enter that line, I get that error.
INSERT into bulk values(32768,'53605');
!SQLException:convert:value (32768) exceeds limits of type sht
Is it possible to bubble this error up?
2. Please include a line number where the failure occurred. For a 2 line file it doesn't matter but when you have millions of entries, doing a binary search to find the failing entry gets annoying.
thanks much
-matt
## Comment 8507
Date: 2007-12-02 07:14:23 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
This is more a bug as it casts the overflowing value into a null, which isn't correct.
## Comment 8508
Date: 2007-12-02 08:17:15 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Added a test for this bug in
src/test/BugTracker/Tests/copy_overflow_null_bug.SF-1842550.sql
## Comment 8509
Date: 2007-12-02 08:36:09 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
added checks for unexpected nil values.
## Comment 8510
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1842550 at http://sourceforge.net/support/tracker.php?aid=1842550
| Better error reports on bulk load (include line num)... | https://api.github.com/repos/MonetDB/MonetDB/issues/1508/comments | 0 | 2020-11-30T09:44:15Z | 2024-06-27T11:27:20Z | https://github.com/MonetDB/MonetDB/issues/1508 | 753,321,525 | 1,508 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-12-01 01:08:06 +0100
From: mharrison <<matt_harrison>>
To: @njnes
Version: -- development
Last updated: 2007-12-01 10:10:12 +0100
## Comment 8503
Date: 2007-12-01 01:08:06 +0100
From: mharrison <<matt_harrison>>
Using a build from today, I'm still getting issues with bulk load...
CREATE TABLE bulk2 (
id NUMERIC(9, 0) NOT NULL,
fax NUMERIC(10, 0),
phone NUMERIC(10, 0),
acctnum NUMERIC(7, 0),
PRIMARY KEY (id)
);
contents of /tmp/bulk.csv:
1001||1231231234|1001
1002|1234|1231231235|1002
COPY 2 RECORDS INTO bulk2 from '/tmp/bulk.csv' USING DELIMITERS '|', '\n';
COPY 2 RECORDS INTO bulk2 from '/tmp/bulk.csv' USING DELIMITERS '|', '\n';
!SQLException:sql:decimal wrong format (|1231231234|1001)
!SQLException:sql:value |1231231234|1001 from line 0 not inserted
!SQLException:importTable:failed to import table
Timer 1.362 msec 0 rows
## Comment 8504
Date: 2007-12-01 10:10:12 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Test added too src/test/bugs/Tests/decimal_copy_into_bug.sql
Now also empty values are (again) treated as NULL values.
## Comment 8505
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1842019 at http://sourceforge.net/support/tracker.php?aid=1842019
| BULK load failing for NUMERIC columns | https://api.github.com/repos/MonetDB/MonetDB/issues/1507/comments | 0 | 2020-11-30T09:44:12Z | 2024-06-27T11:27:19Z | https://github.com/MonetDB/MonetDB/issues/1507 | 753,321,481 | 1,507 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-30 08:00:39 +0100
From: mharrison <<matt_harrison>>
To: @njnes
Version: -- development
Last updated: 2007-12-04 04:18:59 +0100
## Comment 8496
Date: 2007-11-30 20:00:39 +0100
From: mharrison <<matt_harrison>>
It appears that OFFSET with no LIMIT clause is still broken. I think the last query below should return (3,ed)...(7,fido):
sql>select * from query_users ;
+---------+----------+
|user_id |user_name |
+=========+==========+
| 1 |john |
| 2 |jack |
| 3 |ed |
| 4 |wendy |
| 5 |laura |
| 6 |ralph |
| 7 |fido |
+---------+----------+
Timer 1.049 msec 7 rows
sql>select * from query_users LIMIT 3 OFFSET 2;
+---------+----------+
|user_id |user_name |
+=========+==========+
| 3 |ed |
| 4 |wendy |
| 5 |laura |
+---------+----------+
Timer 1.378 msec 3 rows
sql>select * from query_users LIMIT 3;
+---------+----------+
|user_id |user_name |
+=========+==========+
| 1 |john |
| 2 |jack |
| 3 |ed |
+---------+----------+
Timer 1.142 msec 3 rows
sql>select * from query_users OFFSET 2;
+---------+----------+
|user_id |user_name |
+=========+==========+
| 1 |john |
| 2 |jack |
| 3 |ed |
| 4 |wendy |
| 5 |laura |
| 6 |ralph |
| 7 |fido |
+---------+----------+
Timer 1.022 msec 7 rows
## Comment 8497
Date: 2007-11-30 20:07:50 +0100
From: mharrison <<matt_harrison>>
Logged In: YES
user_id=1164236
Originator: YES
Some other dbs support LIMIT -1 in this instance....
## Comment 8498
Date: 2007-11-30 20:14:30 +0100
From: mharrison <<matt_harrison>>
Logged In: YES
user_id=1164236
Originator: YES
Some other interesting queries.... Here's a hack that appears to work (specify a large number instead of -1 or no LIMIT clause):
sql>select * from query_users LIMIT 100000 OFFSET 5;
+---------+----------+
|user_id |user_name |
+=========+==========+
| 6 |ralph |
| 7 |fido |
+---------+----------+
But if you add in a ORDER BY it fails....
sql>SELECT query_users.user_id, query_users.user_name
more>FROM query_users ORDER BY query_users.user_id
more> LIMIT 1000000 OFFSET 5
more>;
+---------+----------+
|user_id |user_name |
+=========+==========+
| 1 |john |
| 2 |jack |
| 3 |ed |
| 4 |wendy |
| 5 |laura |
| 6 |ralph |
| 7 |fido |
+---------+----------+
## Comment 8499
Date: 2007-11-30 22:13:56 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
indeed the offset without limit wasn't handled at all. Now it is. Added test to the test script
sql/src/test/bugs/Tests/offset_bug.sql
## Comment 8500
Date: 2007-12-04 06:56:37 +0100
From: mharrison <<matt_harrison>>
Logged In: YES
user_id=1164236
Originator: YES
offset without limit WITH ORDER BY still fails on Dec 3 build.
## Comment 8501
Date: 2007-12-04 16:18:59 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
indeed found another problem in the combination of offset with order by. Added this test case to the same test script.
## Comment 8502
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1841896 at http://sourceforge.net/support/tracker.php?aid=1841896
| LIMIT / OFFSET support still broken | https://api.github.com/repos/MonetDB/MonetDB/issues/1506/comments | 0 | 2020-11-30T09:44:10Z | 2024-06-27T11:27:18Z | https://github.com/MonetDB/MonetDB/issues/1506 | 753,321,443 | 1,506 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-30 03:51:19 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2007-12-01 04:03:24 +0100
## Comment 8491
Date: 2007-11-30 15:51:19 +0100
From: @romulogoncalves
The following insertion crashes Mserver5-SQL:
create temp table pp (f1 text);
insert into pp values (repeat('abcdefghijkl', 100000));
Regards,
Romulo
## Comment 8492
Date: 2007-11-30 23:09:44 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
the function definition in sql_types was incorrect. Will you add the test script?
## Comment 8493
Date: 2007-12-01 15:30:32 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
The test to this bug was added in:
sql/src/test/BugTracker/Tests/insert_text_with_repeat.SF-1841759
The Mserver5 does not crash after Niels fix. However, the insertion does not insert any tuple in the table.
I did a select over the table after the insertion and there is not tuples inserted.
So I will keep the bug open and the resolution is none.
Regards,
Romulo
## Comment 8494
Date: 2007-12-01 16:03:24 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
Because we are using a temp table (the content is destroyed after the commit)
I inserted a Start transaction to check the temp table status after the insert.
I Approved the out output for the test and the test can be closed.
Regards,
Romulo
## Comment 8495
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1841759 at http://sourceforge.net/support/tracker.php?aid=1841759
| insert text with repeat... | https://api.github.com/repos/MonetDB/MonetDB/issues/1505/comments | 0 | 2020-11-30T09:44:07Z | 2024-06-27T11:27:17Z | https://github.com/MonetDB/MonetDB/issues/1505 | 753,321,410 | 1,505 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-30 03:46:08 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2007-12-01 10:33:13 +0100
## Comment 8488
Date: 2007-11-30 15:46:08 +0100
From: @romulogoncalves
The following sql code crashes the Mserver5-SQL:
CREATE TABLE t1 (name TEXT, n INTEGER);
CREATE TABLE t2 (name TEXT, n INTEGER);
CREATE TABLE t3 (name TEXT, n INTEGER);
INSERT INTO t1 VALUES ( 'aa', 11 );
INSERT INTO t2 VALUES ( 'aa', 12 );
INSERT INTO t2 VALUES ( 'bb', 22 );
INSERT INTO t2 VALUES ( 'dd', 42 );
INSERT INTO t3 VALUES ( 'aa', 13 );
INSERT INTO t3 VALUES ( 'bb', 23 );
INSERT INTO t3 VALUES ( 'cc', 33 );
SELECT * FROM t1 FULL JOIN t2 USING (name) FULL JOIN t3 USING (name);
Regards,
Romulo
## Comment 8489
Date: 2007-12-01 10:33:13 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
crash is fixed now (removed incorrect assert).
Added test to src/test/BugTracker/Tests/full_join_crash.SF-1841754
## Comment 8490
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1841754 at http://sourceforge.net/support/tracker.php?aid=1841754
| select with full join... | https://api.github.com/repos/MonetDB/MonetDB/issues/1504/comments | 0 | 2020-11-30T09:44:04Z | 2024-06-27T11:27:16Z | https://github.com/MonetDB/MonetDB/issues/1504 | 753,321,380 | 1,504 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-30 03:38:52 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2007-12-01 03:39:33 +0100
## Comment 8484
Date: 2007-11-30 15:38:52 +0100
From: @romulogoncalves
The following query against empty database in M5-SQL crashes the Mserver:
SELECT '' AS one, i.* FROM INT2_TBL i WHERE (i.f1 % smallint '2') = smallint '1';
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912517404944 (LWP 11656)]
0x00000039b4c76160 in strlen () from /lib64/libc.so.6
(gdb)
Regards,
Romulo
## Comment 8485
Date: 2007-11-30 23:10:42 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
The error was use as format for a printf call. As it contains a % this caused problems. Will you add a test script.
## Comment 8486
Date: 2007-12-01 15:39:33 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
Fixed by Niels 30/11/2007 at 23:09
Log Message:
sql_scenario.mx: make sure we have a properly defined format string
(is use "%s" to print errors which could hold a % sign)
sql_types.mx: a number of string functions used incorrect
module names (changed to str now)
sql_select.mx: make user 'JOIN" statements include all tables
Test added and approved in:
sql/src/test/BugTracker/Tests/creation_of_exeception_for_select.SF-1841749
Regards,
Romulo
## Comment 8487
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1841749 at http://sourceforge.net/support/tracker.php?aid=1841749
| creation of exeception for select crash... | https://api.github.com/repos/MonetDB/MonetDB/issues/1503/comments | 0 | 2020-11-30T09:44:01Z | 2024-06-27T11:27:15Z | https://github.com/MonetDB/MonetDB/issues/1503 | 753,321,342 | 1,503 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-30 03:36:33 +0100
From: Henning Rode <<hrode>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2007-12-02 12:10:14 +0100
## Comment 8480
Date: 2007-11-30 15:36:33 +0100
From: Henning Rode <<hrode>>
let $c := <a><t/><t/><p/><t><p/></t></a>
for $doc in $c//p
return $doc/preceding-sibling::*
causes the following error:
ERROR = !ERROR: PFll_child: both iter_bat and ctx_bat must have a dense head.
!ERROR: PFll_child: operation failed.
the same query, however, works fine as soon as we change "preceding-sibling" by "following-sibling"
## Comment 8481
Date: 2007-12-01 03:14:54 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
confirmed for default (i.e., `Mserver --debug=0`); however, it seems to work fine with property checking enabled (i.e., `Mserver --debug=10`); hence, it's most probably a property related issue --- investigating ...
## Comment 8482
Date: 2007-12-02 00:10:14 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Fixed in CVS (XQuery_0-20 release branch):
ll_preceding relied on properties that ll_parent did not set completely in all cases;
in case the result of ll_parent is as long at the input, i.e., each item found a (per iter)
unique item, then the ll_parent result head (iter) should inherit the properties of the input
iter_bat's tail.
Added test in pathfinder/tests/BugTracker/Tests/preceding-sibling_failure.SF-1841747*
## Comment 8483
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1841747 at http://sourceforge.net/support/tracker.php?aid=1841747
| preceding-sibling failure | https://api.github.com/repos/MonetDB/MonetDB/issues/1502/comments | 0 | 2020-11-30T09:43:58Z | 2024-06-27T11:27:14Z | https://github.com/MonetDB/MonetDB/issues/1502 | 753,321,302 | 1,502 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-30 03:23:46 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2007-11-30 04:32:40 +0100
## Comment 8475
Date: 2007-11-30 15:23:46 +0100
From: @romulogoncalves
The following sq1 code crashes the Mserver5-SQL:
CREATE TABLE CASE_TBL (
i integer,
f double precision
);
CREATE TABLE CASE2_TBL (
i integer,
j integer
);
SELECT *
FROM CASE_TBL a, CASE2_TBL b
WHERE COALESCE(a.f, b.i, b.j) = 2;
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912517404944 (LWP 11063)]
0x00002aaabc3d199d in sql_case (sql=0x13b6c68, scp=0xaf22d8, token=48, opt_cond=0x0, when_search_list=0x14f4a68, opt_else=0x14f4a48, grp=0x0, subset=0x0, f=1)
at /ufs/goncalve/MonetDB/sql/src/server/sql_select.mx:630
630 if (cond && subset->nrcols && cond->nrcols == 0)
Regards,
Romulo
## Comment 8476
Date: 2007-11-30 16:32:40 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
The bug is ifxed in the checkin:
[Monetdb-sql-checkins] sql/src/server sql_select.mx,,1.208,1.209
at 4:30
The test to cover it was added it in:
sql/src/test/BugTracker/Tests/select_with_coalesce.SF-1841734
Regards,
Romulo
## Comment 8477
Date: 2007-11-30 16:48:01 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
This also affects the stable branch. Why didn't you fix it there?
## Comment 8478
Date: 2007-11-30 16:51:14 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
Yes you are right, I forgot the stable...
I will also change there.
Sorry...
Regards,
Romulo
## Comment 8479
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1841734 at http://sourceforge.net/support/tracker.php?aid=1841734
| select with coalesce | https://api.github.com/repos/MonetDB/MonetDB/issues/1501/comments | 0 | 2020-11-30T09:43:56Z | 2024-06-27T11:27:13Z | https://github.com/MonetDB/MonetDB/issues/1501 | 753,321,274 | 1,501 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-30 03:14:20 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-01-05 08:22:51 +0100
## Comment 8466
Date: 2007-11-30 15:14:20 +0100
From: @romulogoncalves
Dear developers if I run the following query against M5-SQL server:
>CREATE TEMP TABLE PKTABLE (ptest1 int PRIMARY KEY);
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912517404944 (LWP 10828)]
0x00002aaabc428bbf in sql_trans_create_kc (tr=0xb5c638, k=0x0, c=0x13edde8) at /ufs/goncalve/MonetDB/sql/src/storage/store.mx:3580
3580 int nr = list_length(k->columns);
(gdb)
Regards,
Romulo
## Comment 8467
Date: 2007-11-30 16:13:22 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
After some debug I found out that in MonetDB we do not allow temp tables with primary key.
This line of code is in the SQL code:
sql_trans_create_ukey (tr=0xf534b8, t=0x1152a98, name=0x2aaabc674020 "pktable_ptest1_pkey", kt=pkey)
at /ufs/goncalve/MonetDB/sql/src/storage/store.mx:3487
if (isTempTable(t))
3495 return NULL;
Why?
I would like to know if we want to continue like this (so I need to create warning message to avoid the segmentation fault) or I should I change it?
I take the second option.
Regards,
Romulo
## Comment 8468
Date: 2007-11-30 22:16:10 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
temp tables can do without key checking.. So make a nice warning.
## Comment 8469
Date: 2007-12-01 15:43:15 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
The problem is not the check but the key creation.
Should we accept or not pkey creation in temp tables?
If yes I remove the lines:
if (isTempTable(t))
3495 return NULL;
if not I will have to warn the user that he cannot create pkey on temp tables.
Regards,
Romulo
## Comment 8470
Date: 2007-12-01 15:48:11 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
I don't see a reason to forbid it...
but the standard may dictate differently.
(most likely not)
## Comment 8471
Date: 2007-12-01 16:45:27 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
In the stable branch a proper warning message is sent to the user in case he tries to insert column constraints on temporary tables. That message informs him that we do not support constraints on temp tables.
In the future such feature will be implemented on the current branch. So I will open a feature request for constraints on temp tables.
It was fixed in:
sql/src/server sql_schema.mx, SQL_2-20, 1.132.2.2, 1.132.2.3
The test to cover this bug is:
src/test/BugTracker/Tests/pkey_in_temp_table.SF-1841727
Regards,
Romulo
## Comment 8472
Date: 2008-01-05 20:12:43 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
The bug need to be open. Not all the situations were covered.
The following query crashes the mserver:
create global temporary table t2 (id int primary key);
All the combinations should be tested.
Regards,
Romulo
## Comment 8473
Date: 2008-01-05 20:22:51 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
A simple test shows the following error (ie no crash)
!CONSTRAINT: constraints on temporary tables are not supported
## Comment 8474
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1841727 at http://sourceforge.net/support/tracker.php?aid=1841727
| pkey in temp table | https://api.github.com/repos/MonetDB/MonetDB/issues/1500/comments | 0 | 2020-11-30T09:41:01Z | 2024-06-28T13:30:39Z | https://github.com/MonetDB/MonetDB/issues/1500 | 753,319,317 | 1,500 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-30 02:04:03 +0100
From: mharrison <<matt_harrison>>
To: @njnes
Version: -- development
Last updated: 2007-11-30 11:20:54 +0100
## Comment 8461
Date: 2007-11-30 02:04:03 +0100
From: mharrison <<matt_harrison>>
For some reason, sequences can have capital names...
CREATE SEQUENCE "Foo" AS INTEGER;
sql>select next value for Foo;
!NEXT VALUE FOR: no such sequence 'sys'.'foo'
Timer 0.286 msec 0 rows
Lowercase works fine
sql>CREATE SEQUENCE "foo" AS INTEGER;
Timer 383.992 msec 0 rows
sql>select next value for foo;
+--------------------+
|next_value_for_sys |
+====================+
|1 |
+--------------------+
Timer 73.789 msec 1 rows
## Comment 8462
Date: 2007-11-30 02:19:19 +0100
From: mharrison <<matt_harrison>>
Logged In: YES
user_id=1164236
Originator: YES
appears to be an issue with table names as well. So perhaps this is a general bug and not sequence specific.
## Comment 8463
Date: 2007-11-30 08:18:18 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
You use quoted names for your create statements, that means they are used as is. But you do not quote
your identifiers in your select next value for call, this means it will 'cast it too lower case and
compare it with the sequence names', later is there because upper and lower case names should be triated
equally (for unquote identifiers). Could you try that and report if that fails (then that is a bug) else this is the intended semantics.
## Comment 8464
Date: 2007-11-30 11:20:54 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
The standard prescribes this behaviour. Ideally you should quote all of your identifiers.
## Comment 8465
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1841372 at http://sourceforge.net/support/tracker.php?aid=1841372
| Sequences can't start with Capital names.... | https://api.github.com/repos/MonetDB/MonetDB/issues/1499/comments | 0 | 2020-11-30T09:40:58Z | 2024-06-28T13:30:38Z | https://github.com/MonetDB/MonetDB/issues/1499 | 753,319,278 | 1,499 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-29 08:29:53 +0100
From: mharrison <<matt_harrison>>
To: @njnes
Version: -- development
Last updated: 2007-11-29 11:38:03 +0100
## Comment 8458
Date: 2007-11-29 20:29:53 +0100
From: mharrison <<matt_harrison>>
If I create the following table
CREATE TABLE testdate (
id INTEGER NOT NULL,
adate DATE,
adatetime TIMESTAMP,
PRIMARY KEY (id)
)
I can't insert the following:
INSERT INTO testdate (id, adate, adatetime) VALUES (1, '2007-10-30', '2007-10-30');
It gives the following error:
!SQLException:timestamp:conversion of string '2007-10-30' failed
One could argue that a timestamp is a superset of date, and thus should accept date formatted input. (I believe mysql, postgres and oracle behave this way). The databases should just add an implied [000000000000](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=000000000000) for the time portion of the timestamp value.
ps - the following works, which is sort of confusing too (what does the "0:0" mean?)
INSERT INTO testdate (id, adate, adatetime) VALUES (2, '2007-10-30', '2007-10-30 0:0');
## Comment 8459
Date: 2007-11-29 23:37:27 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
test added to src/test/BugTracker/Tests/timestamp_default_time.SF-1841191.sql
Fixed this in the modules (mtime/monettime).
## Comment 8460
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1841191 at http://sourceforge.net/support/tracker.php?aid=1841191
| Timestamp column won't accept insert without time | https://api.github.com/repos/MonetDB/MonetDB/issues/1498/comments | 0 | 2020-11-30T09:40:55Z | 2024-06-27T11:27:10Z | https://github.com/MonetDB/MonetDB/issues/1498 | 753,319,250 | 1,498 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-29 12:09:35 +0100
From: mharrison <<matt_harrison>>
To: @njnes
Version: -- development
Last updated: 2007-12-01 02:07:00 +0100
## Comment 8452
Date: 2007-11-29 00:09:35 +0100
From: mharrison <<matt_harrison>>
when running the following query from python it returns a string instead of a int (or long in python's case).
select next value for a_sequence
The fix is to add
"bigint": long,
to converters.py "conversions" dictionary
thanks
matt
## Comment 8453
Date: 2007-11-29 01:58:12 +0100
From: mharrison <<matt_harrison>>
Logged In: YES
user_id=1164236
Originator: YES
The following is also missing from the dictionary
"tinyint": int, also missing
## Comment 8454
Date: 2007-11-29 20:00:40 +0100
From: mharrison <<matt_harrison>>
Logged In: YES
user_id=1164236
Originator: YES
two more that are missing:
"decimal": float, also missing
"real": float, also missing
## Comment 8455
Date: 2007-11-29 22:35:11 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
I just checked in your patch into the stable branch. It would be very nice I you could send us a simple python testscript.
## Comment 8456
Date: 2007-12-01 14:07:00 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
the sqlsample.py in the clients repo already tests this
## Comment 8457
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1840642 at http://sourceforge.net/support/tracker.php?aid=1840642
| converters.py missing "bigint":long | https://api.github.com/repos/MonetDB/MonetDB/issues/1497/comments | 0 | 2020-11-30T09:40:53Z | 2024-06-27T11:27:09Z | https://github.com/MonetDB/MonetDB/issues/1497 | 753,319,230 | 1,497 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-28 02:36:30 +0100
From: @sjoerdmullender
To: @sjoerdmullender
Version: -- development
Last updated: 2009-07-09 04:22:31 +0200
## Comment 8449
Date: 2007-11-28 14:36:30 +0100
From: @sjoerdmullender
We should check that BATs don't become larger than we can deal with in the rest of the code. The BUN type is defined as oid which means that if you have 32-bit oids on a 64-bit system, you could have BATs that are too large to index. This needs to be prevented from happening, so that implies we need to do some checking in a number of functions:
when creating a new BAT, the size cannot be larger than what can fit in an oid;
when setting a seqbase on a void column (setseqbase/mark), we should check that the seqbase plus the size still fits in an oid;
when appending to a BAT, we should check that the new size still fits in an oid, and if a column is of type void-with-seqbase, that the seqbase plus size also fits.
## Comment 8450
Date: 2009-07-09 16:22:31 +0200
From: @sjoerdmullender
Since BAT counts are now of type BUN, and everywhere where it matters we have checks and assertions to make sure that the BATs don't grow too large, I think we have dealt with this issue.
## Comment 8451
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1840239 at http://sourceforge.net/support/tracker.php?aid=1840239
| BAT capacity checking needed | https://api.github.com/repos/MonetDB/MonetDB/issues/1496/comments | 0 | 2020-11-30T09:40:50Z | 2024-06-27T11:27:08Z | https://github.com/MonetDB/MonetDB/issues/1496 | 753,319,206 | 1,496 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-26 05:42:20 +0100
From: @sjoerdmullender
To: @njnes
Version: -- development
Last updated: 2007-11-26 10:14:04 +0100
## Comment 8445
Date: 2007-11-26 17:42:20 +0100
From: @sjoerdmullender
sql>create function foo(_2foo int) returns int begin return _2foo; end;
sql>select foo(2);
!MALException:user.foo[0]:newVariable:variable _2foo mis-aligned
!TypeException:user.foo[1]:'_2' may not be used before being initialized
!TypeException:user.s0_1[3]:'_30' may not be used before being initialized
+------------------+
| foo_single_value |
+==================+
| 0 |
+------------------+
sql>
## Comment 8446
Date: 2007-11-26 22:14:04 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
identifiers of sql cannot be directly used as identifiers in mal, ie we now prefix them with SQL_.
## Comment 8447
Date: 2007-11-26 22:15:55 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
added test to sql/src/test/BugTrackers/variable_names.SF-1838816.sql
## Comment 8448
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1838816 at http://sourceforge.net/support/tracker.php?aid=1838816
| SQL: can't use variable name staring with _digit in SQL func | https://api.github.com/repos/MonetDB/MonetDB/issues/1495/comments | 0 | 2020-11-30T09:40:47Z | 2024-06-27T11:27:07Z | https://github.com/MonetDB/MonetDB/issues/1495 | 753,319,177 | 1,495 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-26 05:39:15 +0100
From: @sjoerdmullender
To: @njnes
Version: -- development
Last updated: 2007-11-26 10:17:54 +0100
## Comment 8442
Date: 2007-11-26 17:39:15 +0100
From: @sjoerdmullender
mserver5 --dbinit 'include sql;'
mclient -lsql -s 'select 5 % 3'
results in Segmentation fault of server.
## Comment 8443
Date: 2007-11-26 22:17:54 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
added the missing mod operator in m5 calc.mx
added a test in src/test/BugTracker/Tests/select_mod.SF-1838813.sql
## Comment 8444
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1838813 at http://sourceforge.net/support/tracker.php?aid=1838813
| SQL: select 5 % 3 crashes | https://api.github.com/repos/MonetDB/MonetDB/issues/1494/comments | 0 | 2020-11-30T09:40:45Z | 2024-06-27T11:27:06Z | https://github.com/MonetDB/MonetDB/issues/1494 | 753,319,141 | 1,494 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-26 04:53:02 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2007-11-28 01:05:07 +0100
## Comment 8438
Date: 2007-11-26 16:53:02 +0100
From: @romulogoncalves
Dear developers,
I ran the following example in the Mserver5 SQL cvs head branch (updated one hour ago) in my Linux machine.
>create table test1(
id bigint NOT NULL,
name char(1024) NOT NULL,
date33 date NOT NULL);
&3
>insert into test1(id,name,date33)
values(669207071,'hlwP94fhemRqP7bpmvM5fbhlr855Q42yO5TTaafgMbm5pKiZskvclg3MkvcN2cpTOfOf1iOf0Wa98ddioVdU2xjdj47zYOpLbNagahw0v37Kjq0n5aOWKd1hc4jsQegTabzSZTfQlrUrSghmUrc7hj5znvk5glg06ht4jYbRPKcm4OxUzsVkP3iMa8SdZPgjsNPnTSP8eP2syaSWNldk0tshj4OyqwOcn5sgeNe7Qzcdeg4bv80NWneMi701eaamna2gXVhjitMQ5Zew9c4iVnSWV9P0ZgRoM8PjYaZP1M5u6qylYZL6dYa7Uj9qcgiZLqkkz8Z93udrN3ajahVughPqPTUZidP43f5RtiysbWimPXZx84TVcURZ52tWpYsc8oqnf0roQTVTjWO8viMR6o0mreQqMPcKhwr0LajKeb2PTgXufLijL3XvaaN0PVzudNzdwUs0bdU4R1ejVfjNaPa16q3pnfx3eaXVviUf8tz3M9bnf3sSnqxiPUf5XaOvuyrekssqenndbUycgh1QefhWiQgdzj5qWTb7kWe4SY7Zb0q5nTiWQoahcm6ibWaPLa7k0fUMTuf8KMk46fbpcqpwq3TzeQZh4tOyWf5sXuuKmUqeqTzeWbuTif9fi5agau4VgOLxgUqwhXSRixf69KPcrbUbbbrazTleVQrn3lXVTgxVOTbpeLpb6oiUVwfad5eeiLVf1TKiY5vbY5bghcsnN2ZV9Wx0dKus4zzVcsnxg8eSe0Teh6iczhLxmT0VKz3bOMu2R0yc5cLi9ue25eofMfs66dcoglrzogghfjfNNi15TkbMVUZw2yqhdyLy4i51el1geOVSQiXOSh0eK7PeQrb1T32YV25ThqishhxWiZnbdNf6frmaiSZ52utNrVlgsXdx8l1hb7p7NeeoqomXiflMWmmaLbr4rtOcgmv6gg5XizoNjOfuYu8PPSmfQRiglh05iNMZim1KefLzvxi853uZv5d96ixrNVazyO42rfv7W8R1bV62y8zcc2qm',1957-08-01)
;
!TypeException:user.s0_0[8]:'calc.date' undefined in: _13:any := calc.date(_12:sht)
&2 1
>select * from test1;
&1 0 1 3 1
% test1, test1, test1 table_name
% id, name, date33 name
% bigint, char, date type
% 9, 1024, 10 length
[ 669207071, "hlwP94fhemRqP7bpmvM5fbhlr855Q42yO5TTaafgMbm5pKiZskvclg3MkvcN2cpTOfOf1iOf0Wa98ddioVdU2xjdj47zYOpLbNagahw0v37Kjq0n5aOWKd1hc4jsQegTabzSZTfQlrUrSghmUrc7hj5znvk5glg06ht4jYbRPKcm4OxUzsVkP3iMa8SdZPgjsNPnTSP8eP2syaSWNldk0tshj4OyqwOcn5sgeNe7Qzcdeg4bv80NWneMi701eaamna2gXVhjitMQ5Zew9c4iVnSWV9P0ZgRoM8PjYaZP1M5u6qylYZL6dYa7Uj9qcgiZLqkkz8Z93udrN3ajahVughPqPTUZidP43f5RtiysbWimPXZx84TVcURZ52tWpYsc8oqnf0roQTVTjWO8viMR6o0mreQqMPcKhwr0LajKeb2PTgXufLijL3XvaaN0PVzudNzdwUs0bdU4R1ejVfjNaPa16q3pnfx3eaXVviUf8tz3M9bnf3sSnqxiPUf5XaOvuyrekssqenndbUycgh1QefhWiQgdzj5qWTb7kWe4SY7Zb0q5nTiWQoahcm6ibWaPLa7k0fUMTuf8KMk46fbpcqpwq3TzeQZh4tOyWf5sXuuKmUqeqTzeWbuTif9fi5agau4VgOLxgUqwhXSRixf69KPcrbUbbbrazTleVQrn3lXVTgxVOTbpeLpb6oiUVwfad5eeiLVf1TKiY5vbY5bghcsnN2ZV9Wx0dKus4zzVcsnxg8eSe0Teh6iczhLxmT0VKz3bOMu2R0yc5cLi9ue25eofMfs66dcoglrzogghfjfNNi15TkbMVUZw2yqhdyLy4i51el1geOVSQiXOSh0eK7PeQrb1T32YV25ThqishhxWiZnbdNf6frmaiSZ52utNrVlgsXdx8l1hb7p7NeeoqomXiflMWmmaLbr4rtOcgmv6gg5XizoNjOfuYu8PPSmfQRiglh05iNMZim1KefLzvxi853uZv5d96ixrNVazyO42rfv7W8R1bV62y8zcc2qm", 5-05-02 ]
>
I got the Type Exception and at the same time the value selected from the column date33 does not represent the one inserted by the insert statement.
## Comment 8439
Date: 2007-11-26 17:42:45 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
you need to pass the date as a string, but the server shouldn't have inserted the record...
## Comment 8440
Date: 2007-11-28 13:05:07 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
The bug was fixed in the Romulo's checkin today at (12:54).
Log message:
The EC_NUM should not be converted to EC_DATE.
This conversion was creating problems in the insertion of values for date type.
The insertion as without cotes was interpreted as int (1999-08-01 = 1990) and not as date ('1999-08-01').
The test to cover this bug is in the directory:
sql/src/test/BugTracker/Tests/insert_date.SF-1838785
Regards,
Romulo
## Comment 8441
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1838785 at http://sourceforge.net/support/tracker.php?aid=1838785
| column with date type | https://api.github.com/repos/MonetDB/MonetDB/issues/1493/comments | 0 | 2020-11-30T09:40:42Z | 2024-06-27T11:27:05Z | https://github.com/MonetDB/MonetDB/issues/1493 | 753,319,100 | 1,493 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-24 10:08:44 +0100
From: @grobian
To: @njnes
Version: -- development
Last updated: 2007-12-01 04:08:23 +0100
## Comment 8433
Date: 2007-11-24 22:08:44 +0100
From: @grobian
common/src/gdk/gdk_utils.mx:1639
umask(0000);
This effectively means that the umask from the parent (caller) is ignored, which is IMHO not desirable.
I don't see why the umask has to be tampered with to create the gdk lock.
## Comment 8434
Date: 2007-11-24 22:13:59 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
gdk_posix.mx in MT_lockf creates the lockfile with explicit file mask 662 by the way...
## Comment 8435
Date: 2007-11-28 13:09:53 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
Added a workaround for Merovingian.
## Comment 8436
Date: 2007-12-01 16:08:23 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
checked the open calls, these now use mode 0666. We don't reset the umask anymore.
## Comment 8437
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1837764 at http://sourceforge.net/support/tracker.php?aid=1837764
| gdk: umask(0000); kind of bad for security | https://api.github.com/repos/MonetDB/MonetDB/issues/1492/comments | 0 | 2020-11-30T09:40:40Z | 2024-06-27T11:27:04Z | https://github.com/MonetDB/MonetDB/issues/1492 | 753,319,077 | 1,492 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-23 11:54:49 +0100
From: Maurice van Keulen <<mvankeulen>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-04-07 10:26:19 +0200
## Comment 8426
Date: 2007-11-23 11:54:49 +0100
From: Maurice van Keulen <<mvankeulen>>
(Stable 0.20; SuSe Linux)
I tried to declare a variable inside a module and tried to use it in a function of the module. It is as if the variable is empty inside the function. If I use the function outside the module, it appears properly defined. The query below does the same thing inside the module with the test:specialpos function as below it inside the byquery-element.
import module namespace test = "http://www.cs.utwente.nl/~keulen"
at "/local/keulen/Programming/probprot/monetdb/bugs/http://sourceforge.net/support/tracker.php?aid=17mod.xq";
(: change this path :)
let $test := (<a/>,<b/>,$test:special,<c/>)
return
<result>
<bymodule>{test:specialpos($test)}</bymodule>
<byquery>{for $e at $p in $test
where $e is $test:special
return $p
}</byquery>
</result>
The results are different:
<result><bymodule/><byquery>3</byquery></result>
Correct answer should be
<result><bymodule>3</bymodule><byquery>3</byquery></result>
## Comment 8427
Date: 2007-11-23 13:36:43 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Added test in pathfinder/tests/BugTracker/Tests/variable_in_module.SF-1836980*
Fails as reported with the MPS back-end,
but
works fine with the Algebra back-end!
;-)
## Comment 8428
Date: 2007-11-23 13:39:40 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
For convenience:
tagged Summary with "XQ:"
## Comment 8429
Date: 2008-01-22 15:10:32 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Lowered priority as it only fails with the "soon-to-be-history" MPS version
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/variable_in_module.SF-1836980.out.00.html
but works fine with the "soo-to-be-standard" ALG version
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder_algebra/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/variable_in_module.SF-1836980.out.00.html
## Comment 8430
Date: 2009-04-07 10:26:19 +0200
From: @peterboncz
will not be fixed (MPS)
## Comment 8431
Date: 2009-04-07 12:53:52 +0200
From: @drstmane
completed administration.
## Comment 8432
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1836980 at http://sourceforge.net/support/tracker.php?aid=1836980
| XQ: Error with declared variable in module | https://api.github.com/repos/MonetDB/MonetDB/issues/1491/comments | 0 | 2020-11-30T09:40:37Z | 2024-06-27T11:27:03Z | https://github.com/MonetDB/MonetDB/issues/1491 | 753,319,054 | 1,491 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-21 01:58:00 +0100
From: Hans <<hans_0_>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2008-12-12 12:14:32 +0100
## Comment 8420
Date: 2007-11-21 13:58:00 +0100
From: Hans <<hans_0_>>
version: Supersource tarball SR3.
Compiled on fedora core 5, 64-bit with 32-bits oid.
The following xquery returns an erroneous result:
The query:
declare function test($nodes as node()*) {
for $n in $nodes[./self::a]
let $c := test($n/*)
where (count($c) > 0)
order by $n/@name
return element a { $n/@name, $c } ,
for $n in $nodes[./self::b] return $n
};
test(<x><a name="1"></a><a name="2"><a name="y"><b name="2"/></a></a></x>/*) ,
test(<x><a name="1"><a name="x"/></a><a name="2"><a name="y"><b name="2"/></a></a></x>/*)
<>
Returns:
<a name="2"><a name="y"><b name="2"/></a></a>,
<a name="1"><a name="y"><b name="2"/></a></a>
Expected result is:
<a name="2"><a name="y"><b name="2"/></a></a>,
<a name="2"><a name="y"><b name="2"/></a></a>
If the order by clause is omitted, the result is correct, except for the ordering.
Regards,
Hans van Rijswijk.
## Comment 8421
Date: 2007-11-21 17:20:02 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Test added in pathfinder/tests/BugTracker/Tests/recursive_function.SF-1835745.* (XQuery_0-20 branch).
Confirms that without "order by" the result is as expected, while it is not with "order by".
Further investigations still need to be performed.
Volunteer(s)?
## Comment 8422
Date: 2007-11-27 16:00:23 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
nested order by in milprint-summer is buggy (see some W3C tests that have been failing for a long time).
this will not be fixed. the algebra backend does not have these problems.
## Comment 8423
Date: 2007-11-27 16:11:04 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Note, though, that the algebra back-end does not support recursive functions, yet:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder_algebra/.mTests103/GNU.64.32.d-Fedora6/tests_BugTracker/recursive_function.SF-1835745.err.00.html
ERROR = !fatal error: Algebra implementation cannot cope with recursive functions yet.
## Comment 8424
Date: 2008-10-04 10:07:26 +0200
From: @drstmane
See also
[ 2140992 ] XQ: "order by" doesn't work in the non-algebra version
https://sourceforge.net/tracker/index.php?func=detail&aid=2140992&group_id=56967&atid=482468
## Comment 8425
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1835745 at http://sourceforge.net/support/tracker.php?aid=1835745
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| XQ: recursive function call gives wrong result | https://api.github.com/repos/MonetDB/MonetDB/issues/1490/comments | 0 | 2020-11-30T09:40:35Z | 2024-06-28T13:30:38Z | https://github.com/MonetDB/MonetDB/issues/1490 | 753,319,033 | 1,490 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-21 12:58:51 +0100
From: @grobian
To: Lefteris Sidirourgos <<lsidir>>
Version: -- development
Last updated: 2007-11-21 04:21:15 +0100
## Comment 8417
Date: 2007-11-21 12:58:51 +0100
From: @grobian
I believe this is due to lefteris' checkins:
3946 changes = p->sem.fun_1to1.refs.atts[1];
3947 mvar_t *loop = NULL;
3948 int update_str;
3949
3950 assert (env_count (L(p)->env));
/vol/localfs/tmp_manegold/manegold.GNU.32.32.d.2051/pathfinder/compiler/mil/milg
en.brg: In function `reduce':
/vol/localfs/tmp_manegold/manegold.GNU.32.32.d.2051/pathfinder/compiler/mil/milg
en.brg:3948: warning: 'update_str' might be used uninitialized in this function
make[5]: *** [libmil_la-milgen.lo] Error 1
Looks like assigning it 0 might help, but I don't know the code, so I'm not sure if that is correct.
## Comment 8418
Date: 2007-11-21 16:21:15 +0100
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
I fixed the default case of the switch statement causing this problem.
## Comment 8419
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1835717 at http://sourceforge.net/support/tracker.php?aid=1835717
| XQ: compilation fails on various platforms | https://api.github.com/repos/MonetDB/MonetDB/issues/1489/comments | 0 | 2020-11-30T09:40:32Z | 2024-06-27T11:27:01Z | https://github.com/MonetDB/MonetDB/issues/1489 | 753,319,002 | 1,489 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-21 09:44:09 +0100
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2007-11-23 07:18:39 +0100
## Comment 8412
Date: 2007-11-21 09:44:09 +0100
From: @drstmane
On our new 32-bit Fedora 8 machine f8,
various M4 & M5 tests seems to fail with
*** invalid open64 call: O_CREAT without mode ***
All affected tests seem to be mmap-related:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.32.32.d-Fedora8/tests_BugReports/no.031.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.32.32.d-Fedora8/tests_suite_01/test_40.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.32.32.d-Fedora8/src_modules_plain/ascii_io.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.32.32.d-Fedora8/src_modules_plain/bat.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.32.32.d-Fedora8/src_modules_plain/bat2.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.32.32.d-Fedora8/tests_BugTracker/mmap_bats.SF-1428389.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.32.32.d-Fedora8/tests_by_Peter/tst_mmap.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.32.32.d-Fedora8/tests_by_Peter/tst_priv.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.32.32.d-Fedora8/tests_by_Peter/tst_writestr.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.32.32.d-Fedora8/tests_by_Peter/tst_updatestr.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.32.32.d-Fedora8/tests_by_Peter/tst_append_readonly.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.32.32.d-Fedora8/tests_by_Peter/tst_append_readonly_commit.err.00.html
I have not yet managed to either analyze the problem on f8 or gain access to another Fedora 8 to check the behavior there...
## Comment 8413
Date: 2007-11-21 09:53:15 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
does Fedora 8 by chance use glibc 2.7?
## Comment 8414
Date: 2007-11-21 10:02:27 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Yes, Fedora 8 uses glibc2.7 .
## Comment 8415
Date: 2007-11-23 07:18:39 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
With Sjoerd's checkin
===================================================================
2007/11/21 - sjoerd:
src/gdk/gdk_posix.mx,1.143.2.2(MonetDB_1-20,Stable_DailyBuild-23,Stable_DailyBuild-22)
Add mode argument to open with O_CREAT flag.
Please check whether the mode has an appropriate value.
===================================================================
the problem appears to be fixed.
Thanks!
## Comment 8416
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1835610 at http://sourceforge.net/support/tracker.php?aid=1835610
| M4+M5: mmap fails on f8 | https://api.github.com/repos/MonetDB/MonetDB/issues/1488/comments | 0 | 2020-11-30T09:40:30Z | 2024-06-27T11:27:00Z | https://github.com/MonetDB/MonetDB/issues/1488 | 753,318,964 | 1,488 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-20 07:00:00 +0100
From: mharrison <<matt_harrison>>
To: @njnes
Version: -- development
Last updated: 2007-11-20 02:38:27 +0100
## Comment 8408
Date: 2007-11-20 07:00:00 +0100
From: mharrison <<matt_harrison>>
When trying executemany from cursors.py it fails. There is an undefined "m" variable, so it throws the following error:
NameError: "global name 'm' is not defined"
Also there is no ._execute method on the cursor.
It should be something like this:
if not args: return
r = 0
for a in args:
r = r + self.execute(query, a)
self._executed = query
return r
## Comment 8409
Date: 2007-11-20 14:28:46 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
the python test is extended to test this bug. see clients/src/examples/python. (run in sql/src/test/mapi)
## Comment 8410
Date: 2007-11-20 14:32:10 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
indeed when applying your changes it seems to work (much) better. Thanks..
## Comment 8411
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1834941 at http://sourceforge.net/support/tracker.php?aid=1834941
| cursor.executemany (python) fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1487/comments | 0 | 2020-11-30T09:40:27Z | 2024-06-27T11:27:00Z | https://github.com/MonetDB/MonetDB/issues/1487 | 753,318,937 | 1,487 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-19 10:55:25 +0100
From: @grobian
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2007-11-19 05:41:28 +0100
## Comment 8402
Date: 2007-11-19 10:55:25 +0100
From: @grobian
make[7]: Entering directory `/var/tmp/monet.GNU.32.32.d.22666/pathfinder/Fedora8/src/tools/java'
"/usr/local/bin/ant" -f "`readlink -f /var/tmp/monet.GNU.32.32.d.22666/pathfinder/src/tools/java/build.xml`" -Dbuilddir="`readlink -f /var/tmp/monet.GNU.32.32.d.22666/pathfinder/Fedora8/src/tools/java`" -Djardir="`readlink -f /var/tmp/monet.GNU.32.32.d.22666/pathfinder/Fedora8/src/tools/java`" -Dbasedir="`readlink -f /var/tmp/monet.GNU.32.32.d.22666/pathfinder/src/tools/java`" distall
Buildfile: /var/tmp/monet.GNU.32.32.d.22666/pathfinder/src/tools/java/build.xml
distall:
prepare:
[echo] Debug is true, optimise is true
compile_util:
[echo] Compiling Utilities
[javac] Compiling 9 source files to /var/tmp/monet.GNU.32.32.d.22666/pathfinder/Fedora8/src/tools/java
[javac] ----------
[javac] 1. ERROR in /var/tmp/monet.GNU.32.32.d.22666/pathfinder/src/tools/java/src/nl/cwi/monetdb/xquery/util/CmdLineOpts.java (at line 1)
[javac] /*
[javac] ^
[javac] The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files
Fedora 8's "java" implementation is completely b0rkened.
Either install a real Java implementation, or stop testing Java on this broken platform.
Thx.
## Comment 8403
Date: 2007-11-19 10:56:15 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
same thing for clients
## Comment 8404
Date: 2007-11-19 11:16:41 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
The Java we're using is supposed to be a "real" one:
monet@f8:~ $ type -p java
/usr/local/bin/java
monet@f8:~ $ ls -l /usr/local/bin/java
lrwxrwxrwx 1 root soft 23 2007-11-17 12:53 /usr/local/bin/java -> /soft/jdk1.5.0/bin/java
monet@f8:~ $ java -version
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64)
Java HotSpot(TM) Client VM (build 1.5.0-b64, mixed mode)
Moreover, I had tried with the latest "real" JDK 1.5 update 14 RPM from the Sun(!) web site on Saturday, but that lead to the same results.
## Comment 8405
Date: 2007-11-19 11:20:14 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
Testweb doesn't use Sun's Java, that can clearly be seen from the error message style.
Maybe ant is configured in such a way that it picks gcj?
## Comment 8406
Date: 2007-11-19 17:41:28 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
The "ant" (both in /usr/local/bin/ and /usr/bin/) on our f8 (the very machine;
I cannot make any statement about Fedora 8 in general!) seems to be configured
to use the GCJ JDK from /usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/ by default,
even if there is an other Java available earlier in the PATH.
Given my limited knowledge about and experiences with ant & Java,
the first (and hence only) way I found to fix this is by explicitly
set JAVA_HOME and have it point to the Sun JDK in /soft/jdk1.5.0/ .
## Comment 8407
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1834445 at http://sourceforge.net/support/tracker.php?aid=1834445
| Compiling pathfinder (Stable) failed on GNU.32.32.d-Fedora8 | https://api.github.com/repos/MonetDB/MonetDB/issues/1486/comments | 0 | 2020-11-30T09:40:24Z | 2024-06-27T11:26:58Z | https://github.com/MonetDB/MonetDB/issues/1486 | 753,318,899 | 1,486 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-19 10:53:03 +0100
From: @grobian
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2007-11-19 11:45:36 +0100
## Comment 8399
Date: 2007-11-19 10:53:03 +0100
From: @grobian
MapiLib.pm.c: In function 'boot_MapiLib':
MapiLib.pm.c:6157: warning: passing argument 2 of '_swig_create_magic' discards
qualifiers from pointer target type
make[7]: *** [MapiLib.pm.lo] Error 1
## Comment 8400
Date: 2007-11-19 11:45:36 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
fixed in CVS (Clients_1-20) release branch.
## Comment 8401
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1834442 at http://sourceforge.net/support/tracker.php?aid=1834442
| Compiling clients (Stable) failed on GNU.32.32.d-Gentoo1.12. | https://api.github.com/repos/MonetDB/MonetDB/issues/1485/comments | 0 | 2020-11-30T09:40:22Z | 2024-06-27T11:26:57Z | https://github.com/MonetDB/MonetDB/issues/1485 | 753,318,866 | 1,485 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-17 11:33:48 +0100
From: mharrison <<matt_harrison>>
To: @njnes
Version: -- development
Last updated: 2007-11-20 02:45:31 +0100
## Comment 8396
Date: 2007-11-17 23:33:48 +0100
From: mharrison <<matt_harrison>>
Just filing a bug reported by Bart, that I'm running into as well.
Here's bart's description from 10-17::
>Comment By: bjbuter (bjbuter)
Date: 2007-10-17 01:20
Message:
Logged In: YES
user_id=1624832
Originator: YES
I forgot to add a big annoyance, though not critical, the Python client
does not relay any error messages from MonetDB. If anything goes wrong it
issues a RuntimeError:None instead of the more detailed response the normal
MapiClient gives.
Bart
It appears that the Mapi.error_str() (MonetDB/CMapi.py) method always returns None rather than passing through the actual failure.
The workaround is to take the queries and run them from the command line, which is annoying and flow disrupting....
A fix would be greatly appreciated.
cheers!
-matt
## Comment 8397
Date: 2007-11-20 14:45:31 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
matt reported that the patches, which have been applied to the stable cvs branch did indeed fix his problem. This is also tested by the python test in the clients package
## Comment 8398
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1833800 at http://sourceforge.net/support/tracker.php?aid=1833800
| Python errors not getting passed through MAPI | https://api.github.com/repos/MonetDB/MonetDB/issues/1484/comments | 0 | 2020-11-30T09:40:19Z | 2024-06-27T11:26:56Z | https://github.com/MonetDB/MonetDB/issues/1484 | 753,318,844 | 1,484 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-16 07:08:38 +0100
From: mharrison <<matt_harrison>>
To: @njnes
Version: -- development
Last updated: 2007-11-27 01:00:13 +0100
## Comment 8392
Date: 2007-11-16 19:08:38 +0100
From: mharrison <<matt_harrison>>
Summary says it all. If you create a table with NUMERIC(9,2) (you can add NULL or leave it off behavior is the same), you can't insert the initial value into that table if it contains a NULL. After you insert a non-NULL value, NULL values will go in.
Here's a sample session showing this::
sql>CREATE TABLE decimal_null (
more>promoid NUMERIC(8, 2) NULL
more>);
Timer 858.044 msec 0 rows
sql>INSERT into "decimal_null" values (NULL);
!SQLException:int:"" is no decimal value (doesn't contain a '.')
Timer 0.700 msec 0 rows
sql>INSERT into "decimal_null" values (2.3);
Rows affected 1
Timer 34.488 msec 0 rows
sql>INSERT into "decimal_null" values (NULL);
Rows affected 1
Timer 3.121 msec 0 rows
And here's the SQL all by itself to recreate:
CREATE TABLE decimal_null (
promoid NUMERIC(8, 2)
);
' this will fail
INSERT into "decimal_null" values (NULL);
' this will work
INSERT into "decimal_null" values (2.3);
'now the one that failed will work
INSERT into "decimal_null" values (NULL);
Note, I'm running Gentoo, version 5.2 of monetdb
## Comment 8393
Date: 2007-11-16 21:41:29 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
A problem existed in the function which converted strings to numeric values. This is now fixed in the stable branch.
## Comment 8394
Date: 2007-11-16 21:42:18 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
A test was added to the src/test/BugTracker/Tests directory.
number_null_first_row.SF-1833286
## Comment 8395
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1833286 at http://sourceforge.net/support/tracker.php?aid=1833286
| Decimal / NUMERIC (9,2) won't allow initial NULL value | https://api.github.com/repos/MonetDB/MonetDB/issues/1483/comments | 0 | 2020-11-30T09:40:17Z | 2024-06-27T11:26:55Z | https://github.com/MonetDB/MonetDB/issues/1483 | 753,318,815 | 1,483 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-14 09:42:37 +0100
From: @grobian
To: Arjen de Rijke <<arjen.de.rijke>>
Version: -- development
Last updated: 2007-11-19 11:25:03 +0100
## Comment 8378
Date: 2007-11-14 09:42:37 +0100
From: @grobian
make[7]: Entering directory `/home/monet/monet.GNU.32.32.d.26420/clients/Debian4.0/src/java/tests'
"/usr/bin/ant" -f "`readlink -f /home/monet/monet.GNU.32.32.d.26420/clients/src/java/tests/build.xml`" -Dbuilddir="`readlink -f /home/monet/monet.GNU.32.32.d.26420/clients/Debian4.0/src/java/tests`" -Djardir="`readlink -f /home/monet/monet.GNU.32.32.d.26420/clients/Debian4.0/src/java/tests`" -Dbasedir="`readlink -f /home/monet/monet.GNU.32.32.d.26420/clients/src/java/tests`" compile
Unable to locate tools.jar. Expected to find it in /usr/lib/jvm/java-1.4.2-gcj-4.1-1.4.2.0/lib/tools.jar
Buildfile: /home/monet/monet.GNU.32.32.d.26420/clients/src/java/tests/build.xml
prepare:
compile:
[echo] Compiling JDBC tests
[javac] Compiling 15 source files to /home/monet/monet.GNU.32.32.d.26420/clients/Debian4.0/src/java/tests
BUILD FAILED
/home/monet/monet.GNU.32.32.d.26420/clients/src/java/tests/build.xml:56: Unable to find a javac compiler;
com.sun.tools.javac.Main is not on the classpath.
Perhaps JAVA_HOME does not point to the JDK
Total time: 1 second
The problem most likely is because of ant's first warning:
Unable to locate tools.jar. Expected to find it in /usr/lib/jvm/java-1.4.2-gcj-4.1-1.4.2.0/lib/tools.jar
## Comment 8379
Date: 2007-11-14 09:53:38 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Thanks, Fabian!
Arjen,
could you please also install gcj-dev[el] and/or gcj-compat-dev[el] (provided either or both exist for Debian) on timmy?
Thanks!
## Comment 8380
Date: 2007-11-14 10:11:10 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
or better, just install Sun Java, such that the test outputs will also be useful.
## Comment 8381
Date: 2007-11-14 10:24:01 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
we do not (yet?) "officially require Sun Java; hence, let's see how far we get with gcj ...
## Comment 8382
Date: 2007-11-14 10:29:33 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
No, but it is known that JDBC doesn't work properly if executed under GCJ's runtime VM.
## Comment 8383
Date: 2007-11-14 14:37:44 +0100
From: @arjenderijke
Logged In: YES
user_id=1836138
Originator: NO
I have installed java-gcj-compat-(dev). If this is not enough, we can try the sun-jdk.
## Comment 8384
Date: 2007-11-15 08:42:24 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Compilation of all Java seems to work fine with GCJ on timmy (Debian), now.
However, as experienced earlier (and hence expected), running with GCJ's JVM does not work properly.
To finish the testing, I'd propose to (if possible) first install only the Sun JRE, but not the JDK. Thus, we could check, whether the GCJ compiler code at least works fine with Sun's JVM (as it did with earlier tests on my FC6 laptop).
If this indeed works, I'd suggest to keep timmy as a GCJ-JDK + Sun-JRE test platform.
(Only) otherwise, let's go for Sun-JDK+JRE only also on timmy.
## Comment 8385
Date: 2007-11-16 16:14:31 +0100
From: @arjenderijke
Logged In: YES
user_id=1836138
Originator: NO
I installed sun's jre 1.5.0 on timmy. I did not remove gcj.
## Comment 8386
Date: 2007-11-16 16:42:49 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Thanks!
... we need to keep gcj('s jdk) for compilation!
I'll (try to) make sure that the testing environment/scripts use Sun's JRE (iso. gcj's jre) for running the gcj-compiled "stuff".
Stefan
## Comment 8387
Date: 2007-11-17 08:36:45 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
This kind of obviously fails as ant itself is a Java program too, so it gets started by Sun's JRE, and hence expects Sun's javac, unless explicitly told not to via i.e. defining build.compiler.
## Comment 8388
Date: 2007-11-17 09:52:55 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Indeed. Hence:
In order not to complicate compilation on timmy (Debian),
in particular to not confuse ant by using Sun JRE (java)
but GCj JDK (javac, jar), we now make sure that the build
process sees GCJ JDK & JRE (only), but testing sees (and
hence uses) Sun JRE (first).
(Admittedly a bit "hacky", but I do not have time to invest
into a "more elegant" solution --- which should not be required
in cse this one turns out to work ...)
## Comment 8389
Date: 2007-11-19 11:25:03 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
Java appears to do something on timmy now, but it has quite strange errors.
I consider this bug fixed for now.
## Comment 8390
Date: 2007-11-20 07:33:59 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Just for the records, and hence ensuring that the documentation is complete and correct:
Due to a typo of mine, Java & JDBC tests on timmy were not only compiled witj GCJ JDK but also still run with GCJ JRE.
The latter was and is known to result in unexpected behaviour, no matter whether our Java code is compiled with GCJ JDK or Sun JDK.
(The actual problem has not been investigated, yet.)
After fixing my typo, the Java & JDBC tests are now run with Sun JRE on timmy (while still compiled with GCJ JDK),
and this seems to work fine for all Java/JDBC tests,
with the only exception being Test_PStimezone:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.32.32.d-Debian4.0/src_jdbc_tests/Test_PStimezone.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql5/.mTests103/GNU.32.32.d-Debian4.0/src_jdbc_tests/Test_PStimezone.out.00.html
Investigation is pending, whether the unexpected outcome of this test is due to the GCJ compilation (and if so, why),
or whether it is due to local settings on timmy.
## Comment 8391
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1831630 at http://sourceforge.net/support/tracker.php?aid=1831630
| Clients: Debian gcj/ant doesn't work. | https://api.github.com/repos/MonetDB/MonetDB/issues/1482/comments | 0 | 2020-11-30T09:40:14Z | 2024-06-27T11:26:54Z | https://github.com/MonetDB/MonetDB/issues/1482 | 753,318,781 | 1,482 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-12 12:38:15 +0100
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2008-01-11 10:32:27 +0100
## Comment 8368
Date: 2007-11-12 12:38:15 +0100
From: @drstmane
(Triggered by Arjen d.V.'s problems of loading module pathfinder after a default compilation of the develoment trunk from CVS on his 64-bit Fedora Core 6 desktop at CWI; see below.)
Since recently --- I cannot tell exactly since when, surely only after the latest MonetDB_1-20 release branch has been created, possibly since the GDK-2 branch has been merged into the development trunk --- gcc seems to generate faulty code for gdk_scanselect in very selected situations:
1)
With gcc 4.1.2 on 64-bit Fedora Core 6, only with 64-bit OIDs and only when compiled with "--disable-optimize --disable-debug" (the default in the development trunk) resulting in CFLAGS="-g -O2"; using either "--enable-debug" (CFLAGS="-g") or "--enable-optimize" (CFLAGS="-O6 ...") does seem to generate correct code.
2)
With gcc 4.2.0 on 64-bit Red Hat Enterprise Linux WS release 4 (Nahant Update 4) on Itanuim 2 with 64-bit OIDs (32-bit OIDs not tested), both with "--disable-optimize" and "--enable-optimize" ("--enable-debug" not tested).
(The problem only occurs in the development trunk, but not in the MonetDB_1-20 release branch.)
The code that triggers the problem is in lines 468-476 of MonetDB/src/gdk/gdk_scanselect.mx:
========
BATloop(b, p, q) {
ptr v = BUN@3(bi, p);
@4 {
@7@2_bunfastins_nocheck_noinc(bn, _p, (void *) (@8), @5);
_p++;
}
@9
}
========
or once Mx-expanded
========
BATloop(b, p, q) {
ptr v = BUNtloc(bi, p);
if ( simple_EQ(tl ,v,int) ) {
lngvoid_bunfastins_nocheck_noinc(bn, _p, (void *) (&oid_ctr), v);
_p++;
}
oid_ctr++;
}
========
and with (some) C macros expanded:
========
BATloop(b, p, q) {
ptr v = BUNtloc(bi, p);
if ( simple_EQ(tl ,v,int) ) {
((lng*)((bn)->H->heap.base))[_p] = *(lng*) (ptr) ((void *) &oid_ctr));
_p++;
}
oid_ctr++;
}
========
It appears that the resulting faulty code does perform the increment "oid_ctr++;" before the code in the if-body has dereferenced "&oid_ctr" and read the value.
See these tests for details:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB4/.mTests103/GNU.64.64.d-Fedora6/src_gdk/scanselect.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.mTests103/GNU.64.64.d-Fedora6/tests_gdkTests/scanselect.out.00.html
(last night, I had the TestWeb compiled with "--disable-optimize" as opposed to the usual "--enable-optimize".)
Additionally, this problem makes loading the pathfinder module fail with:
========
MonetDB>module(pathfinder);
PF/Tijah module v0.3.0 loaded. http://dbappl.cs.utwente.nl/pftijah
!ERROR: BATfetchjoin(tmp_221,ws_nme) does not hit always (2) (|bn|=57 != 58=|l|) => can't use fetchjoin.
!ERROR: CMDleftfetchjoin: operation failed.
!ERROR: interpret_params: rename(param 1): evaluation error.
========
Explicitly assigning "oid oid_val = oid_ctr;" in the if-body and then replacing "&oid_ctr" by "&oid_val" seems to "solve" (prevent) the problem.
However, I'm hesitant to apply this patch since (1) the original code seems correct to me and (2) the problem occurs only in selected cases --- although the very default case on Fedora Core 6 ...
Any comments and/or help is more than welcome!
## Comment 8369
Date: 2007-11-12 13:13:00 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
Maybe related:
64 =sys-devel/gcc-4.2.0*
65 =sys-devel/gcc-4.2.1*
are "too broken", GCC upstream fixed many issues in 4.2.2, worth a try to use it on Itanium.
Gentoo has 4.2.2 installed (iirc) at least I use 4.2.2 on my desktop. I will try and compile with 4.1.2 on (still) FC6 with --disable-optimize --disable-debug and see if I get the same issue.
## Comment 8370
Date: 2007-11-12 14:33:57 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
I tested with gcc 4.1.2 and gcc 4.2.2 and get exactly the same behaviour, i.e. significantly differing output.
## Comment 8371
Date: 2007-11-12 14:41:47 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
using
CFLAGS="-march=athlon64 -pipe -g -W -Wall"
./configure --disable-strict --disable-optimize
remedies the problem indeed also on 4.2.2.
## Comment 8372
Date: 2007-11-13 11:26:01 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Just for the records, the following combinations seem to work fine:
gcc 4.1.2 on 32-bit Debian 4.0
gcc 4.1.1 on 32-bit Fedora Core 6
gcc 4.2.2 on 32-bit Gentoo 1.12.9
gcc 4.1.2 on 64-bit Fedora Core 6 using 32-bit OIDs
## Comment 8373
Date: 2007-12-18 11:31:23 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
This (or a similar gcc 4.1.* related) problem might affect Pathfinder testing on 64-bit Fedora Core 6 with 64-bit OIDs also with --enable-optimize;
see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/index_short.html
and (e.g.)
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/benchmarks_MBench/qr02.out.00.html
## Comment 8374
Date: 2007-12-21 13:46:54 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Since Fedora Core 6 has reached EOL and our systems are slowly but surely being upgraded to Fedora 8, and since the bug seems to be in the compiler, it is unlikely that we're going to fix this.
## Comment 8375
Date: 2008-01-07 17:31:35 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
With the default gcc 4.1.2 on Fedora 8 (basically the same as on Fedora Core 6) the problem still persists.
## Comment 8376
Date: 2008-01-11 10:32:27 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
we worked around this gcc bug. Its hard to make a simple small example this problem, ie we won't send a bug report to the gcc comunity.
## Comment 8377
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1830366 at http://sourceforge.net/support/tracker.php?aid=1830366
| gcc 4.1/4.2 produces wrong code on FC6, F8 & RHEL4WS | https://api.github.com/repos/MonetDB/MonetDB/issues/1481/comments | 0 | 2020-11-30T09:40:10Z | 2024-06-27T11:26:53Z | https://github.com/MonetDB/MonetDB/issues/1481 | 753,318,742 | 1,481 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-08 04:51:37 +0100
From: Maurice van Keulen <<mvankeulen>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2007-11-11 02:26:36 +0100
## Comment 8365
Date: 2007-11-08 16:51:37 +0100
From: Maurice van Keulen <<mvankeulen>>
(stable 0.20, Suse Linux, mps backend)
The function fn:normalize-space($arg as xs:string?) as xs:string is defined in the standard as
"Returns the value of $arg with whitespace normalized by stripping leading and trailing whitespace and replacing sequences of one or more than one whitespace character with a single space."
(see http://www.w3.org/TR/xpath-functions/func-normalize-space)
It does however not remove the final leading and trailing whitespace, i.e., normalize-space(" a b c ") gives " a b c " instead of "a b c".
## Comment 8366
Date: 2007-11-11 14:26:36 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
fixed in CVS (XQuery_0-20 branch; propagation to development trunk pending):
fn:normalize-space now also (correcly) removes leading & trailing spaces.
Test added in pathfinder/tests/BugTracker/Tests/fn_normalize-space.SF-1828362.* .
## Comment 8367
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1828362 at http://sourceforge.net/support/tracker.php?aid=1828362
| XQ:normalize-space does not remove leading/trailing space | https://api.github.com/repos/MonetDB/MonetDB/issues/1480/comments | 0 | 2020-11-30T09:40:08Z | 2024-06-27T11:26:52Z | https://github.com/MonetDB/MonetDB/issues/1480 | 753,318,714 | 1,480 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-08 03:35:48 +0100
From: @arjenderijke
To: @sjoerdmullender
Version: -- development
Last updated: 2007-11-12 09:32:02 +0100
## Comment 8359
Date: 2007-11-08 15:35:48 +0100
From: @arjenderijke
When compiling MonetDB5 on CWI desktop, code checkout today, make failed with:
make[4]: Leaving directory `/ufs/rijke/src/monetdb/MonetDB5/src/modules'
Making all in tools
make[4]: Entering directory `/ufs/rijke/src/monetdb/MonetDB5/src/tools'
/export/scratch1/rijke/monetdb/bin/Mx -x c stethoscope.mx
stethoscope.mx: ./stethoscope.c - created
/export/scratch1/rijke/monetdb/bin/Mx -x c embeddedclient.mx
embeddedclient.mx: ./embeddedclient.c - created
/export/scratch1/rijke/monetdb/bin/Mx -l -x h embeddedclient.mx
embeddedclient.mx: ./embeddedclient.h - created
make[4]: *** No rule to make target `mcheckpoint', needed by `all'. Stop.
make[4]: Leaving directory `/ufs/rijke/src/monetdb/MonetDB5/src/tools'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/ufs/rijke/src/monetdb/MonetDB5/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/ufs/rijke/src/monetdb/MonetDB5/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/ufs/rijke/src/monetdb/MonetDB5'
make: *** [all] Error 2
Fedora Core 6
libtool 1.5.22
autoconf 2.59
automake 1.9.6
## Comment 8360
Date: 2007-11-10 01:21:10 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Hm, looks like your check-out is broken:
========
$ grep mcheckpoint /ufs/rijke/src/monetdb/MonetDB5/src/tools/CVS/Entries
/mcheckpoint/1.3/Fri Oct 12 17:40:25 2007//
$ ls /ufs/rijke/src/monetdb/MonetDB5/src/tools/mcheckpoint
ls: /ufs/rijke/src/monetdb/MonetDB5/src/tools/mcheckpoint: No such file or directory
========
(sorry for being so "noncharlant" to peek in you home ;-))
Either the cvs checkout/update failed for some reason or the code does not like the fact that you are running configure and make in your right source tree instead of using a separate build tree (don't get me wrong although we usuallu strongly recommend to use a separate build tree for "convenience", running configure & make straight in the source tree should work, and if it does not, this is a bug...).
Hence, just do an other `cvs -q update -dP`, watch the output carefully for potential errors (and please report all files that are checked out again because they "were lost"), and then try make again, and report whether it works or not.
## Comment 8361
Date: 2007-11-10 17:03:11 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Indeed. error not confimed.
Arjen, can it be closed?
## Comment 8362
Date: 2007-11-11 16:19:38 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Martin,
did you try (and fail) to confirm the error that using the source-dir as build-dir (i.e., calling `./configure` & `make` in .../MonetDB5/) fails as reported , or do you "just" mean that "normal" compilation using a separate build-dir (e.g., .../MonetDB5/Linux/) does work fine?
## Comment 8363
Date: 2007-11-12 09:32:02 +0100
From: @arjenderijke
Logged In: YES
user_id=1836138
Originator: YES
Forgiving Stefan for his invasion of privacy, another cvs update did the trick. There seem to have been a problem with the cvs repository last week, but now it works again
## Comment 8364
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1828314 at http://sourceforge.net/support/tracker.php?aid=1828314
| make failed on MonetDB5 | https://api.github.com/repos/MonetDB/MonetDB/issues/1479/comments | 0 | 2020-11-30T09:40:05Z | 2024-06-27T11:26:51Z | https://github.com/MonetDB/MonetDB/issues/1479 | 753,318,685 | 1,479 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-07 04:49:07 +0100
From: @MarcinZukowski
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2007-11-21 04:08:02 +0100
## Comment 8350
Date: 2007-11-07 16:49:07 +0100
From: @MarcinZukowski
--enable-bits is still in configure and HowToStart.
However, it doesn't seem to work with icc.
So either some fixes are needed to guarantee it does what a user expects, or prints a fail message, or it should be removed.
## Comment 8351
Date: 2007-11-07 17:01:25 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
"does not seem to work" as in (1) "does not have any effect" or (2) "results in an error" or (3) "..."?
It --- to be precise one of "--enable-bi1970-01-01 01:00:32 +0100", "i--enable-bi1970-01-01 01:01:04 +0100" --- is (IMHO) still supposed to work ...
## Comment 8352
Date: 2007-11-07 17:12:49 +0100
From: @MarcinZukowski
Logged In: YES
user_id=607094
Originator: YES
I'm sure you know, but if you insist :)
On Athlon 64 X2, "--enable-bi1970-01-01 01:00:32 +0100" with icc it compiles into 64-bit binaries.
I don't even know if icc supports that, but I was simply suprised to get a 64-bit thing.
## Comment 8353
Date: 2007-11-07 17:27:29 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
No, I didn't know that --- actually I did not even know what platform you were using (I could have guessed but we do have more than one at CWI ...).
Given the CPU you specify, I now *guess* you're referring to our FC6 desktops at CWI and to icc 10.0, right?
Well, I am actually not sure whether (1) "our" icc 10.0 allows to produce 32-bit binaries on our 64-bit FC6 desktops, (2) the correct option to do this is set (added to $CC) in buildtools/conf/MonetDB.m4, (3) our 64-bit FC6 comes with all the 32-bit libraries to actually get a 32-bit MonetDB compiled successfully, (4) it would work with gcc.
In any case I agree with Marcin that the current behavior of silently ignoring --enable-bi1970-01-01 01:00:32 +0100 (with icc on our 64-bit FC6 machines) is not the desired one.
(Who ever will take care of this one may consider the above as hint where to start the investigation.)
## Comment 8354
Date: 2007-11-07 17:44:40 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
does file(1) actually agree that it is a 64-bits binary?
## Comment 8355
Date: 2007-11-07 18:00:51 +0100
From: @MarcinZukowski
Logged In: YES
user_id=607094
Originator: YES
Of course:
[17:58:51 marcin@kanda] /export/scratch0/marcin/BUILD/MonetDB-icc-DBGXPROF-32-32/src/gdk/.libs
$ grep 'CC=icc' ../../../config.log
$ /ufs/marcin/monet/MonetDB/configure CC=icc --prefix=/ufs/marcin/local/monet-icc-DBGXPROF-32-32 --enable-bi1970-01-01 01:00:32 +0100 --enable-oid32 --disable-profile --without-java --without-bz2 --enable-debug --disable-optimize
$ file libbat_la-gdk_align.o
libbat_la-gdk_align.o: ELF 64-bit LSB relocatable, x86-64, version 1 (GNU/Linux), not stripped
## Comment 8356
Date: 2007-11-07 18:22:08 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
[on our desktops at CWI]
$ icc --help | egrep '32|64'
while also generating generic IA-32 code. <codes> includes
320 - gcc 3.2.x compatibility
-Wp64 print diagnostics for 64-bit porting
-W[no-]shorten-64-to-32
warn for values implicitly converted from a 64-bit to
a 32-bit type. Similar to -Wp64
extended - rounds intermediates in 64-bit (extended) precision
-pc32 set internal FPU precision to 24 bit significand
-pc64 set internal FPU precision to 53 bit significand
-pc80 set internal FPU precision to 64 bit significand (DEFAULT)
-auto-ilp32 specify that the application cannot exceed a 32-bit
$ type -a icc
icc is /usr/local/bin/icc
$ ls -l /usr/local/bin/icc
/usr/local/bin/icc -> /soft/64/icc-10.0.023/bin/icc*
$ ls -l /soft/64/icc-10.0.023/bin/icc
/soft/64/icc-10.0.023/bin/icc*
$ ls -l /soft/32/icc-10.0.023/bin/icc
/soft/32/icc-10.0.023/bin/icc*
$ cat > hello.c
include <stdlib.h>
include <stdio.h>
int main () {
printf("Hello\n");
return 0;
}
$ /soft/64/icc-10.0.023/bin/icc -o hello hello.c ; file hello ; ./hello
hello: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped
Hello
$ /soft/32/icc-10.0.023/bin/icc -o hello hello.c ; file hello ; ./hello
hello: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped
Hello
In other words, icc does not seem to offer a commandline swithc to enable 32-bit compilation.
But .../configure CC=/soft/32/icc-10.0.023/bin/icc might do the job...
## Comment 8357
Date: 2007-11-21 16:08:02 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Fixed in CVS (MonetDB_1-20 branch of buildtools).
Intel's icc does not provide a command line option to switch between 32- & 64-bit compilation;
hence, configure now detects if icc is used together with "--enable-bi1970-01-01 01:00:00 +0100",
and if so, bails-out, advising the user to chose the proper 32- or 64-bit version of icc
using variables CC & PATH.
## Comment 8358
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1827627 at http://sourceforge.net/support/tracker.php?aid=1827627
| --enable-bits doesn't work with icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1478/comments | 0 | 2020-11-30T09:40:02Z | 2024-06-27T11:26:50Z | https://github.com/MonetDB/MonetDB/issues/1478 | 753,318,647 | 1,478 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-07 04:39:59 +0100
From: Maurice van Keulen <<mvankeulen>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2010-08-20 14:04:03 +0200
## Comment 8346
Date: 2007-11-07 16:39:59 +0100
From: Maurice van Keulen <<mvankeulen>>
(needs --enable-probxml=yes)
(stable 0.20; compiled on Suse Linux)
Attached file contains two documents, the probxml.xq module and a query "http://sourceforge.net/support/tracker.php?aid=16.xq" (you need to adapt the path in the import-statement of the query to the location of probxml.xq).
When running this query, I get the following error message:
!ERROR: CMDleftjoin: operation failed.
I wrote a small script that adds line numbers to the generated MIL. The file "http://sourceforge.net/support/tracker.php?aid=16.mil" is the result of "pf http://sourceforge.net/support/tracker.php?aid=16.xq" with line number printing added to it. If you execute it with "mclient -lmil http://sourceforge.net/support/tracker.php?aid=16.mil" you see that it stops at number 13645:
var oidMap_expOid := outer002.chk_order().leftjoin(iter_expOid.chk_order());
## Comment 8347
Date: 2007-11-07 16:53:45 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
is there any output/message prior to
"!ERROR: CMDleftjoin: operation failed."
?
if so what does it say?
## Comment 8348
Date: 2007-11-07 17:03:31 +0100
From: Maurice van Keulen <<mvankeulen>>
Logged In: YES
user_id=654674
Originator: YES
There is no output before this message
... but I just found out that I set one parameter wrong which caused a blow-up of the constructed elements. Setting the parameter to the correct value doesn't produce the error, so I presume it is caused by some overflow somewhere.
I close the bug by giving it status "Deleted" and resolution "Invalid".
Sorry for wasting some of your time on diagnosis.
## Comment 8349
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1827614 at http://sourceforge.net/support/tracker.php?aid=1827614
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
Bug has invalid status, setting status to "NEW".
Previous status was "DELETED".
## Comment 14338
Date: 2010-07-09 15:16:10 +0200
From: @sjoerdmullender
Bug was DELETED in SF.
| MXQ error CMDleftjoin operation failed | https://api.github.com/repos/MonetDB/MonetDB/issues/1477/comments | 0 | 2020-11-30T09:40:00Z | 2024-06-28T13:30:37Z | https://github.com/MonetDB/MonetDB/issues/1477 | 753,318,619 | 1,477 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-06 11:05:24 +0100
From: @grobian
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2007-11-07 01:17:58 +0100
## Comment 8343
Date: 2007-11-06 11:05:24 +0100
From: @grobian
Merovingian cannot start out of the box, as the dbfarm doesn't exist. The makefiles should pre-create the dbfarm for a fool-proof installation.
## Comment 8344
Date: 2007-11-07 13:17:58 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
fixed in cvs.
## Comment 8345
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1826708 at http://sourceforge.net/support/tracker.php?aid=1826708
| Merovingian: cannot start out of the box, as dbfarm doesn't | https://api.github.com/repos/MonetDB/MonetDB/issues/1476/comments | 0 | 2020-11-30T09:39:57Z | 2024-06-27T11:26:48Z | https://github.com/MonetDB/MonetDB/issues/1476 | 753,318,588 | 1,476 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-06 11:00:38 +0100
From: @grobian
To: @sjoerdmullender
Version: -- development
Last updated: 2007-11-07 01:09:57 +0100
## Comment 8340
Date: 2007-11-06 11:00:38 +0100
From: @grobian
In the ebuild I made for MonetDB5 I see on both pegasus and a solaris 10 machine that the log path is generated to be ${prefix}/var/lib/log. On pegasus using bootstrapped sources I get ${prefix}/var/log.
I noticed sjoerd made the releases using (rather old) autoconf 2.59, whereas I use 2.61, which perhaps does a different expansion for ${localstatedir}.
## Comment 8341
Date: 2007-11-07 13:09:57 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
localstatedir is not the right thing to use.
## Comment 8342
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1826702 at http://sourceforge.net/support/tracker.php?aid=1826702
| M5/Merovingian: logs end up in /var/lib/log??? | https://api.github.com/repos/MonetDB/MonetDB/issues/1475/comments | 0 | 2020-11-30T09:39:55Z | 2024-06-28T13:31:27Z | https://github.com/MonetDB/MonetDB/issues/1475 | 753,318,561 | 1,475 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-06 08:09:54 +0100
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2007-11-07 06:59:10 +0100
## Comment 8336
Date: 2007-11-06 08:09:54 +0100
From: @drstmane
Since
===================================================================
2007/10/29 - nielsnes: ./sql/src/backends/monet4/sql_session.mx,1.230.2.4
cleanup of global variable creation (code resembles m5 version again)
also fixed a leak (free stmt as its dupped in the set_var call)
===================================================================
test sql/src/benchmark/ATIS/Tests/cache.sql segfaults (strangely with icc, only) in the strcmp() in line 1364 of sql/src/server/sql_mvc.mx's stack_set_var(), called from line 741 of sql/src/backends/monet4/sql_session.mx, as variable "char *name" is handed to stack_set_var() in sql/src/backends/monet4/sql_session.mx's global_variables() without being initialized.
I'm actually a bit puzzled, why it "happens to work" with gcc...
gdb did not help to find this (as it seems to initialize variables to 0 (NULL) be default) |-(
valgrind DID help to find this ;-)
N.B.:
Since sql/src/backends/monet4/Makefile.ag disabls the "X_CFLAGS", no compiler (is told to) detect(s) that the variable name "is used before its value is set".
|-((
## Comment 8337
Date: 2007-11-06 08:11:03 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
ps:
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/ntv.64.64.d-Fedora6/src_benchmarks_ATIS/cache.err.00.html
## Comment 8338
Date: 2007-11-07 06:59:10 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed by Niels' & my yesterday's checkins.
## Comment 8339
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1826627 at http://sourceforge.net/support/tracker.php?aid=1826627
| SQL/4: tests segfault due to uninitialized variable | https://api.github.com/repos/MonetDB/MonetDB/issues/1474/comments | 0 | 2020-11-30T09:39:52Z | 2024-06-27T11:26:46Z | https://github.com/MonetDB/MonetDB/issues/1474 | 753,318,539 | 1,474 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-01 01:55:48 +0100
From: @drstmane
To: Tom Schreiber <<ts-tum>>
Version: -- development
Last updated: 2007-11-06 10:19:01 +0100
## Comment 8331
Date: 2007-11-01 13:55:48 +0100
From: @drstmane
Hi Tom,
here's the second one ;-)
After your yesterday's changes, loading module pathfinder --- and hence *all* pathfinder tests that actually require the pathfinder runtime module --- fail with
========
loading module 'pathfinder'
!ERROR: DL_open: dlopen(/scratch/monet.GNU.64.64.d.29864/pathfinder/Fedora6/runtime/.libs/lib_pathfinder.so,258) -> Error: /scratch/monet.GNU.64.64.d.29864/pathfinder/Fedora6/runtime/.libs/lib_pathfinder.so: undefined symbol: PFxml2la_importXMLFromMemory.
!ERROR: TBL_openmod: DL_open: /scratch/monet.GNU.64.64.d.29864/pathfinder/Fedora6/runtime/.libs/lib_pathfinder.so: undefined symbol: PFxml2la_importXMLFromMemory.
!ERROR: TBL_loadmod: module load _pathfinder cancelled.
!ERROR: moduleClient: module(_pathfinder) load error.
!ERROR: DL_open: dlopen(/scratch/monet.GNU.64.64.d.29864/pathfinder/Fedora6/runtime/.libs/lib_xrpc_server.so,258) -> Error: /scratch/monet.GNU.64.64.d.29864/pathfinder/Fedora6/runtime/.libs/lib_pathfinder.so.0: undefined symbol: PFxml2la_importXMLFromMemory.
!ERROR: TBL_openmod: DL_open: /scratch/monet.GNU.64.64.d.29864/pathfinder/Fedora6/runtime/.libs/lib_pathfinder.so.0: undefined symbol: PFxml2la_importXMLFromMemory.
!ERROR: TBL_loadmod: module load _xrpc_server cancelled.
!ERROR: moduleClient: module(_xrpc_server) load error.
!ERROR: DL_open: dlopen(/scratch/monet.GNU.64.64.d.29864/pathfinder/Fedora6/runtime/.libs/lib_xrpc_client.so,258) -> Error: /scratch/monet.GNU.64.64.d.29864/pathfinder/Fedora6/runtime/.libs/lib_pathfinder.so.0: undefined symbol: PFxml2la_importXMLFromMemory.
!ERROR: TBL_openmod: DL_open: /scratch/monet.GNU.64.64.d.29864/pathfinder/Fedora6/runtime/.libs/lib_pathfinder.so.0: undefined symbol: PFxml2la_importXMLFromMemory.
!ERROR: TBL_loadmod: module load _xrpc_client cancelled.
!ERROR: moduleClient: module(_xrpc_client) load error.
PF/Tijah module v0.3.0 loaded. http://dbappl.cs.utwente.nl/pftijah
!ERROR: interpret: no matching MIL operator to 'xquery_start_query_cache(lng)'.
========
See
http://monetdb.cwi.nl/projects/monetdb/Development/TestWeb/Current/pathfinder/index.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/index_short.html
and in particular
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/runtime/load.out.00.html
for details.
Next time, please try to ensure (at least) that module pathfinder in loadable prior to checking in your changes. Or better, run Mtest.py for at least the tests in pathfinder/runtime/, even better also for those in pathfinder/tests/ & pathfinder/compiler/, ideally also for those in pathfinder/benchmarks/ ...
Don't hesitate to ask for help in case you need any!
Stefan
## Comment 8332
Date: 2007-11-02 18:25:43 +0100
From: Tom Schreiber <<ts-tum>>
Logged In: YES
user_id=1926291
Originator: NO
Shame on me! The previous version of the "XML Importer" totally ignored the existence of MonetDB, and was developed and integrated and tested only in the scope of Pathfinder.
## Comment 8333
Date: 2007-11-03 04:43:47 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Thanks for the instant fix, Tom!
And don't worry, one of the purposes of automatic nightly multi-platform testing is actually to identify and locate the problems that you were not aware of (in particular when you joined the family).
The testing result emails and the TestWeb will tell you in case anything went wrong.
## Comment 8334
Date: 2007-11-06 10:19:01 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
TestWeb has confirmed Tom's fix.
Thanks!
Closing.
## Comment 8335
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1824042 at http://sourceforge.net/support/tracker.php?aid=1824042
| PF: loading module pathfinder fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1473/comments | 0 | 2020-11-30T09:39:50Z | 2024-06-27T11:26:45Z | https://github.com/MonetDB/MonetDB/issues/1473 | 753,318,505 | 1,473 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-11-01 01:48:04 +0100
From: @drstmane
To: Tom Schreiber <<ts-tum>>
Version: -- development
Last updated: 2007-11-06 10:19:27 +0100
## Comment 8326
Date: 2007-11-01 13:48:04 +0100
From: @drstmane
Hi Tom,
first of all an honest warm and hearty welcome to the MonetDB developers family!!
Obviously, your first checkin did not pass unnoticed ;-)
With Intel's icc, compilation of your new code fails with
========
icc -no-gcc -fPIC -DHAVE_CONFIG_H -I. -I/scratch/monet.ntv.64.64.d.29864/pathfinder/compiler/xmlimport -I../.. -I/scratch/monet.ntv.64.64.d.29864/pathfinder/compiler/xmlimport -I../include -I/scratch/monet.ntv.64.64.d.29864/pathfinder/compiler/xmlimport/../include -I/scratch/monet.ntv.64.64.d.29864/MonetDB/.ntv.6
4.64.d-Fedora6/include/MonetDB -I/scratch/monet.ntv.64.64.d.29864/MonetDB/.ntv.64.64.d-Fedora6/include/MonetDB/common -I/scratch/monet.ntv.64.64.d.29864/MonetDB/.ntv.64.64.d-Fedora6/include/MonetDB/gdk -I/usr/include/libxml2 -DLIBXMLIMPORT -we140 -wd1418 -Wall -w2 -std=c99 -mp1 -O0 -restrict -unroll -axWPT -we266
-Werror -wd1418,1419,279,981,810,193,111,1357,1572,1599 -c /scratch/monet.ntv.64.64.d.29864/pathfinder/compiler/xmlimport/xml2lalg_xpath_utils.c -DPIC -o .libs/libxmlimport_la-xml2lalg_xpath_utils.o
/scratch/monet.ntv.64.64.d.29864/pathfinder/compiler/xmlimport/xml2lalg_xpath_utils.c(277): error 1011: missing return statement at end of non-void function "PFxml2la_xpath_getBoolValue"
}
^
compilation aborted for /scratch/monet.ntv.64.64.d.29864/pathfinder/compiler/xmlimport/xml2lalg_xpath_utils.c (code 2)
make[5]: *** [libxmlimport_la-xml2lalg_xpath_utils.lo] Error 1
========
and there are many more similar errors;
for details, look for "***" in
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.ntv.64.64.d-Fedora6/make-k.out
## Comment 8327
Date: 2007-11-02 18:26:57 +0100
From: Tom Schreiber <<ts-tum>>
Logged In: YES
user_id=1926291
Originator: NO
Oops, I wasn't aware of icc's rigorous data-flow analysis that expects a proper return value even for "exit-paths" (PFoops...).
## Comment 8328
Date: 2007-11-03 04:44:08 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Thanks for the instant fix, Tom!
And don't worry, one of the purposes of automatic nightly multi-platform testing is actually to identify and locate the problems that you were not aware of (in particular when you joined the family).
The testing result emails and the TestWeb will tell you in case anything went wrong.
## Comment 8329
Date: 2007-11-06 10:19:27 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
TestWeb has confirmed Tom's fix.
Thanks!
Closing.
## Comment 8330
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1824035 at http://sourceforge.net/support/tracker.php?aid=1824035
| PF: compilation fails with Intel's icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1472/comments | 0 | 2020-11-30T09:39:47Z | 2024-06-27T11:26:44Z | https://github.com/MonetDB/MonetDB/issues/1472 | 753,318,467 | 1,472 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-10-31 11:20:25 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2007-10-31 01:05:10 +0100
## Comment 8323
Date: 2007-10-31 11:20:25 +0100
From: @romulogoncalves
Dear developers,
I am using linux and the current cvs branch for MonetDB5 and SQL.
If I create the tables:
CREATE TABLE parent (key int PRIMARY KEY);
CREATE TABLE child (parent_key int REFERENCES parent (key) ON DELETE
CASCADE);
INSERT INTO parent VALUES (1);
INSERT INTO child VALUES (1);
And then restart my mserver5 and execute the query:
DELETE FROM parent WHERE key = 1;
The cascade deletion is not performed because the catalog information for keys is wrong. This means that the information to perform the cascade delete (fkey->on_delete) is 0 (NO_ACTION) instead of 1 (CASCADE).
If the mserver is not restarted the value is correct.
After some debug I got some useful information:
I also checked the catalog load (when the mserver is restarted) and the value is set correctly. However, when I do the bin of the schema (normally done with mvc_bind_schema) the information is incorrect.
I hope my description is useful to fix the bug.
Regards,
Romulo
## Comment 8324
Date: 2007-10-31 13:05:09 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
the structures are (after loading) copied for each client, ie the key_dup functions did not correctly propagate the on_delete value
The fix and committed in the stable branch. Now we just need to wait for the propagation to have fixed in the current branch.
A test was also added (the log message):
Add tests for bug:
cascade_operations_in_different_sessions.SF-1823387
The test is done with two files:
cascade_operations_in_different_sessions.SF-1823387_create
to load the data and then the Mserver is restarted by Mtest.
cascade_operations_in_different_sessions.SF-1823387_drop
to perform the delete and check if it was done correctly.
In this way no scripts are needed and we are sure that the Mserver was restarted.
Regards,
Romulo
## Comment 8325
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1823387 at http://sourceforge.net/support/tracker.php?aid=1823387
| Cascade operations in different sessions... | https://api.github.com/repos/MonetDB/MonetDB/issues/1471/comments | 0 | 2020-11-30T09:39:44Z | 2024-06-27T11:26:43Z | https://github.com/MonetDB/MonetDB/issues/1471 | 753,318,442 | 1,471 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-10-31 11:06:00 +0100
From: Maurice van Keulen <<mvankeulen>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2007-10-31 04:07:43 +0100
## Comment 8320
Date: 2007-10-31 11:06:00 +0100
From: Maurice van Keulen <<mvankeulen>>
(algebra backend only)
The attached query gives the following type error:
type error: body of pxml:complete() evaluates to `node*' which is not a subtype of `element list { item* }*'
halted in typecheck.brg (reduce), line 1207
Apparently. the "with ... seeded by ... recurse ..." expression has the type node*. Removing the return type specification on the function works fine (YESSS!!! one of the major stumbling blocks for porting my probxml code to algebra has been solved!!!). I do need a better type because it effectively prohibits any navigation on the result, e.g., changing the bottom part to
for $l in pxml:complete($pk)
return <list>{for $c in $l/c return $c}</list>
gives
fatal error: Sorry, I cannot translate the test for type `node*'
## Comment 8321
Date: 2007-10-31 16:06:57 +0100
From: Maurice van Keulen <<mvankeulen>>
Logged In: YES
user_id=654674
Originator: YES
The correct type can be enforced by saying
with $result as element(list)* seeded by ... recurse ...
So, no bug after all.
## Comment 8322
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1823378 at http://sourceforge.net/support/tracker.php?aid=1823378
| Incorrect return type of "with - seeded by - recurse" | https://api.github.com/repos/MonetDB/MonetDB/issues/1470/comments | 0 | 2020-11-30T09:39:42Z | 2024-06-28T13:31:26Z | https://github.com/MonetDB/MonetDB/issues/1470 | 753,318,419 | 1,470 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-10-30 03:25:56 +0100
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2007-12-01 02:22:40 +0100
## Comment 8316
Date: 2007-10-30 15:25:56 +0100
From: @drstmane
With nightly testing, test
sql/src/test/mapi/Tests/python_dbapi_embedded.*
is bound to fail as the test and/or the embedded python version of MonetDB itself does not (yet?) (allow to) exploit the information given in MONET_MOD_PATH to find the sql_server (M4) resp. sql (M5) module, which are not in the default M4/M5 module search path, neither during SQL/4's `make check` (`sh RunMtest`) as the module has not been installed at all, yet, nor during SQL/5's `Mtest.py -r` as nightly testing uses individual prefixes for all packages.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.32.d-Fedora6/src_test_mapi/python_dbapi_embedded.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.32.d-Fedora6/src_test_mapi/python_dbapi_embedded.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql5/.mTests103/GNU.64.32.d-Fedora6/src_test_mapi/python_dbapi_embedded.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql5/.mTests103/GNU.64.32.d-Fedora6/src_test_mapi/python_dbapi_embedded.err.00.html
## Comment 8317
Date: 2007-10-30 19:01:37 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Embedding monetdb/sql into python requires an api in python, this is currently limited to setting dbfarm and dbname, ie all settings MOD_PATH etc are taken from the config file(s). Not sure if we could correct the monetdb5.conf and Mserver.conf files for testing?
## Comment 8318
Date: 2007-12-01 14:22:40 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
the latest fixes by stefan fixed the problem. This is a bugreport about a failing test, ie no
new tests needed.
## Comment 8319
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1822816 at http://sourceforge.net/support/tracker.php?aid=1822816
| SQL: python_dbapi_embedded test bound to fail in TestWeb | https://api.github.com/repos/MonetDB/MonetDB/issues/1469/comments | 0 | 2020-11-30T09:39:40Z | 2024-06-27T11:26:41Z | https://github.com/MonetDB/MonetDB/issues/1469 | 753,318,390 | 1,469 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-10-25 11:57:31 +0200
From: Maurice van Keulen <<mvankeulen>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2007-10-30 07:09:25 +0100
## Comment 8311
Date: 2007-10-25 11:57:31 +0200
From: Maurice van Keulen <<mvankeulen>>
The attached query (no document needed) crashes the server with:
MonetDB>*** glibc detected *** malloc(): memory corruption: 0x09b9da78 ***
If you set the $pta and $ptb variables at the bottom to $testworks1 and $testworks2 instead, then the query works fine.
I just downloaded and compiled (on Suse Linux) a fresh stable version of MonetDB/XQuery 0.20 by checking out the following braches of modules from sourceforge:
buildtools branch MonetDB_1-20
MonetDB branch MonetDB_1-20
clients branch Clients_1-20
MonetDB4 branch MonetDB_4-20
pathfinder branch XQuery_0-20
## Comment 8312
Date: 2007-10-25 13:35:03 +0200
From: Maurice van Keulen <<mvankeulen>>
Logged In: YES
user_id=654674
Originator: YES
CVS head version runs the query correctly once, but crashes upon a second try. Looks like coincidence.
## Comment 8313
Date: 2007-10-25 14:32:19 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Before others (also) loose time on investigating this problem:
Please note that the attached query requires the non-default "probxml" extensions, i.e., pathfinder needs to be configured with "--enable-probxml" !
(I currently don't have such pathfinder readily compiled, and not much time to compile one right now...)
## Comment 8314
Date: 2007-10-30 19:09:25 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
(hopefully) fixed in CVS (XQuery_0-20 branch):
While Maurice reported
"*** glibc detected *** malloc(): memory corruption: 0x09b9da78 ***"
as error, I got
"*** glibc detected *** Mserver: double free or corruption (!prev): 0x00002aaabde0bc20 ***",
and a simple gdb run revealed that the failing GDKfree() was called
in line 142 of pathfinder/modules/probxml/probxml.mx:
"GDKfree(matrix);".
A quick look at the code revealed that an incorrect linearization
of 2-dim matrix indeces to 1-dim array indeces could (potentially)
lead to corruption of the data, in particular the header/prefix
of a GDKmalloc()-ed array.
Fixing the linearization macro made the given query (http://sourceforge.net/support/tracker.php?aid=14.xq)
work fine, again --- well, at least it does not crash any more
and returns a result; I have no idea, whether the result is correct
or not... Please check!
Lessons learned:
- There are bugs (also) in code that was not produced at CWI.
- GDK'\''s memory sanity checks helped to find a bug in probxml code.
- gdb is a very handy tool --- provided it is indeed used.
[Test cannot be added to CVS as "--enable-probxml" is not default (yet?) ...]
## Comment 8315
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1819868 at http://sourceforge.net/support/tracker.php?aid=1819868
| PF/probxml: Memory corruption in MXQ 0.20 | https://api.github.com/repos/MonetDB/MonetDB/issues/1468/comments | 0 | 2020-11-30T09:39:37Z | 2024-06-27T11:26:40Z | https://github.com/MonetDB/MonetDB/issues/1468 | 753,318,358 | 1,468 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-10-24 11:31:00 +0200
From: @sjoerdmullender
To: @sjoerdmullender
Version: -- development
Last updated: 2007-11-16 08:48:59 +0100
## Comment 8306
Date: 2007-10-24 11:31:00 +0200
From: @sjoerdmullender
The python_dbapi and python_dbapi_embedded in sql/src/test/mapi fail when run in the testweb.
The reason for this is because the MonetDB and clients packages are installed in different directories.
In MonetDB/src/common there are a couple of Python files which get installed in PYTHON_LIBDIR/MonetDB. One of the files installed is __init__.py which turns the directory into an importable Python module. In clients/src/python/Cimpl some more files are installed into that same (supposedly) directory. But since in the testweb, the directories are not the same, MonetDB.CMapi is not found. You can't install an extra __init__.py into the directory for several reasons: it is not a good idea to overwrite installed files; and it is not possible to have two identically named but distinct Python modules (i.e. the one from MonetDB/src/common and the one from clients/src/python/Cimpl).
I don't know the solution to this.
## Comment 8307
Date: 2007-10-24 14:32:28 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
In the test scripts,
I extended PYTHONPATH to find CMapi in client-prefix
in case clients-prefix differs from MonetDB-prefix.
Tonight's testing will show whether this helps, or not...
## Comment 8308
Date: 2007-10-25 10:14:10 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
The import of CMapi seems to work, now.
Sjoerd seems to be taking care of (some of) the remaining problems with these tests and/or the implementation of CMapi.py itself.
...
## Comment 8309
Date: 2007-11-16 20:48:59 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
the ohter problem is python_dbapi_embedded, which now has its own bug report. So this one can be closed.
## Comment 8310
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1819168 at http://sourceforge.net/support/tracker.php?aid=1819168
| sql/src/test/mapi/python_dbapi test fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1467/comments | 0 | 2020-11-30T09:39:35Z | 2024-06-27T11:26:39Z | https://github.com/MonetDB/MonetDB/issues/1467 | 753,318,324 | 1,467 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-10-22 03:08:49 +0200
From: @grobian
To: Documentation maintainers <<bugs-docs>>
Version: unspecified
Last updated: 2007-10-22 03:15:36 +0200
## Comment 8303
Date: 2007-10-22 15:08:49 +0200
From: @grobian
The URL mentioned in the latest release notes doesn't exist:
http://monetdb.cwi.nl/projects/monetdb/Development/Releases/Version4.20/
## Comment 8304
Date: 2007-10-22 15:15:36 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
I wasn't supposed to read any release notes.
## Comment 8305
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1817885 at http://sourceforge.net/support/tracker.php?aid=1817885
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-docs@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| website: invalid URL in release notes | https://api.github.com/repos/MonetDB/MonetDB/issues/1466/comments | 0 | 2020-11-30T09:39:32Z | 2024-06-28T13:31:26Z | https://github.com/MonetDB/MonetDB/issues/1466 | 753,318,295 | 1,466 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-10-17 09:31:24 +0200
From: Hans <<hans_0_>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2007-10-22 10:52:34 +0200
## Comment 8299
Date: 2007-10-17 09:31:24 +0200
From: Hans <<hans_0_>>
version: Supersource tarball SR3.
Compiled on fedora core 5, 64-bit with 32-bits oid.
While inserting a previously deleted object in a DB, a ERROR: CMDdelete_bat_bun: operation failed occurs.
The operation is completed, but raises an error.
I started with a small document "proj.xml", and executed a small script "erroneous.xq". The result is enclosed too.
Regards,
Hans van Rijswijk.
[xiraf@namibia hans]$ cat proj.xml
<?xml version="1.0" encoding="utf-8"?>
<projects>
<project name="consumer02"><index>consumer02.xml</index><notes>notes_consumer02.xml</notes><description>aap</description></project>
<project name="hackingCase"><index>hackingCase.xml</index><notes>notes_hackingCase.xml</notes><description>This is the hacking case</description></project>
</projects>
$ cat erroneous.xq
pf:add-doc("/home/xiraf/hans/proj.xml", "proj.xml", "proj.xml", 10)
<>
doc("proj.xml")
<>
let $proj := element project {
attribute name {"consumer02a"},
element index {"consumer02.xml"},
element notes {"notes_consumer02a.xml"},
element description {"Consumer A"}
} return do insert $proj as last into doc("proj.xml")/projects
<>
doc("proj.xml")
<>
do delete doc("proj.xml")/projects/project[@name='consumer02a']
<>
doc("proj.xml")
<>
let $proj := element project {
attribute name {"consumer02a"},
element index {"consumer02.xml"},
element notes {"notes_consumer02a.xml"},
element description {"Consumer A"}
} return do insert $proj as last into doc("proj.xml")/projects
<>
doc("proj.xml")
<>
$ cat erroneous.xq | /opt/MonetDB-4.18/bin/MapiClient -h uganda -lxq
<?xml version="1.0" encoding="utf-8"?>
<projects>
<project name="consumer02"><index>consumer02.xml</index><notes>notes_consumer02.xml</notes><description>aap</description></project>
<project name="hackingCase"><index>hackingCase.xml</index><notes>notes_hackingCase.xml</notes><description>This is the hacking case</description></project>
</projects>
<?xml version="1.0" encoding="utf-8"?>
<projects>
<project name="consumer02"><index>consumer02.xml</index><notes>notes_consumer02.xml</notes><description>aap</description></project>
<project name="hackingCase"><index>hackingCase.xml</index><notes>notes_hackingCase.xml</notes><description>This is the hacking case</description></project>
<project name="consumer02a"><index>consumer02.xml</index><notes>notes_consumer02a.xml</notes><description>Consumer A</description></project></projects>
<?xml version="1.0" encoding="utf-8"?>
<projects>
<project name="consumer02"><index>consumer02.xml</index><notes>notes_consumer02.xml</notes><description>aap</description></project>
<project name="hackingCase"><index>hackingCase.xml</index><notes>notes_hackingCase.xml</notes><description>This is the hacking case</description></project>
</projects>
MAPI = monetdb@uganda:50000
QUERY = let $proj := element project {
ERROR = !ERROR: CMDdelete_bat_bun: operation failed.
<?xml version="1.0" encoding="utf-8"?>
<projects>
<project name="consumer02"><index>consumer02.xml</index><notes>notes_consumer02.xml</notes><description>aap</description></project>
<project name="hackingCase"><index>hackingCase.xml</index><notes>notes_hackingCase.xml</notes><description>This is the hacking case</description></project>
<project name="consumer02a"><index>consumer02.xml</index><notes>notes_consumer02a.xml</notes><description>Consumer A</description></project></projects>
$
## Comment 8300
Date: 2007-10-17 09:40:23 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Appears to work fine with the latest CVS code base from the *_?-20 release branches, i.e., the upcoming release (at least with 64-bit OIDs on my 64-bit FC6 machine):
$ cat /tmp/erroneous.xq | mclient -lxq
<?xml version="1.0" encoding="utf-8"?>
<projects>
<project name="consumer02"><index>consumer02.xml</index><notes>notes_consumer02.xml</notes><description>aap</description></project>
<project name="hackingCase"><index>hackingCase.xml</index><notes>notes_hackingCase.xml</notes><description>This is the hacking case</description></project>
</projects>
<?xml version="1.0" encoding="utf-8"?>
<projects>
<project name="consumer02"><index>consumer02.xml</index><notes>notes_consumer02.xml</notes><description>aap</description></project>
<project name="hackingCase"><index>hackingCase.xml</index><notes>notes_hackingCase.xml</notes><description>This is the hacking case</description></project>
<project name="consumer02a"><index>consumer02.xml</index><notes>notes_consumer02a.xml</notes><description>Consumer A</description></project></projects>
<?xml version="1.0" encoding="utf-8"?>
<projects>
<project name="consumer02"><index>consumer02.xml</index><notes>notes_consumer02.xml</notes><description>aap</description></project>
<project name="hackingCase"><index>hackingCase.xml</index><notes>notes_hackingCase.xml</notes><description>This is the hacking case</description></project>
</projects>
<?xml version="1.0" encoding="utf-8"?>
<projects>
<project name="consumer02"><index>consumer02.xml</index><notes>notes_consumer02.xml</notes><description>aap</description></project>
<project name="hackingCase"><index>hackingCase.xml</index><notes>notes_hackingCase.xml</notes><description>This is the hacking case</description></project>
<project name="consumer02a"><index>consumer02.xml</index><notes>notes_consumer02a.xml</notes><description>Consumer A</description></project></projects>
## Comment 8301
Date: 2007-10-22 22:52:34 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Added test in pathfinder/tests/BugTracker/Tests/repeated-insert.SF-1814911*
Works fine with the just released MonetDB/XQuery 0.20.
## Comment 8302
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1814911 at http://sourceforge.net/support/tracker.php?aid=1814911
| xq: Repeated insert fails (CMDdelete_bat_bun: operation fai) | https://api.github.com/repos/MonetDB/MonetDB/issues/1465/comments | 0 | 2020-11-30T09:39:30Z | 2024-06-27T11:26:37Z | https://github.com/MonetDB/MonetDB/issues/1465 | 753,318,263 | 1,465 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-10-17 01:12:31 +0200
From: bjbuter <<bjbuter>>
To: @njnes
Version: -- development
Last updated: 2007-11-16 08:47:41 +0100
## Comment 8291
Date: 2007-10-17 01:12:31 +0200
From: bjbuter <<bjbuter>>
The Python client in /clients/src/python/Cimpl
after issuing cvs -d:pserver:anonymous@monetdb.cvs.sourceforge.net:/cvsroot/monetdb checkout clients, needs some hacks to work.
specifically:
in CMapi.py: the MapiLib.mapi_connect requires a dbname other than the default None, else a connection to the database cannot be established.
in MonetSQLdb/__init__.py
from CMapi import *
leads to errors, CMapi cannot be found this should be:
from MonetDB.CMapi import *
(when a dbname is required in CMapi, MonetSQLdb/__init__ should use CMapi with this dbname when using CMapi)
diffs of these hacks are provided
greetings
Bart
## Comment 8292
Date: 2007-10-17 01:20:53 +0200
From: bjbuter <<bjbuter>>
Logged In: YES
user_id=1624832
Originator: YES
I forgot to add a big annoyance, though not critical, the Python client does not relay any error messages from MonetDB. If anything goes wrong it issues a RuntimeError:None instead of the more detailed response the normal MapiClient gives.
Bart
## Comment 8293
Date: 2007-10-21 20:22:13 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Niels is taking care of it.
## Comment 8294
Date: 2007-10-23 09:08:20 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
bart could you check if the current code in the stable branch fixed your problems.
## Comment 8295
Date: 2007-11-06 20:31:31 +0100
From: bjbuter <<bjbuter>>
Logged In: YES
user_id=1624832
Originator: YES
Did: cvs -d:pserver:anonymous@monetdb.cvs.sourceforge.net:/cvsroot/monetdb co buildtools MonetDB clients
build: buildtools & MonetDD
then in clients:
./bootstrap
./configure
./configure --prefix=/home/bjbuter --with-python
however this chokes in odbc with
Making all in odbc
make[4]: Entering directory `/tmp/clients/src/odbc'
make all-recursive
make[5]: Entering directory `/tmp/clients/src/odbc'
Making all in include
make[6]: Entering directory `/tmp/clients/src/odbc/include'
make[6]: *** No rule to make target `sql.h', needed by `all'. Stop.
make[6]: Leaving directory `/tmp/clients/src/odbc/include'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory `/tmp/clients/src/odbc'
make[4]: *** [all] Error 2
make[4]: Leaving directory `/tmp/clients/src/odbc'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/tmp/clients/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/tmp/clients/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/clients'
make: *** [all] Error 2
So no chance to check Python yet
## Comment 8296
Date: 2007-11-16 19:20:08 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
m h reports this fix to be sufficient. We should release this soon.
## Comment 8297
Date: 2007-11-16 20:47:41 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
the try/ except clause solves the problem. ie release needed and bug can be closed.
## Comment 8298
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1814768 at http://sourceforge.net/support/tracker.php?aid=1814768
| Python Client problems | https://api.github.com/repos/MonetDB/MonetDB/issues/1464/comments | 0 | 2020-11-30T09:39:27Z | 2024-06-27T11:26:36Z | https://github.com/MonetDB/MonetDB/issues/1464 | 753,318,225 | 1,464 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-10-13 04:54:33 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2007-10-15 09:37:42 +0200
## Comment 8278
Date: 2007-10-13 16:54:33 +0200
From: @drstmane
After checkins on Wed Oct 10 2007 and/or Thu Oct 11 2007 (due to compilation problems, there were no pathfinder-testing results on Thu Oct 11 2007), 24 pathfinder tests fail. This might be considered a show-stopper for the upcoming release!
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/benchmarks_XMark/upd.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/benchmarks_XMark_alg/upd.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/runtime/namespaces.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/runtime/serialization.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/runtime/serialization-mclient.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/nested_doc.SF-1446426.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/NULL_BAT_in_serializer.SF-1694814b.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/polymorphic_sequences.SF-1497419.mps.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/replace-corrupts.SF-1758902.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/replace-corrupts.SF-1758902.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_i18n/good-006.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_Update/setattr-1.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_Update/insert-1.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_Update/insert-2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_Update/symm.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_Update/update.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_XQuery/attr_err.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_XQuery/element1.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_XQuery/element3.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_XQuery/element5.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_XQuery/element5.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_XQuery/element6.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_XQuery/fun6.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_XQuery/is2ns.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_XRpc/echoAll.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_XRpc/echoAll.err.00.html
## Comment 8279
Date: 2007-10-13 17:39:48 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
The only checkins to pathfinder on 2007/10/10 & 2007/10/11 were by Sjoerd, Jennie & Niels.
Those of Sjoerd & Jennie were most probably unrelated to this bug;
while that of Niels might be related (see attached log & diffs for details).
Niels,
would it be possible to revert your changes completely to the version of Wed Oct 10 2007 early morning (tagged as Stable_DailyBuild-10)?
File Added: log-diff
## Comment 8280
Date: 2007-10-13 18:01:48 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
reverting is not really a problem. But as you can see from my 2 line changes (one char -> signed char, one
to range removed as higher values aren't possible for the type), they are not very likely to cause problems.
## Comment 8281
Date: 2007-10-13 18:20:18 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
reverting the range check in isncnamechar seems to fix the first problematic test. Now just need to find out why.
## Comment 8282
Date: 2007-10-13 18:47:14 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Allthough \xfe .. \xff looks like the maximum of the the type (char) its not, its right in the middle (-8 till -1). So we need a different solution for the ppc compiler with 'unsigned' chars. So sjoerd shall
we revert this in the to be released?
## Comment 8283
Date: 2007-10-13 20:33:47 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Niels, Sjoerd,
what about the attached patch that explicitly makes all char's (variables and constants) inside isncnamechar() signed and explicitly casts the arguments in the two calls of isncnamechar() to (const signed char)?
Seems to work fine with gcc on Linux (FC6)...
File Added: signed_char_patch
## Comment 8284
Date: 2007-10-13 23:10:53 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Does this more minimalist patch also work?
|| (c >= '\xf8'
if '\xff' == -1
&& c <= '\xff'
endif
)
instead of the current
|| (c >= '\xf8' /* c <= '\xff'*/ )
This of course assumes that the preprocessor and the compiler agree on the signedness of char.
In any case, it looks like I will need to do a recompile. :-(
## Comment 8285
Date: 2007-10-14 00:14:53 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Yes, my patch does seem to work. The advantage is: no casts necessary.
## Comment 8286
Date: 2007-10-14 08:33:28 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
the borked ppc/gcc compiler seems to like this patch too.
## Comment 8287
Date: 2007-10-14 10:42:24 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
I'd like to check in a slightly different patch: in MonetDB.m4 I'll add a test AC_C_CHAR_UNSIGNED, and in scanner.l I'll change the if into ifndef __CHAR_UNSIGNED__.
## Comment 8288
Date: 2007-10-14 11:16:45 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Checked in. Tomorrow we'll see if this is actually fixed.
## Comment 8289
Date: 2007-10-15 09:37:42 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Sjoerd's fix seems to work fine. Thanks!
## Comment 8290
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1812882 at http://sourceforge.net/support/tracker.php?aid=1812882
| PF: 24 tests fail after recent checkins | https://api.github.com/repos/MonetDB/MonetDB/issues/1463/comments | 0 | 2020-11-30T09:39:24Z | 2024-06-27T11:26:35Z | https://github.com/MonetDB/MonetDB/issues/1463 | 753,318,182 | 1,463 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-10-12 06:29:46 +0200
From: @grobian
To: @sjoerdmullender
Version: -- development
Last updated: 2007-10-15 09:48:31 +0200
## Comment 8272
Date: 2007-10-12 18:29:46 +0200
From: @grobian
As detected on the monetdb-X ML, M5 spits out completely bogus data on --version due to some brain damage@127.0.0.1.
The to be attached patch supplies a workaround for the coming release by removing the bogus information. The issue should be solved, ideally by just using a plain C file instead of MX.
## Comment 8273
Date: 2007-10-12 21:44:22 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
The problem is a combination of Mx and configure. The file that produces the bogus information is mserver.mx.in. This file, in order to be included in the source tar ball, is processed by configure to produce mserver5.mx, which is then processed by Mx to produce mserver5.c. The latter processing is necessary for a source tar ball, but the former isn't. It's only necessary so that the latter can be done. If we could somehow reverse the two processes and postpone the processing by configure until the configure run by the end user, all would be well.
In the mean time, is this bug serious enough to jeopardize the release? (I.e., is it a show stopper?)
## Comment 8274
Date: 2007-10-12 21:50:18 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
I think the least we should do, is to remove the invalid information (as my patch does).
So yes. (If we hadn't found out the problem, we had a good reason to ignore it...)
## Comment 8275
Date: 2007-10-12 22:10:45 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
I'm not sure you realize how much work it is to make new release candidates. The work is, admittedly, mostly waiting, but it does take the better part of a day to do it all.
In other words, this is not something to take too lightly.
Having thought about the issue a little, I think this can wait until after the release, unless something really important crops up.
Lowering the priority.
## Comment 8276
Date: 2007-10-15 09:48:31 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Fixed by Niels' and Sjoerd's combined efforts to extract the configure-replaced part of mserver5.mx.in (i.e., function monet_version()) into a separate monet_version.c.in, tuning mserver5.mx.in back into a simple mserver5.mx, and fixing the buildtools (autogen) to handle .c.in files correctly.
Thanks!
## Comment 8277
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1812341 at http://sourceforge.net/support/tracker.php?aid=1812341
| M5: distribution tarballs contain non-sense data | https://api.github.com/repos/MonetDB/MonetDB/issues/1462/comments | 0 | 2020-11-30T09:39:21Z | 2024-06-27T11:26:34Z | https://github.com/MonetDB/MonetDB/issues/1462 | 753,318,163 | 1,462 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-10-11 02:36:18 +0200
From: @skinkie
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-04-07 04:29:03 +0200
## Comment 8266
Date: 2007-10-11 02:36:18 +0200
From: @skinkie
A fairly large document (20GB) inserting with 5% slack space results in a partial insert (without errors). But when querying anything for this document it gets the following error:
> xquery>
> more> fn:count(doc("planet.osm")//*)
> more>MAPI = monetdb@localhost:50000
> QUERY = fn:count(doc("planet.osm")//*)
> ERROR = !ERROR: [remap]: 5 times inserted nil due to errors at tuples
> 1@0, 2@0, 3@0, 4@0, 5@0.
> !ERROR: [remap]: first error was:
> !ERROR: CMDremap: operation failed.
> !ERROR: interpret_unpin: [remap] bat=492,stamp=-729 OVERWRITTEN
> !ERROR: BBPdecref: 1000000001_rid_nid does not have pointer fixes.
> !ERROR: interpret_params: leftfetchjoin(param 2): evaluation error.
Inserting the same document in read only mode works. Enough disk space is available. I'm using the -SR3 release.
The document itself can be obtained from an OpenStreetMap mirror.
## Comment 8267
Date: 2007-10-15 12:10:50 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
on request, Stfan provided the following detailed info about this problem:
PLATFORM INFO
=============
Monet Database Server V4.18.2
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs;
Gentoo, Linux, xen01 2.6.20-xen-r3 3 SMP Sun Oct 7 05:22:20 CEST 2007
x86_64 Intel(R) Xeon(R) CPU L5320 @ 1.86GHz GenuineIntel GNU/Linux
REPRODUCTION
============
- - Download http://mirror.openstreetmap.nl/planet/planet-071003.osm.bz2
- - Decompress the document.
- - Start the MonetDB4 server with Pathfinder module.
- - Add this document to the database server with 5 procent space for
updates.
- - Request any operation to this document will result in the failure
reported.
This error doesn't happen if the document was added without the ability
to update the document.
Also for you my current ls()
MonetDB>ls();
-----------------------------------------------------------------------------------------------------------------------------------------
name htype ttype count
heat dirty status kind refcnt lrefcnt name
str str str lng
int str str str int int type
-----------------------------------------------------------------------------------------------------------------------------------------
[ "1000000000_attr_own", "void", "oid", 747750437,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_attr_prop", "void", "oid", 747750437,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_attr_qn", "void", "oid", 747750437,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_frag_root", "oid", "oid", 1,
0, "clean", "disk", "pers", 0, 1 ]
[ "1000000000_map_pid", "void", "void", 42822,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_nid_rid", "void", "void", 701587412,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_prop_com", "void", "str", 0,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_prop_ins", "void", "str", 0,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_prop_text", "void", "str", 3,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_prop_tgt", "void", "str", 0,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_prop_val", "void", "str", 118077679,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_qn_histogram", "void", "lng", 19,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_qn_loc", "void", "str", 19,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_qn_nid", "oid", "oid", 271876931,
0, "clean", "disk", "pers", 0, 1 ]
[ "1000000000_qn_prefix", "void", "str", 19,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_qn_prefix_uri_loc", "void", "str", 19,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_qn_uri", "void", "str", 19,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_qn_uri_loc", "void", "str", 19,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_rid_kind", "void", "chr", 701587412,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_rid_level", "void", "chr", 701587412,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_rid_nid", "void", "void", 701587412,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_rid_prop", "void", "oid", 701587412,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_rid_size", "void", "int", 701587412,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000000_vx_hsh_nid", "int", "oid", 402481184,
0, "clean", "disk", "pers", 0, 1 ]
[ "1000000001_attr_own", "void", "oid", 754314985,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_attr_prop", "void", "oid", 754314985,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_attr_qn", "void", "oid", 754314985,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_frag_root", "oid", "oid", 1,
0, "clean", "disk", "pers", 0, 1 ]
[ "1000000001_map_pid", "void", "oid", 45450,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_nid_rid", "void", "oid", 707424150,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_prop_com", "void", "str", 0,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_prop_ins", "void", "str", 0,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_prop_text", "void", "str", 3,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_prop_tgt", "void", "str", 0,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_prop_val", "void", "str", 119784146,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_qn_histogram", "void", "lng", 19,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_qn_loc", "void", "str", 19,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_qn_prefix", "void", "str", 19,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_qn_prefix_uri_loc", "void", "str", 19,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_qn_uri", "void", "str", 19,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_qn_uri_loc", "void", "str", 19,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_rid_kind", "void", "chr", 744652800,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_rid_level", "void", "chr", 744652800,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_rid_nid", "void", "oid", 744652800,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_rid_prop", "void", "oid", 744652800,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000001_rid_size", "void", "int", 744652800,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_attr_own", "void", "oid", 754314985,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_attr_prop", "void", "oid", 754314985,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_attr_qn", "void", "oid", 754314985,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_frag_root", "oid", "oid", 1,
0, "clean", "disk", "pers", 0, 1 ]
[ "1000000002_map_pid", "void", "void", 43178,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_nid_rid", "void", "void", 707424150,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_prop_com", "void", "str", 0,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_prop_ins", "void", "str", 0,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_prop_text", "void", "str", 3,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_prop_tgt", "void", "str", 0,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_prop_val", "void", "str", 119784146,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_qn_histogram", "void", "lng", 19,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_qn_loc", "void", "str", 19,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_qn_nid", "oid", "oid", 273809205,
0, "clean", "disk", "pers", 0, 1 ]
[ "1000000002_qn_prefix", "void", "str", 19,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_qn_prefix_uri_loc", "void", "str", 19,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_qn_uri", "void", "str", 19,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_qn_uri_loc", "void", "str", 19,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_rid_kind", "void", "chr", 707424150,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_rid_level", "void", "chr", 707424150,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_rid_nid", "void", "void", 707424150,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_rid_prop", "void", "oid", 707424150,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_rid_size", "void", "int", 707424150,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000002_vx_hsh_nid", "int", "oid", 407415839,
0, "clean", "disk", "pers", 0, 1 ]
[ "1000000003_attr_own", "void", "oid", 5870236,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_attr_prop", "void", "oid", 5870236,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_attr_qn", "void", "oid", 5870236,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_frag_root", "oid", "oid", 1,
0, "clean", "disk", "pers", 0, 1 ]
[ "1000000003_map_pid", "void", "oid", 351,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_nid_rid", "void", "oid", 5455263,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_prop_com", "void", "str", 0,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_prop_ins", "void", "str", 0,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_prop_text", "void", "str", 3,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_prop_tgt", "void", "str", 0,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_prop_val", "void", "str", 1814631,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_qn_histogram", "void", "lng", 16,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_qn_loc", "void", "str", 16,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_qn_prefix", "void", "str", 16,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_qn_prefix_uri_loc", "void", "str", 16,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_qn_uri", "void", "str", 16,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_qn_uri_loc", "void", "str", 16,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_rid_kind", "void", "chr", 5750784,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_rid_level", "void", "chr", 5750784,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_rid_nid", "void", "oid", 5750784,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_rid_prop", "void", "oid", 5750784,
0, "clean", "disk", "pers", 0, 2 ]
[ "1000000003_rid_size", "void", "int", 5750784,
0, "clean", "disk", "pers", 0, 2 ]
[ "collection_name", "oid", "str", 4,
0, "clean", "load", "pers", 0, 2 ]
[ "collection_size", "oid", "lng", 4,
0, "clean", "disk", "pers", 0, 2 ]
[ "doc_collection", "oid", "oid", 6,
0, "clean", "load", "pers", 0, 2 ]
[ "doc_location", "oid", "str", 4,
0, "clean", "disk", "pers", 0, 2 ]
[ "doc_name", "oid", "str", 4,
0, "clean", "load", "pers", 0, 2 ]
[ "doc_timestamp", "oid", "timestamp", 4,
0, "clean", "disk", "pers", 0, 2 ]
[ "uri_lifetime", "str", "lng", 1,
0, "clean", "load", "pers", 0, 2 ]
[ "xquery_catalog", "int", "str", 86,
0, "clean", "load", "pers", 1, 1 ]
[ "xquery_seqs", "int", "lng", 1,
0, "clean", "load", "pers", 1, 2 ]
[ "xquery_snapshots", "int", "int", 0,
0, "clean", "load", "pers", 1, 2 ]
## Comment 8268
Date: 2007-10-21 20:17:42 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Please include the comments made by SM and your assessment,
planning etc.
## Comment 8269
Date: 2007-10-21 22:12:17 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
Hi Stefan, et al,
summary: the new release of XQuery (0.20) will fix the remap failing problem. However, until further fixes are made, performance problems on very large datasets will persist. Work continues to be underway on this.
The remap failing was just a bug.
The simple diagnosis why it remains slow is that with 8GB of memory and a 20GB document, there is too little to keep everything in RAM. My rule of thumb is that the file-size of all documents you are querying simultanuously should not be larger than your RAM size. You are violating that rule.
What is worse, on updatable documents, the index is created at "first use" and is *not* persistent, hence each time the database is restarted; the first query will take long, because it constructs the index. As you observed, constructing the index may take very long (>6 hours). It may help using a 64-bits OS but 32bit-oid binary. I have looked at your datasize and "it fits" within the constraints of 32bit-oids, which means that wrt 64bit-oids you win 50% memory usage for them (but of course, not nearly all data is oid-data). Given your extreme shortage of memory, saving space this way is a good idea after all.
I have looked into the question why under memory shortage index construction is so slow (>6 hours) and why also with the index available, the query remains slow (multiple minutes). This resulted in a patch that I attach to this bugreport, that you may test. Main thing is that I switched back to ordered indices from an unorderd index with a hash table. Under swapping, the hash table keeps getting lost, and also with swapping, sorted selections tend to be faster than (random access) hash selections.
The patch is applied by substituting the pathfinder.mil file in your installation by the attached file (decompress it first). NOTE: this pathfinder.mil *only* matches 0.20 installations, thus the new release!!
On a machine with 15GB memory, I can now create the index in 1 hour. Shredding is 25 minutes. Queries in 15 seconds. Whether it will work on your 8GB machine is questionable, but you may give it try.
As a general note, your problem triggered me to review the behavior of the (just added) value indices under memory pressure. The situation that a first query will necessarily take 1.5 hours is certainly undesirable. Sure, on data sizes smaller than 20GB, it is faster, but still sluggisch. I am now considering making the indices persistent for updatable documents as well (they already are for readonly ones), but doing so implies that changes to the index in its so-called delta structures will need to be logged during a commit, which is not yet implemented.
This is the main reason why the attached patch is not yet final, it is probable that I will switch to persistent indices if I find time to hack it in... to be continued
File Added: pathfinder.zip
## Comment 8270
Date: 2009-04-07 16:29:03 +0200
From: @peterboncz
performance will not be fixed further; the bug was fixed already
## Comment 8271
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1811229 at http://sourceforge.net/support/tracker.php?aid=1811229
| [ADT] Adding large document, with update support | https://api.github.com/repos/MonetDB/MonetDB/issues/1461/comments | 0 | 2020-11-30T09:39:18Z | 2024-06-27T11:26:33Z | https://github.com/MonetDB/MonetDB/issues/1461 | 753,318,122 | 1,461 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-10-09 07:41:26 +0200
From: @drstmane
To: Manuel Mayr <<mayrm>>
Version: -- development
Last updated: 2007-10-10 10:46:40 +0200
## Comment 8262
Date: 2007-10-09 19:41:26 +0200
From: @drstmane
When configure with --enable-strict --- which can unfortunately not be the default in the to-be distributed code base and hence in the Stable branch(es), as it might trigger "unnecessary compilation problems at user sites --- the latest changes to pfshed fail to compile with:
========
gcc -DHAVE_CONFIG_H -I. -I/export/scratch0/manegold/Monet/Testing/Stable/source/pathfinder/src/sqlhelpers/xmlshred -I../../.. -I/export/scratch0/manegold/Monet/Testing/Stable/source/pathfinder/src/sqlhelpers/xmlshred -I/export/scratch0/manegold/Monet/Testing/Stable/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/include/MonetDB -I/export/scratch0/manegold/Monet/Testing/Stable/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/include/MonetDB/common -I/export/scratch0/manegold/Monet/Testing/Stable/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/include/MonetDB/gdk -I/usr/include/libxml2 -I./include -I/export/scratch0/manegold/Monet/Testing/Stable/source/pathfinder/src/sqlhelpers/xmlshred/./include -I../../../compiler/include -I/export/scratch0/manegold/Monet/Testing/Stable/source/pathfinder/src/sqlhelpers/xmlshred/../../../compiler/include -I../../../compiler -I/export/scratch0/manegold/Monet/Testing/Stable/source/pathfinder/src/sqlhelpers/xmlshred/../../../compiler -Wall -Wextra -std=c99 -g -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2 -Wno-declaration-after-statement -D_REENTRANT -c /export/scratch0/manegold/Monet/Testing/Stable/source/pathfinder/src/sqlhelpers/xmlshred/encoding.c
cc1: warnings being treated as errors
/export/scratch0/manegold/Monet/Testing/Stable/source/pathfinder/src/sqlhelpers/xmlshred/encoding.c: In function ‘flush_node’:
/export/scratch0/manegold/Monet/Testing/Stable/source/pathfinder/src/sqlhelpers/xmlshred/encoding.c:215: warning: comparison between signed and unsigned
/export/scratch0/manegold/Monet/Testing/Stable/source/pathfinder/src/sqlhelpers/xmlshred/encoding.c: In function ‘characters’:
/export/scratch0/manegold/Monet/Testing/Stable/source/pathfinder/src/sqlhelpers/xmlshred/encoding.c:438: warning: comparison between signed and unsigned
make[7]: *** [encoding.o] Error 1
========
Please (try to) fix this a.s.a.p.
Moreover (for all of us, not only Manuel) explicitly configuring --enable-strict (the default for nightly testing also for the Stable branch!) is highly recommended to keep our code base clean and thus portable!
## Comment 8263
Date: 2007-10-09 21:55:03 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Since I ((too?) "generously") "allowed" Manuel'\''s last-minute checkin on the Stable branch,
I also take the freedom to feel "responsible" for it and take care of fixing the
"comparison between signed and unsigned"
warning (that is turned into an error when configured with --enable-strict)
by casting the signed value to unsigned, provided the former ar non-negative.
Manuel,
please double-check my fix and close this bug report in case it is OK.
## Comment 8264
Date: 2007-10-10 10:46:40 +0200
From: Manuel Mayr <<mayrm>>
Logged In: YES
user_id=1629542
Originator: NO
Hi Stefan,
thx for fixing.
Before I checked in those files I patched them into my HEAD directory (assuming the --enable-strict option is set for default).
Well, I've turned on this option now, seeing those warnings myself.
Thx for your suggestions.
Manuel
## Comment 8265
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1810292 at http://sourceforge.net/support/tracker.php?aid=1810292
| PF: compilation of pfshred fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1460/comments | 0 | 2020-11-30T09:39:15Z | 2024-06-27T11:26:32Z | https://github.com/MonetDB/MonetDB/issues/1460 | 753,318,091 | 1,460 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-10-08 06:23:48 +0200
From: Jan Rittinger <<jan.rittinger>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2009-11-12 10:35:49 +0100
## Comment 8256
Date: 2007-10-08 18:23:48 +0200
From: Jan Rittinger <<jan.rittinger>>
Currently (probably not after a restart anymore) the port 50001 on my PC is in use.
This causes MonetDB to crash if I load 'module(pathfinder)' whereas loading only 'module(mapi)' does not kill the Mserver:
$> Mserver --set='mapi_port=50000' --dbinit='module(mapi);'
MonetDB Server v4.21.0
based on GDK v1.21.0
Copyright (c) 1993-2007, CWI. All rights reserved.
Compiled for i686-suse-linux/32bit with 32bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
MonetDB>
$> Mserver --set='mapi_port=50001' --dbinit='module(mapi);'
MonetDB Server v4.21.0
based on GDK v1.21.0
Copyright (c) 1993-2007, CWI. All rights reserved.
Compiled for i686-suse-linux/32bit with 32bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
!ERROR: MAPIlisten:binding to stream socket (50001) failed
!OS: Address already in use
MonetDB>
$> Mserver --set='mapi_port=50000' --dbinit='module(pathfinder);'
MonetDB Server v4.21.0
based on GDK v1.21.0
Copyright (c) 1993-2007, CWI. All rights reserved.
Compiled for i686-suse-linux/32bit with 32bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.3.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.21.0 loaded
XRPC administrative console at http://localhost:50001/admin
01/Jan/1970 01:00:00 shttpd_open_port: bind(50001): Address already in use
$> Mserver --set='mapi_port=50001' --dbinit='module(pathfinder);'
MonetDB Server v4.21.0
based on GDK v1.21.0
Copyright (c) 1993-2007, CWI. All rights reserved.
Compiled for i686-suse-linux/32bit with 32bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.3.0 loaded. http://dbappl.cs.utwente.nl/pftijah
!ERROR: MAPIlisten:binding to stream socket (50001) failed
!OS: Address already in use
$>
## Comment 8257
Date: 2007-10-08 18:33:21 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
loading module sql_server also crashed the Msever instantly if the requested mapi_port is busy:
$ Mserver --dbinit='module(sql_server);'
MonetDB Server v4.20.0
based on GDK v1.20.0
Copyright (c) 1993-2007, CWI. All rights reserved.
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
!ERROR: MAPIlisten:binding to stream socket (50000) failed
!OS: Address already in use
$
## Comment 8258
Date: 2009-07-31 10:45:53 +0200
From: @sjoerdmullender
Added test in pathfinder/tests/BugTracker/Tests: port_busy.SF-1809586.
No correct stable output yet.
## Comment 8259
Date: 2009-11-12 10:35:49 +0100
From: @peterboncz
requested to remove this test
## Comment 8260
Date: 2009-11-25 15:28:03 +0100
From: @drstmane
===================================================================
2009/11/25 - stmane: testing/src/Mfilter.py.in,1.5.4.3
pathfinder/tests/BugTracker/Tests/port_busy.SF-1809586.py,1.2.6.3
pathfinder/tests/BugTracker/Tests/port_busy.SF-1809586.stable.err,1.2.6.1
pathfinder/tests/BugTracker/Tests/port_busy.SF-1809586.stable.out,1.2.6.1
slightly extended test and approved stable output for
ID: 1809586 "PF: busy port crashes Mserver"
https://sourceforge.net/tracker/?func=detail&aid=1809586&group_id=56967&atid=482468
and added extra Mfilter rule to cope with variable output
due to changing port numbers.
We accept the fact that starting a MonetDB/XQury server (`Mserver --dbinit="module(pathfinder);"`)
quits instantly (with a proper error message)
in case either the MAPIPORT or the XQUERYPORT are not available
(the server does not make much sense without access to these ports).
The default ports can easily be overwritten on the server commandline:
--set mapi_port=<portno> --set xrpc_port=<portno>
===================================================================
## Comment 8261
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1809586 at http://sourceforge.net/support/tracker.php?aid=1809586
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| PF: busy port crashes Mserver | https://api.github.com/repos/MonetDB/MonetDB/issues/1459/comments | 0 | 2020-11-30T09:39:13Z | 2024-06-28T13:31:25Z | https://github.com/MonetDB/MonetDB/issues/1459 | 753,318,063 | 1,459 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-10-08 03:10:36 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2007-10-16 11:25:54 +0200
## Comment 8250
Date: 2007-10-08 15:10:36 +0200
From: @grobian
Am I the only one having this?
make[5]: Entering directory `/net/pegasus.ins.cwi.nl/export/scratch0/fabian/vtmp/build-stable-pegasus.ins.cwi.nl/clients/src/mapiclient'
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I/ufs/fabian/scratch/monetdb/stable/clients/src/mapiclient -I/ufs/fabian/scratch/monetdb/stable/clients/src/mapiclient -I/ufs/fabian/scratch/monetdb/stable/program-x86_64/include/MonetDB -I/ufs/fabian/scratch/monetdb/stable/program-x86_64/include/MonetDB/common -I/ufs/fabian/scratch/monetdb/stable/program-x86_64/include/MonetDB/gdk -I.. -I/ufs/fabian/scratch/monetdb/stable/clients/src/mapiclient/.. -march=athlon64 -pipe -g -W -Wall -std=c99 -fgnu89-inline -Werror -D_FORTIFY_SOURCE=2 -D_REENTRANT -c MapiClient.c
cc1: warnings being treated as errors
/ufs/fabian/scratch/monetdb/stable/clients/src/mapiclient/MapiClient.mx: In function ‘fetch_row’:
/ufs/fabian/scratch/monetdb/stable/clients/src/mapiclient/MapiClient.mx:381: warning: implicit declaration of function ‘mapi_split_line’
/ufs/fabian/scratch/monetdb/stable/clients/src/mapiclient/MapiClient.mx: In function ‘SQLqueryEcho’:
/ufs/fabian/scratch/monetdb/stable/clients/src/mapiclient/MapiClient.mx:506: warning: implicit declaration of function ‘mapi_get_query’
/ufs/fabian/scratch/monetdb/stable/clients/src/mapiclient/MapiClient.mx:506: warning: assignment makes pointer from integer without a cast
/ufs/fabian/scratch/monetdb/stable/clients/src/mapiclient/MapiClient.mx: In function ‘doFileByLines’:
/ufs/fabian/scratch/monetdb/stable/clients/src/mapiclient/MapiClient.mx:1310: warning: implicit declaration of function ‘mapi_log’
/ufs/fabian/scratch/monetdb/stable/clients/src/mapiclient/MapiClient.mx: In function ‘main’:
/ufs/fabian/scratch/monetdb/stable/clients/src/mapiclient/MapiClient.mx:1744: error: too many arguments to function ‘mapi_stream_into’
make[5]: *** [MapiClient.o] Error 1
make[5]: Leaving directory `/net/pegasus.ins.cwi.nl/export/scratch0/fabian/vtmp/build-stable-pegasus.ins.cwi.nl/clients/src/mapiclient'
make[4]: *** [all] Error 2
make[4]: Leaving directory `/net/pegasus.ins.cwi.nl/export/scratch0/fabian/vtmp/build-stable-pegasus.ins.cwi.nl/clients/src/mapiclient'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/net/pegasus.ins.cwi.nl/export/scratch0/fabian/vtmp/build-stable-pegasus.ins.cwi.nl/clients/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/net/pegasus.ins.cwi.nl/export/scratch0/fabian/vtmp/build-stable-pegasus.ins.cwi.nl/clients/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/net/pegasus.ins.cwi.nl/export/scratch0/fabian/vtmp/build-stable-pegasus.ins.cwi.nl/clients'
make: *** [all] Error 2
Happens with both
gcc (GCC) 4.2.1 (Gentoo 4.2.1 p1.0)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
and
gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.0.1)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Looks like it /can/ find mapilib/Mapi.h, but somehow those definitions aren't used.
## Comment 8251
Date: 2007-10-08 15:20:41 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Works fine with nightly on all tested platforms, including (a.o.) Gentoo 1.12.9 with gcc (GCC) 4.2.0 (Gentoo 4.2.0) and Fedora Core 6 with gcc (GCC) 4.1.2 20070626 (Red Hat 4.1.2-13):
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/clients/.Makes3/index.html
## Comment 8252
Date: 2007-10-10 20:33:12 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
It found mapilib/Mapi.h else you got an error about this. The reason your build fails is that you have an monetdb clients compiled/installed somewhere (and these are added somehow too your include paths).
Therefor I'm closing the bug report, hope you agree.
## Comment 8253
Date: 2007-10-16 11:09:58 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
Reopening, as this is not a solution, the following (and attached) patch is:
RCS file: /cvsroot/monetdb/clients/src/mapiclient/Makefile.ag,v
retrieving revision 1.8.2.1
diff -u -r1.8.2.1 Makefile.ag
--- Makefile.ag 2 Oct 2007 11:49:05 -0000 1.8.2.1
+++ Makefile.ag 16 Oct 2007 09:07:20 -0000
@@ -15,7 +15,7 @@
All Rights Reserved.
MTSAFE
-INCLUDES = $(MONETDB_INCS) -I.. $(READLINE_INCS) $(OPENSSL_INCS)
+INCLUDES = -I.. $(MONETDB_INCS) $(READLINE_INCS) $(OPENSSL_INCS)
MAPI_LIBS = $(SOCKET_LIBS) $(OPENSSL_LIBS)
This patch simply makes sure the source provided headers are used before the already installed ones.
File Added: mapiclient-compile.patch
## Comment 8254
Date: 2007-10-16 11:25:54 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
The fix has been checked in.
## Comment 8255
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1809447 at http://sourceforge.net/support/tracker.php?aid=1809447
| clients: compilation MapiClient.mx failed | https://api.github.com/repos/MonetDB/MonetDB/issues/1458/comments | 0 | 2020-11-30T09:39:10Z | 2024-06-27T11:26:30Z | https://github.com/MonetDB/MonetDB/issues/1458 | 753,318,026 | 1,458 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-10-03 12:48:43 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2007-10-05 09:54:07 +0200
## Comment 8247
Date: 2007-10-03 12:48:43 +0200
From: @grobian
monetdb-> PREPARE select * from columns;
Exception in thread "main" java.lang.AssertionError: table_name is not fully qualified! (prepare)
Problem:
> &5 2 0 3 0
> % prepare, prepare, prepare table_name
all table names should include a schema here. If none, ".prepare" should be used to qualify it.
## Comment 8248
Date: 2007-10-05 21:54:07 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
prepare now outputs qualified names (as can be seen by the tests with prepare)
## Comment 8249
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1806869 at http://sourceforge.net/support/tracker.php?aid=1806869
| SQL: prepare output has unqualified table_name header | https://api.github.com/repos/MonetDB/MonetDB/issues/1457/comments | 0 | 2020-11-30T09:39:07Z | 2024-06-27T11:26:29Z | https://github.com/MonetDB/MonetDB/issues/1457 | 753,317,998 | 1,457 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-10-03 01:02:14 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2007-10-03 09:23:00 +0200
## Comment 8243
Date: 2007-10-03 01:02:14 +0200
From: @drstmane
When receiving en empty line on standard input --- either by hitting [Enter] on the interactive "mal>" prompt or via a redirected/piped input --- `mclient -lmal` immediately crashes with
MAPI = monetdb@localhost:50000
ACTION= read_line
QUERY =
ERROR = Connection terminated
With all other front-end languages (MIL & XQuery on M4, SQL on M4 & M5), empty lines are handled without any problems.
## Comment 8244
Date: 2007-10-03 01:25:34 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
added test in MonetDB5/tests/BugTracker/Tests/empty_line_crash.SF-1806638*
## Comment 8245
Date: 2007-10-03 09:23:00 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Fixed a problem in the MCreadClient code.
## Comment 8246
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1806638 at http://sourceforge.net/support/tracker.php?aid=1806638
| `mclient -lmal` crashes on empty line on stdin | https://api.github.com/repos/MonetDB/MonetDB/issues/1456/comments | 0 | 2020-11-30T09:39:04Z | 2024-06-27T11:26:28Z | https://github.com/MonetDB/MonetDB/issues/1456 | 753,317,955 | 1,456 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-10-02 05:55:12 +0200
From: Riham A. K. <<rihamabdelkader>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2007-10-22 10:51:48 +0200
## Comment 8233
Date: 2007-10-02 17:55:12 +0200
From: Riham A. K. <<rihamabdelkader>>
I checked out (current) today the MonetDB/XQuery code and Mserver is crashing whenever I try to execute MIL statements using the mclient command. More details follow.
I first compile an XQuery to MIL statements using the command "pf -A"
Then I execute the MIL statements with "mclient -t -l"
Whenever I do so, I get the correct results but Mserver aborts after giving the following error message:
======================================================
Mserver: monet_tbl.mx:1743: TBL_M_decref: Assertion `p' failed.
Aborted
======================================================
Moreover if I try to run the XQuery with: "mclient -lxquery", then mserver does not abort.
It, however, aborts if I use "pf -M | mclient -lmil" and returns the same error message as the one above.
I have attached the XQuery file. I could not attach the XML document (size problem).
Thank you and best regards,
Riham Abdel Kader
## Comment 8234
Date: 2007-10-02 18:06:23 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Riham,
for testing, debugging and (hopefully) fixing the bug, it would be more than handy to have (access to) the document you're using.
Could you please attach it to this report, or at least provide a link where we could find/download the document?
Thanks again!
Stefan
## Comment 8235
Date: 2007-10-02 19:08:54 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Using the latest release branches
========
$ grep . */CVS/Tag
--------
buildtools/CVS/Tag:TMonetDB_1-20
MonetDB/CVS/Tag:TMonetDB_1-20
clients/CVS/Tag:TClients_1-20
MonetDB4/CVS/Tag:TMonetDB_4-20
pathfinder/CVS/Tag:TXQuery_0-20
========
all three variants
cat /tmp/q100000_10ab_1000pr.xq | mclient -lxquery -fxml
pf -M /tmp/q100000_10ab_1000pr.xq | mclient -lmil
pf -A /tmp/q100000_10ab_1000pr.xq | mclient -lmil
work fine for me (see attached log for details).
(Will test the latest development trunk, once I have time to build it.)
Riham,
how exactly did you start your Mserver and load the document?
File Added: log
## Comment 8236
Date: 2007-10-02 19:33:58 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
For me (on my Fedora Core 6 desktop), the latest developement trunk (cvs HEAD) works just as fine with all variants.
## Comment 8237
Date: 2007-10-02 22:47:06 +0200
From: Riham A. K. <<rihamabdelkader>>
Logged In: YES
user_id=1611221
Originator: YES
Hi Stefan,
I started Mserver in the following way: Mserver --dbinit="module(mapi); mil_start(); module(pathfinder);"
I shred the XML document using the "shred_doc()" command.
Any idea?
## Comment 8238
Date: 2007-10-02 22:53:53 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Idea 1:
try (as I did; see my log) staring Mserver with
Mserver --dbinit='module(pathfinder); mil_start();'
(module pathfinder depends on module mapi, and hence loads it automatically;
loading it explicitly is hence not required, but *should* not cause any problem, either...)
Idea 2:
try (as I did; see my log) loading the document with XQuery function pf:add-doc() instead of MIL command shred_doc().
Try one idea at a time --- in fact, neither should make a difference, but you never know ...
## Comment 8239
Date: 2007-10-02 23:04:08 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
A quick test revealed that when loading module mapi *before* module pathfinder, Mserver crashes reported after the first MIL-MAPI connection, even if that's as simple as
mclient -lmil -s'print(1);'
XQuery-MAPI connections do work fine.
While this is indeed a bug that needs to be analysed --- I'll file a new bug report including a proper test later or tomorrow,
the work-around for Riham (and others ;-)) is to start the Mserver as I suggested, i.e., not loading the mapi module explicitly.
## Comment 8240
Date: 2007-10-03 10:55:04 +0200
From: Riham A. K. <<rihamabdelkader>>
Logged In: YES
user_id=1611221
Originator: YES
Stefan,
The work-around you suggested works perfectly with me. Thank you for your time.
## Comment 8241
Date: 2007-10-21 20:23:56 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Riham, if you are satisfied with the solution,
you can close the bug report
## Comment 8242
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1806421 at http://sourceforge.net/support/tracker.php?aid=1806421
| Mserver aborting after executing generated MIL | https://api.github.com/repos/MonetDB/MonetDB/issues/1455/comments | 0 | 2020-11-30T09:39:01Z | 2024-06-28T13:31:24Z | https://github.com/MonetDB/MonetDB/issues/1455 | 753,317,927 | 1,455 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-25 07:54:25 +0200
From: @grobian
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2007-09-25 08:53:02 +0200
## Comment 8230
Date: 2007-09-25 07:54:25 +0200
From: @grobian
4318 case la_project:
4319 {
4320 unsigned int i, j;
4321 PFalg_att_t old, new;
4322 /* projection has the ability to omit and change names */
/export/scratch1/monet/monet.GNU.32.32.d.29714/pathfinder/compiler/sql/lalg2sql.
brg: In function 'ser_info_worker':
/export/scratch1/monet/monet.GNU.32.32.d.29714/pathfinder/compiler/sql/lalg2sql.
brg:4320: warning: unused variable 'j'
make[5]: *** [libsql_la-lalg2sql.lo] Error 1
make[5]: Leaving directory
`/export/scratch1/monet/monet.GNU.32.32.d.29714/pathfinder/Fedora6/compiler/sql'
make[4]: *** [all] Error 2
make[4]: Leaving directory
`/export/scratch1/monet/monet.GNU.32.32.d.29714/pathfinder/Fedora6/compiler/sql'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/export/scratch1/monet/monet.GNU.32.32.d.29714/pathfinder/Fedora6/compiler'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/export/scratch1/monet/monet.GNU.32.32.d.29714/pathfinder/Fedora6/compiler'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/export/scratch1/monet/monet.GNU.32.32.d.29714/pathfinder/Fedora6'
make: *** [all] Error 2
Please note that this is the "stable" branch.
## Comment 8231
Date: 2007-09-25 08:53:02 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
Fixed.
## Comment 8232
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1801790 at http://sourceforge.net/support/tracker.php?aid=1801790
| Compiling pathfinder (Stable) failed on Fedora/CentOS | https://api.github.com/repos/MonetDB/MonetDB/issues/1454/comments | 0 | 2020-11-30T09:38:58Z | 2024-06-27T11:26:26Z | https://github.com/MonetDB/MonetDB/issues/1454 | 753,317,890 | 1,454 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-24 01:17:55 +0200
From: @sjoerdmullender
To: @sjoerdmullender
Version: -- development
Last updated: 2007-09-29 10:25:37 +0200
## Comment 8225
Date: 2007-09-24 13:17:55 +0200
From: @sjoerdmullender
make rpm in clients in the test web fails with mktemp:
+ /usr/lib/rpm/redhat/brp-java-repack-jars
cannot make temp dir /tmp/monet.GNU.32.32.d.19936.tmpdir/monetdb-1.0-mcl.jar.tmpdir.bXXEJ28396/monetdb-1.6-jdbc.jar.tmpdir.DxPBC28514: No such file or directory
error: Bad exit status from /tmp/rpm-tmp.48127 (%install)
The reason for this is a bug in the script brp-java-repack-jars. The script sets the variable TMPDIR to the output of mktemp, and then later does an rm -rf $TMPDIR. Then it uses mktemp again (if there are multiple jars in an rpm). Normally this is not a problem, but if TMPDIR is set in the environment, the assignment changes the environment variable instead of just setting a local variable. This means that the second call to mktemp sees an environment variable TMPDIR which points to a by this time non-existent directory. (It TMPDIR was not set in the environment, setting it doesn't put it into the environment, so it has no effect on subsequent calls to mktemp.)
Needless to say, the test tools set TMPDIR in the environment.
## Comment 8226
Date: 2007-09-24 18:19:41 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
A work-around (*HACK!*) would be to temporarily unset TMPDIR in the TestTools while calling `make rpm`/`rpmbuild` ...
## Comment 8227
Date: 2007-09-24 21:57:25 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: YES
Indeed.
I don't know whether that is a problem on any of our testing platforms. Compilation during the make rpm will then use /tmp (or is it /var/tmp?) which may or may not be big enough.
## Comment 8228
Date: 2007-09-29 10:25:37 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
With Sjoerd's changes to unset TMPDIR in the TestTools while building RPMs,
also the clients RPMs build fine, again.
Hence, I consider this one fixed.
## Comment 8229
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1801058 at http://sourceforge.net/support/tracker.php?aid=1801058
| make rpm in clients fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1453/comments | 0 | 2020-11-30T09:38:55Z | 2024-06-27T11:26:25Z | https://github.com/MonetDB/MonetDB/issues/1453 | 753,317,858 | 1,453 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-21 08:31:38 +0200
From: @grobian
To: @sjoerdmullender
Version: -- development
Last updated: 2007-10-04 12:33:07 +0200
## Comment 8222
Date: 2007-09-21 08:31:38 +0200
From: @grobian
1583 if (atts)
1584 for (i = 0; atts[i] != NULL; i += 2)
1585 safe_insert_oid(get_schema_node(n, (str)
atts[i], ATTRIBUTE)->bat, n->oid, (ptr) atts[i + 1]);
1586
1587 g->path = stack_push(g->path, n);
/home/monet/monet.GNU.32.32.d.17891/xml/src/Mxml/xml.mx: In function
'start_tag':
/home/monet/monet.GNU.32.32.d.17891/xml/src/Mxml/xml.mx:1585: warning: passing
argument 3 of 'safe_insert_oid' discards qualifiers from pointer target type
make[5]: *** [lib_xml_la-xml.lo] Error 1
make[5]: Leaving directory
`/home/monet/monet.GNU.32.32.d.17891/xml/Gentoo1.12.9/src/Mxml'
make[4]: *** [all] Error 2
make[4]: Leaving directory
`/home/monet/monet.GNU.32.32.d.17891/xml/Gentoo1.12.9/src/Mxml'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/home/monet/monet.GNU.32.32.d.17891/xml/Gentoo1.12.9/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/monet/monet.GNU.32.32.d.17891/xml/Gentoo1.12.9/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/home/monet/monet.GNU.32.32.d.17891/xml/Gentoo1.12.9'
make: *** [all] Error 2
grep: /home/monet/monet.GNU.32.32.d.17891/TestTools/ALL.xml: No such file or
directory
Gentoo uses a GNU GCC 4.2.0 compiler.
## Comment 8223
Date: 2007-10-04 12:33:07 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
The usage and maintenance of the XML repository has defacto been abandoned quite some time ago.
Testing of it will be stopped as of tomorrow.
Hence, this bug will not be fixed, but also not occur any longer.
Closing.
## Comment 8224
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1799448 at http://sourceforge.net/support/tracker.php?aid=1799448
| Compiling xml (Current) failed on GNU.32.32.d-Gentoo1.12.9 | https://api.github.com/repos/MonetDB/MonetDB/issues/1452/comments | 0 | 2020-11-30T09:38:53Z | 2024-06-28T13:31:24Z | https://github.com/MonetDB/MonetDB/issues/1452 | 753,317,826 | 1,452 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-21 08:29:20 +0200
From: @grobian
To: @sjoerdmullender
Version: -- development
Last updated: 2007-09-29 10:44:34 +0200
## Comment 8218
Date: 2007-09-21 08:29:20 +0200
From: @grobian
1038 char *m_clients = GDKgetenv("mapi_clients");
1039 int nr = (m_clients)?strtol(m_clients, NULL, 10):1;
1040 mapi_frontend *f =
(mapi_frontend*)GDKmalloc(sizeof(mapi_frontend));
1041 f->name = GDKstrdup("sql");
1042 f->cache_limit = nr;
/private/var/tmp/monet.GNU.32.32.d.17891/sql/src/backends/monet4/sql_session.mx:
1040: error: 'f' undeclared (first use in this function)
/private/var/tmp/monet.GNU.32.32.d.17891/sql/src/backends/monet4/sql_session.mx:
1040: error: parse error before ')' token
make[7]: *** [lib_sql_server_la-sql_session.lo] Error 1
make[6]: *** [all] Error 2
make[5]: *** [all-recursive] Error 1
make[4]: *** [all] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
grep: /private/var/tmp/monet.GNU.32.32.d.17891/TestTools/ALL.sql: No such file
or directory
Looks like the mapi_frontend struct is still not being recognised as such. (Error messages may be truncated)
## Comment 8219
Date: 2007-09-21 08:56:37 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Seems to be fixed in the latest release branch, and should hence be fixed in the development trunk once the latest changes from the release branch will be propagated.
## Comment 8220
Date: 2007-09-29 10:44:34 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
After Sjoerd's latest propagation, also the Current developmnet trunk (CVS HEAD) is fixed.
## Comment 8221
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1799445 at http://sourceforge.net/support/tracker.php?aid=1799445
| Compiling sql (Current) failed on GNU.32.32.d-Darwin8.10.0 | https://api.github.com/repos/MonetDB/MonetDB/issues/1451/comments | 0 | 2020-11-30T09:38:50Z | 2024-06-27T11:26:23Z | https://github.com/MonetDB/MonetDB/issues/1451 | 753,317,794 | 1,451 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-21 08:25:58 +0200
From: @grobian
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2007-09-21 09:28:35 +0200
## Comment 8214
Date: 2007-09-21 08:25:58 +0200
From: @grobian
792
793 if MILPRINT_SUMMER_IS_DEFAULT
794 PFstate.output_format == PFoutput_format_milprint_summer;
795 else
796 PFstate.output_format == PFoutput_format_mil;
/export/scratch1/monet/monet.GNU.32.32.d.6853/pathfinder/compiler/compile.c: In
function 'PFcompile_MonetDB':
/export/scratch1/monet/monet.GNU.32.32.d.6853/pathfinder/compiler/compile.c:794:
warning: statement with no effect
make[4]: *** [libcompiler1_la-compile.lo] Error 1
make[4]: Leaving directory
`/export/scratch1/monet/monet.GNU.32.32.d.6853/pathfinder/Fedora6/compiler'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/export/scratch1/monet/monet.GNU.32.32.d.6853/pathfinder/Fedora6/compiler'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/export/scratch1/monet/monet.GNU.32.32.d.6853/pathfinder/Fedora6/compiler'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/export/scratch1/monet/monet.GNU.32.32.d.6853/pathfinder/Fedora6'
make: *** [all] Error 2
grep: /export/scratch1/monet/monet.GNU.32.32.d.6853/TestTools/ALL.pathfinder: No
such file or directory
Looks like a '=' should be used instead of '==' here.
## Comment 8215
Date: 2007-09-21 08:55:01 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
This is JanR's bug.
## Comment 8216
Date: 2007-09-21 09:28:35 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
No reason for opening a bug report before I'm even able to fix it :-) -- Anyway the problem should be fixed now.
(The lesson learned from my side is that -Wall -Werror are switched off by default in the release branch.)
## Comment 8217
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1799440 at http://sourceforge.net/support/tracker.php?aid=1799440
| Compiling pathfinder (Stable) failed on all platforms | https://api.github.com/repos/MonetDB/MonetDB/issues/1450/comments | 0 | 2020-11-30T09:38:47Z | 2024-06-27T11:26:22Z | https://github.com/MonetDB/MonetDB/issues/1450 | 753,317,768 | 1,450 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-20 01:32:01 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2007-09-21 11:09:02 +0200
## Comment 8208
Date: 2007-09-20 13:32:01 +0200
From: Jan Rittinger <<jan.rittinger>>
In the release version I get the following error message if I try to run Mtest:
> Mtest.py
Traceback (most recent call last):
File "/local_tmp/work_stable20/MonetDB/Linux/bin/Mtest.py", line 2569, in ?
DIST,VERSION = LINUX_DIST.split(':', 1)
NameError: name 'LINUX_DIST' is not defined
It seems like the directly preceding else branch (line 2568) in Mtest.py is not evaluated. If I remove the if block and only keep the content of the else part everything works nicely.
I'm using version 1.309 of Mtest.py.in.
## Comment 8209
Date: 2007-09-20 23:08:18 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Jan,
could you please provide me with the following informtation/output:
uname -a
ls /etc/*-release
grep . /etc/*-release
Thanks!
Stefan
## Comment 8210
Date: 2007-09-21 09:18:49 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: YES
> uname -a
Linux notekemper08 2.6.16.53-0.8-default 1 Fri Aug 31 13:07:27 UTC 2007 i686 i686 i386 GNU/Linux
> ls /etc/*-release
/etc/lsb-release /etc/SuSE-release
> grep . /etc/*-release
/etc/lsb-release:LSB_VERSION="core-2.0-noarch:core-3.0-noarch:core-2.0-ia32:core-3.0-ia32"
/etc/SuSE-release:SUSE LINUX 10.1 (i586)
/etc/SuSE-release:VERSION = 10.1
## Comment 8211
Date: 2007-09-21 10:24:27 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
(hopefully) fixed in CVS (MonetDB_1-20 branch of MonetDB):
generalized Linux distribution recognition on SuSE
Jan,
could you please check and close this of in case it works for you
(and report otherwise)?
Thanks!
## Comment 8212
Date: 2007-09-21 11:09:02 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: YES
Seems to work fine again.
## Comment 8213
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1798695 at http://sourceforge.net/support/tracker.php?aid=1798695
| Mtest.py error: 'LINUX_DIST' is not defined | https://api.github.com/repos/MonetDB/MonetDB/issues/1449/comments | 0 | 2020-11-30T09:38:44Z | 2024-06-27T11:26:21Z | https://github.com/MonetDB/MonetDB/issues/1449 | 753,317,742 | 1,449 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-19 10:07:29 +0200
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2007-09-29 10:22:35 +0200
## Comment 8200
Date: 2007-09-19 10:07:29 +0200
From: @drstmane
The following tests run worse than with the previous (0.18) release:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/benchmarks_XMark_alg/q02.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/benchmarks_XMark_alg/q02.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/benchmarks_XMark_alg/q03.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/benchmarks_XMark_alg/q03.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/compiler/pf-A_XMark.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/runtime/sigs.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/runtime/procs.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/src_tools/mclient-lxquery--help.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/SCJ_with_void_void_BATs.SF-1400473.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/nested_element_construction.SF-1712578_alg.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_Update/illegal-insert.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_XQuery/attr_err2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_XQuery/attr_err2.err.00.html
(as always, see also
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/index_short.html
)
## Comment 8201
Date: 2007-09-19 14:12:17 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
In detail:
benchmarks/XMark/alg/Tests/q02,
benchmarks/XMark/alg/Tests/q03,
compiler/Tests/pf-A_XMark
fail with
"
fatal error: physical algebra equivalent for logical algebra node kind 11 not implemented, yet
"
tests/BugTracker/Tests/SCJ_with_void_void_BATs.SF-1400473
shows different OIDs;
might be OK, but needs to be checked and approved by whoever triggered this change by her/his code changes.
runtime/Tests/sigs,
runtime/Tests/procs
show new/modified procs & signatures;
might be OK, but needs to be checked and approved by whoever intensionally added/modified the respective procs and/or signatures.
tests/BugTracker/Tests/nested_element_construction.SF-1712578_alg
fails with
"
!ERROR: merged_union: BAT/column 3 of table 1 must have a dense head.
"
tests/XQuery/Tests/attr_err2
produces an empty result instead of the formerly approved error message
"
QUERY = doc("foo.xml")//@*/child::*
ERROR = !ERROR: path steps are only supported starting from non-attribute nodes
"
I just fixed (the stable output of)
tests/Update/Tests/illegal-insert
## Comment 8202
Date: 2007-09-21 09:29:39 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
benchmarks/XMark/alg/Tests/q02, benchmarks/XMark/alg/Tests/q03, and compiler/Tests/pf-A_XMark work again.
## Comment 8203
Date: 2007-09-24 18:39:18 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
This info might be of some help:
tests/XQuery/Tests/attr_err2
fails since 2007.07.28, i.e., after checkins on 2007.07.27
tests/BugTracker/Tests/nested_element_construction.SF-1712578_alg
fails since 2007.09.07, i.e., after checkins on 2007.09.06
tests/BugTracker/Tests/SCJ_with_void_void_BATs.SF-1400473
fails since 2007.09.12, i.e., after checkins on 2007.09.11
## Comment 8204
Date: 2007-09-26 11:22:23 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
I think everything is now fixed from the compiler side.
There are however 4 tests left, which mostly seem to be caused by Peters changes to the pf/runtime. (-- Peter will you have a look?)
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/runtime/sigs.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/runtime/procs.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/src_tools/mclient-lxquery--help.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/SCJ_with_void_void_BATs.SF-1400473.ou
t.00.html
## Comment 8205
Date: 2007-09-26 12:08:40 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
Hi Jan,
all these changes can be approved, but I cannot approve them right now because I do not have a compiled stable testweb run. You may have expected this answer for all proc signatured, help texts, but also holds for the @1 oids having become @2s. Actually, a week ago I already approved a couple of similar differences, but I forgot to do this one.
I think we can declare PF ready for release.
Peter
## Comment 8206
Date: 2007-09-29 10:22:35 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
All related code and/or stable output has been fixed by JanR, Sjoerd, and/or Peter.
Thanks!
## Comment 8207
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1797691 at http://sourceforge.net/support/tracker.php?aid=1797691
| PF: various tests run worse than with previous release | https://api.github.com/repos/MonetDB/MonetDB/issues/1448/comments | 0 | 2020-11-30T09:38:42Z | 2024-06-27T11:26:20Z | https://github.com/MonetDB/MonetDB/issues/1448 | 753,317,718 | 1,448 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-19 09:39:36 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2007-10-04 10:10:59 +0200
## Comment 8196
Date: 2007-09-19 09:39:36 +0200
From: @drstmane
With SQL/5, various tests run worse than with the previous (5.0+2.18) release;
see attached diff "SQL_5.0-2.18_5.2-2.20_diff" and
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql5/.mTests103/index_short.html
for details.
Also, SQL/5 appears to perform worse than the "obsolete" SQL/4;
see attached "SQL_4.20-2.20_5.2-2.20_diff" and
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/index_short.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql5/.mTests103/index_short.html
for details.
## Comment 8197
Date: 2007-09-19 09:40:30 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
File Added: SQL_4.20-2.20_5.2-2.20_diff
## Comment 8198
Date: 2007-10-04 10:10:59 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Problems have been solved by Niels.
Thanks!
## Comment 8199
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1797680 at http://sourceforge.net/support/tracker.php?aid=1797680
| SQL: various tests run worse than with previous release | https://api.github.com/repos/MonetDB/MonetDB/issues/1447/comments | 0 | 2020-11-30T09:38:40Z | 2024-06-27T11:26:19Z | https://github.com/MonetDB/MonetDB/issues/1447 | 753,317,689 | 1,447 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-19 08:27:50 +0200
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2007-10-04 10:12:41 +0200
## Comment 8189
Date: 2007-09-19 08:27:50 +0200
From: @drstmane
"Old" test
MonetDB5/tests/gdkTests/Tests/casts.*
runs worse than with the previous (5.2) release;
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.64.64.d-Fedora6/tests_gdkTests/casts.out.00.html
New test
MonetDB5/src/modules/mal/Tests/xml10.*
fails with property error;
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.64.64.d-Fedora6/src_modules_mal/xml10.out.00.html
## Comment 8190
Date: 2007-09-29 22:35:21 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
For info:
MonetDB5/tests/gdkTests/Tests/casts.*
fails since 2007.08.18, i.e., after checkins on 2007.08.17.
MonetDB5/src/modules/mal/Tests/xml10.*
fails since 2007.08.31, i.e., after checkins on 2007.08.30.
... or shall they remain unfixed in the upcoming release?
## Comment 8191
Date: 2007-10-02 18:12:33 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
To me, the differences with
MonetDB5/tests/gdkTests/Tests/casts.*
mainly look like new variable IDs in the MAL comments:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.64.64.d-Fedora6/tests_gdkTests/casts.out.00.html
Could you please check, confirm and/or approve?
MonetDB5/src/modules/mal/Tests/xml10.*
fails with
!MALException:mal.propertyCheck:Errors found
!WARNING: BATpropcheck: BAT tmp_20(-16)[xml,void] with 2 tuples was incorrectly marked sorted!
!WARNING: BATpropcheck: BAT tmp_20(-16)[xml,void] with 2 tuples remains marked radix-clustered on 32 bits; not checked!
in the MonetDB_5-2 release branch, only:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.64.64.d-Fedora6/src_modules_mal/xml10.out.00.html
while it seems to work fine in the development trunk:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.mTests103/GNU.64.64.d-Fedora6/src_modules_mal/xml10.out.00.html
In case the functionality tested in this test is not yet supported in the MonetDB_5-2 release branch,
we should consider disabling this test (in the brnach, only).
## Comment 8192
Date: 2007-10-02 18:28:56 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Yes. The search window for constant re-use was reduced.
The critial part was the [ 0 ] versus [ -0 ]
Checking against M4 showed that it is indeed correct.
The other platforms can also be approved.(I think)
## Comment 8193
Date: 2007-10-02 18:58:11 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Just for clarity:
For test MonetDB5/tests/gdkTests/Tests/casts.*,
no output has been modified and/or approved in the MonetDB_5-2 release branch, yet.
## Comment 8194
Date: 2007-10-04 10:12:41 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
===================================================================
2007/10/02 - nielsnes: src/modules/mal/Tests/All,1.44.2.1
disabled all xml* tests. They aren't about to be fixed.
SHOULD NOT BE PROPAGATED!
===================================================================
2007/10/02 - stmane: tests/gdkTests/Tests/casts.stable.out.Linux,1.3.6.1
tests/gdkTests/Tests/casts.stable.out.Linux.64bit,1.4.8.1
approved new variable IDs in MAL comments in stable output
(only for those platforms we're currently testing;
the variable IDs seem to be platform-dependend(??),
hence, I cannot "guess" their correct values on other platforms)
===================================================================
## Comment 8195
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1797649 at http://sourceforge.net/support/tracker.php?aid=1797649
| M5: 2 tests run worse than with previous release | https://api.github.com/repos/MonetDB/MonetDB/issues/1446/comments | 0 | 2020-11-30T09:38:37Z | 2024-06-27T11:26:18Z | https://github.com/MonetDB/MonetDB/issues/1446 | 753,317,652 | 1,446 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-18 10:50:41 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2007-09-24 06:27:37 +0200
## Comment 8185
Date: 2007-09-18 10:50:41 +0200
From: @drstmane
After the move of MonetDB4 specific code/tools from sql/src/tools/ to sql/src/backends/monet4 and after Sjoerd's fix of conditional-handly=ing for headers in autogen, compilation of SQL still fails on Darwin in sql/src/backends/monet4/, now with (a.o.):
nested redefinition of 'enum sql_query_t'
and
redeclaration of enumerator 'Q_PARSE'
See attached log and/or
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.GNU.32.32.d-Darwin8.10.0/make-k.out
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.GNU.32.32.d-Darwin8.10.0/make.out
for details.
## Comment 8186
Date: 2007-09-19 08:04:53 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Now (after Niels' yesterday's changes) fails with
/private/var/tmp/monet.GNU.32.32.d.26163/sql/src/backends/monet4/sql_session.mx:914: error: parse error before '*' token
See
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.GNU.32.32.d-Darwin8.10.0/make-k.out
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.GNU.32.32.d-Darwin8.10.0/make.out
sql_session.mx also includes "mapi.h"; hence, it might a again be a problem with including the wrong header file ("Mapi.h") on a case-insensitive file system ...
(increased priority, as this now is a "release-bug")
## Comment 8187
Date: 2007-09-24 18:27:37 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed by Niels by explicitly including "mapilib/Mapi.h" resp. "mapi/mapi.h" to avoid ambiguity on case-insensitive file systems.
We might want to change all includes from other than the currectly compiling package to use explicit paths relative to <prefix>/include/ to reduce the usage of / need for extended include PATHs in Makefiles ...
## Comment 8188
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1796917 at http://sourceforge.net/support/tracker.php?aid=1796917
| SQL: compilation fails on Darwin | https://api.github.com/repos/MonetDB/MonetDB/issues/1445/comments | 0 | 2020-11-30T09:38:34Z | 2024-06-27T11:26:17Z | https://github.com/MonetDB/MonetDB/issues/1445 | 753,317,611 | 1,445 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-17 04:53:37 +0200
From: @BitGrit
To: @njnes
Version: -- development
Last updated: 2007-11-19 07:12:52 +0100
## Comment 8180
Date: 2007-09-17 16:53:37 +0200
From: @BitGrit
This query came up during ADT labwork session 1.
We use the VOC dataset, 32-bit/32-bit-oid mserver 5, Mars SR2, on UvA linux machines:
uname -a
Linux ow126 2.6.12-1.1381_FC3smp 1 SMP Fri Oct 21 04:03:26 EDT 2005 i686 i686 i386 GNU/Linux
The original query hangs mserver without any resource consumption:
select count(*) from
craftsmen c,
passengers p
where c.trip = p.trip and exists
(select 1 from voyages v
where c.trip = v.trip and v.boatname = 'AMSTERDAM'
and v.departure_harbour ='Texel');
When reducing it to the below query, the server segfaults:
select count(*)
from craftsmen c,
passengers p
where c.trip = p.trip and exists (select 1) ;
without a join we get for both:
select count(*) from craftsmen c ;
select count(*) from craftsmen c where exists (select 1) ;
BOTH GIVE:
+--------+
| count_ |
+========+
| 2349 |
+--------+
1 row
## Comment 8181
Date: 2007-09-18 23:39:44 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
This bug is not confirmed on the head MonetDB/SQL
There is no segfault
## Comment 8182
Date: 2007-11-16 13:15:59 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Niels, can it be closed?
## Comment 8183
Date: 2007-11-19 19:12:52 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
added these queries to the VOC test in src/test/VOC.
Fixed in 2 parts. 1) use dynamic hash sizes for the exist part of the first query. 2) exists(select 1)
is now handled properly (old incorrect code did one join to much leading to large results)
## Comment 8184
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1796269 at http://sourceforge.net/support/tracker.php?aid=1796269
| SQL: hangs/crashes on 'exists' subqueries after a join | https://api.github.com/repos/MonetDB/MonetDB/issues/1444/comments | 0 | 2020-11-30T09:38:31Z | 2024-06-27T11:26:16Z | https://github.com/MonetDB/MonetDB/issues/1444 | 753,317,587 | 1,444 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-11 03:30:18 +0200
From: Robin Aly <<raly>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-09-05 11:32:55 +0200
## Comment 8171
Date: 2007-09-11 15:30:18 +0200
From: Robin Aly <<raly>>
The problem occured of "time wise"-joining mpeg7 documents. There are shot segments and speaker segments both having a start and a duration. Now I want to update the shot segments <mpeg7:VideoSegment> with all text data from the overlapping speaker segments. I shred with pf:add-doc(PATH, BASENAME, "trecvid2007,10). This is done for ca 130 docs. Then I execute integrate.xq (see attachment) on each of them by substituting THEDUMMY with the actual filename. For the first 10 docs this works then on 120.mp7.xml it stops: " cannot mmap(): name=20/2042, ext=buns.priv" (full error message in dump in attachment). Anybody any idea?
I also attach the config.log files from thte compilation directory.
Best,
Robin
--enable-pftijah
SuSE 10.2
autoconf-2.60-21
automake-1.9.6-35
libtool-1.5.22-34
## Comment 8172
Date: 2007-10-04 00:46:36 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Robin,
what kind of hardware are you using (CPU type, amount physical memory, amount of swap, free disk space)?
Are you using a 32-bit or 64-bit CPU/system/OS?
In case it's 64-bit are you using a 32-bit or 64-bit MonetDB/XQuery?
In case of 64-bit MonetDB/XQuery, are you using 64-bit (default) or 32-bit (--enable-oid32) OIDs?
From your error message, I see that MonetDB fails to mmap ~487 MB possibly (on a 32-bit system) because the address space is full/exhausted...
How large are the 130 documents you're using (min, max, total) and how much data do you (try to) insert (per doc and in total).
Did I get it right that you load all 130 documents before starting the inserts and the loading is successful?
Inserting (using integrate.xq) works fine for the first 10 documents, but fails for the 11th?
## Comment 8173
Date: 2007-10-05 16:24:03 +0200
From: Robin Aly <<raly>>
Logged In: YES
user_id=1423368
Originator: YES
Stefan
thanks for your answer. I configured the MonetDB + Pathfinder as follows:
MonetDB:
/local/alyr/dev/src/MonetDB-2007-09-06/configure --enable-debug --prefix=/lo
cal/alyr/dev/root/monetdb-2007-09-06
Pathfinder
/local/alyr/dev/src/pathfinder-2007-09-06/configure --enable-debug --enable-
pftijah --prefix=/local/alyr/dev/root/monetdb-2007-09-06
I have a 32 bit machine (uname -m = i686)
Here are the statistics over the data set:
I achieved the problem using another way so
I can only give you the size after the desired
insert:
min max avg s sum [bytes]
Orig Files 3965 155987 37455.2 4082618
Result Files 16361 625657 168992 17913114
Yes, It works fine for documents 1-10.
Suggestions: I discussed with Maurice, that it probably would be good
for bug tracking if everybody appends his config.logs to the report.
This way ./configure calls, library versions, architecture etc are all
visible. No critique - only a suggestion.
## Comment 8174
Date: 2007-10-05 16:58:53 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Hi Robin,
if I understand your numbers correctly, the 130 documents have a original/initial total size of about 4MB,
and after all inserts (provided they succeed) the total size should grow to about 18 MB, right.
Still open: How much physical memory and free disk space (on the partition you're using for your dbfarm and xquery_logdir) does your machine have?
In any case, I consider the amount of data rather small and would not expect the reported error.
Hence, could you provided us (via an attached or downloadable .tar.gz) with all the data (documents), queries, scripts and instructions we need to reproduce the problem?
Thanks!
Stefan
ps: attaching config.log is good, but (1) it's easier (at least for me) if I can the important info in the bug report instead of grepping through a large config.log, and (2) often, (much) more info the available in config.log is required (see above).
## Comment 8175
Date: 2007-10-05 19:05:53 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: NO
hello robin,
i am not sure whether it is completely related to this bug report, but a while ago we added 'standoff annotation' support to monetdb/xquery. you might want to have a look at it (http://repos.project.cwi.nl:8888/cwi_repository/docs/II/11/11086B.pdf), because one of the reasons to add it was the difficulty of having the query-optimizer recognize the temporal join (interval A overlaps/contains interval B).
greetings,
wouter
## Comment 8176
Date: 2007-11-19 17:54:10 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Robin,
is this one still an issue ?
If so, also with the latest MonetDB/XQuery 0.20 ?
If so, being able to reproduce the problem (using your test case) would be a prerequisite for us to analyze, locate and possibly fix the problem.
In case the reported problem does not occur any more, please close this bug report.
Thanks!
Stefan
## Comment 8177
Date: 2008-01-22 15:30:52 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Lowered priority, as we cannot reproduce it (yet?) ...
## Comment 8178
Date: 2008-09-05 11:32:55 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Closing with "out of date" as we never received the data to be able to reproduce it.
Robin,
please do not hesitate to re-open and update in case this is still a problem for you!
Stefan
## Comment 8179
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1792353 at http://sourceforge.net/support/tracker.php?aid=1792353
| XQ:Crash while updating XML | https://api.github.com/repos/MonetDB/MonetDB/issues/1443/comments | 0 | 2020-11-30T09:38:28Z | 2024-06-27T11:26:15Z | https://github.com/MonetDB/MonetDB/issues/1443 | 753,317,549 | 1,443 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-11 02:47:42 +0200
From: Maurice van Keulen <<mvankeulen>>
To: @sjoerdmullender
Version: -- development
Last updated: 2007-10-03 02:46:00 +0200
## Comment 8152
Date: 2007-09-11 14:47:42 +0200
From: Maurice van Keulen <<mvankeulen>>
When doing a fresh compile of MonetDB/XQuery, I stumbled on Java-compilation error messages (see below). I'm using Java 1.5.0_07 on Suse 10.0. I'm not sure, but I can't remember that it ever tried to compile the java-code before (my previous install was on 10 august).
make[6]: Entering directory `/local/keulen/Distrib/MonetDB.XQuery.0911/clients/src/java'
"/usr/bin/ant" -f "`echo ./build.xml`" -Dbuilddir="`echo /local/keulen/Distrib/MonetDB.XQuery/clients/src/java`" -Djardir="`echo /local/keulen/Distrib/MonetDB.XQuery/clients/src/java`" -Dbasedir="`echo .`" distall
Buildfile: ./build.xml
distall:
prepare:
[echo] Debug is true, optimise is true
compile_mcl:
[echo] Compiling MCL
jar_mcl:
prepare:
[echo] Debug is true, optimise is true
compile_mcl:
[echo] Compiling MCL
driver:
compile_jdbc:
[echo] Compiling JDBC driver
[javac] Compiling 20 source files to /local/keulen/Distrib/MonetDB.XQuery/clients/src/java
[javac] /local/keulen/Distrib/MonetDB.XQuery/clients/src/java/src/nl/cwi/monetdb/jdbc/MonetClob.java:35: duplicate class: nl.cwi.monetdb.jdbc.MonetClob
[javac] public class MonetClob implements Clob {
[javac] ^
[javac] /local/keulen/Distrib/MonetDB.XQuery/clients/src/java/src/nl/cwi/monetdb/jdbc/MonetConnection.java:57: duplicate class: nl.cwi.monetdb.jdbc.MonetConnection
[javac] public class MonetConnection implements Connection {
[javac] ^
[javac] /local/keulen/Distrib/MonetDB.XQuery/clients/src/java/src/nl/cwi/monetdb/jdbc/MonetConnection.java:2235: duplicate class: nl.cwi.monetdb.jdbc.MonetEmbeddedInstance
[javac] class MonetEmbeddedInstance extends Thread {
[javac] ^
[javac] /local/keulen/Distrib/MonetDB.XQuery/clients/src/java/src/nl/cwi/monetdb/jdbc/MonetDataSource.java:40: duplicate class: nl.cwi.monetdb.jdbc.MonetDataSource
[javac] public class MonetDataSource implements DataSource {
[javac] ^
[javac] /local/keulen/Distrib/MonetDB.XQuery/clients/src/java/src/nl/cwi/monetdb/jdbc/MonetDatabaseMetaData.java:31: duplicate class: nl.cwi.monetdb.jdbc.MonetDatabaseMetaData
[javac] public class MonetDatabaseMetaData implements DatabaseMetaData {
[javac] ^
[javac] /local/keulen/Distrib/MonetDB.XQuery/clients/src/java/src/nl/cwi/monetdb/jdbc/MonetDatabaseMetaData.java:3116: duplicate class: nl.cwi.monetdb.jdbc.MonetVirtualResultSet
[javac] class MonetVirtualResultSet extends MonetResultSet {
[javac] ^
[javac] /local/keulen/Distrib/MonetDB.XQuery/clients/src/java/src/nl/cwi/monetdb/jdbc/MonetDriver.java:45: duplicate class: nl.cwi.monetdb.jdbc.MonetDriver
[javac] final public class MonetDriver implements Driver {
[javac] ^
[javac] /local/keulen/Distrib/MonetDB.XQuery/clients/src/java/src/nl/cwi/monetdb/jdbc/MonetPreparedStatement.java:51: duplicate class: nl.cwi.monetdb.jdbc.MonetPreparedStatement
[javac] public class MonetPreparedStatement
[javac] ^
[javac] /local/keulen/Distrib/MonetDB.XQuery/clients/src/java/src/nl/cwi/monetdb/jdbc/MonetPreparedStatementJavaImpl.java:50: duplicate class: nl.cwi.monetdb.jdbc.MonetPreparedStatementJavaImpl
[javac] public class MonetPreparedStatementJavaImpl
[javac] ^
[javac] /local/keulen/Distrib/MonetDB.XQuery/clients/src/java/src/nl/cwi/monetdb/jdbc/MonetResultSet.java:49: duplicate class: nl.cwi.monetdb.jdbc.MonetResultSet
[javac] public class MonetResultSet implements ResultSet {
[javac] ^
[javac] /local/keulen/Distrib/MonetDB.XQuery/clients/src/java/src/nl/cwi/monetdb/jdbc/MonetSavepoint.java:43: duplicate class: nl.cwi.monetdb.jdbc.MonetSavepoint
[javac] public class MonetSavepoint implements Savepoint {
[javac] ^
[javac] /local/keulen/Distrib/MonetDB.XQuery/clients/src/java/src/nl/cwi/monetdb/jdbc/MonetStatement.java:48: duplicate class: nl.cwi.monetdb.jdbc.MonetStatement
[javac] public class MonetStatement implements Statement {
[javac] ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] 12 errors
BUILD FAILED
/local/keulen/Distrib/MonetDB.XQuery.0911/clients/src/java/build.xml:71: The following error occurred while executing this line:
/local/keulen/Distrib/MonetDB.XQuery.0911/clients/src/java/build.xml:166: Compile failed; see the compiler error output for details.
## Comment 8153
Date: 2007-09-11 14:50:47 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
Your problem looks like a polluted build enviroment problem to me. Can you try in a clean build environment?
## Comment 8154
Date: 2007-09-11 15:03:45 +0200
From: Maurice van Keulen <<mvankeulen>>
Logged In: YES
user_id=654674
Originator: YES
Did a fresh CVS checkout and started from scratch with compiling the modules one-by-one: same problem.
## Comment 8155
Date: 2007-09-11 15:13:31 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
did you clean-up (read: remove) all your prefixes (install destinations) and build directories, and then start building with ./bootstrap for buildtools?
## Comment 8156
Date: 2007-09-11 15:30:06 +0200
From: Maurice van Keulen <<mvankeulen>>
Logged In: YES
user_id=654674
Originator: YES
Yes, I started with an empty directory before checking out the sources again. I used the script below for this.
I tried to confirm my feeling that the installation procedure never tried to compile the java-files below. I tried to find a file MonetClob.class. There is no such file in the build-directories nor the installation-directories, so I guess this confirms my feeling. Has this JDBC-compilation been switched on somehow between 8 oct and now? Is there a way to switch it off (so that I can continue)?
set pp=(buildtools MonetDB clients MonetDB4 pathfinder)
foreach pkg ($pp)
echo " removing package" $pkg
rm -rf $pkg
end
foreach pkg ($pp)
cvs -d:ext:mvankeulen@monetdb.cvs.sourceforge.net:/cvsroot/monetdb co $pkg
end
## Comment 8157
Date: 2007-09-11 15:35:32 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
Your script only wipes the sources. Do you happen to compile in your source dirs perhaps? (This is supported.)
You can use configure --with-java=no to disable the Java files from being built.
## Comment 8158
Date: 2007-09-11 15:47:30 +0200
From: Maurice van Keulen <<mvankeulen>>
Logged In: YES
user_id=654674
Originator: YES
Yes, I compile in my source dirs (./configure --prefix=/local/keulen/Software/MonetDB --enable-probxml=yes --enable-pftijah=yes). Adding the --with-java=no works to switch of the compilation of JDBC, but of course does not solve the problem ...
## Comment 8159
Date: 2007-09-24 12:46:40 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
This actually looks like a bug in ant or the java build environment when dealing with symbolic links.
If you're compiling in a directory which is reachable through a symbolic link, and your PWD environment variable contains the path through that symbolic link, ant/javac gets confused, since it uses both that path and the path without symbolic links (the one that you see if you run /bin/pwd).
The solution: cd `/bin/pwd`; make
Please try and close the bug with a Won't Fix if this solves the problem.
## Comment 8160
Date: 2007-09-24 12:55:14 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Come to think of it, if this does indeed solve the problem, we could add a cd `/bin/pwd` in front of the call to ant in the makefiles.
## Comment 8161
Date: 2007-10-03 09:17:33 +0200
From: Maurice van Keulen <<mvankeulen>>
Logged In: YES
user_id=654674
Originator: YES
Your diagnosis is correct, but the solution doesn't work. The build fails when I compile from "/local/keulen/Distrib/MonetDB.XQuery/clients". The "MonetDB.XQuery" is a symbolic link to "MonetDB.XQuery.0911". When I "cd" to "/local/keulen/Distrib/MonetDB.XQuery.0911/clients", the build succeeds. Doing a "cd `\bin\pwd'", however, doesn't bring me from .../MonetDB.XQuery/clients to .../MonetDB.XQuery.0911/clients.
There is probably another way to "cd" to a path without any symbolic links in it. That would solve the problem.
## Comment 8162
Date: 2007-10-03 09:24:08 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Where *exactly* did you do that cd `/bin/pwd`? It should work if done correctly.
## Comment 8163
Date: 2007-10-03 09:34:22 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
What excatly does `/bin/pwd` say in your case when executed in "/local/keulen/Distrib/MonetDB.XQuery/clients",
i.e.,
cd /local/keulen/Distrib/MonetDB.XQuery/clients && /bin/pwd
?
## Comment 8164
Date: 2007-10-03 09:41:35 +0200
From: Maurice van Keulen <<mvankeulen>>
Logged In: YES
user_id=654674
Originator: YES
It says /local/keulen/Distrib/MonetDB.XQuery/clients
(so it doesn't expand the symbolic link)
## Comment 8165
Date: 2007-10-03 09:50:49 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Which OS are you using?
Sure you're explicitly using /bin/pwd, and your shell's built-in pwd?
On FC6, `info pwd` says:
========
`pwd' prints the fully resolved name of the current directory. That
is, all components of the printed name will be actual directory
names--none will be symbolic links.
^^^^^^^^^^^^^^^^^^^^^^^^^^^
Because most shells have a built-in `pwd' command, using an
unadorned `pwd' in a script or interactively may get you different
functionality than that described here.
========
## Comment 8166
Date: 2007-10-03 10:00:24 +0200
From: Maurice van Keulen <<mvankeulen>>
Logged In: YES
user_id=654674
Originator: YES
You're right. The "pwd" I was using was the shell built-in. If I use /bin/pwd, it reports the correct absolute path. Sorry for the confusion.
Perhaps you can implement your "`cd /bin/pwd` before the ant call" and close the bug.
## Comment 8167
Date: 2007-10-03 10:12:51 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
There was/is a reason why both Sjoerd and I kept on explicitly used `/bin/pwd` instead of simply `pwd` ...
We'll look into the build-process/-scripts.
## Comment 8168
Date: 2007-10-03 14:46:00 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Solved in CVS (MonetDB_1-20 brach of buildtools):
Apparently, ant gets confused with paths containing symbolic links;
hence, we use `readlink -f` (if available)
to translate paths that (potentially) contain symbolic links
into absolut physical paths without symbolic links.
Thanks to Sjoerd for analyzing the problem and suggesting the solution!
## Comment 8169
Date: 2007-10-04 12:42:09 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
Just for the record: this problem only happens when compiling *in* the source directory, which happens to be currently addressed via a symlink.
The monetdb-install.sh script works around this by using
to avoid problems with JDBC compilation, make the path we use absolute
BUILDROOT=$(cd $BUILDROOT && pwd -P)
given that this is a bash script, the result is an absolute path generated by bash's internal pwd.
## Comment 8170
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1792333 at http://sourceforge.net/support/tracker.php?aid=1792333
| Java compilation errors when compiling clients module | https://api.github.com/repos/MonetDB/MonetDB/issues/1442/comments | 0 | 2020-11-30T09:38:25Z | 2024-06-27T11:26:14Z | https://github.com/MonetDB/MonetDB/issues/1442 | 753,317,503 | 1,442 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-11 02:30:28 +0200
From: Maurice van Keulen <<mvankeulen>>
To: @sjoerdmullender
Version: -- development
Last updated: 2007-09-11 02:37:02 +0200
## Comment 8149
Date: 2007-09-11 14:30:28 +0200
From: Maurice van Keulen <<mvankeulen>>
I just tried to do a fresh full compile of MonetDB/XQuery and it stopped in module MonetDB (see below). The PYTHONPATH correctly points to __init__.py which was installed by "make install" in the buildtools module. Removing the reference to __init__,py from the Makefile allowed me to compile the MonetDB module as usual.
Message generated by "make" in the MonetDB directory:
make all-recursive
make[1]: Entering directory `/local/keulen/Distrib/MonetDB.XQuery.0911/MonetDB'
Making all in src
make[2]: Entering directory `/local/keulen/Distrib/MonetDB.XQuery.0911/MonetDB/src'
make all-recursive
make[3]: Entering directory `/local/keulen/Distrib/MonetDB.XQuery.0911/MonetDB/src'
Making all in common
make[4]: Entering directory `/local/keulen/Distrib/MonetDB.XQuery.0911/MonetDB/src/common'
make[4]: *** No rule to make target `__init__.py', needed by `all'. Stop.
make[4]: Leaving directory `/local/keulen/Distrib/MonetDB.XQuery.0911/MonetDB/src/common'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/local/keulen/Distrib/MonetDB.XQuery.0911/MonetDB/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/local/keulen/Distrib/MonetDB.XQuery.0911/MonetDB/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/local/keulen/Distrib/MonetDB.XQuery.0911/MonetDB'
make: *** [all] Error 2
## Comment 8150
Date: 2007-09-11 14:37:02 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
This was already fixed in CVS before you submitted this bugreport. :-)
## Comment 8151
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1792324 at http://sourceforge.net/support/tracker.php?aid=1792324
| MonetDB compilation error "__init__.py" | https://api.github.com/repos/MonetDB/MonetDB/issues/1441/comments | 0 | 2020-11-30T09:38:22Z | 2024-06-27T11:26:13Z | https://github.com/MonetDB/MonetDB/issues/1441 | 753,317,470 | 1,441 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-07 02:56:05 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2007-09-07 10:10:31 +0200
## Comment 8146
Date: 2007-09-07 14:56:05 +0200
From: @grobian
Making MonetDB/SQL in /ufs/fabian/scratch/vtmp/build-current-pegasus.ins.cwi.nl/sql
sql_parser.y:539.4-551.25: warning: unused value: $2
sql_parser.y:552.4-564.25: warning: unused value: $2
conflicts: 24 shift/reduce, 51 reduce/reduce
sql_parser.y:539.4-551.25: warning: unused value: $2
sql_parser.y:552.4-564.25: warning: unused value: $2
conflicts: 24 shift/reduce, 51 reduce/reduce
## Comment 8147
Date: 2007-09-07 22:10:31 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
The warnings are fixed. No test needed.
## Comment 8148
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1790101 at http://sourceforge.net/support/tracker.php?aid=1790101
| SQL: parser warnings | https://api.github.com/repos/MonetDB/MonetDB/issues/1440/comments | 0 | 2020-11-30T09:38:20Z | 2024-06-27T11:26:12Z | https://github.com/MonetDB/MonetDB/issues/1440 | 753,317,437 | 1,440 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-06 02:26:52 +0200
From: @grobian
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2007-09-11 07:01:28 +0200
## Comment 8140
Date: 2007-09-06 14:26:52 +0200
From: @grobian
gcc -DHAVE_CONFIG_H -I. -I../../.. -I. -I../atoms -I./../atoms -I../../mal -I./
../../mal -I/scratch/inst/include/MonetDB -I/scratch/inst/include/MonetDB/common
-I/scratch/inst/include/MonetDB/gdk -DLIBCOUNTERS -g -O2 -D__EXTENSIONS__ -std=
c99 -fgnu89-inline -DHWCOUNTERS -DHW_SunOS -DHW_sun4u -D_REENTRANT -c counters.c
-fPIC -DPIC -o .libs/lib_counters_la-counters.o
../../../../src/modules/kernel/counters.mx: In function 'start_count':
../../../../src/modules/kernel/counters.mx:2872: error: storage size of 'evnt' i
sn't known
../../../../src/modules/kernel/counters.mx: In function 'stop_count':
../../../../src/modules/kernel/counters.mx:3038: error: storage size of 'evnt' i
sn't known
../../../../src/modules/kernel/counters.mx: In function 'counter2bat':
../../../../src/modules/kernel/counters.mx:3111: warning: passing argument 3 of
'BUNins' discards qualifiers from pointer target type
make[7]: *** [lib_counters_la-counters.lo] Error 1
make[7]: Leaving directory `/scratch/jail/build/MonetDB5-server/MonetDB5/src/mod
ules/kernel'
This is using the nrelease (candidate) sources.
## Comment 8141
Date: 2007-09-08 12:40:28 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
To be honest, I have no idea.
I never tried to compile on Solaris/Sparc since we gave up testing on dying
and too slow apps some years ago (back then running Solaris 8) --- I have no
idea, how the counters work on Solaris 10 (on Sparc).
(I *guess* this one refers to Solaris 10 ?)
Checking the Solaris/Sparc man-pages for
libpfm (HW counters interface on Solaris/Sparc <= 7)
or
libcpc (HW counters interface on Solaris/Sparc 8, possibly also >= 9 ?)
and/or
grep-ing through /usr/include/libcpc.h and/or all system headers for "evnt"
might help ...
Stefan
## Comment 8142
Date: 2007-09-09 10:58:40 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Any step forward is helpful. Including removal of counters
module from SUN if it can not be resolved.
## Comment 8143
Date: 2007-09-09 11:09:05 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Removal of counter module for one particular platform is not required;
only the checks for counters support need to be checked/updated,
and in case we cannot find/use HW counter support for Solaris 10 on Sparc
(it used to work fine with Solaris 8 on Sparc),
we just need to fall-back to the code w/o HW counter support
(readily available in the counters module code base).
## Comment 8144
Date: 2007-09-11 19:01:28 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Fixed in CVS (development trunk of "buildtools";
refrained from checking this in to the MonetDB_1-18 stable branch,
since that one will become obsolete in a couple of days.)
The interface if the CPC library to access hardware counters on Solaris/Sparc
seems to have changes between Solaris 8 & Solaris 10.
In particular a type "cpc_event_t" that used to be provided by libcpc.h
has apparently become obsolete and removed.
Since our code (at list for the time being) only supports the old interface,
we have configure test for the exitence of type "cpc_event_t" (in addition
to the checks for header file "libcpc.h" and library "cpc", and thus
prevent compilation problems in case (only) the new interface is available.
## Comment 8145
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1789365 at http://sourceforge.net/support/tracker.php?aid=1789365
| M5: unable to compile on Solaris/Sparc | https://api.github.com/repos/MonetDB/MonetDB/issues/1439/comments | 0 | 2020-11-30T09:38:17Z | 2024-06-27T11:26:11Z | https://github.com/MonetDB/MonetDB/issues/1439 | 753,317,409 | 1,439 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-06 10:37:03 +0200
From: loicsg <<loicsg>>
To: @sjoerdmullender
Version: -- development
Last updated: 2007-09-07 12:51:20 +0200
## Comment 8137
Date: 2007-09-06 10:37:03 +0200
From: loicsg <<loicsg>>
We have problems with namespaces and the way theay are given back.
Here is the document I put in MonetDB :
<?xml version="1.0" encoding="UTF-8"?>
<documentElement xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ns2="http://model.space.com/" uri="c://myuri.htm" xsi:type="document">
</documentElement>
I get back :
<?xml version="1.0" encoding="UTF-8"?>
<documentElement xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
uri="c://myuri.htm" xsi:type="document">
</documentElement>
The namespace ns2 is never used in the document and it seems that it is removed. The problem is that we are using a JaxB parser which needs this to serialize JavaClass then.
## Comment 8138
Date: 2007-09-07 12:51:20 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Duplicate of bug [ 1588053 ] XQ: W3C_use_cases namespace tests fail: Bug or Feature?
(I admit, this would be hard to find.)
## Comment 8139
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1789206 at http://sourceforge.net/support/tracker.php?aid=1789206
This bug was marked DUPLICATE in the database it was moved from.
Changing resolution to "MOVED"
| Namespace disappearing | https://api.github.com/repos/MonetDB/MonetDB/issues/1438/comments | 0 | 2020-11-30T09:38:15Z | 2024-06-28T13:31:23Z | https://github.com/MonetDB/MonetDB/issues/1438 | 753,317,379 | 1,438 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-03 08:56:07 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2007-09-03 08:56:31 +0200
## Comment 8133
Date: 2007-09-03 08:56:07 +0200
From: @drstmane
Trying to load both "sql_server" & "pathfinder" into Mserver with either of the following commands
Mserver --dbinit='module(sql_server); module(pathfinder);'
Mserver --dbinit='module(pathfinder); module(sql_server);'
Mserver
MonetDB>module(sql_server);
MonetDB>module(pathfinder);
fails with
!ERROR: int: conversion of string '' failed
!ERROR: str_2_int: operation failed.
work-arounds (working alternatives):
Mserver
MonetDB>module(pathfinder);
MonetDB>module(sql_server);
Mserver --dbinit='{ module("pathfinder"); module("sql_server"); }'
## Comment 8134
Date: 2007-09-03 09:00:25 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
forgot:
Mserver --dbinit='{ module("sql_server"); module("pathfinder"); }'
does not work, either (i.e., pathfinder has to be loaded first).
The problem also exists in the latest CVS development version (HEAD).
## Comment 8135
Date: 2007-09-03 20:56:31 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
[ thanks go to Niels for advising me what to look for! ]
Fixed in CVS (XQuery_0-18 branch).
The load sequence of module pathfinder calls `int("")`
in PROC get_xrpc_port() in case the monetdb config file / environment
contains key "xrpc_port" with empty value "".
With the default `int(str):int` this results in int(nil),
which is handled properly.
However, once the sql_server module is loaded,
the default `int(str):int` is overloaded by a
specific one for SQL that raises an error
in case it is called with an empty string ("") argument.
Handling the empty string case separately in PROC get_xrpc_port()
helps to get both modules "sql_server" & "pathfinder"
loaded in arbitrary order.
Unfortunately, I cannot say whether there are other places in the
pathfinder code that rely in `int("")` returning int(nil)
without raising an error ...
## Comment 8136
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1786908 at http://sourceforge.net/support/tracker.php?aid=1786908
| SQL+PF: loading both "sql_server" and "pathfinder" fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1437/comments | 0 | 2020-11-30T09:38:12Z | 2024-06-27T11:26:09Z | https://github.com/MonetDB/MonetDB/issues/1437 | 753,317,362 | 1,437 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-09-01 08:40:56 +0200
From: @drstmane
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2007-09-18 09:05:23 +0200
## Comment 8128
Date: 2007-09-01 20:40:56 +0200
From: @drstmane
It seems, the SAX serialization mode of MonetDB/XQuery does not work properly (any more); at least, trying it, I get errors like
========
MAPI = monetdb@localhost:50000
QUERY = (1, 2.3, attribute attr { "val" }, 3E1, "string", doc("/tmp/nodekinds.xml")/descendant-or-self::node())
ERROR = !ERROR: xquery_print_result_loop: operation failed.
========
See the attached log for details.
In fact, I'm not sure, whether/how the SAX mode is supposed to work, who's "responsible for it, and/or whether is is still supported at all...
## Comment 8129
Date: 2007-09-06 09:06:15 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Apparently, this functionality is obsolete and no longer used and/or maintained.
JanF. volunteered to remove this functionality.
## Comment 8130
Date: 2007-09-18 09:00:23 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Jan (F.),
did you finish the SAX code removal?
If so (or once you're done), please close this bug report (including a respective comment).
Thanks in advance!
Stefan
## Comment 8131
Date: 2007-09-18 09:05:23 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Originator: NO
Finished removal of SAX funtionality. Removed SAXOPHONE serilializer completely. Left some strategic if's 'commented' just in case we want to reinstall the serializer. Did not see any problems after one week so I consider the bug closed.
## Comment 8132
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1786397 at http://sourceforge.net/support/tracker.php?aid=1786397
| XQ: SAX serialization not working properly | https://api.github.com/repos/MonetDB/MonetDB/issues/1436/comments | 0 | 2020-11-30T09:38:10Z | 2024-06-27T11:26:08Z | https://github.com/MonetDB/MonetDB/issues/1436 | 753,317,324 | 1,436 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-08-20 12:43:07 +0200
From: @grobian
To: @mlkersten
Version: -- development
Last updated: 2007-08-21 05:50:16 +0200
## Comment 8123
Date: 2007-08-20 12:43:07 +0200
From: @grobian
bin/sh ../../../libtool --tag=CC --mode=compile icc -no-gcc -fPIC -DHAVE_CONFIG_H -I. -I/scratch/monet.ntv.64.32.d.25309/MonetDB5/src/modules/mal -I../../.. -I/scratch/monet.ntv.64.32.d.25309/MonetDB5/src/modules/mal -I../atoms -I/scratch/monet.ntv.64.32.d.25309/MonetDB5/src/modules/mal/../atoms -I../kernel -I/scratch/monet.ntv.64.32.d.25309/MonetDB5/src/modules/mal/../kernel -I../../mal -I/scratch/monet.ntv.64.32.d.25309/MonetDB5/src/modules/mal/../../mal -I/scratch/monet.ntv.64.32.d.25309/MonetDB/.ntv.64.32.d-Fedora6/include/MonetDB -I/scratch/monet.ntv.64.32.d.25309/MonetDB/.ntv.64.32.d-Fedora6/include/MonetDB/common -I/scratch/monet.ntv.64.32.d.25309/MonetDB/.ntv.64.32.d-Fedora6/include/MonetDB/gdk -I/scratch/monet.ntv.64.32.d.25309/clients/.ntv.64.32.d-Fedora6/include/MonetDB -I/scratch/monet.ntv.64.32.d.25309/clients/.ntv.64.32.d-Fedora6/include/MonetDB/mapilib -DLIBMAT -we140 -wd1418 -Wall -w2 -std=c99 -mp1 -O0 -restrict -unroll -axWPT -we266 -Werror -wd1418,1419,279,981,810,193,111,1357,1572,1599 -D_REENTRANT -c -o lib_mat_la-mat.lo `test -f 'mat.c' || echo '/scratch/monet.ntv.64.32.d.25309/MonetDB5/src/modules/mal/'`mat.c
icc -no-gcc -fPIC -DHAVE_CONFIG_H -I. -I/scratch/monet.ntv.64.32.d.25309/MonetDB5/src/modules/mal -I../../.. -I/scratch/monet.ntv.64.32.d.25309/MonetDB5/src/modules/mal -I../atoms -I/scratch/monet.ntv.64.32.d.25309/MonetDB5/src/modules/mal/../atoms -I../kernel -I/scratch/monet.ntv.64.32.d.25309/MonetDB5/src/modules/mal/../kernel -I../../mal -I/scratch/monet.ntv.64.32.d.25309/MonetDB5/src/modules/mal/../../mal -I/scratch/monet.ntv.64.32.d.25309/MonetDB/.ntv.64.32.d-Fedora6/include/MonetDB -I/scratch/monet.ntv.64.32.d.25309/MonetDB/.ntv.64.32.d-Fedora6/include/MonetDB/common -I/scratch/monet.ntv.64.32.d.25309/MonetDB/.ntv.64.32.d-Fedora6/include/MonetDB/gdk -I/scratch/monet.ntv.64.32.d.25309/clients/.ntv.64.32.d-Fedora6/include/MonetDB -I/scratch/monet.ntv.64.32.d.25309/clients/.ntv.64.32.d-Fedora6/include/MonetDB/mapilib -DLIBMAT -we140 -wd1418 -Wall -w2 -std=c99 -mp1 -O0 -restrict -unroll -axWPT -we266 -Werror -wd1418,1419,279,981,810,193,111,1357,1572,1599 -D_REENTRANT -c mat.c -DPIC -o .libs/lib_mat_la-mat.o
/scratch/monet.ntv.64.32.d.25309/MonetDB5/src/modules/mal/mat.mx(138): error 593: variable "tpe" was set but never used
int i,*ret,tpe;
^
compilation aborted for mat.c (code 2)
## Comment 8124
Date: 2007-08-21 17:43:45 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
solved
## Comment 8125
Date: 2007-08-21 17:44:08 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
solved
## Comment 8126
Date: 2007-08-21 17:50:16 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Close the report. It is obsolete
## Comment 8127
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1777571 at http://sourceforge.net/support/tracker.php?aid=1777571
| compilation of onetDB5/src/modules/mal/mat.mx fails on icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1435/comments | 0 | 2020-11-30T09:38:07Z | 2024-06-27T11:26:07Z | https://github.com/MonetDB/MonetDB/issues/1435 | 753,317,295 | 1,435 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-08-16 05:35:14 +0200
From: Colin Foss <<cgfoss>>
To: @njnes
Version: -- development
Last updated: 2007-08-16 11:40:46 +0200
## Comment 8120
Date: 2007-08-16 17:35:14 +0200
From: Colin Foss <<cgfoss>>
e.g.
sql>select 11.456;
% . table_name
% single_value name
% decimal type
% 7 length
[ 11.456 ]
sql>select 11.456 || 'hi';
MAPI = monetdb@rodan:50000
ACTION= read_line
QUERY = select 11.456 || 'hi';
ERROR = Connection terminated
Here is my environment:
uname -a : Linux 2.6.9-55.ELsmp 1 SMP Wed May 2 14:04:42 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
g++ --version: 3.4.6 20060404 (Red Hat 3.4.6-8)
autoconf --version: 2.59
automake --version: 1.9.2
libtool --version: 1.5.6 (1.1220.2.95 2004/04/11 05:50:42)
last src compiled 2007/08/02 at 13:26 PDT.
## Comment 8121
Date: 2007-08-16 23:40:46 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Fixed bug in conversion too strings (missed a string type).
## Comment 8122
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1775550 at http://sourceforge.net/support/tracker.php?aid=1775550
| SQL: implied conversion from numeric to varchar disconnect | https://api.github.com/repos/MonetDB/MonetDB/issues/1434/comments | 0 | 2020-11-30T09:38:04Z | 2024-06-27T11:26:06Z | https://github.com/MonetDB/MonetDB/issues/1434 | 753,317,264 | 1,434 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-08-15 11:32:45 +0200
From: @arjenderijke
To: @sjoerdmullender
Version: -- development
Last updated: 2007-08-30 09:52:40 +0200
## Comment 8117
Date: 2007-08-15 11:32:45 +0200
From: @arjenderijke
After downloading the single page manual from "http://monetdb.cwi.nl/projects/monetdb//Assets/manual.pdf" Acrobat reader gives the following error if you open the document:
There was an error opening this document. The file is damaged and could not be repaired.
The double page manual, manual-2x1.pdf is correct.
## Comment 8118
Date: 2007-08-30 21:52:40 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Fixed during the last website upgrade
## Comment 8119
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1774575 at http://sourceforge.net/support/tracker.php?aid=1774575
| Single page manual damaged | https://api.github.com/repos/MonetDB/MonetDB/issues/1433/comments | 0 | 2020-11-30T09:38:01Z | 2024-06-27T11:26:05Z | https://github.com/MonetDB/MonetDB/issues/1433 | 753,317,230 | 1,433 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-08-14 10:28:05 +0200
From: Colin Foss <<cgfoss>>
To: @njnes
Version: -- development
Last updated: 2007-08-16 11:42:29 +0200
## Comment 8114
Date: 2007-08-14 22:28:05 +0200
From: Colin Foss <<cgfoss>>
MonetDB will throw an error on this SQL:
select tr, cast(tr as varchar(10)) from (select 11.34555 as tr) as foo;
ERROR = !TypeException:user.s7_1[13]:'sql.trunc' undefined in: _47:any := sql.trunc(_45:int, _12:int)
!TypeException:user.s7_1[14]:'bat.insert' undefined in: _48:any := bat.insert(_39:bat[:oid,:int], _44:oid, _47:any)
% .foo, . table_name
% tr, truncate_tr name
% decimal, varchar type
% 9, 0 length
Here is my environment:
uname -a : Linux 2.6.9-55.ELsmp 1 SMP Wed May 2 14:04:42 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
g++ --version: 3.4.6 20060404 (Red Hat 3.4.6-8)
autoconf --version: 2.59
automake --version: 1.9.2
libtool --version: 1.5.6 (1.1220.2.95 2004/04/11 05:50:42)
last src compiled 2007/08/02 at 13:26 PDT.
## Comment 8115
Date: 2007-08-16 23:42:29 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
fixed, the missing function isn't required anymore. Removed this from the defined functions list now.
## Comment 8116
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1774312 at http://sourceforge.net/support/tracker.php?aid=1774312
| SQL: conversion from decimal to varchar error | https://api.github.com/repos/MonetDB/MonetDB/issues/1432/comments | 0 | 2020-11-30T09:37:59Z | 2024-06-27T11:26:04Z | https://github.com/MonetDB/MonetDB/issues/1432 | 753,317,188 | 1,432 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-08-14 09:24:01 +0200
From: Colin Foss <<cgfoss>>
To: @njnes
Version: -- development
Last updated: 2007-08-16 11:43:41 +0200
## Comment 8111
Date: 2007-08-14 21:24:01 +0200
From: Colin Foss <<cgfoss>>
Using Order by on a timestampz column and using limit NNN will crash MonetDB5, SQL 2.18.
e.g.
---------------------------------------
create table t1 (
tr_time timestamp(3) with time zone
)
;
insert into t1
select *
from
(
select timestamp with time zone '2005-04-12 06:30-07:00' as tr_time
union
select timestamp with time zone '2005-04-12 07:30-07:00' as tr_time
union
select timestamp with time zone '2005-04-12 05:30-07:00' as tr_time
union
select timestamp with time zone '2005-04-12 05:35-07:00' as tr_time
union
select timestamp with time zone '2005-04-12 07:15-07:00' as tr_time
) as foo
;
-- this will crash server
select tr_time from t1
order by tr_time
limit 3
;
---------------------------------------
Here is my environment (it would be nice to have a utility to gather everything needed):
uname -a : Linux 2.6.9-55.ELsmp 1 SMP Wed May 2 14:04:42 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
g++ --version: 3.4.6 20060404 (Red Hat 3.4.6-8)
autoconf --version: 2.59
automake --version: 1.9.2
libtool --version: 1.5.6 (1.1220.2.95 2004/04/11 05:50:42)
last src compiled 2007/08/02 at 13:26 PDT.
## Comment 8112
Date: 2007-08-16 23:43:41 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Fixed in the m4/5 pqueue module. This didn't properly external types, ie > type_str.
## Comment 8113
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1774217 at http://sourceforge.net/support/tracker.php?aid=1774217
| SQL: order by timestampz column with limit crash | https://api.github.com/repos/MonetDB/MonetDB/issues/1431/comments | 0 | 2020-11-30T09:37:56Z | 2024-06-27T11:26:03Z | https://github.com/MonetDB/MonetDB/issues/1431 | 753,317,162 | 1,431 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-08-10 12:35:15 +0200
From: Maurice van Keulen <<mvankeulen>>
To: Maurice van Keulen <<mvankeulen>>
Version: -- development
Last updated: 2007-09-11 02:00:37 +0200
## Comment 8102
Date: 2007-08-10 12:35:15 +0200
From: Maurice van Keulen <<mvankeulen>>
When running big queries, i.e., queries with many lines of XQuery code (possibly due to import of modules), you sometimes run into MonetDB error messages like
ERROR = !ERROR: BATfetchjoin(tmp_5102,tmp_5122) does not hit always (|bn|=2 != 4=|l|) => can't use fetchjoin.
!ERROR: CMDleftfetchjoin: operation failed.
The problem is not in the mps generating faulty code, but in the MIL-optimizer (mil_opt.c) running out of bounds. Switching off the MIL-optimizer by changing line 697 of mil_opt.c from "* if (!(o->optimize)) {" into "if (1) {" avoids the bug.
The attached query runs into the bug. Switching off the MIL-optimizer results in it running into another bug:
ERROR = !ERROR: interpret: no matching MIL operator to 'append(BAT[oid,oid], BAT[oid,void])'.
!MAYBE YOU MEAN:
! append(BAT[any::1,BAT], any) : BAT[any::1,BAT]
! append(BAT[void,any::1], any::1, bit) : BAT[void,any::1]
! append(BAT[void,any::1], any::1) : BAT[void,any::1]
! append(BAT[oid,any::1], any::1, bit) : BAT[oid,any::1]
! append(BAT[oid,any::1], any::1) : BAT[oid,any::1]
! append(BAT[void,any::1], BAT[oid,any::1], bit) : BAT[void,any::1]
! append(BAT[void,any::1], BAT[oid,any::1]) : BAT[void,any::1]
! append(BAT[void,any::1], BAT[void,any::1], bit) : BAT[void,any::1]
! append(BAT[void,any::1], BAT[void,any::1]) : BAT[void,any::1]
! append(BAT[oid,any::1], BAT[oid,any::1], bit) : BAT[oid,any::1]
! append(BAT[oid,any::1], BAT[oid,any::1]) : BAT[oid,any::1]
Apparently, there is a missing assignment to "pos" somewhere in mps, because if I add "pos:=1@0;" to line 11641 in milprint_summer.c (function PFudfMIL), the code runs fine.
Sorry to report two bugs in one bug-report.
## Comment 8103
Date: 2007-08-10 12:44:54 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
$ pf /tmp/http://sourceforge.net/support/tracker.php?aid=12.xq
bad usage of XML namespaces: at (46,53-46,78): unknown namespace in qualified function name pxmlsup:deep-equal
halted in /ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/compiler/semantics/ns.c (ns_resolve), line 851
## Comment 8104
Date: 2007-08-10 12:48:07 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
next time, *please*
(1) use one report per bug
(2) state clearly that your are using/requiring that PF is configured with "--enable-probxml"
Would save us a lot of precious time and make us lives much easier!
aTdHvAaNnKcSe!
## Comment 8105
Date: 2007-08-10 17:29:13 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Part 2 fixed in CVS:
With MIL code optimization (mil_opt.[hc]) disabled (`pf -O0`)
not only the attached query, but also 9 more tests
tests/BugTracker/Tests/complex-XQuery-batbat_lng_add_inplace-error-OK.SF-1562868.xq
tests/BugTracker/Tests/complex-XQuery-batbat_lng_add_inplace-error-KO.SF-1562868.xq
tests/BugTracker/Tests/complex-XQuery-batbat_lng_add_inplace-error-KO2.SF-1562868.xq
tests/BugTracker/Tests/posjoin_null_BAT_2nd_run.SF-1678948.xq
tests/BugsViaSourgeforce/Tests/ID.1652527.xq
tests/W3C_use_cases/XQ/R/Tests/Q12.xq
tests/W3C_use_cases/XQ/R/Tests/Q12x.xq
tests/W3C_use_cases/XQ/STRING/Tests/Q2.xq
tests/XQuery/Tests/orderby2.xq
failed with the reported "append" error message.
The reason was (IMHO) that used-defined functions did not return the "pos";
making used-defined functions return the "pos" seems to solve the problem
without causing any other harm.
Test will follow, once I manage to create one that does not require probxml.
## Comment 8106
Date: 2007-08-10 17:40:40 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
With the fix of part 2 (initially generated MIL code was wrong),
also part 1 (potential MIL code optimizer BUG) does not seem to be reproducible any more.
Maurice, could you please check and report whether it works for you, too?
Unfortunately, we cannot (yet?) add the attached query as test to CVS,
as it requires "probxml", which is by default disabled, and can
only be enabled by a configure switch at compile-time.
## Comment 8107
Date: 2007-08-12 17:50:05 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
added test for part 2 (`pf -O0` produces wrong MIL)
in
pathfinder/tests/BugTracker/Tests/pf-O0_produces_wrong_MIL.SF-1771532.*
## Comment 8108
Date: 2007-09-09 10:57:06 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Maurice, please confirm status
## Comment 8109
Date: 2007-09-11 14:00:37 +0200
From: Maurice van Keulen <<mvankeulen>>
Logged In: YES
user_id=654674
Originator: YES
Fixes seem to have solved the bug. It runs my queries fine even when they import large modules. Sorry for waiting so long to check and close this one.
## Comment 8110
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1771532 at http://sourceforge.net/support/tracker.php?aid=1771532
| MIL-optimizer fails sometimes for big queries | https://api.github.com/repos/MonetDB/MonetDB/issues/1430/comments | 0 | 2020-11-30T09:37:53Z | 2024-06-27T11:26:02Z | https://github.com/MonetDB/MonetDB/issues/1430 | 753,317,124 | 1,430 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-08-02 11:49:39 +0200
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2007-08-03 10:19:24 +0200
## Comment 8099
Date: 2007-08-02 23:49:39 +0200
From: @drstmane
With optimization enabled src/modules/mal/bpm.mx fails to compile since Thu
Aug 2 (i.i., after checkins on Wed Aug 1) with
"
.../MonetDB5/src/modules/mal/bpm.mx(1351): error 593: variable "ps" was set but never used
Partition ps;
^
"
cf. (e.g.):
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.ntv.64.64.d-Fedora6/make.out
## Comment 8100
Date: 2007-08-03 10:19:24 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed by Martin in CVS.
Thanks!
## Comment 8101
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1766462 at http://sourceforge.net/support/tracker.php?aid=1766462
| M5: src/modules/mal/bpm.mx fails to compile w/ icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1429/comments | 0 | 2020-11-30T09:37:51Z | 2024-06-27T11:26:01Z | https://github.com/MonetDB/MonetDB/issues/1429 | 753,317,091 | 1,429 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-08-02 11:42:13 +0200
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2007-08-03 10:20:04 +0200
## Comment 8096
Date: 2007-08-02 23:42:13 +0200
From: @drstmane
With optimization enabled src/optimizer/opt_partitions.mx compile since Sat Jul 28 (i.i., after checkins on Fri Jul 27) with
"
.../MonetDB5/src/optimizer/opt_partitions.mx: In function `OPTpartitionStrategy':
.../MonetDB5/src/optimizer/opt_partitions.mx:176: warning: 'p' might be used uninitialized in this function
"
cf. (e.g.):
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.GNU.64.64.d-Fedora6/make.out
## Comment 8097
Date: 2007-08-03 10:20:04 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed by Martin (and me) in CVS.
Thanks!
## Comment 8098
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1766459 at http://sourceforge.net/support/tracker.php?aid=1766459
| M5: src/optimizer/opt_partitions.mx fails to compile w/ gcc | https://api.github.com/repos/MonetDB/MonetDB/issues/1428/comments | 0 | 2020-11-30T09:37:48Z | 2024-06-27T11:26:00Z | https://github.com/MonetDB/MonetDB/issues/1428 | 753,317,057 | 1,428 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-08-02 11:30:39 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2007-08-03 01:12:17 +0200
## Comment 8093
Date: 2007-08-02 23:30:39 +0200
From: @drstmane
Since Wed Aug 01 2007, i.e., after checkin
"
Fix serializing comments.
"
on Tue Jul 31 2007, pathfinder/runtime/serialize_dflt.mx fails to compile with icc due to:
"
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Stable/source/pathfinder/runtime/serialize_dflt.mx(219): error 593: variable "isspecial_ch" was set but never used
unsigned char isspecial_ch;
^
"
cf.:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.ntv.64.32.d-Fedora6/make-k.out
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.ntv.64.64.d-Fedora6/make-k.out
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.ntv.64.32.d-Fedora6/make-k.out
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.ntv.64.64.d-Fedora6/make-k.out
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.ntv.64.64.d-RedHat4WS/make-k.out
## Comment 8094
Date: 2007-08-03 13:12:17 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Variable is removed.
## Comment 8095
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1766455 at http://sourceforge.net/support/tracker.php?aid=1766455
| PF: runtime/serialize_dflt.mx fails to compile with icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1427/comments | 0 | 2020-11-30T09:37:45Z | 2024-06-27T11:25:59Z | https://github.com/MonetDB/MonetDB/issues/1427 | 753,317,026 | 1,427 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-08-02 09:35:18 +0200
From: @peterboncz
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2007-08-12 07:05:29 +0200
## Comment 8085
Date: 2007-08-02 21:35:18 +0200
From: @peterboncz
I have not been able to add more than two documents to a specific collection, here is the code I tried:
pf:add-doc("c://bib.xml","bib.xml","myCollection")
<>
pf:add-doc("c://book.xml","book.xml","myCollection")
<>
pf:add-doc("c://helloworld.xml","helloworld.xml","myCollection")
<>
This return always the same error : ERROR: __shred_into_docBAT:bat(old_10000000XX_qn_nid) does not exist !!!!
Am I doing something wrong?
(submitted on behalf of Loic.SAINT-GHISLAIN@mines.inpl-nancy.fr)
## Comment 8086
Date: 2007-08-02 22:42:58 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: YES
fixed in branch
added test script in tests/BugsViaSourceforge
fix in HEAD will follow soon
## Comment 8087
Date: 2007-08-02 22:47:59 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Thanks for the fix!
Does the fix in HEAD (development trunk) need more than the usual propagation that Sjoerd or I usually do?
## Comment 8088
Date: 2007-08-03 12:13:02 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
- back-ported test
tests/BugsViaSourgeforce/Tests/ID.1766414.*
from the development trunk (where it was originally added)
to the XQuery_0-18 release branch (where the bug was reported and fixed).
- fixed test
tests/BugsViaSourgeforce/Tests/ID.1766414.*
to make it actually work:
1) renamed
ID.1766414.xq
into
ID.1766414.xq.in
to be able to use/replace TSTSRCDIR variable at runtime
2) to use/replace the TSTSRCDIR environment variable, it must be called
"$TSTSRCDIR"
not
"<TSTSRCDIR>"
3) use new test-specific document names to avoid conflicts with previous tests in this directory
## Comment 8089
Date: 2007-08-03 12:14:04 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
re-opened as test still fails with
QUERY = pf:add-doc("/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Stable/source/pathfinder/tests/BugsViaSourgeforce/Tests/ID.1766414.xml","book.xml","myCollection")
ERROR = !WARNING: BATpropcheck: BAT 1000000000_attr_prop(-263)[oid,void] with 1000 tuples was incorrectly marked keyed!
further investigation pending.
## Comment 8090
Date: 2007-08-08 08:32:30 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugsViaSourgeforce/ID.1766414.err.00.html
## Comment 8091
Date: 2007-08-12 19:05:29 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Felt free to fix the property setting bug in the shredder.
## Comment 8092
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1766414 at http://sourceforge.net/support/tracker.php?aid=1766414
| XQ: third pf-add into collection fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1426/comments | 0 | 2020-11-30T09:37:43Z | 2024-06-27T11:25:59Z | https://github.com/MonetDB/MonetDB/issues/1426 | 753,316,992 | 1,426 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-08-02 05:20:29 +0200
From: Wouter Alink <<alink>>
To: @sjoerdmullender
Version: -- development
Last updated: 2008-02-11 04:00:03 +0100
## Comment 8063
Date: 2007-08-02 17:20:29 +0200
From: Wouter Alink <<alink>>
this is another try at reproducing errors i get. (using monday's nightly build containing sjoerd's fixes for first swizzle bug)
given a set of documents (they are again too large to be included as attachment at sourceforge, and i've sent them to sjoerd again) and executing a list of updates (by typing 'MapiClient -lxq < scenario.xq') will result in a (large) document. it seems to be broken though, because when doing another update:
echo 'do insert <aap/> into doc("test003.xml")/id("17990")' | MapiClient
the document is not updated (no 'aap' is inserted) :
echo 'doc("test003.xml")/id("17990")' | MapiClient
<file xend="36325078" xstart="36324973" name="MANIFEST.MF"><size>106</size><modified><date unixtime="1169823760"/></modified><compressedsize>94</compressedsize><container tool="general-purpose/magic-tool"><magic>text/plain; charset=us-ascii</magic></container></file>
## Comment 8064
Date: 2007-08-03 16:13:17 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
I've tried running your test, but after nearly two hours of thrashing I killed the Mserver so I could use my machine again.
Please, if you think this is a bug and you want to get it fixed, come up with a smaller test.
## Comment 8065
Date: 2007-09-09 11:00:04 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Wouter, please check status and update/close the report.
## Comment 8066
Date: 2007-09-25 12:01:39 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
next try... (sorry for the delay)
i could not find a smaller script with the exact same details of this bug, but this one comes close (and the result is again that the document seems to be broken and no updates can be performed afterwards).
i attached a script (+xml files) that should run within a minute with Monetdb claiming less than 500MB of memory. It produces the error message:
ERROR = !ERROR: CMDfind: value not found.
!ERROR: CMDfind: operation failed.
on the last query of the script, which tries to insert 256 elements (each with 2 child elements (total=768 element-nodes)) into the test10.xml document.
trying to insert those elements in batches of 100, 100 and 56 elements (instead of 256 at once) seems to work, but afterwards the document is corrupted. (for example: adding the first batch of 100 again, yields only 101 new element-nodes (instead of the expected 300))
(perhaps this helps to find the cause: i noticed that it is still possible to insert elements (say: '<aap/>') into nodes that occur in the beginning of the document (for example the node with xid=10))
p.s. i used the 0.18.4 Superball, compiled with 64bit, 64bit-oids, optimization enabled, on fedora core 6
File Added: test10.tar.gz
## Comment 8067
Date: 2007-09-29 14:07:59 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Wouter,
could you add your latest test to CVS?
Thanks in advance!
Stefan
## Comment 8068
Date: 2007-10-02 21:31:39 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
i filed a test under tests/BugTracker/Tests/immune_for_updates.SF-1766259.*
i did not add stable output. it currently returns:
ERROR = !ERROR: CMDfind: value not found.
!ERROR: CMDfind: operation failed.
on the last query.
## Comment 8069
Date: 2007-10-02 22:40:45 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Waiting for 4.5 minutes (optimized MonetDB/XQuery 0.20 build on 2GHz Dual-Core Athlon 64), I get quite some output (no idea, whether that's correct or not) and then (as first and only error):
QUERY = let $todo := subsequence(doc("prepared49736.data")/XIRAF/item[*], 1537,256)
let $dest := for $i in doc("test10.xml")//*[@xid]
where some $k in $todo/@xid satisfies $k = $i/@xid
return $i
for $item in $todo
return
do insert $item/*
into exactly-one($dest[@xid[. = $item/@xid]])
>
let $todo := subsequence(doc("prepared49736.data")/XIRAF/item[*], 1537,256)
let $dest := for $i in doc("test10.xml")//*[@xid]
where some $k in $todo/@xid satisfies $k = $i/@xid
ERROR = !parse error: syntax error, unexpected let $ on line 12, column 6 (next token is `let $')
!parse error: XQuery parsing failed
## Comment 8070
Date: 2007-10-02 22:41:53 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Attached the output (stdout) I get.
File Added: immune_for_updates.SF-1766259.test.out
## Comment 8071
Date: 2007-10-02 22:42:39 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Attached the output (stderr) I get.
File Added: immune_for_updates.SF-1766259.test.err
## Comment 8072
Date: 2007-10-03 08:47:03 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
see also
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/immune_for_updates.SF-1766259.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/immune_for_updates.SF-1766259.err.00.html
## Comment 8073
Date: 2007-10-03 09:57:54 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
that was the initial error i also got, but i thought i did something wrong, because when i did the following afterwards:
- stop monetdb
- delete the dbfarm (and log-folder)
- start monetdb
- rerun the test-script
it gave me the error as i reported it earlier: ERROR = !ERROR: CMDfind: value not found.
could it be a issue with mapiclient's blocksize?
## Comment 8074
Date: 2007-10-05 00:01:14 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Wouter,
can you check the output of the first n-1 queries in your test (those that do not trigger an error) and approve the output for all queries that yield correct results/output?
Simply run the test, check all output and fix incorrect output by hand, if you know the correct one,
or otherwise replace it by, say,
! Correct/expected output of query N still needs to be provided/approved !
That would help us very much with debugging!
Thanks in advance!
Stefan
## Comment 8075
Date: 2007-10-06 16:07:53 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
I added a node-counting query to the BugTracker-test to determine whether the updates succeeded.
I also added (expected) stable output.
Somehow by adding the following lines to the xq-script, the parser error is gone:
"
<>
count(doc("test10.xml")//*)
"
should this be reported in a separate bug-report?
## Comment 8076
Date: 2007-10-06 16:51:01 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Thanks.
What exactly do you mean with "the parser error is gone"?
Does no error at all occur any more, or is it now back to your originally reported "CMDfind: value not found." error?
## Comment 8077
Date: 2007-10-07 16:27:00 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
i meant that the error:
QUERY = let $todo := subsequence(doc("prepared49736.data")/XIRAF/item[*],
1537,256)
let $dest := for $i in doc("test10.xml")//*[@xid]
where some $k in $todo/@xid satisfies $k = $i/@xid
return $i
for $item in $todo
return
do insert $item/*
into exactly-one($dest[@xid[. = $item/@xid]])
>
let $todo := subsequence(doc("prepared49736.data")/XIRAF/item[*],
1537,256)
let $dest := for $i in doc("test10.xml")//*[@xid]
where some $k in $todo/@xid satisfies $k = $i/@xid
ERROR = !parse error: syntax error, unexpected let $ on line 12, column 6
(next token is `let $')
has gone. the "CMDfind: value not found." error still occurs, as you can see in the testweb output :)
## Comment 8078
Date: 2007-10-07 22:55:55 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Intensive debugging revealed that the "CMDfind: value not found." error occurs in pf_support.mx's
PROC movedata(bat[void,bat] ws, oid cont, oid from, int size, int delta): void
in line 2379:
2375: if (isoldpage) {
2376: if (rid_nid_update.exist(from_rid)) {
2377: from_nid := rid_nid_update.find(from_rid);
2378: } else {
2379: from_nid := pre_nid.find(swizzle(from_rid, map_pid_update));
2380: }
2381: } else {
2382: from_nid := rid_nid.find(from_rid);
2383: }
As far as I can tell, it looks as if the code tries to access a new page in pre_nid that has not been added, yet; here are some details in cases where the error occurs:
from = 34159@0
from_rid = 17775@0
swizzle(from_rid, map_pid_update) = 34159@0
pageno = 2@0
pageid = 1@0
isoldpage = true
|rid_nid_update| = 16289
|map_pid_update| = 3
|map_pid| = 2
|rid_nid| = 49152
|pre_nid| = 32768
Obviously, swizzle(from_rid, map_pid_update)==34159@0 does not occur in the dense head of pre_nid.
My initial idea of changing
2379: from_nid := pre_nid.find(swizzle(from_rid, map_pid_update));
into
2379: from_nid := pre_nid.find(swizzle(from_rid, map_pid));
did not help. It made the error message vanish, but some of the inserts got lost without trace.
Splitting the original failing query
let $todo := subsequence(doc("prepared49736.data")/XIRAF/item[*], 1537, 256)
...
into two consecutive complementary queries
let $todo := subsequence(doc("prepared49736.data")/XIRAF/item[*], 1537, $a)
...
<>
let $todo := subsequence(doc("prepared49736.data")/XIRAF/item[*], 1537+$a, 256-$a)
...
revealed that the reported bug only occurs with 0 <= $a <= 68 (i.e., 256 >= 256-$a >= 188) and 195 <= $a <= 256 (i.e., 61 >= 256-$a >= 0).
With that, I reached the limit of my humble update implementation expertise, and hence feel free to hand it over to the real update experts Peter & Sjoerd.
## Comment 8079
Date: 2007-12-07 15:29:23 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
The bug has been fixed.
Stefan rightly located one problem, and his tentative fix was correct, but not sufficient.
There was another place where there was a confusion between RID and PRE numbers which in this case mattered, since a new page had been inserted between the original pages 0 and 1.
## Comment 8080
Date: 2008-01-22 15:04:31 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
re-opened as the test still (again) fails, though now differently than originally reported:
ERROR = !ERROR: interpret: no matching MIL operator to 'xmltab4(BAT[oid,BAT], str, BAT[oid,str], str, BAT[oid,str], str, BAT[oid,str], str, BAT[oid,str])'.
!MAYBE YOU MEAN:
! xmltab4(BAT[void,BAT], str, BAT[void,str], str, BAT[void,str], str, BAT[void,str], str, BAT[void,str]) : BAT[void,oid]
!ERROR: interpret_params: cross(param 2): evaluation error.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/immune_for_updates.SF-1766259.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/immune_for_updates.SF-1766259.err.00.html
## Comment 8081
Date: 2008-02-10 20:39:27 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
When run in isolation, the test works fine.
Only when run after the preceding tests in the same directory the test fails as reported below.
I have not (yet?) analyzed, which (combination of) preceding tests makes this test(s) fail.
However, the attached "debugging" patch for pathfinder.mx and the respective output suggest that
(1) the call to xmltab4() in ws_collections() is the failing one, and
(2) the failure is triggered by the head of coll_upd being materialized by a "[+](BAT[VoID,str],BAT[VoID,str])" received to inputs of different length because the coll_* are (unexpectedly? / incorrectly?) not aligned.
Here, it's time for some XQuery updated expert(s) to join in / take over ...
File Added: SF-1766259.debug.patch
## Comment 8082
Date: 2008-02-10 20:40:18 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
File Added: SF-1766259.debug.output
## Comment 8083
Date: 2008-02-11 16:00:03 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
This error had nothing to do with the immune for updates problem. It occurred in the call to pf:collections() at the start of the test.
The problem was in the unoptimized multiplex code where the head column was copied to the result BAT. This was a GDK-2 bug.
No test needed.
## Comment 8084
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1766259 at http://sourceforge.net/support/tracker.php?aid=1766259
| XQ: monetdb immune for updates | https://api.github.com/repos/MonetDB/MonetDB/issues/1425/comments | 0 | 2020-11-30T09:37:39Z | 2024-06-27T11:25:58Z | https://github.com/MonetDB/MonetDB/issues/1425 | 753,316,952 | 1,425 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-08-02 04:07:20 +0200
From: Maurice van Keulen <<mvankeulen>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2007-08-08 01:15:50 +0200
## Comment 8057
Date: 2007-08-02 16:07:20 +0200
From: Maurice van Keulen <<mvankeulen>>
The query below contains a double for, each with an "at"-clause to track the position of the elements over which we iterate. We use subsequence to get the remainder of each list. The subsequence for the second list is incorrect.
declare function complete($al as xs:string*, $bl as xs:string*)
as element(list)*
{
for $a at $pa in $al
,$b at $pb in $bl
let $arest := subsequence($al,$pa+1)
,$brest := subsequence($bl,$pb+1)
return
<list>
<a pos="{$pa}">{$a}</a>
<arest>{$arest}</arest>
<b pos="{$pb}">{$b}</b>
<brest>{$brest}</brest>
</list>
};
<result>{
let $a := ("x","y")
,$b := ("p","q")
return
complete($a,$b)
}</result>
it gives
<?xml version="1.0"?>
<result>
<list>
<a pos="1">x</a>
<arest>y</arest>
<b pos="1">p</b>
<brest>p q</brest>
</list>
<list>
<a pos="1">x</a>
<arest>y</arest>
<b pos="2">q</b>
<brest>p q</brest>
</list>
<list>
<a pos="2">y</a>
<arest/>
<b pos="1">p</b>
<brest>p q</brest>
</list>
<list>
<a pos="2">y</a>
<arest/>
<b pos="2">q</b>
<brest>p q</brest>
</list>
</result>
instead of
<?xml version="1.0"?>
<result>
<list>
<a pos="1">x</a>
<arest>y</arest>
<b pos="1">p</b>
<brest>q</brest>
</list>
<list>
<a pos="1">x</a>
<arest>y</arest>
<b pos="2">q</b>
<brest/>
</list>
<list>
<a pos="2">y</a>
<arest/>
<b pos="1">p</b>
<brest>q</brest>
</list>
<list>
<a pos="2">y</a>
<arest/>
<b pos="2">q</b>
<brest/>
</list>
</result>
## Comment 8058
Date: 2007-08-03 02:31:33 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
fixed, really basic bug on computing pos inside function bodies (it only worked for the first param)
## Comment 8059
Date: 2007-08-03 12:15:01 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
back-ported test
tests/BugsViaSourgeforce/Tests/ID.1766173.*
from the development trunk (where it was originally added)
to the XQuery_0-18 release branch (where the bug was reported and fixed).
## Comment 8060
Date: 2007-08-03 12:25:48 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
re-opened:
While working fine with the XQuery_0-18 release branch, the test fail with the development head (after the fix has been propagated) with
Mserver: .../MonetDB4/src/monet/monet_interpreter.mx:1564: interpret_batcast: Assertion `tpe != 7' failed.
further investigation pending ...
## Comment 8061
Date: 2007-08-08 13:15:50 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
the assertion occured due to an apparently too strict sanity-check in interpret_batcast():
we need to allow the cast to check for under-/overflows when casting
from ftl/dbl to oid and/or from 64-bit wrd/lng to 32-bit oid.
(though I don'\''t know, why/where the eveluation of test
pathfinder tests/BugsViaSourgeforce/Tests/ID.1766173.xq
requires a cast from dbl to oid ...)
Trusting Peter's test and the correctness of the stable output he provided (didn't double-check it),
I finally closed this bug report.
## Comment 8062
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1766173 at http://sourceforge.net/support/tracker.php?aid=1766173
| Double for / position / subsequence bug | https://api.github.com/repos/MonetDB/MonetDB/issues/1424/comments | 0 | 2020-11-30T09:37:37Z | 2024-06-27T11:25:57Z | https://github.com/MonetDB/MonetDB/issues/1424 | 753,316,908 | 1,424 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-08-02 10:16:03 +0200
From: @sjoerdmullender
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2007-11-16 01:12:37 +0100
## Comment 8042
Date: 2007-08-02 10:16:03 +0200
From: @sjoerdmullender
From a message sent directly to Peter:
I ran tests with 4.18.0 version of the database on windows platform using the MonetDB4-XQuery-i686-0.18.2.msi install. I work on a bi-processor machine under Windows XP.
Problems with the JDBC interface
Opening documents
If I try to open a document (giving the doc (“documentNameâ€) instruction) which is bigger than 150ko I get an error most of the time (60%):
Incomplete block read from stream (Mserver still alive?)
I ran a code from the tutorial :
public class testMonet {
public static void main(String[] args) {
int errors = 0;
for(int k=0;k<100;k++){
System.out.println(k);
try {
Class.forName("nl.cwi.monetdb.jdbc.MonetDriver");
} catch (Exception e1) {
e1.printStackTrace();
}
try {
Connection myConnection = DriverManager.getConnection("jdbc:monetdb://localhost:50000/database?language=xquery","monetdb", "monetdb");
Statement myStatement = myConnection.createStatement();
ResultSet myResultSet = myStatement.executeQuery("doc(\"new\")");
myResultSet.next();
String buffer = myResultSet.getString(1);
myConnection.close();
System.out.println("ok");
} catch (SQLException e) {
System.out.println("error");
errors ++;
}
}
System.out.println("Errors "+errors);
}
}
I had the same problems with more complex queries returning too big results.
It seems to be a thread problem. The success rate of opening documents is even under 1% for documents which are bigger than 10megs.
## Comment 8043
Date: 2007-08-02 10:21:16 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
I would like to have a (tail of a) JDBC logfile of such "crash" occurring. You can obtain it by using the following connection creation statement:
DriverManager.getConnection("jdbc:monetdb://localhost:50000/database?language=xquery&debug=true","monetdb", "monetdb");
it will generate a monet_4987427864287323.log file located in the current working directory.
## Comment 8044
Date: 2007-08-03 10:27:29 +0200
From: loicsg <<loicsg>>
Logged In: YES
user_id=1843262
Originator: NO
Here are parts of the logfile I get using the debug mode :
RD 1186127660312: read new block: 8190 bytes
RD 1186127660312: the following incomplete block was received:
RX 1186127660312: (then I have a part of my document which is not always the same part)
## Comment 8045
Date: 2007-08-03 10:36:49 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
thanks, it looks like it gets an EOF before it can read the promised 8190 bytes, which feels like a problem on the server side of the connection to me.
A second weird thing here is that the block isn't marked as "final". Does the part of the document that is received look like a complete part? Or is it cut off?
## Comment 8046
Date: 2007-08-03 11:08:24 +0200
From: loicsg <<loicsg>>
Logged In: YES
user_id=1843262
Originator: NO
The part of the document that is received doesn't look like a complete part since it is cut in the middle of a tag.
I don't know if it can help but as I run tests, I got a MonetDB server opened and when the crash happens it sends a message :
xquery_server: client X could not flush prompt (X between 1 and 15..)
## Comment 8047
Date: 2007-08-03 11:15:07 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
Ok, I need try to reproduce this myself. Just generating a document > 150KB and using the query doc("xxx") is enough, right?
## Comment 8048
Date: 2007-08-03 11:28:54 +0200
From: loicsg <<loicsg>>
Logged In: YES
user_id=1843262
Originator: NO
Yes, even with a document with a very simple structure I have the same problem.
Here is the Java complete StackTrace if it can be any help :
java.sql.SQLException: Incomplete block read from stream (Mserver still alive?)
at nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.executeQuery(MonetConnection.java:2049)
at nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.processQuery(MonetConnection.java:1796)
at nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:371)
at nl.cwi.monetdb.jdbc.MonetStatement.execute(MonetStatement.java:340)
at nl.cwi.monetdb.jdbc.MonetStatement.executeQuery(MonetStatement.java:404)
at testMonet.main(testMonet.java:34)
## Comment 8049
Date: 2007-08-03 11:32:39 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
I just shredded a doc of 2.9MB's ($XQUERY_DIR/tests/BugTracker/Tests/predicate_selects_too_few_nodes.SF-1636588.xml) and used the query 'doc("big.xml")' in JdbcClient -lxquery with no problem.
Can you try if your document also results in a problem when using JdbcClient? If it does there too, then maybe this is a windows specific issue. I expect JdbcClient not to work for you either, since it basically does the same.
## Comment 8050
Date: 2007-08-03 11:52:03 +0200
From: loicsg <<loicsg>>
Logged In: YES
user_id=1843262
Originator: NO
It does the same with the JdbcClient.
## Comment 8051
Date: 2007-11-10 23:31:36 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Is this still an issue?
## Comment 8052
Date: 2007-11-11 01:26:10 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
this is a windows issue that I cannot debug due to the lack of access to such machine.
## Comment 8053
Date: 2007-11-16 13:09:51 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Has this been solved with your latest patch.
## Comment 8054
Date: 2007-11-16 13:12:22 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
indeed, this has been fixed in Steadfast_p13
## Comment 8055
Date: 2007-11-16 13:12:37 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
indeed, this has been fixed in Steadfast_p13
## Comment 8056
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1765919 at http://sourceforge.net/support/tracker.php?aid=1765919
| API:Incomplete block read from stream (Mserver still alive?) | https://api.github.com/repos/MonetDB/MonetDB/issues/1423/comments | 0 | 2020-11-30T09:37:34Z | 2024-06-27T11:25:56Z | https://github.com/MonetDB/MonetDB/issues/1423 | 753,316,876 | 1,423 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-07-31 10:14:04 +0200
From: @romulogoncalves
To: @mlkersten
Version: -- development
Last updated: 2007-08-30 09:54:44 +0200
## Comment 8039
Date: 2007-07-31 10:14:04 +0200
From: @romulogoncalves
Dear developers,
The partition optimizer is breaking some SQL tests, to be more specific the test:
sql/src/test/BugConstraints/delete_primarykey_1643845.sql
Regards,
Romulo
## Comment 8040
Date: 2007-08-30 21:54:10 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Partition (and mergetable) optimizers are under development
and should not be activated in the SQL optimizer.
## Comment 8041
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1764221 at http://sourceforge.net/support/tracker.php?aid=1764221
| partition optimizer breaks SQL tests... | https://api.github.com/repos/MonetDB/MonetDB/issues/1422/comments | 0 | 2020-11-30T09:37:31Z | 2024-06-28T13:31:22Z | https://github.com/MonetDB/MonetDB/issues/1422 | 753,316,837 | 1,422 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-07-30 03:17:28 +0200
From: Wouter Alink <<alink>>
To: Wouter Alink <<alink>>
Version: -- development
Last updated: 2007-10-02 09:33:20 +0200
## Comment 8031
Date: 2007-07-30 15:17:28 +0200
From: Wouter Alink <<alink>>
(using today's nightly stable build)
shredding the attached document with:
pf:add-doc("/tmp/tmpDoc3.xml","test.xml","test.xml",10)
and afterwards issuing the following two queries:
for $i in doc("test.xml")//file return do insert attribute { "nid" } { pf:nid($i) } into $i
for $i in doc("test.xml")//*[not(file)] return do insert attribute { "nid" } { pf:nid($i) } into $i
returns an error:
MAPI = monetdb@botswana.xiraf:50182
QUERY = for $i in doc("test.xml")//*[not(file)] return do insert attribute { "nid" } { pf:nid($i) } into $i
ERROR = !ERROR: merged_union: tail of first BAT must be sorted.
!ERROR: CMDmerged_union: operation failed.
!ERROR: interpret_params: reverse(param 1): evaluation error.
!ERROR: interpret_params: kdiff(param 1): evaluation error.
!ERROR: interpret_params: access(param 1): evaluation error.
!ERROR: interpret_params: insert(param 1): evaluation error.
## Comment 8032
Date: 2007-08-01 15:30:15 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
I can easily reproduce this on the current Stable.
The problem occurs in the call to merged_union in get_attr_own(). The first two input BATs need to be sorted in the tail, but aren't.
The way the code works is that the head columns of the ATTR_OWN_PRIVATE and ATTR_OWN_SHARED BATs need to be sorted (there is a .hmark(0@0) done on both), but in this case they aren't.
My question to Peter: is it a bug that those tables are not sorted in their head columns?
If not, can you fix your code in get_attr_own?
## Comment 8033
Date: 2007-08-02 21:19:12 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
fixed
now the query gives another error stating that a target node exists that already has a nid attribute.
this is correct, because the second update adds the nid attribute to all nodes that do ot have a *CHILD* of type file. Examples of such nodes are all file nodes..
Anyway, I really do appreciate the bug reports. Still a remark. From the coding patterns these reports express, I deduce some desire to add explicit 'nid' attributes to XML as IDs. I think this is very confusing and should be forbidden; each note has a native NID; it should not be present explicitly. I would only use nids as in IDREFs (ie referring to other nodes).
And of course, you are aware that as of yet, backup/restore in the admin GUI does not preserve NIDs in updatable documents..
## Comment 8034
Date: 2007-08-02 23:12:04 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
As usually, we should add a test for this one.
Unless anybody is faster, I'll try to do so tomorrow (CEST).
## Comment 8035
Date: 2007-08-03 12:21:55 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
i'll add a test for this.
peter is correct in that i meant 'not(self::file)'.
and to assure peter: the use of the query was only to be able to produce better bugreports.
## Comment 8036
Date: 2007-09-29 14:02:10 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
After almost 2 month, I finally felt free to add a test myself as monitor whether this feature (apparently required by NFI) is indeed fixed in the upcoming release and will remain fixed in the future.
See .../pathfinder/tests/BugTracker/Tests/insert_attribute_gives_ERROR_in_merged_union.SF-1763575.*
Wouter,
could you please check, whether my test makes sense (also) for you, and if so finally close this bug report?
Thanks in advance!
Stefan
## Comment 8037
Date: 2007-10-02 21:33:20 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
looks correct to me. stefan, thanks for adding the test (i had forgotten about it)
## Comment 8038
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1763575 at http://sourceforge.net/support/tracker.php?aid=1763575
| XQ: insert attribute gives ERROR in merged_union | https://api.github.com/repos/MonetDB/MonetDB/issues/1421/comments | 0 | 2020-11-30T09:37:29Z | 2024-06-27T11:25:54Z | https://github.com/MonetDB/MonetDB/issues/1421 | 753,316,808 | 1,421 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-07-30 12:44:10 +0200
From: Wouter Alink <<alink>>
To: Wouter Alink <<alink>>
Version: -- development
Last updated: 2007-08-03 04:06:25 +0200
## Comment 8014
Date: 2007-07-30 12:44:10 +0200
From: Wouter Alink <<alink>>
(today's nightly build from the stable branch, which includes sjoerd's recent fix for a similar problem)
given the attached script, the error:
!ERROR: [swizzle]: tmp_2750 contains illegal offsets
is returned.
the gzipped version of the attached script including source docs is too large for sourceforge (>256kb). i've mailed it to sjoerd.
## Comment 8015
Date: 2007-07-30 15:16:36 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
I haven't seen that promised mail...
## Comment 8016
Date: 2007-07-30 16:27:11 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
the subject reads 'swizzle 2', and you already replied to it on 12:37 local time.
## Comment 8017
Date: 2007-07-30 16:36:14 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Sorry, I hadn't seen the attachment. I've got it now.
## Comment 8018
Date: 2007-07-30 16:49:40 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Hmm, maybe the input you sent me is not correct:
The first insert query inserts a node <device name="pc01" type="unknown"/> into the document. Then the next insert query inserts into doc("wrappers.xml")/XIRAF/device[@name="pc01"] . I get an error there because the original document already contained such a node, and the first insert inserted another such node, so now there are two that match.
## Comment 8019
Date: 2007-07-31 08:21:21 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
sorry, my fault. i might have given the wrong initial document (it looks like it was the document after the updates instead of before the updates). document xiraf31973 should read:
<?xml version="1.0" encoding="utf-8"?>
<XIRAF version="TEST-VERSION" timestamp="Mon Jul 30 11:04:39 CEST 2007" revision="TEST"/>
## Comment 8020
Date: 2007-07-31 09:18:58 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
That's indeed how it starts. But after that it has a newline and
<device type="unknown" name="pc01"><image type="LocalFolder" location="/scratch/
weka-3-4-10" xstart="0" xend="31417045">
## Comment 8021
Date: 2007-07-31 17:35:27 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
The reason for the [swizzle] failing seems to be that the last document that is used in scenario.xq, xiraf32017.xml, internally known as prepared32015.data, in the very first <item> already, has nid="31351", a NID which does not occur in the wrappers.xml document.
When you use the id() function, you have to be very careful.
For now I would call this a Pilot Error.
## Comment 8022
Date: 2007-08-02 21:01:30 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
can you close this now, Wouter?
## Comment 8023
Date: 2007-08-02 21:02:59 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
can you close this now, Wouter?
## Comment 8024
Date: 2007-08-02 23:13:07 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
As usually, we should add a test for this one.
Wouter? Peter? Stefan?
## Comment 8025
Date: 2007-08-03 09:37:34 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
What do you want tested here? As far as I can see, the bug is the use of pf:nid() that refers to a NID which is not actually in the document.
I could add Wouter's test, but it is more-or-less the same as the previous swizzle bug which I fixed and which does have a test.
## Comment 8026
Date: 2007-08-03 09:48:15 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Apparently, this turned out to be a pilot error rather than a bug.
Hence, no (additional) test required.
Closing.
## Comment 8027
Date: 2007-08-03 12:13:14 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
what sjoerd concluded is correct. i made a mistake in reporting this bug. i am able to reproduce the bug, but the script that i've attached was meant to use correct nids. it was perhaps caused by not starting with an empty dbfarm.
however, i do think that the behaviour of monetdb is counter intuitive.
the query 'doc("x.xml")/id("1234567890")' gives me an empty result (not a swizzle error). in case when this is the 'into' part of an update statement, monetdb could return the in my opinion correct error: exactly-one() expected exactly one result.
## Comment 8028
Date: 2007-08-03 13:28:40 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
re-opend.
we should indeed try to either return an empty result or issue a proper error message in such cases.
## Comment 8029
Date: 2007-08-03 16:06:25 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
This bug is now fixed, a (very much simplified) test was added in pathfinder/tests/BugTracker/Tests/swizzle-http://sourceforge.net/support/tracker.php?aid=2.SF-1763495.*
## Comment 8030
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1763495 at http://sourceforge.net/support/tracker.php?aid=1763495
| XQ: illegal offsets in swizzle (2) | https://api.github.com/repos/MonetDB/MonetDB/issues/1420/comments | 0 | 2020-11-30T09:37:26Z | 2024-06-27T11:25:53Z | https://github.com/MonetDB/MonetDB/issues/1420 | 753,316,774 | 1,420 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-07-26 09:47:25 +0200
From: Wouter Alink <<alink>>
To: @sjoerdmullender
Version: -- development
Last updated: 2007-07-27 01:34:17 +0200
## Comment 8009
Date: 2007-07-26 09:47:25 +0200
From: Wouter Alink <<alink>>
Given a series of updates/add-doc queries (these can be reproduced with the attached script and documents) the following error occurs:
MAPI = monetdb@botswana.xiraf:50182
QUERY = element { "job" } {
ERROR = !ERROR: [swizzle]: tmp_53654 contains illegal offsets.
!ERROR: CMDswizzle: operation failed.
I already reduced the number of queries to reproduce the bug by a factor 3, but it might be that there are still queries in the script that do not contribute to the above error.
I used the stable nightly build (0.18) that i downloaded on Monday.
## Comment 8010
Date: 2007-07-27 13:34:17 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Fixed in CVS stable branch.
Also added a test (pathfinder/tests/BugTracker/Tests/Attic/swizzle-bug*).
## Comment 8011
Date: 2008-06-09 15:54:27 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Sjoerd's latest fix for
[ 1981852 ] PF/alg: test immune_for_updates.SF-1766259 fails
https://sourceforge.net/tracker/index.php?func=detail&aid=1981852&group_id=56967&atid=482468
also fixed a yet undetected bug triggered by the test for this bug report (swizzle-bug.SF-1760811) ---
apparently, this test has been used with incorrect stable output since it had been added...
Wouter,
Since this seems to be a fundamental fix, and both bugs involved seem to be representative for your workload,
I would not be surprised if this also fixes more (all?) of your orally reported (but never formally filed) problems
with (long-running) XQuery updates.
Please check again with the latest Stable code base (e.g., nightly build), and report on your findings.
Stefan
## Comment 8012
Date: 2008-06-09 18:35:33 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
Thanks Stefan/Sjoerd,
That would be wonderful. I was planning to do some testing tomorrow, so I will try to take the XQUF into account as well. I'll let you know about the results.
## Comment 8013
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1760811 at http://sourceforge.net/support/tracker.php?aid=1760811
| XQ: illegal offsets in swizzle | https://api.github.com/repos/MonetDB/MonetDB/issues/1419/comments | 0 | 2020-11-30T09:37:23Z | 2024-06-27T11:25:52Z | https://github.com/MonetDB/MonetDB/issues/1419 | 753,316,744 | 1,419 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-07-25 08:40:35 +0200
From: @drstmane
To: Alexander Gafriller <<gafriller>>
Version: -- development
Last updated: 2007-07-25 10:46:50 +0200
## Comment 8006
Date: 2007-07-25 20:40:35 +0200
From: @drstmane
After today's checkins, pathfinder fails to compile with
.../pathfinder/compiler/debug/prettysql.c: In function 'print_expr':
.../pathfinder/compiler/debug/prettysql.c:324: error: 'sql_in' undeclared (first use in this function)
.../pathfinder/compiler/debug/prettysql.c:324: error: (Each undeclared identifier is reported only once
.../pathfinder/compiler/debug/prettysql.c:324: error: for each function it appears in.)
.../pathfinder/compiler/debug/prettysql.c: In function 'print_lit_list':
.../pathfinder/compiler/debug/prettysql.c:896: error: 'sql_lit_list' undeclared (first use in this function)
## Comment 8007
Date: 2007-07-25 22:46:50 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Alexander's late-night checkins fix the compilation, again.
Thanks!
## Comment 8008
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1760527 at http://sourceforge.net/support/tracker.php?aid=1760527
| Pathfinder fails to compile | https://api.github.com/repos/MonetDB/MonetDB/issues/1418/comments | 0 | 2020-11-30T09:37:20Z | 2024-06-27T11:25:51Z | https://github.com/MonetDB/MonetDB/issues/1418 | 753,316,717 | 1,418 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-07-25 06:33:47 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2007-07-27 05:34:31 +0200
## Comment 8002
Date: 2007-07-25 18:33:47 +0200
From: @drstmane
Since Sat Jul 7 2007, i.e., after checkins on Fri Jul 6 2007, test attribute_value_comparison.SF-1576463.alg fails with
"
fatal error: sort criterion for rank must be monomorphic, type: 769, name: pos52
halted in /scratch/monet.GNU.64.64.d.6964/pathfinder/compiler/algebra/logical.c (PFla_rank), line 1817
"
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/attribute_value_comparison.SF-1576463.alg.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/attribute_value_comparison.SF-1576463.alg.out.00.html
## Comment 8003
Date: 2007-07-26 13:58:11 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
I checked in a fix. Let's wait for tomorrows testing to see its effect.
## Comment 8004
Date: 2007-07-27 17:34:31 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
Testweb is green again.
## Comment 8005
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1760475 at http://sourceforge.net/support/tracker.php?aid=1760475
| PF/alg: test attribute_value_comparison.SF-1576463.alg fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1417/comments | 0 | 2020-11-30T09:37:18Z | 2024-06-27T11:25:50Z | https://github.com/MonetDB/MonetDB/issues/1417 | 753,316,691 | 1,417 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-07-25 06:26:30 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2007-07-26 02:13:46 +0200
## Comment 8000
Date: 2007-07-25 18:26:30 +0200
From: @drstmane
Since Wed Jul 4 2007, i.e., after checkins on Tue Jul 03 2007, the following pathfinder "semantics" tests fail by no longer producing the error they did produce before:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/compiler_semantics_tests_ns/bad-006.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/compiler_semantics_tests_ns/bad-006.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/compiler_semantics_tests_recursion/recursion4.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/compiler_semantics_tests_recursion/recursion4.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/compiler_semantics_tests_recursion/recursion5.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/compiler_semantics_tests_recursion/recursion5.err.00.html
## Comment 8001
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1760467 at http://sourceforge.net/support/tracker.php?aid=1760467
| PF: semantics tests fail since 2007/07/04 | https://api.github.com/repos/MonetDB/MonetDB/issues/1416/comments | 0 | 2020-11-30T09:37:15Z | 2024-06-27T11:25:49Z | https://github.com/MonetDB/MonetDB/issues/1416 | 753,316,662 | 1,416 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-07-25 06:20:38 +0200
From: @drstmane
To: Manuel Mayr <<mayrm>>
Version: -- development
Last updated: 2008-02-06 11:13:59 +0100
## Comment 7989
Date: 2007-07-25 18:20:38 +0200
From: @drstmane
Since Wed Jul 11 2007, i.e., after checkins on Tue Jul 10 2007, the following pathfinder algebra tests fail:
benchmarks/MBench/Tests/qj01alg.py:
"
fatal error: attribute `item' referenced in projection not found
halted in /scratch/monet.GNU.64.64.d.6964/pathfinder/compiler/algebra/logical.c (PFla_project_), line 867
"
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/benchmarks_MBench/qj01alg.err.00.html
benchmarks/MBench/Tests/qj02alg.py:
"
fatal error: attribute `item' referenced in projection not found
halted in /scratch/monet.GNU.64.64.d.6964/pathfinder/compiler/algebra/logical.c (PFla_project_), line 867
"
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/benchmarks_MBench/qj02alg.err.00.html
benchmarks/XBench/TC/MD/Tests/q17alg.py:
"
[empty result]
"
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/benchmarks_XBench_TC_MD/q17alg.out.00.html
benchmarks/XBench/TC/SD/Tests/q02alg.py:
"
fatal error: attribute `item2' referenced in projection not found
halted in /scratch/monet.GNU.64.64.d.6964/pathfinder/compiler/algebra/logical.c (PFla_project_), line 867
"
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/benchmarks_XBench_TC_SD/q02alg.err.00.html
benchmarks/XMark/alg/Tests/upd.py,
compiler/Tests/pf-A_XMark:
"
fatal error: projection results in duplicate attribute `pos7' (attributes 2 and 1)
halted in /scratch/monet.GNU.64.64.d.6964/pathfinder/compiler/algebra/logical.c (PFla_project_), line 875
"
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/benchmarks_XMark_alg/upd.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/compiler/pf-A_XMark.err.00.html
## Comment 7990
Date: 2007-07-25 18:21:27 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
guess algebra is for JR.
## Comment 7991
Date: 2007-07-26 13:55:16 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
It is Manuels duplicate elimination optimization phase that introduces invalid rewrites.
## Comment 7992
Date: 2007-08-09 08:40:40 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Any news on this one?
## Comment 7993
Date: 2007-09-09 11:34:56 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
All reported errors seem to have disappeared, again.
Manuel,
can you confirm the fix,
and if so close the bug report with Resolution "Fixed", please?
Thanks,
Stefan
## Comment 7994
Date: 2007-09-10 11:03:07 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
Manuels checkin message (08/21/2007):
As a non-satisfying workaround for the bug bothering the testweb,
due to the common subexpression elimination, I removed this optimization
phase from pathfinder.
Please leave this the bug open, until I really fixed it.
## Comment 7995
Date: 2007-11-10 23:25:50 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
what is the status? The testweb indicates most are solved
or annotated with a proper message.
## Comment 7996
Date: 2008-01-22 15:26:32 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Any news / progress on this one?
## Comment 7997
Date: 2008-02-06 11:13:59 +0100
From: Manuel Mayr <<mayrm>>
Logged In: YES
user_id=1629542
Originator: NO
I checked in a rewritten CSE phase a few days ago and enabled it by default.
Since then there haven't been errors in the testweb caused by this phase,
so I take the liberty to close this bug ;)
## Comment 7998
Date: 2008-02-06 11:24:52 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Manuel,
unfotunately, your recent (this weeks') checkins went to the Current develoment head, not to the XQuery_0-22 Stable release branch; hence, the fixes will not be available in the upcoming release.
Please comment, whether you think these changes should also be in the release.
If so, please back-port them (using CVS commands, only; see page 14 of http://homepages.cwi.nl/~manegold/Presentations/MonetDBdevTTT.pdf for details, or feel free to ask for help!) to the XQuery_0-22 Stable release branch.
If not, please comment on whether you still consider this bug fixed also in the XQuery_0-22 Stable release branch.
Thanks!
Stefan
## Comment 7999
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1760459 at http://sourceforge.net/support/tracker.php?aid=1760459
| PF/alg: tests fails since 2007/07/11 | https://api.github.com/repos/MonetDB/MonetDB/issues/1415/comments | 0 | 2020-11-30T09:37:13Z | 2024-06-28T13:31:22Z | https://github.com/MonetDB/MonetDB/issues/1415 | 753,316,631 | 1,415 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-07-25 06:03:33 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2007-09-10 11:15:15 +0200
## Comment 7984
Date: 2007-07-25 18:03:33 +0200
From: @drstmane
Since Wed Jul 25 2007, i.e., after checkins on Tue Jul 24 2007, test pathfinder/tests/BugTracker/Tests/attribute_access_mposjoin_error.SF-1726928.xq fails, producing output in different (reverse) order than before; cf.:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/attribute_access_mposjoin_error.SF-1726928.out.00.html
## Comment 7985
Date: 2007-09-09 11:06:12 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
The test web does not show them as errors anymore.
## Comment 7986
Date: 2007-09-09 11:11:03 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
It DOES show errors for me.
## Comment 7987
Date: 2007-09-10 11:15:15 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
The specification says (http://www.w3.org/TR/xquery/; section 3.7.1.3; point 5 c): "attributes consist of all the attributes specified in the start tag as described in 3.7.1.1 Attributes, together with all the attribute nodes in the content sequence, in implementation-dependent order."
Thus the modified order is ok and I took the freedom to approve the output of the test.
## Comment 7988
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1760445 at http://sourceforge.net/support/tracker.php?aid=1760445
| PF: test attribute_access_mposjoin_error.SF-1726928 fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1414/comments | 0 | 2020-11-30T09:37:10Z | 2024-06-27T11:25:47Z | https://github.com/MonetDB/MonetDB/issues/1414 | 753,316,590 | 1,414 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-07-25 11:39:53 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2007-08-07 03:44:06 +0200
## Comment 7969
Date: 2007-07-25 11:39:53 +0200
From: Jan Rittinger <<jan.rittinger>>
If I run the following XQuery query:
declare function int-check($ylist as xs:integer*) { $ylist };
int-check(distinct-values(1 to 3))
MonetDB exits with a segfault:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1342772320 (LWP 11960)]
lngFromStr (src=0xe454dabb <Address 0xe454dabb out of bounds>, len=0xaff683fc, dst=0xaff68400) at /local_tmp/work/MonetDB/src/gdk/gdk_atoms.mx:1528
1528 while (GDKisspace(*p))
(gdb) bt
0 lngFromStr (src=0xe454dabb <Address 0xe454dabb out of bounds>, len=0xaff683fc, dst=0xaff68400) at /local_tmp/work/MonetDB/src/gdk/gdk_atoms.mx:1528
1 0xb7e182e7 in interpret_batcast (atom=0xb7c44060 "lng", argc=2, val=0xaff68684, res=0xaff6d3ac) at /local_tmp/work/MonetDB4/src/monet/monet_interpreter.mx:1684
2 0xb7e1cf3d in interpret (stk=560, lt=0x818ade0, res=0xaff6d3ac) at /local_tmp/work/MonetDB4/src/monet/monet_interpreter.mx:1188
If I run the same query with debug=10 I get the following error message:
MAPI = monetdb@localhost:50000
QUERY = declare function int-check($ylist as xs:integer*) { $ylist };
int-check(distinct-values(1 to 3))
ERROR = !ERROR: err:FORG0001: could not cast value from string to integer.
The reason is either the typing of fn:distinct-values or the implementation of distinct-values. The former provides values of type untypedAtomic* whereas the MIL implementation produces the more specific int*. The result is that the MIL implementation tries to lookup values in the wrong container.
To come back to the real bug report: Mserver shouldn't segfault!
## Comment 7970
Date: 2007-07-25 12:58:03 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
A simple initial check shows that with property checking enabled, we get a "proper" (also expected/correct??) runtime error, but no segfault:
========
$ echo '
declare function int-check($ylist as xs:integer*) { $ylist };
int-check(distinct-values(1 to 3))
' | pf | Mserver -d10 --dbinit='module(pathfinder);' --set monet_prompt=''
--------
MonetDB Server v4.19.0
based on GDK v1.19.0
Copyright (c) 1993-2007, CWI. All rights reserved.
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
MonetDB/XQuery module v0.19.0 loaded
XRPC administrative console at http://localhost:50001/admin
!ERROR: err:FORG0001: could not cast value from string to integer.
========
Without property checking, the segfautl occurs in
========
0x00002aaaac5095da in lngFromStr (src=0xdbdbdbdbdcd55e43 <Address 0xdbdbdbdbdcd55e43 out of bounds>, len=0x7fff48eadcfc, dst=0x7fff48eadd00) at /ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB/src/gdk/gdk_atoms.mx:1528
1528 while (GDKisspace(*p))
========
because
========
1 0x00002aaaabbfea47 in interpret_batcast (atom=0x2aaaac93cd20 "lng", argc=2, val=0x7fff48eae240, res=0x7fff48eb5350) at /ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB4/src/monet/monet_interpreter.mx:1684
1684 (*fromstr) (BUNtvar(b, p), &len, &v);
========
is apparently called with a corrupted BAT:
========
(gdb) print *b
$4 = {GDKversion = 25105, batCacheid = 267, dims = {headtype = 0 '\0', tailtype = 13 '\r', headloc = 0, tailloc = 0, headkey = 1 '\001', tailkey = 0 '\0', headvarsized = 1 '\001', tailvarsized = 1 '\001', bunshift = 3 '\003', bunwidth = 8, hseq = 0, tseq = 0}, batBuns = 0x112a7e0, hhash = 0x0, thash = 0x0,
H = 0x112a720, T = 0x112a770, P = 0x112a7c0, U = 0x112a7e0, void_tid = 1, void_cnt = 1, void_seq1 = 0, void_seq2 = 9223372036854775808}
(gdb) print *b.U
$5 = {buns = {maxsize = 2048, free = 24, size = 2048, base = 0x12820c8 "\b ", storage = 0 '\0', copied = 0 '\0', newstorage = 0 '\0', filename = 0x7c4328 "04/413.buns"}, deleted = 0x12820c8 "\b ", first = 0x12820c8 "\b ", inserted = 0x12820c8 "\b ", count = 3}
^^^^^^^^^
(gdb) print BATprint(BATslice(b,0,1))
^^^
-----------------
h t name
void str type
-----------------
[ 0@0, "" ]
$6 = 16843009
(gdb) print BATprint(BATslice(b,0,2))
^^^
Program received signal SIGSEGV, Segmentation fault.
0x00002aaaac50abee in strPut (h=0x631618, dst=0xf87c30, v=0xdbdbdbdbdcd55e43 <Address 0xdbdbdbdbdcd55e43 out of bounds>) at /ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB/src/gdk/gdk_atoms.mx:1993
1993 size_t i = GDK_STRLEN(v);
The program being debugged was signaled while in a function called from GDB.
GDB remains in the frame where the signal was received.
To change this behavior use "set unwindonsignal on"
Evaluation of the expression containing the function (BATslice) will be abandoned.
========
see attached LOG for more details --- further investigation is required ...
File Added: LOG
## Comment 7971
Date: 2007-07-25 17:44:13 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Provided some more info about this bug.
Please correct me if I'm wrong!
## Comment 7972
Date: 2007-07-27 13:51:19 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: YES
Added annotated MIL script (as the way to trigger the bug does not work anymore).
File Added: bug-1760168.mil
## Comment 7973
Date: 2007-08-02 10:59:33 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
If you look at the output of
echo 'declare function int-check($ylist as xs:integer*) { $ylist }; int-check(distinct-values(1 to 3))' | pf
you'll see a line
var cast_val := item.leftfetchjoin(str_values).[lng]();
It is in this [lng] cast that the crash occurs. Printing the values involved just before this line reveals some interesting info:
str_values.print();
-----------------
t h name
void str type
-----------------
[ 0@0, "" ]
item.print();
-----------------
h t name
void oid type
-----------------
[ 0@0, 0@0 ]
[ 1@0, 1@0 ]
[ 2@0, 2@0 ]
item.leftfetchjoin(str_values).print();
-----------------
h t name
void str type
-----------------
[ 0@0, "" ]
[ 1@0, "" ]
[ 2@0, "" ]
The conclusion is inescapable: the leftfetchjoin is not allowed here. The item BAT contains values in the tail which do not have a corresponding value in the str_values BAT.
By the way, I seem to get the crash consistently the *second* time I run the query. But in any case, the error happens before this bat cast.
## Comment 7974
Date: 2007-08-02 21:31:42 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
Hm, to obtain full speed on leftfetchjoin, it is AFAIK the only BAT operator where we do *not* check properly whether the outer OID is in range of the void inner bat.
Its implementation comes doen to:
for(i=0;i<n; i++) res[i] = inner[outer[i]]
Lack of checking is further exploited logically in leftfetchjoin by making
leftfetchjoin an indentity operation (zero cost, returns self) on the inner BAT, iff the outer BAT is a bat[void,void] with equal head and tail seqbase.
That is why it was not strrictly necessary to add that 0@0 tuple to the NID_RID column in ws_create... This BAT is never really filled during element construction, but is used in leftfetchjoins.. where the NID-RID (and -PRE) are identity operations, zero cost.
so leftfetchjoin should be used with a lot of care.. closing now
## Comment 7975
Date: 2007-08-02 23:10:31 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Was it intended that this bug has been closed with neither a "Resolution", nor a fix, nor a test in CVS ?
## Comment 7976
Date: 2007-08-04 10:54:48 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
updated summary
## Comment 7977
Date: 2007-08-04 10:59:11 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
this bug also exists in the XQuery_0-18 release branch
## Comment 7978
Date: 2007-08-04 11:14:05 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
added test in pathfinder/tests/BugTracker/Tests/Attic/wrong_use_of_leftfetchjoin.{,d0.}SF-1760168.*
without property checking (debugmask==0), it results in the originally reported segfault;
with property checking enabled (debugmask==10), we get:
!ERROR: BATfetchjoin(tmp_344,mapi_1_str_values) does not hit always (|bn|=1 != 3=|l|) => can't use fetchjoin.
!ERROR: CMDleftfetchjoin: operation failed.
!ERROR: interpret_params: [lng](param 1): evaluation error.
when replacing
"var cast_val := item.leftfetchjoin(%s).%s;\n",
by
"var cast_val := item.leftjoin(%s).%s;\n",
in milprint_summer.c's evaluateCast(),
we get
!ERROR: err:FORG0001: could not cast value from string to integer.
I'm not sure, whether the latter is correct/expected,
nor whether the above replacement of leftfetchjoin() by leftjoin()
in milprint_summer.c's evaluateCast() is a fix or merely curing
symptoms, i.e., whether must not be used here, or whether leftfetchjoin()
should be correct, here, but the right operand (str_values) is not correct.
Maybe JanR and/or PeterB can tell more ...
## Comment 7979
Date: 2007-08-04 11:14:48 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
re-opened as the bug still exists.
## Comment 7980
Date: 2007-08-06 14:02:07 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: YES
Backporting my last checkin to typecheck.brg (http://monetdb.cvs.sourceforge.net/monetdb/pathfinder/compiler/semantics/typecheck.brg?r1=1.60&r2=1.61) will fix the compilation.
## Comment 7981
Date: 2007-08-06 15:33:32 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Indeed, the back-port seem to help(?).
Well, two questions:
1)
I no get the following output (and no error message any more):
========
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>1 2 3</XQueryResult>
========
Is this expected/correct?
2)
Why hasn't this bug fix been checked into the Stable XQuery_0-18 release branch in the first place??
I'm getting a bit tired of spending lot of my time on back- and forth- porting various bug fixes and tests ...
Is the agreed-on procedure of "Bug fixes go to the latest release branch (only!); new features go to the development head (only!)." indeed so complex / difficult to implement ???
## Comment 7982
Date: 2007-08-07 11:45:34 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/wrong_use_of_leftfetchjoin.SF-1760168.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/wrong_use_of_leftfetchjoin.SF-1760168.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/wrong_use_of_leftfetchjoin.d0.SF-1760168.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/wrong_use_of_leftfetchjoin.d0.SF-1760168.err.00.html
## Comment 7983
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1760168 at http://sourceforge.net/support/tracker.php?aid=1760168
| PF: wrong use of leftfetchjoin causes segfault in bat_cast | https://api.github.com/repos/MonetDB/MonetDB/issues/1413/comments | 0 | 2020-11-30T09:37:06Z | 2024-06-27T11:25:46Z | https://github.com/MonetDB/MonetDB/issues/1413 | 753,316,537 | 1,413 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-07-24 11:34:05 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2007-09-06 08:28:45 +0200
## Comment 7965
Date: 2007-07-24 23:34:05 +0200
From: @drstmane
With the M5 server, tests
sql/src/test/BugDay_2005-11-09_2.9.3/Tests/hang_on_copy_into.SF-1100504.sql
and
sql/src/test/BugTracker/Tests/copy_decimal.SF-1582957.sql
fail since Sat Jul 2 2007, i.e., after checkins on Fri Jul 1 2007, producing a (slightly?) different ("less complete") error message than they did before:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql5/.mTests103/GNU.64.64.d-Fedora6/src_test_BugDay_2005-11-09_2.9.3/hang_on_copy_into.SF-1100504.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql5/.mTests103/GNU.64.64.d-Fedora6/src_test_BugTracker/copy_decimal.SF-1582957.err.00.html
## Comment 7966
Date: 2007-07-26 10:42:29 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
seems to me to be related to ascii_io/tablet changes
## Comment 7967
Date: 2007-09-06 08:28:45 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Bugs have been resolved. No further test script needed.
## Comment 7968
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1759926 at http://sourceforge.net/support/tracker.php?aid=1759926
| SQL5: tests fails since 2007/07/02 | https://api.github.com/repos/MonetDB/MonetDB/issues/1412/comments | 0 | 2020-11-30T09:37:03Z | 2024-06-27T11:25:46Z | https://github.com/MonetDB/MonetDB/issues/1412 | 753,316,504 | 1,412 |
[
"MonetDB",
"MonetDB"
] | Date: 2007-07-24 03:07:18 +0200
From: Arthur van Bunningen <<arthurvb>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-07-25 04:20:02 +0200
## Comment 7949
Date: 2007-07-24 15:07:18 +0200
From: Arthur van Bunningen <<arthurvb>>
When executing attached query (ca_module.xq) monetdb returns the following error:
==========================
8272 8273 8274 8275 8276 8277 8278 8279 8280 8281 8282 8283 8284 8285 8286 8287 8288 8289 8290 8291 8292 8293 8294 8295 8296 8297 8298 8299 8300 8301 8302 8303 8304 8305 8306 8307 8308 8309 8310 8311 8312 8313 8314 8315 8316 8317 8318 8319 8320 8321 8322 8323 8324 8325 8326 8327 8328 8329 8332 8333 8334 8335 8336 8337 8338 8339 19080 19081 19082 19083 19084 19085 19086 !ERROR: interpret: no matching MIL operator to 'leftjoin(void, BAT[oid,oid])'.
MAPI = monetdb@localhost:50000
QUERY = printf("1 ");
var tID := 9999@0; start counter at an arbitrary number
printf("2 ");
var tijah_tID := new(void,oid).seqbase(0@0);
printf("3 ");
var tijah_frag := new(void,oid).seqbase(0@0);
printf("4 ");
var tijah_pre := new(void,oid).seqbase(0@0);
printf("5 ");
var tijah_score := new(void,dbl).seqbase(0@0);
printf("6 ");
var tijah_resultsz := new(lng,lng);
printf("7 ");
var tijah_lock := lock_nil; pftijah collection lock
printf("8 ");
module("probxml");
printf("9 ");
var newid_counter := 1LL; va
ERROR = !MAYBE YOU MEAN:
! leftjoin(BAT[any::1,any::2], BAT[any::2,any::3]) : BAT[any::1,any::3]
! leftjoin(any::1, BAT[any::1,any::2]) : any::2
! leftjoin(oid, any::1) : any::1
! leftjoin(BAT[void,oid], any::1) : any::1
! leftjoin(BAT[oid,oid], any::1) : BAT[oid,any::1]
==========================
This happens in the following code:
==========================
{ expand ()
printf("8326 ");
var expOid_iter := expOid.leftfetchjoin(v_iter009);
printf("8327 ");
var iter_expOid := expOid_iter.reverse();
printf("8328 ");
var oidMap_expOid := outer010.chk_order().leftjoin(iter_expOid.chk_order());
printf("8329 ");
if (not(ordered(reverse(outer010)) and ordered(iter_expOid) and ordered(reverse(iter_expOid)))) {
printf("8330 ");
var temp_sort := oidMap_expOid.hmark(0@0).CTrefine(oidMap_expOid.tmark(0@0)).mirror();
printf("8331 ");
}
printf("8332 ");
var expOid_oidMap := oidMap_expOid.reverse();
printf("8333 ");
v_iter010 := expOid_iter;
printf("8334 ");
} end of expand ()
printf("8335 ");
join ()
printf("8336 ");
var cnt := count(v_iter010)*2;
printf("8337 ");
var new_v_iter := v_iter010;
printf("8338 ");
v_iter010 := bat(void,oid,cnt).seqbase(0@0).access(BAT_APPEND).append(new_v_iter);
printf("8339 ");
var new_v_vid := oidNew_expOid.leftjoin(v_vid009);
==========================
Further inspection learns that this is caused by the "oidNew_expOid" variable which is not initialized.
When looking at the code in mil_print_summer for expand and join I saw the initialization code is generated but seems to be optimized out by the mil_opt optimizer in compiler/mil/mil_opt.c . When running the compiler without optimizer the query runs fine.
Attachements:
ca_module.xq : the query
mil_opt.mil : the optimized code which fails (generated with extra line numbers for debugging)
mil_not_opt.mil : the non-optimized code which succeeds.
## Comment 7950
Date: 2007-07-24 15:08:58 +0200
From: Arthur van Bunningen <<arthurvb>>
Logged In: YES
user_id=1045637
Originator: YES
File Added: mil_opt.mil.gz
## Comment 7951
Date: 2007-07-24 15:09:49 +0200
From: Arthur van Bunningen <<arthurvb>>
Logged In: YES
user_id=1045637
Originator: YES
File Added: mil_not_opt.mil.gz
## Comment 7952
Date: 2007-07-24 16:48:59 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Arthur,
did you try the latest development version of after Friday Jul 20?
Sjoerd fixed a potentially related MIL optimizer bug on Friday...
Stefan
## Comment 7953
Date: 2007-07-24 19:25:14 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Arthur,
I just tried to add your attached query as a test, but it does not even successfully pass the compiler:
$ pf /tmp/ca_module.xq
bad usage of XML namespaces: at (20,5-20,57): unknown namespace in qualified function name pxmlsup:deep-equal
halted in /ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/compiler/semantics/ns.c (ns_resolve), line 851
Stefan
## Comment 7954
Date: 2007-07-24 20:29:14 +0200
From: Arthur van Bunningen <<arthurvb>>
Logged In: YES
user_id=1045637
Originator: YES
Sorry, I forgot to mention that the pathfinder module should be compiled with "--enable-probxml=yes" to run the XQuery. As can be seen from the attachments, the MIL is actually generated. The version I used I checked out last Friday, I will try again with a newer version.
## Comment 7955
Date: 2007-07-24 21:36:27 +0200
From: Arthur van Bunningen <<arthurvb>>
Logged In: YES
user_id=1045637
Originator: YES
Just checked with a fresh version (using monetdb-install.sh --nightly=current --enable-xquery), it seems that the unwanted behavior still exists.
## Comment 7956
Date: 2007-07-24 22:12:52 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Arthur,
could you also make the required documents available?
otherwise, I cannot run your test query...
Stefan
## Comment 7957
Date: 2007-07-24 22:21:01 +0200
From: Arthur van Bunningen <<arthurvb>>
Logged In: YES
user_id=1045637
Originator: YES
File Added: context_demo3.xml
## Comment 7958
Date: 2007-07-24 22:21:43 +0200
From: Arthur van Bunningen <<arthurvb>>
Logged In: YES
user_id=1045637
Originator: YES
File Added: movies.xml
## Comment 7959
Date: 2007-07-24 22:22:26 +0200
From: Arthur van Bunningen <<arthurvb>>
Logged In: YES
user_id=1045637
Originator: YES
File Added: rules.xml
## Comment 7960
Date: 2007-07-24 22:40:34 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Works for me with the latest CVS code (development trunk), at least after my compilation fix (see my latest checkin):
$ Mserver </dev/null
MonetDB Server v4.19.0
based on GDK v1.19.0
Copyright (c) 1993-2007, CWI. All rights reserved.
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
$ pf /tmp/ca_module.xq | Mserver --set monet_prompt='' --dbinit='module(pathfinder);' > /tmp/ca_module.out.O1
$ pf -O0 /tmp/ca_module.xq | Mserver --set monet_prompt='' --dbinit='module(pathfinder);' > /tmp/ca_module.out.O0
$ diff /tmp/ca_module.out.O[01]
See attached file to check the output.
File Added: ca_module.out.O1
## Comment 7961
Date: 2007-07-25 16:10:30 +0200
From: Arthur van Bunningen <<arthurvb>>
Logged In: YES
user_id=1045637
Originator: YES
Confirmed, it works here again as well.
Thank you for your help!,
Arthur
## Comment 7962
Date: 2007-07-25 17:36:30 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Problem seems to be fixed by Sjoerd's mil_opt fixes last week.
No test added (yet?) as the provided test requires probxml (configure --enable-probxml), which is not standard, yet(?).
## Comment 7963
Date: 2008-07-25 04:20:02 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
---- 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 7964
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1759552 at http://sourceforge.net/support/tracker.php?aid=1759552
| Mil optimizer bug | https://api.github.com/repos/MonetDB/MonetDB/issues/1411/comments | 0 | 2020-11-30T09:37:00Z | 2024-06-27T11:25:44Z | https://github.com/MonetDB/MonetDB/issues/1411 | 753,316,463 | 1,411 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.