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: 2006-07-28 12:58:57 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2006-08-28 04:50:16 +0200
## Comment 5732
Date: 2006-07-28 12:58:57 +0200
From: @drstmane
When casting chr to str, the atomic cast and the
batcast act differently. As introduced by Sjoerd on Aug
18 2005:
===================================================================
2005/08/18 - sjoerd:
/cvsroot/monetdb/MonetDB/src/gdk/gdk_atoms.mx,1.104
/cvsroot/monetdb/MonetDB/src/modules/contrib/Tests/array.stable.out,1.3
/cvsroot/monetdb/MonetDB/src/modules/plain/str.mx,1.55
/cvsroot/monetdb/MonetDB/src/modules/plain/Tests/str.stable.out,1.19
/cvsroot/monetdb/MonetDB/src/modules/plain/Tests/xtables.stable.out,1.17
/cvsroot/monetdb/MonetDB/src/monet/monet_interpreter.mx,1.88
/cvsroot/monetdb/MonetDB/tests/BugReports/Tests/no.148.stable.out,1.12
/cvsroot/monetdb/MonetDB/tests/BugsViaSourgeforce/Tests/ID.1010729.stable.out,1.3
/cvsroot/monetdb/MonetDB/tests/suite_00/Tests/test_60.stable.out,1.17
/cvsroot/monetdb/MonetDB/tests/suite_08/Tests/test_02.stable.out,1.9
Print chr values using single quotes and escape control
characters using backslashes.
===================================================================
the atomic cast distingishes latin-1 (ISO-8859-1 and
(7-bit) ASCII:
===================================================================
src/monet/monet_interpreter.mx, r1.103.2.5, lines
1425-1437:
--------
} else if (val->vtype == TYPE_chr) {
/* special case for chr -> str */
char *s = res->val.sval =
GDKmalloc(3);
if (val->val.cval[0] & 0x80) {
/* interpret as latin-1
(ISO-8859-1) */
*s++ = 0xC0 |
((val->val.cval[0] >> 6) & 0x3);
*s++ = 0x80 |
(val->val.cval[0] & 0x3F);
} else {
/* (7-bit) ASCII */
*s++ = val->val.cval[0];
}
*s++ = 0;
res->len = s - res->val.sval;
===================================================================
while the bascast simply copies the plain chr:
===================================================================
src/monet/monet_interpreter.mx, r1.103.2.5, lines
1638-1649:
--------
} else if (b->ttype ==
TYPE_chr) {
/* chr => str:
do this efficiently */
char s[2];
s[1] = 0;
BATloopFast(b,
p, q, xx) {
/*
accidentally works well on NILs */
s[0] =
*(char *) BUNtloc(b, p);
bunfastins_nocheck(bn, r, BUNhead(b, p), s, yy);
r += yy;
}
/*reduce = 0;*/
/* this should be fine */
===================================================================
Do we need to propagate the atomic cast solution also
to the batcast?
## Comment 5733
Date: 2006-08-28 16:50:16 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed.
## Comment 5734
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1530310 at http://sourceforge.net/support/tracker.php?aid=1530310
| chr -> str: inconsistency between atom cast and batcast | https://api.github.com/repos/MonetDB/MonetDB/issues/1010/comments | 0 | 2020-11-30T09:15:50Z | 2024-06-27T11:19:12Z | https://github.com/MonetDB/MonetDB/issues/1010 | 753,300,819 | 1,010 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-27 03:01:17 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-07-28 12:59:48 +0200
## Comment 5728
Date: 2006-07-27 15:01:17 +0200
From: @drstmane
When casting chr to str, batcast does not remove single
quotes ('); the atomic cast does remove them:
MonetDB>var c := 'a';
MonetDB>print(c);
[ 'a' ]
MonetDB>print(str(c));
[ "a" ]
MonetDB>var b:=new(void,chr).append('a');
MonetDB>print(b);
-----------------
h t name
void chr type
-----------------
[ nil, 'a' ]
MonetDB>print([str](b));
-----------------
h t name
void str type
-----------------
[ nil, "'a'" ]
This is tested by the following two tests
src/gdk/Tests/casts.milM ("old")
src/gdk/Tests/batcasts.milM ("new")
## Comment 5729
Date: 2006-07-28 10:49:18 +0200
From: @drstmane
Logged In: YES
user_id=572415
See
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU.64.64.d-Fedora4/src_gdk/batcasts.out.00.html
## Comment 5730
Date: 2006-07-28 12:59:48 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS:
omit the extra single quotes around a chr when batcast-ing
it to str
## Comment 5731
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1529658 at http://sourceforge.net/support/tracker.php?aid=1529658
| batcast chr->str does not remove single quotes (') | https://api.github.com/repos/MonetDB/MonetDB/issues/1009/comments | 0 | 2020-11-30T09:15:47Z | 2024-06-27T11:19:11Z | https://github.com/MonetDB/MonetDB/issues/1009 | 753,300,777 | 1,009 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-26 10:29:38 +0200
From: Jens Teubner <<teubner>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-08-15 02:58:27 +0200
## Comment 5724
Date: 2006-07-26 10:29:38 +0200
From: Jens Teubner <<teubner>>
Peter tried to implement some module caching
functionality for server-side XQuery evaluation. This
functionality is completely undocumented and fragile.
To demonstrate how fragile the code is, I have
modified the test cases
XMark/mod/XQ/Tests/q01.xq.in and
XMark/mod/XQ/Tests/q02.xq.in
in a way that should not affect the semantics of the
queries. The changes, however, break server-side
evaluation, while standalone compilation and execution
runs perfectly fine.
## Comment 5725
Date: 2006-08-15 01:00:53 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Hi Jens,
I just discovered this bug report - no idea why I missed the
email notification about it..
My take is that this is your way of saying:
"I just implemented support in the parser for the 'xquery
version' clause. Peter, would you please start supporting
this as well in the query cache?"
A nasty response would be to propose a feature swap: you get
version-include in the query cache, and I get nested
comments from the static parser.
But I will not be picky and hereby declare your wish granted.
However, if there are any more general issues with the query
cache (and your wording 'Peter tried to implement' something
that turns out to be 'completely fragile', suggests this),
would you then please elaborate?
If you are referring to the open 'diamond module include'
bug -- I am aware of that and this will be fixed in due time.
Finally, your remark on 'completely undocumented' confuses
me as to whether you mean user or technical documentation.
If you mean user documentation I disagree. In the web pages
on XQuery modules, the performance benefits of modules
(through caching) are explained. As semantically modules are
transparent, the only user-documentation that is relevant is
about these performance benefits.
As for the technical documentation, runtime/pathfinder.mx is
quite comprehensively commented for my standards. I agree
that it could be that these standards fall short to your
likings, but regrettably there is little hope for more at
this stage of the game.
Peter
## Comment 5726
Date: 2006-08-15 15:19:46 +0200
From: @drstmane
Logged In: YES
user_id=572415
Guessing what Peter forgot
(please correct me in case I'm wrong!)
1) Set resolution to "Fixed".
2) Peter's checking message says:
========
bugfix 1528839 (interpreting Jens as requesting support for
'xquery version')
- xquery cache accepts version declaration as well now
- xquery cache refrains now from giving error messages,
diverting all
queries it already knows to have a syntax error to PF anyway
(so that we get the same error message as in standalone
execution).
- added a check in the compiler on the encoding. As it
stands now, we only
support UTF-8 (which is fine, from my point of view).
========
3) No test added, as tests XMark/mod/XQ/Tests/q01.xq.in and
XMark/mod/XQ/Tests/q02.xq.in do (should?) cover this.
## Comment 5727
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1528839 at http://sourceforge.net/support/tracker.php?aid=1528839
| XQuery: Module caching undocumented and fragile | https://api.github.com/repos/MonetDB/MonetDB/issues/1008/comments | 0 | 2020-11-30T09:15:43Z | 2024-06-27T11:19:10Z | https://github.com/MonetDB/MonetDB/issues/1008 | 753,300,718 | 1,008 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-19 12:51:43 +0200
From: Henning Rode <<hrode>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2007-02-19 04:05:12 +0100
## Comment 5718
Date: 2006-07-19 12:51:43 +0200
From: Henning Rode <<hrode>>
the following query:
for $i in (0,1,2) return string($i > 0)
outputs:
<XQueryResult>
0@0 1@0 1@0
</XQueryResult>
which is probably not what XQuery defines for casting
boolean values to strings.
the query:
1 > 0
results correctly in:
true
however:
string(1 > 0)
results as above in:
1@0
## Comment 5719
Date: 2006-07-19 23:08:21 +0200
From: @drstmane
Logged In: YES
user_id=572415
prefixed the summary with "XQuuery: "
## Comment 5720
Date: 2006-08-16 23:38:11 +0200
From: @peterboncz
Logged In: YES
user_id=591107
indeed strange this was not dicovered before. thanks for
reporting!
## Comment 5721
Date: 2006-12-02 18:40:30 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Re-opened, as no test has been provided, yet.
User (submitter) and/or developer (assignee),
please supply a respective test,
or explain why a test is not required/possible.
## Comment 5722
Date: 2007-02-19 16:05:12 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Test added.
## Comment 5723
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1525175 at http://sourceforge.net/support/tracker.php?aid=1525175
| XQuery: casting boolean to string | https://api.github.com/repos/MonetDB/MonetDB/issues/1007/comments | 0 | 2020-11-30T09:15:41Z | 2024-06-27T11:19:09Z | https://github.com/MonetDB/MonetDB/issues/1007 | 753,300,690 | 1,007 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-18 04:21:52 +0200
From: @grobian
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2006-07-19 08:16:53 +0200
## Comment 5715
Date: 2006-07-18 16:21:52 +0200
From: @grobian
http://koala.ins.cwi.nl:8000/projects/monetdb/MonetDB/Version5/Documentation/index.html
has lots of menus. It is unclear to me why. The
subpages (generated) are correct.
## Comment 5716
Date: 2006-07-19 20:16:38 +0200
From: @grobian
Logged In: YES
user_id=963970
Fixed. Awk expanded on the & in Stefan's urls :)
## Comment 5717
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1524556 at http://sourceforge.net/support/tracker.php?aid=1524556
| M5/Documentation page has lots of of menus | https://api.github.com/repos/MonetDB/MonetDB/issues/1006/comments | 0 | 2020-11-30T09:15:38Z | 2024-06-27T11:19:08Z | https://github.com/MonetDB/MonetDB/issues/1006 | 753,300,664 | 1,006 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-18 02:59:55 +0200
From: @peterboncz
To: Peter Boncz <<boncz>>
Version: unspecified
Last updated: 2007-01-17 05:40:33 +0100
## Comment 5709
Date: 2006-07-18 14:59:55 +0200
From: @peterboncz
A subsection of the Research page should just provide
an overview of all MonetDB papers, structured along the
topics.
i.e. it should mention my thesis and the Bwit paoer as
general entry points.
It should also point to the work on cache-conscious
algorithms and list the papers there.
It should point to the early work by Albrecht on XQuery
and XMark, as well as the pathfinder work.
Then, also a paragraph on cracking and possibly armada.
It should also contain a section on MonetDB/X100 and
explain that it is not released here.
## Comment 5710
Date: 2006-07-19 00:23:01 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Development/Research already contains the paragraphs and the
place-holders to all project's web pages.
Development/Research/Articles . The old shell script is
insufficient for a grouped presentation.
## Comment 5711
Date: 2006-07-19 07:34:12 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Development/Research already contains the paragraphs and the
place-holders to all project's web pages.
Development/Research/Articles . The old shell script is
insufficient for a grouped presentation.
## Comment 5712
Date: 2006-07-19 10:13:36 +0200
From: @peterboncz
Logged In: YES
user_id=591107
This illustrates the problem of having pages with the same
name in different locations repeated, because the research
page that I was referring to was the V5 one:
http://koala.ins.cwi.nl:8000/projects/monetdb/MonetDB/Version5/Research/index.html
Of course a mistake, because I indeed see a more appropriate
page here:
http://koala.ins.cwi.nl:8000/projects/monetdb/Development/Roadmap/index.html
This illustrates my confusion, and I think underlines my
request to assign each information a single 'home' in the
website, such that for users there is no confusion where
they should go to to read about a certain topic.
Therefore, I propose to concentrate all
- research, and
- roadmap
information in the Development section, if necessary divided
over subsections (but I doubt that this is actually required
in this case).
Currently, all topics (SQL,Server), and in intent also
XQuery have the following subdivision:
- Documentation
- Research
- Roadmap
But, if the latter two are removed, we may also remove the
Documentation, and remove a level of indirection.
Further, while stuff is being moved out, we may use the
green links to re-introduce them:
- X/Download => Download/Download/Y
- X/Tutorial => Download/Tutorial/Y
- X/Roadmap => Development/Roadmap/Y
- X/Research => Development/Research/Y
where X identifies the page where the green links depart
from (Vx/{SQL,XQuery,Server}) and Y is the sub-page, of the
topic (Development,Download) home to that info.
The green links are not exploited enough yet!
what do you think??
## Comment 5713
Date: 2007-01-17 05:40:33 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
The underlying system does not easily support
construction of topic based library access
automatically.
The general access point to the library
is retained instead and the entry page
describes projects.
## Comment 5714
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1524507 at http://sourceforge.net/support/tracker.php?aid=1524507
| WEB: Concentrate Research & Roadmap | https://api.github.com/repos/MonetDB/MonetDB/issues/1005/comments | 0 | 2020-11-30T09:15:35Z | 2024-06-27T11:19:07Z | https://github.com/MonetDB/MonetDB/issues/1005 | 753,300,635 | 1,005 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-18 02:49:56 +0200
From: @peterboncz
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2006-07-23 09:56:33 +0200
## Comment 5706
Date: 2006-07-18 14:49:56 +0200
From: @peterboncz
http://koala.ins.cwi.nl:8000/projects/monetdb/MonetDB/Version4/Documentation/APIs/JDBC/index.html
the JDBC manual is missing here
## Comment 5707
Date: 2006-07-23 09:56:32 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Solved in proto web-site.
## Comment 5708
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1524505 at http://sourceforge.net/support/tracker.php?aid=1524505
| V4/Documentation/APIs/JDBC doc missing | https://api.github.com/repos/MonetDB/MonetDB/issues/1004/comments | 0 | 2020-11-30T09:15:32Z | 2024-06-27T11:19:06Z | https://github.com/MonetDB/MonetDB/issues/1004 | 753,300,613 | 1,004 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-18 02:48:18 +0200
From: @peterboncz
To: @mlkersten
Version: unspecified
Last updated: 2007-01-01 11:25:46 +0100
## Comment 5703
Date: 2006-07-18 14:48:18 +0200
From: @peterboncz
http://koala.ins.cwi.nl:8000/projects/monetdb/MonetDB/Version4/Documentation/APIs/index.html
in the contents there are wrong link error messages
## Comment 5704
Date: 2007-01-01 23:25:46 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
The version 4 end of life has been reached.
## Comment 5705
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1524502 at http://sourceforge.net/support/tracker.php?aid=1524502
| WEB: V4/Doc/API errors in link generation | https://api.github.com/repos/MonetDB/MonetDB/issues/1003/comments | 0 | 2020-11-30T09:15:29Z | 2024-06-28T13:32:59Z | https://github.com/MonetDB/MonetDB/issues/1003 | 753,300,578 | 1,003 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-18 02:46:56 +0200
From: @peterboncz
To: @mlkersten
Version: -- development
Last updated: 2006-07-30 09:12:54 +0200
## Comment 5700
Date: 2006-07-18 14:46:56 +0200
From: @peterboncz
http://koala.ins.cwi.nl:8000/projects/monetdb/MonetDB/Version4/Documentation/APIs/Mapi/index.html
in the menu, as well as in the contents we get missing
directives errors
## Comment 5701
Date: 2006-07-30 21:12:53 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Mapi documentation is back in again.
## Comment 5702
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1524499 at http://sourceforge.net/support/tracker.php?aid=1524499
| V4 Mapi docs missing | https://api.github.com/repos/MonetDB/MonetDB/issues/1002/comments | 0 | 2020-11-30T09:15:26Z | 2024-06-27T11:19:04Z | https://github.com/MonetDB/MonetDB/issues/1002 | 753,300,543 | 1,002 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-18 02:44:20 +0200
From: @peterboncz
To: @mlkersten
Version: unspecified
Last updated: 2006-12-28 04:43:43 +0100
## Comment 5693
Date: 2006-07-18 14:44:20 +0200
From: @peterboncz
The new website on koala, while introducing some
new ideas that may be neat, is in a *DISMAL* state
of consistency.
Consistency is not only a matter of fixing broken links
though. It is a matter of complying to rules.
So, what are the rules? It would be nice to have a
website design document that describes the function of
the navigation elements (top bar, side bar, links side
bar).
Consider this report as a reverse engineering effort of
extracting rules from what is on display (partially
consistent) on koala now.
Some items:
* I think the decision to separate SQL, XQuery and
Kernel is good, as it separates audiences and backgrounds.
However, many people will click "MonetDB" thus ending
up in the kernel section, and getting lost there.
*CHANGEREQUEST* Therefore, I propose to rename
"MonetDB" to "MonetDB Kernel" and make it the third
entry in the top bar; i.e. not the default.
* navigation is one of the weakpoints of the old
website, as the *context* is changed unexpectedly by
following links.
So the new rule should be that sub-links within a topic
(i.e. the side-bar) should predictably always stay in
this subtopic. Jumpy links should be in green below.
This also means all web pages should belong to a single
easily identifyable topic. Thus, when you go there, you
are always in the same context.
*CHANGEREQUEST* everything related to download or
source install and quick-tour should be part of the
'download' topic.
* the functional differences between monet4 and monet5
are too large (documentation must be precise and
consistent to be of use) to have documentation that
covers both.
Additionally, the migration to monet5 will be a major
thing and therefore it is good to make this visible to
the end users in the documentation.
Finally, by separting now, phasing out version4 will be
more easy later.
Thus, all topics apart from Development should have
this Version4/Version5 division.
*CHANGEREQUEST*
In SQL this should be just done.
In XQuery this also be done. The V5 documentation
section should say not yet available and will follow later.
*CHANGEREQUEST* Version5 should for now be renamed
Version5-alpha. Otherwise people will go with the
latest version by default. Next release, you may remove
the alpha. At this point of time, I think it should be
a conscious choice to use V5.
* if you agree to rename the "MonetDB" topic in the top
bar to "MonetDB Kernel" (and put it in third position
only), it is clear that these topics do not need any
specific documentation about front-ends anymore.
Thus, both from the V4 and V5 documentation we should
remove documentation related to SQL and XQuery. It
should only about MIL and MAL usage.
This in order to comply that each piece of information
shoule belong only to a single context.
The same holds not only for front-ends but also for the
tutorial info and download info.
*CHANGEREQUEST*
in V4: Overview/Background: unite
Tutorials: remove
Tools: remove references to SQL tools
Installation guide: remove
in V5: SQL/XQuery: remove
## Comment 5694
Date: 2006-07-18 14:57:30 +0200
From: @grobian
Logged In: YES
user_id=963970
Peter, thanks for your feedback, I feel this are good
suggestions.
> Consistency is not only a matter of fixing broken links
> though. It is a matter of complying to rules.
>
> So, what are the rules? It would be nice to have a
> website design document that describes the function of
> the navigation elements (top bar, side bar, links side
> bar).
Perhaps, at least for internal use.
> However, many people will click "MonetDB" thus ending
> up in the kernel section, and getting lost there.
>
> *CHANGEREQUEST* Therefore, I propose to rename
> "MonetDB" to "MonetDB Kernel" and make it the third
> entry in the top bar; i.e. not the default.
I agree and support this, the location is not an issue for me.
> So the new rule should be that sub-links within a topic
> (i.e. the side-bar) should predictably always stay in
> this subtopic. Jumpy links should be in green below.
This was indeed the intention.
> *CHANGEREQUEST* everything related to download or
> source install and quick-tour should be part of the
> 'download' topic.
We separated QuickTour to give a better hand to people to
immediately jump into the "howtostart" arena.
> Finally, by separting now, phasing out version4 will be
> more easy later.
Agreed
> Thus, all topics apart from Development should have
> this Version4/Version5 division.
Questionable. In theory, SQL should only have a small piece
of backend specific stuff, that we would like to solve
through the quicktour thing.
> *CHANGEREQUEST*
> In SQL this should be just done.
> In XQuery this also be done. The V5 documentation
> section should say not yet available and will follow later.
agreed.
> *CHANGEREQUEST* Version5 should for now be renamed
> Version5-alpha. Otherwise people will go with the
> latest version by default. Next release, you may remove
> the alpha. At this point of time, I think it should be
> a conscious choice to use V5.
This is a good point. V5 is indeed now presented as the
'last' usable version. This is far from true (for outsiders).
> * if you agree to rename the "MonetDB" topic in the top
> bar to "MonetDB Kernel" (and put it in third position
> only), it is clear that these topics do not need any
> specific documentation about front-ends anymore.
Good point. Also resolves a lot of problems in that area.
> Thus, both from the V4 and V5 documentation we should
> remove documentation related to SQL and XQuery. It
> should only about MIL and MAL usage.
Agreed.
> This in order to comply that each piece of information
> shoule belong only to a single context.
Would clear up a lot, IMO.
> The same holds not only for front-ends but also for the
> tutorial info and download info.
>
> *CHANGEREQUEST*
> in V4: Overview/Background: unite
> Tutorials: remove
> Tools: remove references to SQL tools
> Installation guide: remove
>
> in V5: SQL/XQuery: remove
ok.
## Comment 5695
Date: 2006-07-18 15:18:06 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Peter strikes back... ;)) Did I miss something? Did
somebody offer money again for creating bug-reports?
(perhaps this is more a developers-mailing-list-discussion)
But, i agree with you on most points, except:
-- Version 5 should in my opinion be in the developer-
corner (at least for XQuery), and be hidden from the end-
users. End-users should in every case be directed
to 'production' releases. Perhaps MonetDB 5 should be
mentioned in news-items, benchmarks, development-corner
and roadmaps, but hide it in the menu-structure (at least
for XQuery).
The other way around: if MonetDB/SQL is intended to be
used with Monet5, then Monet4 should be 'hidden' from the
end-user there.
By the way: I made a design for the website structure a
little over a year ago, which basically describes what
Martin is doing. I can dig it up, if you want such a
document...
## Comment 5696
Date: 2006-07-18 23:10:46 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Dear all,
Thank you so far for the lively response on the new website
structure. Many of the issues raised in here
were already taken up by those directly involved in the
re-vamping process. A time-consuming activity, knowing
that the complete documentation of the product line is
around 400 A4 pages. The web site is just the tip of the
iceberg.
Furthermore, beware that this forum is a public forum,
which calls for a polite and informative prose.
Items not accessible outside CWI are at best a
starting point for a feature request, not a flamed
bug report.
## Comment 5697
Date: 2006-07-18 23:14:47 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Dear all,
Thank you so far for the lively response on the new website
structure. Many of the issues raised in here
were already taken up by those directly involved in the
re-vamping process. A time-consuming activity, knowing
that the complete documentation of the product line is
around 400 A4 pages. The web site is just the tip of the
iceberg.
Furthermore, beware that this forum is a public forum,
which calls for a polite and informative prose.
Items not accessible outside CWI are at best a
starting point for a feature request, not a flamed
bug report.
## Comment 5698
Date: 2006-12-28 16:43:43 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Most of these comments have been taken into account or have become
obsolete.
The current structure takes the departure of 3 functional productlines (top)
and a consistent navigational structure to their respective documentation
sections. The core of each section contains the details of the language.
Although the structure is not finished, the urgency of this bug report has become
invalid.
## Comment 5699
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1524497 at http://sourceforge.net/support/tracker.php?aid=1524497
| WEB: missing: Website Design | https://api.github.com/repos/MonetDB/MonetDB/issues/1001/comments | 0 | 2020-11-30T09:15:22Z | 2024-06-28T13:32:58Z | https://github.com/MonetDB/MonetDB/issues/1001 | 753,300,501 | 1,001 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-18 02:25:43 +0200
From: @peterboncz
To: @mlkersten
Version: unspecified
Last updated: 2006-12-28 04:44:22 +0100
## Comment 5690
Date: 2006-07-18 14:25:43 +0200
From: @peterboncz
http://koala.ins.cwi.nl:8000/projects/monetdb/GetGoing/Setup/
a number of things are bad here:
* this should be part of the Download topic
"all pages should belong to a certain topic of the
top bar"
* the menu is not colored, there must be some bug
somewhere.
* the source installation should be split in V4 and V5
sections.
* the tutorials should also be split in V4 and V5 and
provide different tutorials for different front-ends
V4(SQL,XQuery,MIL=gold) V5(SQL,MAL)
## Comment 5691
Date: 2006-12-28 16:44:22 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Comments have become obsolete.
## Comment 5692
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1524480 at http://sourceforge.net/support/tracker.php?aid=1524480
| WEB: download topic underdeveloped and buggy | https://api.github.com/repos/MonetDB/MonetDB/issues/1000/comments | 0 | 2020-11-30T09:10:35Z | 2024-06-28T13:32:57Z | https://github.com/MonetDB/MonetDB/issues/1000 | 753,297,184 | 1,000 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-18 02:04:57 +0200
From: @peterboncz
To: @mlkersten
Version: -- development
Last updated: 2006-07-23 10:06:27 +0200
## Comment 5687
Date: 2006-07-18 14:04:57 +0200
From: @peterboncz
http://koala.ins.cwi.nl:8000/projects/monetdb/MonetDB/Version4/Documentation/Tutorials/VOC/index.html
the TANAP link is disfunctional
the other 'The Hague' link points to the VOC page itself
## Comment 5688
Date: 2006-07-23 10:06:27 +0200
From: @mlkersten
Logged In: YES
user_id=490798
VOC tutorial is only relevant in the context of SQL.
## Comment 5689
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1524463 at http://sourceforge.net/support/tracker.php?aid=1524463
| VOC tutorial links disfunctional | https://api.github.com/repos/MonetDB/MonetDB/issues/999/comments | 0 | 2020-11-30T09:10:32Z | 2024-06-27T11:11:20Z | https://github.com/MonetDB/MonetDB/issues/999 | 753,297,157 | 999 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-18 01:55:29 +0200
From: @peterboncz
To: @mlkersten
Version: unspecified
Last updated: 2007-01-01 11:24:43 +0100
## Comment 5682
Date: 2006-07-18 13:55:29 +0200
From: @peterboncz
http://koala.ins.cwi.nl:8000/projects/monetdb/MonetDB/Version4/Documentation/mel/
the documentation enclosed in the Monet4 source code,
i.e. the doc/ directory is outdated in the new structure.
Most outwards links in the 'monet.mx' are disfunctional;
in the new website.
## Comment 5683
Date: 2006-07-18 14:26:53 +0200
From: @peterboncz
Logged In: YES
user_id=591107
ah, and don't forget to fix the picture, it is not linked in
correctly
or remove it, of course
## Comment 5684
Date: 2006-07-18 17:52:07 +0200
From: @peterboncz
Logged In: YES
user_id=591107
ah, and don't forget to fix the picture, it is not linked in
correctly
or remove it, of course
## Comment 5685
Date: 2007-01-01 23:24:43 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Used Xenu application to check the links in the new website.
The internal likes all worked fine. Remainder maintenance
should become part of the normal testing cycle.
## Comment 5686
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1524456 at http://sourceforge.net/support/tracker.php?aid=1524456
| WEB: monet.mx links outdated | https://api.github.com/repos/MonetDB/MonetDB/issues/998/comments | 0 | 2020-11-30T09:10:29Z | 2024-06-27T11:11:18Z | https://github.com/MonetDB/MonetDB/issues/998 | 753,297,128 | 998 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-18 01:54:46 +0200
From: @peterboncz
To: @mlkersten
Version: -- development
Last updated: 2006-07-23 10:04:56 +0200
## Comment 5679
Date: 2006-07-18 13:54:46 +0200
From: @peterboncz
http://koala.ins.cwi.nl:8000/projects/monetdb/MonetDB/Version4/Documentation/mil/
the documentation enclosed in the Monet4 source code,
i.e. the doc/ directory is outdated in the new structure.
Most outwards links in the 'mil.mx' are disfunctional;
in the new website.
## Comment 5680
Date: 2006-07-23 10:04:56 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Closed for the proto websit by fabian it seems
## Comment 5681
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1524455 at http://sourceforge.net/support/tracker.php?aid=1524455
| mil.mx links outdated | https://api.github.com/repos/MonetDB/MonetDB/issues/997/comments | 0 | 2020-11-30T09:10:26Z | 2024-06-27T11:11:18Z | https://github.com/MonetDB/MonetDB/issues/997 | 753,297,090 | 997 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-18 01:52:29 +0200
From: @peterboncz
To: @mlkersten
Version: -- development
Last updated: 2006-07-23 10:05:19 +0200
## Comment 5676
Date: 2006-07-18 13:52:29 +0200
From: @peterboncz
http://koala.ins.cwi.nl:8000/projects/monetdb/MonetDB/Version4/Documentation/mel/
the documentation enclosed in the Monet4 source code,
i.e. the doc/ directory is outdated in the new structure.
All outwards links in the 'mel.mx' are disfunctional;
in the new website.
Please fix.
## Comment 5677
Date: 2006-07-23 10:05:19 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Closed for the proto websit by fabian it seems
## Comment 5678
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1524451 at http://sourceforge.net/support/tracker.php?aid=1524451
| mel.mx links outdated | https://api.github.com/repos/MonetDB/MonetDB/issues/996/comments | 0 | 2020-11-30T09:10:23Z | 2024-06-27T11:11:16Z | https://github.com/MonetDB/MonetDB/issues/996 | 753,297,060 | 996 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-18 10:28:24 +0200
From: Henning Rode <<hrode>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2006-08-16 11:37:09 +0200
## Comment 5670
Date: 2006-07-18 10:28:24 +0200
From: Henning Rode <<hrode>>
The following query with two nested for-expressions
let $doc := doc("events.xml")
for $query in $doc//query
return <query> {$query/@id} {$query/qtext}
{ for $event in $doc//event
where $event/@rel = "not"
return <event>{$event/@rel}{$event/s}</event>
}</query>
results in the error message:
ERROR: combine_text_string: input BAT iter must be
sorted on tail.
ERROR: CMDcombine_text_string: operation failed.
or on a smaller instance:
ERROR: merged_union: tail of second BAT must be sorted.
ERROR: CMDmerged_union: operation failed.
this does not happen when the query is reformulated
expressing the where-clause in a predicate:
let $doc := doc("events.xml")
for $query in $doc//query
return <query> {$query/@id} {$query/qtext}
{ for $event in $doc//event[@rel = "not"]
return <event>{$event/@rel}{$event/s}</event>
}</query>
it also does not happen, when i remove the nesting of
the for-expressions:
let $doc := doc("events.xml")
for $event in $doc//event
where $event/@rel = "not"
return <event>{$event/@rel}{$event/s}</event>
## Comment 5671
Date: 2006-07-19 23:11:17 +0200
From: @drstmane
Logged In: YES
user_id=572415
Henning, could you please try whether the problem also
occurs when you start you Mserver with property-checking
enabled, i.e., with "--debug=10"?
## Comment 5672
Date: 2006-07-19 23:33:53 +0200
From: @drstmane
Logged In: YES
user_id=572415
tests added to CVS (development trunk) in
pathfinder/tests/BugTracker/Tests/where-clause.SF-1524344*
## Comment 5673
Date: 2006-07-20 09:45:22 +0200
From: Henning Rode <<hrode>>
Logged In: YES
user_id=909189
I tested it with "--debug=10" as Stefan suggested but
without any success. The error remained the same.
I can only add now that the script runs without problems,
when i exchange the inner for-loop:
from
for $event in $doc//event
to
for $event in $query//event
(which had been the initial intention of the author :-) )
still that does not explain why it fails in the other case.
## Comment 5674
Date: 2006-08-16 23:37:07 +0200
From: @peterboncz
Logged In: YES
user_id=591107
problem in forward mapping after recognized join
iter numbers were occuring out of order, causing havoc.
## Comment 5675
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1524344 at http://sourceforge.net/support/tracker.php?aid=1524344
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| PF: problem in where-clause | https://api.github.com/repos/MonetDB/MonetDB/issues/995/comments | 0 | 2020-11-30T09:10:19Z | 2024-06-27T11:11:15Z | https://github.com/MonetDB/MonetDB/issues/995 | 753,297,021 | 995 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-11 09:28:41 +0200
From: Wouter Alink <<alink>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2007-12-15 04:20:03 +0100
## Comment 5662
Date: 2006-07-11 21:28:41 +0200
From: Wouter Alink <<alink>>
Sometimes (don't know exactly when it occurs, but at
least Michael Schmidt and I have noticed it) the
dbfarm gets broken when adding documents to the
database. Subsequently shredding new documents
implicitly or explicitly (with the same name) results
in errors like:
ERROR: [rename]: 29 times inserted nil due to errors
at
tuples "pre_size", "pre_level", "pre_prop", "pre_kind"
, "qn_uri", "qn_prefix".
ERROR: [rename]: first error was:
ERROR: rename(<tmp_351>,pre_size2): operation failed
ERROR: interpret_unpin: [rename] bat=171,stamp=-1285
OVERWRITTEN
ERROR: BBPdecref: tmp_253 does not have pointer fixes.
ERROR: interpret_params: +(param 2): evaluation error.
Some of the characteristics:
- so far has been noticed on Linux systems (Suse and
Redhat)
- has been noticed on both 32 and 64 bit machines
- until now has only been noticed with relatively
large documents (100MB+)
- occured in 0.11.3 (few months back) as well as the
0.12.0 release
- occurs with both implicit (using "doc
("/home/.../...xml")") and explicit shredding using
shred_doc("...","...").
- only clearing the dbfarm folder seems to solve the
problem
I can't reproduce it, but if anybody notices the same
error... please let it be known.
p.s. maybe it would be better not to delete the
dbfarm folder when this error occurs, but keep a copy
of it so that it can be analysed ;)
Question for the GDK-gurus among us: could it have
anything to do with the mmap-ing of bats in the
shredder?
## Comment 5663
Date: 2006-07-11 21:45:13 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
had a look at shredder.mx (CVS-HEAD): from line 602 and
1644 it appears that no post processing is done when the
libxml halts. So my question: what happens with the non-
finalized (possibly mmap-ed) bats (dstBAT[]) in that case?
Shouldn't there be some cleaning-up code?
## Comment 5664
Date: 2006-07-13 16:43:03 +0200
From: @peterboncz
Logged In: YES
user_id=591107
*please* be explicit whether you are working on the HEAD or
in the Stablee
## Comment 5665
Date: 2006-07-13 23:00:35 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
sorry, my fault. in my last comment i meant: 0.12.1
## Comment 5666
Date: 2006-10-26 16:03:49 +0200
From: @grobian
Logged In: YES
user_id=963970
noticed anything lately?
## Comment 5667
Date: 2006-12-14 18:31:50 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
there was a bug in TMsubcommit (gdk_delta.mx) that caused repositories to corrupt.
(some heaps were not saved)
This has been fixed in the 0.12 => 0.14, september 2006 timeframe
0.12 still has this bug.
In any case, I also find it hard to provide a test script for this one.
## Comment 5668
Date: 2007-12-15 04:20:03 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 365 days (the time period specified by
the administrator of this Tracker).
## Comment 5669
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1520735 at http://sourceforge.net/support/tracker.php?aid=1520735
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| XQ: broken dbfarm | https://api.github.com/repos/MonetDB/MonetDB/issues/994/comments | 0 | 2020-11-30T09:10:16Z | 2024-06-28T13:32:57Z | https://github.com/MonetDB/MonetDB/issues/994 | 753,296,986 | 994 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-11 04:21:17 +0200
From: Gustavo Hispagnol <<gmhispagnol>>
To: @njnes
Version: -- development
Last updated: 2006-07-12 10:38:55 +0200
## Comment 5656
Date: 2006-07-11 16:21:17 +0200
From: Gustavo Hispagnol <<gmhispagnol>>
Group by <alias> functionality is not working in
MonetDB 4.12:
create table test(a int);
select a as b from test group by b; <<fails with a
message like "b is unknown or ambibuous"
## Comment 5657
Date: 2006-07-12 10:38:55 +0200
From: @grobian
Logged In: YES
user_id=963970
Thanks for your bug report. However, I think you're a bit
confused here. Your group by statement is semantically
impossible, although technically possible in this case.
You are probably looking for something like this, which does
work:
select count(*) as b from test group by a order by b;
Obviously, a "select count(*) as b from test group by b;"
would yield in a non-sense query. Therefore, the group by
operator only deals with real columns.
## Comment 5658
Date: 2006-07-12 14:31:33 +0200
From: Gustavo Hispagnol <<gmhispagnol>>
Logged In: YES
user_id=818683
The example I gave is just a test case and is semantically
similar to "select distinct a as b from test" (no
impossible!). Lets look at a very common (real) scenario:
create table a(f1 varchar(20),f2 int);
select coalesce(f1,'EMPTY') as bug_alias,sum(f2) group by
bug_alias;
I want to group by an **expression**, so I have to use a
field alias. It works perfectly well in 4.10.
## Comment 5659
Date: 2006-07-13 09:31:18 +0200
From: @njnes
Logged In: YES
user_id=43556
Allthough strict SQL doesn't allow selection alias
references it is a common feature of many other dbms-es.
Therefor I added code to allow for this.
Also a bug test script is added for the given two cases.
In BugTracker/Tests/groupby_with_alias
## Comment 5660
Date: 2006-07-14 19:57:53 +0200
From: Gustavo Hispagnol <<gmhispagnol>>
Logged In: YES
user_id=818683
Any ideia on next release date? This bug is a showstopper
for me.
Many thanks for the fix.
## Comment 5661
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1520575 at http://sourceforge.net/support/tracker.php?aid=1520575
| Group By <alias> not working | https://api.github.com/repos/MonetDB/MonetDB/issues/993/comments | 0 | 2020-11-30T09:10:13Z | 2024-06-27T11:11:13Z | https://github.com/MonetDB/MonetDB/issues/993 | 753,296,948 | 993 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-06 03:46:38 +0200
From: @MarcinZukowski
To: MonetDB4 devs <<bugs-monetdb4>>
Version: -- development
Last updated: 2008-08-05 02:13:39 +0200
## Comment 5645
Date: 2006-07-06 15:46:38 +0200
From: @MarcinZukowski
Start server with a mapi listener, and run e.g. this
shell script:
!/bin/sh
i=0;
while [ $i -lt 100 ] ; do
echo $i
echo "module(alarm);sleep(10);" | MapiClient &
usleep 10000
((i++))
done
Result on the server side:
MT_create_sema: ran out of semaphores
and it dies
## Comment 5646
Date: 2007-01-31 13:43:59 +0100
From: @MarcinZukowski
Logged In: YES
user_id=607094
Originator: YES
Still crashes, with:
Monet Database Server V4.17.1
Copyright (c) 1993-2007, CWI. All rights reserved.
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
MonetDB>module(mapi);
MonetDB>mil_start();
MonetDB>!FATAL: THRnew: too many threads
## Comment 5647
Date: 2007-05-29 13:31:22 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
Originator: YES
Checked the current status.
Still fails.
## Comment 5648
Date: 2007-05-29 14:49:44 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Fatal is gone now. But you will still ge the message, out of threads.
Could you find the time to add a portable script to the testing of M4. A python script for example.
(status is Pending until the test is there)
## Comment 5649
Date: 2007-05-29 15:28:35 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
Originator: YES
Well, not fixed yet.
If I run this script:
i=0; while [ $i -lt 100 ] ; do echo $i; echo "module(alarm);sleep(10);" | MapiClient & usleep 10000; ((i++)); done
a few times, I get segfault.
If MonetDB is in gdb, I get it every time:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1082132800 (LWP 1095)]
0x00002aaab7693e6b in xchange_challenge (father=0x2aaaabe96750, stk=1,
fdin=0x11cf860, fdout=0x64b110, new_client=1 '\001')
at /ufs/marcin/monet/MonetDB4/src/mapi/mapi.mx:702
702 c->fdin = fdin;
(gdb) p c
$1 = (Client) 0x0
As for a portable script, if bash is not portable enough, someone with Python experience (I have none) would do it X100 faster :)
## Comment 5650
Date: 2007-07-31 13:07:47 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Is this still a problem? I don't seem to be able to reproduce the crash.
And no, bash is not portable enough. You can't use it on Windows.
## Comment 5651
Date: 2007-07-31 15:00:34 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
Originator: YES
Yup, still fails. Server output, fresh CVS build:
$ Mserver
MonetDB Server v4.19.0
based on GDK v1.19.0
Copyright (c) 1993-2007, CWI. All rights reserved.
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit OIDs; dynamically linked
.
Visit http://monetdb.cwi.nl/ for further information.
MonetDB>module(mapi);
MonetDB>mil_start();
MonetDB>!WARNING: THRnew: too many threads
!WARNING: THRnew: too many threads
!WARNING: THRnew: too many threads
!WARNING: THRnew: too many threads
!WARNING: THRnew: too many threads
!WARNING: THRnew: too many threads
!WARNING: THRnew: too many threads
!WARNING: THRnew: too many threads
!WARNING: THRnew: too many threads
!WARNING: THRnew: too many threads
!WARNING: THRnew: too many threads
!WARNING: THRnew: too many threads
!WARNING: THRnew: too many threads
!WARNING: THRnew: too many threads
!WARNING: THRnew: too many threads
Segmentation fault
## Comment 5652
Date: 2007-08-02 10:28:52 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Some experimentation on two different machines shows that you can get the crash pretty reliably on Marcin's dual core system, but not at all on my single core. There may be more differences in system libraries.
This probably needs to be investigated more by someone with a dual core system. Stefan, Niels, feel free...
## Comment 5653
Date: 2007-09-09 11:21:59 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
The test ran on M5/MAL leads to a correct response,
i.e. running out of client slots, which is a hardwired
limit. The system does not crash.
## Comment 5654
Date: 2008-08-05 02:13:39 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
THis bug does not seem to be relevant to investigate
due to the deprecated M4 module loader.
## Comment 5655
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1518158 at http://sourceforge.net/support/tracker.php?aid=1518158
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.
| M4: MonetDB crashes with multiple active connections | https://api.github.com/repos/MonetDB/MonetDB/issues/992/comments | 0 | 2020-11-30T09:10:09Z | 2024-06-28T13:32:56Z | https://github.com/MonetDB/MonetDB/issues/992 | 753,296,898 | 992 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-04 01:56:06 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2007-01-17 05:42:59 +0100
## Comment 5640
Date: 2006-07-04 13:56:06 +0200
From: @drstmane
When compiling the MonetDB5-4.99.19.tar.gz tarball with
`configure ; make ; make install` (in a build directory
that is different from the source directory), I get:
Making all in tools
make[4]: Entering directory
`/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Stable/.GNU.64.64.d..BUILD./MONET5/src/tools'
x c monetdb5-config.mx
/ufs/manegold/bin/x: line 5: type: c: not found
/ufs/manegold/bin/x: line 5: type: monetdb5-config.mx:
not found
/ufs/manegold/bin/x: line 10: type: c: not found
/ufs/manegold/bin/x: line 10: type: monetdb5-config.mx:
not found
gcc -m64 -g -O2 -std=c99 -Wall -W
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label
-Wno-sign-compare -D_REENTRANT monetdb5-config.c
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Stable/monet5/src/tools/monetdb5-config.mx.in
-o monetdb5-config
gcc: monetdb5-config.c: No such file or directory
make[4]: *** [monetdb5-config] Error 1
make[4]: Leaving directory
`/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Stable/.GNU.64.64.d..BUILD./MONET5/src/tools'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Stable/.GNU.64.64.d..BUILD./MONET5/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Stable/.GNU.64.64.d..BUILD./MONET5/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Stable/.GNU.64.64.d..BUILD./MONET5'
make: *** [all] Error 2
Moreover, there is a "bootstrap" file in the tarball
that should not be there.
Also, there is IMHO no documentation, how to compile
MonetDB/Five from theis tarball.
## Comment 5641
Date: 2007-01-17 05:42:59 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
The tarball should now be available through our nightly builds.
It presumable compiles, or otherwise the testweb would already
triggers a warning.
The old tarball version 4.99 can be removed.
## Comment 5642
Date: 2007-01-17 06:55:37 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
For the sake of "correctness" and "accuracy":
I agree with closing this one as it is out of date (but since the respective tarball has never been changed I doubt it has formally been "fixed").
While tarballs also for MonetDB5 will be available from the DailyBuilds starting from later today (i.e., once testing finishes successfully), the is unfortunately no a priori guarantee that these (or any other) tarballs indeed do/will work. Nightly testing does only build, but not automatically compile/use/test the tarballs. Hence, testing/verification "by hand" is still required.
## Comment 5643
Date: 2007-01-17 07:19:03 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Point taken. For those in need, a scheme to test nightly builds is in the making
as part of the drive to simplify source installation of a MonetDB/{SQL,XQuery}
for developers.
This will hopefully trigger error reports with the tarballs earlier.
The hooks for this are already in the new website,
http://koala.ins.cwi.nl:8000/projects/monetdb-mk/Download/index.html
Development is under control of Niels
## Comment 5644
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1516928 at http://sourceforge.net/support/tracker.php?aid=1516928
| M5: compilation from tarball fails | https://api.github.com/repos/MonetDB/MonetDB/issues/991/comments | 0 | 2020-11-30T09:10:06Z | 2024-06-27T11:11:12Z | https://github.com/MonetDB/MonetDB/issues/991 | 753,296,870 | 991 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-29 06:43:38 +0200
From: @MarcinZukowski
To: @njnes
Version: -- development
Last updated: 2006-07-13 09:59:25 +0200
## Comment 5636
Date: 2006-06-29 18:43:38 +0200
From: @MarcinZukowski
Seems the left modulo operand is casted to the datatype
of the right one. I guess the rationale was, that lng
mod int produces int, but the cast should be done
*after* the computation.
Example:
MonetDB>print( lng(2000000000) % 10 );
[ 0 ]
MonetDB>print( lng(4000000000) % 10 );
[ -6 ]
MonetDB>print( lng(4000000000) % lng(10) );
[ 0 ]
MonetDB>printf("%d\n", lng(4000000000) % 10);
-6
For division it's fine:
MonetDB>print( lng(4000000000) / 10 );
[ 400000000 ]
MonetDB>printf("%d\n", lng(4000000000) / 10);
!ERROR: monet_sprintf(): illegal type in param 1.
!ERROR: print_format: operation failed.
## Comment 5637
Date: 2006-07-13 09:59:25 +0200
From: @njnes
Logged In: YES
user_id=43556
In the arith module a cast to the result type was used
before the module operator was called. A the result of
lng%int is defined as an int, we should use an intermediate
type of lng as the C operator % requires two equal types, to
work correctly.
Added test script to BugTracker directory
## Comment 5638
Date: 2006-07-13 10:25:16 +0200
From: @swingbit
Logged In: YES
user_id=883451
The same problem occurs in bat_arith.
However, [%] and [:%=] behave differently:
[%] has the same problem fixed by Niels in module arith
MonetDB>var a:=new(void,lng).seqbase(0@0);
MonetDB>a.append(4000000000LL);
MonetDB>[%](a,10).print();
-----------------
h t name
void int type
-----------------
[ 0@0, -6 ]
[:%=] does not match any function
MonetDB>[:%=](a,10);
!ERROR: interpret: no matching MIL operator to
'[:%=](BAT[oid,lng], int)'.
!MAYBE YOU MEAN:
! [:%=](BAT[void,dbl], dbl) : BAT[void,dbl]
! [:%=](dbl, BAT[void,dbl]) : BAT[void,dbl]
! [:%=](BAT[void,dbl], BAT[void,dbl]) : BAT[void,dbl]
! [:%=](BAT[void,flt], flt) : BAT[void,flt]
! [:%=](flt, BAT[void,flt]) : BAT[void,flt]
! [:%=](BAT[void,flt], BAT[void,flt]) : BAT[void,flt]
! [:%=](BAT[void,lng], lng) : BAT[void,lng]
! [:%=](lng, BAT[void,lng]) : BAT[void,lng]
! [:%=](BAT[void,lng], BAT[void,lng]) : BAT[void,lng]
! [:%=](BAT[void,int], int) : BAT[void,int]
! [:%=](int, BAT[void,int]) : BAT[void,int]
! [:%=](BAT[void,int], BAT[void,int]) : BAT[void,int]
! [:%=](BAT[void,sht], sht) : BAT[void,sht]
! [:%=](sht, BAT[void,sht]) : BAT[void,sht]
! [:%=](BAT[void,sht], BAT[void,sht]) : BAT[void,sht]
## Comment 5639
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1514452 at http://sourceforge.net/support/tracker.php?aid=1514452
| modulo (%) produces incorrect results for lng | https://api.github.com/repos/MonetDB/MonetDB/issues/990/comments | 0 | 2020-11-30T09:10:03Z | 2024-06-27T11:11:11Z | https://github.com/MonetDB/MonetDB/issues/990 | 753,296,820 | 990 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-23 09:36:40 +0200
From: @grobian
To: @sjoerdmullender
Version: -- development
Last updated: 2006-11-10 09:48:54 +0100
## Comment 5628
Date: 2006-06-23 21:36:40 +0200
From: @grobian
(cd .libs/lib_pathfinder.lax/libcompiler2.a && ar x
/var/tmp/portage/monetdb-4.12.0/work/pathfinder-0.12.0/runtime/../compiler/.libs/libcompiler2.a)
gcc -m32 -dynamiclib ${wl}-undefined
${wl}dynamic_lookup -o .libs/lib_pathfinder.0.0.0.dylib
.libs/lib_pathfinder_la-pathfinder.glue.o
.libs/lib_pathfinder_la-pathfinder.o
.libs/lib_pathfinder.lax/libcompiler1.a/libcompiler1_la-compile.o
.libs/lib_pathfinder.lax/libschema.a/libschema_la-import.o
.libs/lib_pathfinder.lax/libdebug.a/libdebug_la-abssynprint.o
.libs/lib_pathfinder.lax/libdebug.a/libdebug_la-coreprint.o
.libs/lib_pathfinder.lax/libdebug.a/libdebug_la-logdebug.o
.libs/lib_pathfinder.lax/libdebug.a/libdebug_la-physdebug.o
.libs/lib_pathfinder.lax/libdebug.a/libdebug_la-prettyp.o
.libs/lib_pathfinder.lax/libmem.a/libmem_la-array.o
.libs/lib_pathfinder.lax/libmem.a/libmem_la-mem.o
.libs/lib_pathfinder.lax/libparser.a/libparser_la-abssyn.o
.libs/lib_pathfinder.lax/libparser.a/libparser_la-parser.tab.o
.libs/lib_pathfinder.lax/libparser.a/libparser_la-scanner.yy.o
.libs/lib_pathfinder.lax/libsemantics.a/libsemantics_la-functions.o
.libs/lib_pathfinder.lax/libsemantics.a/libsemantics_la-normalize.o
.libs/lib_pathfinder.lax/libsemantics.a/libsemantics_la-ns.o
.libs/lib_pathfinder.lax/libsemantics.a/libsemantics_la-subtyping.o
.libs/lib_pathfinder.lax/libsemantics.a/libsemantics_la-typecheck.o
.libs/lib_pathfinder.lax/libsemantics.a/libsemantics_la-types.o
.libs/lib_pathfinder.lax/libsemantics.a/libsemantics_la-varscope.o
.libs/lib_pathfinder.lax/libsemantics.a/libsemantics_la-xquery_fo.o
.libs/lib_pathfinder.lax/libcore.a/libcore_la-core.o
.libs/lib_pathfinder.lax/libcore.a/libcore_la-coreopt.o
.libs/lib_pathfinder.lax/libcore.a/libcore_la-fs.o
.libs/lib_pathfinder.lax/libcore.a/libcore_la-simplify.o
.libs/lib_pathfinder.lax/libalgebra.a/libalgebra_la-algebra.o
.libs/lib_pathfinder.lax/libalgebra.a/libalgebra_la-algebra_cse.o
.libs/lib_pathfinder.lax/libalgebra.a/libalgebra_la-algopt.o
.libs/lib_pathfinder.lax/libalgebra.a/libalgebra_la-builtins.o
.libs/lib_pathfinder.lax/libalgebra.a/libalgebra_la-core2alg.o
.libs/lib_pathfinder.lax/libalgebra.a/libalgebra_la-logical.o
.libs/lib_pathfinder.lax/libalgebra.a/libalgebra_la-ordering.o
.libs/lib_pathfinder.lax/libalgebra.a/libalgebra_la-physical.o
.libs/lib_pathfinder.lax/libalgebra.a/libalgebra_la-planner.o
.libs/lib_pathfinder.lax/libalgebra.a/libalgebra_la-properties.o
.libs/lib_pathfinder.lax/libmil.a/libmil_la-mil.o
.libs/lib_pathfinder.lax/libmil.a/libmil_la-mil_opt.o
.libs/lib_pathfinder.lax/libmil.a/libmil_la-milgen.o
.libs/lib_pathfinder.lax/libmil.a/libmil_la-milprint.o
.libs/lib_pathfinder.lax/libmil.a/libmil_la-milprint_summer.o
.libs/lib_pathfinder.lax/libcompiler2.a/libcompiler2_la-env.o
.libs/lib_pathfinder.lax/libcompiler2.a/libcompiler2_la-oops.o
.libs/lib_pathfinder.lax/libcompiler2.a/libcompiler2_la-pfstrings.o
.libs/lib_pathfinder.lax/libcompiler2.a/libcompiler2_la-qname.o
.libs/lib_pathfinder.lax/libcompiler2.a/libcompiler2_la-scope.o
.libs/lib_pathfinder.lax/libcompiler2.a/libcompiler2_la-timer.o
.libs/lib_pathfinder.lax/libcompiler2.a/libcompiler2_la-variable.o
-L/usr/lib /usr/lib/libxml2.dylib
/usr/lib/libpthread.dylib /usr/lib/libz.dylib
/usr/lib/libm.dylib -lz -lpthread
/usr/lib/libiconv.dylib -lm -ldl
-L/var/tmp/portage/monetdb-4.12.0/work/MonetDB-4.12.0/lib/MonetDB
-L/var/tmp/portage/monetdb-4.12.0/work/MonetDB-4.12.0/lib
/usr/lib/libbat.dylib /usr/lib/libmutils.dylib
/usr/lib/libbz2.dylib /usr/lib/libdl.dylib
/usr/lib/libmonet.dylib /usr/lib/libstream.dylib
/var/tmp/portage/monetdb-4.12.0/work/MonetDB-4.12.0/lib/MonetDB/.libs/lib_builtin.dylib
/var/tmp/portage/monetdb-4.12.0/work/MonetDB-4.12.0/src/monet/.libs/libmonet.dylib
/var/tmp/portage/monetdb-4.12.0/work/MonetDB-4.12.0/src/gdk/.libs/libbat.dylib
/var/tmp/portage/monetdb-4.12.0/work/MonetDB-4.12.0/src/common/.libs/libstream.dylib
/var/tmp/portage/monetdb-4.12.0/work/MonetDB-4.12.0/src/common/.libs/libmutils.dylib
/usr/lib/libssl.dylib /usr/lib/libcrypto.dylib
/var/tmp/portage/monetdb-4.12.0/work/MonetDB-4.12.0/lib/MonetDB/.libs/lib_ascii_io.dylib
/var/tmp/portage/monetdb-4.12.0/work/MonetDB-4.12.0/lib/MonetDB/.libs/lib_algebra.dylib
/var/tmp/portage/monetdb-4.12.0/work/MonetDB-4.12.0/lib/MonetDB/.libs/lib_sys.dylib
/var/tmp/portage/monetdb-4.12.0/work/MonetDB-4.12.0/lib/MonetDB/.libs/lib_constant.dylib
/var/tmp/portage/monetdb-4.12.0/work/MonetDB-4.12.0/lib/MonetDB/.libs/lib_mapi.dylib
/var/tmp/portage/monetdb-4.12.0/work/MonetDB-4.12.0/src/modules/plain/.libs/lib_streams.dylib
/var/tmp/portage/monetdb-4.12.0/work/MonetDB-4.12.0/lib/MonetDB/.libs/lib_streams.dylib
-m32 -Wl,-search_paths_first -install_name
/usr/lib/MonetDB/lib_pathfinder.0.dylib
-Wl,-compatibility_version -Wl,1 -Wl,-current_version
-Wl,1.0
ld: Undefined symbols:
_ssl_rastream referenced from lib expected to be
defined in libstream
_ssl_wastream referenced from lib expected to be
defined in libstream
_stream_readline referenced from lib expected to be
defined in libstream
_BBPrecycle_minsize referenced from lib expected to be
defined in libbat
/usr/bin/libtool: internal link edit command failed
make[3]: *** [lib_pathfinder.la] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Anyone a clue why this occurs? Will try to do it
manually now. First dropping ppc-macos keyword and
committing ebuild.
## Comment 5629
Date: 2006-06-25 10:48:01 +0200
From: @grobian
Logged In: YES
user_id=963970
This seems to be it for me. Can it have to do anything with
the lab/testing machines having software installed a stock
install hasn't?
## Comment 5630
Date: 2006-06-25 14:36:54 +0200
From: @drstmane
Logged In: YES
user_id=572415
As far as I'm concerned, our 32-bit MacOS X 10.4/Darwin 8.6
testing box has only bison, pcre, and pkgconfig installed un
addition to whatever the respective sysadmin has installed
(which is IMHO just the plain system).
In addition to the afore mentioned software, our 64-bit
MacOS X 10.4/Darwin 8.6 testing box has 64-bit versions of
libiconv, libxml2, and zlib installed, becuase the default
installation does only provide the respective 32-bit version.
I'm not aware of any other additionally installed software
that would be required to compile MonetDB and/or its companions.
Nightly testing uses `source conf/conf.bash` to set the
environment for compilation. In addition to the locations of
the above mentioned software, this adds the following
locations to the PATH: "/usr/local/bin" "/sw/bin" "/usr/bin"
, and explicitly calls configure with "--with-z=..." &
"--with-iconv".
In fact, I doubt than any of these are related to your
problem, which rather seems somehow ssl-related...??
Maybe, you should compare your configure output for MonetDB
& pathfinder with the one on the testoing machine(s):
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.GNU.32.32.d-Darwin8.6.0/config.out_log.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.GNU.32.32.d-Darwin8.6.0/config.out_log.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.GNU.64.64.d-Darwin8.6.0/config.out_log.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.GNU.64.64.d-Darwin8.6.0/config.out_log.html
## Comment 5631
Date: 2006-06-25 14:48:02 +0200
From: @grobian
Logged In: YES
user_id=963970
The problem is related to libtool (?) apparently finding and
using the already installed libraries in /usr/lib while it
should not. Those old libraries do not contain new symbols
(such as ssl stuff, because only this release we enabled ssl
by default).
Outside portage with a prefix != /usr it works fine, so I'm
trying to figure out how the autotooled jungle works and why
it includes those wrong libs, which it doesn't when having a
prefixed install.
## Comment 5632
Date: 2006-06-25 14:49:49 +0200
From: @grobian
Logged In: YES
user_id=963970
additional question; is it just pure luck that SQL
installation has no problems, or doesn't it link against
libstream using SSL symbols? ...
## Comment 5633
Date: 2006-06-25 23:31:25 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: nobody@users.sourceforge.net ----
Logged In: NO
Is the following perhaps related?
I tried to compile MonetDB 4.12.1 on isoda.ins.cwi.nl
(64bit machine) with the options --enable-bi1970-01-01 01:00:32 +0100 --enable-
oid32. I don't know for sure if I am allowed to set the
bits to 32, but I thought I had done this before
successfully.
Anyway, I got:
/bin/sh ../../../libtool --tag=CC --mode=compile gcc -m32 -
DHAVE_CONFIG_H -I. -
I/export/scratch1/alink/src/tmp/MonetDB/src/modules/plain -
I../../.. -
I/export/scratch1/alink/src/tmp/MonetDB/src/modules/plain -
I../../common -
I/export/scratch1/alink/src/tmp/MonetDB/src/modules/plain/.
./../common -I../../gdk -
I/export/scratch1/alink/src/tmp/MonetDB/src/modules/plain/.
./../gdk -I../../monet -
I/export/scratch1/alink/src/tmp/MonetDB/src/modules/plain/.
./../monet -DLIBRADIX -O2 -std=c99 -Wall -W -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 -
Werror-implicit-function-declaration -Werror -Wno-unused-
function -Wno-unused-label -D_REENTRANT -c -o
lib_radix_la-radix.lo `test -f 'radix.c' ||
echo '/export/scratch1/alink/src/tmp/MonetDB/src/modules/pl
ain/'`radix.c
gcc -m32 -DHAVE_CONFIG_H -I. -
I/export/scratch1/alink/src/tmp/MonetDB/src/modules/plain -
I../../.. -
I/export/scratch1/alink/src/tmp/MonetDB/src/modules/plain -
I../../common -
I/export/scratch1/alink/src/tmp/MonetDB/src/modules/plain/.
./../common -I../../gdk -
I/export/scratch1/alink/src/tmp/MonetDB/src/modules/plain/.
./../gdk -I../../monet -
I/export/scratch1/alink/src/tmp/MonetDB/src/modules/plain/.
./../monet -DLIBRADIX -O2 -std=c99 -Wall -W -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 -
Werror-implicit-function-declaration -Werror -Wno-unused-
function -Wno-unused-label -D_REENTRANT -c radix.c -fPIC -
DPIC -o .libs/lib_radix_la-radix.o
In file included
from /export/scratch1/alink/src/tmp/MonetDB/src/modules/pla
in/radix.mx:1095:
/usr/lib/gcc/x86_64-redhat-
linux/4.0.2/include/xmmintrin.h:34:3: error: error "SSE
instruction set not enabled"
make[7]: *** [lib_radix_la-radix.lo] Error 1
make[7]: Leaving directory
`/export/scratch1/alink/src/tmp/MonetDB/Linux/src/modules/p
lain'
make[6]: *** [all] Error 2
make[6]: Leaving directory
`/export/scratch1/alink/src/tmp/MonetDB/Linux/src/modules/p
lain'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory
`/export/scratch1/alink/src/tmp/MonetDB/Linux/src/modules'
make[4]: *** [all] Error 2
make[4]: Leaving directory
`/export/scratch1/alink/src/tmp/MonetDB/Linux/src/modules'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/export/scratch1/alink/src/tmp/MonetDB/Linux/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/export/scratch1/alink/src/tmp/MonetDB/Linux/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/export/scratch1/alink/src/tmp/MonetDB/Linux'
make: *** [all] Error 2
Additional info: during configure I got the following
warning:
checking for winsock.h... no
checking xmmintrin.h usability... no
checking xmmintrin.h presence... yes
configure: WARNING: xmmintrin.h: present but cannot be
compiled
configure: WARNING: xmmintrin.h: check for missing
prerequisite headers?
configure: WARNING: xmmintrin.h: see the Autoconf
documentation
configure: WARNING: xmmintrin.h: section "Present But
Cannot Be Compiled"
configure: WARNING: xmmintrin.h: proceeding with the
preprocessor's result
configure: WARNING: xmmintrin.h: in the future, the
compiler will take precedence
configure: WARNING: --------------------------------
----------
configure: WARNING: Report this to the
AC_PACKAGE_NAME lists.
configure: WARNING: --------------------------------
----------
checking for xmmintrin.h... yes
checking for pid_t... yes
## Comment 5634
Date: 2006-11-10 21:48:54 +0100
From: @njnes
Logged In: YES
user_id=43556
closing this bug as we moved on to 0.14 and pathfinder is
compiled on darwin every night.
## Comment 5635
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1511530 at http://sourceforge.net/support/tracker.php?aid=1511530
| Compilation of 0.12.0 fails on Darwin | https://api.github.com/repos/MonetDB/MonetDB/issues/989/comments | 0 | 2020-11-30T09:09:57Z | 2024-06-27T11:11:10Z | https://github.com/MonetDB/MonetDB/issues/989 | 753,296,777 | 989 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-23 11:40:33 +0200
From: Jan Flokstra <<jflokstra>>
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2007-02-19 04:23:28 +0100
## Comment 5622
Date: 2006-06-23 11:40:33 +0200
From: Jan Flokstra <<jflokstra>>
We encountered a problem with path expressions on an
xhtml file with a DOCtype definition and xmlns
attributes inside <html> tags. The simplified xhtml
file is:
================ tiny_xhtml.xml======================
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN" "http://www.w3.or
g/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<example1>
<html xmlns="http://www.w3.org/1999/xhtml"
xml:lang="en" lang="en">
<head>
<title>SIGIR'07 - Amsterdam</title>
<link rel="stylesheet" href="style.css" type="text/css"
media="all" />
<link rel="shortcut icon" href="images/sigir07.ico"
type="image/x-icon" />
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1" />
</head>
<body class="sigirViewPage"><div class="fullPage">
<div class="sigirMiddleContainer"><div
class="sigirLeftBar">
<div class="sigirLeftBarContents">
<strong><a class="sigirLink"
href="http://www.sigir2007.org">SIGIR'07 Home</a></
strong>
</div></div></div></div></body></html>
</example1>
=========================================================
When we do the query:
fn:doc("tiny_xhtml.xml")//html
The result is empty. When we remove the DOCtype
definition and all attributes from the <html> tags the
query executes correct. Anybody any idea?
## Comment 5623
Date: 2006-06-23 11:49:09 +0200
From: @Teggy
Logged In: YES
user_id=642632
Hi,
did you try ro run the query
fn:doc("tiny_xhtml.xml")//*:html
against the document? (Note: the 'html' element carries a
(default) namespace.)
Cheers,
--Torsten
## Comment 5624
Date: 2006-06-23 12:07:29 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Teggy, thanks this worked. We were not 100% sure if it was
bug or a feature:-)We now know it is a feature.
I will close the bug immediately.
## Comment 5625
Date: 2006-12-02 18:40:20 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Re-opened, as no test has been provided, yet.
User (submitter) and/or developer (assignee),
please supply a respective test,
or explain why a test is not required/possible.
## Comment 5626
Date: 2007-02-19 16:23:28 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Test added.
## Comment 5627
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1511195 at http://sourceforge.net/support/tracker.php?aid=1511195
| DOCtype and/or xmlns causes empty path expr. result | https://api.github.com/repos/MonetDB/MonetDB/issues/988/comments | 0 | 2020-11-30T09:09:54Z | 2024-06-27T11:11:09Z | https://github.com/MonetDB/MonetDB/issues/988 | 753,296,742 | 988 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-23 12:37:16 +0200
From: Wouter Alink <<alink>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-12-14 06:28:36 +0100
## Comment 5617
Date: 2006-06-23 00:37:16 +0200
From: Wouter Alink <<alink>>
Linking modules in a diamond construction, lets
Mserver crash (without error-message):
test.xq
/ \
/ \
v v
noot.xql mies.xql
\ /
\ /
v v
aap.xql
See the attached sources.
If the query-file is changed in that test.xq also
imports aap.xql, then an error-message is returned:
module import: module namespace does not match import
statement (`http://test.cwi.nl/mies' vs. `')
xquery_module_load: could not load module
## Comment 5618
Date: 2006-06-23 16:37:40 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
I can confirm this problem here on the stable branch.
However, the query is parsed correctly (including the
modules) by the standalone compiler (pf test.xq |
MapiClient) returns the expected result. So this must be
related to server-side XQuery.
Problem with Peter's URL caching magic?
## Comment 5619
Date: 2006-08-17 19:29:01 +0200
From: @peterboncz
Logged In: YES
user_id=591107
This was an issue in the compiler (Jens!) but it is fixed now.
A respective test has been added in BugTracker
## Comment 5620
Date: 2006-12-08 12:00:46 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
re-opened, as the tests seem to crash the server
since checkins on Tue Nov 7 2006 and/or Wed Nov 8 2006 (there was no pathfinder testing on Wed Nov 8 2006)
on all x86 & x86_64 Linux platforms
(not on ia64, Solaris x86, and Darwin, though):
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugTracker/modules_diamond.SF-1510975a.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugTracker/modules_diamond.SF-1510975b.err.00.html
## Comment 5621
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1510975 at http://sourceforge.net/support/tracker.php?aid=1510975
| XQuery: modules-diamond | https://api.github.com/repos/MonetDB/MonetDB/issues/987/comments | 0 | 2020-11-30T09:09:51Z | 2024-06-27T11:11:08Z | https://github.com/MonetDB/MonetDB/issues/987 | 753,296,701 | 987 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-21 01:57:18 +0200
From: monica_manzano <<monica_manzano>>
To: @njnes
Version: -- development
Last updated: 2006-06-21 09:30:12 +0200
## Comment 5613
Date: 2006-06-21 13:57:18 +0200
From: monica_manzano <<monica_manzano>>
The value of the sequence is not stored when the server
is restarted.
The behaviour is even stranger because after we first
restart the server, the bug does not appear. Likewise,
I think the number of errors given should be one more
in every try (for example, for the last insertion, we
inserted the forth tuple, so that should have needed
three errors but there are only two)
monetdb-> create table test (id serial, val int);
Operation successful
monetdb-> insert into test (val) values (1);
1 affected row
monetdb-> \q
RESTART SERVER
monetdb-> insert into test (val) values (1);
1 affected row
monetdb-> \q
RESTART SERVER
monetdb-> insert into test (val) values (1);
Error: ERROR: INSERT INTO: PRIMARY KEY constraint
'test.test_id_pkey' violated
monetdb-> insert into test (val) values (1);
1 affected row
monetdb-> \q
RESTART SERVER
monetdb-> insert into test (val) values (1);
Error: ERROR: INSERT INTO: PRIMARY KEY constraint
'test.test_id_pkey' violated
monetdb-> insert into test (val) values (1);
Error: ERROR: INSERT INTO: PRIMARY KEY constraint
'test.test_id_pkey' violated
monetdb-> insert into test (val) values (1);
1 affected row
## Comment 5614
Date: 2006-06-21 14:25:24 +0200
From: @drstmane
Logged In: YES
user_id=572415
I suppose this is a SQL bug that occurs in the SQL_2-12
release branch, i.e., with SQL version 2.12.0[_rc1]?
Please correct me (and my above changes) if I'm wrong!
## Comment 5615
Date: 2006-06-21 21:30:12 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed, after restart update bats get flushed now. Also the
sequence code got a bit cleanup, fixing the use fo the
cached value after restarts.
Added tests to BugTracker directory
sequence_not_stored_{1,2,3}
## Comment 5616
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1509894 at http://sourceforge.net/support/tracker.php?aid=1509894
| SQL: Sequence value is not stored when stopping the server | https://api.github.com/repos/MonetDB/MonetDB/issues/986/comments | 0 | 2020-11-30T09:09:48Z | 2024-06-27T11:11:07Z | https://github.com/MonetDB/MonetDB/issues/986 | 753,296,653 | 986 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-21 12:55:36 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2006-06-21 09:31:33 +0200
## Comment 5610
Date: 2006-06-21 12:55:36 +0200
From: @grobian
monetdb-> create table test (id serial, val int);
Operation successful
monetdb-> insert into test (val) values (1),(1),(1);
3 affected rows
monetdb-> select * from test;
+----+-----+
| id | val |
+====+=====+
| 1 | 1 |
| 1 | 1 |
| 1 | 1 |
+----+-----+
3 rows
That the sequence counter is not incremented is
acceptable, as we talk about a non-standard shortcut
here, but the constraint breakage will cause trouble
for sure:
monetdb-> create table test2 (t int unique);
Operation successful
monetdb-> insert into test2 values (1),(1),(1);
3 affected rows
monetdb-> select * from test2;
+---+
| t |
+===+
| 1 |
| 1 |
| 1 |
+---+
3 rows
monetdb-> \d test2
CREATE TABLE "sys"."test2" (
"t" int,
CONSTRAINT "test2_t_unique" UNIQUE ("t")
);
## Comment 5611
Date: 2006-06-21 21:31:33 +0200
From: @njnes
Logged In: YES
user_id=43556
multi insert key check only check if the values were
allready inserted. Now also the to be inserted set is check
for uniqueness.
added test to BugTracker directory
multivalue_insert.SF-1509864.sql
## Comment 5612
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1509864 at http://sourceforge.net/support/tracker.php?aid=1509864
| SQL: inserting multiple values at once can break constraints | https://api.github.com/repos/MonetDB/MonetDB/issues/985/comments | 0 | 2020-11-30T09:09:45Z | 2024-06-27T11:11:06Z | https://github.com/MonetDB/MonetDB/issues/985 | 753,296,624 | 985 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-21 10:58:00 +0200
From: Jens Teubner <<teubner>>
To: Jens Teubner <<teubner>>
Version: 11.1.1 (Mar2011) [obsolete]
Last updated: 2011-04-28 16:38:56 +0200
## Comment 5602
Date: 2006-06-21 10:58:00 +0200
From: Jens Teubner <<teubner>>
(This is relevant for the algebra back-end only. In
milprint_summer, xs:untypedAtomic == xs:string, which
circumvents the problem.)
The type xs:untypedAtomic is promotable to any atomic
type. Hence, it may be left as a statically possible
type for any (built-in) function with atomic arguments.
An implicit typeswitch (introduced by fs.brg) will
ensure that *dynamically* all items will have a
sensible type (not xs:untypedAtomic). From static
analysis, however, the compiler will see a possible
type of xs:untypedAtomic (i.e., a BAT for this type
when creating MIL code).
Examples are:
fn:string-join ((<a/>, "foo"), "bar)
(fn:string-join() is not yet implemented in the algebra
back-end, though)
declare function foo ($a as xs:string, $b as xs:
string)
{
fn:concat ($a, $b)
};
for $a in (<a/>, "foo") return foo ($a, "bar")
(without the user-defined function, the implicit
introduction of an fn:string() as required by the specs
call would hide our actual problem)
Currently, some built-ins (e.g., fn:concat()) complain
in that situation (e.g., there is an assertion testing
for aat_str in the implementation of fn:concat()). It
seems like we can simply drop the BAT for xs:
untypedAtomic (it will contain nils only due to the
typeswitch) in such cases. We have to be aware that
the BAT *may* be available when generating code.
## Comment 5603
Date: 2006-11-05 16:02:45 +0100
From: @drstmane
Logged In: YES
user_id=572415
added tests in
pathfinder/tests/BugTracker/Tests/xs_untypedAtomic.SF-1509806.{mps,alg}.*
milprint_summer version (mps) fails with
!ERROR: err:FORG0001: could not cast value to untypedAtomic.
algebra version (alg) fails with
pf:
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/pathfinder/compiler/algebra/logical.c:2690:
PFla_fn_concat: Assertion `n->schema.items[ix1].type ==
0x0004' failed.
## Comment 5604
Date: 2006-12-18 12:39:39 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Since also the mps version fails I consider the a "release bug"; cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugTracker/xs_untypedAtomic.SF-1509806.mps.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugTracker/xs_untypedAtomic.SF-1509806.alg.err.00.html
## Comment 5605
Date: 2007-02-19 16:27:38 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Jens, can you check the test output of the mps version and approve it if it is correct?
You can then assign the bug to JR to fix the algebra version.
## Comment 5606
Date: 2008-01-22 14:46:15 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
This is still an issue --- at least the correct output has not yet been provided / checked:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/xs_untypedAtomic.SF-1509806.mps.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/xs_untypedAtomic.SF-1509806.alg.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/xs_untypedAtomic.SF-1509806.alg.err.00.html
## Comment 5607
Date: 2009-02-16 00:38:00 +0100
From: @drstmane
updated TestWeb URLs
ALG:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugTracker/xs_untypedAtomic.SF-1509806.mps.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugTracker/xs_untypedAtomic.SF-1509806.mps.err.00.html
MPS:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_BugTracker/xs_untypedAtomic.SF-1509806.mps.out.00.html
## Comment 5608
Date: 2009-11-14 23:29:40 +0100
From: @drstmane
===================================================================
2009/11/14 - stmane: All,1.146.2.4
Disabled test that is bound to fail.
Please re-enable once bug is fixed.
cf.
ID: 1509806 "PF (Algebra): xs:untypedAtomic may occur for any atomic type"
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1509806&group_id=56967
===================================================================
## Comment 5609
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1509806 at http://sourceforge.net/support/tracker.php?aid=1509806
## Comment 15693
Date: 2011-03-28 17:37:05 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
## Comment 15762
Date: 2011-04-28 16:38:56 +0200
From: @sjoerdmullender
Development on MonetDB4 and MonetDB/XQuery has ceased. It is unlikely that this bug will be fixed.
The last release of MonetDB/XQuery and MonetDB4 is Mar2011.
| PF (Algebra): xs:untypedAtomic may occur for any atomic type | https://api.github.com/repos/MonetDB/MonetDB/issues/984/comments | 0 | 2020-11-30T09:09:41Z | 2024-06-28T13:32:55Z | https://github.com/MonetDB/MonetDB/issues/984 | 753,296,566 | 984 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-21 08:42:44 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2006-06-22 06:47:02 +0200
## Comment 5598
Date: 2006-06-21 08:42:44 +0200
From: @drstmane
Since Monday June 19, i.e., after the changes made on
Sunday June 18 --- mainly icc compilation fixes and the
addition of a "force" bit to the delete operations in
GDK --- the "aggr", "aggrX3", "decimal" &
"decimal_debug" tests in src/modules/plain/Tests fail
on SuSE when compiled with gcc-3.3.5 (apparently not
when compiled with icc-9.1).
See
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU.32.32.d-SuSE9.3/src_modules_plain/aggr.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU.64.64.d-SuSE9.3/src_modules_plain/aggr.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU.32.32.d-SuSE9ES/src_modules_plain/aggr.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU.32.32.d-SuSE9.3/src_modules_plain/aggrX3.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU.64.64.d-SuSE9.3/src_modules_plain/aggrX3.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU.32.32.d-SuSE9ES/src_modules_plain/aggrX3.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU.32.32.d-SuSE9.3/src_modules_plain/decimal.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU.64.64.d-SuSE9.3/src_modules_plain/decimal.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU.32.32.d-SuSE9ES/src_modules_plain/decimal.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU.32.32.d-SuSE9.3/src_modules_plain/decimal_debug.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU.64.64.d-SuSE9.3/src_modules_plain/decimal_debug.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU.32.32.d-SuSE9ES/src_modules_plain/decimal_debug.out.00.html
## Comment 5599
Date: 2006-06-22 06:47:02 +0200
From: @drstmane
Logged In: YES
user_id=572415
Niels fixed the compilation also in case assertions are enabled.
## Comment 5600
Date: 2006-06-22 06:49:15 +0200
From: @drstmane
Logged In: YES
user_id=572415
Sorry, wrong comment (or wrong bug report).
Correct:
Niels fixed the bit-field issues to work with both gcc 3.*
and gcc 4.* .
## Comment 5601
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1509739 at http://sourceforge.net/support/tracker.php?aid=1509739
| MonetDB tests fail on SuSE after Sunday June 18 | https://api.github.com/repos/MonetDB/MonetDB/issues/983/comments | 0 | 2020-11-30T09:09:37Z | 2024-06-27T11:11:04Z | https://github.com/MonetDB/MonetDB/issues/983 | 753,296,524 | 983 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-20 06:07:36 +0200
From: @drstmane
To: Wouter Alink <<alink>>
Version: -- development
Last updated: 2006-06-22 06:45:55 +0200
## Comment 5590
Date: 2006-06-20 18:07:36 +0200
From: @drstmane
The following tests in tests/StandOff fail as follows:
basic/lltest:
!ERROR: ll_select_narrow_join_sort_lng: iter-list is of
type VOID instead of OID.
!ERROR: CMDll_select_narrow_join_sort_lng: operation
failed.
video/scenes:
!ERROR: interpret: no matching MIL operator to
'll_standoff_select_wide(BAT[void,bit], BAT[void,bit],
BAT[void,bit], BAT[void,oid], BAT[oid,oid], BAT[oid,oid])'.
!MAYBE YOU MEAN:
! ll_standoff_select_wide(BAT[oid,oid], BAT[oid,any],
BAT[oid,any], BAT[void,oid], BAT[oid,oid],
BAT[oid,oid]) : BAT[oid,oid]
video/songs:
!ERROR: interpret: no matching MIL operator to
'll_standoff_select_wide(BAT[void,bit], BAT[void,bit],
BAT[void,bit], BAT[void,oid], BAT[oid,oid], BAT[oid,oid])'.
!MAYBE YOU MEAN:
! ll_standoff_select_wide(BAT[oid,oid], BAT[oid,any],
BAT[oid,any], BAT[void,oid], BAT[oid,oid],
BAT[oid,oid]) : BAT[oid,oid]
video/artists:
!ERROR: interpret: no matching MIL operator to
'll_standoff_select_narrow(BAT[void,bit],
BAT[void,bit], BAT[void,bit], BAT[void,oid],
BAT[oid,oid], BAT[oid,oid])'.
!MAYBE YOU MEAN:
! ll_standoff_select_narrow(BAT[oid,oid], BAT[oid,any],
BAT[oid,any], BAT[void,oid], BAT[oid,oid],
BAT[oid,oid]) : BAT[oid,oid]
## Comment 5591
Date: 2006-06-21 09:07:04 +0200
From: @drstmane
Logged In: YES
user_id=572415
With Peter's code fixes of last night, and my test fixes of
this morning (not yet reflected in the testweb), the
situation is as follows:
basic/test2:
!ERROR: interpret: no matching MIL operator to
'insert(BAT[oid,oid], BAT[oid,void])'.
!MAYBE YOU MEAN:
! insert(BAT[any::1,BAT], any::1, any) : BAT[any::1,BAT]
! insert(BAT[any::1,any::2], BAT[any::1,any::2]) :
BAT[any::1,any::2]
! insert(BAT[any::1,any::2], any::1, any::2) :
BAT[any::1,any::2]
basic/lltest:
!ERROR: ll_select_narrow_join_sort_lng: iter-list is of type
VOID instead of OID.
!ERROR: CMDll_select_narrow_join_sort_lng: operation failed.
video/scenes:
!ERROR: ll_select_wide_join_sort_lng: iter-list is of type
VOID instead of OID.
!ERROR: CMDll_select_wide_join_sort_lng: operation failed.
video/artists:
!ERROR: ll_select_narrow_join_sort_lng: iter-list is of type
VOID instead of OID.
!ERROR: CMDll_select_narrow_join_sort_lng: operation failed.
video/songs:
seems to work, now.
I approved the output, and
asked Wouter to verify/confirm it.
## Comment 5592
Date: 2006-06-21 10:40:40 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
The respective line for the failing insert-statement reads:
ws.fetch(ATTR_OWN).fetch(WS).insert(attr_own);
The last line of a create attributes root entries.
Appearantly when the attr-own-list is dense, it is
accidentally optimized to void?? Changing the line to:
ws.fetch(ATTR_OWN).fetch(WS).insert(attr_own.[oid]());
solves the problem and returns the correct output.
I haven't seen this bug before, and I am not sure if it is
in the StandOff code.
## Comment 5593
Date: 2006-06-21 11:01:57 +0200
From: @drstmane
Logged In: YES
user_id=572415
1)
Is the tail of attr_own indeed dense, i.e, with
tseqbase!=oid_nil?
If yes, this is a bug in the insert statment, as "void" with
segbase!=oid_nil (aka. "VID") should be treated as OID.
If no, this seems like a bug in the Pathfinder and/or
StandOff code that generates attr_own.
2)
Or is the respective attr_own empty, and/but the tseqbase
not set as the creator of the empty BAT considered this
unnecessary?
In that case, the tseqbase should be set to some
oid!=oid_nil when creating attr_own.
(We could also make insert ignore void/oid mismatches in
case the to-be-inserted BAT is empty... In that case, insert
is a NOP anyway...)
## Comment 5594
Date: 2006-06-21 15:30:37 +0200
From: @drstmane
Logged In: YES
user_id=572415
The basic/test2 problem is "cured" (rather than fixed...) in
CVS (XQuery_0-12 release branch; propagation to development
trunk will follow tonight):
When attr_own is empty, and the tail type is physically 'void',
it 'sometimes' happens that the tail's seqbase is not set
(i.e., 'nil'),
which makes the tail logically 'NIL' iso. 'VID' or 'OID',
and hence causes the insert to fail due to tail-type mismatch.
Since I haven't found the place where the empty attr_own
'looses' its tail seqbase,
and since neither the tail-seqbase nor the insert has any
impact if attr_own is empty,
we simply avoid the problem by skipping the 'NOP'-insert
completely in that case.
## Comment 5595
Date: 2006-06-21 15:49:34 +0200
From: @drstmane
Logged In: YES
user_id=572415
Attempt to fix the basic/lltest, video/scenes &
video/artists parts of
http://sourceforge.net/support/tracker.php?aid=1509413 "PF: various StandOff tests fail":
In runtime/pf_standoff.mx, @= ll_standoff_join_impl,
CMDll_@1_@2_join_sort_@3():
Instead of only checking whether the head of "source_start"
is TYPE_void,
we now also check whether its seqbase is oid_nil or not.
The error is triggered only for
source_start->htype == TYPE_void && source_start->hseqbase
== oid_nil,
i.e., in case the head is void-NIL,
hoping that the remaining code can cope with both
materialized OIDs
(source_start->htype == TYPE_oid) and non-materialized dense
"virtual" [O]IDs
(aka. "VID"; i.e., source_start->htype == TYPE_void &&
source_start->hseqbase != oid_nil).
This avoids the errors
!ERROR: ll_select_narrow_join_sort_lng: iter-list is of type
VOID instead of OID.
!ERROR: CMDll_select_narrow_join_sort_lng: operation failed.
and results in *some* output.
For test basic/lltest, the new output differen from the one
that Wouter provided.
For tests video/scenes & video/artists, now correct/expected
output has been
provided, yet.
Wouter, Peter,
could you please check/verify/finish/undo my changes, the
new output and the
currently checked-in output of all StandOff tests
(XQuery_0-12 release branch)?
## Comment 5596
Date: 2006-06-22 06:45:55 +0200
From: @drstmane
Logged In: YES
user_id=572415
Wouter approved the new output as correct;
hench, I consider this one fixed and close it.
## Comment 5597
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1509413 at http://sourceforge.net/support/tracker.php?aid=1509413
| PF: various StandOff tests fail | https://api.github.com/repos/MonetDB/MonetDB/issues/982/comments | 0 | 2020-11-30T09:09:33Z | 2024-06-27T11:11:03Z | https://github.com/MonetDB/MonetDB/issues/982 | 753,296,481 | 982 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-20 02:40:48 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-06-20 06:01:17 +0200
## Comment 5586
Date: 2006-06-20 14:40:48 +0200
From: @drstmane
As opposed to all other options,
pf's --enable-standoff does not include the required
'module(pf_standoff);' call in the generated MIL code:
$ pf -b tests/StandOff/basic/Tests/test1.xq | Mserver
--set monet_prompt=''
Monet Database Server V4.12.0_rc1
Copyright (c) 1993-2006, CWI. All rights reserved.
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit
OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
!ERROR: interpret: no matching MIL operator to
'loop_lifted_select_narrow_step_with_kind_test(BAT[oid,oid],
BAT[oid,oid], BAT[void,oid], BAT[oid,BAT], int, chr)'.
$ pf -b tests/StandOff/basic/Tests/test1.xq | Mserver
--set monet_prompt='' --dbinit='module(pf_standoff);'
Monet Database Server V4.12.0_rc1
Copyright (c) 1993-2006, CWI. All rights reserved.
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit
OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>
<a end="11" start="10"/>
</XQueryResult>
## Comment 5587
Date: 2006-06-20 16:27:57 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
I fixed the bug statement, but did not fix the bug:
In CVS XQuery_0-12 i committed a fix that generates
"module(pf_standoff);" when standoff is enabled. But the
tests still fail when ran with Mtest. (they still complain
about functions in pf_standoff that are not available)
might have something to do with the dirty:
environment().insert("standoff","enabled");
statement in the prologue? But I don't know how to pass this
option in another way.
Assigning bug to Stefan, as he probably has some magic to
make Mtest 'see' pf_standoff.
## Comment 5588
Date: 2006-06-20 18:01:17 +0200
From: @drstmane
Logged In: YES
user_id=572415
The tests in tests/StandOff// now work as far as Mtest is
concerned.
I'll report StandOff related bugs in my next bugreport.
## Comment 5589
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1509302 at http://sourceforge.net/support/tracker.php?aid=1509302
| PF: pf --enable-standoff does not issue module(pf_standoff); | https://api.github.com/repos/MonetDB/MonetDB/issues/981/comments | 0 | 2020-11-30T09:09:30Z | 2024-06-27T11:11:02Z | https://github.com/MonetDB/MonetDB/issues/981 | 753,296,450 | 981 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-20 02:14:38 +0200
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-06-20 09:20:44 +0200
## Comment 5583
Date: 2006-06-20 14:14:38 +0200
From: @drstmane
With debugmask 8 (or 10, the default with Mtest),
test
tests/BugDay_2005-12-19_0.9.3/Tests/parent_step_bug.SF-1339844.xq
crashes in
res_scj := loop_lifted_parent_step(iter, item,
constant2bat(kind.get_fragment()), ws, 0);
(Mserver exits with retunr code 1).
## Comment 5584
Date: 2006-06-20 21:20:44 +0200
From: @drstmane
Logged In: YES
user_id=572415
This bugs ha either been fixed, or it cured itself;
at least it seems to be working fine, again.
## Comment 5585
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1509286 at http://sourceforge.net/support/tracker.php?aid=1509286
| PF: parent step test fails with debugmask 8 | https://api.github.com/repos/MonetDB/MonetDB/issues/980/comments | 0 | 2020-11-30T09:09:27Z | 2024-06-28T13:32:54Z | https://github.com/MonetDB/MonetDB/issues/980 | 753,296,423 | 980 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-20 11:12:10 +0200
From: @drstmane
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2006-06-20 11:35:54 +0200
## Comment 5580
Date: 2006-06-20 11:12:10 +0200
From: @drstmane
After the changes of yesterday, Monday June 19 2006,
tests tests/XPath/Tests/q05.xq &
tests/XPathMark/Tests/Q5.xq fail with
========
WARNING: BATpropcheck: BAT tmp_256 was incorrectly
marked keyed!
WARNING: BATpropcheck: BAT tmp_256 was incorrectly
marked keyed!
========
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XPath/q05.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XPathMark/Q5.err.00.html
## Comment 5581
Date: 2006-06-20 11:35:40 +0200
From: @peterboncz
Logged In: YES
user_id=591107
sorry, fixed.
## Comment 5582
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1509161 at http://sourceforge.net/support/tracker.php?aid=1509161
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| PF: tests fail with property error | https://api.github.com/repos/MonetDB/MonetDB/issues/979/comments | 0 | 2020-11-30T09:09:24Z | 2024-06-27T11:11:00Z | https://github.com/MonetDB/MonetDB/issues/979 | 753,296,382 | 979 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-20 11:00:48 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-06-20 12:42:24 +0200
## Comment 5577
Date: 2006-06-20 11:00:48 +0200
From: Jan Rittinger <<jan.rittinger>>
see:
pathfinder/tests/XQuery/Tests/transient_upward_steps.xq
## Comment 5578
Date: 2006-06-20 12:42:22 +0200
From: @peterboncz
Logged In: YES
user_id=591107
a thinking error in parent; solved using an extra stack
per-iter..
## Comment 5579
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1509156 at http://sourceforge.net/support/tracker.php?aid=1509156
| PF: single iteration parent step fails with debug-mask 10 | https://api.github.com/repos/MonetDB/MonetDB/issues/978/comments | 0 | 2020-11-30T09:09:21Z | 2024-06-27T11:10:59Z | https://github.com/MonetDB/MonetDB/issues/978 | 753,296,353 | 978 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-20 10:10:49 +0200
From: Jan Rittinger <<jan.rittinger>>
To: @sjoerdmullender
Version: -- development
Last updated: 2006-06-20 02:27:17 +0200
## Comment 5574
Date: 2006-06-20 10:10:49 +0200
From: Jan Rittinger <<jan.rittinger>>
The script generated by the query in
pathfinder/tests/XQuery/Tests/ID.1490847.xq
crashes the Mserver.
The code responsible for the crash was last modified by
Sjoerd 07-Feb-06 -- so it's his bug :).
## Comment 5575
Date: 2006-06-20 14:27:15 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed by chaning BUNtloc into BUNtail.
But you obviously hadn't looked at the log entry: this line
was last modified by me because I did the merge of the
update branch, not because I wrote the line. ;-)
## Comment 5576
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1509127 at http://sourceforge.net/support/tracker.php?aid=1509127
| PF: correct_sizes() crashes Mserver | https://api.github.com/repos/MonetDB/MonetDB/issues/977/comments | 0 | 2020-11-30T09:09:18Z | 2024-06-27T11:10:58Z | https://github.com/MonetDB/MonetDB/issues/977 | 753,296,321 | 977 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-20 09:32:42 +0200
From: Benjamin Piwowarski <<bpiwowar>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2006-06-23 10:31:08 +0200
## Comment 5564
Date: 2006-06-20 09:32:42 +0200
From: Benjamin Piwowarski <<bpiwowar>>
The following query (x-mark no 15) makes the server crash:
let $auction := doc("auction.xml") return
for $a in
$auction/site/closed_auctions/closed_auction/annotation/description/parlist/
listitem/
parlist/
listitem/
text/
emph/
keyword/text()
return <text>{$a}</text>
It seems that the text() bit at the end of the path of
the for loop is the origin of the problem, because
moving it into the return clause resolves the problem:
let $auction := doc("auction.xml") return
for $a in
$auction/site/closed_auctions/closed_auction/annotation/description/parlist/
listitem/
parlist/
listitem/
text/
emph/
keyword
return <text>{$a/text()}</text>
Some more info:
- system is debian unstable (kernel 2.6.16-2-686)
- pathfinder and monetdb-server were compiled without
any specific options other than a modified prefix
- the server was started with:
Mserver --dbinit="module(pathfinder); pfstart();
mapi_start();"
- Several auction.xml documents were used in order to
test if it was related to a specific document. This was
not the case
## Comment 5565
Date: 2006-06-20 10:13:21 +0200
From: @drstmane
Logged In: YES
user_id=572415
Hi,
according to our TestWeb
(http://monetdb.cwi.nl/Development/TestWeb/) all XMark
queries do work find on a ~500kB XMark document. In fact,
only 2 (tests/XPath/Tests/q05.xq &
tests/XPathMark/Tests/Q5.xq) of the ~1200(!) tests fail with
the last night's version of the XQuery_0-12 release branch
(see
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/index_short.html
and
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/index.html
for details).
(The differences with runtime/Tests/procs.milS,
runtime/Tests/merged_union.milS &
tests/BugDay_2005-12-19_0.9.3/Tests/parent_step_bug.SF-1339844.xq
have just been approved as correct.)
Hence, could you please cvs update, recompile and check
whether the problem still occurs for you?
## Comment 5566
Date: 2006-06-20 10:41:32 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Thanks!
One missing info: did you compile the HEAD branch or the Stable?
You get the stable branch by checking out the monet project
with -r MonetDB_4-10, and the pathfinder project with -r
XQuery_0-10
Actually, end of this week we're releasing a new version,
i.e. a new stable branch that appears to be working well and
is available under the tags MonetDB_4-12 and XQuery_0-12
I tried to reproduce the problem in both HEAD and
XQuery_0-12 branches, but failed to do so. Maybe it is in
XQuery_0_10.
As we are in the middle of a serious develoment operation
that adds updates, the HEAD is only usable for internal
development purposes. Normal users *should* use the stable
branch.
I also compiled your query stand-alone (pf q15.xq >
q15.mil), profiled it (./profile.sh q15.mil > p15.mil).
Maybe you can run this profiled MIL script (Mserver p15.mil)
and report what happens.
Peter
## Comment 5567
Date: 2006-06-20 10:56:49 +0200
From: Benjamin Piwowarski <<bpiwowar>>
Logged In: YES
user_id=1173479
I compiled the stable source packages I downloaded from
sourceforge (4.10.2 and 0.10.2).
I tried to run the mil query and I had no problem. I will
maybe try latter to compile from CVS to check if the bug is
resolved in CVS.
Benjamin
## Comment 5568
Date: 2006-06-20 11:01:46 +0200
From: @drstmane
Logged In: YES
user_id=572415
bug actually occured with 0.10.2, not with 0.12.0
## Comment 5569
Date: 2006-06-20 11:03:16 +0200
From: @grobian
Logged In: YES
user_id=963970
if setting up CVS gives you problems; you can also grab one
of the nightly build sources from our website:
http://monetdb.cwi.nl/GetGoing/Download/index.html
See section under "Sources".
## Comment 5570
Date: 2006-06-20 11:22:02 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
The nightly tarballs are currently unavailable. Stefan fixed
the problem today, and new tarballs should be on the website
tomorrow.
## Comment 5571
Date: 2006-06-22 06:53:47 +0200
From: @drstmane
Logged In: YES
user_id=572415
Benjamin,
any news on this one, i.e., does it work for you with
MonetDB/XQuery 0.12.0 (cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/.DailyBuilds.MonetDB_4-12-0./)
?
## Comment 5572
Date: 2006-06-23 10:31:08 +0200
From: Benjamin Piwowarski <<bpiwowar>>
Logged In: YES
user_id=1173479
Cannot reproduce the bug with monet db 4.12.0 and pf 0.12.0,
so I think this is fixed.
## Comment 5573
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1509110 at http://sourceforge.net/support/tracker.php?aid=1509110
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.
| Segfault with X-Mark query 15 | https://api.github.com/repos/MonetDB/MonetDB/issues/976/comments | 0 | 2020-11-30T09:09:15Z | 2024-06-27T11:10:57Z | https://github.com/MonetDB/MonetDB/issues/976 | 753,296,278 | 976 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-20 12:37:48 +0200
From: Gustavo Hispagnol <<gmhispagnol>>
To: @njnes
Version: -- development
Last updated: 2006-06-22 10:54:38 +0200
## Comment 5554
Date: 2006-06-20 00:37:48 +0200
From: Gustavo Hispagnol <<gmhispagnol>>
Hello,
I hope this is the right place to post this message,
but here it goes: I´m trying to aggregate 6.300.000
rows using a simple SQL:
select product,sum(qty) from sales_fact group by
productid;
the sales_facts is defined as:
create table sales_fact as
(key1 int,
key2 char(1),
date date,
product int,
color int,
size char(5),
style int,
qty double precision,
total double precision,
total_ex double precision)
This query results in about 6.000 rows in about 15
secs. Well, this is not bad, but during all
consecutive runs of this same query, the CPU keeps
bouncing from 0% to 25% usage. The image data has
about 300MB (read from the files in dbfarm) and the
machine is a AMD64 Dual Core with 1GB of memory
running Windows 2003 and MonetDB 4.10.2. As all the
data fits in memory and MonetDB is a main memory
database, why can´t MonetDB use 100% CPU? Am I missing
something? Is there some parameter I can set to make
it better (it´s running on defaults)? I was expecting
a more effective CPU utilization here.
Thanks for the fantastic job and help,
Gustavo.
## Comment 5555
Date: 2006-06-20 08:33:32 +0200
From: @njnes
Logged In: YES
user_id=43556
To help you we need a bit more input. This can be solve in two
ways 1) you suplly the data, so we could run the experiments.
Or you do some measurements and mail/attache the result.
Please Try the following.
SET DEBUG=3072;
Then your query. (keep hitting enter until no more output
is returned) Send/attache the result.
## Comment 5556
Date: 2006-06-20 17:38:53 +0200
From: Gustavo Hispagnol <<gmhispagnol>>
Logged In: YES
user_id=818683
How can I capture the debug output?
## Comment 5557
Date: 2006-06-20 18:20:20 +0200
From: @njnes
Logged In: YES
user_id=43556
run MapiClient -lsql with the set debug statement. The output
will only return if you give enough enters.
## Comment 5558
Date: 2006-06-20 23:00:33 +0200
From: Gustavo Hispagnol <<gmhispagnol>>
Logged In: YES
user_id=818683
The log:
[ 1 ]
< var s13 := mvc_bind(myc, `sys`, `produtos_eventos2`,
`produto`, 0); produtos_eventos2 >
[ 0 ]
| 6082208 * { void , int } |
-----------------
h t name
void int type
-----------------
[ 0@0, 0 ]
[ 1@0, 0 ]
[ 2@0, 0 ]
[ 3@0, 280 ]
[ 4@0, 360 ]
[ 5@0, 319 ]
[ 6@0, 170 ]
[ 7@0, 170 ]
[ 8@0, 305 ]
[ 9@0, 991 ]
[ "..." ]
---------------------------------
h t name
oid int type
---------------------------------
[ 51@0, 170 ]
[ 18518@0, 40135162 ]
[ 24852@0, 40134961 ]
[ 51352@0, 40133771 ]
[ 70521@0, 40134932 ]
[ 86245@0, 40135132 ]
[ 97723@0, 40135446 ]
[ 127081@0, 40135401 ]
[ 154043@0, 40133405 ]
[ 178507@0, 40134994 ]
[ "..." ]
---------------------------------
h t name
void int type
---------------------------------
[ 6082198@0, 40135774 ]
[ 6082199@0, 60198391 ]
[ 6082200@0, 60198391 ]
[ 6082201@0, 60198391 ]
[ 6082202@0, 40135024 ]
[ 6082203@0, 60197445 ]
[ 6082204@0, 40134992 ]
[ 6082205@0, 34180 ]
[ 6082206@0, 34208 ]
[ 6082207@0, 40135774 ]
< var s14 := mvc_bind(myc, `sys`, `produtos_eventos2`,
`produto`, 1); produtos_eventos2 >
[ 0 ]
| 0 * { void , int } |
-----------------
h t name
void int type
-----------------
< var s12 := sql_union(s13, s14); >
[ 0 ]
| 6082208 * { void , int } |
-----------------
h t name
void int type
-----------------
[ 0@0, 0 ]
[ 1@0, 0 ]
[ 2@0, 0 ]
[ 3@0, 280 ]
[ 4@0, 360 ]
[ 5@0, 319 ]
[ 6@0, 170 ]
[ 7@0, 170 ]
[ 8@0, 305 ]
[ 9@0, 991 ]
[ "..." ]
---------------------------------
h t name
oid int type
---------------------------------
[ 5715@0, 40135174 ]
[ 33860@0, 40134911 ]
[ 57141@0, 40133770 ]
[ 73968@0, 40135270 ]
[ 83929@0, 40135357 ]
[ 84420@0, 40135135 ]
[ 87415@0, 40135145 ]
[ 99357@0, 40135400 ]
[ 104184@0, 40134955 ]
[ 109620@0, 40134954 ]
[ "..." ]
---------------------------------
h t name
void int type
---------------------------------
[ 6082198@0, 40135774 ]
[ 6082199@0, 60198391 ]
[ 6082200@0, 60198391 ]
[ 6082201@0, 60198391 ]
[ 6082202@0, 40135024 ]
[ 6082203@0, 60197445 ]
[ 6082204@0, 40134992 ]
[ 6082205@0, 34180 ]
[ 6082206@0, 34208 ]
[ 6082207@0, 40135774 ]
< s13 := nil; >
< s14 := nil; >
< var s15 := mvc_bind(myc, `sys`, `produtos_eventos2`,
`produto`, 3); produtos_eventos2 >
[ 0 ]
| 0 * { oid , int } |
-----------------
h t name
oid int type
-----------------
< var s11 := sql_diff(s12, s15); >
[ 0 ]
| 6082208 * { void , int } |
-----------------
h t name
void int type
-----------------
[ 0@0, 0 ]
[ 1@0, 0 ]
[ 2@0, 0 ]
[ 3@0, 280 ]
[ 4@0, 360 ]
[ 5@0, 319 ]
[ 6@0, 170 ]
[ 7@0, 170 ]
[ 8@0, 305 ]
[ 9@0, 991 ]
[ "..." ]
---------------------------------
h t name
oid int type
---------------------------------
[ 32401@0, 40135303 ]
[ 47005@0, 40135321 ]
[ 50907@0, 40134955 ]
[ 51060@0, 40134926 ]
[ 51352@0, 40133771 ]
[ 63734@0, 40134913 ]
[ 81155@0, 40135145 ]
[ 99871@0, 40135399 ]
[ 119589@0, 40135446 ]
[ 139484@0, 40135169 ]
[ "..." ]
---------------------------------
h t name
void int type
---------------------------------
[ 6082198@0, 40135774 ]
[ 6082199@0, 60198391 ]
[ 6082200@0, 60198391 ]
[ 6082201@0, 60198391 ]
[ 6082202@0, 40135024 ]
[ 6082203@0, 60197445 ]
[ 6082204@0, 40134992 ]
[ 6082205@0, 34180 ]
[ 6082206@0, 34208 ]
[ 6082207@0, 40135774 ]
< s12 := nil; >
< var s10 := sql_union(s11, s15); >
[ 0 ]
| 6082208 * { void , int } |
-----------------
h t name
void int type
-----------------
[ 0@0, 0 ]
[ 1@0, 0 ]
[ 2@0, 0 ]
[ 3@0, 280 ]
[ 4@0, 360 ]
[ 5@0, 319 ]
[ 6@0, 170 ]
[ 7@0, 170 ]
[ 8@0, 305 ]
[ 9@0, 991 ]
[ "..." ]
---------------------------------
h t name
oid int type
---------------------------------
[ 5457@0, 40135299 ]
[ 27183@0, 40134934 ]
[ 41954@0, 40134611 ]
[ 53492@0, 40133940 ]
[ 55361@0, 40134949 ]
[ 75273@0, 40134969 ]
[ 100940@0, 40134961 ]
[ 127239@0, 40135566 ]
[ 144274@0, 40134974 ]
[ 154168@0, 40135562 ]
[ "..." ]
---------------------------------
h t name
void int type
---------------------------------
[ 6082198@0, 40135774 ]
[ 6082199@0, 60198391 ]
[ 6082200@0, 60198391 ]
[ 6082201@0, 60198391 ]
[ 6082202@0, 40135024 ]
[ 6082203@0, 60197445 ]
[ 6082204@0, 40134992 ]
[ 6082205@0, 34180 ]
[ 6082206@0, 34208 ]
[ 6082207@0, 40135774 ]
< s11 := nil; >
< s15 := nil; >
< var s17 := mvc_bind_dbat(myc, `sys`, `produtos_eventos2`,
0); >
[ 0 ]
| 0 * { void , oid } |
-----------------
h t name
void oid type
-----------------
< var s16 := s17.reverse(); >
[ 0 ]
| 0 * { oid , void } |
-----------------
t h name
oid void type
-----------------
< s17 := nil; >
< var s9 := sql_diff(s10, s16); >
[ 0 ]
| 6082208 * { void , int } |
-----------------
h t name
void int type
-----------------
[ 0@0, 0 ]
[ 1@0, 0 ]
[ 2@0, 0 ]
[ 3@0, 280 ]
[ 4@0, 360 ]
[ 5@0, 319 ]
[ 6@0, 170 ]
[ 7@0, 170 ]
[ 8@0, 305 ]
[ 9@0, 991 ]
[ "..." ]
---------------------------------
h t name
oid int type
---------------------------------
[ 28713@0, 40135406 ]
[ 52524@0, 40135146 ]
[ 83846@0, 40135162 ]
[ 114179@0, 40135399 ]
[ 131852@0, 40134859 ]
[ 136516@0, 40135562 ]
[ 151657@0, 40135227 ]
[ 159368@0, 40135427 ]
[ 187621@0, 40134723 ]
[ 194489@0, 40134739 ]
[ "..." ]
---------------------------------
h t name
void int type
---------------------------------
[ 6082198@0, 40135774 ]
[ 6082199@0, 60198391 ]
[ 6082200@0, 60198391 ]
[ 6082201@0, 60198391 ]
[ 6082202@0, 40135024 ]
[ 6082203@0, 60197445 ]
[ 6082204@0, 40134992 ]
[ 6082205@0, 34180 ]
[ 6082206@0, 34208 ]
[ 6082207@0, 40135774 ]
< s16 := nil; >
< var s18 := >
[ 0 ]
[ 0@0 ]
< var s8 := mark(s9, s18); >
[ 454000 ]
| 6082208 * { void , void } |
-----------------
h t name
void void type
-----------------
[ 0@0, 0@0 ]
[ 1@0, 1@0 ]
[ 2@0, 2@0 ]
[ 3@0, 3@0 ]
[ 4@0, 4@0 ]
[ 5@0, 5@0 ]
[ 6@0, 6@0 ]
[ 7@0, 7@0 ]
[ 8@0, 8@0 ]
[ 9@0, 9@0 ]
[ "..." ]
---------------------------------
h t name
oid oid type
---------------------------------
[ 25557@0, 25557@0 ]
[ 53201@0, 53201@0 ]
[ 85863@0, 85863@0 ]
[ 118620@0, 118620@0 ]
[ 138657@0, 138657@0 ]
[ 151516@0, 151516@0 ]
[ 160239@0, 160239@0 ]
[ 169980@0, 169980@0 ]
[ 197509@0, 197509@0 ]
[ 198287@0, 198287@0 ]
[ "..." ]
---------------------------------
h t name
void void type
---------------------------------
[ 6082198@0, 6082198@0 ]
[ 6082199@0, 6082199@0 ]
[ 6082200@0, 6082200@0 ]
[ 6082201@0, 6082201@0 ]
[ 6082202@0, 6082202@0 ]
[ 6082203@0, 6082203@0 ]
[ 6082204@0, 6082204@0 ]
[ 6082205@0, 6082205@0 ]
[ 6082206@0, 6082206@0 ]
[ 6082207@0, 6082207@0 ]
< s18 := nil; >
< var s7 := s8.reverse(); >
[ 0 ]
| 6082208 * { void , void } |
-----------------
h t name
void void type
-----------------
[ 0@0, 0@0 ]
[ 1@0, 1@0 ]
[ 2@0, 2@0 ]
[ 3@0, 3@0 ]
[ 4@0, 4@0 ]
[ 5@0, 5@0 ]
[ 6@0, 6@0 ]
[ 7@0, 7@0 ]
[ 8@0, 8@0 ]
[ 9@0, 9@0 ]
[ "..." ]
---------------------------------
h t name
oid oid type
---------------------------------
[ 12326@0, 12326@0 ]
[ 15361@0, 15361@0 ]
[ 37551@0, 37551@0 ]
[ 39393@0, 39393@0 ]
[ 39681@0, 39681@0 ]
[ 69787@0, 69787@0 ]
[ 78827@0, 78827@0 ]
[ 87769@0, 87769@0 ]
[ 107033@0, 107033@0 ]
[ 129681@0, 129681@0 ]
[ "..." ]
---------------------------------
h t name
void void type
---------------------------------
[ 6082198@0, 6082198@0 ]
[ 6082199@0, 6082199@0 ]
[ 6082200@0, 6082200@0 ]
[ 6082201@0, 6082201@0 ]
[ 6082202@0, 6082202@0 ]
[ 6082203@0, 6082203@0 ]
[ 6082204@0, 6082204@0 ]
[ 6082205@0, 6082205@0 ]
[ 6082206@0, 6082206@0 ]
[ 6082207@0, 6082207@0 ]
< var s6 := s7.join(s10); >
[ 1234000 ]
| 6082208 * { void , int } |
-----------------
h t name
void int type
-----------------
[ 0@0, 0 ]
[ 1@0, 0 ]
[ 2@0, 0 ]
[ 3@0, 280 ]
[ 4@0, 360 ]
[ 5@0, 319 ]
[ 6@0, 170 ]
[ 7@0, 170 ]
[ 8@0, 305 ]
[ 9@0, 991 ]
[ "..." ]
---------------------------------
h t name
oid int type
---------------------------------
[ 27456@0, 40134941 ]
[ 51261@0, 40134960 ]
[ 67151@0, 40134925 ]
[ 73880@0, 40134962 ]
[ 98250@0, 40135165 ]
[ 113600@0, 40134969 ]
[ 128606@0, 40134990 ]
[ 159707@0, 40135409 ]
[ 184100@0, 40134938 ]
[ 187648@0, 40134926 ]
[ "..." ]
---------------------------------
h t name
void int type
---------------------------------
[ 6082198@0, 40135774 ]
[ 6082199@0, 60198391 ]
[ 6082200@0, 60198391 ]
[ 6082201@0, 60198391 ]
[ 6082202@0, 40135024 ]
[ 6082203@0, 60197445 ]
[ 6082204@0, 40134992 ]
[ 6082205@0, 34180 ]
[ 6082206@0, 34208 ]
[ 6082207@0, 40135774 ]
< var s5g := s6.CTgroup(); var s5 := s5g.map(); >
[ 1296000 ]
[ Å\002\000\000Â\002\000\000 ]
[ 1296000 ]
[ Å\002\000\000Â\002\000\000 ]
| 6082208 * { void , oid } |
-----------------
h t name
void oid type
-----------------
[ 0@0, 0@0 ]
[ 1@0, 0@0 ]
[ 2@0, 0@0 ]
[ 3@0, 3@0 ]
[ 4@0, 4@0 ]
[ 5@0, 5@0 ]
[ 6@0, 6@0 ]
[ 7@0, 6@0 ]
[ 8@0, 8@0 ]
[ 9@0, 9@0 ]
[ "..." ]
---------------------------------
h t name
oid oid type
---------------------------------
[ 19639@0, 6545@0 ]
[ 32262@0, 32262@0 ]
[ 56346@0, 3186@0 ]
[ 76300@0, 3084@0 ]
[ 95056@0, 3216@0 ]
[ 106896@0, 3364@0 ]
[ 111862@0, 12673@0 ]
[ 119238@0, 3162@0 ]
[ 133169@0, 3083@0 ]
[ 159477@0, 3676@0 ]
[ "..." ]
---------------------------------
h t name
void oid type
---------------------------------
[ 6082198@0, 1015@0 ]
[ 6082199@0, 6082199@0 ]
[ 6082200@0, 6082199@0 ]
[ 6082201@0, 6082199@0 ]
[ 6082202@0, 3754@0 ]
[ 6082203@0, 4384555@0 ]
[ 6082204@0, 3179@0 ]
[ 6082205@0, 1824@0 ]
[ 6082206@0, 633@0 ]
[ 6082207@0, 1015@0 ]
< s6 := nil; >
< var s4 := s5g.extend().mirror(); >
[ 0 ]
| 6645 * { oid , oid } |
-----------------
h t name
oid oid type
-----------------
[ 0@0, 0@0 ]
[ 3@0, 3@0 ]
[ 4@0, 4@0 ]
[ 5@0, 5@0 ]
[ 6@0, 6@0 ]
[ 8@0, 8@0 ]
[ 9@0, 9@0 ]
[ 36@0, 36@0 ]
[ 37@0, 37@0 ]
[ 38@0, 38@0 ]
[ "..." ]
---------------------------------
h t name
oid oid type
---------------------------------
[ 7293@0, 7293@0 ]
[ 8025@0, 8025@0 ]
[ 477179@0, 477179@0 ]
[ 1158823@0, 1158823@0 ]
[ 2112167@0, 2112167@0 ]
[ 2986214@0, 2986214@0 ]
[ 3642515@0, 3642515@0 ]
[ 3652492@0, 3652492@0 ]
[ 4869519@0, 4869519@0 ]
[ 5541192@0, 5541192@0 ]
[ "..." ]
---------------------------------
h t name
oid oid type
---------------------------------
[ 6050057@0, 6050057@0 ]
[ 6050061@0, 6050061@0 ]
[ 6050121@0, 6050121@0 ]
[ 6050122@0, 6050122@0 ]
[ 6063348@0, 6063348@0 ]
[ 6064631@0, 6064631@0 ]
[ 6064633@0, 6064633@0 ]
[ 6064635@0, 6064635@0 ]
[ 6080986@0, 6080986@0 ]
[ 6082199@0, 6082199@0 ]
< var s19 := s7.join(s10); >
[ 1297000 ]
| 6082208 * { void , int } |
-----------------
h t name
void int type
-----------------
[ 0@0, 0 ]
[ 1@0, 0 ]
[ 2@0, 0 ]
[ 3@0, 280 ]
[ 4@0, 360 ]
[ 5@0, 319 ]
[ 6@0, 170 ]
[ 7@0, 170 ]
[ 8@0, 305 ]
[ 9@0, 991 ]
[ "..." ]
---------------------------------
h t name
oid int type
---------------------------------
[ 4843@0, 40135208 ]
[ 35958@0, 40134972 ]
[ 40597@0, 40134993 ]
[ 70255@0, 40134927 ]
[ 92959@0, 40135506 ]
[ 102889@0, 40135158 ]
[ 116866@0, 40135446 ]
[ 119172@0, 40135140 ]
[ 150845@0, 40135327 ]
[ 173231@0, 40134931 ]
[ "..." ]
---------------------------------
h t name
void int type
---------------------------------
[ 6082198@0, 40135774 ]
[ 6082199@0, 60198391 ]
[ 6082200@0, 60198391 ]
[ 6082201@0, 60198391 ]
[ 6082202@0, 40135024 ]
[ 6082203@0, 60197445 ]
[ 6082204@0, 40134992 ]
[ 6082205@0, 34180 ]
[ 6082206@0, 34208 ]
[ 6082207@0, 40135774 ]
< s10 := nil; >
< var s3 := s4.join(s19); >
[ 0 ]
| 6645 * { oid , int } |
-----------------
h t name
oid int type
-----------------
[ 0@0, 0 ]
[ 3@0, 280 ]
[ 4@0, 360 ]
[ 5@0, 319 ]
[ 6@0, 170 ]
[ 8@0, 305 ]
[ 9@0, 991 ]
[ 36@0, 72 ]
[ 37@0, 225 ]
[ 38@0, 40 ]
[ "..." ]
---------------------------------
h t name
oid int type
---------------------------------
[ 1028@0, 50164132 ]
[ 1211@0, 50164083 ]
[ 3123@0, 40134083 ]
[ 5880@0, 40134445 ]
[ 33380@0, 40135485 ]
[ 1920924@0, 50163640 ]
[ 4035040@0, 60197065 ]
[ 4705309@0, 60198101 ]
[ 5088503@0, 60198011 ]
[ 5883759@0, 60198400 ]
[ "..." ]
---------------------------------
h t name
oid int type
---------------------------------
[ 6050057@0, 60198573 ]
[ 6050061@0, 60198543 ]
[ 6050121@0, 60199120 ]
[ 6050122@0, 60199121 ]
[ 6063348@0, 70229005 ]
[ 6064631@0, 40132623 ]
[ 6064633@0, 40133060 ]
[ 6064635@0, 40133262 ]
[ 6080986@0, 60198317 ]
[ 6082199@0, 60198391 ]
< s19 := nil; >
< var s26 := mvc_bind(myc, `sys`, `produtos_eventos2`,
`quantidade`, 0); produtos_eventos2 >
[ 0 ]
| 6082208 * { void , dbl } |
---------------------------------
h t name
void dbl type
---------------------------------
[ 0@0, 10 ]
[ 1@0, 10 ]
[ 2@0, 10 ]
[ 3@0, 281 ]
[ 4@0, 1328.8 ]
[ 5@0, 313.10000000000002 ]
[ 6@0, 12.109999999999999 ]
[ 7@0, 12.25 ]
[ 8@0, 100 ]
[ 9@0, 100 ]
[ "..." ]
-------------------------
h t name
oid dbl type
-------------------------
[ 23996@0, 1 ]
[ 37286@0, 6 ]
[ 46447@0, 9 ]
[ 65083@0, 1 ]
[ 87438@0, 1 ]
[ 112205@0, 1 ]
[ 135860@0, 1 ]
[ 151434@0, 2 ]
[ 155465@0, 1 ]
[ 167517@0, 2 ]
[ "..." ]
-------------------------
h t name
void dbl type
-------------------------
[ 6082198@0, 1 ]
[ 6082199@0, 105 ]
[ 6082200@0, 210 ]
[ 6082201@0, 105 ]
[ 6082202@0, 1 ]
[ 6082203@0, 1 ]
[ 6082204@0, 1 ]
[ 6082205@0, 1 ]
[ 6082206@0, 1 ]
[ 6082207@0, 1 ]
< var s27 := mvc_bind(myc, `sys`, `produtos_eventos2`,
`quantidade`, 1); produtos_eventos2 >
[ 0 ]
| 0 * { void , dbl } |
-----------------
h t name
void dbl type
-----------------
< var s25 := sql_union(s26, s27); >
[ 0 ]
| 6082208 * { void , dbl } |
---------------------------------
h t name
void dbl type
---------------------------------
[ 0@0, 10 ]
[ 1@0, 10 ]
[ 2@0, 10 ]
[ 3@0, 281 ]
[ 4@0, 1328.8 ]
[ 5@0, 313.10000000000002 ]
[ 6@0, 12.109999999999999 ]
[ 7@0, 12.25 ]
[ 8@0, 100 ]
[ 9@0, 100 ]
[ "..." ]
-------------------------
h t name
oid dbl type
-------------------------
[ 27360@0, 1 ]
[ 28510@0, 1 ]
[ 45451@0, 2 ]
[ 67175@0, 2 ]
[ 81141@0, 2 ]
[ 84571@0, 2 ]
[ 115678@0, 1 ]
[ 145869@0, 1 ]
[ 163876@0, 1 ]
[ 175213@0, 1 ]
[ "..." ]
-------------------------
h t name
void dbl type
-------------------------
[ 6082198@0, 1 ]
[ 6082199@0, 105 ]
[ 6082200@0, 210 ]
[ 6082201@0, 105 ]
[ 6082202@0, 1 ]
[ 6082203@0, 1 ]
[ 6082204@0, 1 ]
[ 6082205@0, 1 ]
[ 6082206@0, 1 ]
[ 6082207@0, 1 ]
< s26 := nil; >
< s27 := nil; >
< var s28 := mvc_bind(myc, `sys`, `produtos_eventos2`,
`quantidade`, 3); produtos_eventos2 >
[ 0 ]
| 0 * { oid , dbl } |
-----------------
h t name
oid dbl type
-----------------
< var s24 := sql_diff(s25, s28); >
[ 0 ]
| 6082208 * { void , dbl } |
---------------------------------
h t name
void dbl type
---------------------------------
[ 0@0, 10 ]
[ 1@0, 10 ]
[ 2@0, 10 ]
[ 3@0, 281 ]
[ 4@0, 1328.8 ]
[ 5@0, 313.10000000000002 ]
[ 6@0, 12.109999999999999 ]
[ 7@0, 12.25 ]
[ 8@0, 100 ]
[ 9@0, 100 ]
[ "..." ]
-------------------------
h t name
oid dbl type
-------------------------
[ 15467@0, 1 ]
[ 27754@0, 1 ]
[ 55507@0, 1 ]
[ 65890@0, 1 ]
[ 80835@0, 1 ]
[ 89744@0, 2 ]
[ 121953@0, 1 ]
[ 131711@0, 2 ]
[ 155932@0, 1 ]
[ 174520@0, 3 ]
[ "..." ]
-------------------------
h t name
void dbl type
-------------------------
[ 6082198@0, 1 ]
[ 6082199@0, 105 ]
[ 6082200@0, 210 ]
[ 6082201@0, 105 ]
[ 6082202@0, 1 ]
[ 6082203@0, 1 ]
[ 6082204@0, 1 ]
[ 6082205@0, 1 ]
[ 6082206@0, 1 ]
[ 6082207@0, 1 ]
< s25 := nil; >
< var s23 := sql_union(s24, s28); >
[ 0 ]
| 6082208 * { void , dbl } |
---------------------------------
h t name
void dbl type
---------------------------------
[ 0@0, 10 ]
[ 1@0, 10 ]
[ 2@0, 10 ]
[ 3@0, 281 ]
[ 4@0, 1328.8 ]
[ 5@0, 313.10000000000002 ]
[ 6@0, 12.109999999999999 ]
[ 7@0, 12.25 ]
[ 8@0, 100 ]
[ 9@0, 100 ]
[ "..." ]
-------------------------
h t name
oid dbl type
-------------------------
[ 6432@0, 1 ]
[ 31378@0, 5 ]
[ 58884@0, 3 ]
[ 71914@0, 8 ]
[ 88327@0, 1 ]
[ 117495@0, 1 ]
[ 118395@0, 2 ]
[ 150986@0, 7 ]
[ 169748@0, 2 ]
[ 171403@0, 1 ]
[ "..." ]
-------------------------
h t name
void dbl type
-------------------------
[ 6082198@0, 1 ]
[ 6082199@0, 105 ]
[ 6082200@0, 210 ]
[ 6082201@0, 105 ]
[ 6082202@0, 1 ]
[ 6082203@0, 1 ]
[ 6082204@0, 1 ]
[ 6082205@0, 1 ]
[ 6082206@0, 1 ]
[ 6082207@0, 1 ]
< s24 := nil; >
< s28 := nil; >
< var s22 := s7.join(s23); >
[ 3266000 ]
| 6082208 * { void , dbl } |
---------------------------------
h t name
void dbl type
---------------------------------
[ 0@0, 10 ]
[ 1@0, 10 ]
[ 2@0, 10 ]
[ 3@0, 281 ]
[ 4@0, 1328.8 ]
[ 5@0, 313.10000000000002 ]
[ 6@0, 12.109999999999999 ]
[ 7@0, 12.25 ]
[ 8@0, 100 ]
[ 9@0, 100 ]
[ "..." ]
-------------------------
h t name
oid dbl type
-------------------------
[ 17420@0, 1 ]
[ 23779@0, 1 ]
[ 51403@0, 1 ]
[ 71940@0, 5 ]
[ 93488@0, 2 ]
[ 99971@0, 1 ]
[ 127566@0, 3 ]
[ 131607@0, 2 ]
[ 135209@0, 1 ]
[ 159559@0, 1 ]
[ "..." ]
-------------------------
h t name
void dbl type
-------------------------
[ 6082198@0, 1 ]
[ 6082199@0, 105 ]
[ 6082200@0, 210 ]
[ 6082201@0, 105 ]
[ 6082202@0, 1 ]
[ 6082203@0, 1 ]
[ 6082204@0, 1 ]
[ 6082205@0, 1 ]
[ 6082206@0, 1 ]
[ 6082207@0, 1 ]
< s23 := nil; >
< var s29 := >
[ 0 ]
[ nil ]
< var s21 := s22.select(s29, s29, FALSE, FALSE); >
[ 5500000 ]
| 6082208 * { oid , dbl } |
---------------------------------
h t name
oid dbl type
---------------------------------
[ 0@0, 10 ]
[ 1@0, 10 ]
[ 2@0, 10 ]
[ 3@0, 281 ]
[ 4@0, 1328.8 ]
[ 5@0, 313.10000000000002 ]
[ 6@0, 12.109999999999999 ]
[ 7@0, 12.25 ]
[ 8@0, 100 ]
[ 9@0, 100 ]
[ "..." ]
-------------------------
h t name
oid dbl type
-------------------------
[ 10301@0, 1 ]
[ 41137@0, 1 ]
[ 50511@0, 1 ]
[ 61531@0, 2 ]
[ 66127@0, 1 ]
[ 90148@0, 3 ]
[ 117496@0, 1 ]
[ 140695@0, 1 ]
[ 160363@0, 2 ]
[ 184847@0, 1 ]
[ "..." ]
-------------------------
h t name
oid dbl type
-------------------------
[ 6082198@0, 1 ]
[ 6082199@0, 105 ]
[ 6082200@0, 210 ]
[ 6082201@0, 105 ]
[ 6082202@0, 1 ]
[ 6082203@0, 1 ]
[ 6082204@0, 1 ]
[ 6082205@0, 1 ]
[ 6082206@0, 1 ]
[ 6082207@0, 1 ]
< s22 := nil; >
< s29 := nil; >
< var s20 := {sum_dbl}(s21, s5, s4); >
[ 453000 ]
| 6645 * { oid , dbl } |
---------------------------------
h t name
oid dbl type
---------------------------------
[ 0@0, 30 ]
[ 3@0, 281 ]
[ 4@0, 2002.8 ]
[ 5@0, 2900.6300000000001 ]
[ 6@0, 262.44999999999999 ]
[ 8@0, 300 ]
[ 9@0, 2900 ]
[ 36@0, 397.87 ]
[ 37@0, 14.300000000000001 ]
[ 38@0, 113.76000000000001 ]
[ "..." ]
-------------------------
h t name
oid dbl type
-------------------------
[ 3076@0, 1590 ]
[ 32000@0, 477 ]
[ 36147@0, 94 ]
[ 44123@0, 458 ]
[ 1661311@0, 6722 ]
[ 1922539@0, 21 ]
[ 4436077@0, 2965 ]
[ 4968259@0, 2000 ]
[ 5538462@0, 130 ]
[ 5603403@0, 1 ]
[ "..." ]
-------------------------
h t name
oid dbl type
-------------------------
[ 6050057@0, 935 ]
[ 6050061@0, 1280 ]
[ 6050121@0, 162 ]
[ 6050122@0, 272 ]
[ 6063348@0, 1 ]
[ 6064631@0, 2 ]
[ 6064633@0, 1 ]
[ 6064635@0, 1 ]
[ 6080986@0, 665 ]
[ 6082199@0, 420 ]
< s21 := nil; >
< s5 := nil; >
< s4 := nil; >
< var s1 := mvc_result_table(myc, 2, 1, s3); >
< mvc_result_column(myc, `sys.produtos_eventos2`,
`produto`, `int`, 32, 0, s3); >
< mvc_result_column(myc, `sys.produtos_eventos2`,
`sum_quantidade`, `double`, 53, 0, s20); >
< mvc_export_result(myc, Output, s1); >
sys.produtos_eventos2, sys.produtos_eventos2
table_name
produto, sum_quantidade name
int, double type
8, 22 length
[ 0, 30 ]
[ 280, 281 ]
[ 360, 2002.8 ]
[ 319, 2900.6300000000001 ]
[ 170, 262.44999999999999 ]
[ 305, 300 ]
[ 991, 2900 ]
[ 72, 397.87 ]
[ 225, 14.300000000000001 ]
[ 40, 113.76000000000001 ]
[ 169, 90.269999999999996 ]
[ 240, 21.280000000000001 ]
[ 244, 29.900000000000002 ]
[ 355, 92.579999999999998 ]
[ 274, 298 ]
[ 17, 49.170000000000002 ]
[ 140, 5.25 ]
[ 259, 1163.5 ]
[ 90, 157.62 ]
[ 241, 2.7000000000000002 ]
[ 345, 271.89999999999998 ]
[ 254, 187 ]
[ 220, 55.609999999999999 ]
[ 238, 37.659999999999997 ]
[ 269, 14.02 ]
[ 62, 12.550000000000001 ]
[ 221, 8.4499999999999993 ]
[ 261, 3.75 ]
[ 335, 111.72 ]
[ 843, 9 ]
[ 19, 321.96999999999997 ]
[ 152, 5.2999999999999998 ]
[ 320, 363.80000000000001 ]
[ 31143, 1168.3999999999999 ]
[ 31179, 111006.3250000001 ]
[ 31253, 1613.3050000000001 ]
[ 31254, 3276.2999999999984 ]
[ 31329, 1081.0999999999999 ]
[ 31026, 726.55100000000004 ]
[ 31049, 26215.840000000011 ]
[ 31070, 3506.4000000000015 ]
[ 31081, 40851.189999999973 ]
[ 31149, 44.109999999999999 ]
[ 31166, 2581.4499999999998 ]
[ 31237, 136.58000000000001 ]
[ 31278, 2718.3600000000006 ]
[ 31290, 3300.9000000000005 ]
[ 31328, 2643.8399999999997 ]
[ 31344, 1543.0300000000004 ]
[ 31368, 9951.2999999999993 ]
[ 33942, 121.40000000000001 ]
[ 50163688, 7484.3499999999976 ]
[ 31023, 318.03999999999996 ]
[ 31028, 10875.595999999994 ]
[ 31096, 4614.4679999999998 ]
[ 31161, 2684.0549999999998 ]
[ 31229, 15583.439999999993 ]
[ 31263, 19255.149999999998 ]
[ 31292, 6514.5299999999997 ]
[ 31029, 655.09000000000003 ]
[ 50163601, 5716 ]
[ 34192, 27992 ]
[ 34194, 12418 ]
[ 34237, 6474 ]
[ 34255, 45175 ]
[ 10032720, 23980 ]
[ 40134011, 117290 ]
[ 40134012, 21606 ]
[ 40135409, 23193 ]
[ 40135633, 3999 ]
[ 40135730, 8681 ]
[ 32310, 165793 ]
[ 40135733, 19665 ]
[ 40134998, 7230 ]
[ 32122, 150 ]
[ 40135741, 5231 ]
[ 40135742, 6154 ]
[ 40135780, 24216 ]
[ 50163754, 2644 ]
[ 50163755, 33220 ]
[ 50163757, 33399 ]
[ 50164056, 19486 ]
[ 50163763, 24757 ]
[ 50163758, 25754 ]
[ 50163760, 20487 ]
[ 50163761, 21835 ]
[ 50163762, 24255 ]
[ 31165, 18002.400000000001 ]
[ 34246, 31910 ]
[ 31371, 130436.94599999998 ]
[ 31381, 124594130.56240001 ]
[ 31509, 0 ]
[ 32277, 1661155 ]
[ 32296, 2552 ]
[ 32319, 2316136 ]
[ 32326, 179037 ]
[ 32358, 1326693.2 ]
[ 31777, 973561 ]
[ 31891, 885191 ]
[ 31118, 16600.769999999997 ]
wall-clock: 30735 ms
[ 50164157, 7648 ]
[ 60196346, 4597 ]
[ 40134524, 12111 ]
[ 50163853, 2998 ]
[ 3053, 305389 ]
[ 32320, 151269 ]
[ 40133853, 5940 ]
[ 50164192, 47453 ]
[ 40134520, 6048 ]
[ 40135589, 36229 ]
[ 34208, 29068 ]
[ 50163764, 34386 ]
[ 50163765, 26096 ]
[ 34290, 16924 ]
[ 34184, 12113 ]
[ 40135779, 2838 ]
[ 34207, 18782 ]
[ 50164057, 7774 ]
[ 50163772, 9135 ]
[ 40134720, 26197 ]
[ 60196272, 5496 ]
[ 60196307, 32871 ]
[ 50164135, 9675 ]
[ 31486, 30358 ]
[ 31803, 82344 ]
[ 32314, 276624 ]
[ 31395, 7498 ]
[ 31485, 435585 ]
[ 31780, 16724 ]
[ 32286, 73740 ]
[ 32359, 532845 ]
[ 31480, 7945 ]
[ 31775, 119122 ]
[ 31384, 83026 ]
[ 31782, 41196 ]
[ 32285, 115794.14 ]
[ 32301, 62883 ]
[ 32357, 338348 ]
[ 31410, 53668 ]
[ 31820, 4753 ]
[ 32188, 53271 ]
[ 34209, 19521 ]
[ 50164079, 6406 ]
[ 32077, 68332 ]
[ 32189, 39281 ]
[ 31387, 139104.5 ]
[ 31383, 126996.25 ]
[ 31442, 34562 ]
[ 32014, 174036 ]
[ 3025, 25854 ]
[ 32103, 505 ]
[ 32111, 5233 ]
[ 32112, 5133 ]
[ 31785, 25499 ]
[ 32303, 14510 ]
[ 3031, 698 ]
[ 32284, 6678 ]
[ 32292, 56348 ]
[ 31193, 66885.800000000003 ]
[ 50163766, 27383 ]
[ 50163771, 4435 ]
[ 50163812, 10398 ]
[ 50164090, 14022 ]
[ 50164060, 9580 ]
[ 50164063, 11889 ]
[ 50164067, 10609 ]
[ 60196493, 9197 ]
[ 34157, 19861 ]
[ 40135601, 227 ]
[ 50163815, 3745 ]
[ 50163816, 7247 ]
[ 40134009, 22258 ]
[ 50163834, 7303 ]
[ 50163847, 6414 ]
[ 50163864, 21398 ]
[ 40135597, 3418 ]
[ 50163868, 18232 ]
[ 34247, 76930 ]
[ 50164182, 3801 ]
[ 34198, 7976 ]
[ 34217, 69844 ]
[ 50163600, 5253 ]
[ 50164048, 6977 ]
[ 50164058, 8823 ]
[ 34177, 58301 ]
[ 40135774, 129338.22 ]
[ 40134977, 11851 ]
[ 31507, 4000 ]
[ 60196276, 3522 ]
[ 50164022, 9369 ]
[ 50164055, 11995 ]
[ 34248, 19683 ]
[ 40135493, 3884 ]
[ 50164132, 17896 ]
[ 32418, 47033 ]
[ 50164026, 10763 ]
[ 50164117, 2615 ]
[ 50164011, 4230 ]
[ 50164065, 8754 ]
[ 50163559, 5211 ]
## Comment 5559
Date: 2006-06-21 13:27:17 +0200
From: @njnes
Logged In: YES
user_id=43556
as we expect the problems are related to memory mapped files
could you try your experiment after running the following
mil code in the server.
vm_minsize(1000000000LL);
## Comment 5560
Date: 2006-06-21 15:30:01 +0200
From: Gustavo Hispagnol <<gmhispagnol>>
Logged In: YES
user_id=818683
Yes. It is a lot better. Total runtime is 4.2 secs now
against 11-12 before the change. Is there some side-effect
of this change? I´d like to understand that parameter
better.
## Comment 5561
Date: 2006-06-21 17:42:52 +0200
From: @njnes
Logged In: YES
user_id=43556
Bats (or heaps) which are smaller than vm_minsize will be
malloced. Bats larger will be mmapped. So I your case the
larger bats (I guess the dbl values once) were mmapped. This
means they need to allocate disk blocks, which is explaining
the low cpu utilisation.
One more remark. If the column on which you perform the avg
is allways 'NOT NULL', it may help the performance of this
query when you add this information using an alter
statement. (in the trace the removal of NULL costed
5seconds, ie 1/3 of the totaal).
## Comment 5562
Date: 2006-06-22 10:54:38 +0200
From: @njnes
Logged In: YES
user_id=43556
closing, as now also the defaults for the vm_minsize are fixed.
## Comment 5563
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1508944 at http://sourceforge.net/support/tracker.php?aid=1508944
| Low CPU utilization in simple query | https://api.github.com/repos/MonetDB/MonetDB/issues/975/comments | 0 | 2020-11-30T09:09:10Z | 2024-06-27T11:10:56Z | https://github.com/MonetDB/MonetDB/issues/975 | 753,296,215 | 975 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-19 02:03:46 +0200
From: Henning Rode <<hrode>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-06-19 04:14:08 +0200
## Comment 5546
Date: 2006-06-19 14:03:46 +0200
From: Henning Rode <<hrode>>
jan r asked me to write a bug report. so here it is:
when trying to run an xquery in the mapiclient i get
the following error:
ERROR: xquery_client_alloc: failed to execute init script.
the mserver outputs meanwhile the following:
MonetDB>!ERROR: interpret: unknown variable 'bool_values'.
!ERROR: interpret_params: insert(param 3): evaluation
error.
!ERROR: interpret_params: insert(param 1): evaluation
error.
!ERROR: interpret_params: insert(param 1): evaluation
error.
!ERROR: interpret_params: insert(param 1): evaluation
error.
!ERROR: interpret_params: insert(param 1): evaluation
error.
!ERROR: interpret_params: insert(param 1): evaluation
error.
!ERROR: interpret_params: access(param 1): evaluation
error.
the failure can perhaps be corrected by just
initializing the boolean values in milprint_summer.c
before.
(at least this works fine with me.)
## Comment 5547
Date: 2006-06-19 14:13:29 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
bug appears sind 14.6. milprint_summer.c revision 1.232 -> 1.233
## Comment 5548
Date: 2006-06-19 16:13:56 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Henning,
being part of the pathfinder 'family' I indeed expect from
you that you always report all bugs you find immediately, so
Jan's help in this should not be required.
bug is fixed
Peter
## Comment 5549
Date: 2006-06-19 16:14:04 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Henning,
being part of the pathfinder 'family' I indeed expect from
you that you always report all bugs you find immediately, so
Jan's help in this should not be required.
bug is fixed
Peter
## Comment 5550
Date: 2006-06-20 02:02:35 +0200
From: @drstmane
Logged In: YES
user_id=572415
Just for the records:
- This is (was) a pathfinder bug, I guess.
- Since it has been fixed in the development trunk (CVS
head), only, I suppose it also occured in with the
development / CVS head version (only?).
Correct me if I'm wrong.
## Comment 5551
Date: 2006-06-20 10:03:33 +0200
From: @peterboncz
Logged In: YES
user_id=591107
This bug only occurred in the HEAD.
## Comment 5552
Date: 2006-06-20 10:55:58 +0200
From: @peterboncz
Logged In: YES
user_id=591107
BTW
this was a bug that occurred on any MapiClient session on
any query, so already covered by any .xq test
## Comment 5553
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1508577 at http://sourceforge.net/support/tracker.php?aid=1508577
| init-script for mapiclient failed | https://api.github.com/repos/MonetDB/MonetDB/issues/974/comments | 0 | 2020-11-30T09:09:06Z | 2024-06-27T11:10:55Z | https://github.com/MonetDB/MonetDB/issues/974 | 753,296,176 | 974 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-19 12:38:37 +0200
From: monica_manzano <<monica_manzano>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2006-06-21 02:44:39 +0200
## Comment 5542
Date: 2006-06-19 12:38:37 +0200
From: monica_manzano <<monica_manzano>>
Using M4 and JdbcClient. Get a crash while running
twice a file with CREATE and INSERT statements. (file
attached)
Error message in the debugger:
/ufs/manzano/monetdb/sql/src/storage/bat/bat_table.mx:73:
full_column: Assertion `i->dims.hseq == BATcount(b)'
failed.
NOTE: running the same file than the one I ran for the
bug I reported saying exactly the same (now I get
different error message)
## Comment 5543
Date: 2006-06-19 15:09:57 +0200
From: @grobian
Logged In: YES
user_id=963970
I just ran it 10 times without getting a crash. Did you
remove and clean your dbfarm?
## Comment 5544
Date: 2006-06-21 14:44:39 +0200
From: @grobian
Logged In: YES
user_id=963970
bug appeared in the head with assertions enabled...
IMHO bug known as:
BugTracker/Tests/drop_sequence_crash{,_2}.SF-1505973
(which indeed is another bug number)
## Comment 5545
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1508521 at http://sourceforge.net/support/tracker.php?aid=1508521
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.
| M4 crashes when running twice the same file (again) | https://api.github.com/repos/MonetDB/MonetDB/issues/973/comments | 0 | 2020-11-30T09:09:02Z | 2024-06-27T11:10:54Z | https://github.com/MonetDB/MonetDB/issues/973 | 753,296,128 | 973 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-18 09:15:07 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2006-06-22 06:48:00 +0200
## Comment 5537
Date: 2006-06-18 21:15:07 +0200
From: @drstmane
After Niels' icc warning option cleanup,
pathfinder does not compile any more with icc,
which now complains about
error 188: enumerated type mixed with another type
in various files.
See attached log for details.
While we could easily avoid these error be re-enabling
the option to disable this warning/error,
it might also be a good idea to take this opportunity
and check whether/how far we could clean-up the code.
Any volunteer(s)?
## Comment 5538
Date: 2006-06-20 08:27:02 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed the compilation issues. Mostly by changing enums into
defines.
## Comment 5539
Date: 2006-06-21 02:16:57 +0200
From: @drstmane
Logged In: YES
user_id=572415
Re-opened as the error still/again(?) occurs with
compiler/mil/milgen.brg
## Comment 5540
Date: 2006-06-22 06:48:00 +0200
From: @drstmane
Logged In: YES
user_id=572415
Niels fixed the compilation also in case assertions are
enabled.
## Comment 5541
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1508245 at http://sourceforge.net/support/tracker.php?aid=1508245
| PF: icc error #188: enumerated type mixed with another type | https://api.github.com/repos/MonetDB/MonetDB/issues/972/comments | 0 | 2020-11-30T09:08:59Z | 2024-06-27T11:10:53Z | https://github.com/MonetDB/MonetDB/issues/972 | 753,296,092 | 972 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-18 05:14:57 +0200
From: @mlkersten
To: @njnes
Version: -- development
Last updated: 2006-06-20 05:12:52 +0200
## Comment 5533
Date: 2006-06-18 17:14:57 +0200
From: @mlkersten
Some unexpected behaviour on SQL variables
sql>declare @i integer;
MAPI = monetdb@localhost:50000
QUERY = declare @i integer;
ERROR = !syntax error, unexpected AT in: "declare @"
sql>select @debug;
tmp. table_name
value name
int type
1 length
[ 0 ]
[ 0 ]
[ 0 ]
[ 0 ]
[ 0 ]
sql>select @cache;
MAPI = monetdb@localhost:50000
QUERY = select @cache;
ERROR = !ERROR: 'batcalc.bit' undefined in
user.s2_1[13] _36:any := batcalc.bit(_34:bat[:void,:str])
tmp. table_name
value name
boolean type
5 length
[ NULL ]
sql>select cache;
. table_name
single_value name
boolean type
5 length
[ true ]
sql>
## Comment 5534
Date: 2006-06-18 17:21:43 +0200
From: @mlkersten
Logged In: YES
user_id=490798
It seems that the variable/session management (on M5) causes
problems. Each user gets a sessions table, which it can
pollute with variables. Ending the session and reconnection
gives him (or somebody else) an old sessions table.
## Comment 5535
Date: 2006-06-20 17:12:52 +0200
From: @njnes
Logged In: YES
user_id=43556
declare @x
set @x are not supported
only select @x.
both select @x and select x (where x is a session variable)
are now handled the same.
Test added to BugTracker directory
variables.SF-1508160
## Comment 5536
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1508160 at http://sourceforge.net/support/tracker.php?aid=1508160
| Variable management | https://api.github.com/repos/MonetDB/MonetDB/issues/971/comments | 0 | 2020-11-30T09:08:56Z | 2024-06-27T11:10:52Z | https://github.com/MonetDB/MonetDB/issues/971 | 753,296,065 | 971 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-15 11:25:50 +0200
From: monica_manzano <<monica_manzano>>
To: @njnes
Version: -- development
Last updated: 2006-06-15 05:12:36 +0200
## Comment 5529
Date: 2006-06-15 11:25:50 +0200
From: monica_manzano <<monica_manzano>>
Playing with the statement SELECT CASE (for avoiding
divisions by zero).
The file attached include the CREATE statements and the
SELECT run which creates the crash
/ufs/manzano/monetdb/sql/src/server/sql_scope.mx:223:
find_pivot: Assertion `0' failed.
## Comment 5530
Date: 2006-06-15 17:12:35 +0200
From: @njnes
Logged In: YES
user_id=43556
The result of a case is a stmt_replace, which didn't have a
relation(->h). Without the relation, the join code was
executed which couldn't find the base table. Now we
correctly keep the relation(pivot).
## Comment 5531
Date: 2006-06-20 16:22:14 +0200
From: @njnes
Logged In: YES
user_id=43556
test added to BugTracker directory
case_in_aggr_bug.SF-1506545.sql
## Comment 5532
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1506545 at http://sourceforge.net/support/tracker.php?aid=1506545
| M4 crashes with an example of SELECT CASE | https://api.github.com/repos/MonetDB/MonetDB/issues/970/comments | 0 | 2020-11-30T09:08:52Z | 2024-06-27T11:10:51Z | https://github.com/MonetDB/MonetDB/issues/970 | 753,296,031 | 970 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-14 02:03:26 +0200
From: monica_manzano <<monica_manzano>>
To: @njnes
Version: -- development
Last updated: 2006-06-15 10:43:57 +0200
## Comment 5525
Date: 2006-06-14 14:03:26 +0200
From: monica_manzano <<monica_manzano>>
In my Java client application (using M4), I was doing
the following actions: open a connection, set
autocommit to false, run all the statements (including
commit), close the connection. The application finishes
successfully.
This created the table 'tapestry' and a fragment of it
'tapestry_0'. I opened a JdbCclient and drop the
tables. When closing the JdbcClient and opening it
again, the tables were still there!!!
At last, today I have found the problem. Because I set
the autocommit to false, somehow that setting stayed
the same when opening a new JdbcClient. So, to make it
work either I have to set autocommit to true before
closing the connection in the Java client application
or I have to manually write 'commit' after writing the
'drop' commands
## Comment 5526
Date: 2006-06-15 10:43:57 +0200
From: @njnes
Logged In: YES
user_id=43556
properly reset session variables now
## Comment 5527
Date: 2006-06-20 16:14:02 +0200
From: @njnes
Logged In: YES
user_id=43556
tested by
./BugTracker/Tests/reset_session_vars.SF-1505987
./BugTracker/Tests/set_session_vars.SF-1505987
## Comment 5528
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1505987 at http://sourceforge.net/support/tracker.php?aid=1505987
| SQL: Autocommit mode saved after closing a connection | https://api.github.com/repos/MonetDB/MonetDB/issues/969/comments | 0 | 2020-11-30T09:08:49Z | 2024-06-27T11:10:50Z | https://github.com/MonetDB/MonetDB/issues/969 | 753,295,995 | 969 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-14 01:45:53 +0200
From: monica_manzano <<monica_manzano>>
To: @njnes
Version: -- development
Last updated: 2006-06-15 04:47:20 +0200
## Comment 5521
Date: 2006-06-14 13:45:53 +0200
From: monica_manzano <<monica_manzano>>
Using M4 and JdbcClient. Get a crash while running
twice a file with CREATE and INSERT statements. (file
attached)
Error message in the debugger:
0x0055bf82 in rollforward_drop_key (tr=0x85cd570,
k=0x86d8068)
at
/ufs/manzano/monetdb/sql/src/storage/bat/bat_store.mx:3391
3391 node *n =
list_find_name(fk->rkey->keys, fk->k.base.name );
## Comment 5522
Date: 2006-06-15 16:47:18 +0200
From: @njnes
Logged In: YES
user_id=43556
when forwarding table drops remove the list from the schema
which dropped the tables (else this will be repeated...)
## Comment 5523
Date: 2006-06-20 16:12:16 +0200
From: @njnes
Logged In: YES
user_id=43556
test added to BugTracker directory
drop_sequence_crash{,_2}.SF-1505973
## Comment 5524
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1505973 at http://sourceforge.net/support/tracker.php?aid=1505973
| SQL: M4 crashes when running twice the same file | https://api.github.com/repos/MonetDB/MonetDB/issues/968/comments | 0 | 2020-11-30T09:08:46Z | 2024-06-27T11:10:49Z | https://github.com/MonetDB/MonetDB/issues/968 | 753,295,965 | 968 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-14 12:51:59 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2006-06-15 09:38:22 +0200
## Comment 5518
Date: 2006-06-14 12:51:59 +0200
From: @grobian
Currently it is possible to drop a schema that is still
in use. This results in all users that have that
schema as their default not to be able to log in any
more. The system should check whether the schema is in
use before dropping and bailing out if so.
## Comment 5519
Date: 2006-06-15 21:38:21 +0200
From: @njnes
Logged In: YES
user_id=43556
new fix. Now we disallow dropping the current schema (as
well as sys and tmp) and any schema which has users with
this default schema. So dropping a table means,
changing/dropping its users first.
## Comment 5520
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1505943 at http://sourceforge.net/support/tracker.php?aid=1505943
| SQL: drop_schema_crash.SF-1504794 needs better fix | https://api.github.com/repos/MonetDB/MonetDB/issues/967/comments | 0 | 2020-11-30T09:08:43Z | 2024-06-27T11:10:48Z | https://github.com/MonetDB/MonetDB/issues/967 | 753,295,921 | 967 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-14 10:23:14 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2006-06-15 09:18:02 +0200
## Comment 5514
Date: 2006-06-14 10:23:14 +0200
From: @grobian
After changing prepare_doesnot_like_LIKE.SF-1234205.sql
to use an inline generated table instead of the system
table "tables", it no longer works, claiming that an
incorrect number of arguments is given to the execute
call of the prepare.
## Comment 5515
Date: 2006-06-15 09:18:01 +0200
From: @njnes
Logged In: YES
user_id=43556
Because of the extra statements the prepared statement ids
changed, ie not a bug but a feature.
## Comment 5516
Date: 2006-06-15 09:18:19 +0200
From: @grobian
Logged In: YES
user_id=963970
The inline creation of course creates internal caches as
well, so the execute counter is further away. This test is
the perfect example why prepare/execute shouldn't be used
like this :)
## Comment 5517
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1505844 at http://sourceforge.net/support/tracker.php?aid=1505844
| SQL: prepare_doesnot_like_LIKE.SF-1234205.sql fails | https://api.github.com/repos/MonetDB/MonetDB/issues/966/comments | 0 | 2020-11-30T09:08:39Z | 2024-06-28T13:33:42Z | https://github.com/MonetDB/MonetDB/issues/966 | 753,295,865 | 966 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-13 06:44:20 +0200
From: Henning Rode <<hrode>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2006-06-20 10:07:42 +0200
## Comment 5507
Date: 2006-06-13 18:44:20 +0200
From: Henning Rode <<hrode>>
the following xquery:
for $d in (<a />, <b />)
return string-join(($d/text(), string(1)), " ")
results in the following error:
!ERROR: interpret: no matching MIL operator to
'ord_uselect(int, int)'.
surprinsingly, adding a string constant resolves the
problem:
for $d in (<a />, <b />)
return string-join(($d/text(), " ", string(1)), " ")
(the above now works!)
the problem can be traced to the kind being a constant
in the first case, and a BAT in the second. there we
were stuck after one day of searching in our code :-(
henning & arjen
just to remark, the following also works correctly
using no string-join:
for $d in (<a />, <b />)
return <x> {$d/text()} {string(1)} </x>
## Comment 5508
Date: 2006-06-20 11:14:34 +0200
From: @peterboncz
Logged In: YES
user_id=591107
added test script in tests/BugTracker
## Comment 5509
Date: 2006-06-20 21:26:00 +0200
From: @drstmane
Logged In: YES
user_id=572415
Re-opened as the new test failes both in the XQuery_0-12
release branch and the development trunk:
branch:
type error: no variant of function fn:string-join accepts
the given argument type(s): (untypedAtomic | string)*; string
type error: maybe you meant:
type error: fn:string-join (string*, string) as string
type error: illegal arguments for function fn:string-join
trunk:
ERROR: interpret: no matching MIL operator to '=(void,
BAT[oid,oid])'.
MAYBE YOU MEAN:
=(timestamp, timestamp) : bit
=(daytime, daytime) : bit
=(date, date) : bit
=(str, str) : bit
=(lng, lng) : bit
=(dbl, dbl) : bit
=(flt, flt) : bit
=(oid, oid) : bit
=(int, int) : bit
=(sht, sht) : bit
=(chr, chr) : bit
=(bit, bit) : bit
=(any::1, any::1) : bit
## Comment 5510
Date: 2006-06-20 21:28:16 +0200
From: @drstmane
Logged In: YES
user_id=572415
set "Category:" and "Group:" and increased priority
## Comment 5511
Date: 2006-06-20 22:07:42 +0200
From: @peterboncz
Logged In: YES
user_id=591107
trunk fix was not propagated in head
Stefan: as you may have seen, lately the Munich folks have
strongly improves static typing. These improvements could
not make it to the stable branch this time. Thus, the error
in the stable branch is unavoidable.
## Comment 5512
Date: 2006-06-21 11:10:28 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Bug was already marked "fixed", though I fixed it only a
couple of seconds ago.
## Comment 5513
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1505520 at http://sourceforge.net/support/tracker.php?aid=1505520
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.
| string-join produces incorrect mil | https://api.github.com/repos/MonetDB/MonetDB/issues/965/comments | 0 | 2020-11-30T09:08:35Z | 2024-06-27T11:10:46Z | https://github.com/MonetDB/MonetDB/issues/965 | 753,295,815 | 965 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-13 09:50:48 +0200
From: @sjoerdmullender
To: @njnes
Version: -- development
Last updated: 2006-06-13 11:17:38 +0200
## Comment 5502
Date: 2006-06-13 09:50:48 +0200
From: @sjoerdmullender
finding the first tuple of a [void,void] bat is broken.
var a :=
new(void,void).seqbase(0@0).reverse().seqbase(0@0).append(0@0).append(1@0);
a.print();
a.find(0@0).print();
Instead of returning the first tuple, this gives an error.
The reason is BUNfndVOID returns a NULL pointer when it
finds the first BUN since BUNfirst() is NULL.
## Comment 5503
Date: 2006-06-13 11:17:38 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed, void,voids have a base again.
## Comment 5504
Date: 2006-06-19 15:48:22 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
The main purpose of creating this bug report was to have a
hook for a test. The test is
tests/BugTracker/Tests/find_first_on_void_void.SF-1505232.milS
## Comment 5505
Date: 2006-09-18 16:53:17 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
I added a test
tests/BugTracker/Tests/find_first_on_void_void.SF-1505232-b.milS
to test the find on a persistent bat.
## Comment 5506
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1505232 at http://sourceforge.net/support/tracker.php?aid=1505232
| find() on [void,void] bat broken | https://api.github.com/repos/MonetDB/MonetDB/issues/964/comments | 0 | 2020-11-30T09:08:32Z | 2024-06-27T11:10:45Z | https://github.com/MonetDB/MonetDB/issues/964 | 753,295,779 | 964 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-13 09:11:00 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2006-06-14 09:06:35 +0200
## Comment 5499
Date: 2006-06-13 09:11:00 +0200
From: @drstmane
`make rpm` fails completely in case of missing tools
like php:
========
php='--without-php';
if [ "" = "" ] ; then php=''; fi
perl='--without-perl';
if [ "" = "" ] ; then perl=''; fi
python='--without-python';
if [ "" = "" ] ; then python=''; fi
java='--without-java';
if [ "" = "" ] ; then java=''; fi
rpmbuild --target `uname -m` --rcfile
/var/tmp/monet.ntv.64.64.d.7817/MonetDB/SuSE9.3/rpm/rpmrc
-ta ./MonetDB-4.12.0_rc1.tar.gz
sh: php-config: command not found
sh: pear: command not found
error: Failed build dependencies:
php is needed by MonetDB-4.12.0_rc1-1
ant is needed by MonetDB-4.12.0_rc1-1
Building target platforms: x86_64
Building for target x86_64
make: *** [rpm] Error 1
========
Although the respective packages are now guarded by the
"_with[out]_X" conditionals in MonetDB.spec[.in], the
respective "BuildRequires: X" still seems to be
triggered even if we aks to buid without X:
========
%if %{?_with_php:1}%{!?_with_php:0}
%package php
Summary: MonetDB php interface
Group: System
BuildRequires: php
%endif
========
In fact, does the build actually depend on the
availability of the respective RPM (e.g., php), or
should there just be some php installation as given by
"--with-php=..."?
In the latter case, we (c|sh)ould IMHO remove the
"BuildRequires: ...".
## Comment 5500
Date: 2006-06-13 12:14:59 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed, we now use automake to properly set the
--with/--without flags. Also correcte the use of them (not
--with-bla but --with bla).
Now when we build using our build system, we don't check
build require anymore as many of our systems have packages
installed without rpm.
Waiting till the test results of tomorrow to close this bug.
## Comment 5501
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1505220 at http://sourceforge.net/support/tracker.php?aid=1505220
| `make rpm`: dependencies too strict? | https://api.github.com/repos/MonetDB/MonetDB/issues/963/comments | 0 | 2020-11-30T09:08:29Z | 2024-06-27T11:10:44Z | https://github.com/MonetDB/MonetDB/issues/963 | 753,295,754 | 963 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-12 04:19:43 +0200
From: monica_manzano <<monica_manzano>>
To: @njnes
Version: -- development
Last updated: 2006-06-13 11:19:45 +0200
## Comment 5496
Date: 2006-06-12 16:19:43 +0200
From: monica_manzano <<monica_manzano>>
Another problem encountered while creating a new schema
in Monetdb4.
We connect with JdbcClient to the user monetdb.
We can the existing users in the table 'users', which
shows only monetdb. This selection can also be done on
'sys.users'
1) CREATE USER "dbtapestry" WITH PASSWORD 'dbtapestry'
NAME 'DB Tapestry' SCHEMA "sys";
2) CREATE SCHEMA "dbtapestry" AUTHORIZATION "dbtapestry";
After creating a new schema (and only if we do not log
out), if we try to select again from the table 'users'
it says it does not exist anymore. Now we have to
access table 'sys.users'
3) ALTER USER "dbtapestry" SET SCHEMA "dbtapestry";
If we drop the schema:
4) drop schema "dbtapestry";
(and no matter if you drop the user or not). You can
still check the users in 'sys.users', BUT if you try to
select from 'users' Monetdb crashes
As a reminder, this does not happen if do not execute
everything in the same client execution
## Comment 5497
Date: 2006-06-13 11:19:45 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed, added test (src/tests/BugTracker/drop_schema_crash)
After dropping the default schema we need to reset the default.
## Comment 5498
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1504794 at http://sourceforge.net/support/tracker.php?aid=1504794
| SQL: M4 crash after dropping schema and selecting from users | https://api.github.com/repos/MonetDB/MonetDB/issues/962/comments | 0 | 2020-11-30T09:08:26Z | 2024-06-27T11:10:43Z | https://github.com/MonetDB/MonetDB/issues/962 | 753,295,720 | 962 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-12 03:55:36 +0200
From: monica_manzano <<monica_manzano>>
To: @njnes
Version: -- development
Last updated: 2006-06-13 11:20:36 +0200
## Comment 5491
Date: 2006-06-12 15:55:36 +0200
From: monica_manzano <<monica_manzano>>
I created a new user and schema like this:
CREATE USER "dbtapestry" WITH PASSWORD 'dbtapestry'
NAME 'DB Tapestry' SCHEMA "sys";
CREATE SCHEMA "dbtapestry" AUTHORIZATION "dbtapestry";
ALTER USER "dbtapestry" SET SCHEMA "dbtapestry";
I tried to connect with that user and JdbcClient but
this error was showed:
A fatal exception occurred: java.sql.SQLException:
SELECT: access denied for dbtapestry to table 'sys.env'
java.sql.SQLException: SELECT: access denied for
dbtapestry to table 'sys.env'
at
nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.executeQuery(MonetConnection.java:2283)
at
nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.processQuery(MonetConnection.java:2036)
at
nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:357)
at
nl.cwi.monetdb.jdbc.MonetStatement.execute(MonetStatement.java:326)
at
nl.cwi.monetdb.jdbc.MonetStatement.executeQuery(MonetStatement.java:390)
at
nl.cwi.monetdb.jdbc.MonetDatabaseMetaData.getEnvMap(MonetDatabaseMetaData.java:54)
at
nl.cwi.monetdb.jdbc.MonetDatabaseMetaData.getDatabaseProductVersion(MonetDatabaseMetaData.java:171)
at
nl.cwi.monetdb.client.JdbcClient.main(JdbcClient.java:450)
## Comment 5492
Date: 2006-06-12 17:25:13 +0200
From: @grobian
Logged In: YES
user_id=963970
release critical problem
## Comment 5493
Date: 2006-06-13 11:20:36 +0200
From: @njnes
Logged In: YES
user_id=43556
env table is now also readable by any user.
## Comment 5494
Date: 2006-06-20 16:01:46 +0200
From: @njnes
Logged In: YES
user_id=43556
is tested by
authorization.SF-1430616.SQL
## Comment 5495
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1504781 at http://sourceforge.net/support/tracker.php?aid=1504781
| SQL: Unable to connect to user different from monetdb in M4 | https://api.github.com/repos/MonetDB/MonetDB/issues/961/comments | 0 | 2020-11-30T09:08:22Z | 2024-06-27T11:10:42Z | https://github.com/MonetDB/MonetDB/issues/961 | 753,295,693 | 961 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-12 11:47:15 +0200
From: monica_manzano <<monica_manzano>>
To: @njnes
Version: -- development
Last updated: 2007-01-29 07:26:26 +0100
## Comment 5481
Date: 2006-06-12 11:47:15 +0200
From: monica_manzano <<monica_manzano>>
I created the tables and inserted the data, and
something went really wrong. I found out it was because
of having another JdbcClient running concurrently.
Because I found it a very interesting bug, I did a
study case (dont know if it will be useful for you).
I checked the behaviour on the clients and took some
steps (I attached a .png with the case study). When
having more than one client running, if you create the
database in one of them, the rest see the tables
created, but there are problems with seeing the data
inserted. In the case study, I insert users tuples in
the users table. In the attached figure, in every step,
I say in which client I do the insertion and the
outcome obtained (when the results are correct, I only
print them sometimes).
After this case study, I went into another one where I
started inserting in the second client run, but the
behaviour was exactly the same; that is, it doesnt
matter if it is the first client run or the second one
the one which does the first create/inserts statements.
Finally, I ran a third client. At the first moment,
this client3 didnt see any of the data inserted. After
inserting another user in any of the three clients,
the other two see the correct data, while the client
who ran it sees wrong data.
I didnt try with MonetDB5
## Comment 5482
Date: 2006-06-12 12:33:38 +0200
From: @grobian
Logged In: YES
user_id=963970
this is release critical
## Comment 5483
Date: 2006-06-13 11:21:54 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed the problem, ie keep delta's also in new transactions.
Could you repeat you test?
## Comment 5484
Date: 2006-12-02 18:39:54 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Re-opened, as no test has been provided, yet.
User (submitter) and/or developer (assignee),
please supply a respective test,
or explain why a test is not required/possible.
## Comment 5485
Date: 2007-01-18 00:16:13 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
lowered priority as it is supposedly fixed, only the test (or a reason why there is none) is missing.
## Comment 5486
Date: 2007-01-25 18:07:01 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: NO
A test was created to cover this bug:
sql/src/jdbc/tests/Tests/BugConcurrent_clients_1504657.SQL
However, the location of the Java file is in:
clients/src/java/tests/BugConcurrent_clients_1504657.java
Regards,
Romulo
## Comment 5487
Date: 2007-01-29 18:52:25 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: NO
This bug is fixed and it is covered by:
sql/src/jdbc/tests/Tests/BugConcurrent_clients_1504657.SQL
However, the location of the Java file is in:
clients/src/java/tests/BugConcurrent_clients_1504657.java
Regards,
Romulo
Note: Why I cannot close it?
## Comment 5488
Date: 2007-01-29 19:26:26 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Closed on behalf of Romulo.
## Comment 5489
Date: 2007-01-29 19:26:48 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Closed on behalf of Romulo.
## Comment 5490
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1504657 at http://sourceforge.net/support/tracker.php?aid=1504657
| SQL: wrong data while inserting tuples in concurrent clients | https://api.github.com/repos/MonetDB/MonetDB/issues/960/comments | 0 | 2020-11-30T09:08:18Z | 2024-06-27T11:10:41Z | https://github.com/MonetDB/MonetDB/issues/960 | 753,295,658 | 960 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-09 08:11:38 +0200
From: Farid Z <<faridz>>
To: @sjoerdmullender
Version: -- development
Last updated: 2007-07-13 11:46:46 +0200
## Comment 5476
Date: 2006-06-09 20:11:38 +0200
From: Farid Z <<faridz>>
It should return something such as 'table'
// table term
rc = SQLGetInfo( hdbc, SQL_TABLE_TERM,
szTableTerm, sizeof( szTableTerm
), &cb );
## Comment 5477
Date: 2006-06-09 21:22:41 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Thanks for noticing this. I have implemented
SQL_PROCEDURE_TERM, SQL_SCHEMA_TERM and SQL_TABLE_TERM.
They will appear in the next release.
## Comment 5478
Date: 2006-12-02 18:39:32 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Re-opened, as no test has been provided, yet.
User (submitter) and/or developer (assignee),
please supply a respective test,
or explain why a test is not required/possible.
## Comment 5479
Date: 2007-07-13 11:46:46 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Added test in sql/src/odbc/samples using program in clients/src/odbc/samples.
## Comment 5480
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1503645 at http://sourceforge.net/support/tracker.php?aid=1503645
| SQLGetInfo SQL_TABLE_TERM returns empty string | https://api.github.com/repos/MonetDB/MonetDB/issues/959/comments | 0 | 2020-11-30T09:08:15Z | 2024-06-27T11:10:40Z | https://github.com/MonetDB/MonetDB/issues/959 | 753,295,623 | 959 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-09 01:34:49 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2006-06-17 09:30:37 +0200
## Comment 5470
Date: 2006-06-09 13:34:49 +0200
From: @drstmane
Unless configured with `--enable-optimize`,
MonetDB fails to compile with icc 8.1 on Itanium 2
under RHEL 4.
System details:
========
$ cat /etc/redhat-release
Red Hat Enterprise Linux WS release 4 (Nahant Update 3)
--------
$ uname -a
Linux titan 2.6.11-1.1381_FC5 1 SMP Thu Jun 9 21:54:39
EDT 2005 ia64 ia64 ia64 GNU/Linux
--------
$ icc --version
8.1
--------
$ cat /proc/cpuinfo
processor : 0
vendor : GenuineIntel
arch : IA-64
family : Itanium 2
model : 1
revision : 5
archrev : 0
features : branchlong
cpu number : 0
cpu regs : 4
cpu MHz : 1300.000000
itc MHz : 1300.000000
BogoMIPS : 1946.15
siblings : 1
========
Error message
========
icc -no-gcc -shared .libs/libbat_la-gdk_scanselect.o
.libs/libbat_la-gdk_batop.o .libs/libbat_la-gdk_desc.o
.libs/libbat_la-gdk_search.o .libs/libbat_la-gdk_tm.o
.libs/libbat_la-gdk_align.o .libs/libbat_la-gdk_bbp.o
.libs/libbat_la-gdk_heap.o .libs/libbat_la-gdk_setop.o
.libs/libbat_la-gdk_utils.o .libs/libbat_la-gdk_atoms.o
.libs/libbat_la-gdk_qsort.o
.libs/libbat_la-gdk_storage.o .libs/libbat_la-gdk_bat.o
.libs/libbat_la-gdk_delta.o .libs/libbat_la-gdk_relop.o
.libs/libbat_la-gdk_system.o
.libs/libbat_la-gdk_value.o .libs/libbat_la-gdk_posix.o
-Wl,--rpath
-Wl,/export/scratch1/manegold/Monet/.ntv.64.64.d..BUILD./MONETDB/src/common/.libs
-Wl,--rpath
-Wl,/export/scratch1/manegold/Monet/.ntv.64.64.d..PREFIX./MONETDB/lib
-L/export/scratch1/manegold/Monet/.ntv.64.64.d..BUILD./MONETDB/src/common/.libs
../common/.libs/libmutils.so
../common/.libs/libstream.so -lz -lbz2 -lpthread -ldl
-lc -Wl,-soname -Wl,libbat.so.0 -o .libs/libbat.so.0.0.0
.libs/libbat_la-gdk_scanselect.o(.text+0x10001e2): In
function `seqscan_Lh_fix_void_tloc_chr_chr':
/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:407:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x1000242):/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:407:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x1002472): In
function `seqscan_Lh_fix_any_tloc_chr_chr_nocheck_noinc':
/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:389:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x10024d2):/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:389:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x1004f62): In
function `seqscan_Lh_fix_any_tloc_chr_chr':
/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:407:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x1004fc2):/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:407:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x1007b32): In
function `seqscan_Lh_fix_void_tloc_sht_sht_nocheck_noinc':
/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:389:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x1007b92):/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:389:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x1009c62): In
function `seqscan_Lh_fix_void_tloc_sht_sht':
/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:407:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x1009cc2):/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:407:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x100bef2): In
function `seqscan_Lh_fix_any_tloc_sht_sht_nocheck_noinc':
/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:389:
additional relocation overflows omitted from the output
ld: final link failed: Nonrepresentable section on output
make[5]: *** [libbat.la] Error 1
make[5]: Leaving directory
`/export/scratch1/manegold/Monet/.ntv.64.64.d..BUILD./MONETDB/src/gdk'
make[4]: *** [all] Error 2
make[4]: Leaving directory
`/export/scratch1/manegold/Monet/.ntv.64.64.d..BUILD./MONETDB/src/gdk'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/export/scratch1/manegold/Monet/.ntv.64.64.d..BUILD./MONETDB/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/export/scratch1/manegold/Monet/.ntv.64.64.d..BUILD./MONETDB/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/export/scratch1/manegold/Monet/.ntv.64.64.d..BUILD./MONETDB'
make: *** [all] Error 2
========
## Comment 5471
Date: 2006-06-09 13:46:54 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
I see relocation problems. Function too large to compile?
(i.e., does icc use a too small type for relocation
information which can be changed when it optimizes the
function (because of extra passes) but not when it doesn't?)
## Comment 5472
Date: 2006-06-10 08:45:00 +0200
From: @drstmane
Logged In: YES
user_id=572415
Without optimization, compilation works only if "-g" is
omitted from the compiler options...
## Comment 5473
Date: 2006-06-10 11:57:49 +0200
From: @drstmane
Logged In: YES
user_id=572415
Compilation fails (with the same errors) with both "-g" and
"-O0".
It works with "-O1", "-mp2 -O2 -restrict -unroll -tpp2
-mcpu=itanium2" as well as without any optimization options
(i.e., the default "-O2").
## Comment 5474
Date: 2006-06-17 09:30:36 +0200
From: @njnes
Logged In: YES
user_id=43556
we switched to icc-9.1 which has new problems but not this
one...
## Comment 5475
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1503463 at http://sourceforge.net/support/tracker.php?aid=1503463
| MonetDB fails to compile with icc8.1 on Itanium2 under RHEL4 | https://api.github.com/repos/MonetDB/MonetDB/issues/958/comments | 0 | 2020-11-30T09:08:11Z | 2024-06-28T13:33:41Z | https://github.com/MonetDB/MonetDB/issues/958 | 753,295,572 | 958 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-09 01:31:24 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2010-05-04 11:19:07 +0200
## Comment 5468
Date: 2006-06-09 13:31:24 +0200
From: @drstmane
========
$ cat /etc/redhat-release
Red Hat Enterprise Linux WS release 4 (Nahant Update 3)
--------
$ uname -a
Linux titan 2.6.11-1.1381_FC5 1 SMP Thu Jun 9 21:54:39
EDT 2005 ia64 ia64 ia64 GNU/Linux
--------
$ icc --version
8.1
--------
$ cat /proc/cpuinfo
processor : 0
vendor : GenuineIntel
arch : IA-64
family : Itanium 2
model : 1
revision : 5
archrev : 0
features : branchlong
cpu number : 0
cpu regs : 4
cpu MHz : 1300.000000
itc MHz : 1300.000000
BogoMIPS : 1946.15
siblings : 1
========
========
icc -no-gcc -shared .libs/libbat_la-gdk_scanselect.o
.libs/libbat_la-gdk_batop.o .libs/libbat_la-gdk_desc.o
.libs/libbat_la-gdk_search.o .libs/libbat_la-gdk_tm.o
.libs/libbat_la-gdk_align.o .libs/libbat_la-gdk_bbp.o
.libs/libbat_la-gdk_heap.o .libs/libbat_la-gdk_setop.o
.libs/libbat_la-gdk_utils.o .libs/libbat_la-gdk_atoms.o
.libs/libbat_la-gdk_qsort.o
.libs/libbat_la-gdk_storage.o .libs/libbat_la-gdk_bat.o
.libs/libbat_la-gdk_delta.o .libs/libbat_la-gdk_relop.o
.libs/libbat_la-gdk_system.o
.libs/libbat_la-gdk_value.o .libs/libbat_la-gdk_posix.o
-Wl,--rpath
-Wl,/export/scratch1/manegold/Monet/.ntv.64.64.d..BUILD./MONETDB/src/common/.libs
-Wl,--rpath
-Wl,/export/scratch1/manegold/Monet/.ntv.64.64.d..PREFIX./MONETDB/lib
-L/export/scratch1/manegold/Monet/.ntv.64.64.d..BUILD./MONETDB/src/common/.libs
../common/.libs/libmutils.so
../common/.libs/libstream.so -lz -lbz2 -lpthread -ldl
-lc -Wl,-soname -Wl,libbat.so.0 -o .libs/libbat.so.0.0.0
.libs/libbat_la-gdk_scanselect.o(.text+0x10001e2): In
function `seqscan_Lh_fix_void_tloc_chr_chr':
/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:407:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x1000242):/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:407:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x1002472): In
function `seqscan_Lh_fix_any_tloc_chr_chr_nocheck_noinc':
/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:389:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x10024d2):/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:389:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x1004f62): In
function `seqscan_Lh_fix_any_tloc_chr_chr':
/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:407:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x1004fc2):/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:407:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x1007b32): In
function `seqscan_Lh_fix_void_tloc_sht_sht_nocheck_noinc':
/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:389:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x1007b92):/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:389:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x1009c62): In
function `seqscan_Lh_fix_void_tloc_sht_sht':
/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:407:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x1009cc2):/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:407:
relocation truncated to fit: PCREL21B BBPcheck
.libs/libbat_la-gdk_scanselect.o(.text+0x100bef2): In
function `seqscan_Lh_fix_any_tloc_sht_sht_nocheck_noinc':
/data/home/manegold/Monet/Current/MonetDB/src/gdk/gdk_scanselect.mx:389:
additional relocation overflows omitted from the output
ld: final link failed: Nonrepresentable section on output
make[5]: *** [libbat.la] Error 1
make[5]: Leaving directory
`/export/scratch1/manegold/Monet/.ntv.64.64.d..BUILD./MONETDB/src/gdk'
make[4]: *** [all] Error 2
make[4]: Leaving directory
`/export/scratch1/manegold/Monet/.ntv.64.64.d..BUILD./MONETDB/src/gdk'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/export/scratch1/manegold/Monet/.ntv.64.64.d..BUILD./MONETDB/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/export/scratch1/manegold/Monet/.ntv.64.64.d..BUILD./MONETDB/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/export/scratch1/manegold/Monet/.ntv.64.64.d..BUILD./MONETDB'
make: *** [all] Error 2
========
## Comment 5469
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1503461 at http://sourceforge.net/support/tracker.php?aid=1503461
Bug has invalid status, setting status to "NEW".
Previous status was "DELETED".
| MonetDB fails to compile with icc8 on Itanium 2 under RHEL 4 | https://api.github.com/repos/MonetDB/MonetDB/issues/957/comments | 0 | 2020-11-30T09:08:08Z | 2024-06-27T11:10:38Z | https://github.com/MonetDB/MonetDB/issues/957 | 753,295,534 | 957 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-03 10:39:36 +0200
From: Jan Rittinger <<jan.rittinger>>
To: @sjoerdmullender
Version: -- development
Last updated: 2006-06-04 05:15:56 +0200
## Comment 5465
Date: 2006-06-03 22:39:36 +0200
From: Jan Rittinger <<jan.rittinger>>
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/ntv.64.64.d-SuSE9.3/tests_XQuery/empty.out.00.html
In the current compilation of milprint_summer.c an
empty sequence is recognised as update tape. This
probably happens in line 11078:
'milprintf(f,_PFstopMIL(PFty_subtype(TY(R(c)),PFty_star(PFty_stmt()))));'
Perhaps a solution would be to check for the empty
sequence first:
if (PFty_subtype (TY(R(c)), PFty_empty ())
milprintf(f,_PFstopMIL(false));
else
milprintf(f,_PFstopMIL(PFty_subtype(TY(R(c)),PFty_star(PFty_stmt()))));
Am I correct?
## Comment 5466
Date: 2006-06-04 17:15:55 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
I checked in a corrected version. It thus should be fixed.
## Comment 5467
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1500199 at http://sourceforge.net/support/tracker.php?aid=1500199
| PF: query '()' fails | https://api.github.com/repos/MonetDB/MonetDB/issues/956/comments | 0 | 2020-11-30T09:08:04Z | 2024-06-27T11:10:37Z | https://github.com/MonetDB/MonetDB/issues/956 | 753,295,493 | 956 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-03 11:15:41 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2006-06-04 01:25:21 +0200
## Comment 5462
Date: 2006-06-03 11:15:41 +0200
From: @drstmane
In various cases, serialization now seems to produce
fewer whitespaces than before.
While this is IMHO irrelevant in some cases
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/union2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/intersect2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/except2.out.00.html
it might be relevant (i.e., incorrect output?) in other
cases
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/orderby4.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/orderby7.out.00.html
What do the experts say?
## Comment 5463
Date: 2006-06-03 22:20:51 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
I changed the xml mode to return its result as created by an
element constructor. Thus spaces are introduced only between
atomic types and string are of course not quoted.
## Comment 5464
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1499979 at http://sourceforge.net/support/tracker.php?aid=1499979
| PF: serialization with fewer whitespace? | https://api.github.com/repos/MonetDB/MonetDB/issues/955/comments | 0 | 2020-11-30T09:08:01Z | 2024-06-27T11:10:36Z | https://github.com/MonetDB/MonetDB/issues/955 | 753,295,455 | 955 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-03 10:21:54 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-06-20 08:13:52 +0200
## Comment 5458
Date: 2006-06-03 10:21:54 +0200
From: @drstmane
Tests tests/XQuery/Tests/typeswitch[34].xq fail with
property errors
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/typeswitch3.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/typeswitch4.err.00.html
## Comment 5459
Date: 2006-06-14 00:30:17 +0200
From: @peterboncz
Logged In: YES
user_id=591107
property bug in outerjoin fixed in gdk_relop.mx (in 4-12 branch)
when propagated to HEAD (stefan), can be closed
## Comment 5460
Date: 2006-06-20 20:13:52 +0200
From: @drstmane
Logged In: YES
user_id=572415
also works in the HEAD, now.
## Comment 5461
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1499969 at http://sourceforge.net/support/tracker.php?aid=1499969
| PF: tests/XQuery/Tests/typeswitch[34].xq: property errors | https://api.github.com/repos/MonetDB/MonetDB/issues/954/comments | 0 | 2020-11-30T09:07:58Z | 2024-06-27T11:10:35Z | https://github.com/MonetDB/MonetDB/issues/954 | 753,295,407 | 954 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-03 10:19:53 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2006-06-04 05:17:59 +0200
## Comment 5455
Date: 2006-06-03 10:19:53 +0200
From: @drstmane
Test tests/XQuery/Tests/typeswitch2.xq fails with
ERROR: " );"
^
can't help you here, sorry.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/typeswitch2.err.00.html
## Comment 5456
Date: 2006-06-04 17:17:57 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
a copy & paste error in the typeswitch translation (that I
extended last week). It should be now fixed.
## Comment 5457
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1499968 at http://sourceforge.net/support/tracker.php?aid=1499968
| PF: tests/XQuery/Tests/typeswitch2.xq fails with MIL error | https://api.github.com/repos/MonetDB/MonetDB/issues/953/comments | 0 | 2020-11-30T09:07:55Z | 2024-06-27T11:10:34Z | https://github.com/MonetDB/MonetDB/issues/953 | 753,295,373 | 953 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-03 09:53:33 +0200
From: @drstmane
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2006-06-14 12:00:00 +0200
## Comment 5453
Date: 2006-06-03 09:53:33 +0200
From: @drstmane
All variants (except the algebra version) of XMark's
Q10 as well as XPathMark's Q46 fail with
Mserver:
/var/tmp/monet.GNU.64.64.d.10716/MonetDB/src/gdk/gdk_search.mx:520:
HASHremove: Assertion `0' failed.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XMark/q10.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XMark_mod_MIL/q10.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XMark_mod_XQ/q10.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XMark_opt_MIL/q10.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XMark_opt_XQ/q10.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XPathMark/Q46.err.00.html
## Comment 5454
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1499962 at http://sourceforge.net/support/tracker.php?aid=1499962
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| PF: XMark Q10: "HASHremove: Assertion `0' failed." | https://api.github.com/repos/MonetDB/MonetDB/issues/952/comments | 0 | 2020-11-30T09:07:51Z | 2024-06-28T13:33:41Z | https://github.com/MonetDB/MonetDB/issues/952 | 753,295,327 | 952 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-03 09:48:44 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2006-06-09 02:01:29 +0200
## Comment 5450
Date: 2006-06-03 09:48:44 +0200
From: @drstmane
Test tests/Update/Tests/update.xq fails with
"reference to undefined function `fn:delete'".
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_Update/update.err.00.html
## Comment 5451
Date: 2006-06-09 14:01:29 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
This should be fixed. The fn:delete function is gone (as
are fn:insert-*, fn:set-* and fn:unset-attr). Updates are
now done using the new syntax and internal functions
upd:delete upd:insert*, upd:rename, and upd:replacValue.
I have fixed the update tests to use the new syntax.
Other bugs remain, but this is not a bug.
## Comment 5452
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1499959 at http://sourceforge.net/support/tracker.php?aid=1499959
| PF: update.xq: "reference to undefined function `fn:delete'" | https://api.github.com/repos/MonetDB/MonetDB/issues/951/comments | 0 | 2020-11-30T09:07:48Z | 2024-06-27T11:10:32Z | https://github.com/MonetDB/MonetDB/issues/951 | 753,295,271 | 951 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-03 09:45:46 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2006-06-09 05:28:56 +0200
## Comment 5446
Date: 2006-06-03 09:45:46 +0200
From: @drstmane
Most tests in tests/Update/Tests/ fail with property
errors:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_Update/insert-1.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_Update/insert-2.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_Update/symm-test-2.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_Update/symm-test-3.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_Update/symm-test-4.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_Update/symm-test-5.err.00.html
## Comment 5447
Date: 2006-06-09 14:04:10 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
I found the proximate problem why we get BATpropcheck errors
in many of the update tests, but not the underlying problem.
For that I think I need Peter's help.
At the end of updating, the indixes get rebuilt. The
operative command (see function build_indices in
pf_support.mx) is
b.access(BAT_WRITE).delete().insert(n);
where b is the result of
ws.fetch(_KND_NID_0).find(containerID) and n is a (correctly
constructed) bat with the new values. In other words,
delete the old contents and insert the new. Note that this
modifies the master copy.
When I then load the modified document in a fresh MapiClient
(with the same server), and I look at the master copy of the
index, it is correct. However, the "view" KND_NID_0 is
incorrect:
mil>ws.fetch(_KND_NID_0).find(1@0).print();
-----------------
h t name
void oid type
-----------------
[ 0@0, 1@0 ]
mil>ws.fetch(KND_NID_0).find(1@0).print();
MAPI = monetdb@localhost:50000
QUERY = ws.fetch(KND_NID_0).find(1@0).print();
ERROR = !WARNING: BATpropcheck: BAT tmp_504 was incorrectly
marked keyed!
-----------------
h t name
void oid type
-----------------
[ 0@0, 1@0 ]
[ 1@0, 1@0 ]
Assigned to Peter to take a closer look.
## Comment 5448
Date: 2006-06-09 17:28:56 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed with revision 1.154 of gdk_bat.mx. The "copy" of a
bat with batFirst not pointing to Bunbase() resulted in a
bat with batFirst set incorrectly, causing confusion in
BATloop and BATpropcheck.
No test added since most of the PF update tests do an
admirable job testing this condition.
## Comment 5449
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1499957 at http://sourceforge.net/support/tracker.php?aid=1499957
| PF: most update tests fail with property errors | https://api.github.com/repos/MonetDB/MonetDB/issues/950/comments | 0 | 2020-11-30T09:07:45Z | 2024-06-27T11:10:31Z | https://github.com/MonetDB/MonetDB/issues/950 | 753,295,231 | 950 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-03 09:41:41 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2006-06-04 05:16:32 +0200
## Comment 5437
Date: 2006-06-03 09:41:41 +0200
From: @drstmane
Various test now fail, because strings (xs:string) are
now serialized without `"', while they used to be
enclosed in `"'.
What's the desired/correct version?
If the new one (w/o `"'), then the respective tests new
output has to be approved.
If the old one (w/ `"'), then the bug has to be
located and fixed.
See e.g.:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-11-09_0.9.3/dashes_in_functions.SF-1198495.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-11-09_0.9.3/distinct_integers.SF-1312716.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugsViaSourgeforce/ID.1286005-1.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_WebSite/distinct_values_bug.SF-1210748.out.00.html
## Comment 5438
Date: 2006-06-03 09:57:05 +0200
From: @drstmane
Logged In: YES
user_id=572415
See also:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/cast5.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/if1.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/if2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/if6.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/if7.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/string-join.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/concat.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/is-before4.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/is.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/is-after.out.00.html
## Comment 5439
Date: 2006-06-03 10:03:44 +0200
From: @drstmane
Logged In: YES
user_id=572415
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/orderby2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/fn_min.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/fn_max.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/replace1.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/replace2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/replace3.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/replace4.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/replace7.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/replace8.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/replace10.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/replace11.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/replace12.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/replace13.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/replace14.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/replace15.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/replace16.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/replace17.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/replace18.out.00.html
## Comment 5440
Date: 2006-06-03 22:20:24 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
I changed the xml mode to return its result as created by an
element constructor. Thus spaces are introduced only between
atomic types and string are of course not quoted.
## Comment 5441
Date: 2006-06-04 13:25:03 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
The replace tests do not work in my setting. Could please
someone else approve their output.
Thanks,
Jan
## Comment 5442
Date: 2006-06-04 13:48:38 +0200
From: @drstmane
Logged In: YES
user_id=572415
Approved new stable output of replace tests.
What about
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-11-09_0.9.3/dashes_in_functions.SF-1198495.out.00.html
?
I has not been approved, yet.
Did you just overlook/forget it, or is the new output not
correct (yet?)?
## Comment 5443
Date: 2006-06-04 16:28:47 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
thanks,
The changes of the dashes_in_functions.SF-1198495 test are
also checked in (at least CVS commit did not report any error).
## Comment 5444
Date: 2006-06-04 17:16:31 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
now more wrong results in my testweb...
## Comment 5445
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1499953 at http://sourceforge.net/support/tracker.php?aid=1499953
| PF: serialization in xs:string now without `"'? | https://api.github.com/repos/MonetDB/MonetDB/issues/949/comments | 0 | 2020-11-30T09:07:42Z | 2024-06-27T11:10:31Z | https://github.com/MonetDB/MonetDB/issues/949 | 753,295,193 | 949 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-03 09:34:44 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2006-06-07 02:26:37 +0200
## Comment 5432
Date: 2006-06-03 09:34:44 +0200
From: @drstmane
In test runtime/Tests/text1.milS, the output of
serialization mode "xml-seq-mapi" differs from the
stable/approved (correct/expected?) output.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/runtime/text1.out.00.html
## Comment 5433
Date: 2006-06-03 22:15:53 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
In my eyes the serialization mode xml-seq-mapi does not make
sense as seq is now completely independent of the xml mode
and has no mapi variant. (But perhaps I'm also getting
something wrong.)
I think Fabian as the creator of this test is the one to
specify the expected result.
## Comment 5434
Date: 2006-06-06 09:06:51 +0200
From: @grobian
Logged In: YES
user_id=963970
The new serialisation engine simply isn't backwards
compatible. This test simply checks if the serialisation
output works with all MAPI implementations. Reassigning to
author of new engine.
## Comment 5435
Date: 2006-06-07 14:26:35 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
This mode does not make sense anymore.
Removed the test (it is subsumed by the 'serialization' test).
## Comment 5436
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1499951 at http://sourceforge.net/support/tracker.php?aid=1499951
| PF: ser. mode "xml-seq-mapi" fails: runtime/Tests/text1.milS | https://api.github.com/repos/MonetDB/MonetDB/issues/948/comments | 0 | 2020-11-30T09:07:38Z | 2024-06-27T11:10:30Z | https://github.com/MonetDB/MonetDB/issues/948 | 753,295,145 | 948 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-02 12:39:15 +0200
From: @yzchang
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2006-12-06 05:16:11 +0100
## Comment 5424
Date: 2006-06-02 12:39:15 +0200
From: @yzchang
There are several problems with the serialization modes.
- 'xml-noroot' prints garbage and hangs
$echo "(\"abc\", 1243, <a/>)" | mapiclnt -lx -s xml-noroot
abc 1243<a/>
- 'xml-root-<newrootname>' gets an additional '-mapi'
which was not the intension of the original implementation:
$echo "(\"abc\", 1243, <a/>)" | mapiclnt -lx -s
xml-root-result
<?xml version="1.0" encoding="utf-8"?>
<result-mapi>
abc 1243<a/>
</result-mapi>
- 'xml-typed-root-hello' does not work:
<result:sequence
xmlns:result="http://monetdb.cwi.nl/xquery-results"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><result:atomic-value
xsi:type="xs:string">abc</result:atomic-value><result:atomic-value
xsi:type="xs:integer">1243</result:atomic-value><result:element><a/></result:element></result:sequence>
## Comment 5425
Date: 2006-06-02 12:45:04 +0200
From: @grobian
Logged In: YES
user_id=963970
> - 'xml-noroot' prints garbage and hangs
> $echo "(\"abc\", 1243, <a/>)" | mapiclnt -lx -s xml-noroot
> abc 1243<a/>
> ^A
This looks like a malformed prompt, which is not recognised
and printed to the screen.
## Comment 5426
Date: 2006-06-02 13:17:25 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
- Fabian is correct: the fix was checked in 11:55.
- The additional mapi is fixed and checked in by Peter (the
mapi argument was the last one since it was first introduced
by Stefan 23-May-05).
- The typed XML mode in my eyes does not work with the
noroot option as well as the root-<name> option because of
two reasons. Omitting the root element results in undeclared
namespaces and replacing only the sequence name and _not_
the other element wrapper names would be inconsistent.
Thus it is won't fix from my side...
## Comment 5427
Date: 2006-06-02 13:18:42 +0200
From: @yzchang
Logged In: YES
user_id=341633
Jan's checkin has fixed the problem with 'xml-noroot'.
Peter's checkin has fixed the problem with
'xml-root-<newrootname>'.
But I'm wondering if the following outputs are expected
behaviour of the mode 'root-hello', 'noroot', and
'noroot-noheader':
$echo "(\"abc\", 1243, <a/>)" | mapiclnt -lx -s root-hello
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>
abc 1243<a/>
</XQueryResult>
$echo "(\"abc\", 1243, <a/>)" | mapiclnt -lx -s noroot
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>
abc 1243<a/>
</XQueryResult>
$echo "(\"abc\", 1243, <a/>)" | mapiclnt -lx -s noroot-noheader
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>
abc 1243<a/>
</XQueryResult>
## Comment 5428
Date: 2006-06-02 14:46:21 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
You forgot to add the 'xml' argument thus it does not now
what to print and chooses the standard output mode (xml mode
without arguments).
## Comment 5429
Date: 2006-11-29 11:10:08 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Re-opened, as no test has been provided, yet.
User (submitter) and/or developer (assignee),
please supply a respective test,
or explain why a test is not required/possible.
## Comment 5430
Date: 2006-12-06 17:16:11 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
there is already a test (runtime/Tests/serialization)
## Comment 5431
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1499426 at http://sourceforge.net/support/tracker.php?aid=1499426
| PF: several problems with serialization modes | https://api.github.com/repos/MonetDB/MonetDB/issues/947/comments | 0 | 2020-11-30T09:07:35Z | 2024-06-27T11:10:29Z | https://github.com/MonetDB/MonetDB/issues/947 | 753,295,109 | 947 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-02 08:44:31 +0200
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-06-03 08:00:56 +0200
## Comment 5421
Date: 2006-06-02 08:44:31 +0200
From: @drstmane
After yesterday's (Thursday, June 1, 2006) changes to
MonetDB (see cvs messages below; there were no changes
to SQL), 359 SQL tests fail.
See attached list and
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/index_short.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/GNU.64.64.d-Fedora4/src_backends_monet4/sample1.out.00.html
for details.
===================================================================
2006/06/01 - stmane:
src/gdk/Tests/refcnt.stable.out.oid32,1.1
tests/from_Twente/Bugs/Tests/Arjen_02.stable.out.oid32,1.2
more oid32 specific stable output
===================================================================
2006/06/01 - sjoerd: src/modules/mnetcdf/mnetcdf.mx,1.15
BUNins now has four args.
===================================================================
2006/06/01 - boncz: src/gdk/gdk_bbp.mx,1.170
src/gdk/gdk_storage.mx,1.108
src/gdk/Tests/All,1.21
src/gdk/Tests/append_bat_val.new.stable.out,1.7
src/gdk/Tests/cache.milM,1.1
src/gdk/Tests/cache.stable.err,1.1
src/gdk/Tests/cache.stable.out,1.1
src/gdk/Tests/casts.stable.out.Linux.64bit,1.7
src/gdk/Tests/insert_bat_bun.new.stable.out,1.5
src/gdk/Tests/refcnt.stable.out,1.30
src/monet/monet_interpreter.mx,1.103
- fixed a bug in BBPcache (in reallocation of BBP
structure BBPvalid() was used)
- added a BBPcache test
- fixed a bug in void casts
- approved some more outputs
===================================================================
2006/06/01 - boncz: src/gdk/gdk_tm.mx,1.37
bugfix in TMcommit: list of bats should be sorted..
(this bug caused a lot of pathfinder mayhem)
===================================================================
2006/06/01 - stmane:
src/gdk/Tests/casts.stable.out.Linux.64bit,1.8
src/gdk/Tests/refcnt.stable.out,1.31
(re-)approved default/64bit-oid64 stable output.
Peter,
could you please cvs update your complete MonetDB
source tree to get the latest
oid32 specific stable output?
This should keep us from constantly overruling our
stable output approvals...
Thanks!
===================================================================
## Comment 5422
Date: 2006-06-03 08:00:56 +0200
From: @drstmane
Logged In: YES
user_id=572415
Checkins of Friday, June 2, 2006, apparently solved the
problem(s) and restored the original state.
Thank you all!
## Comment 5423
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1499315 at http://sourceforge.net/support/tracker.php?aid=1499315
| SQL: 359 tests fail after recent MonetDB changes | https://api.github.com/repos/MonetDB/MonetDB/issues/946/comments | 0 | 2020-11-30T09:07:32Z | 2024-06-27T11:10:28Z | https://github.com/MonetDB/MonetDB/issues/946 | 753,295,078 | 946 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-02 08:08:11 +0200
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-06-03 07:55:10 +0200
## Comment 5418
Date: 2006-06-02 08:08:11 +0200
From: @drstmane
After yesterday's (Thursday June 01 2006) checkins,
test src/gdk/Tests/TMsubcommit.milS fails with
!01 ERROR: BATSIGcrash: Mserver internal error
(Segmentation fault), please restart.
!01 ERROR: (One potential cause could be that your disk
might be full...)
(only) on the following platforms:
Debian3.1 GNU.64.64.d,
Fedora4 GNU.64.32.d,
Fedora4 GNU.64.64.d,
Fedora4 ntv.64.32.d,
Fedora4 ntv.64.64.d,
Gentoo1.6.14 GNU.32.32.d ,
SuSE9.3 ntv.64.64.d,
SunOS5.10 GNU.32.32.d
see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests103/GNU.64.32.d-Fedora4/src_gdk/TMsubcommit.out.00.html
for details.
## Comment 5419
Date: 2006-06-03 07:55:10 +0200
From: @drstmane
Logged In: YES
user_id=572415
Fixed by Niels.
Thanks!
## Comment 5420
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1499307 at http://sourceforge.net/support/tracker.php?aid=1499307
| test src/gdk/Tests/TMsubcommit.milS fails with segfault | https://api.github.com/repos/MonetDB/MonetDB/issues/945/comments | 0 | 2020-11-30T09:07:28Z | 2024-06-27T11:10:27Z | https://github.com/MonetDB/MonetDB/issues/945 | 753,295,040 | 945 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-01 10:05:34 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2007-07-03 12:04:21 +0200
## Comment 5407
Date: 2006-06-01 22:05:34 +0200
From: Jan Rittinger <<jan.rittinger>>
I have no idea why, but shredding of the 100MB XMark
document results in 595094 site nodes. Expected is one
single site node (the root node).
> echo 'count(doc ("auction100MB.xml")//site)' | pfm
Monet Database Server V4.11.3
Copyright (c) 1993-2006, CWI. All rights reserved.
Compiled for i686-suse-linux/32bit with 32bit OIDs;
dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>
595094
</XQueryResult>
> cat auction100MB.xml | grep '<site' | wc
1 1 7
## Comment 5408
Date: 2006-06-01 22:51:58 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
This bug is probably related to [1483706 XQuery: Corrupt
attributelist for document]. When switching to mmapped
bats, the BATs are filled with zeros (or maybe garbage).
To test whether it is the same bug, you could try
setting "vm_minsize();" somewhat larger... does this give
you a different result?
I actually would expect many doc-nodes (=0@0) and not root-
nodes (=1@0), or did the doc-node perhaps disappear in the
new storage scheme?
## Comment 5409
Date: 2006-06-01 23:25:45 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
This happens already in shredder.mx and the reason is
probably the representation of the 'rid_prop' BAT that
contains only 0 values for the first 36% percent of the
table (until BUN no. 1694518).
Don't know whether this helps anybody...
## Comment 5410
Date: 2006-06-01 23:31:29 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Ok -- just read Wouters comment. It seems like these bugs
are related. I make it a duplicate and assign it to Peter :)
## Comment 5411
Date: 2006-06-08 14:50:24 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
I had a look at Wouters repair and talked about it with
Peter. The fix was nearly OK. It only worked for [void,oid]
BAT's. We decided to use the setBATcapacity() function which
we used to make the final BAT administration correct for all
intermediate BATextends(). On my site this solution works fine.
## Comment 5412
Date: 2006-06-14 00:00:44 +0200
From: @peterboncz
Logged In: YES
user_id=591107
I assume this works now
## Comment 5413
Date: 2007-06-14 04:20:05 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 365 days (the time period specified by
the administrator of this Tracker).
## Comment 5414
Date: 2007-06-14 11:48:11 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
I guess the robot should be shut up.
## Comment 5415
Date: 2007-07-03 12:04:21 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
this one was fixed a long time ago - robot was right this time
## Comment 5416
Date: 2007-07-03 12:05:15 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
this one was fixed a long time ago - robot was right this time
## Comment 5417
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1499097 at http://sourceforge.net/support/tracker.php?aid=1499097
This bug was marked DUPLICATE in the database it was moved from.
Changing resolution to "MOVED"
| PF: shredding of large documents is corrupt | https://api.github.com/repos/MonetDB/MonetDB/issues/944/comments | 0 | 2020-11-30T09:07:25Z | 2024-06-28T13:33:40Z | https://github.com/MonetDB/MonetDB/issues/944 | 753,295,007 | 944 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-01 09:05:44 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-06-01 09:09:41 +0200
## Comment 5404
Date: 2006-06-01 09:05:44 +0200
From: @drstmane
see also
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.ntv.64.64.d-Fedora4/make.out
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/runtime
-I..
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/runtime
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.32.d..PREFIX./MONETDB/include/MonetDB
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.32.d..PREFIX./MONETDB/include/MonetDB/common
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.32.d..PREFIX./MONETDB/include/MonetDB/gdk
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.32.d..PREFIX./MONETDB/include/MonetDB/monet
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.32.d..PREFIX./MONETDB/include/MonetDB/plain
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.32.d..PREFIX./MONETDB/include/MonetDB/contrib
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.32.d..PREFIX./MONETDB/include/MonetDB/mapi
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.32.d..PREFIX./MONETDB/include/MonetDB/C
-I/usr/include/libxml2 -I../compiler/include
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/runtime/../compiler/include
-DLIBPF_SUPPORT -g -we140 -wd1418 -c99 -Wall -w2 -we266
-Werror
-wd1418,1419,279,310,981,810,444,193,111,177,171,181,764,269,108,188,1357,102,70,1572
-DEMBEDDED -DMT -DNO_CGI -DNO_AUTH -DIO_MAX=10240 -c
serialize.c -KPIC -DPIC -o
.libs/lib_pf_support_la-serialize.o
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/runtime/serialize.mx(570):
error 593: variable "xnf" was set but never used
XmlNsFrame* xnf;
^
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/runtime/serialize.mx(691):
error 593: variable "xnf" was set but never used
XmlNsFrame* xnf;
^
compilation aborted for serialize.c (code 2)
make[3]: *** [lib_pf_support_la-serialize.lo] Error 1
make[3]: Leaving directory
`/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/.ntv.64.32.d..BUILD./PATHFINDER/runtime'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/.ntv.64.32.d..BUILD./PATHFINDER/runtime'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/.ntv.64.32.d..BUILD./PATHFINDER'
make: *** [all] Error 2
## Comment 5405
Date: 2006-06-01 09:09:41 +0200
From: @drstmane
Logged In: YES
user_id=572415
sorry, couldn't resist to fix it myself;
was quite trivial ...
## Comment 5406
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1498678 at http://sourceforge.net/support/tracker.php?aid=1498678
| PF: runtime/serialize.mx fails to compile with Intel's icc | https://api.github.com/repos/MonetDB/MonetDB/issues/943/comments | 0 | 2020-11-30T09:07:22Z | 2024-06-27T11:10:25Z | https://github.com/MonetDB/MonetDB/issues/943 | 753,294,970 | 943 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-06-01 08:41:00 +0200
From: @drstmane
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2006-06-03 07:53:42 +0200
## Comment 5399
Date: 2006-06-01 08:41:00 +0200
From: @drstmane
After changes between May 19 and May 27 2006,
MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c fails
to compile on Darwin (both 32 & 64 bit);
see also
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.GNU.32.32.d-Darwin8.6.0/make.out
and/or
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.GNU.64.64.d-Darwin8.6.0/make.out
gcc -m32 -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl
-I../../../../..
-I/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl
-I../../C
-I/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/../../C
-I../../../../common
-I/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/../../../../common
-I -I/usr/include/php -I/usr/include/php/main
-I/usr/include/php/TSRM -I/usr/include/php/Zend
-I/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/
-I/usr/include/php -I/usr/include/php/main
-I/usr/include/php/TSRM -I/usr/include/php/Zend -O2
-std=c99 -Wall -W -O6 -fomit-frame-pointer
-finline-functions -DCOMPILE_DL_MONETDB=1 -D_GNU_SOURCE
-D_REENTRANT -c
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c
-fno-common -DPIC -o .libs/php_monetdb.o
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:42:29:
error: zend_exceptions.h: No such file or directory
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function '_php_monetdb_trim_message':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:158:
warning: initialization discards qualifiers from
pointer target type
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
At top level:
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:343:
error: 'OnUpdateLong' undeclared here (not in a function)
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'zm_startup_monetdb':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:370:
warning: unused parameter 'type'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'zm_shutdown_monetdb':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:419:
warning: unused parameter 'type'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'zm_activate_monetdb':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:431:
warning: unused parameter 'type'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:431:
warning: unused parameter 'module_number'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'zm_deactivate_monetdb':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:441:
warning: unused parameter 'type'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:441:
warning: unused parameter 'module_number'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'php_monetdb_do_connect':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:492:
warning: missing initializer
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:492:
warning: (near initialization for 'str.len')
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:482:
warning: unused parameter 'this_ptr'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:482:
warning: unused parameter 'return_value_used'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'zif_monetdb_close':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:684:
warning: unused parameter 'this_ptr'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:684:
warning: unused parameter 'return_value_used'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'php_monetdb_get_link_info':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:732:
warning: unused parameter 'this_ptr'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:732:
warning: unused parameter 'return_value_used'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'zif_monetdb_ping':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:830:
warning: unused parameter 'this_ptr'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:830:
warning: unused parameter 'return_value_used'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'zif_monetdb_query':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:862:
warning: unused parameter 'this_ptr'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:862:
warning: unused parameter 'return_value_used'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'php_monetdb_get_result_info':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1283:
warning: unused parameter 'this_ptr'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1283:
warning: unused parameter 'return_value_used'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'zif_monetdb_last_notice':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1340:
warning: unused parameter 'this_ptr'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1340:
warning: unused parameter 'return_value_used'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'php_monetdb_get_field_info':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1367:
warning: unused parameter 'this_ptr'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1367:
warning: unused parameter 'return_value_used'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'zif_monetdb_field_num':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1438:
warning: unused parameter 'this_ptr'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1438:
warning: unused parameter 'return_value_used'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'zif_monetdb_fetch_result':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1469:
warning: unused parameter 'this_ptr'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1469:
warning: unused parameter 'return_value_used'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'php_monetdb_fetch_hash':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1571:
error: incompatible types in assignment
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1571:
warning: statement with no effect
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1573:
warning: implicit declaration of function
'zend_fetch_class'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1573:
error: 'ZEND_FETCH_CLASS_AUTO' undeclared (first use in
this function)
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1573:
error: (Each undeclared identifier is reported only once
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1573:
error: for each function it appears in.)
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1573:
warning: assignment makes pointer from integer without
a cast
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1670:
error: 'zend_fcall_info' undeclared (first use in this
function)
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1670:
error: parse error before 'fci'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1671:
error: 'zend_fcall_info_cache' undeclared (first use in
this function)
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1675:
warning: implicit declaration of function
'zend_merge_properties'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1677:
error: 'struct _zend_class_entry' has no member named
'constructor'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1678:
error: 'fci' undeclared (first use in this function)
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1678:
error: request for member 'size' in something not a
structure or union
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1678:
warning: statement with no effect
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1679:
error: request for member 'function_table' in something
not a structure or
union/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1679:
warning: statement with no effect
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1680:
error: request for member 'function_name' in something
not a structure or union
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1680:
warning: statement with no effect
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1681:
error: request for member 'symbol_table' in something
not a structure or union
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1681:
warning: statement with no effect
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1682:
error: request for member 'object_pp' in something not
a structure or union
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1682:
warning: statement with no effect
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1683:
error: request for member 'retval_ptr_ptr' in something
not a structure or
union/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1683:
warning: statement with no effect
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1689:
error: request for member 'param_count' in something
not a structure or union
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1689:
warning: statement with no effect
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1690:
error: request for member 'params' in something not a
structure or union
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1690:
warning: statement with no effect
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1693:
error: request for member 'params' in something not a
structure or union
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1693:
error: request for member 'param_count' in something
not a structure or union
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1693:
error: wrong type argument to increment
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1693:
error: array subscript is not an integer
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1693:
warning: statement with no effect
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1704:
warning: implicit declaration of function
'zend_throw_exception'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1704:
warning: implicit declaration of function
'zend_exception_get_default'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1708:
error: request for member 'param_count' in something
not a structure or union
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1708:
warning: statement with no effect
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1709:
error: request for member 'params' in something not a
structure or union
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1709:
warning: statement with no effect
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1711:
error: request for member 'no_separation' in something
not a structure or union
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1711:
warning: statement with no effect
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1713:
error: 'fcc' undeclared (first use in this function)
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1713:
error: request for member 'initialized' in something
not a structure or union
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1713:
warning: statement with no effect
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1714:
error: request for member 'function_handler' in
something not a structure or union
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1714:
error: 'struct _zend_class_entry' has no member named
'constructor'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1714:
warning: statement with no effect
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1715:
error: request for member 'calling_scope' in something
not a structure or union
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1715:
error: 'zend_executor_globals' has no member named 'scope'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1715:
warning: statement with no effect
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1716:
error: request for member 'object_pp' in something not
a structure or union
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1716:
warning: statement with no effect
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1718:
warning: implicit declaration of function
'zend_call_function'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1719:
warning: implicit declaration of function
'zend_throw_exception_ex'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1719:
error: 'struct _zend_class_entry' has no member named
'constructor'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1719:
error: 'struct _zend_ini_entry' has no member named
'common'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1719:
error: request for member 'function_name' in something
not a structure or union
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1725:
error: request for member 'params' in something not a
structure or union
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1726:
error: request for member 'params' in something not a
structure or union
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1551:
warning: unused parameter 'this_ptr'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1551:
warning: unused parameter 'return_value_used'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'zif_monetdb_result_seek':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1775:
warning: unused parameter 'this_ptr'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1775:
warning: unused parameter 'return_value_used'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'php_monetdb_data_info':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1802:
warning: unused parameter 'this_ptr'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1802:
warning: unused parameter 'return_value_used'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'zif_monetdb_free_result':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1902:
warning: unused parameter 'this_ptr'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1902:
warning: unused parameter 'return_value_used'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'zif_monetdb_escape_string':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1922:
warning: unused parameter 'this_ptr'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1922:
warning: unused parameter 'return_value_used'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'zif_monetdb_connection_status':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1942:
warning: unused parameter 'this_ptr'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1942:
warning: unused parameter 'return_value_used'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:
In function 'zif_monetdb_connection_reset':
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1961:
warning: unused parameter 'this_ptr'
/var/tmp/monet.GNU.32.32.d.17344/MonetDB/src/mapi/clients/php/Cimpl/php_monetdb.c:1961:
warning: unused parameter 'return_value_used'
make[12]: *** [php_monetdb.lo] Error 1
make[11]: *** [all-recursive] Error 1
make[10]: *** [all] Error 2
make[9]: *** [all-recursive] Error 1
make[8]: *** [all] Error 2
make[7]: *** [all-recursive] Error 1
make[6]: *** [all] Error 2
make[5]: *** [all-recursive] Error 1
make[4]: *** [all] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
## Comment 5400
Date: 2006-06-01 09:34:02 +0200
From: @grobian
Logged In: YES
user_id=963970
Configure should be changed such that it requires >=PHP5.
We decided to (just like the PHP team) not support older
versions of PHP any more, because it clutters the
implementation a lot (and takes a lot of maintenance).
## Comment 5401
Date: 2006-06-01 09:36:45 +0200
From: @drstmane
Logged In: YES
user_id=572415
fine with me.
please feel free to change connfigure requirements accordingly
(ask Sjoerd and/or Niels for help, if necessary).
## Comment 5402
Date: 2006-06-03 07:53:41 +0200
From: @drstmane
Logged In: YES
user_id=572415
Thanks to Niels, configure now checks for the
proper/required version of php, and skips the compilation of
src/mapi/clients/php otherwise.
## Comment 5403
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1498666 at http://sourceforge.net/support/tracker.php?aid=1498666
| php_monetdb.c fails to compile on Darwin | https://api.github.com/repos/MonetDB/MonetDB/issues/942/comments | 0 | 2020-11-30T09:07:18Z | 2024-06-28T13:33:39Z | https://github.com/MonetDB/MonetDB/issues/942 | 753,294,920 | 942 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-31 04:12:10 +0200
From: @MarcinZukowski
To: @sjoerdmullender
Version: -- development
Last updated: 2007-11-30 04:20:05 +0100
## Comment 5390
Date: 2006-05-31 16:12:10 +0200
From: @MarcinZukowski
Mapi seems to leak memory used to store header
information (column/type names).
I modified smack00.c to print a bat instead of a number:
snprintf(buf, 40, "print(new(int,int));");
so the header is added, and here's the trace after
10000 runs:
120,000 bytes in 40,000 blocks are definitely lost in
loss record 4 of
at 0x4904A66: malloc (vg_replace_malloc.c:149)
by 0x4A152A3: unquote (Mapi.mx:3850)
by 0x4A11A29: slice_row (Mapi.mx:2813)
by 0x4A1245E: parse_header_line (Mapi.mx:3008)
by 0x4A12B61: read_into_cache (Mapi.mx:3135)
by 0x4A135B5: mapi_execute_internal (Mapi.mx:3289)
by 0x4A13811: mapi_query (Mapi.mx:3326)
by 0x400C8F: main (smack00.c:67)
It is a bit important wrt our coming Terabyte TREC
experiments, as we run tens of thousands of queries.
## Comment 5391
Date: 2006-05-31 17:08:34 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
I checked in a fix. Can you recheck?
## Comment 5392
Date: 2006-06-08 14:39:54 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
I reran the experiments with 100K print(new(int,int)) queries.
The original error disappeared, but there are still some
leaks that seem related to SSL (?), see attached leak-client.
On the server side some memory might be lost as well, see
leak-server.
But it seems there are no leaks that increase with the
number of queries, which at least is a good thing.
I will check with an increasing number of connections now.
## Comment 5393
Date: 2006-06-08 14:46:27 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
In smack01 (modified with "print(new(int,int))") there are
still leaks related to the number of connections.
2K runs, see attached smack01-client
59,970 bytes in 7,996 blocks are indirectly lost in loss
record 6 of 9
at 0x4904A66: malloc (vg_replace_malloc.c:149)
by 0x334C8724B1: strdup (in /lib64/libc-2.3.6.so)
by 0x4A0DFEF: mapi_mapi (Mapi.mx:1754)
by 0x4A0F83E: mapi_connect (Mapi.mx:2189)
by 0x400C85: main (smack01.c:58)
32,992,047 (415,792 direct, 32,576,255 indirect) bytes in
1,999 blocks
are definitely lost in loss record 8 of 9
at 0x4904A66: malloc (vg_replace_malloc.c:149)
by 0x4A0DDBC: mapi_new (Mapi.mx:1697)
by 0x4A0DFBA: mapi_mapi (Mapi.mx:1748)
by 0x4A0F83E: mapi_connect (Mapi.mx:2189)
by 0x400C85: main (smack01.c:58)
32,516,285 bytes in 1,985 blocks are indirectly lost in loss
record 9
of 9
at 0x4905EC2: realloc (vg_replace_malloc.c:306)
by 0x4A11D49: read_line (Mapi.mx:2716)
by 0x4A1347A: read_into_cache (Mapi.mx:3108)
by 0x4A14070: mapi_execute_internal (Mapi.mx:3303)
by 0x4A142CC: mapi_query (Mapi.mx:3340)
by 0x400D9F: main (smack01.c:70)
## Comment 5394
Date: 2006-06-08 15:03:50 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
I fixed a leak in smack01: it disconnected and then
discarded the Mapi structure, but discarding is not freeing.
We now reuse the Mapi structure in the loop, merely
reconnecting and disconnecting in each iteration.
## Comment 5395
Date: 2006-06-19 16:00:26 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Closing since I think the bugs are fixed.
Not adding a test since we don't have any tests that test
for memory leaks.
## Comment 5396
Date: 2006-11-29 11:07:59 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Marked as pending to jon the club of missing memory related tests.
## Comment 5397
Date: 2007-11-30 04:20:05 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 365 days (the time period specified by
the administrator of this Tracker).
## Comment 5398
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1498247 at http://sourceforge.net/support/tracker.php?aid=1498247
| Mapi leak | https://api.github.com/repos/MonetDB/MonetDB/issues/941/comments | 0 | 2020-11-30T09:07:15Z | 2024-06-27T11:10:23Z | https://github.com/MonetDB/MonetDB/issues/941 | 753,294,891 | 941 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-30 11:40:09 +0200
From: @Teggy
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-01-13 01:51:09 +0100
## Comment 5383
Date: 2006-05-30 11:40:09 +0200
From: @Teggy
Hi all,
compiling
let $a := <a/>
let $b := attribute b { "b" }
return
$a union $b
using the algebraic code generator yields
fatal error: sort criterion for rownum must be
monomorphic, type: 3840, name: item
halted in ... /pf/compiler/algebra/logical.c
(PFla_rownum), line 1387
Greetings,
--Teggy
## Comment 5384
Date: 2006-11-05 16:44:20 +0100
From: @drstmane
Logged In: YES
user_id=572415
tests added in
pathfinder/tests/BugTracker/Tests/polymorphic_sequences.SF-1497419.(mps,alg}.*
milprint_summer (mps) version works fine
algebra (alg) version fails as reported
## Comment 5385
Date: 2007-02-19 16:29:19 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Algebra -> Jan
## Comment 5386
Date: 2007-06-05 22:35:30 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Lowered priority of algebra bug for this release.
The algebra version will be subject of the next release.
## Comment 5387
Date: 2008-01-12 13:53:16 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
According to nightly testing, the respective test seems to have been working fine since Dec 6 2007 --- fixed intensionally or "by coincidence"?
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.32.d-Fedora6/tests_BugTracker/polymorphic_sequences.SF-1497419.alg.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.32.d-Fedora6/tests_BugTracker/polymorphic_sequences.SF-1497419.alg.err.00.html
In any case, time to check/close this one?
## Comment 5388
Date: 2008-01-13 13:51:09 +0100
From: @Teggy
Logged In: YES
user_id=642632
Originator: YES
Yes, this particular bug may be closed — the issue is still relevant for the SQL back-end where the input produces an
Assertion failed: (monomorphic (pos_ty)), function reduce, file /Users/grust/sci/XQuery/Pathfinder/pathfinder/compiler/sql/lalg2sql.brg, line 1756.
I'll re-open another bug particularly for the SQL issue.
Cheers,
--Teggy
## Comment 5389
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1497419 at http://sourceforge.net/support/tracker.php?aid=1497419
| PF: Algebra trips over polymorphic sequences | https://api.github.com/repos/MonetDB/MonetDB/issues/940/comments | 0 | 2020-11-30T09:07:12Z | 2024-06-27T11:10:22Z | https://github.com/MonetDB/MonetDB/issues/940 | 753,294,856 | 940 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-29 11:19:09 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Jens Teubner <<teubner>>
Version: -- development
Last updated: 2006-07-25 05:51:34 +0200
## Comment 5380
Date: 2006-05-29 11:19:09 +0200
From: Jan Rittinger <<jan.rittinger>>
In the current implementation the special namespace
prefixes 'xml' and 'xmlns' can be redeclared while this
is not allowed.
see:
http://www.w3.org/TR/2004/REC-xml-names11-20040204/xmlReserved
Probably two places are affected:
* the 'declare namespace' statement which can be
checked at compile time
e.g.:
declare namespace xml ="foo"; <xml:a/>
* the attribute constructor whose misuse has to be
checked at runtime
e.g.:
for $a in ("xmlns:xml", "xmlns:xmlns")
return <a>{ attribute {$a} {"foo"}}</a>
The former should be no problem to fix (at namespace
resolution?) while the latter one is probably a little
bit trickier (runtime check during attribute
construction?).
## Comment 5381
Date: 2006-07-25 17:51:34 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Fixed in CVS. Test cases added.
## Comment 5382
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1496781 at http://sourceforge.net/support/tracker.php?aid=1496781
| PF: 'xmlns' and 'xml' qname prefixes can be redeclared. | https://api.github.com/repos/MonetDB/MonetDB/issues/939/comments | 0 | 2020-11-30T09:07:08Z | 2024-06-27T11:10:21Z | https://github.com/MonetDB/MonetDB/issues/939 | 753,294,806 | 939 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-27 11:20:33 +0200
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-06-03 09:18:48 +0200
## Comment 5374
Date: 2006-05-27 23:20:33 +0200
From: @drstmane
Changes in pathfinder and/or MonetDB on Monday May 22,
Tuesday May 23, and/or Wednesday May 24 caused 309
pathfinder tests to fail; see list below and
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/index_short.html
for details.
On the respective days, the following developers did
check-in to pathfinder and/or MonetDB:
pathfinder:
Peter (boncz), Sjoerd, Jens (teubner), Henning (hrode),
JanF (jflokstra), JanR (tsheyar)
MonetDB:
Peter (boncz), Sjoerd, Fabian (mr-meltdown), Niels
(nielsnes)
Old file: Mtest10..2006.05.22_00-02-01..out.
New file: Mtest10..2006.05.25_00-02-02..out.
============================================
309 Tests are WORSE than before:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
runtime/descendant
runtime/descendant-or-self
runtime/ancestor
runtime/ancestor-or-self
runtime/child
runtime/parent
runtime/following
runtime/preceding
runtime/following-sibling
runtime/preceding-sibling
tests/BugTracker/wrong_BATpropcheck_on_void_void_BATs.SF-1397840-d0
tests/BugTracker/wrong_BATpropcheck_on_void_void_BATs.SF-1397840-d10
tests/BugTracker/SCJ_with_void_void_BATs.SF-1400473
tests/BugsViaSourgeforce/ID.1078462_run
tests/BugsViaSourgeforce/ID.1204965-d_run
tests/BugsViaSourgeforce/ID.1207090-1
tests/BugsViaSourgeforce/ID.1207090-2
tests/BugsViaSourgeforce/ID.1207090-3
tests/BugsViaSourgeforce/ID.1207090-4
tests/BugsViaSourgeforce/ID.1207090-5
tests/BugsViaSourgeforce/ID.1207090-6
tests/BugsViaSourgeforce/ID.1207090-7
tests/BugsViaSourgeforce/ID.1207096-1
tests/BugsViaSourgeforce/ID.1207096-2
tests/BugsViaSourgeforce/ID.1207096-3
tests/BugsViaSourgeforce/ID.1207096-4
tests/BugsViaSourgeforce/ID.1207112_run
tests/BugsViaSourgeforce/ID.1210173-1
tests/BugsViaSourgeforce/ID.1210173-2
tests/BugsViaSourgeforce/ID.1244326
tests/BugsViaSourgeforce/ID.1292727.col_name-segfault.run
tests/BugsViaSourgeforce/making_void-void_BAT_appendable.SF-1340615
tests/BugsViaSourgeforce/making_void-void_BAT_writable.SF-1353017
tests/Music/full_01
tests/Music/full_02
tests/Music/full_03
tests/Music/full_04
tests/Music/full_05
tests/Music/full_06
tests/Music/limit_01
tests/Music/limit_02
tests/Music/limit_03
tests/Music/limit_04
tests/Music/limit_05
tests/Music/limit_06
tests/Music/mod/MIL/full_01
tests/Music/mod/MIL/full_02
tests/Music/mod/MIL/full_03
tests/Music/mod/MIL/full_04
tests/Music/mod/MIL/full_05
tests/Music/mod/MIL/full_06
tests/Music/mod/MIL/limit_01
tests/Music/mod/MIL/limit_02
tests/Music/mod/MIL/limit_03
tests/Music/mod/MIL/limit_04
tests/Music/mod/MIL/limit_05
tests/Music/mod/MIL/limit_06
tests/Music/mod/XQ/full_01
tests/Music/mod/XQ/full_02
tests/Music/mod/XQ/full_03
tests/Music/mod/XQ/full_04
tests/Music/mod/XQ/full_05
tests/Music/mod/XQ/full_06
tests/Music/mod/XQ/limit_01
tests/Music/mod/XQ/limit_02
tests/Music/mod/XQ/limit_03
tests/Music/mod/XQ/limit_04
tests/Music/mod/XQ/limit_05
tests/Music/mod/XQ/limit_06
tests/Music/opt/MIL/full_01
tests/Music/opt/MIL/full_02
tests/Music/opt/MIL/full_03
tests/Music/opt/MIL/full_04
tests/Music/opt/MIL/full_05
tests/Music/opt/MIL/full_06
tests/Music/opt/MIL/limit_01
tests/Music/opt/MIL/limit_02
tests/Music/opt/MIL/limit_03
tests/Music/opt/MIL/limit_04
tests/Music/opt/MIL/limit_05
tests/Music/opt/MIL/limit_06
tests/Music/opt/XQ/full_01
tests/Music/opt/XQ/full_02
tests/Music/opt/XQ/full_03
tests/Music/opt/XQ/full_04
tests/Music/opt/XQ/full_05
tests/Music/opt/XQ/full_06
tests/Music/opt/XQ/limit_01
tests/Music/opt/XQ/limit_02
tests/Music/opt/XQ/limit_03
tests/Music/opt/XQ/limit_04
tests/Music/opt/XQ/limit_05
tests/Music/opt/XQ/limit_06
tests/Update/insert-1
tests/Update/insert-2
tests/Update/symm-test-2
tests/Update/symm-test-3
tests/Update/symm-test-4
tests/Update/symm-test-5
tests/Update/update
tests/WebSite/voc1
tests/WebSite/voc2
tests/WebSite/voc3
tests/WebSite/voc4
tests/WebSite/voc5
tests/WebSite/distinct_values_bug.SF-1210748
tests/XMark/q01
tests/XMark/q02
tests/XMark/q03
tests/XMark/q04
tests/XMark/q05
tests/XMark/q06
tests/XMark/q07
tests/XMark/q08
tests/XMark/q09
tests/XMark/q10
tests/XMark/q11
tests/XMark/q12
tests/XMark/q13
tests/XMark/q14
tests/XMark/q15
tests/XMark/q16
tests/XMark/q17
tests/XMark/q18
tests/XMark/q19
tests/XMark/q20
tests/XMark/upd
tests/XMark/alg/q01
tests/XMark/alg/q02
tests/XMark/alg/q03
tests/XMark/alg/q04
tests/XMark/alg/q05
tests/XMark/alg/q06
tests/XMark/alg/q07
tests/XMark/alg/q08
tests/XMark/alg/q09
tests/XMark/alg/q10
tests/XMark/alg/q11
tests/XMark/alg/q12
tests/XMark/alg/q13
tests/XMark/alg/q14
tests/XMark/alg/q15
tests/XMark/alg/q16
tests/XMark/alg/q17
tests/XMark/alg/q18
tests/XMark/alg/q19
tests/XMark/alg/q20
tests/XMark/alg/upd
tests/XMark/mod/MIL/q01
tests/XMark/mod/MIL/q02
tests/XMark/mod/MIL/q03
tests/XMark/mod/MIL/q04
tests/XMark/mod/MIL/q05
tests/XMark/mod/MIL/q06
tests/XMark/mod/MIL/q07
tests/XMark/mod/MIL/q08
tests/XMark/mod/MIL/q09
tests/XMark/mod/MIL/q10
tests/XMark/mod/MIL/q11
tests/XMark/mod/MIL/q12
tests/XMark/mod/MIL/q13
tests/XMark/mod/MIL/q14
tests/XMark/mod/MIL/q15
tests/XMark/mod/MIL/q16
tests/XMark/mod/MIL/q17
tests/XMark/mod/MIL/q18
tests/XMark/mod/MIL/q19
tests/XMark/mod/MIL/q20
tests/XMark/mod/XQ/q01
tests/XMark/mod/XQ/q02
tests/XMark/mod/XQ/q03
tests/XMark/mod/XQ/q04
tests/XMark/mod/XQ/q05
tests/XMark/mod/XQ/q06
tests/XMark/mod/XQ/q07
tests/XMark/mod/XQ/q08
tests/XMark/mod/XQ/q09
tests/XMark/mod/XQ/q10
tests/XMark/mod/XQ/q11
tests/XMark/mod/XQ/q12
tests/XMark/mod/XQ/q13
tests/XMark/mod/XQ/q14
tests/XMark/mod/XQ/q15
tests/XMark/mod/XQ/q16
tests/XMark/mod/XQ/q17
tests/XMark/mod/XQ/q18
tests/XMark/mod/XQ/q19
tests/XMark/mod/XQ/q20
tests/XMark/opt/MIL/q01
tests/XMark/opt/MIL/q02
tests/XMark/opt/MIL/q03
tests/XMark/opt/MIL/q04
tests/XMark/opt/MIL/q05
tests/XMark/opt/MIL/q06
tests/XMark/opt/MIL/q07
tests/XMark/opt/MIL/q08
tests/XMark/opt/MIL/q09
tests/XMark/opt/MIL/q10
tests/XMark/opt/MIL/q11
tests/XMark/opt/MIL/q12
tests/XMark/opt/MIL/q13
tests/XMark/opt/MIL/q14
tests/XMark/opt/MIL/q15
tests/XMark/opt/MIL/q16
tests/XMark/opt/MIL/q17
tests/XMark/opt/MIL/q18
tests/XMark/opt/MIL/q19
tests/XMark/opt/MIL/q20
tests/XMark/opt/XQ/q01
tests/XMark/opt/XQ/q02
tests/XMark/opt/XQ/q03
tests/XMark/opt/XQ/q04
tests/XMark/opt/XQ/q05
tests/XMark/opt/XQ/q06
tests/XMark/opt/XQ/q07
tests/XMark/opt/XQ/q08
tests/XMark/opt/XQ/q09
tests/XMark/opt/XQ/q10
tests/XMark/opt/XQ/q11
tests/XMark/opt/XQ/q12
tests/XMark/opt/XQ/q13
tests/XMark/opt/XQ/q14
tests/XMark/opt/XQ/q15
tests/XMark/opt/XQ/q16
tests/XMark/opt/XQ/q17
tests/XMark/opt/XQ/q18
tests/XMark/opt/XQ/q19
tests/XMark/opt/XQ/q20
tests/XPath/q01
tests/XPath/q02
tests/XPath/q03
tests/XPath/q04
tests/XPath/q05
tests/XPath/q06
tests/XPath/q07
tests/XPath/q08
tests/XPath/q09
tests/XPath/q10
tests/XPath/q11
tests/XPath/q12
tests/XPath/q13
tests/XPath/q14
tests/XPath/q15
tests/XPath/q16
tests/XPath/q17
tests/XPath/q18
tests/XPath/q19
tests/XPath/q20
tests/XPath/q21
tests/XPath/q22
tests/XPath/q23
tests/XPath/q24
tests/XPathMark/Q1
tests/XPathMark/Q2
tests/XPathMark/Q3
tests/XPathMark/Q4
tests/XPathMark/Q5
tests/XPathMark/Q6
tests/XPathMark/Q7
tests/XPathMark/Q8
tests/XPathMark/Q9
tests/XPathMark/Q10
tests/XPathMark/Q11
tests/XPathMark/Q12
tests/XPathMark/Q13
tests/XPathMark/Q15
tests/XPathMark/Q16
tests/XPathMark/Q17
tests/XPathMark/Q18
tests/XPathMark/Q19
tests/XPathMark/Q20
tests/XPathMark/Q21
tests/XPathMark/Q22
tests/XPathMark/Q23
tests/XPathMark/Q24
tests/XPathMark/Q25
tests/XPathMark/Q26
tests/XPathMark/Q27
tests/XPathMark/Q28
tests/XPathMark/Q29
tests/XPathMark/Q30
tests/XPathMark/Q31
tests/XPathMark/Q32
tests/XPathMark/Q33
tests/XPathMark/Q34
tests/XPathMark/Q36
tests/XPathMark/Q37
tests/XPathMark/Q38
tests/XPathMark/Q39
tests/XPathMark/Q40
tests/XPathMark/Q41
tests/XPathMark/Q42
tests/XPathMark/Q43
tests/XPathMark/Q44
tests/XPathMark/Q45
tests/XPathMark/Q46
tests/XPathMark/Q47
tests/XPathMark/A1
tests/XPathMark/A2
tests/XPathMark/A5
tests/XPathMark/A8
tests/XPathMark/A9
tests/XPathMark/A10
tests/XPathMark/A11
tests/XQuery/orderby4
tests/XQuery/orderby5
tests/XQuery/orderby6
tests/XQuery/orderby7
tests/XQuery/orderby8
## Comment 5375
Date: 2006-06-01 09:22:29 +0200
From: @drstmane
Logged In: YES
user_id=572415
For further analysis, please find attached the cvs checkin
messages of May 22-24 2006 for both MonetDB and pathfinder.
## Comment 5376
Date: 2006-06-02 08:53:39 +0200
From: @drstmane
Logged In: YES
user_id=572415
Just for the bookkeeping and to (hopefully) simplify debugging:
Changes to MonetDB and/or pathfinder between May 25 and May
31 caused 61 more pathfinder tests to fail; cf., attached
"PFdiff_2006.05.25-06.01" for details.
## Comment 5377
Date: 2006-06-02 08:56:45 +0200
From: @drstmane
Logged In: YES
user_id=572415
Just for the bookkeeping and to (hopefully) simplify debugging:
Changes to MonetDB and/or pathfinder on June 1 caused 150
more pathfinder tests to fail; cf., attached
"PFdiff_2006.06.01-02" for details.
## Comment 5378
Date: 2006-06-03 09:18:47 +0200
From: @drstmane
Logged In: YES
user_id=572415
Most problems have been fixed by yesterday's checkins.
Thank you all!
I'll document the remaining open problems in new/separate
bug reports. Stay tuned...
## Comment 5379
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1496159 at http://sourceforge.net/support/tracker.php?aid=1496159
| PF: 309 tests fail after recent changes | https://api.github.com/repos/MonetDB/MonetDB/issues/938/comments | 0 | 2020-11-30T09:07:06Z | 2024-06-27T11:10:20Z | https://github.com/MonetDB/MonetDB/issues/938 | 753,294,768 | 938 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-27 08:28:53 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2006-05-28 12:01:28 +0200
## Comment 5371
Date: 2006-05-27 20:28:53 +0200
From: @drstmane
After the changes of Thursday May 25 2006, test
tests/from_Twente/moa/Tests/list.milM fails with
!WARNING: BATpropcheck: BAT tmp_175 was incorrectly
marked keyed!
see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests103/GNU.64.64.d-Fedora4/tests_from_Twente_moa/list.out.00.html
for details.
## Comment 5372
Date: 2006-05-28 12:01:28 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed, the BBPrecycle routine now resets the head and tail
COLrecords (they pointed sometimes to each other, giving
these problems when these bats got reused)
## Comment 5373
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1496099 at http://sourceforge.net/support/tracker.php?aid=1496099
| tests/from_Twente/moa/Tests/list.milM fails with prop. error | https://api.github.com/repos/MonetDB/MonetDB/issues/937/comments | 0 | 2020-11-30T09:07:02Z | 2024-06-27T11:10:19Z | https://github.com/MonetDB/MonetDB/issues/937 | 753,294,719 | 937 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-27 08:22:20 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2006-05-28 12:02:29 +0200
## Comment 5368
Date: 2006-05-27 20:22:20 +0200
From: @drstmane
After the changes of Thursday May 25 2006, test
src/monet/Tests/setaggr_exist.milM fails with
!WARNING: BATpropcheck: BAT tmp_32 was incorrectly
marked sorted!
!WARNING: BATpropcheck: BAT tmp_32 remains marked
radix-clustered on 32 bits; not checked!
possibly in reverse() or accbuild("hash") .
see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests103/GNU.64.64.d-Fedora4/src_monet/setaggr_exist.out.00.html
for details.
## Comment 5369
Date: 2006-05-28 12:02:28 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed, BBPrecycle now resets the COLrecords (sometimes they
pointed to each other, giving problems on reuse)
## Comment 5370
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1496098 at http://sourceforge.net/support/tracker.php?aid=1496098
| src/monet/Tests/setaggr_exist.milM fails with property error | https://api.github.com/repos/MonetDB/MonetDB/issues/936/comments | 0 | 2020-11-30T09:07:00Z | 2024-06-27T11:10:18Z | https://github.com/MonetDB/MonetDB/issues/936 | 753,294,685 | 936 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-27 08:17:25 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2006-05-28 10:52:55 +0200
## Comment 5365
Date: 2006-05-27 20:17:25 +0200
From: @drstmane
After the changes of Thursday May 25 2006, test
src/modules/plain/decimal.milM fails with a segfault,
possibly in sort().
See
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests103/GNU.64.64.d-Fedora4/src_modules_plain/decimal.out.00.html
for details.
## Comment 5366
Date: 2006-05-28 10:52:55 +0200
From: @njnes
Logged In: YES
user_id=43556
Fixed, the recycled bat had an incorrect hheap/theap
## Comment 5367
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1496095 at http://sourceforge.net/support/tracker.php?aid=1496095
| src/modules/plain/Tests/decimal.milM fails with segfault | https://api.github.com/repos/MonetDB/MonetDB/issues/935/comments | 0 | 2020-11-30T09:06:57Z | 2024-06-27T11:10:17Z | https://github.com/MonetDB/MonetDB/issues/935 | 753,294,648 | 935 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-24 02:47:16 +0200
From: @Teggy
To: Torsten Grust <<teggy>>
Version: -- development
Last updated: 2007-06-04 08:33:57 +0200
## Comment 5356
Date: 2006-05-24 14:47:16 +0200
From: @Teggy
Hi guys,
is the following supposed to work (the question
relates to any non-uniform mix of oid/void types in the
argument BATs)?
var t1;
var t2;
t1 := new (oid, oid);
t2 := new (oid, void);
t1.sintersect (t2);
It currently leads to:
!ERROR: interpret: no matching MIL operator to
'sintersect(BAT[oid,oid], BAT[oid,void])'.
!MAYBE YOU MEAN:
! sintersect(BAT[any::1,any::2],
BAT[any::1,any::2]) : BAT[any::1,any::2]
In an ideal world, we would like to not materialize the
BATs before the sintersect().
Cheers,
--Teggy
## Comment 5357
Date: 2006-05-24 15:54:07 +0200
From: @grobian
Logged In: YES
user_id=963970
(According to Niels, playing proxy here)
This is a valid error. oid != void. You have to set the
seqbase/mark on the void column before you can intersect them.
## Comment 5358
Date: 2006-05-24 16:40:55 +0200
From: @Teggy
Logged In: YES
user_id=642632
Hi Fabina (and Niels),
thanks for your immediate reply. I guess I have to be
more specific here -- my first posting was too vague. Sorry
for that.
Consider:
var a0, a1, a2;
a0 := new (void,void).seqbase (0@0).reverse ().seqbase (0@0);
a1 := new (void,void).seqbase (0@0).reverse ().seqbase (0@0);
a2 := a0.sintersect(a1);
That is, we're working with void|void BATs here, all of them
seqbased. The first sintersect() works fine, yielding a BAT
of type oid|void which is then bound to variable a2. Note
that the void column of a2 has *no* seqbase now. (By the
way, it is unclear to me why one column comes out oid, the
other void.)
Is this considered the correct behavior?
Greetings,
--Teggy
## Comment 5359
Date: 2006-05-24 17:02:47 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
sintersect and friends (kintersect, sdiff, kdiff) should set
the seqbase.
## Comment 5360
Date: 2006-05-28 11:19:56 +0200
From: @njnes
Logged In: YES
user_id=43556
added test in tests/BugTracker/Tests/sintersect_on_void_bats
The test however doesn't fail..
## Comment 5361
Date: 2006-11-05 16:33:04 +0100
From: @drstmane
Logged In: YES
user_id=572415
extended test to also check, whether sintersect set the
seqbase without property checking.
it does.
can this bug report be closed, now?
## Comment 5362
Date: 2007-02-19 16:31:27 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Teggy, can this bug be closed?
## Comment 5363
Date: 2007-06-04 20:33:57 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Closing as the respective test apparently has been working for quite some time, now:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/sintersect_on_void_bats.SF-1494263.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB4/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/sintersect_on_void_bats.SF-1494263.out.00.html
Teggy,
please feel free to re-open in case you don't agree.
Stefan.
## Comment 5364
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1494263 at http://sourceforge.net/support/tracker.php?aid=1494263
| MIL: sintersect() and non-uniform BAT arguments | https://api.github.com/repos/MonetDB/MonetDB/issues/934/comments | 0 | 2020-11-30T09:06:53Z | 2024-06-28T13:33:39Z | https://github.com/MonetDB/MonetDB/issues/934 | 753,294,611 | 934 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-19 06:29:24 +0200
From: Henning Rode <<hrode>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2006-06-14 04:42:33 +0200
## Comment 5351
Date: 2006-05-19 18:29:24 +0200
From: Henning Rode <<hrode>>
when using a predicate like [fn:position() < 10] on a
sequence, the position numbering of the items in the
sequence gets incorrect...
query:
let $x := (2,3)
let $y := (10,20)[fn:position() < 10]
for $i at $rank in $y
return <item> {$rank} - {$i} - {$x[$rank]} </item>
buggy pathfinder result:
<item>1 - 10 - 2</item><item>1 - 20 - 2</item>
correct result:
<item>1 - 10 - 2</item><item>2 - 20 - 3</item>
## Comment 5352
Date: 2006-06-14 00:06:34 +0200
From: @peterboncz
Logged In: YES
user_id=591107
I quickly looked at this problem.
the conditional $x[$rank] is translated with a thetajoin.
however, the values for $rank that o into it are already
wrong (i.e. $rank = 1 in both iterations).
I backtracked it in the generated MIL to the line 'ints_cE
:= tmark_grp_unique(outer002,outer002)' where these wrong
values appear to be generated.
maybe the second argument is wrong there.
this is for Jan Rittinger
## Comment 5353
Date: 2006-06-14 16:42:32 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
It is now fixed. A simplification was applied that is only
allowed if the positional predicate is missing.
8876a8877,8880
>
> NOTE: We have to ensure that the outer
iteration has no
> positional variable - it would get
screwed up by
> the nesting.
8878c8882
< if (LR(c)->kind == c_for)
---
> if (LR(c)->kind == c_for && LLR(c)->kind != c_var)
Peter - could you please apply it to the release branch.
## Comment 5354
Date: 2006-06-20 10:15:09 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
test added
## Comment 5355
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1491723 at http://sourceforge.net/support/tracker.php?aid=1491723
| wrong position numbering in sequence after predicate | https://api.github.com/repos/MonetDB/MonetDB/issues/933/comments | 0 | 2020-11-30T09:06:50Z | 2024-06-27T11:10:15Z | https://github.com/MonetDB/MonetDB/issues/933 | 753,294,573 | 933 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-18 01:32:32 +0200
From: Valentin Jijkoun <<jijkoun>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2006-05-18 10:42:21 +0200
## Comment 5346
Date: 2006-05-18 13:32:32 +0200
From: Valentin Jijkoun <<jijkoun>>
MonetDB on 32biti686-redhat-linux-gnu
Different behaviour when using a function (intenal db
error) and when inlining the function (normal query
results).
Attached: xml file. We use it for "burkowski" queries,
but this query does not use extended axes.
XQuery:
---------
declare function output-elt ($elt as xs:string, $node
as node()) as node() {
element { $elt } { $node/@xid }
};
for $np in doc("clef1.xml")//node[@cat="np"],
$name in $np/node[@pos="name"]
return
(: Works :)
(: <entry>
{ output-elt("np", $np) },
{ element {"name"} { $name/@xid } }
</entry>:)
(: Does not work :)
<entry>
{ output-elt("np", $np) },
{ output-elt("name", $name) },
</entry>
(: Produces error:
!ERROR: BATmalleftfetchjoin: Cannot perform
leftfetchjoin: right head is no dense OID column.
!ERROR: CMDleftfetchjoin: operation failed.
!ERROR: interpret_params: materialize(param 1):
evaluation error.
:)
------
## Comment 5347
Date: 2006-05-18 22:29:22 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
This bug is triggered by using a wrong variable. (The
original variable -- here 'attr_qn_cont' -- was used instead
of the new one 'attr_cont'. 'attr_cont' is a view of
'attr_qn_cont' with a modified seqbase. Thus calling the
element construction twice resulted in conflicting oids in
the working set container 'ATTR_CONT'.)
line 2812, compiler/mil/milprint_summer.c:
ws.fetch(ATTR_CONT).fetch(WS).insert(attr_qn_cont);
->
ws.fetch(ATTR_CONT).fetch(WS).insert(attr_cont);
## Comment 5348
Date: 2006-05-18 22:42:21 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
testweb says the fix is ok - so close the bug :)
## Comment 5349
Date: 2006-06-20 10:07:08 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
test added
## Comment 5350
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1490847 at http://sourceforge.net/support/tracker.php?aid=1490847
| problem with functions in xquery | https://api.github.com/repos/MonetDB/MonetDB/issues/932/comments | 0 | 2020-11-30T09:06:47Z | 2024-06-27T11:10:14Z | https://github.com/MonetDB/MonetDB/issues/932 | 753,294,544 | 932 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-17 02:52:05 +0200
From: Jan Rittinger <<jan.rittinger>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2006-06-01 03:29:17 +0200
## Comment 5343
Date: 2006-05-17 14:52:05 +0200
From: Jan Rittinger <<jan.rittinger>>
The following query is an example where two attributes
'at1' and 'at2' are generated with different uris but
equal prefixes:
let $b := <a xmlns:a="bar" a:at1="value"/>
return <c xmlns:a="foo" a:at2="other value">{ $b/@* }</c>
The current routine that introduces namespace
declarations does not check whether conflicts of
prefixes arise or not. That's why the result has two
conflicting namespace declarations 'xmlns:a':
<c xmlns:a="foo" a:at2="other value" xmlns:a="bar"
a:at1="value"/>
I would expect some renaming that is automatically done
by the serialization whenever a conflict arises (e.g.
renaming the second prefix from 'a' to 'pf0001'):
<c xmlns:a="foo" a:at2="other value" xmlns:pf0001="bar"
pf0001:at1="value"/>
## Comment 5344
Date: 2006-06-01 15:29:16 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
fixed (see test runtime/namespaces).
## Comment 5345
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1490231 at http://sourceforge.net/support/tracker.php?aid=1490231
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| PF: serialization prints conflicting namespace declaration | https://api.github.com/repos/MonetDB/MonetDB/issues/931/comments | 0 | 2020-11-30T09:06:44Z | 2024-06-27T11:10:13Z | https://github.com/MonetDB/MonetDB/issues/931 | 753,294,517 | 931 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-17 02:42:25 +0200
From: Jan Rittinger <<jan.rittinger>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2006-06-01 03:29:55 +0200
## Comment 5340
Date: 2006-05-17 14:42:25 +0200
From: Jan Rittinger <<jan.rittinger>>
I started with the example query:
let $a := <a/>
return <b xmlns="foo">{ $a }</b>
This query results in '<b xmlns="foo"><a/></b>', which
automatically assigns node 'b' the default element
namespace 'foo'.
If I query the same query with saxon I get
'<b xmlns="foo"><a xmlns=""/></b>'
as result. Here the namespace definition 'xmlns=""'
removes the default element namespace definition of
element 'a'. It thus does not automagically change the
namespace and returns the correct (and more consistent)
result.
Introducing an 'else' part of the command 'if (uri)' in
function checkNsChange of serialize.mx that handles
this case could solve this problem.
## Comment 5341
Date: 2006-06-01 15:29:54 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
fixed (see test runtime/namespaces).
## Comment 5342
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1490218 at http://sourceforge.net/support/tracker.php?aid=1490218
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| PF: serialization forgets some namespace definitions | https://api.github.com/repos/MonetDB/MonetDB/issues/930/comments | 0 | 2020-11-30T09:06:41Z | 2024-06-27T11:10:12Z | https://github.com/MonetDB/MonetDB/issues/930 | 753,294,487 | 930 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-17 02:09:35 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2006-12-06 06:00:28 +0100
## Comment 5332
Date: 2006-05-17 14:09:35 +0200
From: Jan Rittinger <<jan.rittinger>>
There is a difference between attributes and elements
in treating missing prefixes. While attributes without
prefix have no namespace (see
http://www.w3.org/TR/REC-xml-names/uniqAttrs),
elements without prefix get the default element
namespace (which is empty if not specified otherwise).
Our current shredding however assigns the default
element namespace also to attributes without prefix.
This result in wrong query results. In the example
below we would expect '<a/>' as result:
test.xml:
<z><a xmlns="foo" at3="foo"></z>
query:
declare namespace a = "foo";
<a>{ doc("test.xml")//@a:* }</a>
## Comment 5333
Date: 2006-05-17 14:23:14 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
I think it helps to complete the above sentence :)
We expect an empty a element '<a/>', because the attribute
at3 has no prefix and thus has no uri. In the current
shredder however the default element namespace uri is
provided for at3 (namely 'foo').
I think this could be fixed in line 1262 of shredder.mx, but
I'm not 100% sure.
## Comment 5334
Date: 2006-06-01 16:23:34 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
I do not really see what's special about line 1262 (the
a_pfx parameter decl) but I think you mean add a new line to
store_PfxLocNEW() which is:
if ( !a_pfx && a_uri)
a_uri = NULL;
This will nullify the uri parameter if no prefix is used.
But I do not understand the extend of the problem enough to
see if this would be the solution to your problem.
## Comment 5335
Date: 2006-06-01 22:19:27 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Sorry I should have specified the code snippet I was
referring to. I thought something like your proposol would
fix the bug.
After having a second look, however, I realized that the
code also is triggered for elements. Thus this fix is
probably infeasible.
I think the idea is as you wrote:
If there is an attribute whose prefix is empty, then we
delete its URI as well.
Probably the fix is then better located around line 1459:
'qn_id = store_PfxLocNEW(shredCtx,a_uri,a_pfx,a_tag);'
## Comment 5336
Date: 2006-06-02 08:39:58 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
I made the fix and it had the desired effect. I also think
around line 1459 is the right location. My only question
remains why libxml2 package would provide this 'default'
namespace if it is against the definition.
(Shall I check the fix in???)
## Comment 5337
Date: 2006-11-29 11:11:13 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Re-opened, as no test has been provided, yet.
User (submitter) and/or developer (assignee),
please supply a respective test,
or explain why a test is not required/possible.
## Comment 5338
Date: 2006-12-06 18:00:28 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: YES
Test added
tests/BugTracker/Tests/attr-ns.SF-1490200
## Comment 5339
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1490200 at http://sourceforge.net/support/tracker.php?aid=1490200
| PF: attributes without prefix have no namespace | https://api.github.com/repos/MonetDB/MonetDB/issues/929/comments | 0 | 2020-11-30T09:06:38Z | 2024-06-27T11:10:11Z | https://github.com/MonetDB/MonetDB/issues/929 | 753,294,444 | 929 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-17 12:04:24 +0200
From: Jan Rittinger <<jan.rittinger>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2006-08-15 07:13:49 +0200
## Comment 5327
Date: 2006-05-17 12:04:24 +0200
From: Jan Rittinger <<jan.rittinger>>
In the current version of the loop-lifted path steps
updates are handled by the mx macro 'no_pre' (line 1192
pf_support.mx).
A loop-lifted path step that has no candidate list
(probably only one with node test 'node()') generates a
new candidate list (for each step) that contains the
complete pre table without the deleted nodes (without
updates the complete pre table). Such large candidate
lists force the staircase join algorithm to look at all
pre values of the document and thus prohibit the
concept of skipping which makes staircase join
particularly efficient.
To give an idea: The path /node()/node() completely
scans the document relation 4 times (2 times for each
step) and skips 2 times over the document (1 time for
each step processing). I think the 4 sequential scans
are superfluous. A solution might be to check in
staircase join implementation for deleted nodes and
skip them.
In addition there exist path step implementations which
apply the filter expressions afterwards. These
implementations are totally unaware of holes in the pre
relations. (This did not result in wrong results as
this code is currently switched off.)
## Comment 5328
Date: 2006-08-15 19:13:49 +0200
From: @peterboncz
Logged In: YES
user_id=591107
bugfix [ 1490128 ] PF: inefficient handling of loop-lifted
path steps
=====================================================================
plus two more just-introduced bugs that mess up the test web:
- complaints in ll_scj about non OID candidate lists
- crashes when xquery() MIL queries cause errors
runtime/ll_staircasejoin.mx:
- ll_descendant: made resistent against holes (check highest
bits in size column not set)
- ll_child: move checks on highest-bitset in size column to
asserts
a(as child never should visit deleted nodes in the first
place)
- ll_child/ll_descendant: do allow bat[void,void] candidate
bats in
implemented by materializing the list
runtime/pf_support.mx:
- never use kind tests anymore (remove the kind_idx MIL
switch variable)
- in case of no selection (no_pre macro), we no longer need
to filer out nil sizes.
(this was the cause for the BUG report)
runtime/pathfinder.mx:
- fix just-introduced bug in error handling of xquery() MIL call
## Comment 5329
Date: 2006-08-15 19:25:38 +0200
From: @peterboncz
Logged In: YES
user_id=591107
bugfix [ 1490128 ] PF: inefficient handling of loop-lifted
path steps
=====================================================================
plus two more just-introduced bugs that mess up the test web:
- complaints in ll_scj about non OID candidate lists
- crashes when xquery() MIL queries cause errors
runtime/ll_staircasejoin.mx:
- ll_descendant: made resistent against holes (check highest
bits in size column not set)
- ll_child: move checks on highest-bitset in size column to
asserts
a(as child never should visit deleted nodes in the first
place)
- ll_child/ll_descendant: do allow bat[void,void] candidate
bats in
implemented by materializing the list
runtime/pf_support.mx:
- never use kind tests anymore (remove the kind_idx MIL
switch variable)
- in case of no selection (no_pre macro), we no longer need
to filer out nil sizes.
(this was the cause for the BUG report)
runtime/pathfinder.mx:
- fix just-introduced bug in error handling of xquery() MIL call
## Comment 5330
Date: 2006-08-16 09:10:31 +0200
From: @peterboncz
Logged In: YES
user_id=591107
bugfix [ 1490128 ] PF: inefficient handling of loop-lifted
path steps
=====================================================================
plus two more just-introduced bugs that mess up the test web:
- complaints in ll_scj about non OID candidate lists
- crashes when xquery() MIL queries cause errors
runtime/ll_staircasejoin.mx:
- ll_descendant: made resistent against holes (check highest
bits in size column not set)
- ll_child: move checks on highest-bitset in size column to
asserts
a(as child never should visit deleted nodes in the first
place)
- ll_child/ll_descendant: do allow bat[void,void] candidate
bats in
implemented by materializing the list
runtime/pf_support.mx:
- never use kind tests anymore (remove the kind_idx MIL
switch variable)
- in case of no selection (no_pre macro), we no longer need
to filer out nil sizes.
(this was the cause for the BUG report)
runtime/pathfinder.mx:
- fix just-introduced bug in error handling of xquery() MIL call
## Comment 5331
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1490128 at http://sourceforge.net/support/tracker.php?aid=1490128
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| PF: inefficient handling of loop-lifted path steps | https://api.github.com/repos/MonetDB/MonetDB/issues/928/comments | 0 | 2020-11-30T09:06:35Z | 2024-06-27T11:10:10Z | https://github.com/MonetDB/MonetDB/issues/928 | 753,294,410 | 928 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-15 12:23:56 +0200
From: Jan Rittinger <<jan.rittinger>>
To: @sjoerdmullender
Version: -- development
Last updated: 2006-05-16 04:02:30 +0200
## Comment 5324
Date: 2006-05-15 00:23:56 +0200
From: Jan Rittinger <<jan.rittinger>>
With the following query I inserted one document into
the other (documents are listed in the end of this bug
report):
insert-first (exactly-one(doc("foo.xml")/*[1]),
exactly-one(doc("auction.xml")/*[1]))
Afterwards I deleted 2 subtrees (each in a separate query):
delete(exactly-one(doc("foo.xml")//europe))
delete(exactly-one(doc("foo.xml")//samerica))
Then the PRE_SIZE table or _RID_SIZE table both contain
nil values (which I did not expect there):
MonetDB>bat("1014_rid_size").[isnil]().select(true).print();
-----------------
h t name
oid bit type
-----------------
[ 1918@0, true ]
[ 7619@0, true ]
I looked into the function
'CMDdelete_nodes_prepare_pre_size' but can only guess
there is an off by one error in the BAThdense branch.
(I think the last node should be one less. It is now:
'lst_pre = fst_pre + cnt;'.)
foo.xml:
<a foo="bar"><b>textnode</b><d><e/><f/></d><c
foo2="bar"/></a>
auction.xml:
see auction.xml in the XMark directory of the testweb
## Comment 5325
Date: 2006-05-16 16:02:30 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
There are several misconceptions going on here, but I'm
afraid there is no bug.
- CMDdelete_nodes_prepare_pre_size is not used in the delete
code. It is Stefan's version of a loop-lifted delete before
I finished mine. The code that is actually used for deletes
is do_udpate_delete. CMDdelete_nodes_prepare_pre_size
should be deleted.
- int(nil) is a valid value in the PRE_SIZE table.
To elaborate on the latter point.
The _RID_* tables are the tables as they are stored on disk.
The corresponding PRE_* tables are memory mapped versions
where the order of the pages has possibly been changed.
I.e., the PRE_* tables are just a special "view". The PRE_*
tables are the ones to be used by "ordinary" PF code. Only
the load and update code needs to worry about the _RID_* tables.
Holes in the document are represented as nil values in all
PRE_* tables, except for PRE_SIZE. In PRE_SIZE, a hole is
represented as the size of the rest of the hole ORed with
0x80000000. That is, the size is the same as for a normal
node, except for the left-most bit. When a row is the last
row of a hole, the size of the rest of the hole is 0. When
you OR that value with 0x80000000 you get int(nil).
However, the code does not use this as a nil, but as
0x80000000|0. Consecutive holes are allowed (although it is
more efficient in the staircase processing if consecutive
holes are merged into one).
In addition, if a hole were to span a page boundary, it is
split into multiple holes so that holes never span page
boundaries.
Since you have deleted two nodes, this created two holes. I
don't know whether the holes are consecutive or not. If
they are, they could be merged, but that is possibly too
expensive if the second hole comes after the first (you
would have to find the start of the first hole, and that is
relatively expensive; if the second hole comes before, you
can just look at the start of the next hole and add its size
to the sizes for the newly created hole).
Since there are two holes, there are also two rows that are
at the end of their holes. These rows have a size of 0 ORed
with 0x80000000 which MIL interprets as int(nil).
## Comment 5326
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1488506 at http://sourceforge.net/support/tracker.php?aid=1488506
| delete-node introduces 'nil' size value | https://api.github.com/repos/MonetDB/MonetDB/issues/927/comments | 0 | 2020-11-30T09:06:32Z | 2024-06-28T13:33:38Z | https://github.com/MonetDB/MonetDB/issues/927 | 753,294,372 | 927 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-14 12:08:32 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2006-06-15 10:16:36 +0200
## Comment 5320
Date: 2006-05-14 12:08:32 +0200
From: @grobian
sql>select interval '60' second;
. table_name
single_value name
sec_interval type
0 length
[ 60 ]
sql>select cast(interval '60' second as time);
. table_name
single_value name
time type
8 length
[ 00:00:00 ]
sql>
I would have expected 1 minute, or an error, not zero.
## Comment 5321
Date: 2006-06-15 22:16:36 +0200
From: @njnes
Logged In: YES
user_id=43556
added special mil proc for this (lng -> daytime).
## Comment 5322
Date: 2006-06-20 15:59:04 +0200
From: @njnes
Logged In: YES
user_id=43556
test added
src/test/BugTracker/Tests/cast_interval2time.SF-1488247.sql
## Comment 5323
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1488247 at http://sourceforge.net/support/tracker.php?aid=1488247
| SQL: cast interval to time results in zero time | https://api.github.com/repos/MonetDB/MonetDB/issues/926/comments | 0 | 2020-11-30T09:06:28Z | 2024-06-27T11:10:08Z | https://github.com/MonetDB/MonetDB/issues/926 | 753,294,327 | 926 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-12 11:23:48 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2006-06-01 11:14:26 +0200
## Comment 5315
Date: 2006-05-12 11:23:48 +0200
From: Jan Rittinger <<jan.rittinger>>
In the current version serialization takes 10 seconds
for a 10 MB file
(http://www-db.in.tum.de/~rittinge/files/mixed.xml)
which contains only slightly more nodes (517448) then
the auction xml file of the same size (472681). The
difference however is the number of attribute nodes
which is much higher in mixed.xml (517447 vs. 38266).
While the serialization of doc("auction10MB.xml") takes
2.72 seconds, doc("mixed.xml") requires 10.34 seconds!!
Removing the attributes in mixed.xml (by deleting all
entries from the attr_own bat) speeds up the
serialization to complete in 4.6 seconds.
Some more calculations reveal that for the auction file
we are able to serialize 187 nodes/sec (nodes =
elements+textnodes+attributes) while for mixed.xml the
serialization function (with and without attributes)
was only able to generate about 100 nodes/sec.
In all 3 cases the serialization seems way to slow...
(at least for me). As in principle the serialization is
only a dump of the tables (even in table order) and
other approaches are really faster we should be able to
come up with an appropriate fast serialization routine.
I see at least three possibilities to increase the
performance:
* serialize.mx uses about 50 function calls until one
node without attributes is serialized
* serialize.mx does collect the nodes using random
access with a lot of indirections
* serialize.mx uses stream_printf which is probably
slower than a fixed size print routine like stream_write.
## Comment 5316
Date: 2006-05-18 21:44:59 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Peter's recent fix (removing the BATuselect) and compiling
it with --enable-optimize did improve the performance by a
factor 3. I thus decrease the priority :)
## Comment 5317
Date: 2006-06-01 11:14:26 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Compiling pf with enable-optimize and measuring only the
serialization time (not the Mserver startup) and taking some
courses in math :) we are now at 32000+32000 nodes/sec.
That means the serialization is now 6 times faster than
before (BTW this is faster than shredding).
## Comment 5318
Date: 2006-06-20 09:37:07 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
no test -- serialization is tested in runtime/serialization.xq
## Comment 5319
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1487244 at http://sourceforge.net/support/tracker.php?aid=1487244
| PF: serialization processes only 100 nodes/sec | https://api.github.com/repos/MonetDB/MonetDB/issues/925/comments | 0 | 2020-11-30T09:06:25Z | 2024-06-27T11:10:07Z | https://github.com/MonetDB/MonetDB/issues/925 | 753,294,285 | 925 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-12 09:19:56 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-11-03 11:00:15 +0100
## Comment 5307
Date: 2006-05-12 09:19:56 +0200
From: Jan Rittinger <<jan.rittinger>>
The serialization of the attached document fails both
from persistent store as well as from cache. (Both
MonetDB and pathfinder are recent versions of the cvs
head.)
The query was:
doc("exponential2.xml")
and the resulting output:
!ERROR: [remap]: 4 times inserted nil due to errors at
tuples 0@0, 1@0, 2@0, 3@0.
!ERROR: [remap]: first error was:
!ERROR: remap: map index 8@0 out of range [0@0,7@0]
!ERROR: CMDremap: operation failed.
!ERROR: interpret_unpin: [remap] bat=424,stamp=-421
OVERWRITTEN
!ERROR: BBPdecref: 1011_rid_nid does not have pointer
fixes.
!ERROR: interpret_params: +(param 2): evaluation error.
PS: as sourceforge does not like large files (12MB) I
put it at
http://www-db.in.tum.de/~rittinge/files/exponential2.xml
## Comment 5308
Date: 2006-06-02 10:06:05 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
This seems to be more like a remap bug -- assign it to Peter
## Comment 5309
Date: 2006-06-02 10:23:07 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Sorry the title was incorrect. It is bug triggered at
add_doc. If printing the pre table all kind values (except
the document node) are 0. Thus it seems to be related to the
bugs '[ monetdb-Bugs-1483706 ] XQuery: Corrupt attributelist
for document' and '[ monetdb-Bugs-1499097 ] PF: shredding of
large documents is corrupt'.
In comparison to http://sourceforge.net/support/tracker.php?aid=1499097 Wouters proposed fix in http://sourceforge.net/support/tracker.php?aid=1483706 does not help.
## Comment 5310
Date: 2006-06-14 00:07:30 +0200
From: @peterboncz
Logged In: YES
user_id=591107
is this fixed now?
## Comment 5311
Date: 2006-06-14 15:25:19 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
no -- see yourself
## Comment 5312
Date: 2006-11-01 14:22:36 +0100
From: @drstmane
Logged In: YES
user_id=572415
test added in
pathfinder/tests/BugTracker/Tests/shredding-remap-error.SF-1487156.{unpack,shred,cache}_doc.*
seems to work fine;
once this is confirmed by nightly testing, the bug report
can be closed.
## Comment 5313
Date: 2006-11-03 11:00:15 +0100
From: @drstmane
Logged In: YES
user_id=572415
appears to be fixed:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.32.32.d-Darwin8.8.0/tests_BugTracker/shredding-remap-error.SF-1487156.shred_doc.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.32.32.d-Darwin8.8.0/tests_BugTracker/shredding-remap-error.SF-1487156.shred_doc.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.32.32.d-Darwin8.8.0/tests_BugTracker/shredding-remap-error.SF-1487156.cache_doc.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.32.32.d-Darwin8.8.0/tests_BugTracker/shredding-remap-error.SF-1487156.cache_doc.err.00.html
## Comment 5314
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1487156 at http://sourceforge.net/support/tracker.php?aid=1487156
| PF: add_doc fails because of remap (corrupt shredding) | https://api.github.com/repos/MonetDB/MonetDB/issues/924/comments | 0 | 2020-11-30T09:06:22Z | 2024-06-27T11:10:06Z | https://github.com/MonetDB/MonetDB/issues/924 | 753,294,258 | 924 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-11 05:25:03 +0200
From: @MarcinZukowski
To: @njnes
Version: -- development
Last updated: 2007-05-29 02:23:49 +0200
## Comment 5301
Date: 2006-05-11 17:25:03 +0200
From: @MarcinZukowski
In some situations when running BATextend part of my
data was corrupted. To be exact, last 16 bytes of the
old data was set to zero. The investigation points to
gdk_utils.mx:1175:
size_t newsize = size + sizeof(size_t) + sizeof(size_t);
size_t oldmax = (size_t) s[-2];
size_t newmax = MAX(*maxsize, newsize);
s = (ssize_t *) GDKvmrealloc((ptr) (s - 2),
(size_t) - oldsize,
newsize, oldmax, &newmax, emergency);
What happens, is we pass newsize increased with the
2*sizeof(size_t), to accomodate internal GDK memory
information storage. For the oldsize though we don't
increase this value. Changing the last line into:
s = (ssize_t *) GDKvmrealloc((ptr) (s - 2),
2 * sizeof(size_t) + (size_t) - oldsize,
newsize, oldmax, &newmax, emergency);
resulted in no more data loss. However, I'm not really
confident that it's a proper fix. Someone
(Peter,Niels,Sjoerd?) should take a look at it.
thanks.
## Comment 5302
Date: 2006-05-12 19:16:33 +0200
From: @njnes
Logged In: YES
user_id=43556
There is a fix in cvs now (store the size+2*size_t). Could
you verify that your problem is fixed? Maybe add a test to the
test web?
## Comment 5303
Date: 2006-05-17 20:42:53 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
The fix helped, at least for my problem.
Thanks.
Closing.
## Comment 5304
Date: 2006-06-20 15:53:10 +0200
From: @njnes
Logged In: YES
user_id=43556
put to pending as we need to add a test for this.
## Comment 5305
Date: 2007-05-29 14:23:49 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
As currently the use of vm-allocated bats is down to <= 64K, this is tested by many tests both in sql and pf, ie closing.
## Comment 5306
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1486620 at http://sourceforge.net/support/tracker.php?aid=1486620
| BATextend problem | https://api.github.com/repos/MonetDB/MonetDB/issues/923/comments | 0 | 2020-11-30T09:06:19Z | 2024-06-27T11:10:05Z | https://github.com/MonetDB/MonetDB/issues/923 | 753,294,223 | 923 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-09 02:01:13 +0200
From: Wouter Alink <<alink>>
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2006-12-14 06:23:32 +0100
## Comment 5292
Date: 2006-05-09 14:01:13 +0200
From: Wouter Alink <<alink>>
When MonetDB/XQuery is compiled with 'ADB_USE_NAMES'
defined in shredder.mx, it seems that when it
encounters an element with an 'id'-attribute, it puts
ALL attributes of this node in the index. My guess is
that it should only put the id-attribute in the index.
For example, given the document:
<test>
<a id="1"/>
<b id="2" d="A"/>
<b/>
<c id="3" e="B"/>
<d f="G"/>
<d f="G"/>
</test>
The following is internally generated:
mil>shred_doc("/home/wouter/monetdb/test.xml","test.xml");
Shredded XML doc("test.xml"), total time after
commit=0.433s
mil>bat("id_pre26").print();
-----------------
h t name
str oid type
-----------------
[ "1", 3@0 ]
[ "2", 5@0 ]
[ "A", 5@0 ]
[ "3", 9@0 ]
[ "B", 9@0 ]
mil>
I would expect something like:
-----------------
h t name
str oid type
-----------------
[ "1", 3@0 ]
[ "2", 5@0 ]
[ "3", 9@0 ]
I'm using 0.10.3, about a month old.
## Comment 5293
Date: 2006-05-09 14:11:21 +0200
From: @grobian
Logged In: YES
user_id=963970
> I'm using 0.10.3, about a month old.
upgrade first to see if the issue still is in there?
## Comment 5294
Date: 2006-05-09 14:17:46 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
The following patch for shredder.mx seems to fix the bug (at
least for the example case). JanF, could you please check
this? Thanks in advance.
1186c1186
< if ( (attrType =
specialAttrType(&shredCtx->specAttrDb,(char*)e_loc,(char*)*atts))
) {
---
> if ( (attrType =
specialAttrType(&shredCtx->specAttrDb,(char*)a_pfx,(char*)a_tag))
) {
## Comment 5295
Date: 2006-06-09 11:34:34 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Wouter,
This is very strange because the code is obviously wrong and
should not work because it indeed only works for the first
'id'. You solution is nearly correct, I think it sould read:
specialAttrType(&shredCtx->specAttrDb,(char*)e_loc,(char*)a_tag)
I will do the update, check if it breaks nothing and check
it in later today.
## Comment 5296
Date: 2006-06-14 00:08:55 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Jan:
does your fix work? If so, please mail me the patch and I
will apply it to the release branch.
Peter
## Comment 5297
Date: 2006-06-14 11:15:17 +0200
From: @peterboncz
Logged In: YES
user_id=591107
<!DOCTYPE CONTACTS [ <!ELEMENT CONTACTS ANY>
<!ELEMENT CONTACT (NAME)>
<!ELEMENT NAME (PCDATA)>
<!ATTLIST CONTACT NUM ID REQUIRED>
<!ATTLIST CONTACT BOSS IDREF IMPLIED> ]>
<CONTACTS>
<CONTACT NUM = "1" BOSS = "2">
<NAME>Lok Siu</NAME>
</CONTACT>
<CONTACT NUM = "2" BOSS = "1">
<NAME>Joseph Misuraca</NAME>
</CONTACT>
</CONTACTS>
this document has an internal DTD and allows for easier
testing. it seems fixed indeed.
## Comment 5298
Date: 2006-11-29 10:59:14 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Re-opened, as no test has been provided, yet.
User (submitter) and/or developer (assignee),
please supply a respective test,
or explain why a test is not required/possible.
## Comment 5299
Date: 2006-12-14 18:23:32 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
Adding a test is not worth it: it requires re-compilation of the source with a non-standard flag.
## Comment 5300
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1484616 at http://sourceforge.net/support/tracker.php?aid=1484616
| XQuery: ID-attribute lookup index | https://api.github.com/repos/MonetDB/MonetDB/issues/922/comments | 0 | 2020-11-30T09:06:17Z | 2024-06-28T13:33:37Z | https://github.com/MonetDB/MonetDB/issues/922 | 753,294,198 | 922 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-08 11:40:59 +0200
From: Wouter Alink <<alink>>
To: Wouter Alink <<alink>>
Version: -- development
Last updated: 2006-11-04 04:05:47 +0100
## Comment 5277
Date: 2006-05-08 11:40:59 +0200
From: Wouter Alink <<alink>>
When shredding a document with many attributes, they
are not all recorded anymore. Some, appearantly
randomly picked, attributes get lost.
To test this, I created a document with many elements,
and for each element there is at least an
xid-attribute. (i attached the script generating such
an XML-document).
[wouter@node-001 monetdb]$ cat xid.xml | grep "xid=" | wc
2507422 10029688 119632644
[wouter@node-001 monetdb]$ echo
'count(doc("/home/wouter/monetdb/xid.xml")//*)' |
MapiClient -lxq
2507422
[wouter@node-001 monetdb]$ echo
'count(doc("/home/wouter/monetdb/xid.xml")//@xid)' |
MapiClient -lxq
569048
I'm using the 0.10.3 version (about a month old).
Note: a document generated containing 992695 elements
and also 992695 xid-attributes shredded correctly (or
at least: monnetdb counted all the 992695 xid's
correctly for this document).
Note 2: no warnings or errors were reported during
shredding.
## Comment 5278
Date: 2006-05-10 14:28:06 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
I apologize for blaming the shredder at first.
I dived into the problem a little further: if the statistics
below are correct (were generated by compiling shredder.mx
with "define PRINT_STAT"), then the error is probably not
generated by the shredder (it produced enough PROP_VAL and
ATTR_PROP buns).
Does anybody have any idea where in the code the bug resides?
Maybe a more theoretic question might help to find it: what
is the difference in semantics between:
count(doc("/home/wouter/monetdb/xid.xml")//@*)
and
count(doc("/home/wouter/monetdb/xid.xml")//*/@*)
The difference in the answer is about 6 million (1707145 vs
7522266), while:
count(doc("/home/wouter/monetdb/xid.xml")//*/@xid)
and
count(doc("/home/wouter/monetdb/xid.xml")//@xid)
generate the same (incorrect) result: 569048
The file xid.xml can be found at:
/ufs/alink/monetdb/xid.xml.bz2
--------------------------------------
[wouter@node-001 monetdb]$ echo
'count(doc("/home/wouter/monetdb/xid.xml")//@xid)' |
MapiClient -lxq -T
STATISTICS of shredding "/home/wouter/monetdb/xid.xml":
[ PRE_SIZE, cnt=7522266, eg. the number of document nodes]
[PRE_LEVEL, cnt=7522266]
[ PRE_PROP, cnt=7522266]
[ PRE_KIND, cnt=7522266]
[ PRE_FRAG, cnt=0]
[ QN_URI, cnt=11]
[QN_PREFIX, cnt=11, dupl=10029677(=0%) , eg. the number of
distinct tags]
[ QN_LOC, cnt=11, dupl=10029677(=0%) ]
[PROP_TEXT, cnt=10, dupl=5014833(=0%) ]
[ PROP_COM, cnt=0, dupl=0(=100%) ]
[ PROP_INS, cnt=0]
[ PROP_TGT, cnt=0]
[ ID_PRE, cnt=2507422]
[IDREF_PRE, cnt=0]
[ ATTR_OWN, cnt=7522266, eg. the number of attributes]
[ ATTR_QN, cnt=7522266]
[ATTR_PROP, cnt=7522266]
[ATTR_FRAG, cnt=0]
[ PROP_VAL, cnt=2507423]
Elapsed time = 54s 402ms 639us [006us/node]
569048
[wouter@node-001 monetdb]$ cat xid.xml | grep " xid=\"" | wc
2507422 10029688 119632644
## Comment 5279
Date: 2006-05-23 15:04:17 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
I think I tracked this bug down to the use of the BATextend
function in the shredder. It looks like it is the same bug
as reported by Marcin under 1486620. I haven't tested this,
but will do this soon.
## Comment 5280
Date: 2006-05-24 18:09:28 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
ARGHH.
I couldn't find out why the bug didn't disappear after I
recompiled the latest stable branche. After going in to this
a little further, I found that the BATextend patch had only
been applied to the HEAD. Niels, is the same patch that
Marcin proposed also applicable to the stable branche?
Anyhow, even with the patch, it did not solve this bug.
It took me quite a while, but I finally found:
- when the shredder has allocated to little memory, it calls
BATextend
- BATextend calls HEAPextend to increase the space for BUNs.
- when HEAPextend wants to switch to MMAPPED (gdk_heap.mx,
line 207), it somehow does not (always) copy the current
contents of the in-memory BAT to the file.
A quick fix is to increase the "vm_minsize();", but I assume
a better solution should be found. Can some GDK-guru please
look at this problem (Peter?, Niels?)
## Comment 5281
Date: 2006-06-01 23:56:48 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
My best guess is that the bug occurs because the shredder
does its own BAT-inserts and bypasses the GDK BATinsert-
function. The shredder does (as far as i can see) not
update the bat->free pointer before BATextend is called
and maybe that pointer is used for determining which part
of the BAT to copy. But i don't really know anything about
the gdk-code.
I don't have a useful setup at the moment to reproduce the
bug, but could somebody maybe check whether adding:
sb->bat->batBuns->free = sb->size * sizeof(oid);
or something similar on line 880 of shredder.mx (just
before the line "sb->size = newsize;") would fix the
problem?
## Comment 5282
Date: 2006-06-02 09:39:46 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
applying your patch in the CVS head solves at least the
issues occuring in the '[ monetdb-Bugs-1499097 ] PF:
shredding of large documents is corrupt' bug report.
If you are sure that it does the right thing I can check it in.
## Comment 5283
Date: 2006-06-03 12:37:23 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
No, please do not check it in, or perhaps check it in with
a "TODO"-statement. It was just to see whether the bug was
triggered by not setting the "batBuns->free" pointer. If
you say that this solves the bug, than maybe the bug has
been located. I still would like JanF or a MonetDB-kernel-
expert to have a look at this fixing-code, before this bug
can be closed.
## Comment 5284
Date: 2006-06-08 14:53:21 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
I had a look at Wouters repair and talked about it with
Peter. The fix was nearly OK. It only worked for [void,oid]
BAT's. We decided to use the setBATcapacity() function which
we used to make the final BAT administration correct for all
intermediate BATextends().
I cannot repeat this test so it would be nice if Wouter
could check if my update also works for him.
## Comment 5285
Date: 2006-06-14 00:33:17 +0200
From: @peterboncz
Logged In: YES
user_id=591107
sjoerd, I would like to assign this bug to Wouter, but he
does not appear in the pull-down menu.
is that a sourceforge config issue?
vzzzbx = wouter
## Comment 5286
Date: 2006-06-14 00:38:39 +0200
From: @drstmane
Logged In: YES
user_id=572415
On Peter's request:
Added Wouter to list of assignees and assigned bug to him.
## Comment 5287
Date: 2006-06-14 10:37:51 +0200
From: @peterboncz
Logged In: YES
user_id=591107
OK,
wouter, I assume this is fixed now: please check.
## Comment 5288
Date: 2006-06-14 19:22:19 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
do we need to add a test for this? It seems to be
difficult to trigger this bug in a script (if we don't
want to store or generate a huge XML document).
## Comment 5289
Date: 2006-11-01 16:42:42 +0100
From: @drstmane
Logged In: YES
user_id=572415
test added in
pathfinder/tests/BugTracker/Tests/corrupt-attributelist.SF-1483706.{create,shred,cache,remove}_doc.*
seems to work fine;
once this is confirmed by nightly testing, the bug report
can be closed.
## Comment 5290
Date: 2006-11-04 16:05:47 +0100
From: @drstmane
Logged In: YES
user_id=572415
tests work fine in the testweb:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugTracker/corrupt-attributelist.SF-1483706.shred_doc.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugTracker/corrupt-attributelist.SF-1483706.cache_doc.out.00.html
hence, closing this one.
## Comment 5291
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1483706 at http://sourceforge.net/support/tracker.php?aid=1483706
| XQuery: Corrupt attributelist for document | https://api.github.com/repos/MonetDB/MonetDB/issues/921/comments | 0 | 2020-11-30T09:06:13Z | 2024-06-27T11:10:03Z | https://github.com/MonetDB/MonetDB/issues/921 | 753,294,157 | 921 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-05-05 02:13:49 +0200
From: @sjoerdmullender
To: @mlkersten
Version: -- development
Last updated: 2006-06-11 05:40:31 +0200
## Comment 5274
Date: 2006-05-05 14:13:49 +0200
From: @sjoerdmullender
On a Fedora Core 5 system with the hplip service
running, port 50000 is in use by a process called
hpiod. This is using an out-of-the-box configuration.
Perhaps we should consider a different port?
For now I have disabled the service on my machine.
Perhaps I don't need it, although I do have an HP
printer at home. We'll see.
## Comment 5275
Date: 2006-06-11 17:40:31 +0200
From: @mlkersten
Logged In: YES
user_id=490798
mapi_port in the configuration file can be set by the user
as well to avoid those conflicts. I don't see the need to
change our choice now.
## Comment 5276
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1482437 at http://sourceforge.net/support/tracker.php?aid=1482437
| Mapi port conflict | https://api.github.com/repos/MonetDB/MonetDB/issues/920/comments | 0 | 2020-11-30T09:06:09Z | 2024-06-28T13:33:37Z | https://github.com/MonetDB/MonetDB/issues/920 | 753,294,122 | 920 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-04-27 07:46:39 +0200
From: @grobian
To: @sjoerdmullender
Version: -- development
Last updated: 2006-04-27 07:58:49 +0200
## Comment 5271
Date: 2006-04-27 19:46:39 +0200
From: @grobian
While trying to bootstrap monet5 on my Darwin 8.6.0, I
encountered the following problem:
% env PATH=${INSTALL_DIR}/bin:${PATH}
PYTHONPATH=${INSTALL_DIR}/lib/python`python -V | & cut
-f2 -d" " | cut -c1-3`/site-packages ./bootstrap
using /usr/bin/glibtool and /usr/bin/glibtoolize.
automake 1.6.3 is 1.5 or newer. Good.
autoconf 2.59 is 2.57 or newer. Good.
libtool 1.5 is 1.4 or newer. Good.
Python 2.3.5 is 2.0.0 or newer. Good.
/Volumes/Scratch/monetdb/five/monetdb/src
/Volumes/Scratch/monetdb/five/monetdb/src/mal
/Volumes/Scratch/monetdb/five/monetdb/src/mil
/Volumes/Scratch/monetdb/five/monetdb/src/modules
/Volumes/Scratch/monetdb/five/monetdb/src/modules/atoms
/Volumes/Scratch/monetdb/five/monetdb/src/modules/kernel
/Volumes/Scratch/monetdb/five/monetdb/src/modules/mal
/Volumes/Scratch/monetdb/five/monetdb/src/modules/mil
/Volumes/Scratch/monetdb/five/monetdb/src/tools
/Volumes/Scratch/monetdb/five/monetdb/src/compiler
/Volumes/Scratch/monetdb/five/monetdb/src/optimizer
/Volumes/Scratch/monetdb/five/monetdb/src/scheduler
/Volumes/Scratch/monetdb/five/monetdb/src/applications
/Volumes/Scratch/monetdb/five/monetdb/conf
Remember to add `AC_PROG_LIBTOOL' to `configure.in'.
You should add the contents of
`/usr/share/aclocal/libtool.m4' to `aclocal.m4'.
Putting files in AC_CONFIG_AUX_DIR, `conf'.
aclocal: configure.in: 30: macro `AM_MONETDB_UTILS' not
found in library
bootstrap reports that my automake/autoconf versions
are sufficient, but aclocal dies on some macro thing
which is usually a version related problem.
## Comment 5272
Date: 2006-04-27 19:58:49 +0200
From: @grobian
Logged In: YES
user_id=963970
I believe this bug is kind of invalid without monet4
installed...
## Comment 5273
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1477851 at http://sourceforge.net/support/tracker.php?aid=1477851
| bootstrap failure on OSX | https://api.github.com/repos/MonetDB/MonetDB/issues/919/comments | 0 | 2020-11-30T09:06:06Z | 2024-06-28T13:33:36Z | https://github.com/MonetDB/MonetDB/issues/919 | 753,294,073 | 919 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-04-24 11:50:04 +0200
From: @yzchang
To: @mlkersten
Version: -- development
Last updated: 2006-06-14 12:34:51 +0200
## Comment 5267
Date: 2006-04-24 23:50:04 +0200
From: @yzchang
I tried the following series of threadcnt() (in
"current" version of MonetDB) and the results look
quite strange:
MonetDB>threads();
-------------------------
gdk thread name
int str type
-------------------------
[ 1, "Interpreter" ]
[ 2, "Interpreter" ]
[ 3, "Interpreter" ]
MonetDB>threadcnt(0).print();
[ 3 ] this right
MonetDB>threadcnt(4).print();
[ 6 ] shouldn't this be [ 7 ]?
MonetDB>threadcnt(0).print();
[ 7 ] a thread has been created?!
MonetDB>threadcnt(-1).print();
[ 7 ] no thread has been killed!
MonetDB>threadcnt(0).print();
[ 6 ] a thread has been killed ?!
MonetDB>threadcnt(0).print();
[ 6 ] this seems OK
MonetDB>threadcnt(4).print();
[ 9 ] we miss a thread
MonetDB>threadcnt(4).print();
[ 13 ] we still miss a thread
MonetDB>threadcnt(0).print();
[ 14 ] now comes the missing thread?
## Comment 5268
Date: 2006-04-25 00:24:02 +0200
From: @drstmane
Logged In: YES
user_id=572415
Jennie,
incrementing the threadcount work "instantly" for me; with
decrementing, you just have to be a bit patient (mind the
"sleep(1)" in my example below):
========
MonetDB>print(threadcnt(0)); var i:=0; while (i < 9) {
i:+=1; var t0:=threadcnt(0); var t1:=threadcnt(i); var
t2:=threadcnt(0); printf("i=%d, t0=%d, t1=%d,
t2=%d\n",i,t0,t1,t2); } ; print(threadcnt(0));
[ 1 ]
i=1, t0=1, t1=2, t2=2
i=2, t0=2, t1=4, t2=4
i=3, t0=4, t1=7, t2=7
i=4, t0=7, t1=11, t2=11
i=5, t0=11, t1=16, t2=16
i=6, t0=16, t1=22, t2=22
i=7, t0=22, t1=29, t2=29
i=8, t0=29, t1=37, t2=37
i=9, t0=37, t1=46, t2=46
[ 46 ]
MonetDB>print(threadcnt(0)); var i:=0; while (i < 9) {
i:+=1; var t0:=threadcnt(0); var t1:=threadcnt(-1 * i); var
t2:=threadcnt(0); printf("i=%d, t0=%d, t1=%d,
t2=%d\n",i,t0,t1,t2); } ; print(threadcnt(0));
[ 46 ]
i=1, t0=46, t1=46, t2=46
i=2, t0=46, t1=46, t2=46
i=3, t0=46, t1=46, t2=46
i=4, t0=46, t1=46, t2=46
i=5, t0=46, t1=46, t2=46
i=6, t0=46, t1=46, t2=46
i=7, t0=46, t1=46, t2=46
i=8, t0=46, t1=46, t2=46
i=9, t0=46, t1=46, t2=46
[ 46 ]
MonetDB>print(threadcnt(0));
[ 1 ]
MonetDB>print(threadcnt(0)); var i:=0; while (i < 9) {
i:+=1; var t0:=threadcnt(0); var t1:=threadcnt(i); var
t2:=threadcnt(0); printf("i=%d, t0=%d, t1=%d,
t2=%d\n",i,t0,t1,t2); } ; print(threadcnt(0));
[ 1 ]
i=1, t0=1, t1=2, t2=2
i=2, t0=2, t1=4, t2=4
i=3, t0=4, t1=7, t2=7
i=4, t0=7, t1=11, t2=11
i=5, t0=11, t1=16, t2=16
i=6, t0=16, t1=22, t2=22
i=7, t0=22, t1=29, t2=29
i=8, t0=29, t1=37, t2=37
i=9, t0=37, t1=46, t2=46
[ 46 ]
MonetDB>print(threadcnt(0)); var i:=0; while (i < 9) {
i:+=1; var t0:=threadcnt(0); var t1:=threadcnt(-1 * i);
sleep(1); var t2:=threadcnt(0); printf("i=%d, t0=%d, t1=%d,
t2=%d\n",i,t0,t1,t2); } ; print(threadcnt(0));
[ 46 ]
i=1, t0=46, t1=46, t2=45
i=2, t0=45, t1=45, t2=43
i=3, t0=43, t1=43, t2=40
i=4, t0=40, t1=40, t2=36
i=5, t0=36, t1=36, t2=31
i=6, t0=31, t1=31, t2=25
i=7, t0=25, t1=25, t2=18
i=8, t0=18, t1=18, t2=10
i=9, t0=10, t1=10, t2=1
[ 1 ]
MonetDB>
========
## Comment 5269
Date: 2006-06-11 18:43:14 +0200
From: @mlkersten
Logged In: YES
user_id=490798
This does not require an additional patch it seems.
The message is clear and perhaps it should be added
to the documentation somewhere (in the future)
## Comment 5270
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1475811 at http://sourceforge.net/support/tracker.php?aid=1475811
| threadcnt() behaves weird | https://api.github.com/repos/MonetDB/MonetDB/issues/918/comments | 0 | 2020-11-30T09:06:03Z | 2024-06-28T13:33:35Z | https://github.com/MonetDB/MonetDB/issues/918 | 753,294,031 | 918 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-04-24 07:43:41 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2006-05-01 11:45:38 +0200
## Comment 5264
Date: 2006-04-24 19:43:41 +0200
From: @drstmane
The Update tests seem to fail randomly with:
Mserver:
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/gdk/gdk_bbp.mx:1674:
BBPdescriptor: Assertion
`BBP[(((int)(i))>0?((int)(i)):-((int)(i)))].refs' failed.
## Comment 5265
Date: 2006-05-01 11:45:37 +0200
From: @drstmane
Logged In: YES
user_id=572415
Tests seem to work fine after Sjoerd's fixes of MonetDB's
BAT caching code.
## Comment 5266
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1475689 at http://sourceforge.net/support/tracker.php?aid=1475689
| PF: Update tests seem to fail randomly | https://api.github.com/repos/MonetDB/MonetDB/issues/917/comments | 0 | 2020-11-30T09:06:00Z | 2024-06-27T11:09:59Z | https://github.com/MonetDB/MonetDB/issues/917 | 753,293,995 | 917 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-04-24 07:26:42 +0200
From: @drstmane
To: @yzchang
Version: -- development
Last updated: 2006-04-25 12:31:08 +0200
## Comment 5261
Date: 2006-04-24 19:26:42 +0200
From: @drstmane
All but one XQuery-RPC tests fail with:
ERROR: interpret: no matching MIL operator to
'get_rpc_res(BAT[oid,BAT], oid, str, BAT[oid,lng],
BAT[oid,dbl], BAT[oid,dbl], BAT[oid,str])'.
## Comment 5262
Date: 2006-04-25 12:31:08 +0200
From: @yzchang
Logged In: YES
user_id=341633
Seems fixed by adding an "ADDHELP" for the proc.
Yes, this sounds strange, but it does make difference.
Won't spend too much time on this issue, so close the bug
## Comment 5263
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1475675 at http://sourceforge.net/support/tracker.php?aid=1475675
| PF: all but one XQuery-RPC test fail | https://api.github.com/repos/MonetDB/MonetDB/issues/916/comments | 0 | 2020-11-30T09:05:56Z | 2024-06-27T11:09:58Z | https://github.com/MonetDB/MonetDB/issues/916 | 753,293,948 | 916 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-04-24 11:49:37 +0200
From: @sjoerdmullender
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2006-06-03 10:07:35 +0200
## Comment 5254
Date: 2006-04-24 11:49:37 +0200
From: @sjoerdmullender
Some of the subtests fail with an assertion failed.
The assertion is assert(sig_count) which was introduced
on April 19. In at least one instance of the subtests,
the function PFfun_new was called from
create_join_function in milprint_summer.c with an
explicit sig_count==0.
Please test before checking in.
## Comment 5255
Date: 2006-04-24 19:01:28 +0200
From: @drstmane
Logged In: YES
user_id=572415
Same bug (assertion) occurs with the following tests:
tests/BugsViaSourgeforce/Tests/ID.1297836-1.*
tests/BugsViaSourgeforce/Tests/ID.1204965-b.*
tests/BugsViaSourgeforce/Tests/ID.1204965-c.*
tests/BugsViaSourgeforce/Tests/ID.1244326.*
tests/BugsViaSourgeforce/Tests/ID.1207056-3.*
tests/XQuery/Tests/fun6.*
tests/BugDay_2005-12-19_0.9.3/Tests/zero-or-one_merged-union.SF-1221336.*
tests/BugDay_2005-12-19_0.9.3/Tests/zero-or-one_merged-union_2.SF-1221336.*
tests/XMark/Tests/q03.*
tests/XMark/Tests/q11.*
tests/XMark/Tests/q12.*
tests/XMark/opt/XQ/Tests/q13.*
tests/XMark/opt/XQ/Tests/q02.*
tests/XMark/opt/XQ/Tests/q20.*
tests/XMark/opt/XQ/Tests/q07.*
tests/XMark/opt/XQ/Tests/q16.*
tests/XMark/opt/XQ/Tests/q03.*
tests/XMark/opt/XQ/Tests/q17.*
tests/XMark/opt/XQ/Tests/q19.*
tests/XMark/opt/XQ/Tests/q11.*
tests/XMark/opt/XQ/Tests/q01.*
tests/XMark/opt/XQ/Tests/q05.*
tests/XMark/opt/XQ/Tests/q12.*
tests/XMark/opt/XQ/Tests/q14.*
tests/XMark/opt/XQ/Tests/q06.*
tests/XMark/opt/XQ/Tests/q04.*
tests/XMark/opt/XQ/Tests/q15.*
tests/XMark/opt/XQ/Tests/q09.*
tests/XMark/opt/XQ/Tests/q08.*
tests/XMark/opt/XQ/Tests/q10.*
tests/XMark/opt/XQ/Tests/q18.*
tests/XMark/opt/MIL/Tests/xq2mil.*
tests/XMark/Tests/q09.*
tests/XMark/Tests/q08.*
tests/XMark/mod/XQ/Tests/q13.*
tests/XMark/mod/XQ/Tests/q02.*
tests/XMark/mod/XQ/Tests/q20.*
tests/XMark/mod/XQ/Tests/q07.*
tests/XMark/mod/XQ/Tests/q16.*
tests/XMark/mod/XQ/Tests/q03.*
tests/XMark/mod/XQ/Tests/q17.*
tests/XMark/mod/XQ/Tests/q19.*
tests/XMark/mod/XQ/Tests/q11.*
tests/XMark/mod/XQ/Tests/q01.*
tests/XMark/mod/XQ/Tests/q05.*
tests/XMark/mod/XQ/Tests/q12.*
tests/XMark/mod/XQ/Tests/q14.*
tests/XMark/mod/XQ/Tests/q06.*
tests/XMark/mod/XQ/Tests/q04.*
tests/XMark/mod/XQ/Tests/q15.*
tests/XMark/mod/XQ/Tests/q09.*
tests/XMark/mod/XQ/Tests/q08.*
tests/XMark/mod/XQ/Tests/q10.*
tests/XMark/mod/XQ/Tests/q18.*
tests/XMark/mod/MIL/Tests/xq2mil.*
tests/XMark/Tests/q10.*
## Comment 5256
Date: 2006-04-24 19:24:01 +0200
From: @drstmane
Logged In: YES
user_id=572415
As usually, see
http://monetdb.cwi.nl/Development/TestWeb/Current/
in particular
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/index.html
for details
(Nightly testing of pathfinder should be available/working
again as of tomorrow morning, again --- apparently, nobody
has "missed" it ... |-(()
## Comment 5257
Date: 2006-04-24 19:42:02 +0200
From: @drstmane
Logged In: YES
user_id=572415
A layman's unqualified guess:
simply removing the `assert(sig_count);` from function
PFfun_new in compiler/semantics/functions.c seems to work
fine ("confirmed" by Mtest).
Samuel,
could you please check, whether this is the correct
solution, i.e., whether the assertion is indeed wrong/not
needed, and if so, check in the respective fix?
Thanks!
Stefan
## Comment 5258
Date: 2006-05-02 13:07:28 +0200
From: @drstmane
Logged In: YES
user_id=572415
Samuel,
any news on this one?
Stefan
## Comment 5259
Date: 2006-06-03 10:07:34 +0200
From: @drstmane
Logged In: YES
user_id=572415
Appears to be fixed.
## Comment 5260
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1475404 at http://sourceforge.net/support/tracker.php?aid=1475404
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 kerschbaumers@users.sourceforge.net.
| PF: test compiler/pf-M_XMark fails | https://api.github.com/repos/MonetDB/MonetDB/issues/915/comments | 0 | 2020-11-30T09:05:53Z | 2024-06-27T11:09:57Z | https://github.com/MonetDB/MonetDB/issues/915 | 753,293,907 | 915 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-04-24 11:45:48 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2006-04-27 11:39:42 +0200
## Comment 5251
Date: 2006-04-24 11:45:48 +0200
From: @grobian
Compilation results in the following two warnings:
sql_parser.y:712.5-11: warning: type clash on default
action: <sym> != <>
conflicts: 5 shift/reduce, 43 reduce/reduce
sql_parser.y:712.5-11: warning: type clash on default
action: <sym> != <>
conflicts: 5 shift/reduce, 43 reduce/reduce
## Comment 5252
Date: 2006-04-27 11:39:42 +0200
From: @grobian
Logged In: YES
user_id=963970
fixed by removing the empty rule for TRIGGER
## Comment 5253
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1475401 at http://sourceforge.net/support/tracker.php?aid=1475401
| SQL compilation complains about parser clashes | https://api.github.com/repos/MonetDB/MonetDB/issues/914/comments | 0 | 2020-11-30T09:05:51Z | 2024-06-27T11:09:56Z | https://github.com/MonetDB/MonetDB/issues/914 | 753,293,873 | 914 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-04-20 01:50:11 +0200
From: Farid Z <<faridz>>
To: @sjoerdmullender
Version: -- development
Last updated: 2006-06-13 07:33:22 +0200
## Comment 5233
Date: 2006-04-20 01:50:11 +0200
From: Farid Z <<faridz>>
SQLTables, SQLPrimaryKeys, etc. don't appear to support
ODBC row bind offset SQL_ATTR_ROW_BIND_OFFSET_PTR.
I can attach a sample VC++ project if necessary to
duplicate this issue.
## Comment 5234
Date: 2006-06-09 14:16:36 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
I'm sorry I haven't been able to look at this earlier.
Could you please attach a (small) example?
## Comment 5235
Date: 2006-06-09 19:24:04 +0200
From: Farid Z <<faridz>>
Logged In: YES
user_id=1423442
Actually turns out this is not a bind parameter offset
pointer issue but rather a driver connection issue.
Attached project to dupicate this issue. From the main
screen Test menu Choose the first test item.
The test executes a select statement with an order by clause
that fails. Executing SQLTables after that fails also.
## Comment 5236
Date: 2006-06-13 17:37:55 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
In your program you set autocommit mode off. This means
that you have to handle transactions yourself. Once an
error has occurred in a transaction, you have to first end
the transaction ans start a new one before you can do any
successful query.
If you try this by hand, you would see
ERROR = !current transaction is aborted (please ROLLBACK)
So I would say, this is not a bug, so I'm closing the bug.
If you don't agree, by all means reopen.
## Comment 5237
Date: 2006-06-13 18:02:19 +0200
From: Farid Z <<faridz>>
Logged In: YES
user_id=1423442
Requiring an application to do a rollback after evey error
is not a standard RDBMS behavior.
If a transaction hits an error it is up to the application
to decide to rollback the transaction or not. The
applicaition should be able to continue executing other
statements without rolling back the transaction if needed.
Also note that the statement that hits the error is not
doing any DML and therefore there is really nothing to roll
back. It's just executing a query, so there is nothing to
commit or rollback.
## Comment 5238
Date: 2006-06-13 18:10:15 +0200
From: @grobian
Logged In: YES
user_id=963970
> Requiring an application to do a rollback after evey error
> is not a standard RDBMS behavior.
It is, if you don't use auto commit mode. That mode,
however defaults to enabled for ODBC.
> If a transaction hits an error it is up to the application
> to decide to rollback the transaction or not. The
> applicaition should be able to continue executing other
> statements without rolling back the transaction if needed.
Since statements are on top of a connection, I doubt whether
that is true. Any statement will fail after an error on the
connection. Rollback and commit have to be done on the
connection, not the statements.
> Also note that the statement that hits the error is not
> doing any DML and therefore there is really nothing to roll
> back. It's just executing a query, so there is nothing to
> commit or rollback.
Query execution can result in an error. Even if this is a
syntax error, the transaction needs to be invalidated
because an error was made which might be unexpected to the
application. The latter should deal with it. In any case,
the standard prescribes that the transaction is invalidated
upon an error.
## Comment 5239
Date: 2006-06-13 19:03:02 +0200
From: Farid Z <<faridz>>
Logged In: YES
user_id=1423442
I can understand an all or nothing requirement for ending a
transaction when the statement in error is a DML statement.
But when the statement is not a DML statement there should
be no need to do a commit/rollback because the statement is
not supposed to change the DBMS to begin with.
## Comment 5240
Date: 2006-06-13 19:06:37 +0200
From: @grobian
Logged In: YES
user_id=963970
> But when the statement is not a DML statement there should
> be no need to do a commit/rollback because the statement is
> not supposed to change the DBMS to begin with.
I don't understand this point. If it is a DDL the
database's schema administration is being modified, which
also requires a transaction.
## Comment 5241
Date: 2006-06-13 19:26:59 +0200
From: Farid Z <<faridz>>
Logged In: YES
user_id=1423442
select 1 from sys.users where name = user
union all
select 2 from sys.users where name = user order by 1;
I meant DML statements that do not change data such as a
query as above. Doing a commit/rollback after an error for
such a statement should not be required.
## Comment 5242
Date: 2006-06-13 19:33:21 +0200
From: @grobian
Logged In: YES
user_id=963970
For MonetDB/SQL it is. In a fully serialisable transaction
(the only transaction level supported) dirty or phantom
reads are not allowed.
In any case, either the query is useless, auto-commit should
have been used, or too much knowledge has to be built in to
cover a few sporadic cases that do not look very
representative to me.
## Comment 5243
Date: 2006-06-13 19:57:46 +0200
From: Farid Z <<faridz>>
Logged In: YES
user_id=1423442
This affects the whole application. It means that a
cross-dbms ODBC application that is used successfully with
MS SQL Server, Oracle, DB2, Informix, Sybase, Teradata, and
other DBMSs can not be used with MonetDB. These DBMSs do not
require an application to do a commit/rollback after a query
error.
I don't understand what is being committed/rolled back if
the application has just executed a query and it hits an
error. It must be the statements that preceded the query. If
so, the DBMS can just ignore the query error and continue
since the query execution does not change the database
persistent state.
## Comment 5244
Date: 2006-06-13 20:05:30 +0200
From: @grobian
Logged In: YES
user_id=963970
% psql
Welcome to psql 8.0.8, the PostgreSQL interactive terminal.
u=> start transaction;
START TRANSACTION
u=> select 1;
?column?
----------
1
(1 row)
u=> select something wrong;
ERROR: syntax error at or near "wrong" at character 18
LINE 1: select something wrong;
^
u=> select 1;
ERROR: current transaction is aborted, commands ignored
until end of transaction block
u=> rollback;
ROLLBACK
u=>
PostgreSQL acts like MonetDB/SQL in this case, and I cannot
imagine Oracle not doing the same. Unfortunately I don't
have access to such databases, so I cannot easily check.
## Comment 5245
Date: 2006-06-13 20:16:11 +0200
From: Farid Z <<faridz>>
Logged In: YES
user_id=1423442
PostgreSQL 8.1 does a similar thing but it's being reported
as a new bug in 8.1 and it broke applications. PostgreSQL
8.0 did not exhibit this behavior. Oracle does no such
thing, neither do MS SQL Server 2000, 2005, DB2, Informix,
ANTs, FairCom, Firebird, InterBase, Mimer SQL, MySQL,
PervasiveSQL, Sybase, SQL Anywere, Teradata, etc.
## Comment 5246
Date: 2006-06-13 20:42:45 +0200
From: @grobian
Logged In: YES
user_id=963970
MySQL doesn't seem to do anything with transactions to me.
I used to have access to a MS SQL Server 2000 server, and I
know almost for sure that with the PostgreSQL testcase it
will respond in the same way. Do you perhaps just need meta
data from the driver after an error has occurred?
## Comment 5247
Date: 2006-06-13 21:19:52 +0200
From: Farid Z <<faridz>>
Logged In: YES
user_id=1423442
No. MS SQL Server does not require transaction to be rolled
back/committed after an error. It is up to the application
to decide when it wants to commit/rollback.
begin tran -- start a new transaction
>Command(s) completed successfully.
select 1 from asdfasd
>Msg 208, Level 16, State 1, Line 1
>Invalid object name 'asdfasd'.
select 1
>1
>
>(1 row(s) affected)
commit
>Command(s) completed successfully.
Oracle:
SQL*Plus: Release 9.2.0.1.0 - Production on Tue Jun 13
15:12:46 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights
reserved.
Connected.
select 1 from asdfas
*
ERROR at line 1:
ORA-00942: table or view does not exist
select 1 from dual
1
----------
1
1 row selected.
commit;
Commit complete.
## Comment 5248
Date: 2006-06-13 21:24:16 +0200
From: @grobian
Logged In: YES
user_id=963970
what is the transaction isolation level of MSSQL and Oracle?
## Comment 5249
Date: 2006-06-13 21:41:35 +0200
From: Farid Z <<faridz>>
Logged In: YES
user_id=1423442
Does not make a difference as far as requiring
commit/rollback . I tried the same example with MS SQL
Server 2005 with isolation level READ COMMITTED ( the
default ) and SERIALiZABLE and got the same behavior.
Application is not required to commit/rollback after any
error in manual autocommit mode.
## Comment 5250
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1473288 at http://sourceforge.net/support/tracker.php?aid=1473288
| SQLTables fails if previous statement failed | https://api.github.com/repos/MonetDB/MonetDB/issues/913/comments | 0 | 2020-11-30T09:05:47Z | 2024-06-28T13:33:35Z | https://github.com/MonetDB/MonetDB/issues/913 | 753,293,835 | 913 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-04-13 04:04:43 +0200
From: Stratos Idreos <<idreos>>
To: @mlkersten
Version: -- development
Last updated: 2006-04-13 04:25:37 +0200
## Comment 5229
Date: 2006-04-13 16:04:43 +0200
From: Stratos Idreos <<idreos>>
function nextElement is not recognized
!ERROR: 'mal.nextElement' undefined in user.main
## Comment 5230
Date: 2006-04-13 16:10:12 +0200
From: @grobian
Logged In: YES
user_id=963970
please use bugzilla for M5 as long as it's not yet on SF.
## Comment 5231
Date: 2006-04-13 16:25:37 +0200
From: @mlkersten
Logged In: YES
user_id=490798
The mal.nextElement call has been replaced by
language.nextElement.
## Comment 5232
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1469832 at http://sourceforge.net/support/tracker.php?aid=1469832
| mal.nextElement is not recognized | https://api.github.com/repos/MonetDB/MonetDB/issues/912/comments | 0 | 2020-11-30T09:05:44Z | 2024-06-28T13:33:34Z | https://github.com/MonetDB/MonetDB/issues/912 | 753,293,800 | 912 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-04-08 11:17:54 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2006-04-24 07:57:19 +0200
## Comment 5226
Date: 2006-04-08 11:17:54 +0200
From: @drstmane
`make dist` and hence `make rpm` fail on all our
testing platforms, since none of them has (a proper)
"netcdf" installed.
Thus, there are no "daily builds" for MonetDB any more.
We should either (1) install "netcdf" on all of our
testing platforms, or (2) fix our configure- and/or
Make-file(s) so that either (a) the source distribution
(automatically) checks for "netcdf" only if "netcdf"
was available when the source tar ball was made, or (b)
the "netcdf" related source files are extracted into
the source tar ball even if "netcdf" is not available
when the source tar ball is made.
Similar solution might apply to other parts
(subdirectories) conditional of the code that are/can
be disabled by conditionals.
See also
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.Makes3/index_short.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.GNU.64.64.d-Fedora4/dist.out
## Comment 5227
Date: 2006-04-24 19:57:19 +0200
From: @drstmane
Logged In: YES
user_id=572415
The `make dist` problem seems to be fixed.
There are still/again problems with `make rpm` for sql &
pathfinder, but these will be reported as new bugs tomorrow...
## Comment 5228
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1466788 at http://sourceforge.net/support/tracker.php?aid=1466788
| `make dist` and hence `make rpm` fail on all platforms | https://api.github.com/repos/MonetDB/MonetDB/issues/911/comments | 0 | 2020-11-30T09:05:40Z | 2024-06-27T11:09:53Z | https://github.com/MonetDB/MonetDB/issues/911 | 753,293,754 | 911 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.