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: 2008-08-26 09:22:57 +0200
From: Jane Chen <<cjnn>>
To: @njnes
Version: -- development
Last updated: 2009-08-17 02:25:04 +0200
## Comment 10174
Date: 2008-08-26 09:22:57 +0200
From: Jane Chen <<cjnn>>
OS: RedHat Linux AS 4
GCC: 3.4.6
1.setup:
create table A ( test int );
insert into A (test) values (NULL);
2.execute:
alter table A add constraint test1 primary key (test);
3.result:
The operation is successful, but the table has "null".
## Comment 10175
Date: 2008-08-26 15:52:07 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
added test alter_add_constraint_should_check_existing_data.SF-2075241.sql
. We currently don't check constraints when added to an existing column/table.
## Comment 10176
Date: 2008-11-14 14:54:32 +0100
From: @romulogoncalves
The fix for this bug were the check ins:
[Monetdb-sql-checkins] sql/src/server sql_schema.mx, Nov2008, 1.152, 1.152.2.1
[Monetdb-sql-checkins] sql/src/server sql_updates.mx, Nov2008, 1.153, 1.153.2.1
[Monetdb-sql-checkins] sql/src/storage store.mx, Nov2008, 1.22, 1.22.2.1
## Comment 10177
Date: 2009-08-13 20:03:30 +0200
From: @drstmane
re-opened as the test fails, again, since checkin on 2009/08/05 on the Aug2009 branch,
now complaining
QUERY = alter table A add constraint test1 primary key (test, id);
ERROR = !CONSTRAINT PRIMARY KEY: a table can have only one PRIMARY KEY
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker-2008/alter_add_constraint_should_check_existing_data.SF-2075241.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker-2008/alter_add_constraint_should_check_existing_data.SF-2075241.out.00.html
## Comment 10178
Date: 2009-08-14 13:53:50 +0200
From: @drstmane
tagged subject
## Comment 10179
Date: 2009-08-17 14:25:04 +0200
From: @drstmane
Niels approved the new output and error messages.
## Comment 10180
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075241 at http://sourceforge.net/support/tracker.php?aid=2075241
| SQL: When NULL is in a column,it shouldn't add primary key | https://api.github.com/repos/MonetDB/MonetDB/issues/1810/comments | 0 | 2020-11-30T10:01:51Z | 2024-06-27T11:32:20Z | https://github.com/MonetDB/MonetDB/issues/1810 | 753,334,725 | 1,810 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 09:12:47 +0200
From: Jane Chen <<cjnn>>
To: @njnes
Version: -- development
Last updated: 2008-09-09 02:54:11 +0200
## Comment 10170
Date: 2008-08-26 09:12:47 +0200
From: Jane Chen <<cjnn>>
OS: RedHat Linux AS 4
GCC: 3.4.6
1.setup:
CREATE TABLE A (a CHAR (10));
CREATE VIEW A_VIEW AS
SELECT CAST (a AS NUMERIC (5, 2)) AS b
FROM A;
INSERT INTO A VALUES (' 54.');
2.execute:
select * from A_VIEW;
3.result:
!SQLException:int:decimal ( 54.) doesn't have format (5.2)
## Comment 10171
Date: 2008-08-26 15:27:33 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
added test decimal_cast_in_view.SF-2075223.sql
## Comment 10172
Date: 2008-09-09 14:54:11 +0200
From: @njnes
dynamic coersion bug fixed.
## Comment 10173
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075223 at http://sourceforge.net/support/tracker.php?aid=2075223
| The view with CAST is seems to be something the matter | https://api.github.com/repos/MonetDB/MonetDB/issues/1809/comments | 0 | 2020-11-30T10:01:48Z | 2024-06-27T11:32:19Z | https://github.com/MonetDB/MonetDB/issues/1809 | 753,334,686 | 1,809 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 09:10:58 +0200
From: Jane Chen <<cjnn>>
To: @njnes
Version: -- development
CC: @sjoerdmullender
Duplicates: #1806
Last updated: 2010-07-09 15:12:41 +0200
## Comment 10167
Date: 2008-08-26 09:10:58 +0200
From: Jane Chen <<cjnn>>
OS: RedHat Linux AS 4
GCC: 3.4.6
1.setup:
create table A (a varchar(10));
create view myview
as select * from A;
2.execute:
alter table myview alter column a set null;
3.result:
The operation is OK
4.question:
The View shouldn't alter.
## Comment 10168
Date: 2008-08-26 09:18:27 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Duplicate;
already reported as
[ 2075195 ] The View shouldn't alter.
http://sourceforge.net/tracker/index.php?func=detail&aid=2075195&group_id=56967&atid=482468
## Comment 10169
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075216 at http://sourceforge.net/support/tracker.php?aid=2075216
Bug has invalid status, setting status to "NEW".
Previous status was "DELETED".
## Comment 14328
Date: 2010-07-09 15:12:41 +0200
From: @sjoerdmullender
*** This bug has been marked as a duplicate of bug #1806 ***
| The View shouldn't alter. | https://api.github.com/repos/MonetDB/MonetDB/issues/1808/comments | 0 | 2020-11-30T10:01:45Z | 2024-06-28T07:37:03Z | https://github.com/MonetDB/MonetDB/issues/1808 | 753,334,624 | 1,808 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 08:58:30 +0200
From: Qian Qiao <<drizzlerain>>
To: @njnes
Version: -- development
Last updated: 2008-08-31 10:33:00 +0200
## Comment 10163
Date: 2008-08-26 08:58:30 +0200
From: Qian Qiao <<drizzlerain>>
OS:RedHat Linux AS 4
GCC: 3.4.6
1.setup:
CREATE TABLE A (
GRADE decimal(4,0) DEFAULT NULL
);
INSERT INTO A VALUES (10);
INSERT INTO A VALUES (12);
2.execute:
UPDATE A
SET GRADE = -GRADE;
3.result:
select * from A;
+-------+
| grade |
+=======+
| 2 |
| -9265 |
+-------+
4.question:
After the positive number changes a negative number, its absolute value and the original absolute value are different.
## Comment 10164
Date: 2008-08-26 15:48:19 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
added test update_set_negative.SF-2075197.sql
Seems a bug in the update code.
## Comment 10165
Date: 2008-08-31 10:33:00 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
The accumulator optimizer was over ambitious.
The code based should be extended to allow for
accums over unaries and math functions as well.
## Comment 10166
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075197 at http://sourceforge.net/support/tracker.php?aid=2075197
| the abs value of a negative num not equals with it's positiv | https://api.github.com/repos/MonetDB/MonetDB/issues/1807/comments | 0 | 2020-11-30T10:01:42Z | 2024-06-27T11:32:17Z | https://github.com/MonetDB/MonetDB/issues/1807 | 753,334,582 | 1,807 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 08:57:32 +0200
From: Jane Chen <<cjnn>>
To: @njnes
Version: -- development
Last updated: 2010-07-09 15:12:41 +0200
## Comment 10159
Date: 2008-08-26 08:57:32 +0200
From: Jane Chen <<cjnn>>
OS: RedHat Linux AS 4
GCC: 3.4.6
1.setup:
create table A (a varchar(10));
create view myview
as select * from A;
2.execute:
alter table myview alter column a set null;
3.result:
The operation is OK
4.question:
The View shouldn't alter.
## Comment 10160
Date: 2008-08-26 15:43:44 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
added test alter_view_not_allowed.SF-2075195.sql
## Comment 10161
Date: 2008-09-09 14:52:28 +0200
From: @njnes
improved checking ilegal statements.
## Comment 10162
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075195 at http://sourceforge.net/support/tracker.php?aid=2075195
## Comment 14329
Date: 2010-07-09 15:12:41 +0200
From: @sjoerdmullender
*** Bug #1808 has been marked as a duplicate of this bug. ***
| The View shouldn't alter. | https://api.github.com/repos/MonetDB/MonetDB/issues/1806/comments | 0 | 2020-11-30T10:01:39Z | 2024-06-27T11:32:16Z | https://github.com/MonetDB/MonetDB/issues/1806 | 753,334,547 | 1,806 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 08:54:25 +0200
From: Jane Chen <<cjnn>>
To: @njnes
Version: -- development
CC: @sjoerdmullender
Duplicates: #1803
Last updated: 2010-07-09 15:13:29 +0200
## Comment 10156
Date: 2008-08-26 08:54:25 +0200
From: Jane Chen <<cjnn>>
OS: RedHat Linux AS 4
GCC: 3.4.6
1.setup:
CREATE TABLE A(q1 bigint, q2 bigint);
INSERT INTO A VALUES('4567890123456789','4567890123456789');
2.execute:
SELECT 2 * q1 AS q FROM A;
3.result:
!SQLException:lng_2_sht:too many digits (16 > 4)
## Comment 10157
Date: 2008-08-26 08:58:01 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Duplicate;
already reported as
[ 2075157 ] The return tyte of expression is wrong
http://sourceforge.net/tracker/index.php?func=detail&aid=2075157&group_id=56967&atid=482468
## Comment 10158
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075188 at http://sourceforge.net/support/tracker.php?aid=2075188
Bug has invalid status, setting status to "NEW".
Previous status was "DELETED".
## Comment 14330
Date: 2010-07-09 15:13:29 +0200
From: @sjoerdmullender
*** This bug has been marked as a duplicate of bug #1803 ***
| The return tyte of expression is wrong | https://api.github.com/repos/MonetDB/MonetDB/issues/1805/comments | 0 | 2020-11-30T10:01:35Z | 2024-06-28T13:27:46Z | https://github.com/MonetDB/MonetDB/issues/1805 | 753,334,489 | 1,805 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 08:49:16 +0200
From: Qian Qiao <<drizzlerain>>
To: @njnes
Version: -- development
Last updated: 2008-11-14 02:54:11 +0100
## Comment 10150
Date: 2008-08-26 08:49:16 +0200
From: Qian Qiao <<drizzlerain>>
OS:RedHat Linux AS 4
GCC: 3.4.6
1.setup:
CREATE TABLE FEAT16 (
EMPNUM INT PRIMARY KEY,
PNUM INT UNIQUE);
2.execute:
INSERT INTO FEAT16 VALUES (3, NULL);
INSERT INTO FEAT16 VALUES (4, NULL);
3.result:
The first INSERT operation is OK,but the second INSERT operation is failed:
!SQLException:assert:INSERT INTO: UNIQUE constraint 'feat16.feat16_pnum_unique' violated
## Comment 10151
Date: 2008-08-26 09:19:34 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
*Possibly* related to the NIL semantics issue reported in
[ 1960373 ] kunion and nil
http://sourceforge.net/tracker/index.php?func=detail&aid=1960373&group_id=56967&atid=482468
## Comment 10152
Date: 2008-08-26 15:34:50 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
added insert_into_unique_column.SF-2075180.sql
indeed we should allow for multiple NULL's
## Comment 10153
Date: 2008-09-10 11:17:31 +0200
From: @drstmane
See also
[ 2103348 ] unique problem with nulls
http://sourceforge.net/tracker/index.php?func=detail&aid=2103348&group_id=56967&atid=482468
[ 2075241 ] When the NULL is in a column,it shouldn't add primary key
http://sourceforge.net/tracker/index.php?func=detail&aid=2075241&group_id=56967&atid=482468
[ 1960373 ] kunion and nil
http://sourceforge.net/tracker/index.php?func=detail&aid=1960373&group_id=56967&atid=482468
## Comment 10154
Date: 2008-11-14 14:54:11 +0100
From: @romulogoncalves
The fix for this bug were the check ins:
[Monetdb-sql-checkins] sql/src/server sql_schema.mx, Nov2008, 1.152, 1.152.2.1
[Monetdb-sql-checkins] sql/src/server sql_updates.mx, Nov2008, 1.153, 1.153.2.1
[Monetdb-sql-checkins] sql/src/storage store.mx, Nov2008, 1.22, 1.22.2.1
## Comment 10155
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075180 at http://sourceforge.net/support/tracker.php?aid=2075180
| the unique column can't insert more than 1 row with null | https://api.github.com/repos/MonetDB/MonetDB/issues/1804/comments | 0 | 2020-11-30T10:01:31Z | 2024-06-27T11:32:14Z | https://github.com/MonetDB/MonetDB/issues/1804 | 753,334,442 | 1,804 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 08:34:06 +0200
From: Jane Chen <<cjnn>>
To: @njnes
Version: -- development
Last updated: 2010-07-09 15:13:29 +0200
## Comment 10146
Date: 2008-08-26 08:34:06 +0200
From: Jane Chen <<cjnn>>
OS: RedHat Linux AS 4
GCC: 3.4.6
1.setup:
CREATE TABLE A(q1 bigint, q2 bigint);
INSERT INTO A VALUES('4567890123456789','4567890123456789');
2.execute:
SELECT 2 * q1 AS q FROM A;
3.result:
!SQLException:lng_2_sht:too many digits (16 > 4)
## Comment 10147
Date: 2008-08-26 15:19:54 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Added test auto_coersion_bug.SF-2075157.sql
There is a bug in the automatic coersion of arguments to a binary function
## Comment 10148
Date: 2008-09-09 14:51:33 +0200
From: @njnes
fixed the coersion bug.
## Comment 10149
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075157 at http://sourceforge.net/support/tracker.php?aid=2075157
## Comment 14331
Date: 2010-07-09 15:13:29 +0200
From: @sjoerdmullender
*** Bug #1805 has been marked as a duplicate of this bug. ***
| The return tyte of expression is wrong | https://api.github.com/repos/MonetDB/MonetDB/issues/1803/comments | 0 | 2020-11-30T10:01:28Z | 2024-06-27T11:32:13Z | https://github.com/MonetDB/MonetDB/issues/1803 | 753,334,389 | 1,803 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 08:30:22 +0200
From: Qian Qiao <<drizzlerain>>
To: @njnes
Version: -- development
Last updated: 2009-02-09 03:08:06 +0100
## Comment 10141
Date: 2008-08-26 08:30:22 +0200
From: Qian Qiao <<drizzlerain>>
OS:RedHat Linux AS 4
GCC :3.4.6
1.setup:
CREATE TABLE WORKS
(EMPNUM CHAR(3) NOT NULL,
PNUM CHAR(3) NOT NULL,
HOURS DECIMAL(5),
UNIQUE(EMPNUM,PNUM));
2.execute:
SELECT DISTINCT EMPNUM FROM WORKS WORKSX WHERE NOT EXISTS (SELECT * FROM WORKS WORKSY WHERE EMPNUM = 'E2' AND NOT EXISTS (SELECT * FROM WORKS WORKSZ WHERE WORKSZ.EMPNUM = WORKSX.EMPNUM AND WORKSZ.PNUM = WORKSY.PNUM));
3.result:
MAPI = monetdb@localhost:50000
ACTION= read_line
QUERY = SELECT DISTINCT EMPNUM
ERROR = Connection terminated
## Comment 10142
Date: 2008-08-26 15:04:55 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Added correlated_exists.SF-2075147.sql test. This test gives problems both on the relational and binary relational version
## Comment 10143
Date: 2008-12-01 15:38:30 +0100
From: @romulogoncalves
This bug is fixed in the algebra version for the stable and current version of M5-SQL.
I can't close the bug until it is fixed in the normal version.
To use the algebra version just call mclient with option "-G":
mclient -G
## Comment 10144
Date: 2009-02-09 15:08:06 +0100
From: @romulogoncalves
The algebra version became the default one in the stable branch as well.
So the bug is fixed and it can be closed.
## Comment 10145
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075147 at http://sourceforge.net/support/tracker.php?aid=2075147
| after executing the sql below,the mclient quit | https://api.github.com/repos/MonetDB/MonetDB/issues/1802/comments | 0 | 2020-11-30T10:01:25Z | 2024-06-27T11:32:12Z | https://github.com/MonetDB/MonetDB/issues/1802 | 753,334,339 | 1,802 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 08:23:39 +0200
From: Qian Qiao <<drizzlerain>>
To: @njnes
Version: -- development
Last updated: 2008-09-09 02:50:37 +0200
## Comment 10136
Date: 2008-08-26 08:23:39 +0200
From: Qian Qiao <<drizzlerain>>
OS:RedHat Linux AS 4
GCC:3.4.6
1.setup:
CREATE TABLE A
(TOT_PRICE DECIMAL(12,2),
UNITS INTEGER);
CREATE TABLE B
(DOLLAR_EQUIV NUMERIC(5, 2),
POUND_EQUIV NUMERIC(8,2));
CREATE VIEW C (UNIT_PRICE)
AS SELECT (TOT_PRICE * DOLLAR_EQUIV) / (UNITS * POUND_EQUIV) FROM A, B;
2.insert:
INSERT INTO A VALUES (1411.5, 4000);
INSERT INTO B VALUES (1.00, 2.20);
3.result:
select * from C;
+-----------------------+
| unit_price |
+=======================+
| 0.0000 |
+-----------------------+
4.question:
The result is wrong.
## Comment 10137
Date: 2008-08-26 08:59:09 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
What should (have) be(en) the correct/expected result?
## Comment 10138
Date: 2008-08-26 14:58:30 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Added test mul_div_bug.SF-2075135.sql. The bug seems to trigger 2 problems. One casting of numerics with multiplication isn't done correctly (we lose some of the scale (2.2)). Second problem is with in the core, ie incorrect CMDbataccumMUL is called.
## Comment 10139
Date: 2008-09-09 14:50:37 +0200
From: @njnes
correct accum function is called now (fixes in the resolution of accumulator functions)
## Comment 10140
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075135 at http://sourceforge.net/support/tracker.php?aid=2075135
| the view with account row,selected wrong | https://api.github.com/repos/MonetDB/MonetDB/issues/1801/comments | 0 | 2020-11-30T10:01:22Z | 2024-06-27T11:32:11Z | https://github.com/MonetDB/MonetDB/issues/1801 | 753,334,300 | 1,801 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 08:22:46 +0200
From: Jane Chen <<cjnn>>
To: @njnes
Version: -- development
Last updated: 2008-09-09 02:49:17 +0200
## Comment 10131
Date: 2008-08-26 08:22:46 +0200
From: Jane Chen <<cjnn>>
OS: RedHat Linux AS 4
GCC: 3.4.6
1.setup:
CREATE TABLE A (a DATE);
2.execute:
INSERT INTO A VALUES (
DATE '9999-01-01' + INTERVAL '1-00' YEAR TO MONTH);
3.result:
select * from A;
+------------+
| a |
+============+
| 10000-01-0 |
: 1 |
+------------+
4.question:
"10000-01-01" is not a correct DATE.
## Comment 10132
Date: 2008-08-26 08:51:34 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Why is "10000-01-01" not a correct DATE?
(Admittedly, we cannoth predict whether or planet, let alone our civilization, will still exist, then, but the date itself looks perfectly correct to me...)
Or does the SQL standard limit its calender to 4-digit years, or so?
## Comment 10133
Date: 2008-08-26 14:11:34 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Added test add year_overflow_bug.SF-2075133.sql
. The sql specs indeed specify a DATE literal as YYYY-MM-DD.
## Comment 10134
Date: 2008-09-09 14:49:17 +0200
From: @njnes
We consider this a feature (also because XQuery allready defines these as correct)
## Comment 10135
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075133 at http://sourceforge.net/support/tracker.php?aid=2075133
| Don't limit the disable DATE | https://api.github.com/repos/MonetDB/MonetDB/issues/1800/comments | 0 | 2020-11-30T10:01:18Z | 2024-06-27T11:32:10Z | https://github.com/MonetDB/MonetDB/issues/1800 | 753,334,246 | 1,800 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 08:15:41 +0200
From: Jane Chen <<cjnn>>
To: @njnes
Version: -- development
CC: @sjoerdmullender
Duplicates: #1796
Last updated: 2010-07-09 15:13:57 +0200
## Comment 10128
Date: 2008-08-26 08:15:41 +0200
From: Jane Chen <<cjnn>>
OS:RedHat Linux AS 4
GCC:3.4.6
1.setup:
CREATE TABLE A (
CH1C CHAR (10) NOT NULL);
2.execute:
INSERT INTO A VALUES
('LITTLETOOLONG');
3.result:
select * from A;
+------------+
| ch1c |
+============+
| LITTLETOOL |
: ONG |
+------------+
4.question:
The length of "LITTLETOOLONG" more than 10, but Insert operation is successful
## Comment 10129
Date: 2008-08-26 09:03:23 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Duplicate;
already reported as
[ 2075078 ] The length of inserted string exceed the definded, not trunc
http://sourceforge.net/tracker/index.php?func=detail&aid=2075078&group_id=56967&atid=482468
## Comment 10130
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075118 at http://sourceforge.net/support/tracker.php?aid=2075118
Bug has invalid status, setting status to "NEW".
Previous status was "DELETED".
## Comment 14332
Date: 2010-07-09 15:13:57 +0200
From: @sjoerdmullender
*** This bug has been marked as a duplicate of bug #1796 ***
| Can not truncate the more String | https://api.github.com/repos/MonetDB/MonetDB/issues/1799/comments | 0 | 2020-11-30T10:01:14Z | 2024-06-28T13:29:28Z | https://github.com/MonetDB/MonetDB/issues/1799 | 753,334,184 | 1,799 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 08:07:34 +0200
From: Jane Chen <<cjnn>>
To: @njnes
Version: -- development
Last updated: 2008-09-09 02:48:06 +0200
## Comment 10124
Date: 2008-08-26 08:07:34 +0200
From: Jane Chen <<cjnn>>
OS: RedHat Linux AS 4
GCC: 3.4.6
1.setup:
CREATE TABLE A (a INT);
2.execute:
INSERT INTO A VALUES (.31416E+1);
3.result:
!types double(51,0) (dbl) and int(32,0) (int) are not equal
## Comment 10125
Date: 2008-08-26 14:05:07 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Not sure if why we would support this. It seems better to signal this user error then insert the down casted value. I'm not 100% sure about the SQL specs here but it sounds strange to me.
## Comment 10126
Date: 2008-09-09 14:48:06 +0200
From: @njnes
Was fixed by other changes to the type system. Added test in src/test/BugTracker-2008/Tests/insert_decimal_into_int.SF-2075104.sql
## Comment 10127
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075104 at http://sourceforge.net/support/tracker.php?aid=2075104
| Can not insert a DOUBLE data into the INT type | https://api.github.com/repos/MonetDB/MonetDB/issues/1798/comments | 0 | 2020-11-30T10:01:11Z | 2024-06-27T11:32:08Z | https://github.com/MonetDB/MonetDB/issues/1798 | 753,334,148 | 1,798 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 08:04:56 +0200
From: Qian Qiao <<drizzlerain>>
To: @njnes
Version: -- development
Last updated: 2008-09-09 02:43:11 +0200
## Comment 10120
Date: 2008-08-26 08:04:56 +0200
From: Qian Qiao <<drizzlerain>>
OS : RedHat Linux AS 4
GCC: 3.4.6
1.setup:
CREATE TABLE GROUPS1
(EMPNUM INT, GRP INT);
CREATE TABLE NAMES1
(EMPNUM INT, NAME CHAR(5));
CREATE VIEW NAMGRP1 AS
SELECT * FROM NAMES1 NATURAL JOIN GROUPS1;
2.insert:
INSERT INTO GROUPS1 VALUES (0, 10);
INSERT INTO GROUPS1 VALUES (1, 20);
INSERT INTO GROUPS1 VALUES (2, 30);
INSERT INTO NAMES1 VALUES (5, 'HARRY');
INSERT INTO NAMES1 VALUES (1, 'MARY');
INSERT INTO NAMES1 VALUES (0, 'KERI');
3.result:
SELECT EMPNUM
FROM NAMGRP1
WHERE NAME = 'KERI'
AND GRP = 10;
!SELECT: identifier 'name' unknown
4.question
The view by NATURAL JOIN,INNER JOIN,or RIGHT OUTER JOIN can be created,but when you select view replied wrong.
## Comment 10121
Date: 2008-08-26 14:02:46 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Added Tests/view_reply_incorrect.SF-2075097.sql
We incorrectly only return the 'joined' columns for natural joins.
## Comment 10122
Date: 2008-09-09 14:43:11 +0200
From: @njnes
natural join result columns were incorrect.
## Comment 10123
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075097 at http://sourceforge.net/support/tracker.php?aid=2075097
| select view repliy wrong | https://api.github.com/repos/MonetDB/MonetDB/issues/1797/comments | 0 | 2020-11-30T10:01:08Z | 2024-06-27T11:32:07Z | https://github.com/MonetDB/MonetDB/issues/1797 | 753,334,105 | 1,797 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 07:53:40 +0200
From: Qian Qiao <<drizzlerain>>
To: @njnes
Version: -- development
CC: cjnn
Last updated: 2010-07-09 15:13:57 +0200
## Comment 10115
Date: 2008-08-26 07:53:40 +0200
From: Qian Qiao <<drizzlerain>>
OS:RedHat Linux AS 4
GCC:3.4.6
1.setup:
CREATE TABLE staff (
`CITY` char(15) DEFAULT NULL
);
2.insert:
INSERT INTO STAFF VALUES ('Claggetsville Maryland');
3.result:
select * from staff;
+-----------------+
| CITY |
+=================+
| Claggetsville |
: Maryland |
+-----------------+
4.question:
The length of inserted string exceed the definded 15.
## Comment 10116
Date: 2008-08-26 09:11:10 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
an error should be returned instead
## Comment 10117
Date: 2008-08-26 13:59:37 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
test script added to src/tests/BugTracker-2008/Tests/string_length_not_checked.SF-2075078.sql
## Comment 10118
Date: 2008-09-09 14:42:26 +0200
From: @njnes
fixed dynamic length checking.
## Comment 10119
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075078 at http://sourceforge.net/support/tracker.php?aid=2075078
## Comment 14333
Date: 2010-07-09 15:13:57 +0200
From: @sjoerdmullender
*** Bug #1799 has been marked as a duplicate of this bug. ***
| The length of inserted string exceed the definded, not trunc | https://api.github.com/repos/MonetDB/MonetDB/issues/1796/comments | 0 | 2020-11-30T10:01:02Z | 2024-06-27T11:32:06Z | https://github.com/MonetDB/MonetDB/issues/1796 | 753,333,988 | 1,796 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 07:52:04 +0200
From: Jane Chen <<cjnn>>
To: @njnes
Version: -- development
Last updated: 2008-09-09 02:41:53 +0200
## Comment 10111
Date: 2008-08-26 07:52:04 +0200
From: Jane Chen <<cjnn>>
os: RedHat as 4
gcc: 3.4.6
1.setup:
CREATE TABLE A
(a NUMERIC(4,1) DEFAULT 98.6,
b NUMERIC(5) DEFAULT -55555);
2.insert:
INSERT INTO A(a) VALUES (99.0);
3.execute:
select * from A;
4.result:
+--------+-------+
| a |b |
+========+=======+
| 99.0 |null |
+--------+-------+
5.question:
The values of "b" should be "-55555".
## Comment 10112
Date: 2008-08-26 13:58:54 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Added a test to src/test/BugTracker-2008/Tests/incorrect_default_value_inserted.SF-2075075.sql
## Comment 10113
Date: 2008-09-09 14:41:53 +0200
From: @njnes
- handling wasn't done correctly for 'default' values.
## Comment 10114
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075075 at http://sourceforge.net/support/tracker.php?aid=2075075
| The DEFAULT value is wrong | https://api.github.com/repos/MonetDB/MonetDB/issues/1795/comments | 0 | 2020-11-30T10:00:59Z | 2024-06-27T11:32:05Z | https://github.com/MonetDB/MonetDB/issues/1795 | 753,333,941 | 1,795 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-24 11:40:49 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-08-25 12:08:55 +0200
## Comment 10108
Date: 2008-08-24 23:40:49 +0200
From: @drstmane
On Windows, starting mserver5 fails with
!MALException:MAL.getAddress:address of 'bat.BKCbatvmsize' not found
!MALException:MAL.getAddress:address of 'bat.BKCbatdisksize' not found
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.Int.32.32.d.1-Windows5.1..2008.08.24_00-09-03/test10.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.Int.64.64.d.1-Windows5.2..2008.08.24_00-09-03/test10.out.html
## Comment 10109
Date: 2008-08-25 00:08:55 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed in CVS.
Please note and remember:
Functions that are called from a different module / (shared) library / DLL
--- like, e.g., function that implement MAL commands ---
need to be properly ex- & imported.
Functions that are only used within the same source file they are defined in
MUST NOT be exported, but should (must) rather be declared "static".
## Comment 10110
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2072292 at http://sourceforge.net/support/tracker.php?aid=2072292
| mserver5 fails to start on Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/1794/comments | 0 | 2020-11-30T10:00:56Z | 2024-06-27T11:32:04Z | https://github.com/MonetDB/MonetDB/issues/1794 | 753,333,898 | 1,794 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-24 05:53:04 +0200
From: @mlkersten
To: @mlkersten
Version: -- development
Last updated: 2008-08-24 09:01:06 +0200
## Comment 10105
Date: 2008-08-24 17:53:04 +0200
From: @mlkersten
Properties are stored as constants in the symbol table and referenced from the variables they belong too.
However, in iteractive mode, at the end of the statement, they are garbage collected. This should only happen when the referring variable disappears
## Comment 10106
Date: 2008-08-24 21:01:06 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: YES
Cleanup the stack reduction code for interactive use.
No test needed.
## Comment 10107
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2071738 at http://sourceforge.net/support/tracker.php?aid=2071738
| M5: Properties get lost | https://api.github.com/repos/MonetDB/MonetDB/issues/1793/comments | 0 | 2020-11-30T10:00:53Z | 2024-06-27T11:32:03Z | https://github.com/MonetDB/MonetDB/issues/1793 | 753,333,854 | 1,793 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-24 04:44:42 +0200
From: @skinkie
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-09-25 11:03:01 +0200
## Comment 10089
Date: 2008-08-24 16:44:42 +0200
From: @skinkie
/opt/monetdb/bin/mclient -lxquery
xquery>count(doc("planet-nl.osm")/osm/node)
more>5689472
/opt/monetdb/bin/mclient -lxquery < osm-all-sql-node.xq > node.sql
for $node in doc("planet-nl.osm")/osm/node
return
element { "n" }
{
data($node/@id),
text { ", " },
data($node/@lat),
text { ", " },
data($node/@lon),
text { ", '" },
data($node/@user),
text { "', '" },
data($node/@timestamp),
text { "'" }
}
skinkie@localhost ~ $ wc node.sql
4478 22596 321310 node.sql
Maybe the just reported feature is a solution to this bug.
## Comment 10090
Date: 2008-08-24 17:01:22 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Could you please be a bit more elaborate on what the bug is that you report?
Please also (try to) provide all the information (incl. scripts and data, or at least access/references to them) that is required to reproduce the bug?
Thanks!
## Comment 10091
Date: 2008-08-24 17:06:18 +0200
From: @skinkie
Logged In: YES
user_id=533026
Originator: YES
I expect the output file to have 5689472 lines. And the output file doesn't have more lines than 4478?
http://hypercube.telascience.org/planet/planet-nl-080823.osm.gz is the source input file. It has been added with update support and 10% overhead. (I'm happy to give a login so you don't have to redo this process) The server has been compiled with --enable-optimise.
And the script is as simple as the above.
## Comment 10092
Date: 2008-08-24 17:17:38 +0200
From: @skinkie
Logged In: YES
user_id=533026
Originator: YES
And to be even more verbose:
skinkie@localhost /var/tmp $ grep -c "<node " planet-nl-latest.osm
5689472
Is my flower broken?
## Comment 10093
Date: 2008-08-24 17:18:50 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Thanks.
The problem might be cause by problems in the element construction in the Algebra back-end as, e.g., reported in
[ 2038906 ] XML attribute generation
http://sourceforge.net/tracker/index.php?func=detail&aid=2038906&group_id=56967&atid=482468
Could you please try whether the old "milprint_summer" back-end (`mclient -lx -g`) shows the same (or other) problems, or whether is works fine?
In any case, I don't expect this to be in any way related to how/when results are emitted, nor that any change in that would "solve" this bug ...
## Comment 10094
Date: 2008-08-24 17:20:35 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
ps: haven't managed to analyze/fix the bug in ds_link() of module mkey (cf.,
[ 2038906 ] XML attribute generation
http://sourceforge.net/tracker/index.php?func=detail&aid=2038906&group_id=56967&atid=482468
, yet, but we will look into this as soon as time permits...
## Comment 10095
Date: 2008-08-24 17:25:05 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
maybe a more detailed analysis than `wc` & `grep`, i.e., manually inspect the output, might shed some light on this ...
## Comment 10096
Date: 2008-08-24 17:41:09 +0200
From: @skinkie
Logged In: YES
user_id=533026
Originator: YES
I'm sorry but a file *by far* too small to contain all the nodes.
Here is your question:
skinkie@localhost ~ $ /opt/monetdb/bin/mclient -lx -g < osm-all-sql-node.xq > node.sql-test
MAPI = monetdb@localhost:50000
ACTION= read_line
QUERY = for $node in doc("planet-nl.osm")/osm/node
ERROR = Connection terminated
MonetDB Server v4.25.0
based on GDK v1.25.0
Copyright (c) 1993-2008, CWI. All rights reserved.
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.5.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.25.0 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:50001/admin
MonetDB>Segmentation fault
...specifically this version is non-debug, because I wanted to prepare a *fast* demo.
## Comment 10097
Date: 2008-08-25 17:36:14 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
With the latest CVS HEAD version of MonetDB/XQuery, your query appears to work fine with me, both with a read-only document and with an updateable document with 10% slack space:
$ mclient -lx -s'pf:add-doc("/tmp/planet-nl-080823.osm","planet-nl.osm.RO")'
$ mclient -lx -s'count(doc("planet-nl.osm.RO")/osm/node)' | tee /tmp/planet-nl.osm.RO.count
5689472
$ mclient -lx /tmp/planet-nl.osm.bug.RO.xq > /tmp/planet-nl.osm.bug.RO.out
$ wc /tmp/planet-nl.osm.bug.RO.out
5689472 28725882 399286712 /tmp/planet-nl.osm.bug.RO.out
$ mclient -lx -s'pf:add-doc("/tmp/planet-nl-080823.osm","planet-nl.osm.10","planet-nl.osm.10",10)'
$ mclient -lx -s'count(doc("planet-nl.osm.10")/osm/node)' | tee /tmp/planet-nl.osm.10.count
5689472
$ mclient -lx /tmp/planet-nl.osm.bug.10.xq > /tmp/planet-nl.osm.bug.10.out
$ wc /tmp/planet-nl.osm.bug.10.out
5689472 28725882 399286712 /tmp/planet-nl.osm.bug.10.out
## Comment 10098
Date: 2008-08-25 20:22:47 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Also works with the latest version from most recent release branches (cf., http://monetdb.cwi.nl/Development/Releases/Version4.24/).
## Comment 10099
Date: 2008-08-25 22:17:36 +0200
From: @skinkie
Logged In: YES
user_id=533026
Originator: YES
I'll test it this weekend.
## Comment 10100
Date: 2008-08-26 08:45:51 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Finally:
For me, it also works fine with the old MPS back-end for all 4 cases (Stable & Current each with read-only and updateable).
ps:
My setup:
64-bit machine with 8GB RAM;
running 64-bit Fedora 8;
64-bit MonetDB/XQuery (with default 64-bit OIDs);
configured with --disable-debug --enable-optimize --disable-assert;
compiled with gcc 4.1.2 .
## Comment 10101
Date: 2008-09-05 11:22:51 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Stefan,
any news on this one?
did you manage to test it, again?
does it work for you, too?
can we close this report?
Thanks!
Stefan
## Comment 10102
Date: 2008-09-25 11:03:01 +0200
From: @drstmane
Stefan,
I assuming it also work for you, now;
feel free to re-open if not ...
Stefan
## Comment 10103
Date: 2008-09-25 11:23:53 +0200
From: @skinkie
I also have the same issue with \> in -lsql; but I did not yet upgrade my system to the latest cvs head now. So I didn't want to put a new comment in.
## Comment 10104
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2071638 at http://sourceforge.net/support/tracker.php?aid=2071638
| mclient output is limited? | https://api.github.com/repos/MonetDB/MonetDB/issues/1792/comments | 0 | 2020-11-30T10:00:51Z | 2024-06-28T13:29:27Z | https://github.com/MonetDB/MonetDB/issues/1792 | 753,333,820 | 1,792 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-24 03:38:16 +0200
From: @skinkie
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2008-08-24 01:04:31 +0200
## Comment 10084
Date: 2008-08-24 03:38:16 +0200
From: @skinkie
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../src/saxophone -I../.. -I../../../src/saxophone -I/opt/monetdb/include/MonetDB -I/opt/monetdb/include/MonetDB/common -I/opt/monetdb/include/MonetDB/gdk -I/opt/monetdb/include/MonetDB4 -I/opt/monetdb/include/MonetDB4/monet -I/opt/monetdb/include/MonetDB4/plain -I/opt/monetdb/include/MonetDB4/contrib -I/opt/monetdb/include/MonetDB4/mapi -I/opt/monetdb/include/MonetDB4/calibrator -DLIBSAXOPHONE -march=nocona -O2 -pipe -mno-tls-direct-seg-refs -Wall -Wextra -std=c99 -O6 -fomit-frame-pointer -finline-functions -falign-loops=4 -falign-jumps=4 -falign-functions=4 -fexpensive-optimizations -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -ftree-vectorize -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2 -D_REENTRANT -I/usr/include/libxml2 -c saxophone.c -fPIC -DPIC -o .libs/lib_saxophone_la-saxophone.o
../../../src/saxophone/saxophone.mx: In function 'prefix2uri':
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
cc1: warnings being treated as errors
../../../src/saxophone/saxophone.mx:815: error: passing argument 1 of 'Hpos' from incompatible pointer type
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: passing argument 1 of 'Hpos' from incompatible pointer type
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: passing argument 1 of 'Tpos' from incompatible pointer type
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: passing argument 1 of 'Hpos' from incompatible pointer type
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx:815: error: request for member 'b' in something not a structure or union
../../../src/saxophone/saxophone.mx: In function 'endPrefixMappings':
../../../src/saxophone/saxophone.mx:825: error: implicit declaration of function 'BATloopFast'
../../../src/saxophone/saxophone.mx:825: error: expected ';' before '{' token
make[6]: *** [lib_saxophone_la-saxophone.lo] Error 1
make[6]: Leaving directory `/usr/src/monetdb/xml/Linux/src/saxophone'
## Comment 10085
Date: 2008-08-24 13:04:31 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
The Saxophone code is not maintained. It had been moved to the attic.
The SQL/XML could be used as an alternative route, when someone has
the time and drive to link libxml, handle the SQL/XML copy statement,
and add the calls to execute Xpath over a string using libxml.
Alternatively, one my consider MonetDB/XQuery.
## Comment 10086
Date: 2008-08-24 14:34:55 +0200
From: @skinkie
Logged In: YES
user_id=533026
Originator: YES
Please note this in the Readme.
## Comment 10087
Date: 2008-08-24 15:20:03 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Please note that the whole "xml" tree/module has been abandoned some time ago --- admittedly it is still there in CVS on SF, and its "end of life" might not have been announced properly ... sorry for the inconveniences ...
Which "readme" does refer to saxophone a readme inside the xml tree or some readme outside / somewhere else?
## Comment 10088
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2070571 at http://sourceforge.net/support/tracker.php?aid=2070571
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-common@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| saxophone prefix2uri fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1791/comments | 0 | 2020-11-30T10:00:48Z | 2024-06-28T13:29:27Z | https://github.com/MonetDB/MonetDB/issues/1791 | 753,333,767 | 1,791 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-22 04:20:35 +0200
From: @yzchang
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-11-12 11:54:58 +0100
## Comment 10078
Date: 2008-08-22 16:20:35 +0200
From: @yzchang
The following query triggers an assertion, instead of getting a compiler error:
$ cat st.xq
let $r :=
(for $p in doc("xmark1.xml")//person
let $ca := doc("xmark1.xml")//closed_auction[./seller/@person=$p/@id]
where not(empty($ca))
order by sum($ca/price)
return ($p, sum($ca/price)))
return ($r, $r/name)
$ mclient -lx st.xq
MAPI = monetdb@localhost:50000
ACTION= read_line
QUERY = (: let $a1 := attribute {"attr1"} {"attr val1"}
ERROR = Connection terminated
$ monet_pf
MonetDB Server v4.24.1
based on GDK v1.24.1
Copyright (c) 1993-2008, CWI. All rights reserved.
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.5.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.24.1 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:50001/admin
[ "N.B.: xrpc_trusted and xrpc_admin has been deleted.\n" ]
MonetDB>Mserver: /ufs/zhang/monet/stable/pathfinder/compiler/mil/milgen.brg:576: env_at: Assertion `i < ((env)->appi)' failed.
Aborted
I think we shouldn't let a query with incorrect syntax to terminate Mserver.
Regards,
Jennie
## Comment 10079
Date: 2008-09-05 16:19:19 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
For dynamic errors the MIL environment now does not become empty anymore (as in Jennies example).
The solution is that we keep a dummy error column with no content until an union operator is reached. (This works correctly as conditional errors only appear in typeswitches or if-then-else expressions -- represented by union operators in the algebra.)
## Comment 10080
Date: 2008-09-05 18:02:23 +0200
From: @yzchang
Logged In: YES
user_id=341633
Originator: YES
Jan, thanks for fixing it. However, the problem also exist in the stable branch, while your fix has been checked in into the current branch. Would you please back-port your fix to the stable branch? Thanks again.
I re-opened the bug just as a reminder.
Jennie
## Comment 10081
Date: 2008-09-05 18:05:04 +0200
From: @yzchang
Logged In: YES
user_id=341633
Originator: YES
test added in pathfinder/tests/BugTracker/Tests/pathstep_on_incorrect_type.SF-2067585
## Comment 10082
Date: 2008-11-12 11:54:58 +0100
From: Jan Rittinger <<jan.rittinger>>
We have a new stable branch -- closing again.
## Comment 10083
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2067585 at http://sourceforge.net/support/tracker.php?aid=2067585
| PF: path step on seq. with incorrect type triggers assertion | https://api.github.com/repos/MonetDB/MonetDB/issues/1790/comments | 0 | 2020-11-30T10:00:45Z | 2024-06-27T11:32:00Z | https://github.com/MonetDB/MonetDB/issues/1790 | 753,333,731 | 1,790 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-22 03:00:57 +0200
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2008-09-12 12:41:10 +0200
## Comment 10072
Date: 2008-08-22 15:00:57 +0200
From: @drstmane
/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/optimizer/opt_mergetable.mx(1268): error 593: variable "r" was set but never used
InstrPtr *old=0, r;
^
compilation aborted for opt_mergetable.c (code 2)
I cannot clearly say whether the respective variable can simply be removes, in particular since it seems to be re-declared in a sub-scope.
Hence, assigning to Niels who last modified this file...
## Comment 10073
Date: 2008-08-22 17:09:25 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
The Sun compiler (correctly) complains about
"/ufs/manegold/Monet/Current/source/MonetDB5/src/optimizer/opt_mergetable.mx", line 1545: warning: statement not reached
cc: acomp failed for opt_mergetable.c
## Comment 10074
Date: 2008-08-24 13:05:17 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Compiled by removal of superfluous assignment.
## Comment 10075
Date: 2008-08-24 15:22:23 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
re-opened as it still fails to compile with Sun compiler:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.Sun.32.32.d.1-SunOS5.11..2008.08.24_00-09-03/make.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.Sun.32.32.d.1-SunOS5.11..2008.08.24_00-09-03/make-k.out.html
## Comment 10076
Date: 2008-09-12 12:41:10 +0200
From: @sjoerdmullender
This seems to have been fixed by Martin.
## Comment 10077
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2067454 at http://sourceforge.net/support/tracker.php?aid=2067454
| MonetDB5 fails to compile with Intel & Sun compiler | https://api.github.com/repos/MonetDB/MonetDB/issues/1789/comments | 0 | 2020-11-30T10:00:42Z | 2024-06-27T11:31:59Z | https://github.com/MonetDB/MonetDB/issues/1789 | 753,333,695 | 1,789 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-22 11:31:35 +0200
From: @sjoerdmullender
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2008-08-22 12:01:59 +0200
## Comment 10068
Date: 2008-08-22 11:31:35 +0200
From: @sjoerdmullender
Since Fabian's checkin of Aug 20 to change the visibility of RMTfindconn, RMTinternalget, and RMTinternalput, sql won't build correctly anymore. These functions are referenced in sql/src/backends/monet5/sql_bpm.mx.
Assigning to Fabian because he made the change.
## Comment 10069
Date: 2008-08-22 11:56:15 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
Niels said he'd fix it. I'll check in a "compilation fix".
## Comment 10070
Date: 2008-08-22 12:01:59 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
revision 1.16
date: 2008/08/22 09:53:53; author: nielsnes; state: Exp; lines: +30 -28
make sql_bpm.mx compile again (mostly done the ughly way using comments, needs
cleanup when romulo returns)
## Comment 10071
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2067073 at http://sourceforge.net/support/tracker.php?aid=2067073
| SQL won't compile | https://api.github.com/repos/MonetDB/MonetDB/issues/1788/comments | 0 | 2020-11-30T10:00:39Z | 2024-06-27T11:31:58Z | https://github.com/MonetDB/MonetDB/issues/1788 | 753,333,649 | 1,788 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-20 12:30:31 +0200
From: @grobian
To: @mlkersten
Version: -- development
Last updated: 2008-08-20 09:09:54 +0200
## Comment 10062
Date: 2008-08-20 12:30:31 +0200
From: @grobian
take this example:
function myfunc(o:bat[:any_1,:any_2]);
len := aggr.count(o);
io.print(len);
end myfunc;
function myfunc(o:any);
io.print(o);
end myfunc;
b := bat.new(:str, :int);
myfunc(b);
result:
-----------------
h t name
str int type
-----------------
expected:
[ 0 ]
If this is not allowed, then either kill overloading, or make the parser reject these kinds of overloadings. The ability to overload suggests that overloading also properly works by taking the most specific match. :bat[:any_1,:any_2] is IMHO more specific than :any.
## Comment 10063
Date: 2008-08-20 21:09:54 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
There is no such MAL type resolution rule intended in the language.
Such a rule can not be defined when more then one argument exists.
The function signatures are pre-pended to the symbol table
and matched accordingly.
As such, the last function is called her.
## Comment 10064
Date: 2008-08-20 21:20:14 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
That is somehow disturbing. I'd rather disallow any signatures where the argument list has the same length, and joker types are used, to force a correct order.
## Comment 10065
Date: 2008-08-20 21:22:12 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
There is no such MAL type resolution rule intended in the language.
Such a rule can not be defined when more then one argument exists.
The function signatures are pre-pended to the symbol table
and matched accordingly.
As such, the last function is called her.
## Comment 10066
Date: 2008-08-20 21:24:04 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
No way. It is used in many modules to handle specific types
and is also part of the polymorphic function resolution.
They would not be allowed to exist otherwise.
## Comment 10067
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2062062 at http://sourceforge.net/support/tracker.php?aid=2062062
| M5: resolution doesn't pick most specific overloaded func | https://api.github.com/repos/MonetDB/MonetDB/issues/1787/comments | 0 | 2020-11-30T10:00:37Z | 2024-06-28T13:29:26Z | https://github.com/MonetDB/MonetDB/issues/1787 | 753,333,612 | 1,787 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-20 09:23:08 +0200
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2008-08-20 10:01:21 +0200
## Comment 10059
Date: 2008-08-20 09:23:08 +0200
From: @drstmane
sql_gencode.mx:1883: variable "nr" was set but never used
1881 static void backend_dumpstmt(backend *be, MalBlkPtr mb, stmt *s)
1882 {
1883 int nr = _dumpstmt(be, mb, s);
1884 mvc *c = be->mvc;
1885 InstrPtr q;
http://www.ins.cwi.nl/~monet/permastore/2008-08-20/Current/make-sql-Int.64.32.d.1-Fedora8.errors.htmll346
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.Int.64.64.d.1-Fedora8/make-k.out.html
From the code and the latest changes, I'm not completely sure, whether variable "nr" could simply be removed, or whether is use was simply "forgotten" by accient --- otherwise, I could (and would) have fixed it myself ...
## Comment 10060
Date: 2008-08-20 10:00:30 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
clarified the code, dropping nr.
no test needed
## Comment 10061
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2061707 at http://sourceforge.net/support/tracker.php?aid=2061707
| SQL fails to compile with icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1786/comments | 0 | 2020-11-30T10:00:34Z | 2024-06-27T11:31:56Z | https://github.com/MonetDB/MonetDB/issues/1786 | 753,333,576 | 1,786 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-19 12:05:50 +0200
From: Wouter Alink <<alink>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-11-12 12:00:33 +0100
## Comment 10054
Date: 2008-08-19 12:05:50 +0200
From: Wouter Alink <<alink>>
Occurs with releases MonetDB-Jun and MonetDB-Aug. Algebra backend.
given a document aap.xml and bug.xq:
-bash-3.1$ cat aap.xml
<?xml version="1.0" encoding="utf-8"?>
<reports>
<folder name="noot">
</folder>
</reports>
-bash-3.1$ cat bug.xq
declare option pf:recursion-depth "5";
declare function doThing($folders as node()*) as node()* {
for $folder in $folders
return element folder { doThing($folder/folder) }
};
doThing((doc("aap.xml")/reports/folder, element folder { }))
-bash-3.1$
-bash-3.1$ mclient -lxq -p51240 bug.xq
MAPI = monetdb@localhost:51240
QUERY = declare option pf:recursion-depth "5";
ERROR = !ERROR: PFll_child: cand_bat with kind test must be a real kind bat.
!ERROR: PFll_child: operation failed.
-bash-3.1$
a preliminary investigation seems to point to the following line:
"""
a0009 := step (AXIS_child, TEST_nsloc, a0012, a0010, a0011, nil, ws, 3, ELEMENT, "", "folder", str(nil));
"""
in which BATs 10 11 and 12 have the following values:
[ "a0010" ]
-----------------
t h name
void oid type
-----------------
[ 0@0, 0@0 ]
[ 1@0, 1@0 ]
[ "a0011" ]
-----------------
t h name
void oid type
-----------------
[ 0@0, 2@0 ]
[ 1@0, 4@0 ]
[ "a0012" ]
-----------------
t h name
void oid type
-----------------
[ 0@0, 2@0 ]
[ 1@0, 1@0 ]
## Comment 10055
Date: 2008-09-05 10:45:31 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
The query and the generated MIL-code seems correct to me.
Anyway I hunted down that bug a little bit more.
This query seems to be a very rare case where not a special case is hit in the path algorithms. It can be simplied to e.g.:
((doc("aap.xml")/reports/folder, element folder { }))/folder
The problem resides in lines 181-184 of function PFll_child() (ll_staircasejoin.mx)
181 if (kind_test != chr_nil) {
182 if (cand_bat->ttype != TYPE_chr || /* it contains kinds */
183 BATcount(cand_bat) != BATcount(pre_size) || /* is the entire pre table */
184 cand_bat->htype != TYPE_void) /* and a real void bat (i.e. chr array) */
185 {
186 GDKerror("%s: cand_bat with kind test must be a real kind bat.\n", name);
187 @:ll_return(GDK_FAIL)@
188 }
called from PROC loop_lifted_child_step_with_nsloc_test() where the problematic input parameters are
print(cands);
-----------------
t h name
void oid type
-----------------
[ 0@0, 4@0 ]
print(pre_size);
-----------------
h t name
void int type
-----------------
[ 0@0, 6 ]
[ 1@0, 5 ]
[ 2@0, 4 ]
[ 3@0, 0 ]
[ 4@0, 1 ]
[ 5@0, 0 ]
[ 6@0, 0 ]
print(kind_test);
[ '\000' ]
The kind test is true as 'chr(0) != chr(nil)' but the candidate list contains node references instead of possible kinds.
Stefan could you perhaps have a look?
## Comment 10056
Date: 2008-10-08 19:20:03 +0200
From: @drstmane
Fixed in CVS --- this was a "nice" one; took me some time (despite Jan's detailed preparations; THANKS!) to find out that the solution is quite simple: we need to reset variable "kind_test" to "chr_nil" in the loop_lifted_X_step_with_Y_test() PROCs for each fragment ("cont") ...
Also added a test in pathfinder/tests/BugTracker/Tests/combination_of_constructed_and_doc_elements.SF-2059394.*
Jan, Wouter,
could you please verify the results I check in in
pathfinder/tests/BugTracker/Tests/combination_of_constructed_and_doc_elements.SF-2059394.stable.out
?
Thanks!
Stefan
## Comment 10057
Date: 2008-11-12 12:00:33 +0100
From: Jan Rittinger <<jan.rittinger>>
the output of the test fits the query -- closing the bug.
## Comment 10058
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2059394 at http://sourceforge.net/support/tracker.php?aid=2059394
| XQ: combination of constructed and doc elements | https://api.github.com/repos/MonetDB/MonetDB/issues/1785/comments | 0 | 2020-11-30T10:00:31Z | 2024-06-27T11:31:55Z | https://github.com/MonetDB/MonetDB/issues/1785 | 753,333,539 | 1,785 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-19 11:55:06 +0200
From: @grobian
To: @mlkersten
Version: -- development
Last updated: 2008-08-20 09:58:00 +0200
## Comment 10045
Date: 2008-08-19 11:55:06 +0200
From: @grobian
b := bat.new(:str, :int);
t := inspect.getTypeIndex(b);
io.print(t);
s := inspect.getTypeName(t);
io.print(s);
returns:
[ 6 ]
[ "int" ]
(or is it that getTypeIndex doesn't work well on BATs?)
## Comment 10046
Date: 2008-08-20 09:58:00 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Clarification of semantics. It returns the typeindex of the tail type.
Upon need more will be added, e.g. (ht,tt):= getTypeIndex(b:bat[...
## Comment 10047
Date: 2008-08-20 10:15:36 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
>i:=1:int;
>b:=bat.new(:str, :flt);
>tii:=inspect.getTypeIndex(i);
>tib:=inspect.getTypeIndex(b);
>tni:=inspect.getTypeName(tii);
>tnb:=inspect.getTypeName(tib);
>io.print(tii);
[ 6 ]
>io.print(tib);
[ 10 ]
>io.print(tni);
[ "int" ]
>io.print(tnb);
[ "flt" ]
>manual.help("inspect.getTypeIndex");
inspect.getTypeIndex
>manual.help("getTypeIndex");
inspect.getTypeIndex
>manual.search("getTypeIndex");
pattern inspect.getTypeIndex(v:any_1):int address INSPECTtypeIndex;
Return the type index of a variable.
So, the implementation of getTypeIndex() does not match its documentation.
Is there any other function/way in MAL to find out whether a variable is of an atomic scalar type, or whether it is a BAT?
## Comment 10048
Date: 2008-08-20 10:23:02 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
Hehe, indeed. At one point I was indeed looking for an "isBAT" function.
## Comment 10049
Date: 2008-08-20 10:30:08 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
The historian recalls that MIL used to have a "type" function that returns a variable's type, and functions "htype" & "ttype" to request a BATs head- and tail-type:
MonetDB>var i := 1;
MonetDB>var b := bat(oid,flt);
MonetDB>print(type(i));
[ 6 ]
MonetDB>print(type(b));
[ 5 ]
MonetDB>print(htype(b));
[ 7 ]
MonetDB>print(ttype(b));
[ 10 ]
MonetDB>print(monet_atomtbl.select(type(i)));
-----------------
h t name
str int type
-----------------
[ "int", 6 ]
MonetDB>print(monet_atomtbl.select(type(b)));
-----------------
h t name
str int type
-----------------
[ "bat", 5 ]
[ "BAT", 5 ]
MonetDB>print(head(b));
[ "oid" ]
MonetDB>print(tail(b));
[ "flt" ]
## Comment 10050
Date: 2008-08-20 10:32:21 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
... and: does inspect.getTypeIndex() work recursively on a BAT who's tail type is again a BAT ... ?
## Comment 10051
Date: 2008-08-20 12:38:15 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Martin,
was it your intention with your latest code changes that inspect.getTypeIndex(v:any_1):int still returns the v's tail type in case v if of type BAT?
What is the intention/reason for this behaviour?
Why can't inspect.getTypeIndex(v:any_1):int for v:BAT simply return "5", i.e., the index of type "BAT"?
For me, this would be the most simple, intuitive and consistent semantic of inspect.getTypeIndex(v:any_1):int, definitely since the addition of inspect.getTypeIndex(v:bat[:any_1,:any_2]) (ht:int,tt:int) (and the fact that MAL does signature matching on both arguments and return type) ...
========
>b:=bat.new(:oid,:dbl);
>i:=inspect.getTypeIndex(b);
>(h,t):=inspect.getTypeIndex(b);
>io.print(i);
[ 11 ]
>io.print(h);
[ 7 ]
>io.print(t);
[ 11 ]
>x:=inspect.getTypeName(i);
>io.print(x);
[ "dbl" ]
>x:=inspect.getTypeName(h);
>io.print(x);
[ "oid" ]
>x:=inspect.getTypeName(t);
>io.print(x);
[ "dbl" ]
========
>x:=inspect.getTypeName(5);
>io.print(x);
[ "BAT" ]
========
## Comment 10052
Date: 2008-08-20 12:53:59 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Just to increase my insight, the following behavior of the new inspect.qualType() function is intended to be as follows?
========
>b:=bat.new(:int,:dbl);
>io.print(b);
-----------------
h t name
int dbl type
-----------------
>x:=inspect.equalType(b,:dbl);
>io.print(x);
[ false ]
>x:=inspect.equalType(b,:bat);
>io.print(x);
[ false ] <===============================
>x:=inspect.equalType(b,:bat[:int,:dbl]);
>io.print(x);
[ true ]
>x:=inspect.equalType(b,:bat[:any,:any]);
>io.print(x);
[ false ] <===============================
========
## Comment 10053
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2059378 at http://sourceforge.net/support/tracker.php?aid=2059378
| M5: getTypeIndex && getTypeName misaligned? | https://api.github.com/repos/MonetDB/MonetDB/issues/1784/comments | 0 | 2020-11-30T10:00:28Z | 2024-06-28T13:29:25Z | https://github.com/MonetDB/MonetDB/issues/1784 | 753,333,500 | 1,784 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-19 11:51:46 +0200
From: @grobian
To: @mlkersten
Version: -- development
Last updated: 2008-08-20 08:51:17 +0200
## Comment 10042
Date: 2008-08-19 11:51:46 +0200
From: @grobian
I'm not sure if this behaviour is intended:
b := bat.new(:str, :int);
s := bat.getSize(b);
io.print(s);
bat.insert(b, "test", 1);
s := bat.getSize(b);
io.print(s);
it returns twice the same value:
[ 24576 ]
[ 24576 ]
(question: how do I retrieve the number of BUNs in a BAT?)
## Comment 10043
Date: 2008-08-20 08:51:17 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
The current getSize calculates the storage based on
rounding it to pagesizes.
Given the change in BBP storage structures, the
getSize and getDiskSize have been upgraded.
The capacity of the BAT can be obtained with bat.getCapacity()
and the number of elements with aggr.count()
The page size can be obtained with bbp.getPageSize()
## Comment 10044
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2059370 at http://sourceforge.net/support/tracker.php?aid=2059370
| M5: bat.batSize() broken? | https://api.github.com/repos/MonetDB/MonetDB/issues/1783/comments | 0 | 2020-11-30T10:00:26Z | 2024-06-28T13:29:24Z | https://github.com/MonetDB/MonetDB/issues/1783 | 753,333,473 | 1,783 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-14 01:56:48 +0200
From: @grobian
To: @mlkersten
Version: -- development
Last updated: 2008-08-14 03:25:49 +0200
## Comment 10039
Date: 2008-08-14 13:56:48 +0200
From: @grobian
This trivial piece of MAL code crashes the server:
>t := nil;
>c := "bla";
(segmentation fault)
or a variant:
>c := "bla";
>t := nil;
>f := inspect.getType(t);
(segmentation fault)
Problem is, this only happens on the console, not when executed from a script.
(Too bad, I don't get a euro for each bug. I would get rich if I'd spend another 10 minutes with M5... *shakes head*)
## Comment 10040
Date: 2008-08-14 15:25:49 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Don't leave garbage behind.
No test needed, since this was triggered for console sessions only
## Comment 10041
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2051328 at http://sourceforge.net/support/tracker.php?aid=2051328
| M5: segmentation fault after nil assignment | https://api.github.com/repos/MonetDB/MonetDB/issues/1782/comments | 0 | 2020-11-30T10:00:23Z | 2024-06-27T11:31:52Z | https://github.com/MonetDB/MonetDB/issues/1782 | 753,333,427 | 1,782 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-14 01:47:07 +0200
From: @grobian
To: @mlkersten
Version: -- development
Last updated: 2008-11-08 10:24:38 +0100
## Comment 10033
Date: 2008-08-14 13:47:07 +0200
From: @grobian
observed 14-08-2008: the parser already truncates e in the parsed
program, additionally, l is not a lng, but a string.
s := "89437487923647823647862387462378468723634":str;
io.print(s);
l := s:lng;
io.print(l);
e := 89437487923647823647862387462378468723634:lng;
io.print(e);
added as tests/BugReports/Tests/lngsaretruncated
## Comment 10034
Date: 2008-08-14 13:50:00 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
to repeat: please note that this is 2 bugs in one:
casting string to lng doesn't always work, though parsed as:
7 e:lng := _9: lng
(adding the type to e here results in an error)
the parser does not deal with the overflow when setting the constant
## Comment 10035
Date: 2008-08-18 01:24:00 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
The first and third case are now handled.
The second case can not be easily handled,
because the underlying implementation in
gdk_atoms does not
## Comment 10036
Date: 2008-08-18 08:13:27 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
The second statement is wrong, because only literals can be casted this way.
Other coercions follow the ordinary calc.lng(s) approach.
The parser does not catch this yet.
## Comment 10037
Date: 2008-11-08 00:08:26 +0100
From: @mlkersten
These bugs seem to be fixed in the latest stable.
Test file added BugTracker/parser.SF-2051309.mal
## Comment 10038
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2051309 at http://sourceforge.net/support/tracker.php?aid=2051309
| M5: lngs are truncated | https://api.github.com/repos/MonetDB/MonetDB/issues/1781/comments | 0 | 2020-11-30T10:00:20Z | 2024-06-27T11:31:51Z | https://github.com/MonetDB/MonetDB/issues/1781 | 753,333,390 | 1,781 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-14 01:34:48 +0200
From: @grobian
To: @mlkersten
Version: -- development
Last updated: 2008-08-16 08:05:56 +0200
## Comment 10030
Date: 2008-08-14 13:34:48 +0200
From: @grobian
observed 13-08-2008: printf accepts a long for an int formatter,
whereas it should complain (additionally the error could be clearer)
l := 12:lng;
f := 5:flt;
io.printf("%d\n", l);
io.printf("%d\n", f);
(the same goes for flt and dbl)
added as tests/BugReports/Tests/printfacceptsmismatch
## Comment 10031
Date: 2008-08-16 20:05:56 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
The semantics of io.printf relies on the underlying C-implementation,
which means that we simply pass a pointer to the value and catch
an error of io.printf().
There is no analysis of the format string against the type.
Moved to feature request.
## Comment 10032
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2051290 at http://sourceforge.net/support/tracker.php?aid=2051290
| M5: printf accepts type mismatches | https://api.github.com/repos/MonetDB/MonetDB/issues/1780/comments | 0 | 2020-11-30T10:00:17Z | 2024-06-28T13:29:24Z | https://github.com/MonetDB/MonetDB/issues/1780 | 753,333,357 | 1,780 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-14 01:22:07 +0200
From: @grobian
To: @mlkersten
Version: -- development
Last updated: 2008-08-16 08:00:58 +0200
## Comment 10025
Date: 2008-08-14 13:22:07 +0200
From: @grobian
observed 14-08-2008: true, false and nil are not available in a
function, whereas they are locally
function user.myfunc(i:int):bit;
barrier ifpart := i == 1;
return(true);
exit ifpart;
barrier ifpart := i == 2;
return(false);
exit ifpart;
barrier ifpart := i == 3;
return(nil:bit);
exit ifpart;
end user.myfunc;
!TypeException:user.myfunc[2]:'true' may not be used before being initialized
io.print(true);
p := user.myfunc(1);
io.print(p);
io.print(false);
p := user.myfunc(2);
io.print(p);
io.print(nil:bit);
p := user.myfunc(3);
io.print(p);
no idea what this does
p := user.myfunc(4);
io.print(p);
Added as tests/BugReports/Tests/notruefalsenil
## Comment 10026
Date: 2008-08-16 20:00:58 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
A RETURN qualifier should be used in combination with an assignment.
A function should have at least on return statement at top level,
because you can not statically ensure it will be handled deeper.
These changes have been reflected in the test and stricter parsing.
## Comment 10027
Date: 2008-08-16 23:49:48 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
I don't really understand it, but it sounds like the bug is invalid then?
Also, I do not understand your change to the test.
First, by changing the test, you no longer IMO test the bug.
Second, it seems some "myfunc" is falling out of the air (I don't like the assumption it's just equal to "user.myfunc").
Third, it seems the parser doesn't really return indicative error messages judging by the changes made to this test.
## Comment 10028
Date: 2008-08-17 08:23:12 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Invalid part:
A missing module name is considered a reference to the current module.
This way all functions/patterns/... are associated with the module in which
they are defined unless explicitly told otherwise.
This also applied to function calls.
Valid part: Stricter parsing and error handling is needed.
Error message for true/false/nil is improved
## Comment 10029
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2051271 at http://sourceforge.net/support/tracker.php?aid=2051271
| M5: true, false and nil unavailable in a function | https://api.github.com/repos/MonetDB/MonetDB/issues/1779/comments | 0 | 2020-11-30T10:00:14Z | 2024-06-27T11:31:49Z | https://github.com/MonetDB/MonetDB/issues/1779 | 753,333,320 | 1,779 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-14 01:13:00 +0200
From: @grobian
To: @mlkersten
Version: -- development
Last updated: 2008-08-20 09:05:44 +0200
## Comment 10016
Date: 2008-08-14 13:13:00 +0200
From: @grobian
observed 13-08-2008: inspect.getType works fine local, but not in a
function on an argument with type :any
function user.typetest(o:any);
t := inspect.getType(o);
io.print(t);
end user.typetest;
p := "string";
t := inspect.getType(p);
here it is still a "str"
io.print(t);
but now it is a "any", should be "str"
user.typetest(p);
Added as tests/BugReports/Tests/gettype_in_function
## Comment 10017
Date: 2008-08-14 13:52:55 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
this bug blocks further development on remote module
## Comment 10018
Date: 2008-08-15 08:18:26 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
In cloning all any arguments should be passed on.
Using :any as the equivalent for :any_0
## Comment 10019
Date: 2008-08-16 23:53:57 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
isn't that a good argument to disallow :any as type in function arguments (in their declaration)?
## Comment 10020
Date: 2008-08-19 15:05:04 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
Ultimate fun!:
function user.doit(o:any):void;
t := inspect.getType(o);
io.print(t);
end user.doit;
s := "my string";
user.doit(s);
b := bat.new(:str, :int);
t := inspect.getType(b);
io.print(t);
user.doit(b);
user.doit(s);
returns:
[ "str" ]
[ "bat[:str,:int]" ]
[ "any" ]
[ "any" ]
## Comment 10021
Date: 2008-08-20 11:04:08 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Extended the facilities to retrieve the types
and solved a problem in the cloneFunction.
Additional inspection routines are added upon need.
## Comment 10022
Date: 2008-08-20 12:25:55 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
I'm getting frustrated by this.
function myfunc(o:any);
t := inspect.getType(o);
barrier isbat := str.startsWith(t, "bat");
len := aggr.count(o);
exit isbat;
end myfunc;
works fine for an invocation with a bat, however it fails horribly when invoked with e.g. an int:
!TypeException:user.myfunc[5]:'aggr.count' undefined in: len:any := aggr.count(o:int)
!MALException:user.myfunc[0]:Error in cloned function
reflection (a runtime thing) is mixed up with a static analysis thing here, it seems.
Additionally, see the next bug for a workaround which doesn't work either.
## Comment 10023
Date: 2008-08-20 21:05:44 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
The sample expression is correctly handled.
Test file has been extended with a few more cases.
## Comment 10024
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2051258 at http://sourceforge.net/support/tracker.php?aid=2051258
| M5:inspect.getType returns wrong type in :any typed function | https://api.github.com/repos/MonetDB/MonetDB/issues/1778/comments | 0 | 2020-11-30T10:00:10Z | 2024-06-27T11:31:48Z | https://github.com/MonetDB/MonetDB/issues/1778 | 753,333,267 | 1,778 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-13 11:28:41 +0200
From: mafweb <<mafweb>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-04-07 12:22:59 +0200
## Comment 10009
Date: 2008-08-13 11:28:41 +0200
From: mafweb <<mafweb>>
I've shredded 8931 documents as collection "xbrl" into an empty database build from MonetDB-Feb2008 tarball.
When I do:
let $docs := for $d in collection('xbrl')
where $d/*
return $d
return count($docs)
it should return 8931, but instead the answer was: 8924.
So, I decided to download yesterdays tarball, after a long wait while compiling, I shredded the 8931 documents into collection xbrl again.
Now I get:
ERROR = !fatal error: Algebra implementation for function `fn:collection' unknown.
This is not the main issue, but if someone could tell me why I'm missing fn functions, it would help.
So, changing to
count(pf:documents())
results in 8977 (???)
restart of the Mserver, redo query:
count(pf:documents())
results in 8931 (OK, as it should be)
Rechecked the feb version, after restart Mserver count indeed results correct amount.
What is wrong here? Some counter recalculated after server start, which isn't set correctly initially?
## Comment 10010
Date: 2008-08-13 11:43:41 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
Hi, fn:collection is not implemented yet in the algebra front-end. It was mentioned in the release notes.
This bug seems highly relates to:
[ 2009556 ] XQ: "Zombie" document in collection
https://sourceforge.net/tracker/index.php?func=detail&aid=2009556&group_id=56967&atid=482468
which in turn is related to:
[ 1976341 ] XQ: leftovers after deleting document
http://sourceforge.net/tracker/index.php?func=detail&aid=1976341&group_id=56967&atid=482468
and probably that is why after restarting the server the count was ok.
We are trying to fix these series of bugs, which probably all originate from the same problem.
## Comment 10011
Date: 2008-10-01 16:39:08 +0200
From: @sjoerdmullender
This seems to work in the current development version.
Note that to use the collection function you need to pass the -g (--no-algebra) option to mclient.
Can you check?
What I did to test is to load 8931 copies of the example document from http://sourceforge.net/support/tracker.php?aid=1990815 into the same collection (with 10% extra update space) and then run the two queries mentioned above (with the -g flag). All of this without restarting the server.
I did have to fix an unrelated bug in the server first, so you really need a very up-to-date server.
## Comment 10012
Date: 2009-02-16 13:34:54 +0100
From: @drstmane
re-opened to remind us that we should consider adding a test
## Comment 10013
Date: 2009-04-07 12:22:59 +0200
From: @peterboncz
there is a test for 2009556, which is the same issue
## Comment 10014
Date: 2009-04-07 13:10:12 +0200
From: @drstmane
Since the test for 2009556 still(?) fails (cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugTracker/Zombie_document.SF-2009556.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_BugTracker/Zombie_document.SF-2009556.out.00.html
),
I'd still propose to add a separate test for this one to check/verify that the particular problem reported here has indeed been fixed and does (still) work ...
## Comment 10015
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2049320 at http://sourceforge.net/support/tracker.php?aid=2049320
| pf:collection doc count wrong (again?) | https://api.github.com/repos/MonetDB/MonetDB/issues/1777/comments | 0 | 2020-11-30T10:00:06Z | 2024-06-27T11:31:47Z | https://github.com/MonetDB/MonetDB/issues/1777 | 753,333,220 | 1,777 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-07 04:50:05 +0200
From: Mike Mark <<mmarkog>>
To: @njnes
Version: -- development
Last updated: 2008-08-10 05:24:17 +0200
## Comment 10004
Date: 2008-08-07 16:50:05 +0200
From: Mike Mark <<mmarkog>>
Operating system: Windows XP
I'm having trouble getting range joins on strings working properly.
I looked into it and I found out that
ALGrangejoin (algebra.c) calls BATrangejoin (gdk_rangejoin.c) that
performs the join and returns a BAT as a result. BATrangejoin has a
switch with a case for TYPE_chr that compares strings
When I try to perform a range join on a string attribute (char(n),
even for n=1, varchar(n)) I get an exception:
!MALException:algebra.rangejoin:GDKerror
!ERROR: BATrangejoin: type not implemented
The switch statement skips the TYPE_chr case and goes to the default.
For example,
sql>create table s1 (id int, v char(10)); create table s2 (id int, v
sql>char(10)); insert into s1 values (1,'s1'); insert into s1 values
sql>(2,'s2'); insert into s1 values (3,'s3'); insert into s1 values
sql>(4,'s4'); insert into s1 values (5,'s5'); insert into s1 values
sql>(6,'s6'); insert into s2 values (1,'s1'); insert into s2 values
sql>(2,'s2'); insert into s2 values (3,'s3'); insert into s2 values
sql>(4,'s4'); insert into s2 values (5,'s5'); insert into s2 values
sql>(6,'s6'); select s1.id from s1, s2 where s1.v between s2.v and
sql>s2.v||'c' ;
!MALException:algebra.rangejoin:GDKerror
!ERROR: BATrangejoin: type not implemented
whereas
sql>select s1.id from s1, s2 where s2.id=2 and s1.id between s2.idand s2.id+1 ;
+----+
| id |
+====+
| 2 |
| 3 |
+----+
Thanks
## Comment 10005
Date: 2008-08-10 14:21:07 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
This bug was already been fixed by Niels in the stable branch.
Modified Files:
Tag: MonetDB_1-24
gdk_rangejoin.mx
Log Message:
added missing (rangejoin) implemenation for any types
Changing resolution to fixed, but leaving the bug open because a test need to be added.
## Comment 10006
Date: 2008-08-10 17:24:17 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
Added test with name 'range_join_any.SF-2041785`
Closing bug.
## Comment 10007
Date: 2008-08-13 11:38:15 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
(Just?) for completeness:
To benefit from the fixes, please do the following
1)
In case you built MonetDB from cvs sources, please update to the latest code version from the latest "Stable" release branches:
buildtools: MonetDB_1-24
MonetDB: MonetDB_1-24
clients: Clients_1-24
MonetDB5: MonetDB_5-6
sql: SQL_2-24
2)
In case you built MonetDB using the "monetdb-install.sh" script, rerun the script with
`monetdb-install.sh --enable-sql --nightly=stable`
3)
In case you built MonetDB "by hand" from the individual tarballs, please get their latest "Stable" versions from
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/.DailyBuilds./0_latest/SourceTarBalls/
## Comment 10008
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2041785 at http://sourceforge.net/support/tracker.php?aid=2041785
| range join exception | https://api.github.com/repos/MonetDB/MonetDB/issues/1776/comments | 0 | 2020-11-30T10:00:03Z | 2024-06-27T11:31:45Z | https://github.com/MonetDB/MonetDB/issues/1776 | 753,333,189 | 1,776 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-05 03:42:38 +0200
From: Henning Rode <<hrode>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-10-11 01:16:26 +0200
## Comment 9990
Date: 2008-08-05 15:42:38 +0200
From: Henning Rode <<hrode>>
the following xquery constantly fails on my system.
xquery:
let $rscs := doc("c.xml")//resource
for $c in $rscs//concept
return <concept score="{$c//score/text()}">{$c/text()}</concept>
output:
.
.
.
<concept score="0.0844787">sports</concept>,
<concept score="0.0836574">face</concept>,
<concept score="0.032173">soccer</concept>,
<concept score="0.021382">grass</concept>,
<concept!ERROR: XML Generation: tmp_6313 BAT does not have a 73530 head.
MAPI = monetdb@localhost:50000
QUERY = let $rscs := doc("/export/scratch0/henning/c.xml")//resource
ERROR = !ERROR:
!ERROR: XML Generation: NULL BAT has a 73530 head, but tail is NULL.
!ERROR:
!ERROR: xquery_print_result_main: operation failed.
strange enough, it works fine on smaller instances of c.xml (if i only use half of the data for instance). the complete document c.xml is about 16MB (1MB compressed) and i can provide it for testing.
## Comment 9991
Date: 2008-08-05 15:47:03 +0200
From: Henning Rode <<hrode>>
Logged In: YES
user_id=909189
Originator: YES
I tested also to remove either the score attribute construction or the element content construction. In both cases the error does *not* occur.
## Comment 9992
Date: 2008-08-05 16:17:34 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Assuming that you used the (default) "Algebra" back-end, did you by any chance also try the (old) "milprint_summer" back-end?
If so, what was the effect?
If not, could you please try (simply run your query with `mclient -lx -g`), and report on the effect?
## Comment 9993
Date: 2008-08-05 16:25:43 +0200
From: Henning Rode <<hrode>>
Logged In: YES
user_id=909189
Originator: YES
yes, I tested the MPS back-end as well, and also there it works fine.
## Comment 9994
Date: 2008-08-05 16:28:42 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Might be a bug in the element construction in the Algebra back-end --- assigning to Jan R.
## Comment 9995
Date: 2008-08-06 12:10:54 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
It turned out to be an overflow in ds_link() (which the twig construction uses for the correct handling of attributes). As soon as more than 65536 results (should) appear ds_link() produces garbage.
print(a0000.slice(0,10), a0008);
-------------------------
h t t name
void oid oid type
-------------------------
[ 0@0, 1@0, 0@0 ]
[ 1@0, 2@0, 0@0 ]
[ 2@0, 3@0, 0@0 ]
[ 3@0, 4@0, 0@0 ]
[ 4@0, 5@0, 0@0 ]
[ 5@0, 6@0, 0@0 ]
[ 6@0, 7@0, 0@0 ]
[ 7@0, 8@0, 0@0 ]
[ 8@0, 9@0, 0@0 ]
[ 9@0, 10@0, 0@0 ]
[ 10@0, 11@0, 0@0 ]
print(a0007.fetch(0).slice(0,20), a0007.fetch(1));
-------------------------
h t t name
void oid oid type
-------------------------
[ 0@0, 1@0, 0@0 ]
[ 1@0, 1@0, 1@0 ]
[ 2@0, 2@0, 0@0 ]
[ 3@0, 2@0, 1@0 ]
[ 4@0, 3@0, 0@0 ]
[ 5@0, 3@0, 1@0 ]
[ 6@0, 4@0, 0@0 ]
[ 7@0, 4@0, 1@0 ]
[ 8@0, 5@0, 0@0 ]
[ 9@0, 5@0, 1@0 ]
[ 10@0, 6@0, 0@0 ]
[ 11@0, 6@0, 1@0 ]
[ 12@0, 7@0, 0@0 ]
[ 13@0, 7@0, 1@0 ]
[ 14@0, 8@0, 0@0 ]
[ 15@0, 8@0, 1@0 ]
[ 16@0, 9@0, 0@0 ]
[ 17@0, 9@0, 1@0 ]
[ 18@0, 10@0, 0@0 ]
[ 19@0, 10@0, 1@0 ]
[ 20@0, 11@0, 0@0 ]
a0016 := ds_link (a0000.slice(0,10), a0007.fetch (0).slice(0,20), a0008.slice(0,10), a0007.fetch (1).slice(0,20));
print (a0016.count());
[ 11 ]
a0016 := ds_link (a0000.slice(0,65000), a0007.fetch (0).slice(0,130000), a0008.slice(0,65000), a0007.fetch (1).slice(0,130000));
print (a0016.count());
[ 65001 ]
a0016 := ds_link (a0000.slice(0,70000), a0007.fetch (0).slice(0,140000), a0008.slice(0,70000), a0007.fetch (1).slice(0,140000));
print (a0016.count());
[ 78931 ]
a0016 := ds_link (a0000, a0007.fetch (0), a0008, a0007.fetch (1));
print (a0016.count());
[ 168899 ]
## Comment 9996
Date: 2008-08-24 17:21:24 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
*might* be related to
[ 2071638 ] mclient output is limited?
http://sourceforge.net/tracker/index.php?func=detail&aid=2071638&group_id=56967&atid=482468
## Comment 9997
Date: 2008-09-05 10:58:29 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
It seems Stefan fixed the related http://sourceforge.net/support/tracker.php?aid=2071638. Henning could you verify if your problem here is fixed as well.
## Comment 9998
Date: 2008-09-05 11:25:52 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Jan, Henning,
the (maybe not that) related
http://sourceforge.net/tracker/index.php?func=detail&aid=2071638&group_id=56967&atid=482468
just works for me.
I have not yet been able to locate the problem in ds_link() reported here.
Of course, a double-check is always welcome...
Stefan
## Comment 9999
Date: 2008-09-05 11:45:23 +0200
From: Henning Rode <<hrode>>
Logged In: YES
user_id=909189
Originator: YES
i told it stefan already, but just to keep it recorded here... the bug is not yet solved. i still get the exactly same error.
-henning
## Comment 10000
Date: 2008-10-09 10:43:08 +0200
From: @drstmane
Henning,
could you provide me with (access to) you "c.xml" to reproduce, locate and hopefully fix this bug?
Thanks!
Stefan
## Comment 10001
Date: 2008-10-11 12:34:55 +0200
From: @drstmane
fixed in CVS:
there was a major design flaw in the false-hit removal in module mkey's ds_link() MIL proc
(
could not port fix to M5, as the ds_link MIL proc
apparently has not been ported/propagated to C code in
MonetDB5/src/modules/kernel/mkey.mx
)
THANKS to Jan for the detailed analysis to locate the origin of this bug!
Still need to adjust / trim-down Hennings test case to turn it into a suitable test.
## Comment 10002
Date: 2008-10-11 13:16:26 +0200
From: @drstmane
Test added in pathfinder/tests/BugTracker/Tests/XML_attribute_generation.SF-2038906*
## Comment 10003
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2038906 at http://sourceforge.net/support/tracker.php?aid=2038906
| XML attribute generation | https://api.github.com/repos/MonetDB/MonetDB/issues/1775/comments | 0 | 2020-11-30T10:00:00Z | 2024-06-27T11:31:44Z | https://github.com/MonetDB/MonetDB/issues/1775 | 753,333,155 | 1,775 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-05 11:33:20 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2008-08-08 04:36:54 +0200
## Comment 9987
Date: 2008-08-05 11:33:20 +0200
From: @drstmane
With warnings being treated as error, the pathfinder runtime fails to compile on Windows:
========
serialize.c
.\..\..\runtime\serialize.mx(2090): error 1740: dllexport/dllimport conflict with "xrpc_log_dir" (declared at line 5858 of ".\..\..\runtime\pf_support.mx"); dllexport assumed
xrpc_log_dir() {
^
.\..\..\runtime\serialize.mx(2105): error 1740: dllexport/dllimport conflict with "xrpc_log_message" (declared at line 5857 of ".\..\..\runtime\pf_support.mx"); dllexport assumed
xrpc_log_message(str msg, lng xrpc_seqnr) {
^
.\..\..\runtime\serialize.mx(2581): error 1740: dllexport/dllimport conflict with "CMDfn_deep_eq" (declared at line 70 of ".\pf_support.proto.h"); dllexport assumed
CMDfn_deep_eq(BAT** resbat, BAT* ws, BAT* litem, BAT* lkind, BAT* ritem, BAT* rkind)
^
compilation aborted for serialize.c (code 2)
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Intel\Compiler\C++\10.1.013\EM64T\Bin\icl.EXE"' : return code '0x2'
========
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.Int.32.32.d.1-Windows5.1..2008.08.05_00-09-01/make.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.Int.64.64.d.1-Windows5.2..2008.08.05_00-09-01/make.out.html
In fact, (at least) to me the "design" of the runtime's code base, in particular with respect to which source file (code and/or header) and/or library implements/exports which function and which one imports/uses which function has (with all due respect) become "quite a mess", including cyclic dependencies among header files and libraries.
Unixes seem to be quite "forgiving" with this, but Windows (correctly?) is not.
A proper solution asks for a clean and proper "design" of the runtime code base (at least wrt. providing/using functions) ...
## Comment 9988
Date: 2008-08-08 16:36:54 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
The import/export issues have been fixed.
## Comment 9989
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2038665 at http://sourceforge.net/support/tracker.php?aid=2038665
| PF: runtime fails to compile on Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/1774/comments | 0 | 2020-11-30T09:59:57Z | 2024-06-27T11:31:43Z | https://github.com/MonetDB/MonetDB/issues/1774 | 753,333,109 | 1,774 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-04 12:44:35 +0200
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2008-08-05 01:49:25 +0200
## Comment 9984
Date: 2008-08-04 12:44:35 +0200
From: @drstmane
Being designed to return values of type int (i.e., signed 32-bit integers), bbp.getDiskSpace() fails on databases of >= 2GB (occupied disk space) with
.../MonetDB5/src/modules/mal/bbp.mx:788: CMDbbpDiskSpace: Assertion `(-2147483647 - 1) <= s && s <= 2147483647' failed.
$ mserver5 --dbname=TPC-H.SF-10
MonetDB server v5.7.0, based on kernel v1.25.0
Serving database 'TPC-H.SF-10'
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked using 4 threads
Copyright (c) 1993-2008 CWI, all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
>a := bbp.getDiskSpace();
mserver5: /ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/bbp.mx:788: CMDbbpDiskSpace: Assertion `(-2147483647 - 1) <= s && s <= 2147483647' failed.
Aborted
## Comment 9985
Date: 2008-08-05 01:49:06 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
resolved by using a larger data type to hold the result.
Needs no test.
## Comment 9986
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2037489 at http://sourceforge.net/support/tracker.php?aid=2037489
| M5: bbp.getDiskSpace() triggers assertion on database >= 2GB | https://api.github.com/repos/MonetDB/MonetDB/issues/1773/comments | 0 | 2020-11-30T09:59:55Z | 2024-06-27T11:31:42Z | https://github.com/MonetDB/MonetDB/issues/1773 | 753,333,070 | 1,773 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-01 06:27:40 +0200
From: @yzchang
To: @sjoerdmullender
Version: -- development
Last updated: 2008-08-02 10:30:49 +0200
## Comment 9981
Date: 2008-08-01 18:27:40 +0200
From: @yzchang
In XQuery tests that import module files, the environment variables $TSTSRCBASE, $TSTSRCDIR are often used to dynamically specify the location of the module files. When substituting these variables with their values, Mtest escapes the '\' characters in the path on Windows. This is incorrect, since '\' is a normal character in XML/XQuery, and thus should not be escaped.
## Comment 9982
Date: 2008-08-02 10:30:49 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Too late: this has already been fixed.
But thanks for the reminder.
## Comment 9983
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2035049 at http://sourceforge.net/support/tracker.php?aid=2035049
| Mtest incorrectly escape '\' in XQ mod. locations on Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/1772/comments | 0 | 2020-11-30T09:59:52Z | 2024-06-27T11:31:41Z | https://github.com/MonetDB/MonetDB/issues/1772 | 753,333,032 | 1,772 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-29 08:28:11 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-07-30 11:20:54 +0200
## Comment 9978
Date: 2008-07-29 08:28:11 +0200
From: @drstmane
With the new overflow checks for down-casts, several tests now fail with
.../MonetDB4/src/modules/plain/mkey.mx:466: CMDbulk_rotate_xor_hash: Assertion `val <= 2147483647' failed.
Cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_W3C_use_cases_XQ_NS/Q7.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests4103/GNU.64.64.d.1-Fedora8/src_test_VOC/VOC.err.00.html
## Comment 9979
Date: 2008-07-30 11:20:54 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
fixed:
instead of triggering an assertion when 64-bit hash values are shrunk to 32-bit
(or silently ignoring the top 32 bits as we used to do before),
we now XOR (^) the higher and lower 32 bit of a 64-bit hash value to get a 32-bit hash values
(just as we do in various other places).
## Comment 9980
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2031040 at http://sourceforge.net/support/tracker.php?aid=2031040
| M4: XQuery & SQL tests assert in CMDbulk_rotate_xor_hash() | https://api.github.com/repos/MonetDB/MonetDB/issues/1771/comments | 0 | 2020-11-30T09:59:50Z | 2024-06-27T11:31:40Z | https://github.com/MonetDB/MonetDB/issues/1771 | 753,333,005 | 1,771 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-29 08:20:17 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-07-30 11:21:15 +0200
## Comment 9975
Date: 2008-07-29 08:20:17 +0200
From: @drstmane
With the new overflow checks for down-casts, several tests now fail with
.../MonetDB4/src/modules/plain/mkey.mx:358: CMDhash_str: Assertion `h <= 2147483647' failed.
Cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_W3C_use_cases_XQ_R/Q17.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests4103/GNU.64.64.d.1-Fedora8/src_benchmarks_ATIS/load.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests4103/GNU.64.64.d.1-Fedora8/src_test_ADT2006/bram.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests4103/GNU.64.64.d.1-Fedora8/src_test_BugDay_2005-10-06_2.9.3/sesamstr_parser_error.SF-993366.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests4103/GNU.64.64.d.1-Fedora8/src_test_BugTracker/full_join_crash.SF-1841754.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests4103/GNU.64.64.d.1-Fedora8/src_test_Skyserver/Skyserver.err.00.html
## Comment 9976
Date: 2008-07-30 11:21:15 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
fixed:
instead of triggering an assertion when 64-bit hash values are shrunk to 32-bit
(or silently ignoring the top 32 bits as we used to do before),
we now XOR (^) the higher and lower 32 bit of a 64-bit hash value to get a 32-bit hash values
(just as we do in various other places).
## Comment 9977
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2031030 at http://sourceforge.net/support/tracker.php?aid=2031030
| M4: XQuery & SQL tests trigger assertion in CMDhash_str() | https://api.github.com/repos/MonetDB/MonetDB/issues/1770/comments | 0 | 2020-11-30T09:59:48Z | 2024-06-27T11:31:39Z | https://github.com/MonetDB/MonetDB/issues/1770 | 753,332,969 | 1,770 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-28 10:58:50 +0200
From: @drstmane
To: MonetDB4 devs <<bugs-monetdb4>>
Version: -- development
Last updated: 2008-08-02 11:06:00 +0200
## Comment 9972
Date: 2008-07-28 22:58:50 +0200
From: @drstmane
A first "victim" of the new overflow checks with down-casts:
test geom/src/sql/Tests/geom_mbr.sql fails with
mserver5: .../geom/src/monetdb5/geom.mx:497: mbrWRITE: Assertion `(-2147483647 - 1) <= c->xmin && c->xmin <= 2147483647' failed.
Cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/geom/.mTests5103/GNU.64.64.d.1-Fedora8/src_sql/geom_mbr.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/geom/.mTests4103/GNU.64.64.d.1-Fedora8/src_sql/geom_mbr.err.00.html
## Comment 9973
Date: 2008-08-02 23:06:00 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
We use writeInt to write (binary) floats values of the mbr. Also mbr(nil) is valid ie we should also write float(nil). So no need to check for overflow in the fields is needed.
## Comment 9974
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2030696 at http://sourceforge.net/support/tracker.php?aid=2030696
Unknown Product GEOM
Using default product set in Parameters
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-monetdb4@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| Geom: test src/sql/Tests/geom_mbr.sql triggers assertion | https://api.github.com/repos/MonetDB/MonetDB/issues/1769/comments | 0 | 2020-11-30T09:59:45Z | 2024-06-27T11:31:39Z | https://github.com/MonetDB/MonetDB/issues/1769 | 753,332,940 | 1,769 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-28 07:20:58 +0200
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2008-07-30 12:19:57 +0200
## Comment 9969
Date: 2008-07-28 07:20:58 +0200
From: @drstmane
Calling ceil() and floor() on integer values --- e.g., in functions findQuantHisto() and BPMsplitquant() in src/modules/mal/bpm.mx --- does not make much sense.
For details, see `man ceil`, `man floor` and
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.Mic.32.32.d.1-Windows5.1..2008.07.28_00-09-02/make.out.htmle3
## Comment 9970
Date: 2008-07-30 12:19:57 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Properly casted the arguments
## Comment 9971
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2030011 at http://sourceforge.net/support/tracker.php?aid=2030011
| M5: ceil() and floor() have no effect on integer values | https://api.github.com/repos/MonetDB/MonetDB/issues/1768/comments | 0 | 2020-11-30T09:59:43Z | 2024-06-27T11:31:37Z | https://github.com/MonetDB/MonetDB/issues/1768 | 753,332,917 | 1,768 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-25 04:10:07 +0200
From: @yzchang
To: @sjoerdmullender
Version: -- development
Last updated: 2008-08-01 06:11:13 +0200
## Comment 9964
Date: 2008-07-25 16:10:07 +0200
From: @yzchang
The following MIL commands cause Mserver to crash, when freeing the yytree:
$ cat bugje.mil
var a := nil;
var b;
b := "some text...";
if(and(not(isnil(a)), a != "")) print(a);
$ Mserver bugje.mil
MonetDB Server v4.24.1
based on GDK v1.24.1
Copyright (c) 1993-2008, CWI. All rights reserved.
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
!ERROR: interpret: no matching MIL operator to '!=(void, str)'.
!MAYBE YOU MEAN:
! !=(str, str) : bit
! !=(lng, lng) : bit
! !=(dbl, dbl) : bit
! !=(flt, flt) : bit
! !=(wrd, wrd) : bit
! !=(oid, oid) : bit
! !=(int, int) : bit
! !=(sht, sht) : bit
! !=(bte, bte) : bit
! !=(chr, chr) : bit
! !=(bit, bit) : bit
! !=(any::1, any::1) : bit
!ERROR: interpret_params: and(param 2): evaluation error.
!ERROR: BATSIGcrash: Mserver internal error (Segmentation fault), please restart.
!ERROR: (One potential cause could be that your disk might be full...)
Note that, the crash is only caused by the combination of the conditions: i) variable a is nil, ii) variable b is not initialized immediately, and iii) function and() is used. If one of the conditions doesn't hold, Mserver behaves correctly.
Jennie
## Comment 9965
Date: 2008-07-25 17:29:49 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Jennie,
did you by any chance run this in gdb to see where (and why) the crash happens?
## Comment 9966
Date: 2008-07-25 18:13:44 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
appears to be some double-free in yytree.
see attached log for details.
File Added: bugje.gdb.log
## Comment 9967
Date: 2008-08-01 18:11:13 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Fixed in stable in MonetDB4/src/monet/monet_interpreter.mx, revision 1.17.2.1.
Added test as MonetDB4/tests/BugTracker/cleanup_crash.SF-2027870
## Comment 9968
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2027870 at http://sourceforge.net/support/tracker.php?aid=2027870
| MIL: nil-value variable crashes Mserver | https://api.github.com/repos/MonetDB/MonetDB/issues/1767/comments | 0 | 2020-11-30T09:59:40Z | 2024-06-27T11:31:37Z | https://github.com/MonetDB/MonetDB/issues/1767 | 753,332,887 | 1,767 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-25 08:28:38 +0200
From: @drstmane
To: Marco Antonelli <<marcoantonelli>>
Version: -- development
Last updated: 2008-07-25 11:22:02 +0200
## Comment 9960
Date: 2008-07-25 08:28:38 +0200
From: @drstmane
See
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.GNU.32.32.d.1-Fedora9..2008.07.25_00-09-02/make.out.html
for details.
cc1: warnings being treated as errors
/export/scratch0/monet/monet.GNU.32.32.d.1.25058/MonetDB5/src/modules/mal/rdf.mx: In function 'rdf_datetime_toString':
/export/scratch0/monet/monet.GNU.32.32.d.1.25058/MonetDB5/src/modules/mal/rdf.mx:669: error: large integer implicitly truncated to unsigned type
/export/scratch0/monet/monet.GNU.32.32.d.1.25058/MonetDB5/src/modules/mal/rdf.mx: In function 'rdf_datetime_fromString':
/export/scratch0/monet/monet.GNU.32.32.d.1.25058/MonetDB5/src/modules/mal/rdf.mx:683: error: large integer implicitly truncated to unsigned type
## Comment 9961
Date: 2008-07-25 09:12:35 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Hints:
Use of type "(unsigned) long" is not reccommended as it is not well portable: On Unix the size (usually) follows the system architecture (32-bit on 32-bit systems; 64-bit on 64-bit systems) while on Windows it is fix to either 32-bit or 64-bit (I don't recall which one right now) regardless of the system architecture.
Instead use type
- "(unsigned) int" if you know that 32-bit is big enough;
- "(unsigned) long long" (or better: "lng" (signed) with MonetDB) if you need 64-bit (though "long long" is not that portable either; might be called "__int64" on some systems);
- "(s)size_t" if you need a type that follows the system architecture, i.e. 32-bit on 32-bit systems 64-bit on 64-bit systems.
## Comment 9962
Date: 2008-07-25 11:22:02 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed by Marco & Stefan.
## Comment 9963
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2027508 at http://sourceforge.net/support/tracker.php?aid=2027508
| M5: module rdf fails to compile on 32-bit systems | https://api.github.com/repos/MonetDB/MonetDB/issues/1766/comments | 0 | 2020-11-30T09:59:38Z | 2024-06-27T11:31:36Z | https://github.com/MonetDB/MonetDB/issues/1766 | 753,332,862 | 1,766 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-25 06:56:46 +0200
From: @drstmane
To: Marco Antonelli <<marcoantonelli>>
Version: -- development
Last updated: 2008-07-25 11:21:37 +0200
## Comment 9957
Date: 2008-07-25 06:56:46 +0200
From: @drstmane
Compiling modules rdf fails with Intel's icc;
see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.Int.64.64.d.1-Fedora8..2008.07.25_00-09-02/make.out.html
for details.
/scratch/monet.Int.64.64.d.1.25058/MonetDB5/src/modules/mal/rdf.mx(234): error 188: enumerated type mixed with another type
ret = (oid) bun;
^
/scratch/monet.Int.64.64.d.1.25058/MonetDB5/src/modules/mal/rdf.mx(1026): error 181: argument is incompatible with corresponding format string conversion
written = snprintf(msg, RET_MAXLEN, "In URI location \"%s\": ", raptor_uri_as_string(locator->uri));
^
/scratch/monet.Int.64.64.d.1.25058/MonetDB5/src/modules/mal/rdf.mx(1179): error 181: argument is incompatible with corresponding format string conversion
(str)triple->object, triple->object_literal_language, obj_datatype);
^
/scratch/monet.Int.64.64.d.1.25058/MonetDB5/src/modules/mal/rdf.mx(1092): error 181: argument is incompatible with corresponding format string conversion
snprintf(langPrefixedObject, len, "%s@%s", triple->object_literal_language, (str)triple->object);
^
/scratch/monet.Int.64.64.d.1.25058/MonetDB5/src/modules/mal/rdf.mx(2023): error 188: enumerated type mixed with another type
rdf_section subj_sec = sv[0];
^
/scratch/monet.Int.64.64.d.1.25058/MonetDB5/src/modules/mal/rdf.mx(2024): error 188: enumerated type mixed with another type
rdf_section prop_sec = pv[0];
^
/scratch/monet.Int.64.64.d.1.25058/MonetDB5/src/modules/mal/rdf.mx(2025): error 188: enumerated type mixed with another type
rdf_section obj_sec = ov[0];
^
/scratch/monet.Int.64.64.d.1.25058/MonetDB5/src/modules/mal/rdf.mx(2026): error 188: enumerated type mixed with another type
rdf_type obj_type = tv;
^
compilation aborted for rdf.c (code 2)
make[8]: *** [lib_rdf_la-rdf.lo] Error 1
## Comment 9958
Date: 2008-07-25 11:21:37 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed by Marco & Stefan.
## Comment 9959
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2027470 at http://sourceforge.net/support/tracker.php?aid=2027470
| M5: module rdf fails to compile with icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1765/comments | 0 | 2020-11-30T09:59:36Z | 2024-06-27T11:31:35Z | https://github.com/MonetDB/MonetDB/issues/1765 | 753,332,833 | 1,765 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-25 06:54:38 +0200
From: @drstmane
To: Marco Antonelli <<marcoantonelli>>
Version: -- development
Last updated: 2008-07-25 11:21:50 +0200
## Comment 9954
Date: 2008-07-25 06:54:38 +0200
From: @drstmane
When configured with --disable-debug and/or --enable-optimize, compiling modules rdf fails with GNU's gcc;
see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.GNU.64.64.d.0-Fedora8..2008.07.25_00-09-02/make.out.html
for details.
cc1: warnings being treated as errors
/scratch/monet.GNU.64.64.d.0.25058/MonetDB5/src/modules/mal/rdf.mx: In function 'rdf_datetime_fromString':
/scratch/monet.GNU.64.64.d.0.25058/MonetDB5/src/modules/mal/rdf.mx:709: warning: dereferencing type-punned pointer will break strict-aliasing rules
/scratch/monet.GNU.64.64.d.0.25058/MonetDB5/src/modules/mal/rdf.mx: In function 'RDFdoubleToHexString':
/scratch/monet.GNU.64.64.d.0.25058/MonetDB5/src/modules/mal/rdf.mx:719: warning: dereferencing type-punned pointer will break strict-aliasing rules
/scratch/monet.GNU.64.64.d.0.25058/MonetDB5/src/modules/mal/rdf.mx: In function 'RDFhexStringToDouble':
/scratch/monet.GNU.64.64.d.0.25058/MonetDB5/src/modules/mal/rdf.mx:745: warning: dereferencing type-punned pointer will break strict-aliasing rules
make[8]: *** [lib_rdf_la-rdf.lo] Error 1
## Comment 9955
Date: 2008-07-25 11:21:50 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed by Marco & Stefan.
## Comment 9956
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2027467 at http://sourceforge.net/support/tracker.php?aid=2027467
| M5: module rdf fails to compile with gcc (and optimization) | https://api.github.com/repos/MonetDB/MonetDB/issues/1764/comments | 0 | 2020-11-30T09:59:33Z | 2024-06-27T11:31:34Z | https://github.com/MonetDB/MonetDB/issues/1764 | 753,332,801 | 1,764 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-18 04:09:49 +0200
From: @mlkersten
To: @njnes
Version: -- development
Last updated: 2008-07-21 11:33:12 +0200
## Comment 9951
Date: 2008-07-18 16:09:49 +0200
From: @mlkersten
The following script produces a type error
while it can be evaluated using a cross product.
create table s1 (id int, v char(10));
create table s2 (id int, v char(10));
insert into s1 values (1,'s1');
insert into s1 values (2,'s2');
insert into s1 values (3,'s3');
insert into s1 values (4,'s4');
insert into s1 values (5,'s5');
insert into s1 values (6,'s6');
insert into s2 values (1,'s1');
insert into s2 values (2,'s2');
insert into s2 values (3,'s3');
insert into s2 values (4,'s4');
insert into s2 values (5,'s5');
insert into s2 values (6,'s6');
select s1.id from s1, s2 where s1.v between s2.v and s2.v||'c' ;
## Comment 9952
Date: 2008-07-21 11:33:12 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
missing implementation is added to MonetDB/src/gdk/gdk_rangejoin.mx
also a test is added to sql/src/tests/BugTracker/Tests/between_on_strings.SF-2021508.sql
## Comment 9953
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2021508 at http://sourceforge.net/support/tracker.php?aid=2021508
| SQL: thetajoin limitation | https://api.github.com/repos/MonetDB/MonetDB/issues/1763/comments | 0 | 2020-11-30T09:59:30Z | 2024-06-27T11:31:33Z | https://github.com/MonetDB/MonetDB/issues/1763 | 753,332,768 | 1,763 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-18 03:43:40 +0200
From: @mlkersten
To: @njnes
Version: -- development
Last updated: 2008-07-21 09:27:59 +0200
## Comment 9948
Date: 2008-07-18 15:43:40 +0200
From: @mlkersten
include sql;
sql.init(); -- and likewise sql.start2()
followed by the instruction
sql.eval("select 1;");
gives a system crash on stream_write
called from mvc_export_value
## Comment 9949
Date: 2008-07-21 21:27:59 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
sql.eval wasn't designed for this usage. Fixed this now.
## Comment 9950
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2021499 at http://sourceforge.net/support/tracker.php?aid=2021499
| SQL: initialization for MAL fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1762/comments | 0 | 2020-11-30T09:59:27Z | 2024-06-27T11:31:32Z | https://github.com/MonetDB/MonetDB/issues/1762 | 753,332,724 | 1,762 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-17 04:00:33 +0200
From: Andreas Meinl <<andreasmeinl>>
To: Jens Teubner <<teubner>>
Version: -- development
Last updated: 2009-02-17 12:56:46 +0100
## Comment 9940
Date: 2008-07-17 16:00:33 +0200
From: Andreas Meinl <<andreasmeinl>>
Hi there,
this XQuery works fine for example in eXist and Sedna:
<average> {
fn:round(fn:avg(
fn:collection("samples")/example/@sum
)) } </average>
I expect the adapted XQuery to show the same result in MonetDB/XQuery:
<average> {
fn:round(fn:avg(
pf:collection("samples")/child::document-node()/example/@sum
)) } </average>
But unfortunately I get this error message:
MAPI = monetdb@localhost:50000
QUERY = <average> {
ERROR = !parse error: syntax error, unexpected /, expecting QName on line 4, column 9 (next token is `/')
!parse error: XQuery parsing failed
Modified in the following way this XQuery works as well in MonetDB/XQuery:
let $avg := pf:collection("samples")/child::document-node()/example/@sum
return <average> {
fn:round(fn:avg(
$avg
)) } </average>
So why is pf:collection just working outside the "<average>" element, but not inside?
I filled in this bug report as a result of this thread:
http://sourceforge.net/mailarchive/forum.php?thread_name=FA0CC246-7F48-43A5-A8DC-89760281FEB8%40andreasmeinl.de&forum_name=monetdb-users
Regards,
Andreas Meinl
## Comment 9941
Date: 2008-07-17 18:39:20 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
I checked in a fix in the scanner. The state pushing and popping was out of sync.
As this was my first time touching the scanner -- Jens could you please double-check whether I broke something.
@Andreas: I would use node() instead of document-node() -- this already works and requires no kind test at all.
## Comment 9942
Date: 2008-08-12 16:09:08 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
What is the status of this fix? Can we close the bug report?
## Comment 9943
Date: 2008-08-27 03:29:38 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Originator: NO
There still seems to be a problem with this. Consider, e.g.,
let $x as document(element())* := foo() return 42
which our parser reports as syntactically incorrect.
Don't have a fix, yet...
## Comment 9944
Date: 2009-02-16 16:48:08 +0100
From: @drstmane
re-opened to remind us that we should consider adding a test
## Comment 9945
Date: 2009-02-17 00:56:46 +0100
From: @drstmane
added test in pathfinder/tests/BugTracker/Tests/Parse_error_with_pf:collection.SF-2020631.*
appears to work fine.
## Comment 9946
Date: 2009-03-15 10:52:42 +0100
From: @drstmane
fails with BATpropcheck error:
[ 2627137 ] PF: tests fail with BATpropcheck error
https://sourceforge.net/tracker/index.php?func=detail&aid=2627137&group_id=56967&atid=482468
(
don't know since/for how long, since they were not detected for some time; cf.,
[ 2607229 ] testing does not report detected property errors
https://sourceforge.net/tracker/index.php?func=detail&aid=2607229&group_id=56967&atid=482468
)
## Comment 9947
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2020631 at http://sourceforge.net/support/tracker.php?aid=2020631
| Parse error with pf:collection | https://api.github.com/repos/MonetDB/MonetDB/issues/1761/comments | 0 | 2020-11-30T09:59:24Z | 2024-06-27T11:31:31Z | https://github.com/MonetDB/MonetDB/issues/1761 | 753,332,685 | 1,761 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-17 07:33:18 +0200
From: @drstmane
To: @yzchang
Version: -- development
Last updated: 2008-07-18 07:40:04 +0200
## Comment 9935
Date: 2008-07-17 07:33:18 +0200
From: @drstmane
pathfinder/runtime fails to link on Darwin (MacOS X):
========
[...]
ld: multiple definitions of symbol _xrpc_admin
.libs/lib_xrpc_client_la-xrpc_client.o definition of _xrpc_admin in section (__DATA,__common)
./.libs/libserialize.a(libserialize_la-serialize_dflt.o) definition of _xrpc_admin in section (__DATA,__common)
./.libs/libxrpc_common.a(libxrpc_common_la-xrpc_common.o) definition of _xrpc_admin in section (__DATA,__common)
[...]
/usr/bin/libtool: internal link edit command failed
make[4]: *** [lib_xrpc_client.la] Error 1
========
see also
http://www.ins.cwi.nl/~monet/permastore/2008-07-17/Current/make-pathfinder-GNU.32.32.d-Darwin8.11.0.errors.htmll333
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.GNU.32.32.d-Darwin8.11.0..2008.07.17_00-09-01/make.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.GNU.32.32.d-Darwin8.11.0..2008.07.17_00-09-01/make-k.out.html
The reason seems to be that --- in contrast to, e.g., the "sloppy" GNU/gcc linker on Linux --- the linker on Darwin (correctly) does not like to link together object files that all (independendtly!) define the same (supposed to be shared??) global variables.
In fact, I do not know, whether the BAT* xrpc_* variables defined in xrpc_common.mx's .h file --- and hence in each .o file whos .c file includes the xrpc_common.h --- just "happen to have" the same name in each of these .o files, or whether they are supposed to be shared among them.
I also don't know, how the linker on Linux handles/solves (if at all) this conflict.
In case these variables are supposed to be shared, you might want to define them in one .c/.o file, only (say xrpc_common.c) and declare them "extern" in all other .c/o. files that share them (e.g., by having these include the xrpc.common.h and putting the extern declaration there).
In fact, the "extern" should of course be a proper export/import declaration to also work on Windows...
## Comment 9936
Date: 2008-07-17 08:15:50 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
A simple analysis reveals each of the BAT* xrpc_* variables from xrpc_common.h is used in either xrpc_server.c or xrpc_client.c, only; hence, I would suggest to define those variables also only in the very .c that actually uses them.
Why make the code more "complicated" (and hence error-prone) than necessary...?
## Comment 9937
Date: 2008-07-17 08:19:06 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
In fact, some (most?) of these variable might not be used at all.
Please check carefully!
## Comment 9938
Date: 2008-07-18 07:40:04 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed by Jennie.
Thanks.
## Comment 9939
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2020269 at http://sourceforge.net/support/tracker.php?aid=2020269
| PF/runtime fails to link on Darwin (MacOS X) | https://api.github.com/repos/MonetDB/MonetDB/issues/1760/comments | 0 | 2020-11-30T09:59:20Z | 2024-06-27T11:31:30Z | https://github.com/MonetDB/MonetDB/issues/1760 | 753,332,636 | 1,760 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-16 11:52:50 +0200
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-07-21 06:54:52 +0200
## Comment 9929
Date: 2008-07-16 11:52:50 +0200
From: @romulogoncalves
This bug only occurs in the current branch and for mclient -G.
If you run the following sql code you will crash mserver:
create table prop1 (subj int, obj int, prop int);
create table prop2 (subj int, obj int, prop int);
explain WITH A(subj, obj) as (SELECT * FROM prop1 where obj = 14660332)
SELECT prop, obj, cnt from (
( SELECT 'prop14657240_pso' as prop, B.obj, count(*) as cnt
FROM A, prop2 as B
WHERE A.subj = B.subj
GROUP BY B.obj HAVING count(*) > 1
)
) as trip;
drop table prop1;
drop table prop2;
Some debug information:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1107310928 (LWP 32432)]
0x00002aaabe74dddc in sql_ref_dec (r=0x21)
at /ufs/goncalve/MonetDB/current/sql/src/common/sql_mem.mx:50
50 assert(r->refcnt > 0);
Missing separate debuginfos, use: debuginfo-install bzip2.x86_64 e2fsprogs.x86_64 glibc.x86_64 keyutils.x86_64 krb5.x86_64 libselinux.x86_64 ncurses.x86_64 openssl.x86_64 pcre.x86_64 readline.x86_64 zlib.x86_64
(gdb) up
1 0x00002aaabe6bf89e in stmt_destroy (s=0x21)
at /ufs/goncalve/MonetDB/current/sql/src/server/sql_statement.mx:634
634 if (sql_ref_dec(&s->ref) == 0) {
(gdb) up
2 0x00002aaabe6bfd23 in stmt_destroy (s=0xde9db8)
at /ufs/goncalve/MonetDB/current/sql/src/server/sql_statement.mx:810
810 stmt_destroy(s->t);
(gdb) bt
## Comment 9930
Date: 2008-07-21 09:51:14 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
fixed in stable. Incorrectly used stmt_destroy (exp's != stmt). Also we now return an error on not matching column lists.
## Comment 9931
Date: 2008-07-21 12:10:47 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
The test was added at:
sql/src/test/BugTracker/Tests/assert_fails_on_algebra_version.SF-2019349
## Comment 9932
Date: 2008-07-21 12:17:37 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
The problem is not resolved. If we change the table prop1 definition (remove column prop):
create table prop1 (subj int, obj int);
The mserver will not give the error:
Column lists do not match
Instead of that it will crash (now the problem is seen on stable and current branch):
Program received signal SIGABRT, Aborted.
[Switching to Thread 1107310928 (LWP 19310)]
0x0000003c6d030ec5 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install bzip2.x86_64 e2fsprogs.x86_64 glibc.x86_64 keyutils.x86_64 krb5.x86_64 libselinux.x86_64 ncurses.x86_64 openssl.x86_64 pcre.x86_64 readline.x86_64 zlib.x86_64
(gdb) up
1 0x0000003c6d032970 in abort () from /lib64/libc.so.6
(gdb) up
2 0x0000003c6d02a11f in __assert_fail () from /lib64/libc.so.6
(gdb) up
3 0x00002aaabed042db in set2pivot (c=0x1043ff8, l=0xde58a8)
at /ufs/goncalve/MonetDB/stable/sql/src/server/sql_optimize.mx:1410
1410 assert(n);
(gdb) up
4 0x00002aaabed04d5e in op_stmt2pivot (c=0x1043ff8, s=0x112f008)
at /ufs/goncalve/MonetDB/stable/sql/src/server/sql_optimize.mx:1633
1633 stmt *ns = set2pivot(c, s->op1.lval);
(gdb) down
3 0x00002aaabed042db in set2pivot (c=0x1043ff8, l=0xde58a8)
at /ufs/goncalve/MonetDB/stable/sql/src/server/sql_optimize.mx:1410
1410 assert(n);
(gdb) p n
$1 = (node *) 0x0
(gdb)
Note: The tested added already covers this situation.
## Comment 9933
Date: 2008-07-21 18:54:52 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
new round of fixes. The special case of constants in the selection of a subquery, with aggregation was broken.
## Comment 9934
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2019349 at http://sourceforge.net/support/tracker.php?aid=2019349
| assert fails on algebra version | https://api.github.com/repos/MonetDB/MonetDB/issues/1759/comments | 0 | 2020-11-30T09:59:17Z | 2024-06-27T11:31:29Z | https://github.com/MonetDB/MonetDB/issues/1759 | 753,332,593 | 1,759 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-16 11:44:47 +0200
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2008-07-19 07:27:35 +0200
## Comment 9924
Date: 2008-07-16 11:44:47 +0200
From: @drstmane
Since Monday July 14 2008, i.e., after checkins on Sunday July 13 2008, the following tests fail with MonetDB 5.6:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.64.64.d-Fedora8/src_mal/tst042.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.64.64.d-Fedora8/src_mal/tst450.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.64.64.d-Fedora8/src_modules_mal/inspect05.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.64.64.d-Fedora8/tests_BugDay_2005-10-06_4.9.3/return_types_of_head_and_tail.SF-701641.out.00.html
## Comment 9925
Date: 2008-07-18 15:39:54 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
they have been resolved.
## Comment 9926
Date: 2008-07-19 16:38:38 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Re-opened as todays TestWeb still shows theses tests failing with Stable MonetDB 5.6.
See above links.
## Comment 9927
Date: 2008-07-19 19:27:35 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Accidental some CURRENT patches had ended up in the stable.
## Comment 9928
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2019345 at http://sourceforge.net/support/tracker.php?aid=2019345
| M5 (Stable): tests fail since July 14 2008 | https://api.github.com/repos/MonetDB/MonetDB/issues/1758/comments | 0 | 2020-11-30T09:59:14Z | 2024-06-27T11:31:28Z | https://github.com/MonetDB/MonetDB/issues/1758 | 753,332,563 | 1,758 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-15 07:46:37 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2008-07-16 06:38:54 +0200
## Comment 9921
Date: 2008-07-15 07:46:37 +0200
From: @drstmane
With the development trunk only (i.e., not with the latest Jun2008 release),
all MAPI-/client-/remote tests fail (timeout) on Darwin (MacOS X).
See e.g.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB4/.mTests103/GNU.32.32.d-Darwin8.11.0/src_mapi/monet_BATs.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB4/.mTests103/GNU.32.32.d-Darwin8.11.0/src_mapi/monet_BATs.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.mTests103/GNU.32.32.d-Darwin8.11.0/src_modules_mal/mserver00.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.mTests103/GNU.32.32.d-Darwin8.11.0/src_modules_mal/mserver00.err.00.html
This seems to be the case since "out" MacOS X machine come back on-line on June 13 2008,
while is was not the case before it went off-line on
March 26 2008.
I have no idea, which differences between the Jun2008 release and the development trunk might cause these problems.
## Comment 9922
Date: 2008-07-16 06:38:54 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed by Niels.
Thanks!
## Comment 9923
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2018428 at http://sourceforge.net/support/tracker.php?aid=2018428
| All MAPI-/client-/remote tests fail (timeout) on Darwin | https://api.github.com/repos/MonetDB/MonetDB/issues/1757/comments | 0 | 2020-11-30T09:59:11Z | 2024-06-27T11:31:27Z | https://github.com/MonetDB/MonetDB/issues/1757 | 753,332,529 | 1,757 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-14 12:41:53 +0200
From: @yzchang
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2008-10-14 06:36:39 +0200
## Comment 9913
Date: 2008-07-14 12:41:53 +0200
From: @yzchang
Shred an empty file using pf:add-doc() in mclient crashes Mserver:
In terminal 1:
$ Mserver --dbinit="module(pathfinder);"
MonetDB Server v4.24.1
based on GDK v1.24.1
Copyright (c) 1993-2008, CWI. All rights reserved.
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.5.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.24.1 loaded (default back-end is 'milprint_summer')
XRPC administrative console at http://127.0.0.1:50001/admin
MonetDB>Segmentation fault
In terminal 2:
$ mclient -lx
xquery>pf:add-doc("/ufs/zhang/tmp/empty.xml", "empty.xml")
more><>
MAPI = monetdb@localhost:50000
ACTION= read_line
QUERY = pf:add-doc("/ufs/zhang/tmp/empty.xml", "empty.xml")
ERROR = Connection terminated
The crash happens in shredder.mx
Empty file is not a valid XML document, however, I think it should not cause Mserver to segmentation fault. Shredding the same doc using MIL shred_doc() results (correctly) in an error:
MonetDB>shred_doc("/ufs/zhang/tmp/empty.xml", "empty.xml");
!ERROR: Document is empty
!ERROR: Start tag expected, '<' not found
!ERROR: [shred_url]: 1 times inserted nil due to errors at tuples 0@0.
!ERROR: [shred_url]: first error was:
!ERROR: emit_tuple: node.level(18831648) >= XML_DEPTH_MAX(128)
!ERROR: CMDshred_url: operation failed.
Kind regards,
Jennie
## Comment 9914
Date: 2008-08-12 16:07:44 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
Did some looking around for this bug. Although the original bug report was for milprint_summer, the same behavior is noticed with the algebra (since is a runtime error anyway). The stack trace from gdb looks like:
0x00002aaab9bb22f5 in emit_tuple (shredCtx=0x18a1508, pre=15842497851538791387, size=606348325, level=-606348325, prop=5185, kind=48 '0', nid=15842497851538791387)
at /home/lsidir/develop//current/pathfinder/runtime/shredder.mx:574
574 shredCtx->dstBAT[PRE_SIZE].cast.intCAST[pre] = size;
Missing separate debuginfos, use: debuginfo-install bzip2.x86_64 e2fsprogs.x86_64 glibc.x86_64 keyutils.x86_64 krb5.x86_64 libselinux.x86_64 libxml2.x86_64 openssl.x86_64 pcre.x86_64 zlib.x86_64
(gdb) bt
0 0x00002aaab9bb22f5 in emit_tuple (shredCtx=0x18a1508, pre=15842497851538791387, size=606348325, level=-606348325, prop=5185, kind=48 '0', nid=15842497851538791387)
at /home/lsidir/develop//current/pathfinder/runtime/shredder.mx:574
1 0x00002aaab9bb23c5 in emit_node (shredCtx=0x18a1508, node=0x18ba360) at /home/lsidir/develop//current/pathfinder/runtime/shredder.mx:626
2 0x00002aaab9bb35be in shred_end_document (xmlCtx=0x18a1508) at /home/lsidir/develop//current/pathfinder/runtime/shredder.mx:822
3 0x00000038aae48cc8 in xmlParseDocument () from /usr/lib64/libxml2.so.2
4 0x00002aaab9bb4fdb in shredder_parse (shredCtx=0x18a1508, location=0x1006370 "/export/scratch0/lsidir/xmldocs/empty.xml", buffer=0x0, s=0x0)
at /home/lsidir/develop//current/pathfinder/runtime/shredder.mx:1479
5 0x00002aaab9bb71d9 in shred (docBAT=0x127c8c8, location=0x1006370 "/export/scratch0/lsidir/xmldocs/empty.xml", buffer=0x0, s=0x0, percentage=0, serFun=0x0, serCtx=0x0, collLock=0x427f8890)
at /home/lsidir/develop//current/pathfinder/runtime/shredder.mx:1985
6 0x00002aaab9bb7422 in CMDshred_url (docBAT=0x127c8c8, location=0x1006370 "/export/scratch0/lsidir/xmldocs/empty.xml", percentage=0x427f8880, collLock=0x427f8890, verbose=0x427f88a0 "")
at /home/lsidir/develop//current/pathfinder/runtime/shredder.mx:2013
7 0x00002aaab9b70753 in CMDshred_url_unpack524513197 (argc=6, argv=0x427f8850) at pf_support.glue.c:52
You have to try 3-4 times to shred the same empty doc before you get the segmentation fault. The segmentation fault is caused when the call back function "shred_end_document" is called by xmllib2, so it might be some leftovers from previous runs that have not been freed correctly.
## Comment 9915
Date: 2008-10-14 16:27:40 +0200
From: @drstmane
Jan,
could you please have a look at this one?
It seems to work fine in the stable release, but fails in the development trunk ...
Thanks!
Stefan
## Comment 9916
Date: 2008-10-14 16:37:53 +0200
From: Jan Flokstra <<jflokstra>>
I had a look at this a couple of weeks ago and it did not crash with me on my SuSe10.3 system. I now have the newest HEAD and it still does not crash. I think I will just have to guess what goes wrong and anticipate on this. I will try to solve it this week (in the HEAD)
## Comment 9917
Date: 2008-10-14 17:04:32 +0200
From: @sjoerdmullender
Could this be a problem of non-initialized memory when the memory is used for the second time, i.e. it is used in the first run, freed at the end of the query, and the next query allocates the same memory again. Until today, allocated memory was not initialized, but it was assumed that it was. I have seen crashes because of this. Today I checked in a change to mem.c to initialize all memory allocated by PFalloc and PFrealloc (only the extension, obviously) to zero. If this is indeed the cause, the bug should be fixed as of today. Somebody needs to check that.
## Comment 9918
Date: 2008-10-14 17:12:30 +0200
From: Jan Flokstra <<jflokstra>>
I found another problem here. In case of an empty document libxml2 calls end_document() without having called start_document(). I now detect this and bail out a.s.a.p when this happens. This could solve the problem but there may be more. I checked it in in the HEAD.
## Comment 9919
Date: 2008-10-14 18:36:38 +0200
From: @drstmane
added test in pathfinder/tests/BugTracker/Tests/empty_file.SF-2017862*
seems to work fine, now.
## Comment 9920
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2017862 at http://sourceforge.net/support/tracker.php?aid=2017862
| PF: shredding empty file causes MXQ to crash | https://api.github.com/repos/MonetDB/MonetDB/issues/1756/comments | 0 | 2020-11-30T09:59:08Z | 2024-06-27T11:31:26Z | https://github.com/MonetDB/MonetDB/issues/1756 | 753,332,492 | 1,756 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-10 06:54:05 +0200
From: @yzchang
To: @yzchang
Version: -- development
Last updated: 2008-07-10 07:04:58 +0200
## Comment 9910
Date: 2008-07-10 18:54:05 +0200
From: @yzchang
If the evaluation of the MIL code passed to pf:mil() results in a 'nil' value, pf:mil() will print garbage:
xquery>pf:mil('var a := new (void,oid);')
more><>
"�"
I think the problem is in the MPS translation of pf:mil():
{ translate pf:mil (string) as item*
if (count(loop000) != 1) ERROR("pf:mil cannot be called from within a for- loop");
kind := ELEM;
item := ws_mil(ws, item_str_.fetch(0));
if (type(item) = str) {
item := addValues(str_values,item);
kind := STR;
}
kind := set_kind(WS,kind);
iter := item.materialize(ipik).project(1@0);
ipik := iter;
} end of translate fn:mil (string) as item*
Note that the return value of ws_mil is not checked if it is a 'nil'.
Jennie
## Comment 9911
Date: 2008-07-10 19:04:58 +0200
From: @yzchang
Logged In: YES
user_id=341633
Originator: YES
Test added:
pathfinder/tests/BugTracker/Tests/pfmil_prints_garbage.SF-2015232
I have also checked in a fix.
Jennie
## Comment 9912
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2015232 at http://sourceforge.net/support/tracker.php?aid=2015232
| PF: pf:mil() prints garbage if MIL result is 'nil' | https://api.github.com/repos/MonetDB/MonetDB/issues/1755/comments | 0 | 2020-11-30T09:59:04Z | 2024-06-27T11:31:25Z | https://github.com/MonetDB/MonetDB/issues/1755 | 753,332,443 | 1,755 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-10 06:37:40 +0200
From: @yzchang
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-11-12 12:05:36 +0100
## Comment 9904
Date: 2008-07-10 18:37:40 +0200
From: @yzchang
When converting the resulting BAT to XML elements (in elem_constr()), the value of the last BUN is lost, as show by the query below:
xquery>pf:mil('var a :=new(str,str); a.insert("abc", "abc").insert("dsaf", "dad"); a.print(); return a;')
more><>
-----------------
h t name
str str type
-----------------
[ "abc", "abc" ]
[ "dsaf", "dad" ]
<bun tail="abc" head="abc"/>,
<bun/>
While 'a' does contain two BUNs, as show by the print() statement.
Regards,
Jennie
## Comment 9905
Date: 2008-09-05 16:58:28 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
I'm definitely not responsible for pf:mil and elem_constr() is a deprecated proc.
It however seems to work if mark is done starting from 0@0 in ws_mil instead of 1@0.
Jennie could you please check if everything works fine.
## Comment 9906
Date: 2008-09-05 18:12:18 +0200
From: @yzchang
Logged In: YES
user_id=341633
Originator: YES
Jan,
Thanks for fixing this. It works fine. However, your fix goes into the current branch, while the problem also exists in the stable branch. Would you please back-port your fix to the stable branch? Thanks again.
I assigned it to you because cvs said the code was latestly checked in by you, but it doesn't have to mean you are responsible for fixing it. But thanks for looking at it.
Jennie
## Comment 9907
Date: 2008-09-05 18:14:03 +0200
From: @yzchang
Logged In: YES
user_id=341633
Originator: YES
test added in pathfinder/tests/BugTracker/Tests/pfmil_loses_last_bun.SF-2015219
## Comment 9908
Date: 2008-11-12 12:05:36 +0100
From: Jan Rittinger <<jan.rittinger>>
We have a new stable branch -- closing.
## Comment 9909
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2015219 at http://sourceforge.net/support/tracker.php?aid=2015219
| PF: pf:mil() loses last MIL resulting BUN in elem_constr() | https://api.github.com/repos/MonetDB/MonetDB/issues/1754/comments | 0 | 2020-11-30T09:59:01Z | 2024-06-27T11:31:24Z | https://github.com/MonetDB/MonetDB/issues/1754 | 753,332,396 | 1,754 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-10 05:01:08 +0200
From: @yzchang
To: @yzchang
Version: -- development
Last updated: 2009-11-12 10:45:37 +0100
## Comment 9893
Date: 2008-07-10 17:01:08 +0200
From: @yzchang
If the result of the MIL code passed to pf:mil() is a BAT, and it contains nil values in its head, or tail, error will happen when translating the MIL result into XML elements, in elem_constr():
xquery>pf:mil('var a := new(str,str); a.insert(str_nil, "abc"); return a;')
more><>
MAPI = monetdb@localhost:50000
QUERY = pf:mil('var a := new(str,str); a.insert(str_nil, "abc"); return a;')
ERROR = !ERROR: mposjoin: all BATs in the tail of the third input BAT (ws_item) must have a dense head.
!ERROR: CMDmposjoin: operation failed.
!ERROR: interpret_params: fetch(param 1): evaluation error.
xquery>pf:mil('var a := new(str,str); a.insert("abc", str_nil); return a;')
more><>
MAPI = monetdb@localhost:50000
QUERY = pf:mil('var a := new(str,str); a.insert("abc", str_nil); return a;')
ERROR = !ERROR: mposjoin: missing matches. The result requires the same number of tuples as the first two input arguments: 1 < 2.
!ERROR: CMDmposjoin: operation failed.
!ERROR: interpret_params: fetch(param 1): evaluation error.
## Comment 9894
Date: 2008-09-05 17:06:37 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
I'm definitely not responsible for pf:mil and elem_constr() is a deprecated proc. If you in addition use elem_constr() incorrectly it of course fails.
What you would need is to turn nil values in ws_mil() into real strings instead of str(nil).
If you want to use pf:mil please fix it yourself.
## Comment 9895
Date: 2008-09-05 18:25:13 +0200
From: @yzchang
Logged In: YES
user_id=341633
Originator: YES
Jan,
Thanks for looking at this. I assigned it to you because cvs said the code was latestly checked in by
you, but it doesn't have to mean you are responsible for fixing it. I will try to fix it myself.
Regards,
Jennie
## Comment 9896
Date: 2008-09-05 18:26:24 +0200
From: @yzchang
Logged In: YES
user_id=341633
Originator: YES
tests added in pathfinder/tests/BugTracker/Tests/pfmil_and_nil_in_results_{1,2}.SF-2015135
## Comment 9897
Date: 2008-10-15 15:10:55 +0200
From: @drstmane
Jennie,
the expected output of your tests shows NIL values in the result of pf:mil() as empty strings, making them indistinguishable from "real" empty strings.
What about omitting the respective "head"/"tail" attribute completely in case its value is NIL?
That would not only make empty strings and NIL values distinguishable, but also IMHO match the NIL semantics (no value) better...
BTW, the problem is indeed not caused by/in elem_constr() itself, but xmltab2() and/or attr_constr() do not handle NIL values correctly and hence feed elem_constr() with inconsistent/incorrect input ...
## Comment 9898
Date: 2009-02-15 21:51:35 +0100
From: @drstmane
There appears to be only ONE test
$ l pathfinder/tests/BugTracker/Tests/pfmil_and_nil_in_results*
-rw-r----- 1 manegold ins1 1272 2009-01-29 14:10 pathfinder/tests/BugTracker/Tests/pfmil_and_nil_in_results.SF-2015135.stable.err
-rw-r----- 1 manegold ins1 1889 2009-01-29 14:10 pathfinder/tests/BugTracker/Tests/pfmil_and_nil_in_results.SF-2015135.stable.out
-rw-r----- 1 manegold ins1 138 2009-01-29 14:10 pathfinder/tests/BugTracker/Tests/pfmil_and_nil_in_results.SF-2015135.xq
while the "All" file (and this bug report) list(s) TWO:
$ grep pfmil_and_nil_in_results pathfinder/tests/BugTracker/Tests/All
NOT_ALGEBRA?pfmil_and_nil_in_results_1.SF-2015135
NOT_ALGEBRA?pfmil_and_nil_in_results_2.SF-2015135
Please check and fix.
## Comment 9899
Date: 2009-02-17 12:37:23 +0100
From: @yzchang
sorry, forgot to change the test name in "All" file, when merged those two tests into one.
This is fixed now.
## Comment 9900
Date: 2009-08-06 13:34:13 +0200
From: @sjoerdmullender
Jennie, what is the status of this?
## Comment 9901
Date: 2009-08-06 15:50:28 +0200
From: @yzchang
The bug still exists. However, pf:mil() is only supported by MPS, and it is rarely used.
So I lower the priority of this bug.
## Comment 9902
Date: 2009-11-12 10:45:37 +0100
From: @peterboncz
pf:mil is mps, don't care anymore
## Comment 9903
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2015135 at http://sourceforge.net/support/tracker.php?aid=2015135
| PF: pf:mil() can't deal with nil values in MIL results | https://api.github.com/repos/MonetDB/MonetDB/issues/1753/comments | 0 | 2020-11-30T09:58:58Z | 2024-06-28T13:29:23Z | https://github.com/MonetDB/MonetDB/issues/1753 | 753,332,349 | 1,753 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-10 07:20:21 +0200
From: @drstmane
To: @yzchang
Version: -- development
Last updated: 2008-07-10 07:07:54 +0200
## Comment 9890
Date: 2008-07-10 07:20:21 +0200
From: @drstmane
From
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.GNU.64.64.d-Fedora8..2008.07.09_07-04-11/rpm.out.html :
========
Checking for unpackaged file(s): /usr/lib/rpm/check-files /tmp/MonetDB4-XQuery-0.25.0-1_Fedora8.oid64-zNG593
error: Installed (but unpackaged) file(s) found:
/usr/share/MonetDB/xrpc/demo/MultimediaN.png
/usr/share/MonetDB/xrpc/demo/cwi.bmp
/usr/share/MonetDB/xrpc/demo/demo-mod.xq
/usr/share/MonetDB/xrpc/demo/demo-xrpcmod.xq
/usr/share/MonetDB/xrpc/demo/index.html
/usr/share/MonetDB/xrpc/demo/monet.png
/usr/share/MonetDB/xrpc/demo/noquery.gif
/usr/share/MonetDB/xrpc/demo/req1.xml
/usr/share/MonetDB/xrpc/demo/res1.xml
/usr/share/MonetDB/xrpc/demo/style.css
RPM build errors:
Installed (but unpackaged) file(s) found:
/usr/share/MonetDB/xrpc/demo/MultimediaN.png
/usr/share/MonetDB/xrpc/demo/cwi.bmp
/usr/share/MonetDB/xrpc/demo/demo-mod.xq
/usr/share/MonetDB/xrpc/demo/demo-xrpcmod.xq
/usr/share/MonetDB/xrpc/demo/index.html
/usr/share/MonetDB/xrpc/demo/monet.png
/usr/share/MonetDB/xrpc/demo/noquery.gif
/usr/share/MonetDB/xrpc/demo/req1.xml
/usr/share/MonetDB/xrpc/demo/res1.xml
/usr/share/MonetDB/xrpc/demo/style.css
make: *** [rpm] Error 1
========
## Comment 9891
Date: 2008-07-10 19:07:54 +0200
From: @yzchang
Logged In: YES
user_id=341633
Originator: NO
I have added the new files to MonetDB-XQuery.spec.in and rebuild the RPMs.
It should be fixed now.
## Comment 9892
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2014741 at http://sourceforge.net/support/tracker.php?aid=2014741
| PF: building RPMs (`make rpm`) fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1752/comments | 0 | 2020-11-30T09:58:54Z | 2024-06-27T11:31:22Z | https://github.com/MonetDB/MonetDB/issues/1752 | 753,332,304 | 1,752 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-09 12:59:46 +0200
From: Pawel Lewicki <<plewy>>
To: @sjoerdmullender
Version: -- development
Last updated: 2008-08-01 03:55:30 +0200
## Comment 9886
Date: 2008-07-09 12:59:46 +0200
From: Pawel Lewicki <<plewy>>
All data with Polish characters (utf-8) inserted via ODBC was broken. The same data put using Python bindings was fine.
All tests I performed show that all 'utf-8' data I try to input (SQL: INSERT, WHERE) is broken. Query results are fine.
(MonetDB-ODBC-Installer-i386-20080624.msi)
## Comment 9887
Date: 2008-08-01 15:21:29 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
There was a bug in the way non-ASCII bytes (as will occur in UTF-8 encoded data) was prepared for transmission to the server. This has now been fixed in the stable branch.
## Comment 9888
Date: 2008-08-01 15:55:30 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Adapted the odbcsample1 test to also check UTF-8 encoded data (albeit just funny versions of left and right quotation marks).
Closing.
## Comment 9889
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2014118 at http://sourceforge.net/support/tracker.php?aid=2014118
| ODBC - broken 'utf-8' data on input | https://api.github.com/repos/MonetDB/MonetDB/issues/1751/comments | 0 | 2020-11-30T09:58:51Z | 2024-06-27T11:31:21Z | https://github.com/MonetDB/MonetDB/issues/1751 | 753,332,263 | 1,751 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-08 11:09:13 +0200
From: @drstmane
To: Stratos Idreos <<idreos>>
Version: -- development
Last updated: 2008-07-09 01:21:05 +0200
## Comment 9884
Date: 2008-07-08 23:09:13 +0200
From: @drstmane
When configured with "--disable-debug" and/or "--enable-optimize" (i.e., once any "-O" switch is used with gcc), crackers fails to compile:
========
make[9]: Entering directory `/net/rig.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/build.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/MonetDB5/src/modules/mal/crackers'
/bin/sh ../../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../.. -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers -I../../atoms -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/../../atoms -I../../kernel -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/../../kernel -I../../../mal -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/../../../mal -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/include/MonetDB -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/include/MonetDB/mapilib -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/include/MonetDB -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/include/MonetDB/common -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/include/MonetDB/gdk -DLIBCRACKERS -O2 -Wall -Wextra -std=c99 -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2 -D_REENTRANT -c -o lib_crackers_la-crackers_partial_sideways.lo `test -f 'crackers_partial_sideways.c' || echo '/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/'`crackers_partial_sideways.c
gcc -DHAVE_CONFIG_H -I. -I../../../.. -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers -I../../atoms -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/../../atoms -I../../kernel -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/../../kernel -I../../../mal -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/../../../mal -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/include/MonetDB -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/include/MonetDB/mapilib -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/include/MonetDB -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/include/MonetDB/common -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/include/MonetDB/gdk -DLIBCRACKERS -O2 -Wall -Wextra -std=c99 -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2 -D_REENTRANT -c crackers_partial_sideways.c -fPIC -DPIC -o .libs/lib_crackers_la-crackers_partial_sideways.o
cc1: warnings being treated as errors
/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/crackers_partial_sideways.mx: In function 'CRKselectBoundsTailIncrementalSideways_int_int':
/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/crackers_partial_sideways.mx:1534: warning: 'base' may be used uninitialized in this function
/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/crackers_partial_sideways.mx:1522: warning: 'posh' may be used uninitialized in this function
/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/crackers_partial_sideways.mx:1522: warning: 'posl' may be used uninitialized in this function
/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/crackers_partial_sideways.mx:1534: warning: 'tuplesToAnalyze' may be used uninitialized in this function
/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/crackers_partial_sideways.mx:1533: warning: 'pairt' may be used uninitialized in this function
make[9]: *** [lib_crackers_la-crackers_partial_sideways.lo] Error 1
make[9]: Leaving directory `/net/rig.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/build.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/MonetDB5/src/modules/mal/crackers'
========
## Comment 9885
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2013815 at http://sourceforge.net/support/tracker.php?aid=2013815
| M5: crackers fails to compile with optimization enabled | https://api.github.com/repos/MonetDB/MonetDB/issues/1750/comments | 0 | 2020-11-30T09:55:16Z | 2024-06-27T11:31:20Z | https://github.com/MonetDB/MonetDB/issues/1750 | 753,329,646 | 1,750 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-08 08:21:30 +0200
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2008-07-08 10:22:07 +0200
## Comment 9881
Date: 2008-07-08 08:21:30 +0200
From: @drstmane
When configured with --disable-debug or --enable-optimize, M5 fails to compile:
make[5]: Entering directory `/net/rig.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/build.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/MonetDB5/src/mal'
/bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/mal -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/mal -I../optimizer -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/mal/../optimizer -I../scheduler -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/mal/../scheduler -I../modules/kernel -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/mal/../modules/kernel -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/include/MonetDB -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/include/MonetDB/common -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/include/MonetDB/gdk -DLIBMAL -O2 -Wall -Wextra -std=c99 -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2 -D_REENTRANT -c -o libmonetdb5_la-mal_interpreter.lo `test -f 'mal_interpreter.c' || echo '/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/mal/'`mal_interpreter.c
gcc -DHAVE_CONFIG_H -I. -I../.. -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/mal -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/mal -I../optimizer -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/mal/../optimizer -I../scheduler -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/mal/../scheduler -I../modules/kernel -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/mal/../modules/kernel -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/include/MonetDB -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/include/MonetDB/common -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/include/MonetDB/gdk -DLIBMAL -O2 -Wall -Wextra -std=c99 -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2 -D_REENTRANT -c mal_interpreter.c -fPIC -DPIC -o .libs/libmonetdb5_la-mal_interpreter.o
cc1: warnings being treated as errors
/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/mal/mal_interpreter.mx: In function 'runFlow':
/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/mal/mal_interpreter.mx:1851: warning: 'oldMemory.arena' is used uninitialized in this function
/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/mal/mal_interpreter.mx:740: warning: 'exceptionVar' may be used uninitialized in this function
make[5]: *** [libmonetdb5_la-mal_interpreter.lo] Error 1
make[5]: Leaving directory `/net/rig.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/build.--enable-strict_--disable-optimize_--disable-debug_--disable-assert/MonetDB5/src/mal'
## Comment 9882
Date: 2008-07-08 10:22:07 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
committed changes pending
## Comment 9883
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2013182 at http://sourceforge.net/support/tracker.php?aid=2013182
| M5 fails to compile with optimization enabled | https://api.github.com/repos/MonetDB/MonetDB/issues/1749/comments | 0 | 2020-11-30T09:55:13Z | 2024-06-27T11:31:19Z | https://github.com/MonetDB/MonetDB/issues/1749 | 753,329,608 | 1,749 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-06 06:40:34 +0200
From: @drstmane
To: @yzchang
Version: -- development
Last updated: 2008-07-18 07:41:38 +0200
## Comment 9876
Date: 2008-07-06 18:40:34 +0200
From: @drstmane
icl -Qstd=c99 -GR- -Qsafeseh- -GF -W3 -wd4273 -wd4102 -MD -nologo -Ox -I. -I.\.. "-IC:\Pthreads\include" -I.\..\..\runtime "-I.." -I.\..\..\runtime\.. "-IC:\cygwin\var\tmp\monet.Int.32.32.d.16202\MonetDB4\.Int.32.32.d-Windows5.1\include\MonetDB4" "-IC:\cygwin\var\tmp\monet.Int.32.32.d.16202\MonetDB4\.Int.32.32.d-Windows5.1\include\MonetDB4\monet" "-IC:\cygwin\var\tmp\monet.Int.32.32.d.16202\MonetDB4\.Int.32.32.d-Windows5.1\include\MonetDB4\plain" "-IC:\cygwin\var\tmp\monet.Int.32.32.d.16202\MonetDB4\.Int.32.32.d-Windows5.1\include\MonetDB4\contrib" "-IC:\cygwin\var\tmp\monet.Int.32.32.d.16202\MonetDB\.Int.32.32.d-Windows5.1\include\MonetDB" "-IC:\cygwin\var\tmp\monet.Int.32.32.d.16202\MonetDB\.Int.32.32.d-Windows5.1\include\MonetDB\common" "-IC:\cygwin\var\tmp\monet.Int.32.32.d.16202\MonetDB\.Int.32.32.d-Windows5.1\include\MonetDB\gdk" -DHAVE_LIBXML2 "-IC:\libxml2-2.6.30.win32\include" "-IC:\zlib-1.2.3.win32\include" "-IC:\iconv-1.9.2.win32\include" -DMILPRINT_SUMMER_IS_DEFAULT=0 -DALGEBRA_IS_DEFAULT=1 -DSQL_IS_DEFAULT=0 -DEMBEDDED -DMT -DNO_CGI -DNO_AUTH -DIO_MAX=10240 -LD -Felib_xrpc_client.dll xrpc_client.glue.obj xrpc_client.obj /link libserialize.lib "C:\libxml2-2.6.30.win32\lib\libxml2.lib" "C:\zlib-1.2.3.win32\lib\zdll.lib" "C:\iconv-1.9.2.win32\lib\iconv.lib" wsock32.lib .\lib_pf_support.lib .\lib_pathfinder.lib /LIBPATH:"C:\cygwin\var\tmp\monet.Int.32.32.d.16202\MonetDB\.Int.32.32.d-Windows5.1\lib" libbat.lib libstream.lib /LIBPATH:"C:\cygwin\var\tmp\monet.Int.32.32.d.16202\MonetDB4\.Int.32.32.d-Windows5.1\lib" libmonet.lib /LIBPATH:"C:\cygwin\var\tmp\monet.Int.32.32.d.16202\MonetDB4\.Int.32.32.d-Windows5.1\lib\MonetDB4" lib_streams.lib lib_builtin.lib lib_ascii_io.lib
Creating library lib_xrpc_client.lib and object lib_xrpc_client.exp
xrpc_client.obj : error LNK2019: unresolved external symbol __imp__XRPCreq_free referenced in function _CMDget_rpc_res
xrpc_client.obj : error LNK2019: unresolved external symbol __imp__xrpc_parse_message referenced in function _CMDget_rpc_res
lib_xrpc_client.dll : fatal error LNK1120: 2 unresolved externals
NMAKE : fatal error U1077: '"C:\Program Files\Intel\Compiler\C++\10.1.013\Ia32\Bin\icl.EXE"' : return code '0x460'
Stop.
For details, see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.Int.32.32.d-Windows5.1..2008.07.06_08-53-25/make.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.Int.32.32.d-Windows5.1..2008.07.06_08-53-25/make.out.htmle201
http://www.ins.cwi.nl/~monet/permastore/2008-07-06/Current/make-pathfinder-Int.32.32.d-Windows5.1.errors.htmll422
## Comment 9877
Date: 2008-07-17 07:56:44 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Compiling (and linking) xrpc_client no "happens to work" on Windows, "despite"
[ 2020269 ] PF/runtime fails to link on Darwin (MacOS X)
https://sourceforge.net/tracker/index.php?func=detail&aid=2020269&group_id=56967&atid=482468 .
However, now linking pathfinder/runtime5 fails on Windows:
========
libserialize.lib(serialize.obj) : error LNK2019: unresolved external symbol __imp__xrpc_port referenced in function _draw_queryflow
libserialize.lib(serialize_dflt.obj) : error LNK2001: unresolved external symbol __imp__xrpc_port
libserialize.lib(serialize.obj) : error LNK2019: unresolved external symbol __imp__xrpc_hostname referenced in function _draw_queryflow
libserialize.lib(serialize_dflt.obj) : error LNK2001: unresolved external symbol __imp__xrpc_hostname
lib_xquery.dll : fatal error LNK1120: 2 unresolved externals
========
see also
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.Int.32.32.d-Windows5.1..2008.07.17_00-09-01/make.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.Int.32.32.d-Windows5.1..2008.07.17_00-09-01/make-k.out.html
http://www.ins.cwi.nl/~monet/permastore/2008-07-17/Current/make-pathfinder-Int.32.32.d-Windows5.1.errors.htmll430
Please note, simply linking runtime5 with lib_pf_support from runtime(4) is IMHO no solution.
Please also be aware of cyclic dependencies, e.g., between libserialize and lib_pf_support in pathfinder/runtime, and (try to) avoid them.
## Comment 9878
Date: 2008-07-17 08:41:33 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Also here, you should carefully check, which global variables are indeed required, and avoid them as far as possible.
Passing information to functions via function arguments is usually a much cleaner and more maintainable alternative than using global variables...
## Comment 9879
Date: 2008-07-18 07:41:38 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed by Jennie.
Thanks.
## Comment 9880
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2011858 at http://sourceforge.net/support/tracker.php?aid=2011858
| PF: xrpc_client fails to compile on Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/1748/comments | 0 | 2020-11-30T09:55:11Z | 2024-06-27T11:31:18Z | https://github.com/MonetDB/MonetDB/issues/1748 | 753,329,571 | 1,748 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-04 06:55:38 +0200
From: @yzchang
To: @njnes
Version: -- development
Last updated: 2008-07-11 12:58:01 +0200
## Comment 9872
Date: 2008-07-04 18:55:38 +0200
From: @yzchang
Execute the MIL PROC project() on a BAT which has a batFirst > 0 returns wrong results:
MonetDB>var a := monet_environment.copy().access(BAT_WRITE).delete("exec_prefix").delete("prefix").delete("gdk_debug").delete("gdk_embedded").delete("gdk_vm_minsize").delete("mapi_debug").delete("mapi_noheaders").delete("monet_daemon").delete("monet_mod_path").delete("monet_pid").delete("monet_prompt").delete("monet_welcome").delete("sql_debug").delete("sql_logdir").insert("gdk_mem_maxsize", str(mem_maxsize())).sort();
MonetDB>a.info().print();
-----------------------------------------
h t name
str str type
-----------------------------------------
...
[ "batFirst", "13" ]
...
MonetDB>a.project(oid_nil).print();
---------------------------------
h t name
str oid type
---------------------------------
[ "config", nil ]
[ "datadir", nil ]
[ "gdk_alloc_map", nil ]
[ "gdk_arch", nil ]
[ "gdk_dbfarm", nil ]
[ "gdk_dbname", nil ]
[ "gdk_mem_bigsize", nil ]
[ "gdk_mem_maxsize", nil ]
[ "gdk_mem_pagebits", nil ]
[ "gdk_version", nil ]
[ "gdk_vmtrim", nil ]
[ "host", nil ]
[ "mapi_clients", nil ]
[ "mapi_open", nil ]
[ "mapi_port", nil ]
[ "monet_admin", nil ]
[ "monet_cwd", nil ]
[ "monet_version", nil ]
[ "standoff_end", nil ]
[ "standoff_ns", nil ]
[ "standoff_start", 0@0 ]
[ "xquery_backend", 0@0 ]
[ "xquery_cacheMB", 0@0 ]
[ "xquery_cacherules", 0@0 ]
[ "xquery_logdir", 0@0 ]
[ "xquery_output", 0@0 ]
[ "xquery_procMB", 0@0 ]
[ "xrpc_admin", 0@0 ]
[ "xrpc_open", 0@0 ]
[ "xrpc_options", 0@0 ]
[ "xrpc_port", 0@0 ]
[ "xrpc_trusted", 0@0 ]
[ "xrpc_user", 0@0 ]
Thanks Sjoerd and Stefan for find the (possible) cause of the problem:
it seems that BATconst does not take into account an input BAT with deleted BUNs and batFirst > 0. When VIEWcreate(b, bt) is called, b is not alligned with bt.
However, this problem seems also related with the use of 'sort()' in above MIL code. Because, without the 'sort', even batFirst > 0, project produces correct result:
1. Start a new Mserver session, without 'sort()', project(oid_nil) produces correct results:
MonetDB>var a := monet_environment.copy().access(BAT_WRITE).delete("exec_prefix").delete("prefix").delete("gdk_debug").delete("gdk_embedded").delete("gdk_vm_minsize").delete("mapi_debug").delete("mapi_noheaders").delete("monet_daemon").delete("monet_mod_path").delete("monet_pid").delete("monet_prompt").delete("monet_welcome").delete("sql_debug").delete("sql_logdir").insert("gdk_mem_maxsize", str(mem_maxsize()));
MonetDB>a.info().find("batFirst").print();
[ "13" ]
MonetDB>a.project(oid_nil).print();
---------------------------------
h t name
str oid type
---------------------------------
[ "gdk_alloc_map", nil ]
[ "gdk_mem_pagebits", nil ]
...
[ "xquery_backend", nil ]
[ "gdk_mem_maxsize", nil ]
2. In the same Mserver session, now we use 'sort()', results of project(oid_nil) contains garbage:
MonetDB>a := monet_environment.copy().access(BAT_WRITE).delete("exec_prefix").delete("prefix").delete("gdk_debug").delete("gdk_embedded").delete("gdk_vm_minsize").delete("mapi_debug").delete("mapi_noheaders").delete("monet_daemon").delete("monet_mod_path").delete("monet_pid").delete("monet_prompt").delete("monet_welcome").delete("sql_debug").delete("sql_logdir").insert("gdk_mem_maxsize", str(mem_maxsize())).sort();
MonetDB>a.info().find("batFirst").print();
[ "13" ]
MonetDB>a.project(oid_nil).print();
---------------------------------
h t name
str oid type
---------------------------------
[ "config", nil ]
[ "datadir", nil ]
...
[ "standoff_end", nil ]
[ "standoff_ns", nil ]
[ "standoff_start", 0@0 ]
[ "xquery_backend", 0@0 ]
...
[ "xrpc_trusted", 0@0 ]
[ "xrpc_user", 0@0 ]
3. In the same Mserver session, subsequent execution of the MIL statement, *with* 'sort()' produces correct results:
MonetDB>a := monet_environment.copy().access(BAT_WRITE).delete("exec_prefix").delete("prefix").delete("gdk_debug").delete("gdk_embedded").delete("gdk_vm_minsize").delete("mapi_debug").delete("mapi_noheaders").delete("monet_daemon").delete("monet_mod_path").delete("monet_pid").delete("monet_prompt").delete("monet_welcome").delete("sql_debug").delete("sql_logdir").insert("gdk_mem_maxsize", str(mem_maxsize())).sort();
MonetDB>a.info().find("batFirst").print();
[ "13" ]
MonetDB>a.project(oid_nil).print();
---------------------------------
h t name
str oid type
---------------------------------
[ "config", nil ]
[ "datadir", nil ]
...
[ "xrpc_trusted", nil ]
[ "xrpc_user", nil ]
Kind regards,
Jennie
## Comment 9873
Date: 2008-07-07 17:27:31 +0200
From: @yzchang
Logged In: YES
user_id=341633
Originator: YES
Test added in
MonetDB4/tests/BugTracker/Tests/project_on_BAT_with_batFirst.SF-2020806
## Comment 9874
Date: 2008-07-11 12:58:01 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
fixed in the stable and current. The bunFirst got unaligned because the sort leaves this correctly set. We solved this in BATconst with an extra BATslice.
## Comment 9875
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2010806 at http://sourceforge.net/support/tracker.php?aid=2010806
| Project on BAT with batFirst > 0 returns wrong results | https://api.github.com/repos/MonetDB/MonetDB/issues/1747/comments | 0 | 2020-11-30T09:55:08Z | 2024-06-27T11:31:17Z | https://github.com/MonetDB/MonetDB/issues/1747 | 753,329,549 | 1,747 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-03 10:55:26 +0200
From: @drstmane
To: @yzchang
Version: -- development
Last updated: 2008-07-04 05:50:26 +0200
## Comment 9869
Date: 2008-07-03 22:55:26 +0200
From: @drstmane
make[4]: Entering directory `/net/rig.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/build.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/pathfinder/runtime'
/bin/sh ../libtool --tag=CC --mode=compile icc -no-gcc -fPIC -DHAVE_CONFIG_H -I. -I.. -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime -I.. -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime/.. -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB4 -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB4/monet -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB4/plain -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB4/contrib -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB4/mapi -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB4/calibrator -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB/common -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB/gdk -I/usr/include/libxml2 -DLIBPF -we140 -wd1418 -Wall -w2 -std=c99 -O3 -we266 -Werror -wd1418,1419,279,981,810,193,111,1357,1572,1599 -DEMBEDDED -DMT -DNO_CGI -DNO_AUTH -DIO_MAX=10240 -c -o libpf_la-ll_staircasejoin.lo `test -f 'll_staircasejoin.c' || echo '/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime/'`ll_staircasejoin.c
icc -no-gcc -fPIC -DHAVE_CONFIG_H -I. -I.. -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime -I.. -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime/.. "-I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB4" "-I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB4/monet" "-I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB4/plain" "-I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB4/contrib" "-I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB4/mapi" "-I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB4/calibrator" "-I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB" "-I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB/common" "-I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB/gdk" -I/usr/include/libxml2 -DLIBPF -we140 -wd1418 -Wall -w2 -std=c99 -O3 -we266 -Werror -wd1418,1419,279,981,810,193,111,1357,1572,1599 -DEMBEDDED -DMT -DNO_CGI -DNO_AUTH -DIO_MAX=10240 -c ll_staircasejoin.c -DPIC -o .libs/libpf_la-ll_staircasejoin.o
pf_support.h(34): error 310: old-style parameter list (anachronism)
pf_support_export char* xrpc_log_dir();
^
compilation aborted for ll_staircasejoin.c (code 2)
make[4]: *** [libpf_la-ll_staircasejoin.lo] Error 1
make[4]: Leaving directory `/net/rig.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/build.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/pathfinder/runtime'
## Comment 9870
Date: 2008-07-04 17:50:26 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed by Jennie.
Thanks.
## Comment 9871
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2010064 at http://sourceforge.net/support/tracker.php?aid=2010064
| PF: pathfinder/runtime fails to compile with icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1746/comments | 0 | 2020-11-30T09:55:05Z | 2024-06-27T11:31:16Z | https://github.com/MonetDB/MonetDB/issues/1746 | 753,329,518 | 1,746 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-03 08:01:28 +0200
From: @drstmane
To: @yzchang
Version: -- development
Last updated: 2009-02-15 09:57:21 +0100
## Comment 9863
Date: 2008-07-03 20:01:28 +0200
From: @drstmane
For details please see the TestWeb tomorrow (or run Mtest yourself).
The following summaries show the path of degradation:
Today's Stable branches (XQuery_0-24 + MonetDB_4-24):
108 out of 1797 tests could not be executed
2 out of 1797 tests produced slightly different output
1 out of 1797 tests ran into timeout
17 out of 1797 tests produced SIGNIFICANTLY different output
Today's Stable pathfinder (XQuery_0-24) + Current MonetDB4 (HEAD):
110 out of 1797 tests could not be executed
1 out of 1797 tests ran into timeout
323 out of 1797 tests produced SIGNIFICANTLY different output
Today's Current pathfinder (HEAD) before xrpcdemo merge-in + Current MonetDB4 (HEAD):
16 out of 1801 tests could not be executed
1 out of 1801 tests produced slightly different output
1 out of 1801 tests ran into timeout
420 out of 1801 tests produced SIGNIFICANTLY different output
pathfinder's xrpcdemo branch after propagating all changes from Stable XQuery_0-24 branch + Current MonetDB4 (HEAD):
110 out of 1797 tests could not be executed
1056 out of 1797 tests produced SIGNIFICANTLY different output
Current pathfinder (HEAD) after xrpcdemo merge-in + Current MonetDB4 (HEAD):
16 out of 1801 tests could not be executed
1 out of 1801 tests produced slightly different output
1155 out of 1801 tests produced SIGNIFICANTLY different output
## Comment 9864
Date: 2008-07-16 08:00:54 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Most tests have been fixed by Jennie (and others).
Thanks.
However, (at least) the following tests still run worse than before on all platforms:
modules/pftijah/load o o X o
modules/pftijah/procs o o X o
runtime/sigs o o X o
runtime/sigs_xrpc o o X o
tests/BugTracker/treat_as.SF-1586454 o o X o
tests/BugTracker/insert_multiple.SF-1590580 o o X o
tests/BugTracker/inserting_multiple_elements.SF-1590583 o o X o
tests/BugTracker/clear_attrs_on_delete.SF-1612739 o o o X
tests/BugTracker/clear_attrs_on_delete.SF-1612739-b o o o X
tests/BugTracker/clear_attrs_on_delete.SF-1612739-c o o X X
tests/BugTracker/corrupt_after_update.SF-1706640 o o X X
tests/BugTracker/accessing_renamed_inserted_deleted_node.SF-1718622-1718635-1718709 o o X o
tests/BugTracker/insert_large_doc.SF-1726954 o o X X
tests/BugTracker/replace-corrupts.SF-1758902 o o X X
tests/BugTracker/swizzle-bug.SF-1760811 o o X X
tests/BugTracker/swizzle-http://sourceforge.net/support/tracker.php?aid=2.SF-1763495 o o X X
tests/BugTracker/insert_attribute_gives_ERROR_in_merged_union.SF-1763575 o o X X
tests/BugTracker/immune_for_updates.SF-1766259 o o X X
tests/BugTracker/repeated-insert.SF-1814911 o o X X
tests/BugTracker/insert-new-page.SF-1854215 o o o X
tests/BugTracker/update-stress.SF-1896755 o o o X
tests/BugTracker/immune_for_updates.SF-1981852 o o X X
tests/Update/setattr-1 o o X X
tests/Update/insert-1 o o X X
tests/Update/insert-2 o o X X
tests/Update/symm o o X X
tests/Update/replacevaluetest o o X X
tests/Update/replacevaluetest2 o o X X
tests/Update/update o o X X
tests/Update/insert_test_order o o X X
tests/Update/insert_test_order_seq X o X X
tests/W3C_use_cases/XQUF/AddressBook/Q1x o o o X
tests/W3C_use_cases/XQUF/AddressBook/check_docs o o X o
tests/W3C_use_cases/XQUF/Parts/Q1 o o X o
tests/W3C_use_cases/XQUF/Parts/Q2 o o X o
tests/W3C_use_cases/XQUF/Parts/Q3a1 o o X o
tests/W3C_use_cases/XQUF/Parts/Q3a2 o o X o
tests/W3C_use_cases/XQUF/Parts/Q4a o o X o
tests/W3C_use_cases/XQUF/Parts/Q4ax o o X o
tests/W3C_use_cases/XQUF/Parts/Q4b o o X o
tests/W3C_use_cases/XQUF/Parts/Q4bx o o X o
tests/W3C_use_cases/XQUF/Parts/Q4c o o X o
tests/W3C_use_cases/XQUF/Parts/Q4cx o o X o
tests/W3C_use_cases/XQUF/Parts/Q6 o o X o
tests/W3C_use_cases/XQUF/Parts/Q6x o o X o
tests/W3C_use_cases/XQUF/R/Q1 o o X o
tests/W3C_use_cases/XQUF/R/Q2 o o X o
tests/W3C_use_cases/XQUF/R/Q3 o o X o
tests/W3C_use_cases/XQUF/R/Q4x o o X o
tests/W3C_use_cases/XQUF/R/Q5a o o X o
tests/W3C_use_cases/XQUF/R/Q5b o o X o
tests/W3C_use_cases/XQUF/R/Q6a o o X o
tests/W3C_use_cases/XQUF/R/Q6b o o X o
tests/W3C_use_cases/XQUF/R/Q7 o o X o
tests/W3C_use_cases/XQUF/R/Q7x o o X o
tests/W3C_use_cases/XQUF/R/Q8 o o X o
tests/W3C_use_cases/XQUF/R/Q9 o o X o
## Comment 9865
Date: 2008-07-16 12:50:04 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Undo of accidental closing.
## Comment 9866
Date: 2008-07-16 12:51:46 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
In addition to the tests listed below,
most XRPC tests in tests/XRpc/ fail with the MPS back-end,
and all XRPC tests in both tests/XRpc/ and benchmarks/XMark/XRpc/ fail when compiled with icc.
Cf.:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTestsg103/index_short.html
## Comment 9867
Date: 2009-02-15 21:57:21 +0100
From: @drstmane
most tests seem to work, again --- I failed to keep track of all the details (don't recall having seen any checkins mentioning fixes for this bug report, though)
closing this one --- more specific report about individual failing tests might come later ... or just see the testweb for details ...
## Comment 9868
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2009938 at http://sourceforge.net/support/tracker.php?aid=2009938
| PF: XRPC demo merge makes hundreds of tests fail | https://api.github.com/repos/MonetDB/MonetDB/issues/1745/comments | 0 | 2020-11-30T09:55:02Z | 2024-06-27T11:31:15Z | https://github.com/MonetDB/MonetDB/issues/1745 | 753,329,491 | 1,745 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-03 07:12:34 +0200
From: @drstmane
To: @yzchang
Version: -- development
Last updated: 2008-07-04 05:50:39 +0200
## Comment 9860
Date: 2008-07-03 19:12:34 +0200
From: @drstmane
In case M5 is found during configure:
========
make[3]: Entering directory `/net/rig.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/build./pathfinder/runtime5'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime5 -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime5 -I../compiler/include -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime5/../compiler/include -I../runtime -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime5/../runtime -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB5/atoms -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB5/compiler -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB5/kernel -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB5/mal -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB5/optimizer -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB5/scheduler -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB5 -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB/common -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB/gdk -I/usr/include/libxml2 -DLIBXQUERY -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 -c -o lib_xquery_la-xquery.lo `test -f 'xquery.c' || echo '/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime5/'`xquery.c
gcc -DHAVE_CONFIG_H -I. -I.. -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime5 -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime5 -I../compiler/include -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime5/../compiler/include -I../runtime -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime5/../runtime -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB5/atoms -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB5/compiler -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB5/kernel -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB5/mal -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB5/optimizer -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB5/scheduler -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB5 -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB/common -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix./include/MonetDB/gdk -I/usr/include/libxml2 -DLIBXQUERY -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 -c xquery.c -fPIC -DPIC -o .libs/lib_xquery_la-xquery.o
cc1: warnings being treated as errors
/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime5/xquery.mx: In function 'xquery_print_result_main_wrap':
/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime5/xquery.mx:214: warning: passing argument 5 of 'xquery_print_result_DRIVER' makes integer from pointer without a cast
/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime5/xquery.mx:214: warning: passing argument 7 of 'xquery_print_result_DRIVER' makes pointer from integer without a cast
/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime5/xquery.mx:214: warning: passing argument 13 of 'xquery_print_result_DRIVER' from incompatible pointer type
/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime5/xquery.mx:214: warning: passing argument 14 of 'xquery_print_result_DRIVER' from incompatible pointer type
/ufs/manegold/_/scratch0/Monet/Testing/Current/source/pathfinder/runtime5/xquery.mx:214: error: too few arguments to function 'xquery_print_result_DRIVER'
make[3]: *** [lib_xquery_la-xquery.lo] Error 1
make[3]: Leaving directory `/net/rig.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/build./pathfinder/runtime5'
========
## Comment 9861
Date: 2008-07-04 17:50:39 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed by Jennie.
Thanks.
## Comment 9862
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2009903 at http://sourceforge.net/support/tracker.php?aid=2009903
| PF: pathfinder (runtime5/xquery.mx) fails to compile with M5 | https://api.github.com/repos/MonetDB/MonetDB/issues/1744/comments | 0 | 2020-11-30T09:55:00Z | 2024-06-27T11:31:14Z | https://github.com/MonetDB/MonetDB/issues/1744 | 753,329,458 | 1,744 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-03 07:07:25 +0200
From: @drstmane
To: Stratos Idreos <<idreos>>
Version: -- development
Last updated: 2008-07-03 10:19:47 +0200
## Comment 9857
Date: 2008-07-03 19:07:25 +0200
From: @drstmane
make[9]: Entering directory `/net/rig.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/build.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/MonetDB5/src/modules/mal/crackers'
/bin/sh ../../../../libtool --tag=CC --mode=compile icc -no-gcc -fPIC -DHAVE_CONFIG_H -I. -I../../../.. -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers -I../../atoms -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/../../atoms -I../../kernel -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/../../kernel -I../../../mal -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/../../../mal -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB/mapilib -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB/common -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB/gdk -DLIBCRACKERS -we140 -wd1418 -Wall -w2 -std=c99 -O3 -we266 -Werror -wd1418,1419,279,981,810,193,111,1357,1572,1599 -D_REENTRANT -c -o lib_crackers_la-crackers_joins.lo `test -f 'crackers_joins.c' || echo '/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/'`crackers_joins.c
icc -no-gcc -fPIC -DHAVE_CONFIG_H -I. -I../../../.. -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers -I../../atoms -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/../../atoms -I../../kernel -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/../../kernel -I../../../mal -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/../../../mal "-I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB" "-I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB/mapilib" "-I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB" "-I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB/common" "-I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/include/MonetDB/gdk" -DLIBCRACKERS -we140 -wd1418 -Wall -w2 -std=c99 -O3 -we266 -Werror -wd1418,1419,279,981,810,193,111,1357,1572,1599 -D_REENTRANT -c crackers_joins.c -DPIC -o .libs/lib_crackers_la-crackers_joins.o
/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/crackers_joins.mx(1199): error 593: variable "existsHashTableLeft" was set but never used
bit existsHashTableLeft;
^
/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/modules/mal/crackers/crackers_joins.mx(1207): error 593: variable "existsHashTableRight" was set but never used
bit existsHashTableRight;
^
compilation aborted for crackers_joins.c (code 2)
make[9]: *** [lib_crackers_la-crackers_joins.lo] Error 1
make[9]: Leaving directory `/net/rig.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/build.--enable-strict_--disable-debug_--enable-optimize_--disable-assert_CC~icc/MonetDB5/src/modules/mal/crackers'
## Comment 9858
Date: 2008-07-03 22:19:47 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Stratos' fix seems to work.
Thanks.
## Comment 9859
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2009896 at http://sourceforge.net/support/tracker.php?aid=2009896
| M5: crackers_joins.mx fails to compile with icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1743/comments | 0 | 2020-11-30T09:54:57Z | 2024-06-27T11:31:13Z | https://github.com/MonetDB/MonetDB/issues/1743 | 753,329,422 | 1,743 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-03 11:41:21 +0200
From: Luc Touraille <<touraillel>>
To: Lefteris Sidirourgos <<lsidir>>
Version: -- development
Last updated: 2009-11-18 10:52:38 +0100
## Comment 9839
Date: 2008-07-03 11:41:21 +0200
From: Luc Touraille <<touraillel>>
[Jun 2008 release]
A deleted document from a collection where there is more than 1 document is still visible using the collection("mycoll") function.
On Feb 2008 release, the pf:collection function worked correctly, but not the fn:collection function, that produced the same bug.
Stefan reproduced this bug, giving the following trace :
========
$ cat /tmp/MyDoc1.xml
--------
<a/>
========
$ cat /tmp/MyDoc2.xml
--------
<b/>
========
========
$ mclient -lx -s'pf:add-doc("/tmp/MyDoc1.xml","MyDoc1","MyCol")'
--------
========
$ mclient -lx -s'pf:collections()'
--------
<collection updatable="false" size="99 KiB" numDocs="1">MyCol</collection>
========
$ mclient -lx -s'pf:collection("MyCol")'
--------
<a/>
========
$ mclient -lx -g -s'fn:collection("MyCol")'
--------
<?xml version="1.0" encoding="utf-8"?>
<a/>
========
$ mclient -lx -s'pf:documents()'
--------
<document updatable="false" url="/tmp/MyDoc1.xml" collection="MyCol">MyDoc1</document>
========
$ mclient -lx -s'pf:documents("MyCol")'
--------
<document updatable="false" url="/tmp/MyDoc1.xml" collection="MyCol">MyDoc1</document>
========
========
$ mclient -lx -s'pf:del-doc("MyDoc1")'
--------
========
$ mclient -lx -s'pf:collections()'
--------
========
$ mclient -lx -s'pf:collection("MyCol")'
--------
========
$ mclient -lx -g -s'fn:collection("MyCol")'
--------
========
$ mclient -lx -s'pf:documents()'
--------
========
$ mclient -lx -s'pf:documents("MyCol")'
--------
========
========
$ mclient -lx -s'pf:add-doc("/tmp/MyDoc1.xml","MyDoc1","MyCol")'
--------
========
$ mclient -lx -s'pf:add-doc("/tmp/MyDoc2.xml","MyDoc2","MyCol")'
--------
========
$ mclient -lx -s'pf:collections()'
--------
<collection updatable="false" size="99 KiB" numDocs="2">MyCol</collection>
========
$ mclient -lx -s'pf:collection("MyCol")'
--------
<a/><b/>
========
$ mclient -lx -g -s'fn:collection("MyCol")'
--------
<?xml version="1.0" encoding="utf-8"?>
<a/>
,
<?xml version="1.0" encoding="utf-8"?>
<b/>
========
$ mclient -lx -s'pf:documents()'
--------
<document updatable="false" url="/tmp/MyDoc1.xml" collection="MyCol">MyDoc1</document>,
<document updatable="false" url="/tmp/MyDoc2.xml" collection="MyCol">MyDoc2</document>
========
$ mclient -lx -s'pf:documents("MyCol")'
--------
<document updatable="false" url="/tmp/MyDoc2.xml" collection="MyCol">MyDoc2</document>,
<document updatable="false" url="/tmp/MyDoc1.xml" collection="MyCol">MyDoc1</document>
========
========
$ mclient -lx -s'pf:del-doc("MyDoc2")'
--------
========
$ mclient -lx -s'pf:collections()'
--------
<collection updatable="false" size="99 KiB" numDocs="1">MyCol</collection>
========
$ mclient -lx -s'pf:collection("MyCol")'
--------
<a/><b/>
========
$ mclient -lx -g -s'fn:collection("MyCol")'
--------
<?xml version="1.0" encoding="utf-8"?>
<a/>
,
<?xml version="1.0" encoding="utf-8"?>
<b/>
========
$ mclient -lx -s'pf:documents()'
--------
<document updatable="false" url="/tmp/MyDoc1.xml" collection="MyCol">MyDoc1</document>
========
$ mclient -lx -s'pf:documents("MyCol")'
--------
<document updatable="false" url="/tmp/MyDoc1.xml" collection="MyCol">MyDoc1</document>
========
========
$ mclient -lx -s'pf:del-doc("MyDoc1")'
--------
========
$ mclient -lx -s'pf:collections()'
--------
========
$ mclient -lx -s'pf:collection("MyCol")'
--------
========
$ mclient -lx -g -s'fn:collection("MyCol")'
--------
========
$ mclient -lx -s'pf:documents()'
--------
========
$ mclient -lx -s'pf:documents("MyCol")'
--------
========
## Comment 9840
Date: 2008-07-03 14:48:32 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Added test in
pathfinder/tests/BugTracker/Tests/Zombie_document.SF-2009556.*
## Comment 9841
Date: 2008-07-03 22:33:04 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
The problem seems to be "even worse":
* add 2 documents to a single collection "MyCol"
* delete one of them, again
=> + pf:colections(), pf:documents(), & pf:documents("MyCol") correctly show only one remaining document
- pf:collection("MyCol") & fn:collection("MyCol") wrongly show both documents
* stop Mserver
* restart Mserver
=> - all above functions wrongly show *both* documents, again!
This happens both with the (now) default Algebra back-end and with the (old) "milprint_summer" back-end.
## Comment 9842
Date: 2008-07-03 22:34:22 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Might be related to
[ 1976341 ] XQ: leftovers after deleting document
http://sourceforge.net/tracker/index.php?func=detail&aid=1976341&group_id=56967&atid=482468
## Comment 9843
Date: 2008-11-18 11:31:15 +0100
From: @lsidir
Hi,
the test Zombie_document.SF-2009556 seems to be failing not because the bug is still there, but because of some dynamic(?) information in the documents, such as size in kb and URL. I am not aware if and how can we make testweb to ignore these differences. Assigning to Stefan:) I considering this bug fixed though. We just have to manage the tests a little, the same holds for the rest, of the related to this bug, reports.
lefteris
## Comment 9844
Date: 2008-11-18 11:48:52 +0100
From: @drstmane
The URLs are indeed to be ignored --- not trivial with Mtest.py right now, though, I'll check and think about it.
The changes sizes in KB look very suspicious to me --- I would strongly object to ignoring or approving them unless we know for sure why they differ, or better, which size they represent --- I honestly don't know either, yet ...
Moreover, the current output shows an extra
<aap>
Hello World
</aap>
compared to the stable/approved output --- also that needs to be checked before considering this bug fixed ...
## Comment 9845
Date: 2008-12-12 00:02:42 +0100
From: @peterboncz
Lefteris, can you check if the output is correct (the extra <aap>??) and this bug really fixed? If so, close it. If not, re-open it. Thanks!
## Comment 9846
Date: 2008-12-15 16:45:20 +0100
From: @lsidir
Hi, the bug is still around indeed. The bug characteristics are as follows:
* If the mil proc ws_collection_root() is invoked, delete documents still appear
* if the mil proc ws_collection() is invoked, delete documents do not appear.
By investigating a little more, after the second document is deleted the database looks like that:
mil>print(doc_name);
---------------------------------
h alias name
oid str type
---------------------------------
[ 1000000000@0, "MyDoc1" ]
[ 1000000001@0, nil ]
Which is expected. On the other hand,
mil>print(doc_collection);
---------------------------------
h t name
oid oid type
---------------------------------
[ 1@0, 14@0 ]
[ 1000000000@0, 1000000000@0 ]
[ 0@0, 1000000002@0 ]
[ 1000000001@0, 1000000000@0 ]
thus the delete document appears in the tail, which it looks that this is known and correct since the implementation of ws_collection() knows that and has the following two lines of code:
var docs := doct.leftjoin(doc_name).select(str_nil,str_nil); selected existing docs
doc := doch.leftjoin(docs.mirror().leftjoin(doct)); reduced doc to existing docs
thus from the doc_name BAT decides which document still exists, but in the implementation of ws_collection_root this is not the case, since no filtering is happening. Notice that the PRE_Table, after deleting the document and after restarting the logger looks like:
PRE table
[ 0@0 ]
-------------------------------------------------------------------------
h nid size level prop kind tag cont name
void oid int chr oid str str oid type
-------------------------------------------------------------------------
[ 0@0, nil, nil, 'þ', nil, "COLLECTION", nil, nil ]
[ 1@0 ]
-------------------------------------------------------------------------
h nid size level prop kind tag cont name
void void int chr oid str str oid type
-------------------------------------------------------------------------
[ 0@0, 0@0, 4, 'þ', nil, "COLLECTION", nil, 1@0 ]
[ 1@0, 1@0, 1, 'ÿ', nil, "DOCUMENT", nil, 1@0 ]
[ 2@0, 2@0, 0, '\000', 0@0, "ELEMENT", "||a", 1@0 ]
[ 3@0, 3@0, 1, 'ÿ', nil, "DOCUMENT", nil, 1@0 ]
[ 4@0, 4@0, 0, '\000', 1@0, "ELEMENT", "||b", 1@0 ]
thus the elements etc. still exist
I am not sure what is the best way to fix this problem, so I am open to suggestions, I am also not sure what are the steps taken after a document is deleted, so I will need Peter's help on this one
## Comment 9847
Date: 2008-12-16 09:12:06 +0100
From: @lsidir
During the pathfinder skype meeting on Monday 15/12 the solution that was proposed was to apply the docfilter proc after the pf:collection+step. This will fix the fn:collection results. However if a query serializes the results of pf:collection, the delete documents will still appear. This is acceptable since pf:collection was not designed for such use, and users should use the built in functions of XQuery (i.e., fn:collection) rather than pf:collection.
In addition docfilter should break to 2 new functions to separate the "swizzling" from the filtering.
## Comment 9848
Date: 2009-02-15 21:58:24 +0100
From: @drstmane
Lefteris,
what is the status of this one?
Stefan
## Comment 9849
Date: 2009-02-16 01:08:10 +0100
From: @drstmane
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugTracker/Zombie_document.SF-2009556.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_BugTracker/Zombie_document.SF-2009556.out.00.html
## Comment 9850
Date: 2009-04-07 10:48:22 +0200
From: @peterboncz
I think we should give an run-time error in the serializer if the collection root gets serialized..
## Comment 9851
Date: 2009-04-07 11:34:42 +0200
From: @grobian
debug spam, sorry for the noise.
## Comment 9852
Date: 2009-11-16 22:29:36 +0100
From: @drstmane
the test has been failing at least since 2009-01-01, now resulting in a timeout
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_BugTracker/Zombie_document.SF-2009556.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_BugTracker/Zombie_document.SF-2009556.out.00.html
## Comment 9853
Date: 2009-11-17 01:05:39 +0100
From: @peterboncz
the output differs as follows:
- the collection function given an error on a nonexistent collection, which is ok
- the attenpt to serialize a collection gives an error - which is ok
approved the output, this test seems to work correctly on my platform
## Comment 9854
Date: 2009-11-17 09:56:57 +0100
From: @drstmane
Thanks!
I made the test's output invariant (independent of local paths) by loading documents from the MonetDB web site instead of from local files,
and moved it to be first in this directory, to not require delete_all_docs() to empty the DB --- the latter might take several minutes to remove all docs accumulated by the numerous tests in this directory.
Seems to work fine, now.
Can be closed, once nightly testing confirms this.
## Comment 9855
Date: 2009-11-18 10:52:37 +0100
From: @drstmane
confirmed.
closing.
## Comment 9856
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2009556 at http://sourceforge.net/support/tracker.php?aid=2009556
| XQ: "Zombie" document in collection | https://api.github.com/repos/MonetDB/MonetDB/issues/1742/comments | 0 | 2020-11-30T09:54:54Z | 2024-06-27T11:31:12Z | https://github.com/MonetDB/MonetDB/issues/1742 | 753,329,377 | 1,742 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-03 09:19:45 +0200
From: Wouter Alink <<alink>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-10-08 09:04:12 +0200
## Comment 9832
Date: 2008-07-03 09:19:45 +0200
From: Wouter Alink <<alink>>
(MonetDB-0.24, algebra)
see below
-bash-3.2$ cat aap.xml
<aap>
<mies>1</mies>
<mies>2</mies>
</aap>
-bash-3.2$ cat noot.xml
<aap>
<mies>3</mies>
<mies>4</mies>
</aap>
-bash-3.2$ cat beer.xml
<aap>
<mies>5</mies>
<mies>6</mies>
</aap>
-bash-3.2$ cat test_order.xq
for $p in ("/tmp/test_order/aap" ,"/tmp/test_order/beer", "/tmp/test_order/noot")
let $name := concat($p,".xml")
return pf:add-doc($name, $name)
<>
element result {
for $p in ("/tmp/test_order/aap" ,"/tmp/test_order/beer", "/tmp/test_order/noot")
return element test {
attribute name {$p},
let $dn := concat($p, ".xml")
return if (exists(pf:documents()[.=$dn]))
then
let $dc := doc($dn)
for $i in $dc//mies
return
element mies {$i/text()}
else ()
}
}
<>
for $p in ("/tmp/test_order/aap" ,"/tmp/test_order/beer", "/tmp/test_order/noot")
let $name := concat($p,".xml")
return pf:del-doc($name)
results in:
mclient -lxq test_order.xq
<result>
<test name="/tmp/test_order/aap">
<mies>1</mies>
<mies>5</mies>
</test>
<test name="/tmp/test_order/beer">
<mies>3</mies>
<mies>2</mies>
</test>
<test name="/tmp/test_order/noot">
<mies>6</mies>
<mies>4</mies>
</test>
</result>
which is obviously not what was intended...
## Comment 9833
Date: 2008-08-08 15:42:46 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Test added as tests/BugTracker test_order.SF-2009467.
Wouter can you check that I did the output correctly (I think I did)?
Assigning to Jan since it looks like an PF-internal issue.
## Comment 9834
Date: 2008-08-08 18:51:00 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
yes, i think you did too. thanks.
## Comment 9835
Date: 2008-09-05 17:42:26 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
The steps $dc//mies and $i/text() are responsible for the incorrect behavior. In the stable branch pathfinder plans for both steps to return their results in item|iter order (note that the HEAD uses a slightly different plan).
Instead of ordering by cont|pre|iter the 'mies' descendant step returns its result in the incorrect pre|cont|iter order. The following text step then gets its input in a different order as it expects and totally screws up the output order in the end.
Stefan, could you please have a look at the step code -- it is important that cont is the major ordering and pre the minor.
## Comment 9836
Date: 2008-10-08 19:17:17 +0200
From: @drstmane
Seems to work fine with the MPS version; I'll check the ALG version ...
## Comment 9837
Date: 2008-10-08 21:04:12 +0200
From: @drstmane
Fixed in CVS:
In case the result of loop_lifted_X_step...() is requested to be in
[item,iter] order, we actually need to preserver the fragment-clustering,
i.e., effectively return [cont,item,iter] order
Thanks, for the detailed analysis, Jan!!
## Comment 9838
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2009467 at http://sourceforge.net/support/tracker.php?aid=2009467
| XQ: nodes change places | https://api.github.com/repos/MonetDB/MonetDB/issues/1741/comments | 0 | 2020-11-30T09:54:51Z | 2024-06-27T11:31:11Z | https://github.com/MonetDB/MonetDB/issues/1741 | 753,329,350 | 1,741 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-07-01 08:06:34 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2008-07-03 03:26:04 +0200
## Comment 9828
Date: 2008-07-01 08:06:34 +0200
From: @drstmane
While working fine until yesterday, compiling buildtools fails on titan (with GNU's gcc --- builstools are always compiled with gcc) since tonight.
For details, see
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/buildtools/.Int.64.64.d-RedHat4WS..2008.07.01_00-09-02/make.out.html
Were there any other changes to the machine's configuration other installing a new version of icc?
## Comment 9829
Date: 2008-07-01 09:04:46 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
removed icc includes from the directories linked to /usr/local seems to solve the compilation problem.
## Comment 9830
Date: 2008-07-03 15:26:04 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Works fine, again.
Thanks.
## Comment 9831
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2007408 at http://sourceforge.net/support/tracker.php?aid=2007408
| compiling buildtools fails on "titan" | https://api.github.com/repos/MonetDB/MonetDB/issues/1740/comments | 0 | 2020-11-30T09:54:49Z | 2024-06-27T11:31:10Z | https://github.com/MonetDB/MonetDB/issues/1740 | 753,329,316 | 1,740 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-26 09:24:13 +0200
From: @arjenderijke
To: @sjoerdmullender
Version: -- development
Last updated: 2008-06-26 04:50:49 +0200
## Comment 9824
Date: 2008-06-26 09:24:13 +0200
From: @arjenderijke
When i run a long (> 10 min) query, using mclient with the -t option, the reported time is completely wrong. I use a query like: cat datafile|mclient -lsql -s"copy records into table from stdin" -i -t
The result for the timer are for example:
Timer 1214318792583.995 msec or Timer -16852.-61 msec
This happens on a version compiled with a checkout of the current branch of last Tuesday and on the June 2008 release candidate of last week. The machines where a cluster machine and an Athlon i386.
## Comment 9825
Date: 2008-06-26 10:11:17 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Clearly overflow.
I changed the code to use a 64 bit integer and to calculate times relative to a local epoch so that the chance of overflow is reduced significantly.
Arjen, can you test with a new build of mclient from the stable branch?
A test would take too long to run, so no test added.
## Comment 9826
Date: 2008-06-26 16:50:49 +0200
From: @arjenderijke
Logged In: YES
user_id=1836138
Originator: YES
I build the stable code and running a query gave as results: Timer 1687355.203 msec and Timer 1981582.464 msec The second one i used the time command and that gave result: real 33m45.522 user 10m19.401s sys 2m3.811s
So the overflow bug is solved.
## Comment 9827
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2002962 at http://sourceforge.net/support/tracker.php?aid=2002962
| mclient -t returns wrong results | https://api.github.com/repos/MonetDB/MonetDB/issues/1739/comments | 0 | 2020-11-30T09:54:46Z | 2024-06-27T11:31:09Z | https://github.com/MonetDB/MonetDB/issues/1739 | 753,329,281 | 1,739 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-21 11:27:09 +0200
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-07-30 12:30:45 +0200
## Comment 9818
Date: 2008-06-21 11:27:09 +0200
From: @romulogoncalves
If I run the following example against a M5 server with option sql_debug=64
CREATE FUNCTION f2(deg float, truncat int , precision int)
RETURNS varchar(32)
BEGIN
DECLARE
d float,
nd int,
np int,
q varchar(10),
t varchar(16);
--
SET t = '00:00:00.0';
IF (precision < 1)
THEN SET precision = 1;
END IF;
IF (precision > 10)
THEN SET precision = 10;
END IF;
SET np = 0;
WHILE (np < precision-1) DO
SET t = t||'0';
SET np = np + 1;
END WHILE;
SET d = ABS(deg/15.0);
-- degrees
SET nd = FLOOR(d);
SET q = LTRIM(CAST(nd as varchar(2)));
SET t = MS_STUFF(t,3-LENGTH(q),LENGTH(q), q);
-- minutes
SET d = 60.0 * (d-nd);
SET nd = FLOOR(d);
SET q = LTRIM(CAST(nd as varchar(4)));
SET t = MS_STUFF(t,6-LENGTH(q),LENGTH(q), q);
-- seconds
SET d = MS_ROUND( 60.0 * (d-nd),precision,truncat );
SET q = LTRIM(STR(d,precision));
SET t = MS_STUFF(t,10+precision-LENGTH(q),LENGTH(q), q);
-- SET d = 60.0 * (d-nd);
-- SET q = LTRIM(STR(d,3));
-- SET t = MS_STUFF(t,13-LENGTH(q),LENGTH(q), q);
--
RETURN(t);
END;
SELECT f2(1,2,3);
--SELECT fIAUFromEq(p.ra,p."dec") FROM PhotoPrimary as p;
drop function f2;
I get the following errors:
MAPI = monetdb@localhost:50000
QUERY = SELECT f2(1,2,3);
ERROR = !TypeException:user.f2[120]:'calc.str' undefined in: _135:any := calc.str(_133:dbl, _134:int)
mdb> Ad := nil:dbl;
mdb>EOD
MAPI = monetdb@localhost:50000
QUERY = SELECT f2(1,2,3);
ERROR = !TypeException:user.s0_1[183]:'calc.str' undefined in: _171:any := calc.str(_169:dbl, _170:int)
Plus the mdb prompt:
mdb> _4 := A0;
Romulo
## Comment 9819
Date: 2008-06-22 16:46:56 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
test added at:
sql/src/test/BugTracker/Tests/mdb_starts_with_sql_debug_64.SF-1999354.py
## Comment 9820
Date: 2008-06-24 13:44:36 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
The test was improved and now the mserver is crashing....
To the test I added 3 statements:
create table
select on this table to then call the function f2
drop table
The mserver crashes when we drop the table...
Romulo
## Comment 9821
Date: 2008-07-19 19:28:49 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
The sql_dehttp://sourceforge.net/support/tracker.php?aid=64, 32 should be moved to proper environment variables.
## Comment 9822
Date: 2008-07-30 12:30:45 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
--readonly and --single-user have been added to the system
escape to debugger fixed
## Comment 9823
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1999354 at http://sourceforge.net/support/tracker.php?aid=1999354
| mdb starts with sql_debug 64 | https://api.github.com/repos/MonetDB/MonetDB/issues/1738/comments | 0 | 2020-11-30T09:54:44Z | 2024-06-27T11:31:08Z | https://github.com/MonetDB/MonetDB/issues/1738 | 753,329,251 | 1,738 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-19 11:39:39 +0200
From: @romulogoncalves
To: @mlkersten
Version: -- development
Last updated: 2008-07-13 05:32:33 +0200
## Comment 9813
Date: 2008-06-19 11:39:39 +0200
From: @romulogoncalves
Just run the following sql code:
CREATE FUNCTION degrees(r double)
RETURNS double
RETURN r*180/pi();
CREATE FUNCTION fHtm(x float, y float, z float, radius float)
RETURNS TABLE (
HtmIDStart bigint ,
HtmIDEnd bigint
)
BEGIN
RETURN TABLE (SELECT 1,2);
END;
create table t1 (id int, age int);
CREATE FUNCTION f1(ra float, deci float,
radius float, zoo int)
RETURNS TABLE (
fieldID bigint ,
distance float -- distance in arc minutes
)
BEGIN
--
DECLARE nx float,ny float,nz float;
SET nx = ra;
SET ny = ra;
SET nz = deci;
DECLARE TABLE cover(
htmidStart bigint, htmidEnd bigint
);
INSERT into cover
SELECT htmidStart, htmidEnd
FROM fHtm(nx,ny,nz,radius);
RETURN TABLE(SELECT age, (2*DEGREES(ASIN(sqrt(power(nx-id,2)+power(ny-id,2)+power(nz-id,2))/2))*60) as val
FROM cover H, t1 F );
END;
select * from f1(1,2,3,4) n;
drop function f1;
drop table t1;
drop function fHtm;
The error is:
MAPI = monetdb@localhost:50000
QUERY = select * from f1(1,2,3,4) n;
ERROR = !TypeException:user.f1[26]:'bat.new' undefined in: _184:bat[:str,:BAT] := bat.new(_185:str, _186:bat[:oid,:dbl])
!TypeException:user.s0_1[35]:'bat.new' undefined in: _240:bat[:str,:BAT] := bat.new(_241:str, _242:bat[:oid,:dbl])
!TypeException:user.s0_1[38]:type mismatch bat[:oid,:dbl] := bat[:str,:BAT]
!TypeException:user.s0_1[40]:'sql.columnBind' undefined in: _83:bat[:oid,:lng] := sql.columnBind(_81:bat[:oid,:dbl], _82:str)
!TypeException:user.s0_1[49]:'sql.columnBind' undefined in: _94:bat[:oid,:lng] := sql.columnBind(_81:bat[:oid,:dbl], _93:str)
!MALException:bat.insert:Cannot access descriptor
!WARNING: BATdescriptor: range error 18294344
Romulo
## Comment 9814
Date: 2008-06-30 17:50:59 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
Test added:
sql/src/tests/BugTracker/Tests/bat_descriptor_problem.SF-199764.sql
## Comment 9815
Date: 2008-07-11 13:00:42 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
this problems is related to the optimizers reduce and aliases. So reassigning.
## Comment 9816
Date: 2008-07-13 17:32:33 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Solved by making the return type of TABLE returning functions in SQL more precise.
The area remains a source of potential problems. TYPE_bat should be used sparingly.
## Comment 9817
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1997643 at http://sourceforge.net/support/tracker.php?aid=1997643
| batdescriptor problem | https://api.github.com/repos/MonetDB/MonetDB/issues/1737/comments | 0 | 2020-11-30T09:54:41Z | 2024-06-27T11:31:07Z | https://github.com/MonetDB/MonetDB/issues/1737 | 753,329,215 | 1,737 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-19 09:30:12 +0200
From: @drstmane
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2008-07-16 06:46:02 +0200
## Comment 9804
Date: 2008-06-19 09:30:12 +0200
From: @drstmane
Already for some time, test
MonetDB5/src/modules/mal/Tests/remote03.mal
fails with
!MALException:remote.get:no such object '�)�;'
!MALException:user.main[32]:Exception not catched
## Comment 9805
Date: 2008-06-19 09:30:52 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
See, e.g.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.64.64.d-Fedora8/src_modules_mal/remote03.out.00.html
## Comment 9806
Date: 2008-06-19 11:11:51 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
This is the relevant code snippet:
str RMTserveget(MalBlkPtr mb, MalStkPtr stk, InstrPtr pci) {
int i;
str name;
name = (str)getArgValue(stk, pci, 1);
i = findVariable(mb, name);
if (i < 0)
throw(MAL, "remote.serveget", "no such object '%s'", name);
either, garbage was given as argument, or retrieving the first argument (like this) doesn't work (any more).
## Comment 9807
Date: 2008-06-19 11:15:20 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
garbage can be passed as argument (does the parser even accept that?), if:
str RMTget(MalBlkPtr mb, MalStkPtr stk, InstrPtr pci) {
str conn, ident, tmp;
ident = (str)getArgValue(stk, pci, 2);
if (isIdentifier(ident) < 0)
throw(ILLARG, "remote.get", "identifier expected, got '%s'", ident);
/* perform the get */
rethrow("remote.get", tmp, RMTinternalget(c->mconn,
ident, &stk->stk[getArg(pci, 0)]));
ident in the above code is valid for isIdentifier(), but in fact garbage.
## Comment 9808
Date: 2008-06-19 15:29:16 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
The test fails since Wednesday June 4 2008, i.e., after checkins on Tuesday June 3 2008.
## Comment 9809
Date: 2008-06-19 15:37:13 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
Solaris shows an interesting behaviour. In contrast to all other platforms, on Solaris a value is printed (io.print), containing "bla". While this is certainly wrong (there is no output), the problematic part here is that the io.print should never be called, since an exception is thrown.
## Comment 9810
Date: 2008-06-19 15:48:24 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
I think I found the problem. The "object name" comes from a Mapi handle, which is closed. Hence the pointer is invalid. I now properly copy the string, which should solve the issue.
A few questions remain:
- How can Solaris print a value
- How/why can the parser accept the garbage
I checked in my fix on the Stable branch. Mtest successfully completes here on my system.
## Comment 9811
Date: 2008-07-16 06:46:02 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed by Fabian(?).
Thanks!
## Comment 9812
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1997535 at http://sourceforge.net/support/tracker.php?aid=1997535
| M5: test src/modules/mal/Tests/remote03.mal fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1736/comments | 0 | 2020-11-30T09:54:38Z | 2024-06-27T11:31:06Z | https://github.com/MonetDB/MonetDB/issues/1736 | 753,329,192 | 1,736 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-19 06:55:14 +0200
From: David Wung <<fivecolor>>
To: @njnes
Version: -- development
Last updated: 2008-06-19 07:57:06 +0200
## Comment 9801
Date: 2008-06-19 06:55:14 +0200
From: David Wung <<fivecolor>>
When i did TPC-H test, it seemed index doesn't work.
repeat step:
1. create tables by file 'c.sql-dec-primary' below 'MonetDB-SQL/sql/src/benchmarks/tpch'
2. generate data by 'dbgen' below 'MonetDB-SQL/sql/src/benchmarks/tpch/dbgen'. eg. './dbgen -s 1'
3. execute 'run.all' below 'MonetDB-SQL/sql/src/benchmarks/tpch', and record query time.
4. create indexes by file 'create_index.sql' in attachment.
5. repeat step 3.
You can find that whether or not index created, influence on query time is paltry.
## Comment 9802
Date: 2008-06-19 07:57:06 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
This is to be expected as the indices you create are already created to support the primary keys. I you want to improve the performance, also create foreign keys. This can be done using the create script c.sql-dec-primary-foreign or on your current setup using the alter.sql script.
## Comment 9803
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1997434 at http://sourceforge.net/support/tracker.php?aid=1997434
| SQL: Index is of no effect | https://api.github.com/repos/MonetDB/MonetDB/issues/1735/comments | 0 | 2020-11-30T09:54:36Z | 2024-06-28T13:29:22Z | https://github.com/MonetDB/MonetDB/issues/1735 | 753,329,158 | 1,735 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-18 06:40:21 +0200
From: Sam Mason <<sam_mason>>
To: @njnes
Version: -- development
Last updated: 2008-08-02 07:09:51 +0200
## Comment 9798
Date: 2008-06-18 18:40:21 +0200
From: Sam Mason <<sam_mason>>
As far as I'm aware the SQL spec requires the RDMS to verify that data already existing within a table is valid when applying new constraints. This check currently appears to be missing from monetdb.
CREATE TABLE foo (i INT);
INSERT INTO foo (i) VALUES (NULL);
ALTER TABLE foo ALTER COLUMN i SET NOT NULL;
I'd expect this last command to fail. Running INSERT again causes monet to recognize the constraint but only for the new data.
SELECT i FROM foo;
verifies that there is a null value still in the column.
## Comment 9799
Date: 2008-08-02 19:09:51 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Added test to src/test/BugTracker/Tests/alter_table_set_not_null.SF-1997030.sql
The missing code was added to sql_schema.mx
## Comment 9800
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1997030 at http://sourceforge.net/support/tracker.php?aid=1997030
| SQL: NOT NULL constraint is not checked when applied to | https://api.github.com/repos/MonetDB/MonetDB/issues/1734/comments | 0 | 2020-11-30T09:54:33Z | 2024-06-27T11:31:04Z | https://github.com/MonetDB/MonetDB/issues/1734 | 753,329,113 | 1,734 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-18 06:33:55 +0200
From: Sam Mason <<sam_mason>>
To: @njnes
Version: -- development
Last updated: 2009-09-20 10:07:59 +0200
## Comment 9793
Date: 2008-06-18 18:33:55 +0200
From: Sam Mason <<sam_mason>>
Adding a primary key to a table containing ~30million rows causes the disks to thrash and the machine to perform little useful work.
I'm running a nightly stable release from 2008-June-16.
## Comment 9794
Date: 2008-11-17 15:58:30 +0100
From: @romulogoncalves
I do not have enough information to debug or at least create a test for this bug.
Niels, what should we do about it?
## Comment 9795
Date: 2009-02-09 15:11:18 +0100
From: @romulogoncalves
I am still waiting for information to create a test to cover this bug.
Or should I consider this bug invalid?
Niels?
## Comment 9796
Date: 2009-09-20 22:07:58 +0200
From: @njnes
Primary key checking has been improved (and more fixes are coming). As this is a performance issue, I'm closing this without a test script
## Comment 9797
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1997025 at http://sourceforge.net/support/tracker.php?aid=1997025
| SQL:adding a primary key causes HDD to thrash | https://api.github.com/repos/MonetDB/MonetDB/issues/1733/comments | 0 | 2020-11-30T09:54:31Z | 2024-06-28T13:29:21Z | https://github.com/MonetDB/MonetDB/issues/1733 | 753,329,081 | 1,733 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-17 12:05:02 +0200
From: @peterboncz
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2008-06-18 10:45:47 +0200
## Comment 9785
Date: 2008-06-17 12:05:02 +0200
From: @peterboncz
when algebra is default, the XRPC admin GUI does not work anymore, and blocks all subsequent queries.
The problem is that XRPC should continue to use mps, whatever the compiler choice is for mapi sessions. This should be enforced in the code.
## Comment 9786
Date: 2008-06-17 12:24:23 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Enforcing the use of (fall-back to) MPS for features that are no yet supported by / ported to ALG is an interesting idea
(in the release branch, only; otherwise we might forget to port them for the next release).
... at least for features whose use can easily be detected automatically before query compilation ...
Any ideas, how/where to do this for XRPC (I'm an XRPC illiterate)?
Would any other features be suitable for "automatic detection and fall-back to MPS"?
Cannot imagine how to do it for, e.g., pre-compiled MIL modules and/or recusive functions.
Standoff extensions seem to a be simple candidate: `--set standoff=enabled` triggers `--set xquery_backend=milprint_summer`.
## Comment 9787
Date: 2008-06-17 14:41:53 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
The attached patch (to be applied to the XQuery_0-24 release branch, but not to be propagated to the development trunk) does the following for/with the StandOff extensions:
In case
(1) Pathfinder is configured with --with-default-backend=algebra AND
(2) StandOff extensions are enabled at runtime via `Mserver --set standoff=enabled` and/or `pf --enable-standoff` AND
(3) the Algebra back-end is NOT explicitly requested via `Mserver --set xquery_backend=algebra`, `pf -A`, or `mclient -G`
then, Pathfinder automatically falls back to thew "milprint_summer" back-end to enable support for the StandOff extensions.
I don't know, yet, how to achieve a similar setup for XRPC or at least the admininstrative console.
File Added: StandOff-MPS-patch.diff
## Comment 9788
Date: 2008-06-17 19:08:06 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: YES
fixed in stable
## Comment 9789
Date: 2008-06-17 21:28:44 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Thanks for the fix, Peter.
Shall we skip the propagation of these fixes to the development trunk to keep us reminded that XRPC still need to be ported to the Algebra back-end?
Or shall we simply port them "for convenience"?
## Comment 9790
Date: 2008-06-17 23:31:18 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
You say "fixed in stable" but I only see a checkin in the current branch.
## Comment 9791
Date: 2008-06-18 10:45:47 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Peter back-ported his fix to the XQuery_0-24 branch.
See also
https://sourceforge.net/mailarchive/forum.php?thread_name=DMEDIAKACKDOOIPCMFAJGEPPCHAA.p.a.boncz%40chello.nl&forum_name=monetdb-developers
## Comment 9792
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1995879 at http://sourceforge.net/support/tracker.php?aid=1995879
| algebra kills admin GUI | https://api.github.com/repos/MonetDB/MonetDB/issues/1732/comments | 0 | 2020-11-30T09:54:28Z | 2024-06-27T11:31:02Z | https://github.com/MonetDB/MonetDB/issues/1732 | 753,329,055 | 1,732 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-14 07:09:56 +0200
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-06-17 11:30:25 +0200
## Comment 9782
Date: 2008-06-14 19:09:56 +0200
From: @romulogoncalves
To simulate the crash just create the table:
CREATE TABLE PlateX(
plateID bigint NOT NULL,
spRerun int NOT NULL,
mjd int NOT NULL,
plate smallint NOT NULL,
tile smallint NOT NULL,
mapMjd int NOT NULL,
nExp smallint NOT NULL,
tai real NOT NULL,
raBoresight float NOT NULL,
decBoresight float NOT NULL,
taiHMS varchar(64) NOT NULL,
expTime real NOT NULL,
expTimeB1 real NOT NULL,
expTimeB2 real NOT NULL,
expTimeR1 real NOT NULL,
expTimeR2 real NOT NULL,
helioRV real NOT NULL,
ra real NOT NULL,
"dec" real NOT NULL,
cx float NOT NULL,
cy float NOT NULL,
cz float NOT NULL,
htmID bigint NOT NULL,
sn1_0 real NOT NULL,
sn1_1 real NOT NULL,
sn1_2 real NOT NULL,
sn2_0 real NOT NULL,
sn2_1 real NOT NULL,
sn2_2 real NOT NULL,
dateObs varchar(12) NOT NULL,
timeSys varchar(8) NOT NULL,
quality varchar(12) NOT NULL,
name varchar(32) NOT NULL,
program varchar(16) NOT NULL,
version varchar(64) NOT NULL,
observer varchar(64) NOT NULL,
camVer varchar(64) NOT NULL,
spec2DVer varchar(64) NOT NULL,
utilsVer varchar(64) NOT NULL,
spec1DVer varchar(64) NOT NULL,
readVer varchar(64) NOT NULL,
combVer varchar(64) NOT NULL,
extinction_u real NOT NULL,
extinction_g real NOT NULL,
extinction_r real NOT NULL,
extinction_i real NOT NULL,
extinction_z real NOT NULL,
rOffset1 real NOT NULL,
rSigma1 real NOT NULL,
grOff1 real NOT NULL,
grSigma1 real NOT NULL,
rOffset2 real NOT NULL,
rSigma2 real NOT NULL,
grOff2 real NOT NULL,
grSigma2 real NOT NULL,
sfd_used tinyint NOT NULL,
xygrSig1 real NOT NULL,
xygrSig2 real NOT NULL,
mpgrSig1 real NOT NULL,
mpgrSig2 real NOT NULL,
mpgrOff1 real NOT NULL,
mpgrOff2 real NOT NULL,
isPrimary tinyint NOT NULL,
cartridgeID smallint NOT NULL,
plateVersion varchar(32) NOT NULL,
haMin real NOT NULL,
haMax real NOT NULL,
mjdDesign int NOT NULL,
theta real NOT NULL,
fscanVersion varchar(32) NOT NULL,
fmapVersion varchar(32) NOT NULL,
fscanMode varchar(32) NOT NULL,
fscanSpeed int NOT NULL,
programType int NOT NULL,
programName varchar(32) NOT NULL,
loadVersion int NOT NULL,
expID blob NULL,
CONSTRAINT pk_PlateX_plateID PRIMARY KEY
(
plateID
)
);
Load the file in attach. This file contains one line for insertion which will crash the mserver.
The command to insert used was:
COPY 1 RECORDS INTO PlateX from '/ufs/goncalve/SkyServer/skyserver/PlateX.out' USING DELIMITERS '\t', '\n';
the crash is:
>[New Thread 4060334992 (LWP 20079)]
[New Thread 4056136592 (LWP 20080)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 4056136592 (LWP 20080)]
0x0044c3d7 in memset () from /lib/libc.so.6
Missing separate debuginfos, use: debuginfo-install bzip2.i386 e2fsprogs.i386 glibc.i686 keyutils.i386 krb5.i386 libselinux.i386 ncurses.i386 openssl.i686 pcre.i386 readline.i386 zlib.i386
Romulo
## Comment 9783
Date: 2008-06-17 11:30:25 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
added test to BugTracker/copy_into_crash.SF-1993999.sql
## Comment 9784
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1993999 at http://sourceforge.net/support/tracker.php?aid=1993999
| copy into platex | https://api.github.com/repos/MonetDB/MonetDB/issues/1731/comments | 0 | 2020-11-30T09:54:24Z | 2024-06-28T13:29:21Z | https://github.com/MonetDB/MonetDB/issues/1731 | 753,329,005 | 1,731 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-14 05:38:29 +0200
From: @mlkersten
To: @njnes
Version: -- development
Last updated: 2008-06-16 12:42:41 +0200
## Comment 9777
Date: 2008-06-14 17:38:29 +0200
From: @mlkersten
Confirmation of bug reported by Rt Ibmer:
select avg(1);
crashes the mserver.
## Comment 9778
Date: 2008-06-14 18:40:21 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: YES
The bug does not appear on Stable, so it will resolve
when the patches are rolled forward.
## Comment 9779
Date: 2008-06-16 12:42:41 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
test has been added in src/test/bugs
## Comment 9780
Date: 2009-02-16 19:13:59 +0100
From: @drstmane
for the records: test is in sql/src/test/bugs/Tests/aggr_single_value.*
## Comment 9781
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1993961 at http://sourceforge.net/support/tracker.php?aid=1993961
| SQL: avg(1) crashes server | https://api.github.com/repos/MonetDB/MonetDB/issues/1730/comments | 0 | 2020-11-30T09:54:21Z | 2024-06-27T11:31:00Z | https://github.com/MonetDB/MonetDB/issues/1730 | 753,328,959 | 1,730 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-14 11:40:16 +0200
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-06-17 11:26:53 +0200
## Comment 9773
Date: 2008-06-14 11:40:16 +0200
From: @romulogoncalves
If I use the algebra version (mclient -G) and I run the following queries the mserver crashes:
create table t1(id int, age int);
create view v1 as select * from t1 where id = 0;
create view v2 as select * from v1 where age =1;
select * from v2 LIMIT 10;
drop view v2;
drop view v1;
drop table t1;
It seems it is looking for a persistent BAT from a view...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 4056136592 (LWP 11694)]
0xf220fe28 in bind_col (tr=0x86c66b8, c=0x9380210, access=0) at /ufs/goncalve/MonetDB/stable/sql/src/storage/bat/bat_storage.mx:190
190 if (isTemp(c) || access == RD_INS || !bat->bid) {
(gdb) p bat
$1 = (sql_delta *) 0x0
(gdb) up
1 0xf2153e85 in mvc_bind (m=0x9310d48, sname=0x956c178 "sys", tname=0x956c1d8 "v1", cname=0x956c238 "age", access=0)
at /ufs/goncalve/MonetDB/stable/sql/src/backends/monet5/sql.mx:1286
1286 b = store_funcs.bind_col(tr, c, access);
(gdb)
## Comment 9774
Date: 2008-06-14 11:45:29 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
A test was added at:
sql/src/test/BugTracker/Tests/nested_views_algebra_version.SF-1993765.sql
Romulo
## Comment 9775
Date: 2008-06-17 11:26:53 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
fixed bug in recursive view handling
## Comment 9776
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1993765 at http://sourceforge.net/support/tracker.php?aid=1993765
| nested views algebra version | https://api.github.com/repos/MonetDB/MonetDB/issues/1729/comments | 0 | 2020-11-30T09:54:19Z | 2024-06-27T11:30:59Z | https://github.com/MonetDB/MonetDB/issues/1729 | 753,328,925 | 1,729 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-12 02:36:01 +0200
From: Wouter Alink <<alink>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-06-19 07:24:37 +0200
## Comment 9769
Date: 2008-06-12 14:36:01 +0200
From: Wouter Alink <<alink>>
(nightly build, stable, June 11, 2008, algebra-backend)
The following query:
doc("test.xml")//*[@mies and @kees and
(@name[ends-with(lower-case(.),'.doc')]
or a/beer[.="noot"])
and not(a/beer)
]
complains about:
!fatal error: attribute `iter' referenced in join not found
when compiling the query with 'pf -A'
## Comment 9770
Date: 2008-06-13 14:51:38 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
Fixed in CVS -- Testing will show us tomorrow whether the fix was more harmful to other queries than anticipated.
## Comment 9771
Date: 2008-06-19 19:24:37 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Added test (compilation only) in pathfinder/tests/BugTracker/Tests/iter_in_join.SF-1991938.*
Appears to work fine.
Closing.
## Comment 9772
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1991938 at http://sourceforge.net/support/tracker.php?aid=1991938
| XQ: iter in join | https://api.github.com/repos/MonetDB/MonetDB/issues/1728/comments | 0 | 2020-11-30T09:54:16Z | 2024-06-27T11:30:58Z | https://github.com/MonetDB/MonetDB/issues/1728 | 753,328,880 | 1,728 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-12 11:30:34 +0200
From: Wouter Alink <<alink>>
To: Wouter Alink <<alink>>
Version: -- development
Last updated: 2009-11-12 07:09:31 +0100
## Comment 9757
Date: 2008-06-12 11:30:34 +0200
From: Wouter Alink <<alink>>
(stable nightly build, compiled from supersourcetarball, June 11, 2008)
The following query takes about 35 minutes to compile (and I have reason to believe it was also the reason why the machine crashed after it was executed a few times):
for $run in pf:collection("log.xml")//run
let $successCount := if ($run/success) then count($run/success/task) else 0
let $failureCount := if ($run/failure) then count($run/failure/task) else 0
let $nooutputCount := if ($run/nooutput) then (if ($run/nooutput/@count) then zero-or-one($run/nooutput/@count) else 0) + count($run/nooutput/task) else 0
let $totalTasks := $successCount + $failureCount + $nooutputCount
return <run>
{ $run/@tool }
{ for $v in $run/prepared/date/@unixtime[. > 0] return attribute preparation {$v - exactly-one($run/started/date/@unixtime)} }
{ for $v in $run/executed/date/@unixtime[. > 0] return attribute execution {$v - exactly-one($run/prepared/date/@unixtime)} }
{ for $v in $run/validated/date/@unixtime[. > 0] return attribute validation {$v - exactly-one($run/executed/date/@unixtime)} }
{ for $v in $run/committed/date/@unixtime[. > 0] return attribute commit {$v - exactly-one($run/validated/date/@unixtime)} }
{ for $v in $run/prepared/date/@unixtime[. > 0 and $totalTasks > 0] return attribute preparationPerTask {($v - exactly-one($run/started/date/@unixtime)) div $totalTasks} }
{ for $v in $run/executed/date/@unixtime[. > 0 and $totalTasks > 0] return attribute executionPerTask {($v - exactly-one($run/prepared/date/@unixtime)) div $totalTasks} }
{ for $v in $run/validated/date/@unixtime[. > 0 and $totalTasks > 0] return attribute validationPerTask {($v - exactly-one($run/executed/date/@unixtime)) div $totalTasks} }
{ for $v in $run/committed/date/@unixtime[. > 0 and $totalTasks > 0] return attribute commitPerTask {($v - exactly-one($run/validated/date/@unixtime)) div $totalTasks} }
{attribute allowedExecution {exactly-one($run/allowedExecutionTime) * 1000}}
{attribute successCount {$successCount}}
{attribute failureCount {$failureCount}}
{attribute nooutputCount {$nooutputCount}}
{attribute totalTasks {$totalTasks}}
</run>
but, as you might have noticed the query is not written in a very nice way... Therefore i tried to rewrite the query to the (hopefully) equivalent:
for $run in pf:collection("log.xml")//run
let $successCount := count($run/success/task)
let $failureCount := count($run/failure/task)
let $nooutputCount := if ($run/nooutput/@count) then exactly-one($run/nooutput/@count) cast as xs:integer else 0 + count($run/nooutput/task)
let $totalTasks := ($successCount + $failureCount + $nooutputCount) cast as xs:integer
let $started := $run/started/date/@unixtime cast as xs:integer?
let $prepared := $run/prepared/date/@unixtime cast as xs:integer?
let $executed := $run/executed/date/@unixtime cast as xs:integer?
let $validated := $run/validated/date/@unixtime cast as xs:integer?
let $committed := $run/committed/date/@unixtime cast as xs:integer?
return element { "run" } {
$run/@tool,
if ($prepared > 0) then attribute preparation { $prepared - $started } else (),
if ($executed > 0) then attribute execution { $executed - $prepared } else (),
if ($validated > 0) then attribute validation { $validated - $executed } else (),
if ($committed > 0) then attribute commit { $committed - $validated } else (),
if ($totalTasks > 0)
then
(if ($prepared > 0) then attribute preparationPerTask { ($prepared - $started) div $totalTasks } else (),
if ($executed > 0) then attribute executionPerTask { ($executed - $prepared) div $totalTasks } else (),
if ($validated > 0) then attribute vaalidationPerTask { ($validated - $executed) div $totalTasks } else (),
if ($committed > 0) then attribute commitPerTask { ($committed - $validated) div $totalTasks } else ())
else
(),
attribute allowedExecution {exactly-one($run/allowedExecutionTime) * 1000},
attribute successCount {$successCount},
attribute failureCount {$failureCount},
attribute nooutputCount {$nooutputCount},
attribute totalTasks {$totalTasks}
}
This query compiles within seconds, but then the runtime environment complains:
MAPI = monetdb@localhost
QUERY = for $run in pf:collection("log.xml")//run
ERROR = !ERROR: merged_union: tail of first BAT/column of table 2 must be sorted.
!ERROR: CMDmerged_union: operation failed.
Unfortunately I cannot provide the log.xml-document, but when leaving out the if-statement:
"if ($totalTasks > 0) then ... else ()"
the query executes fine.
p.s. This workaround works for us at the moment.
## Comment 9758
Date: 2008-06-13 09:42:09 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
Hi Wouter,
I'm not sure what you expect from this bug report.
The optimization of the first query screws up because the optimizer wants to get rid of all ``for loops'' and has a harder time reaching this goal than in the second case. If you however look at the query heavy optimization is not needed to provide a good performance. Knowing this it could be perhaps helpful to state that you only want to apply ``light'' optimization for this query (in comparison to others).
For the second query I cannot see anything wrong in the code generation. To solve this problem I would need some help from you.
If you generate the query with pf -A, profile it, give the position in the MIL code (the merged_union that is going to fail; probably one of the 3 calls with 10 arguments), and perhaps a characteristic snippet of the second input BAT (it should be an iter/oid column), then it should be possible to decide whether the underlying string_join() operator or an incorrect property inference in MonetDB might be the reason for the failing merged_union() call.
## Comment 9759
Date: 2008-06-13 18:53:30 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
Hello Jan,
There is not much that I expect out of this bugreport. We found a viable workaround for the given query, so there is certainly no hurry in fixing this. I wanted to indicate that there were problems with running this query. I will try to provide the failing line in the milscript on monday.
For the first query: i knew monetdb was memory-hungry, however it might be nice to have some 'detection-mechanism' that stops optimizing when more than 2?GB of memory is spent by the pathfinder compiler alone trying to come up with a query plan... but i guess that is probably a feature request for a next release :)
## Comment 9760
Date: 2008-06-16 12:54:39 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
The error:
ERROR = !ERROR: merged_union: tail of first BAT/column of table 2 must be sorted.
!ERROR: CMDmerged_union: operation failed.
happens in the merged_union on line 1854:
a0051 := unused;
a0007 := unused;
a0007 := [lng](a0039);
if (a0007.reverse ().exist (lng(nil))) {
ERROR ("err:FORG0001.");
} else {
}
a0051 := unused;
a0051 := [+](a0107, a0108);
a0107 := unused;
a0108 := unused;
a0039 := unused;
a0039 := merged_union (a0103, a0090, a0097, a0075, a0098, a0076, a0099, a0077, a0100, a0087, a0101, a0088, a0102, a0089, a0007, a0047, a0051, a0050);
a0056 := a0039.fetch (0);
a0057 := a0039.fetch (1);
a0058 := a0039.fetch (2);
a0059 := a0039.fetch (3);
a0060 := a0039.fetch (4);
a0073 := a0039.fetch (6);
a0074 := a0039.fetch (7);
a0091 := a0039.fetch (8);
a0039 := unused;
a0103 := unused;
a0097 := unused;
a0098 := unused;
## Comment 9761
Date: 2008-06-16 13:48:48 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
Wouter, Am I right that adding the line
assert_order(a0090);
before the failing merged_union fixes the problem for this call to merged_union?
## Comment 9762
Date: 2008-06-16 16:22:20 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
yep, and when doing the same for the merged_union at lines (+-) 2090, 2512, 2765, 3190, 3444, 3873
then the query returns an answer that looks like the expected result.
## Comment 9763
Date: 2008-06-16 16:47:08 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
The merged_union problem is fixed in CVS. A test triggering this problem is still pending.
## Comment 9764
Date: 2008-06-20 09:04:37 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Added tests (compilation, only) in pathfinder/tests/BugTracker/Tests/compilation_or_runtime_choice.SF-1991738_[01]_{MPS,ALG}:
- First query compiles fine with MPS.
- First query takes >30 minutes & >6 GB to compile with ALG.
- Second query fails to compile with MPS:
type error: can't cast type 'untypedAtomic*' to type 'integer?'
- Second query compiles fine with ALG.
A test to trigger the (now fixed) merged_union problem with the second query is still pending --- mainly, some proper data is missing ...
## Comment 9765
Date: 2008-12-12 00:54:18 +0100
From: @drstmane
I don't have the data to re-produce this bug;
if at all, the original submitter (Wouter) needs to either provide us should with the respective data to add a test, or check (and accept) the fix without test and close the bug report.
## Comment 9766
Date: 2009-02-15 22:09:37 +0100
From: @drstmane
ALG compilation (also) of the first query (now) seems to work fine.
Wouter,
could you please either provide the data to make a proper test (also) for the reported (and fixed) merged_union problem, or close this bug report with a comment that (and why) a test is not possible or required?
Thanks!
Stefan
## Comment 9767
Date: 2009-11-12 19:09:31 +0100
From: Wouter Alink <<alink>>
cant get access to the data, closing bug
## Comment 9768
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1991738 at http://sourceforge.net/support/tracker.php?aid=1991738
| XQ: compilation or runtime choice | https://api.github.com/repos/MonetDB/MonetDB/issues/1727/comments | 0 | 2020-11-30T09:54:13Z | 2024-06-27T11:30:57Z | https://github.com/MonetDB/MonetDB/issues/1727 | 753,328,843 | 1,727 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-12 11:16:07 +0200
From: Wouter Alink <<alink>>
To: Wouter Alink <<alink>>
Version: -- development
Last updated: 2009-02-15 10:16:52 +0100
## Comment 9750
Date: 2008-06-12 11:16:07 +0200
From: Wouter Alink <<alink>>
yesterdays nightly stable build with algebra enabled.
the query:
pf:collection("aap")
seems to return the empty collection (assuming aap is not a collection)
but the following query:
pf:collection("aap")//*
returns:
MAPI = monetdb@localhost:53220
QUERY =
ERROR = !ERROR: CMDfetch: idx out of range
!ERROR: CMDfetch_int: operation failed.
## Comment 9751
Date: 2008-09-05 10:48:38 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
Works for me.
Wouter could you please verify this.
## Comment 9752
Date: 2008-12-18 11:44:49 +0100
From: @drstmane
Re-opened, as there is neither a test, nor a confirmation from the original submitter that the problem is indeed solved, nor a reason given for closing the bug report.
## Comment 9753
Date: 2008-12-18 12:01:21 +0100
From: @lsidir
But it also works for me:
xquery>pf:collection("aap")
more><>
xquery>pf:collection("aap")//*
more><>
xquery>
Both of them are correctly returning an empty collection. Maybe then what is missing is just a test.
## Comment 9754
Date: 2009-02-15 22:16:52 +0100
From: @drstmane
add test in pathfinder/tests/BugTracker/Tests/non-existing_collection.SF-1991726.*
appears to work fine.
closing.
## Comment 9755
Date: 2009-11-14 23:49:37 +0100
From: @drstmane
For (quite) some time, know both queries give the (IMHO correct/to be expected) error
ERROR = !ERROR: err:FODC0004: collection 'aap' unknown (1 missing in total)
I feel free to approve this.
Please re-open and comment in case this is not correct/expected/desired ...
## Comment 9756
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1991726 at http://sourceforge.net/support/tracker.php?aid=1991726
| XQ: non-existing collection | https://api.github.com/repos/MonetDB/MonetDB/issues/1726/comments | 0 | 2020-11-30T09:54:11Z | 2024-06-28T13:29:20Z | https://github.com/MonetDB/MonetDB/issues/1726 | 753,328,808 | 1,726 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-11 02:53:12 +0200
From: mafweb <<mafweb>>
To: Lefteris Sidirourgos <<lsidir>>
Version: -- development
Last updated: 2008-08-11 05:05:14 +0200
## Comment 9744
Date: 2008-06-11 14:53:12 +0200
From: mafweb <<mafweb>>
backup using the MonetDB/XQuery Administrative Console results in a 8.5GB backup containing a lot of xml files, bot 2.5MB and 0 bytes, while original files are +- 10KB.
2.5MB files seems shredded, like serializing wasn't thread-safe.
## Comment 9745
Date: 2008-06-18 10:14:55 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
Hi,
Please try to provide bug reports with a reproduction path. You can also attempt to provide more information. How did you shred the documents? Were they updatable? Did you update them?
Lacking any of that, most likely is that this bug report is simply wrong.
## Comment 9746
Date: 2008-06-18 10:49:52 +0200
From: mafweb <<mafweb>>
Logged In: YES
user_id=1131544
Originator: YES
MonetDB Server v4.22.0
based on GDK v1.22.0
Copyright (c) 1993-2008, CWI. All rights reserved.
Compiled for i686-pc-linux-gnu/32bit with 32bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.5.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.22.0 loaded
XRPC administrative console at http://127.0.0.1:50001/admin
Reproduction path:
- create database of about 78MB XML documents (documents have several namespaces, default and with prefix), 10% overhead for updates
- don't do anything in the database (except some querying)
- goto Administrative Console
- create backup
- watch folder size of backup grow
I don't know what you mean with "how did you shred the documents"...
I certainly hope this bug report isn't 'simply' wrong anymore... with all this extra information.
File Added: 11800_example.xbrl
## Comment 9747
Date: 2008-06-18 19:58:31 +0200
From: mafweb <<mafweb>>
Logged In: YES
user_id=1131544
Originator: YES
I've discovered the database to be corrupt. I'll try to recreate the database tomorrow and see if it's happening again.
Thanx anyway.
## Comment 9748
Date: 2008-08-11 17:05:14 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
I am closing this bug with resolution Invalid. It is been almost two months and didn't hear about this problem again and we could not re-produce it. Moreover, the original bug report, as it turned out, it was on a corrupted db.
## Comment 9749
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1990815 at http://sourceforge.net/support/tracker.php?aid=1990815
| XQ:backup creates 8.5GB data from 78MB database | https://api.github.com/repos/MonetDB/MonetDB/issues/1725/comments | 0 | 2020-11-30T09:54:08Z | 2024-06-28T13:29:19Z | https://github.com/MonetDB/MonetDB/issues/1725 | 753,328,776 | 1,725 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-10 11:38:10 +0200
From: mafweb <<mafweb>>
To: Lefteris Sidirourgos <<lsidir>>
Version: -- development
Last updated: 2008-08-11 05:24:19 +0200
## Comment 9740
Date: 2008-06-10 11:38:10 +0200
From: mafweb <<mafweb>>
I'm filling the database with xml documents, but I'm using 10 docs as test first. I need to clear the database on every run until I finished my loading code.
On the first run, all test documents were present in the database and in a collection. All was fine.
Next, I've used the delete collection button in the MonetDB/XQuery Administrative Console under the "List Collections". Then I re-added my 10 test documents and they do list under "List All Documents", but when I look under "List Collections", I get "No (documents) collections in the database".
Refresh page, restart server, it all resulted in the same empty collections list. Maybe this bug only appears when emptying the whole database and some (meta)data part of collections isn't entirely removed?
## Comment 9741
Date: 2008-06-10 13:29:24 +0200
From: mafweb <<mafweb>>
Logged In: YES
user_id=1131544
Originator: YES
mclient:
xquery>pf:collections()
more><collection updatable="true" size="159 KiB">xbrl</collection>
This seems to work, so it looks like an error in the administrative console.
I've removed the dbfarm (/usr/local/var/MonetDB4/dbfarm/demo) and Mserver has created a new db directory. Now collections are present in the administrative console.
## Comment 9742
Date: 2008-08-11 17:24:19 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
So I guess there was a problem with your dbfarm and not a problem with the administrative console. Also I repeated the test and there were no problems.
Closing the bug.
## Comment 9743
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1989573 at http://sourceforge.net/support/tracker.php?aid=1989573
| XQ:no collections in db while collections do exist | https://api.github.com/repos/MonetDB/MonetDB/issues/1724/comments | 0 | 2020-11-30T09:54:06Z | 2024-06-28T13:29:18Z | https://github.com/MonetDB/MonetDB/issues/1724 | 753,328,743 | 1,724 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-10 07:49:02 +0200
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2008-06-18 12:41:07 +0200
## Comment 9733
Date: 2008-06-10 07:49:02 +0200
From: @drstmane
After recent changes, the website fails to build (via ./link.sh and/or ./copy.sh) with
========
[...]
+ cp /tmp/monetdb//Assets/xqrymanual/xqrymanual.pdf /tmp/monetdb//Assets
+ echo 'pdf created'
pdf created
+ cd /tmp/monetdb//Assets/xqrymanual/
+ makeinfo -D=xqrymanual --force --html xqrymanual.texi --css-include=manual.css
+ echo 'html created'
html created
+ cd /tmp/monetdb//Assets/xqrymanual/
+ makeinfo -D=xqrymanual --force --xml xqrymanual.texi
Element stack index : 1
+ exit 1
========
## Comment 9734
Date: 2008-06-10 09:35:53 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
This error was (partly) resolved in the current version
and requires back-porting if it was not already done.
## Comment 9735
Date: 2008-06-10 09:53:26 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
All recent changes that went accidentally to the development trunk have been back-ported to the Stable_Jun2008 branch.
The development trunk and the Stable_Jun2008 branch are currently identical.
The reported error (hence) occurs both with the development trunk and the Stable_Jun2008 branch.
## Comment 9736
Date: 2008-06-17 00:30:11 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
I tried to fix this one, but my texinfo knowledge proved to be insufficient.
Any help is more than welcome!
We need to be able to build the web site for the new release ...
## Comment 9737
Date: 2008-06-17 10:42:19 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
The problem seems to be that the structure of the Mapi documentation as extracted/generated from the code (Mapi.bdy.texi) is not properly embedded in the XQUERY manual (xqrymanual.texi) --- I could not (easily) find a way to fix this w/o breaking the other manuals that include Mapi.bdy.texi ...
## Comment 9738
Date: 2008-06-18 00:41:06 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed by Martin. Thanks.
I just re-built the pre-view web site on alf.
Please feel free to check it.
## Comment 9739
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1989422 at http://sourceforge.net/support/tracker.php?aid=1989422
| Website fails to build | https://api.github.com/repos/MonetDB/MonetDB/issues/1723/comments | 0 | 2020-11-30T09:54:03Z | 2024-06-27T11:30:53Z | https://github.com/MonetDB/MonetDB/issues/1723 | 753,328,710 | 1,723 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-09 04:36:35 +0200
From: mafweb <<mafweb>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-06-09 06:33:38 +0200
## Comment 9727
Date: 2008-06-09 16:36:35 +0200
From: mafweb <<mafweb>>
Source Link:
http://monetdb.cwi.nl/projects/monetdb/XQuery/QuickTour/HelloWorld/index.html
Example 4
<example> {
<doc>Hello World</doc>/doc/text()
} </example>
Returns:
<example/>
It should be:
<example> {
<doc>Hello World</doc>/text()
} </example>
or
<example> {
<doc><node>Hello World</node></doc>/node/text()
} </example>
## Comment 9728
Date: 2008-06-09 17:54:52 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
As far as I can tell, the result is correct:
The given context node (<doc>Hello World</doc>) has no "doc" child node; hence, the result it empty.
But maybe, one of our XQuery experts (Jan?) could double-check.
Currently, MonetDB/XQuery produces the follwing answers:
$ mclient -lx -s' <example> { <doc>Hello World</doc>/doc/text() } </example> ' | mclient -lx
<example/>
$ mclient -lx -s' <example> { <doc>Hello World</doc>/doc } </example> ' | mclient -lx
<example/>
$ mclient -lx -s' <example> { <doc>Hello World</doc>/text() } </example> ' | mclient -lx
<example>Hello World</example>
$ mclient -lx -s' <example> { <doc>Hello World</doc>/. } </example> ' | mclient -lx
<example><doc>Hello World</doc></example>
(Haven't checked with Galax and/or Saxon, yet ...)
## Comment 9729
Date: 2008-06-09 17:57:49 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Sorry, cut&paste error in the examples; they should of course read as follows:
$ mclient -lx -s' <example> { <doc>Hello World</doc>/doc/text() } </example> '
<example/>
$ mclient -lx -s' <example> { <doc>Hello World</doc>/doc } </example> '
<example/>
$ mclient -lx -s' <example> { <doc>Hello World</doc>/text() } </example> '
<example>Hello World</example>
$ mclient -lx -s' <example> { <doc>Hello World</doc>/. } </example> '
<example><doc>Hello World</doc></example>
## Comment 9730
Date: 2008-06-09 18:04:13 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Aha, you actually mean the example it self is broken, not how MonetDB/XQuery evaluates it, right?
You're (IMHO) right.
Since the intention of the example is to return the "Hello World" text, it should indeed read as
<example> {
<doc>Hello World</doc>/text()
} </example>
instead of
<example> {
<doc>Hello World</doc>/doc/text()
} </example>
I'll fix that.
Thanks for noticing and reporting it!
## Comment 9731
Date: 2008-06-09 18:33:38 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
The example is fixed in our (local) CVS repository for the MonetDB website.
It will be visible once the new web site goes live together with the upcoming "Jun2008" release.
## Comment 9732
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1988948 at http://sourceforge.net/support/tracker.php?aid=1988948
| XQuery Hello World example 4 broken | https://api.github.com/repos/MonetDB/MonetDB/issues/1722/comments | 0 | 2020-11-30T09:54:01Z | 2024-06-27T11:30:52Z | https://github.com/MonetDB/MonetDB/issues/1722 | 753,328,681 | 1,722 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-09 12:25:47 +0200
From: Jorge Limon <<geolemo>>
To: @njnes
Version: -- development
Last updated: 2008-06-10 11:11:48 +0200
## Comment 9722
Date: 2008-06-09 12:25:47 +0200
From: Jorge Limon <<geolemo>>
I'm evaluating Monetdb to store large tables. To test the monetdb perfomance I decided to load a large table of radius logs into a single table "radlog_logs":
CREATE TABLE "radius"."radlog_logs" (
"cpi" varchar(20),
"login" varchar(40),
"segundos" int,
"connections" int,
"nodoacceso" int,
"telefono" int,
"idprovincia" smallint,
"idred" smallint,
"idfecha" int,
"mmbb" varchar(11),
"codproducto" varchar(10),
"es_suscriptor" char(5)
I use a sql dump file and mclient to bulk the data into my test table like this:
mclient -lsql -uradius -Pvoc < final2.sql
where "final2.sql" has 1,3 millons of inserts commands like:
INSERT INTO "radlog_logs" VALUES ('arrakis', -1, -1, 1, 4495, 'igmap', '1411', 'false');;
I repeated this step several times until I have a table with more that 20 millons of records (I spent 2 days in this tasks because server crashed several times in this process).
After this, I started to review data by launching diferents querys and I saw that information was corrupted.
For example, the last column has only "true" or "false" string values, but I found registers with bad information (it seems like some columns was stored data of others columns!!!)
For example in the following query ALLt records must contain the following:
cpi = arrakis
login = arkadsl954789006
es_suscriptor = false
but...columns data are mixed!
sql>select cpi,login, es_suscriptor from radius.radlog_logs where login='arkadsl954789006';
+------------------+-----------------+--------------+
| cpi |login |es_suscriptor |
+==================+=================+==============+
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arrakis |arkadsl954789006 |false |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arrakis |arkadsl954789006 |false |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arrakis |arkadsl954789006 |false |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arrakis |arkadsl954789006 |false |
| arrakis |arkadsl954789006 |false |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arrakis |arkadsl954789006 |false |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arrakis |arkadsl954789006 |false |
| arrakis |arkadsl954789006 |false |
| arrakis |arkadsl954789006 |false |
| arrakis |arkadsl954789006 |false |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arrakis |arkadsl954789006 |false |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arkadsl954789006 |arkadsl954789006 |arkadsl954789 |
: | |006 |
| arrakis |arkadsl954789006 |false |
| arrakis |arkadsl954789006 |false |
| arrakis |arkadsl954789006 |false |
| arrakis |arkadsl954789006 |false |
| arrakis |arkadsl954789006 |false |
| arrakis |arkadsl954789006 |false |
| arrakis |arkadsl954789006 |false |
| arrakis |arkadsl954789006 |false |
| arrakis |arkadsl954789006 |false |
| arrakis |arkadsl954789006 |false |
| arrakis |arkadsl954789006 |false |
| arrakis |arkadsl954789006 |false |
+------------------+-----------------+--------------+
I use:
Monetdb v5.4.0
Windows 2003 Standard
I use a Proliant DL380 server with 1 gb ram
## Comment 9723
Date: 2008-06-09 13:04:36 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
I would like to know if it correctly works on the soon to be released MonetDB (5.6)/SQL (2.24.0). Also loading will be much faster if you change to using copy into instead of insert statements.
## Comment 9724
Date: 2008-06-09 13:08:21 +0200
From: Jorge Limon <<geolemo>>
Logged In: YES
user_id=2039975
Originator: YES
Ok, thanks. When do you plan to releale 5.6 version for windows?
## Comment 9725
Date: 2008-06-10 11:11:47 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
geolemo mailed that the users incorrectly inserted the data, ie not a bug.
## Comment 9726
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1988776 at http://sourceforge.net/support/tracker.php?aid=1988776
| Data are corrupted | https://api.github.com/repos/MonetDB/MonetDB/issues/1721/comments | 0 | 2020-11-30T09:53:58Z | 2024-06-28T13:29:18Z | https://github.com/MonetDB/MonetDB/issues/1721 | 753,328,660 | 1,721 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-09 11:51:16 +0200
From: Jorge Limon <<geolemo>>
To: @njnes
Version: -- development
Last updated: 2008-06-13 07:00:08 +0200
## Comment 9719
Date: 2008-06-09 11:51:16 +0200
From: Jorge Limon <<geolemo>>
Randomly I have a problem with users password validation because I countinuoly need to change it again.
To solve the problem I use "mclient -sql" and summit the command:
alter user "radius" with password 'XXXXXX';
where XXXXXX is the correct password I want to use.
I use:
Monetdb v5.4.0
Windows 2003 Standard
I use a Proliant DL380 server with 1 gb ram
## Comment 9720
Date: 2008-06-09 13:05:30 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Did you try this on the soon to be released 5.6 // 2.24 version. We had a similar bug report which I hopefully fixed
## Comment 9721
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1988747 at http://sourceforge.net/support/tracker.php?aid=1988747
| User password problem | https://api.github.com/repos/MonetDB/MonetDB/issues/1720/comments | 0 | 2020-11-30T09:53:55Z | 2024-06-28T13:29:17Z | https://github.com/MonetDB/MonetDB/issues/1720 | 753,328,635 | 1,720 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-09 11:17:33 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-06-09 02:36:47 +0200
## Comment 9716
Date: 2008-06-09 11:17:33 +0200
From: @drstmane
Checkin
===================================================================
2008/06/08 - tsheyar: pathfinder/compiler/algebra/opt/opt_complex.c,1.45.2.3
-- Add consistency check for a rewrite that merges adjacent twigs:
Only if the child twig provides for every iteration of the parent twig
a node we may merge the two twigs.
===================================================================
makes 8 tests in tests/W3C_use_cases/XQUF/R/Tests/ fail with
"
!ERROR: interpret: no matching MIL operator to 'printf(void)'.
!MAYBE YOU MEAN:
! printf(str, ..any..) : void
"
See
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQUF_R/Q2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQUF_R/Q3.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQUF_R/Q5a.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQUF_R/Q5b.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQUF_R/Q6a.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQUF_R/Q6b.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQUF_R/Q8.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQUF_R/Q9.out.00.html
## Comment 9717
Date: 2008-06-09 14:36:47 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
These queries work again: In the node property inference we cannot assume that update and document management queries can be optimized. (Updates failed with lightweight node constructors -- nodes of kind REFERENCE.)
## Comment 9718
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1988728 at http://sourceforge.net/support/tracker.php?aid=1988728
| PF/alg: tests/W3C_use_cases/XQUF/R fail after latest change | https://api.github.com/repos/MonetDB/MonetDB/issues/1719/comments | 0 | 2020-11-30T09:53:53Z | 2024-06-27T11:30:49Z | https://github.com/MonetDB/MonetDB/issues/1719 | 753,328,610 | 1,719 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-06 03:56:50 +0200
From: Eelco Eerenberg <<eelcotje>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-06-06 04:39:08 +0200
## Comment 9713
Date: 2008-06-06 15:56:50 +0200
From: Eelco Eerenberg <<eelcotje>>
When using the mclient with the -t option, to benchmark XQuery perfomance for adding documents (pf:add-doc), the statistics always show 0 milliseconds for the shredding part of the add process.
This is not a problem due to building the source, anyhow here is the information asked for:
autoconf 2.61
automake 1.9.6
libtool 1.5.26 Debian 1.5.26-4 (1.1220.2.493 2008/02/01 16:58:18)
## Comment 9714
Date: 2008-06-06 16:39:08 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
The time for shredding a document explicitly via pf:add-doc() is (currently?) reported as "Update" time.
The "Shred" time (only) reports the time for (implicitly) shredding and/or loading documents via fn:doc().
While seeming "unintuitive", the idea behind this decision is (was) (most probably) the "Shred" reports document loading in read-only (parts of) queries.
"Update" reports on update costs in update queries and on document management costs in document management queries.
## Comment 9715
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1986499 at http://sourceforge.net/support/tracker.php?aid=1986499
| query statistics | https://api.github.com/repos/MonetDB/MonetDB/issues/1718/comments | 0 | 2020-11-30T09:53:50Z | 2024-06-28T13:30:13Z | https://github.com/MonetDB/MonetDB/issues/1718 | 753,328,575 | 1,718 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-03 04:13:37 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-06-05 11:28:13 +0200
## Comment 9707
Date: 2008-06-03 16:13:37 +0200
From: @drstmane
checkin
===================================================================
2008/06/03 - tsheyar: compiler/algebra/builtins.c,1.95.2.3
compiler/algebra/core2alg.brg,1.71.2.2
compiler/algebra/map/resolve_proxy.c,1.12.2.1
compiler/algebra/opt/opt_complex.c,1.45.2.2
compiler/algebra/opt/opt_set.c,1.10.2.1
-- Disable the blocking step and semijoin operators
and replace them by step_join+distinct and eqjoin+distinct.
This change gives the optimizer more freedom and removes the last
traces of staircase-join from the logical plans.
The physical algebra planner will try to implement step_join whenever
possible with a duplicate-eliminating staircase-join operator.
===================================================================
causes the following 3 tests to fail (see TestWeb tomorrow):
tests/BugTracker/Tests/seqcast_opt_int_to_numeric.SF-1637867.xq:
SegFault!
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/seqcast_opt_int_to_numeric.SF-1637867.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/seqcast_opt_int_to_numeric.SF-1637867.out.00.html
tests/W3C_use_cases/XQUF/AddressBook/Tests/Q1x.xq:
ERROR = !fatal error: attribute `item1' referenced in not operation not found
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQUF_AddressBook/Q1x.err.00.html
tests/XQuery/Tests/union.xq:
different result(-order)
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/union.out.00.html
## Comment 9708
Date: 2008-06-04 15:37:09 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
I just "fixed"
tests/XQuery/Tests/union.xq
by removing the Algebra-specific output (again);
ALG now seems to (again) produce the same output order as MPS;
let's assume this is correct ...
## Comment 9709
Date: 2008-06-04 21:30:30 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
The segfault in
tests/BugTracker/Tests/seqcast_opt_int_to_numeric.SF-1637867.xq
seems to be due to an "endless" recursion in
mark_right_subdag() in compiler/algebra/opt/opt_join_pd.c
possibly caused by a cicle in the "DAG"?
========
$ gdb --args pf -A tests/BugTracker/Tests/seqcast_opt_int_to_numeric.SF-1637867.xq
--------
GNU gdb Red Hat Linux (6.6-45.fc8rh)
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...
Using host libthread_db library "/lib64/libthread_db.so.1".
(gdb) r
Starting program: /net/rig.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Stable/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/bin/pf -A tests/BugTracker/Tests/seqcast_opt_int_to_numeric.SF-1637867.xq
Program received signal SIGSEGV, Segmentation fault.
0x00000000004f82bf in mark_right_subdag (p=Cannot access memory at address 0x7fff4f79afe8
) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/pathfinder/compiler/algebra/opt/opt_join_pd.c:1504
1504 {
Missing separate debuginfos, use: debuginfo-install glibc.x86_64 libxml2.x86_64 zlib.x86_64
(gdb) bt
0 0x00000000004f82bf in mark_right_subdag (p=Cannot access memory at address 0x7fff4f79afe8
) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/pathfinder/compiler/algebra/opt/opt_join_pd.c:1504
1 0x00000000004f832f in mark_right_subdag (p=0x2aaaaafe2fe0) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/pathfinder/compiler/algebra/opt/opt_join_pd.c:1515
2 0x00000000004f832f in mark_right_subdag (p=0x2aaaaafe2b40) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/pathfinder/compiler/algebra/opt/opt_join_pd.c:1515
[...]
9999 0x00000000004f832f in mark_right_subdag (p=0x2aaaaafe2700) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/pathfinder/compiler/algebra/opt/opt_join_pd.c:1515
10000 0x00000000004f832f in mark_right_subdag (p=0x2aaaaafa6290) at /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/pathfinder/compiler/algebra/opt/opt_join_pd.c:1515
[...]
========
## Comment 9710
Date: 2008-06-04 23:21:49 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
The segfault problem is fixed. As Stefan observed it turned out to be a cycle detection problem.
## Comment 9711
Date: 2008-06-05 11:28:13 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
After fixing the CSE phase query tests/W3C_use_cases/XQUF/AddressBook/Tests/Q1x.xq works fine again.
Closing the bug as all three queries work as expected again.
## Comment 9712
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1983619 at http://sourceforge.net/support/tracker.php?aid=1983619
| PF/alg: 3 test fail after disabling blocking step & semijoin | https://api.github.com/repos/MonetDB/MonetDB/issues/1717/comments | 0 | 2020-11-30T09:53:48Z | 2024-06-27T11:30:47Z | https://github.com/MonetDB/MonetDB/issues/1717 | 753,328,543 | 1,717 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-03 03:35:20 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2009-02-17 11:43:17 +0100
## Comment 9704
Date: 2008-06-03 15:35:20 +0200
From: @drstmane
[Just for the bookkeeping; might become a "Won't fix" eventually...]
With the old ((soon) deprecated) milprint_summer back-end fn:sum() incorrectly returns the default value as xs:double 0.
(With the new Algebra back-end, fn:sum() correctly returns the default value as xs:integer 0.)
See
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.32.d-Fedora8/tests_BugTracker/merged-union_error_with_fn-sum.SF-1751684.out.00.html
See also
[ 1751684 ] XQ: merged_union error with fn:sum()
https://sourceforge.net/tracker/index.php?func=detail&aid=1751684&group_id=56967&atid=482468
## Comment 9705
Date: 2009-02-17 11:43:17 +0100
From: @drstmane
ALG works fine:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugTracker/merged-union_error_with_fn-sum.SF-1751684.out.00.html
MPS won't fix
(cf. https://sourceforge.net/tracker/index.php?func=detail&aid=1751684&group_id=
56967&atid=482468):
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_BugTracker/merged-union_error_with_fn-sum.SF-1751684.out.00.html
Closing.
## Comment 9706
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1983577 at http://sourceforge.net/support/tracker.php?aid=1983577
| PF/mps: fn:sum() default return value has wrong type | https://api.github.com/repos/MonetDB/MonetDB/issues/1716/comments | 0 | 2020-11-30T09:53:46Z | 2024-06-28T13:30:12Z | https://github.com/MonetDB/MonetDB/issues/1716 | 753,328,508 | 1,716 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-03 03:26:25 +0200
From: @drstmane
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2008-08-11 05:27:46 +0200
## Comment 9701
Date: 2008-06-03 15:26:25 +0200
From: @drstmane
[Just for the bookkeeping; might become a "Won't fix" eventually...]
While the new Algebra back-end correctly refuses casts from arbitrary strings to boolean, the old ((soon) deprecated) milprint_summer back-end still allows this.
See
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora8/tests_XQuery/cast7.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora8/tests_XQuery/cast7.err.00.html
See also
[ 1981784 ] PF/alg: test cast7: "casting from string to boolean failed"
https://sourceforge.net/tracker/index.php?func=detail&aid=1981784&group_id=56967&atid=482468
## Comment 9702
Date: 2008-08-11 17:27:46 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
The "old ((soon) deprecated) milprint_summer back-end" is now the "old deprecated milprint_summer back-end". So it is time to close it as an wont fix.
## Comment 9703
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1983567 at http://sourceforge.net/support/tracker.php?aid=1983567
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-common@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| PF/mps: allows incorrect cast from string to boolean | https://api.github.com/repos/MonetDB/MonetDB/issues/1715/comments | 0 | 2020-11-30T09:53:43Z | 2024-06-28T13:30:12Z | https://github.com/MonetDB/MonetDB/issues/1715 | 753,328,482 | 1,715 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-03 12:36:43 +0200
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-06-09 01:00:26 +0200
## Comment 9693
Date: 2008-06-03 12:36:43 +0200
From: @romulogoncalves
The following code crashed Mserver5 SQL (including the algebra version):
create table t1 (id int, age int);
create function f1()
RETURNS table (idd int, aage int)
BEGIN
DECLARE TABLE cover(
id int, htmidEnd int
);
INSERT into cover
SELECT id, age
FROM t1;
RETURN TABLE (
SELECT id , htmidEnd
FROM cover H
WHERE 1 > id);
END;
select * from f1() n;
Some debug information:
>[New Thread 1098918224 (LWP 2776)]
[New Thread 1107310928 (LWP 2777)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1107310928 (LWP 2777)]
0x00002aaabecc718c in _dumpstmt (sql=0x11694f8, mb=0x6d82228, s=0x6e9a8d8) at /ufs/goncalve/MonetDB/stable/sql/src/backends/monet5/sql_gencode.mx:1387
1387 q = pushStr(mb, q, c->t->s->base.name);
Missing separate debuginfos, use: debuginfo-install bzip2.x86_64 e2fsprogs.x86_64 glibc.x86_64 keyutils.x86_64 krb5.x86_64 libselinux.x86_64 ncurses.x86_64 openssl.x86_64 pcre.x86_64 readline.x86_64 zlib.x86_64
(gdb) p c
$3 = (sql_column *) 0x6eb66b8
(gdb) p c->t
$4 = (struct sql_table *) 0x6d85bd8
(gdb) p c->t->s
$5 = (struct sql_schema *) 0x0
(gdb)
Romulo
## Comment 9694
Date: 2008-06-03 13:50:46 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
Test added at:
sql/src/test/BugTracker/Tests/schema_from_declared_table.SF-1983341.sql
Romulo
## Comment 9695
Date: 2008-06-04 22:38:34 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
The bug is fixed. The declared tables were not created properly. Now the are created in a special schema (%dt%).
## Comment 9696
Date: 2008-06-05 08:21:41 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
If it is fixed why is not closed?
Romulo
## Comment 9697
Date: 2008-06-05 09:15:56 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
(Only) Now that testing has confirmed Niels' fix for SQL/4, SQL/5 & SQL/Algebra,
we can savely close this bug report.
## Comment 9698
Date: 2008-06-05 15:43:20 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
The test was improved and it shows that the bug is not complete fixed.
I just add new selection:
select * from f1() n;
And now the mserver is again crashing:
>[New Thread 1098918224 (LWP 20645)]
[New Thread 1107310928 (LWP 20646)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1107310928 (LWP 20646)]
0x00002aaabed4715b in validate_tables (s=0x293ddc8, os=0x1379748) at /ufs/goncalve/MonetDB/current/sql/src/storage/store.mx:2415
2415 for (o = t->columns.set->h, p = ot->columns.set->h; o && p; o = o->next, p = p->next) {
(gdb) p ot->columns
$11 = {destroy = 0x2aaabed3e71b <column_destroy>, set = 0x2924168, dset = 0x0, nelm = 0x0}
(gdb) p t->columns
$12 = {destroy = 0x2aaabed3e71b <column_destroy>, set = 0x0, dset = 0x0, nelm = 0x0}
(gdb)
Romulo
## Comment 9699
Date: 2008-06-09 13:00:26 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
also fixed
## Comment 9700
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1983341 at http://sourceforge.net/support/tracker.php?aid=1983341
| schema from declared table... | https://api.github.com/repos/MonetDB/MonetDB/issues/1714/comments | 0 | 2020-11-30T09:53:40Z | 2024-06-27T11:30:44Z | https://github.com/MonetDB/MonetDB/issues/1714 | 753,328,451 | 1,714 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-03 12:28:39 +0200
From: @drstmane
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2008-08-14 11:01:54 +0200
## Comment 9686
Date: 2008-06-03 12:28:39 +0200
From: @drstmane
With the Algebra back-end, test tests/W3C_use_cases/XQUF/AddressBook/Tests/check_doc.xq fails with
!ERROR: XML Generation: tmp_647 BAT does not have a 16384 head.
ERROR: XML Generation: NULL BAT has a 16384 head, but tail is NULL.
probably because one of the preceding update queries in this directory (silently) fails and/or corrupts the database.
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQUF_AddressBook/check_docs.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQUF_AddressBook/check_docs.err.00.html
## Comment 9687
Date: 2008-06-10 10:03:23 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
After yesterday's (Monday Jun 09 2008) checkins,
the test seems to work fine on 64-bit systems
(http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQUF_AddressBook/check_docs.out.00.html),
but still produces "unexpected" (wrong) output on 32-bit systems
(though the initial error message is gone there, too):
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.32.32.d-Fedora8/tests_W3C_use_cases_XQUF_AddressBook/check_docs.out.00.html
## Comment 9688
Date: 2008-08-11 17:29:18 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
Who's checkins was? Can you re-assign please to that person Stefan. Thank you.
## Comment 9689
Date: 2008-08-13 11:23:50 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
See attached list.
Updated links to the TestWeb are
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora9/tests_W3C_use_cases_XQUF_AddressBook/check_docs.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.32.32.d.1-Fedora9/tests_W3C_use_cases_XQUF_AddressBook/check_docs.out.00.html
File Added: Pathfinder-checkins-2008-06-09
## Comment 9690
Date: 2008-08-13 11:25:47 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
See attached list.
Updated links to the TestWeb are
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora9/tests_W3C_use_cases_XQUF_AddressBook/check_docs.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.32.32.d.1-Fedora9/tests_W3C_use_cases_XQUF_AddressBook/check_docs.out.00.html
File Added: Pathfinder-checkins-2008-06-09
## Comment 9691
Date: 2008-08-14 11:01:54 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
This one is failing because tests/W3C_use_cases/XQUF/AddressBook/Q1x is failing.
However, this is because of the same reason as described in [ 1981762 ] PF/alg: "Mapping unique name to an original name failed."
There has been a workaround submited by Jan for the stable version (which works only for 64bit machines), but a solution in the head is still pending.
Since this problem is the same as bug [ 1981762 ] and to avoid confusion with duplicate bug reports, I will close this bug and add the details of this one to the original bug report.
## Comment 9692
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1983333 at http://sourceforge.net/support/tracker.php?aid=1983333
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.
This bug was marked DUPLICATE in the database it was moved from.
Changing resolution to "MOVED"
| PF/alg: tests/W3C_use_cases/XQUF/AddressBook/check_doc fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1713/comments | 0 | 2020-11-30T09:53:36Z | 2024-06-28T13:30:11Z | https://github.com/MonetDB/MonetDB/issues/1713 | 753,328,401 | 1,713 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-03 08:51:18 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2008-06-04 11:29:56 +0200
## Comment 9682
Date: 2008-06-03 08:51:18 +0200
From: @drstmane
After yesterdays checkins, tests src/test/BugDay_2005-10-06_2.9.3/Tests/having.SF-922614.sql & src/test/BugTracker/Tests/authorization.SF-1430616.SQL.sh produce different output than before:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests4103/GNU.64.64.d-Fedora8/src_test_BugDay_2005-10-06_2.9.3/having.SF-922614.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests4103/GNU.32.32.d-Debian4.0/src_test_BugTracker/authorization.SF-1430616.out.00.html
## Comment 9683
Date: 2008-06-03 08:54:47 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
also with SQL/5:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests5103/GNU.64.64.d-Fedora8/src_test_BugDay_2005-10-06_2.9.3/having.SF-922614.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests5103/GNU.32.32.d-Fedora8/src_test_BugTracker/authorization.SF-1430616.out.00.html
## Comment 9684
Date: 2008-06-04 11:29:56 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed by Niels.
Thanks.
## Comment 9685
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1983086 at http://sourceforge.net/support/tracker.php?aid=1983086
| SQL: tests having.SF-922614 & authorization.SF-1430616 fail | https://api.github.com/repos/MonetDB/MonetDB/issues/1712/comments | 0 | 2020-11-30T09:53:34Z | 2024-06-27T11:30:42Z | https://github.com/MonetDB/MonetDB/issues/1712 | 753,328,368 | 1,712 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-02 06:03:31 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-06-03 09:21:47 +0200
## Comment 9679
Date: 2008-06-02 18:03:31 +0200
From: @drstmane
With the Algebra back-end, "boolean (())" seems to be skipped in the else-branch of the following query; a stand-alone "boolean (())" or a "boolean ($b)" in the else-branch do work fine.
See also
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/bool7.out.00.html
========
$ mclient -lx -G -s'boolean (())'
--------
false
========
$ mclient -lx -G -s'for $b in (1,0) return if ($b) then for $a in (0,1,2,"foo","",0.0,1.3,boolean(1),boolean(0),<a/>) return boolean($a) else boolean (())'
--------
false,
true,
true,
true,
false,
false,
true,
true,
false,
true
<== "false" missing !
========
$ mclient -lx -G -s'for $b in (1,0) return if ($b) then for $a in (0,1,2,"foo","",0.0,1.3,boolean(1),boolean(0),<a/>) return boolean($a) else boolean (())' | wc
--------
10 10 63
========
$ mclient -lx -s'for $b in (1,0) return if ($b) then for $a in (0,1,2,"foo","",0.0,1.3,boolean(1),boolean(0),<a/>) return boolean($a) else boolean (())' | wc
--------
11 11 70
========
$ mclient -lx -G -s'for $b in (1,0) return if ($b) then for $a in (0,1,2,"foo","",0.0,1.3,boolean(1),boolean(0),<a/>) return boolean($a) else boolean ($b)'
false,
true,
true,
true,
false,
false,
true,
true,
false,
true,
false
========
$ mclient -lx -G -s'for $b in (1,0) return if ($b) then for $a in (0,1,2,"foo","",0.0,1.3,boolean(1),boolean(0),<a/>) return boolean($a) else boolean ($b)' | wc
--------
11 11 70
========
## Comment 9680
Date: 2008-06-03 09:21:47 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
Cause: Incorrect domain property inference for union+empty_tbl. Fixed in CVS.
## Comment 9681
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1982310 at http://sourceforge.net/support/tracker.php?aid=1982310
| PF/alg: "boolean (())" skipped in complex query | https://api.github.com/repos/MonetDB/MonetDB/issues/1711/comments | 0 | 2020-11-30T09:53:31Z | 2024-06-27T11:30:41Z | https://github.com/MonetDB/MonetDB/issues/1711 | 753,328,340 | 1,711 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.