issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.46B | issue_number int64 1 127k |
|---|---|---|---|---|---|---|---|---|---|
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-02 04:47:28 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2008-07-16 06:41:21 +0200
## Comment 9676
Date: 2008-06-02 16:47:28 +0200
From: @drstmane
While working fine in the previous Feb2006 release, test tests/from_Twente/moa/Tests/list.milS fails in the development trunk since 2008/04/05, i.e., after checkins on 2008/04/04 or on 2008/04/03 (there were no testing results on 2008/04/04), and hence also in the MonetDB_4-24 release branch:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.64.64.d-Fedora8/tests_from_Twente_moa/list.out.00.html
## Comment 9677
Date: 2008-07-16 06:41:21 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Niels fixed wrong stable output.
Thanks!
## Comment 9678
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1982220 at http://sourceforge.net/support/tracker.php?aid=1982220
| M4: test tests/from_Twente/moa/Tests/list.milS fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1710/comments | 0 | 2020-11-30T09:53:28Z | 2024-06-27T11:30:40Z | https://github.com/MonetDB/MonetDB/issues/1710 | 753,328,300 | 1,710 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-02 04:35:39 +0200
From: Wouter Alink <<alink>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-04-07 11:00:34 +0200
## Comment 9664
Date: 2008-06-02 16:35:39 +0200
From: Wouter Alink <<alink>>
The following script crashes MonetDB in about 20 steps... (0.24, preJune, 28 may 2008)
QUERY='element { "test" } { for $i in 1 to 100000000 return <aap/> }'
QUERY2='pf:add-doc("/tmp/tempdoc.xml","tempdoc.xml")'
QUERY3='pf:del-doc("tempdoc.xml")'
create a large temporary document
time echo $QUERY | mclient -lxq > /tmp/tempdoc.xml;
n=0;
while [ "$n" -ne "100" ]
do
echo "Iter $n"
shred document
mclient -lxq -s $QUERY2 &
MAPI_PID=$!
do not allow mclient enough time to finish shredding
sleep .01
kill $MAPI_PID
remove document again (should fail, as it was never shredded completely)
echo $QUERY3 | mclient -lxq
n=$(($n + 1))
sleep 2
done
## Comment 9665
Date: 2008-06-03 18:29:49 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
WARNING:
DO *NOT* TRY THIS AT HOME!
Already the first query to "create a large temporary document" will make Mserver grow to >> 20 GB !
Is indeed such a huge document required to reproduce the problem???
## Comment 9666
Date: 2008-06-03 18:39:13 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
How does Mserver crash, i.e., is there any message, and if so, which one?
(Such info always helps analysis & debugging a lot ...)
## Comment 9667
Date: 2008-06-03 18:56:07 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Ok, in my 8 GB Fedora 8 desktop, Mserver survives the script with documents of 100000 & 1000000 nodes (0.58 MB & 5.8 MB),
but indeed crashes with a
*** glibc detected *** Mserver: double free or corruption (fasttop): 0x0000000001208e90 ***
after 17 Iterations with a document of 10000000 nodes (58 MB).
See attached logs for details.
Further analysis pending.
Any help, ideas, suggestions are more than welcome!
File Added: client.1000000.log
## Comment 9668
Date: 2008-06-03 18:56:23 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
File Added: server.1000000.log
## Comment 9669
Date: 2008-06-03 18:56:39 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
File Added: client.10000000.log
## Comment 9670
Date: 2008-06-03 18:56:54 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
File Added: server.10000000.log
## Comment 9671
Date: 2008-06-04 15:37:22 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
stefan, i wasn't trying it at home ;)
i just needed some document, for which it was guaranteed that the kill signal would arrive earlier than that the shred-doc completed, and it seemed that this one would do the trick :)
## Comment 9672
Date: 2008-12-12 00:24:59 +0100
From: @peterboncz
If I understand correctly, killing the Mserver resulted in a SEGV?
I tried to reproduce this in various ways, killing Mserver while shredding, but could not reproduce this.
## Comment 9673
Date: 2009-02-17 01:40:21 +0100
From: @drstmane
re-opened to remind us that we should consider adding a test.
## Comment 9674
Date: 2009-04-07 11:00:34 +0200
From: @peterboncz
will add a test that adds a large invalid document to a collection
## Comment 9675
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1982210 at http://sourceforge.net/support/tracker.php?aid=1982210
| XQ: crash when shredding is interrupted | https://api.github.com/repos/MonetDB/MonetDB/issues/1709/comments | 0 | 2020-11-30T09:53:25Z | 2024-06-28T13:30:10Z | https://github.com/MonetDB/MonetDB/issues/1709 | 753,328,267 | 1,709 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-02 03:14:55 +0200
From: Wouter Alink <<alink>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-06-05 01:45:17 +0200
## Comment 9653
Date: 2008-06-02 15:14:55 +0200
From: Wouter Alink <<alink>>
MonetDB/XQuery slows down after each query. It seems to be related to the complexity of the query. If running a simple query (for example "1+1") 10000 times, the first time it executes in .01 second. Then the execution time gradually increases. The last time it executes in .05 seconds. Only restarting mserver seems to reduce the execution time again to .01
The following script illustrates the problem:
n=0;
while [ $n -le 10000 ]
do
if [ $(($n % 100)) -eq 0 ]
then
clear
echo "Iteration $n"
time echo '1+1' | mclient -lxq > /dev/null;
fi
echo '1+1' | mclient -lxq > /dev/null;
n=$(($n + 1))
done
Is this expected behavior? (i know that 10000 times executing 1+1 is not really a good example, but the same behavior is observed with more complex queries)
i'm using: MonetDB-preJune supersourcetarball (28-may-2008), Fedora Core 8, 64bit-oid
## Comment 9654
Date: 2008-06-03 17:18:24 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
At least with the tiny "1+1" query, I cannot reproduce the problem; time per query stays at .01 sec:
========
$ n=0 ; while [ $n -le 10000 ] ; do if [ $(($n % 1000)) -eq 0 ] ; then echo "`date` Iteration $n" ; echo '1+1' | time mclient -lx -t >/dev/null ; fi ; echo '1+1' | mclient -lx -t >/dev/null ; n=$(($n + 1)) ; done
Tue Jun 3 16:49:16 CEST 2008 Iteration 0
0.00user 0.00system 0:00.01elapsed 26%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+577minor)pagefaults 0swaps
Tue Jun 3 16:49:28 CEST 2008 Iteration 1000
0.00user 0.00system 0:00.01elapsed 27%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+577minor)pagefaults 0swaps
Tue Jun 3 16:49:39 CEST 2008 Iteration 2000
0.00user 0.00system 0:00.01elapsed 36%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+577minor)pagefaults 0swaps
Tue Jun 3 16:49:51 CEST 2008 Iteration 3000
0.00user 0.00system 0:00.01elapsed 30%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+577minor)pagefaults 0swaps
Tue Jun 3 16:50:02 CEST 2008 Iteration 4000
0.00user 0.00system 0:00.01elapsed 20%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+577minor)pagefaults 0swaps
Tue Jun 3 16:50:14 CEST 2008 Iteration 5000
0.00user 0.00system 0:00.01elapsed 36%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+578minor)pagefaults 0swaps
Tue Jun 3 16:50:25 CEST 2008 Iteration 6000
0.00user 0.00system 0:00.01elapsed 30%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+577minor)pagefaults 0swaps
Tue Jun 3 16:50:37 CEST 2008 Iteration 7000
0.00user 0.00system 0:00.01elapsed 10%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+577minor)pagefaults 0swaps
Tue Jun 3 16:50:49 CEST 2008 Iteration 8000
0.00user 0.00system 0:00.01elapsed 20%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+577minor)pagefaults 0swaps
Tue Jun 3 16:51:00 CEST 2008 Iteration 9000
0.00user 0.00system 0:00.01elapsed 20%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+578minor)pagefaults 0swaps
Tue Jun 3 16:51:12 CEST 2008 Iteration 10000
0.00user 0.00system 0:00.01elapsed 30%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+577minor)pagefaults 0swaps
========
The above log actually represents the 3rd or 4th 10k query on on the same Mserver session, i.e., I actually executed 30k-40k queries without any visible performance degradation...
## Comment 9655
Date: 2008-06-04 10:37:47 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
This is an interesting observation, but I really cant think from where to start looking for the problem. Is it true that this delay can be an OS accumulate overhead? For the more complex queries, do you see an increase of only few milliseconds (e.g. .04 milliseconds) or this delay is increasing with the increase of the complexity of the query?
Thank you,
lefteris
## Comment 9656
Date: 2008-06-04 15:30:05 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
i tried it again with the nightly build, and again, the same behavior as i reported earlier occured.
the execution time seems to gradually increase over time.
the following steps were taken:
-installed using "monetdb-install.sh --enable-xquery"
-deleted the dbfarm and log folders
-started mserver with: Mserver --dbinit="module(pathfinder);" --set xquery_backend=algebra
p.s. i perhaps forgot to mention that i was testing the algebra version, the behavior does not occur with the mps frontend.
## Comment 9657
Date: 2008-06-04 18:17:50 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Indeed, the fact that you use the algebra back-end (Mserver --set xquery_backend=algebra) and not the (still default) milprint_summer back-end is the crucial info.
With the algebra back-end I can reproduce your slow-down, as the attached logs show.
In fact, after a slowly degrading sequence of 10000 "1+1" queries via the algebra back-end, querying the same running server using the milprint_summer back-end via `mclient -lx -g` is fast (~0.1 sec), again ...
Also, with the algebra back-end, the Mserver seem to grow (leak?) *less* than with the milprint_summer back-end... !???
Hence, the problem seems to be in the (embedded) algebra compiler, but I have absolutely no idea what is/causes the problem ...
File Added: ALG.log
## Comment 9658
Date: 2008-06-04 18:18:14 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
File Added: MPS.log
## Comment 9659
Date: 2008-06-04 21:25:48 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
I think the measurements were to coarse. On my maschine (see attached log ALG.jr.log) there are some few query runs that take really long (see at 4000 -> 4100) whereas most of the other runs seem to evaluate the query in the same time (first 1000 and last 1000 require each 24 seconds). Note Mserver was the only active process running with 97% CPU usage all the time during the test.
One wild guess what could go wrong is that perhaps the query cache gets to large at some point in time...
File Added: ALG.jr.log
## Comment 9660
Date: 2008-06-04 22:57:16 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
find attached the results of
n=0 ; while [ $n -le 10000 ] ; do printf "%5d " $n ; { time mclient -glx -s'1+1' >/dev/null ; } 2>&1 | grep real ; n=$(($n + 1)) ; done > /tmp/MPS.StM.fine.log ; sort -t. -n -k2 /tmp/MPS.StM.fine.log > /tmp/MPS.StM.fine.log.hist
n=0 ; while [ $n -le 10000 ] ; do printf "%5d " $n ; { time mclient -Glx -s'1+1' >/dev/null ; } 2>&1 | grep real ; n=$(($n + 1)) ; done > /tmp/ALG.StM.fine.log ; sort -t. -n -k2 /tmp/ALG.StM.fine.log > /tmp/ALG.StM.fine.log.hist
tar -cpzf StM.fine.log.tgz *.StM.fine.log*
and
gnuplot> plot "< sed 's|0m||' ALG.StM.fine.log" using 1:3 title 'ALG' with lines , "< sed 's|0m||' MPS.StM.fine.log" using 1:3 title 'MPS' with lines
... basically, there is a clear tendency with ALG that is not there with MPS --- why? --- "someone" need to profile "where time goes" ...
File Added: StM.fine.log.tgz
## Comment 9661
Date: 2008-06-04 23:00:06 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
forgot to mention:
on my Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
with MPS, Mserver starts at ~40% CPU and never exceeds ~45% CPU during the 10000 queries;
with ALG, Mserver starts at ~40% CPU and then continuously grow towards ~90% CPU at the end of the 10000 query sequence.
File Added: StM.fine.log.pdf
## Comment 9662
Date: 2008-06-05 01:45:17 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Fixed in CVS (XQuery_0-24 release branch):
Profiling turned indeed out to be the key to the problem:
I ran Mserver in valgrind and fired 1000 trivial "1+1" XQuery queries, once using MPS and once using ALG.
kcachegrind revealed that ALG spent *most* of its time in loading and dropping MIL modules!
A quick look at the code than revealed that in case of ALG, each query was preceded by
"
module(pathfinder);
module(mkey);
".
Well, this might (have) be(en) handy to run, e.g., `pf -A | Mserver` or `pf -A | mclient -lmil`, but Mserver is apparently not optimized for just loading and dropping modules tenth od thousands of times.
Simply removing the above to statements --- assuming that module pathfinder (and hence module mkey) is loaded when the server is started via `Mserver --dbinit='module(pathfinder);'` --- makes the 10000 queries perform equally fast with MPS and ALG without any performance degradation.
I hope that everybody can live with changing `Mserver` into `Mserver --dbinit='module(pathfinder);'` when using Pathfinder/XQuery.
## Comment 9663
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1982101 at http://sourceforge.net/support/tracker.php?aid=1982101
| XQ: slowing down | https://api.github.com/repos/MonetDB/MonetDB/issues/1708/comments | 0 | 2020-11-30T09:53:22Z | 2024-06-27T11:30:38Z | https://github.com/MonetDB/MonetDB/issues/1708 | 753,328,222 | 1,708 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-02 12:15:22 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2009-07-31 03:09:16 +0200
## Comment 9646
Date: 2008-06-02 12:15:22 +0200
From: @drstmane
These still need to be checked/analyzed:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/runtime/printEmptySeq.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/id-function_fails_to_locate_some_kinds_of_nodes.SF-1698498.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQUF_R/Q5a.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/bool7.out.00.html
## Comment 9647
Date: 2008-06-02 18:07:58 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
for
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG10
3/GNU.64.64.d-Fedora8/tests_XQuery/bool7.out.00.html
see
[ 1982310 ] PF/alg: "boolean (())" skipped in complex query
https://sourceforge.net/tracker/index.php?func=detail&aid=1982310&group_id=56967&atid=482468
## Comment 9648
Date: 2008-06-03 12:57:02 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQUF_R/Q5a.out.00.html
appears to be fixed, now.
## Comment 9649
Date: 2008-10-11 13:20:52 +0200
From: @drstmane
new URLs of the two remaining problems are
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/runtime/printEmptySeq.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugTracker/id-function_fails_to_locate_some_kinds_of_nodes.SF-1698498.out.00.html
## Comment 9650
Date: 2009-02-14 19:04:30 +0100
From: @drstmane
Only this one seems to remain:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/runtime/printEmptySeq.out.00.html
## Comment 9651
Date: 2009-07-31 15:09:16 +0200
From: @drstmane
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/runtime/printEmptySeq.out.00.html
has been fixed by Sjoerd.
Closing.
## Comment 9652
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981918 at http://sourceforge.net/support/tracker.php?aid=1981918
| PFalg: more test that work with MPS but fail with ALG | https://api.github.com/repos/MonetDB/MonetDB/issues/1707/comments | 0 | 2020-11-30T09:53:20Z | 2024-06-27T11:30:37Z | https://github.com/MonetDB/MonetDB/issues/1707 | 753,328,188 | 1,707 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-02 11:33:21 +0200
From: @drstmane
To: Lefteris Sidirourgos <<lsidir>>
Version: -- development
Last updated: 2008-06-06 12:17:37 +0200
## Comment 9643
Date: 2008-06-02 11:33:21 +0200
From: @drstmane
With the Algebra back-end, the behavior of test pathfinder/tests/XQuery/Tests/replace05.xq differs from that of MPS:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/replace05.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/replace05.err.00.html
Lefteris,
I recall vague that we might have talked about this one earlier but I don't recall the details ...
## Comment 9644
Date: 2008-06-06 12:17:37 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
fixed in the june 2008 stable branch.
See log message of commit for details:
We do not support variables in replacement strings for both MPS and Algebra
## Comment 9645
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981873 at http://sourceforge.net/support/tracker.php?aid=1981873
| PF/alg: behavior of test replace05 differs from MPS | https://api.github.com/repos/MonetDB/MonetDB/issues/1706/comments | 0 | 2020-11-30T09:53:17Z | 2024-06-27T11:30:36Z | https://github.com/MonetDB/MonetDB/issues/1706 | 753,328,161 | 1,706 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-02 10:49:10 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2008-06-08 03:33:44 +0200
## Comment 9637
Date: 2008-06-02 10:49:10 +0200
From: @drstmane
With the Algebra back-end, test pathfinder/Tests/BugTracker/immune_for_updates.SF-1766259.xq.in fails with
ERROR = !ERROR: ordered left and right head columns (iters) expected.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/immune_for_updates.SF-1766259.err.00.html
Since the test uses fn:subsequence(), this might be related to
[ 1981800 ] PF/alg: fn:subsequence() returns empty result
https://sourceforge.net/tracker/index.php?func=detail&aid=1981800&group_id=56967&atid=482468
## Comment 9638
Date: 2008-06-03 11:55:24 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
The original error message is gone.
The query or better the queries however still fail because exactly-one() is called with an empty input sequence in the second to last query.
If I replace the original second to last query
let $todo := subsequence(doc("prepared49736.data")/XIRAF/item[*], 1537,256)
let $dest := for $i in doc("test10.xml")//*[@xid]
where some $k in $todo/@xid satisfies $k = $i/@xid
return $i
for $item in $todo
return
do insert $item/*
into exactly-one($dest[@xid[. = $item/@xid]])
with the query
let $todo := subsequence(doc("prepared49736.data")/XIRAF/item[*], 1537,256)
let $dest := for $i in doc("test10.xml")//*[@xid]
where some $k in $todo/@xid satisfies $k = $i/@xid
return $i
for $item at $b in $todo
return
($b, $dest[@xid[. = $item/@xid]], "
")
that prints the input for the exactly-one call for each iteration then iterations 1-65 and 67-69 contain no join results.
As I'm not sure what happens I reassign the bug to the ones that were originally involved (Sjoerd, Stefan, and Wouter).
## Comment 9639
Date: 2008-06-03 16:22:22 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
extended test for debugging
before the
"let $todo := subsequence(doc("prepared49736.data")/XIRAF/item[*], 1281,256) ..." update query,
the updated document seems to have the same status with both MPS & ALG;
after this update query, the status with ALG differs from the one with MPS,
resulting in the error with ALG in the
"let $todo := subsequence(doc("prepared49736.data")/XIRAF/item[*], 1537,256)" update query
as analyzed by JanR.
## Comment 9640
Date: 2008-06-08 15:33:44 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Appears to be fix by Lefteris' latest Algebra update re-order fixes/changes.
## Comment 9641
Date: 2008-06-08 16:18:33 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Even though Lefteris' reversal of inserts already seemed to fix this bug, that wasn't actually a fix for this.
If you change the subsequence quoted by Stefan into a reverse(subsequence(...()), both MPS and ALG fail the test, although the order of updates shouldn't matter in this test since all updates are to different nodes.
The real fix for this test was to add a couple of copy() calls.
Added test tests/BugTracker/immune_for_updates.SF-1981852 which is like immune_for_updates.SF-1766259, except that it uses reverse(subsequence(...)).
## Comment 9642
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981852 at http://sourceforge.net/support/tracker.php?aid=1981852
| PF/alg: test immune_for_updates.SF-1766259 fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1705/comments | 0 | 2020-11-30T09:53:15Z | 2024-06-27T11:30:35Z | https://github.com/MonetDB/MonetDB/issues/1705 | 753,328,125 | 1,705 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-02 10:36:41 +0200
From: @drstmane
To: Lefteris Sidirourgos <<lsidir>>
Version: -- development
Last updated: 2008-06-06 11:18:37 +0200
## Comment 9631
Date: 2008-06-02 10:36:41 +0200
From: @drstmane
With the Algebra back-end the order of nodes in the result of several tests differs from that produced by MPS.
I am not sure whether any / which of these order differences can be excepted as "correct" --- to me, none seems to be due to simple (non-specified) attribute order.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugDay_2005-12-19_0.9.3/doc-order_in_attributes.SF-1328671.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/corrupt_after_update.SF-1706640.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQ_NS/Q1.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQ_XMP/Q10.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_WebSite/voc3.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_WebSite/distinct_values_bug.SF-1210748.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/transient_upward_steps.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/except3.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/ns3.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/ns4.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/ns6.out.00.html
## Comment 9632
Date: 2008-06-02 21:39:09 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
The order for all tests except 'corrupt_after_update' is now approved.
Lefteris could you please check for test http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/corrupt_after_update.SF-1706640.out.00.html if the insert order is defined and if yes if it is correct.
## Comment 9633
Date: 2008-06-03 13:22:46 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
In addition to
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/corrupt_after_update.SF-1706640.out.00.html
also
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_WebSite/voc3.out.00.html
and
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_WebSite/distinct_values_bug.SF-1210748.out.00.html
still differ.
## Comment 9634
Date: 2008-06-03 14:10:30 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Approved Algebra-specific order of distinct-values() for
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_WebSite/voc3.out.00.html
and
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_WebSite/distinct_values_bug.SF-1210748.out.00.html
Hence, only
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/corrupt_after_update.SF-1706640.out.00.html
is still open.
## Comment 9635
Date: 2008-06-06 23:18:37 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
Fixed in stable branch.
Now, at runtime we correctly reverse the order of insert into as last and insert before.
Closing the bug.
## Comment 9636
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981844 at http://sourceforge.net/support/tracker.php?aid=1981844
| PF/alg: result order differs from MPS | https://api.github.com/repos/MonetDB/MonetDB/issues/1704/comments | 0 | 2020-11-30T09:53:12Z | 2024-06-27T11:30:34Z | https://github.com/MonetDB/MonetDB/issues/1704 | 753,328,094 | 1,704 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-02 10:25:45 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-06-05 11:15:03 +0200
## Comment 9625
Date: 2008-06-02 10:25:45 +0200
From: @drstmane
With the Algebra back-end, test pathfinder/tests/Update/Tests/symm.xq.in fails with
ERROR = !ERROR: illegal expression in `do replace' clause
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_Update/symm.err.00.html
## Comment 9626
Date: 2008-06-02 15:00:15 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
After some fixes this test now works for me -- the result however seems to be incorrect (re-assigning to the master of algebra updates: Lefteris).
## Comment 9627
Date: 2008-06-03 13:24:41 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
The TestWeb still shows the original error:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_Update/symm.err.00.html
## Comment 9628
Date: 2008-06-05 18:39:12 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
I just checked in what was wrong from my part in this test. There was no loop around in updates so this test was failing because of a conflict. However, yesterday the illegal expression error re-appear:) I am re-assigning this to Jan since he already fixed it once and it will be easy for him to re-fix it.
## Comment 9629
Date: 2008-06-05 23:15:03 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
This turned out to be related to incorrect aggregate rewrites (see http://sourceforge.net/support/tracker.php?aid=1981827).
Fixed version is in the CVS.
## Comment 9630
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981831 at http://sourceforge.net/support/tracker.php?aid=1981831
| PF/alg: test symm: illegal expression in `do replace' clause | https://api.github.com/repos/MonetDB/MonetDB/issues/1703/comments | 0 | 2020-11-30T09:53:10Z | 2024-06-27T11:30:33Z | https://github.com/MonetDB/MonetDB/issues/1703 | 753,328,069 | 1,703 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-02 10:21:41 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-06-02 06:38:04 +0200
## Comment 9622
Date: 2008-06-02 10:21:41 +0200
From: @drstmane
With the Algebra back-end, the if-then-else evaluation seems to differ from MPS. With MPS, only the qualifying branch is evaluated at runtime. With ALG, is seems as if both branches are "silently" eveluated, but only the qualifying branch's results (actions) are used/effective --- at least that's what the failure of test
pathfinder/tests/BugTracker/Tests/replace-corrupts.SF-1758902.xq.in seems to suggest: with ALG, the first if-then-else seems to evaluate the then branch although $orig is empty (and hence exists($orig) is false), correctly causing the do replace to fail on the implicitly called fn:exactly-one(); cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/replace-corrupts.SF-1758902.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/replace-corrupts.SF-1758902.out.00.html
## Comment 9623
Date: 2008-06-02 18:38:03 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
Removed incorrect aggregate rewrite.
## Comment 9624
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981827 at http://sourceforge.net/support/tracker.php?aid=1981827
| PF/alg: if-then-else evaluation differs from MPS? | https://api.github.com/repos/MonetDB/MonetDB/issues/1702/comments | 0 | 2020-11-30T09:53:07Z | 2024-06-27T11:30:33Z | https://github.com/MonetDB/MonetDB/issues/1702 | 753,328,034 | 1,702 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-02 09:58:51 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-06-02 02:01:35 +0200
## Comment 9618
Date: 2008-06-02 09:58:51 +0200
From: @drstmane
With the Algebra back-end, fn:subsequences seem to return an empty result; at least in:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/NULL_BAT_in_serializer.SF-1694814b.out.00.html
## Comment 9619
Date: 2008-06-02 10:49:50 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
See also
[ 1981852 ] PF/alg: test immune_for_updates.SF-1766259 fails
https://sourceforge.net/tracker/index.php?func=detail&aid=1981852&group_id=56967&atid=482468
## Comment 9620
Date: 2008-06-02 14:01:34 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
MPS and stable output is incorrect. Quoting the specification: 'The first item of a sequence is located at position 1, not position 0.'
Patched the test to check whatever it was supposed to check.
## Comment 9621
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981800 at http://sourceforge.net/support/tracker.php?aid=1981800
| PF/alg: fn:subsequence() returns empty result | https://api.github.com/repos/MonetDB/MonetDB/issues/1701/comments | 0 | 2020-11-30T09:53:05Z | 2024-06-27T11:30:32Z | https://github.com/MonetDB/MonetDB/issues/1701 | 753,328,012 | 1,701 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-02 09:35:00 +0200
From: @drstmane
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2008-06-03 03:28:12 +0200
## Comment 9611
Date: 2008-06-02 09:35:00 +0200
From: @drstmane
With the Algebra back-end, test pathfinder/tests/XQuery/Tests/cast7.xq fails with
ERROR = !ERROR: FORG0001. casting from string to boolean failed.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/cast7.err.00.html
## Comment 9612
Date: 2008-06-02 17:34:23 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
The output was incorrect -- Approved correct stable output.
## Comment 9613
Date: 2008-06-03 11:28:17 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
With the corrected stable output, the MS test now fails as MPS is apparently wrong.
Do we care about this, and hence should try to fix MPS?
## Comment 9614
Date: 2008-06-03 11:29:32 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora8/tests_XQuery/cast7.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora8/tests_XQuery/cast7.err.00.html
## Comment 9615
Date: 2008-06-03 11:59:57 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
I won't fix MPS.
## Comment 9616
Date: 2008-06-03 15:28:12 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Algebra is right and output is fixed.
For the MPS bug see
[ 1983567 ] PF/mps: allows incorrect cast from string to boolean
https://sourceforge.net/tracker/index.php?func=detail&aid=1983567&group_id=56967&atid=482468
## Comment 9617
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981784 at http://sourceforge.net/support/tracker.php?aid=1981784
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/alg: test cast7: "casting from string to boolean failed" | https://api.github.com/repos/MonetDB/MonetDB/issues/1700/comments | 0 | 2020-11-30T09:53:02Z | 2024-06-28T13:30:10Z | https://github.com/MonetDB/MonetDB/issues/1700 | 753,327,993 | 1,700 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-02 09:32:18 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-06-02 05:19:48 +0200
## Comment 9608
Date: 2008-06-02 09:32:18 +0200
From: @drstmane
With the Algebra back-end, test pathfinder/tests/XQuery/Tests/sum11.xq fails with
ERROR = !fatal error: attribute 'item' with type '0x2000' not found in environment
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/sum11.err.00.html
## Comment 9609
Date: 2008-06-02 17:19:48 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
Lost some type bits in the type assertion operator. Fixed in CVS.
## Comment 9610
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981783 at http://sourceforge.net/support/tracker.php?aid=1981783
| PF/alg: test sum11 fails: "attribute not found in env." | https://api.github.com/repos/MonetDB/MonetDB/issues/1699/comments | 0 | 2020-11-30T09:53:00Z | 2024-06-27T11:30:30Z | https://github.com/MonetDB/MonetDB/issues/1699 | 753,327,971 | 1,699 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-02 09:29:29 +0200
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-04-07 10:30:19 +0200
## Comment 9603
Date: 2008-06-02 09:29:29 +0200
From: @drstmane
With the Algebra back-end, some typeswitch tests fail with
!fatal error: aborted too deep recursion
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/typeswitch3.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/typeswitch4.err.00.html
## Comment 9604
Date: 2008-06-02 16:18:45 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
The resulting query plan is quite big. To successfully complete the MIL generation a recursion depth of 425 is required for these queries.
Re-assigning to the creator of PFrecursion_fence(): Peter.
## Comment 9605
Date: 2009-02-14 18:10:29 +0100
From: @drstmane
The problem has "disappeared" from all platforms except on OpenSolaris x86 with GNU gcc:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.32.32.d.1-SunOS5.11/tests_XQuery/typeswitch3.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.32.32.d.1-SunOS5.11/tests_XQuery/typeswitch4.err.00.html
## Comment 9606
Date: 2009-04-07 10:30:19 +0200
From: @peterboncz
this is correct behavior AFAIC.
the recursion fence has to draw a line somewhere.
## Comment 9607
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981779 at http://sourceforge.net/support/tracker.php?aid=1981779
| PF/alg: typeswitch tests fail: "aborted too deep recursion" | https://api.github.com/repos/MonetDB/MonetDB/issues/1698/comments | 0 | 2020-11-30T09:52:57Z | 2024-06-28T13:30:09Z | https://github.com/MonetDB/MonetDB/issues/1698 | 753,327,931 | 1,698 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-02 09:10:21 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2010-07-09 15:43:26 +0200
## Comment 9597
Date: 2008-06-02 09:10:21 +0200
From: @drstmane
With the Algebra back-end, several tests fail with
ERROR = !fatal error: Mapping unique name to an original name failed. (unique =..., free=(NULL))
E.g.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQ_R/Q05o.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQUF_AddressBook/Q1x.err.00.html
## Comment 9598
Date: 2008-06-02 13:00:41 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
This bug report probably describes the problem best.
For some queries the rewrites are so good that we run out of bit-encoded
column names. A complete overhaul of the optimization and property
inference phases is needed here.
For the release I checked in a fallback solution that at least avoids
errors.
For the head the resolution is pending.
This bug report supersedes
http://sourceforge.net/tracker/index.php?func=detail&aid=1981491&group_id=56967&atid=482468
http://sourceforge.net/tracker/index.php?func=detail&aid=1908822&group_id=56967&atid=482468
## Comment 9599
Date: 2008-06-02 13:58:33 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
This bug report probably describes the problem best.
For some queries the rewrites are so good that we run out of bit-encoded
column names. A complete overhaul of the optimization and property
inference phases is needed here.
For the release I checked in a fallback solution that at least avoids
errors.
For the head the resolution is pending.
This bug report supersedes
http://sourceforge.net/tracker/index.php?func=detail&aid=1981491&group_id=56967&atid=482468
http://sourceforge.net/tracker/index.php?func=detail&aid=1908822&group_id=56967&atid=482468
## Comment 9600
Date: 2008-08-14 11:05:57 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
Another affect of this bug is described in bug report: [ 1983333 ] PF/alg: tests/W3C_use_cases/XQUF/AddressBook/check_doc fails
<https://sourceforge.net/tracker/index.php?func=detail&aid=1983333&group_id=56967&atid=482468>
In reality, test tests/W3C_use_cases/XQUF/AddressBook/Q1x is failing in the stable version only for 32 bit machines since the workaround works for 64-bit machines, while in the current version fails with the same message as this bug report:
!fatal error: Mapping unique name to an original name failed. (unique =item3396, free=(NULL))
## Comment 9601
Date: 2008-08-14 11:10:59 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
For completeness:
in the Stable release, test tests/W3C_use_cases/XQUF/AddressBook/Q1x fails on 32-bit systems (only) with
QUERY = for $a in doc("archive.xml")/archived-agenda/entry,
ERROR = !fatal error: aborted too deep recursion
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.32.32.d.1-Fedora9/tests_W3C_use_cases_XQUF_AddressBook/Q1x.err.00.html
## Comment 9602
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981762 at http://sourceforge.net/support/tracker.php?aid=1981762
## Comment 14343
Date: 2010-07-09 15:43:26 +0200
From: @sjoerdmullender
*** Bug #1626 has been marked as a duplicate of this bug. ***
| PF/alg: "Mapping unique name to an original name failed." | https://api.github.com/repos/MonetDB/MonetDB/issues/1697/comments | 0 | 2020-11-30T09:52:54Z | 2024-06-27T11:30:28Z | https://github.com/MonetDB/MonetDB/issues/1697 | 753,327,893 | 1,697 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-02 08:54:45 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-06-02 11:53:53 +0200
## Comment 9593
Date: 2008-06-02 08:54:45 +0200
From: @drstmane
With the Algebra back-end, some tests fail with:
ERROR = !ERROR: unknown variable 'err'
See, e.g.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/insert_large_doc.SF-1726954.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/swizzle-bug.SF-1760811.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/insert-new-page.SF-1854215.err.00.html
## Comment 9594
Date: 2008-06-02 15:14:41 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
The MIL variable 'err' only appears in some prologue & epilogue code in MPS. It looks like this prologue & epilogue stuff is in some cases not compatible with the algebra generated code (that also evaluates but then ignores this additional MIL code).
Re-assigning to a runtime expert with more knowledge about this magic :)
## Comment 9595
Date: 2008-06-02 23:53:53 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed typo in pathfinder.mx's PROC ws_newpage() to make sure that (local) variable "err" is properly declared:
"var page_id := 0@0; err := CATCH(page_id := __runtime_newpage(runtime));"
|
V
"var page_id := 0@0, err := CATCH(page_id := __runtime_newpage(runtime));"
## Comment 9596
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981750 at http://sourceforge.net/support/tracker.php?aid=1981750
| PF/alg: some tests fail with "unknown variable 'err'" | https://api.github.com/repos/MonetDB/MonetDB/issues/1696/comments | 0 | 2020-11-30T09:52:51Z | 2024-06-27T11:30:27Z | https://github.com/MonetDB/MonetDB/issues/1696 | 753,327,863 | 1,696 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-02 08:43:24 +0200
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-11-16 11:38:08 +0100
## Comment 9578
Date: 2008-06-02 08:43:24 +0200
From: @drstmane
With the Algebra back-end, some error messages seem to differ from the milprint_summer back-end.
In case this is intended, we should (must) approved the Algebra-specific output
(as I already did with
tests/BugDay_2005-12-19_0.9.3/Tests/tag_name_validation.SF-1221984.stable.err{,.Algebra}
tests/BugDay_2005-12-19_0.9.3/Tests/zero-or-one_merged-union.SF-1221336.stable.err{,.Algebra}
).
Otherwise, we should (must) fix the error messages.
Examples:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_i18n/bad-001.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/matches02.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/matches01.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/attr_err.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/div.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/cast2.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQUF_R/Q4.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugsViaSourgeforce/invisible_error_messages.SF-1409122.err.00.html
## Comment 9579
Date: 2008-06-02 15:57:08 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
Fixed attr_err.err, cast2.err, Q4.out, and invisible_error_messages.SF-
1409122.err.
Still remaining:
bad-001.err (could it be that mclient has problems with the characters?)
matches (CATCH is missing in the code generation)
div (check for denominator in milgen is missing)
Re-assigned to Lefteris as he can fix the MIL specific problems (and he started fn:matches).
## Comment 9580
Date: 2008-06-03 11:33:27 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
With the updated error message of invisible_error_messages.SF-
1409122.stable.err, the MPS test now fails
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.32.d-Fedora8/tests_BugsViaSourgeforce/invisible_error_messages.SF-1409122.err.00.html
## Comment 9581
Date: 2008-06-03 13:43:36 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Still differing:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_i18n/bad-001.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/matches02.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/matches01.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/div.err.00.html
## Comment 9582
Date: 2008-06-09 15:11:48 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
The following tests are now producing the correct error msg:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/matches02.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/matches01.err.00.html
## Comment 9583
Date: 2008-06-12 14:34:08 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
Lower the priority since the remaining two different error messages are not important
## Comment 9584
Date: 2009-02-14 18:41:22 +0100
From: @drstmane
For the records:
Only one seems to remain:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_XQuery/div.err.00.html
## Comment 9585
Date: 2009-02-14 19:20:36 +0100
From: @drstmane
for this one, the error message appears to be identical (now) with ALG & MPS, but differs from what it used to be, giving less information than before:
ALG:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.32.32.d.1-Debian4.0/tests_i18n/bad-001.err.00.html
MPS:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.32.32.d.1-Debian4.0/tests_i18n/bad-001.err.00.html
## Comment 9586
Date: 2009-11-12 10:37:16 +0100
From: @peterboncz
after my latest pass over the web, such issues should be gone
## Comment 9587
Date: 2009-11-14 22:37:07 +0100
From: @drstmane
The issues is not gone, yet.
The question is still, why the same query triggers different error messages on different systems, and/or whether this matters or whether we just accept the differences as given.
We seems to get either
"
ERROR = !parse error: syntax error, unexpected invalid_character on line 5, column 19 (next token is `�')
!parse error: XQuery parsing failed
"
or simply
"
ERROR = ! !parse error: XQuery parsing failed
"
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_i18n/bad-001.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora10/tests_i18n/bad-001.err.00.html
## Comment 9588
Date: 2009-11-16 23:23:30 +0100
From: @peterboncz
Stefan, I'd say this seems to have to do with different locales on different test machines.
## Comment 9589
Date: 2009-11-16 23:38:08 +0100
From: @drstmane
Thanks.
I approved the Linux-specific error message.
## Comment 9590
Date: 2009-11-17 09:31:35 +0100
From: @sjoerdmullender
Actually, I think this does show a (small) problem in the compiler: when confronted with a multi-byte character that it doesn't expect, it only prints the first byte. The compiler should treat the document as a sequence of Unicode code point, not as a sequence of bytes.
## Comment 9591
Date: 2009-11-17 10:11:17 +0100
From: @sjoerdmullender
I now have a patch ready for the problem I identified in my last comment. It's too late for the release build I'm doing now, so if this patch proofs to be good, it'll come in the next release.
The error message I now get contains the complete invalid character, not just the first byte of its UTF-8 encoding.
## Comment 9592
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981735 at http://sourceforge.net/support/tracker.php?aid=1981735
| PF/alg: some error messages differ from PF/mps | https://api.github.com/repos/MonetDB/MonetDB/issues/1695/comments | 0 | 2020-11-30T09:52:49Z | 2024-06-27T11:30:26Z | https://github.com/MonetDB/MonetDB/issues/1695 | 753,327,820 | 1,695 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-02 12:17:30 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-06-02 12:55:38 +0200
## Comment 9574
Date: 2008-06-02 00:17:30 +0200
From: @drstmane
With the Algebra back-end empty nodes are often serialized as "<x></x>" instead of "<x/>" (as with the MPS back-end).
I'm no sure, whether we should/must treat this as bug and (try to) fix the serialization, or whether we could rather simply accept this (minor?) difference as correct and hence approve the Algebra-specific output.
See e.g.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugDay_2005-12-19_0.9.3/non-existent_attribute.SF-1324219.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/interpret_while-bit_nil.SF-1567021.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugsViaSourgeforce/ID.1766173.out.00.html
## Comment 9575
Date: 2008-06-02 08:46:58 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Also:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQ_XMP/Q06.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQ_R/Q02.out.00.html
## Comment 9576
Date: 2008-06-02 12:55:38 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
The serialization routine is the same. The problem is an additional textnode---see also http://sourceforge.net/tracker/index.php?func=detail&aid=1350418&group_id=56967&atid=482468.
## Comment 9577
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981522 at http://sourceforge.net/support/tracker.php?aid=1981522
This bug was marked DUPLICATE in the database it was moved from.
Changing resolution to "MOVED"
| PF/alg: serializes empty nodes as "<x></x>" iso. "<x/>" | https://api.github.com/repos/MonetDB/MonetDB/issues/1694/comments | 0 | 2020-11-30T09:52:46Z | 2024-06-28T13:30:08Z | https://github.com/MonetDB/MonetDB/issues/1694 | 753,327,788 | 1,694 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-01 11:01:03 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-06-02 10:48:03 +0200
## Comment 9571
Date: 2008-06-01 23:01:03 +0200
From: @drstmane
While working fine (also) with the Algebra back-end in the previous Feb2008 release (XQuery_0-22 branch),
test tests/W3C_use_cases/XQ/R/Tests/Q05o.xq now fails with
========
!fatal error: Mapping unique name to an original name failed. (unique =iter1094, free=(NULL))
========
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQ_R/Q05o.err.00.html
## Comment 9572
Date: 2008-06-02 10:48:03 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
That's the a problem that cannot be fixed easily (see also http://sourceforge.net/tracker/index.php?func=detail&aid=1908822&group_id=56967&atid=482468). For some queries the rewrites are so good that we run out of bit-encoded column names. A complete overhaul of the optimization and property inference phases is needed here.
For the release I checked in a fallback solution that at least avoids errors.
## Comment 9573
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981491 at http://sourceforge.net/support/tracker.php?aid=1981491
| PF/alg: test tests/W3C_use_cases/XQ/R/Q05o fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1693/comments | 0 | 2020-11-30T09:52:44Z | 2024-06-27T11:30:24Z | https://github.com/MonetDB/MonetDB/issues/1693 | 753,327,757 | 1,693 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-01 10:50:58 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-11-12 01:24:24 +0100
## Comment 9566
Date: 2008-06-01 22:50:58 +0200
From: @drstmane
While working fine (finishing in < 60 secs) in the previous Feb2008 release (XQuery_0-22 branch) with the Algebra back-end,
tests benchmarks/MBench/Tests/j0[24].xq now run into a timeout; when allowing more than the default 60 secs, the tests eventually finish (on a 8 GB machine) but Mserver grows to ~10 GB.
Possibly (probably?) join-recognition fails.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/benchmarks_MBench/qj02.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/benchmarks_MBench/qj02.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/benchmarks_MBench/qj04.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/benchmarks_MBench/qj04.err.00.html
## Comment 9567
Date: 2008-06-02 10:33:41 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
Stefan, you are right about the join-recognition --- it does not work anymore.
As this requires more changes to the compiler/optimizer (whose effects I cannot oversee) it won't make it into the release. I'll thus postpone the resolution.
## Comment 9568
Date: 2008-06-02 10:45:09 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Thanks, Jan!
I disabled the tests in the XQuery_0-24 branch.
## Comment 9569
Date: 2008-11-12 13:24:24 +0100
From: Jan Rittinger <<jan.rittinger>>
These tests now work fine -- thus closing the bug.
## Comment 9570
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981486 at http://sourceforge.net/support/tracker.php?aid=1981486
| PF/alg: tests benchmarks/MBench/qj0[24] timeout | https://api.github.com/repos/MonetDB/MonetDB/issues/1692/comments | 0 | 2020-11-30T09:52:41Z | 2024-06-28T13:30:07Z | https://github.com/MonetDB/MonetDB/issues/1692 | 753,327,722 | 1,692 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-01 10:42:58 +0200
From: @drstmane
To: @yzchang
Version: -- development
Last updated: 2008-06-05 12:59:04 +0200
## Comment 9563
Date: 2008-06-01 22:42:58 +0200
From: @drstmane
Test pathfinder/tests/XRpc/Tests/echoAll used to work fine with the previous Feb2006 release (XQuery_0-22 branch), but fails now:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora8/tests_XRpc/echoAll.out.00.html
## Comment 9564
Date: 2008-06-05 12:59:04 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed by Jennie.
Closing.
## Comment 9565
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981481 at http://sourceforge.net/support/tracker.php?aid=1981481
| PF: tests/XRpc/Tests/echoAll fails while it worked with 0.22 | https://api.github.com/repos/MonetDB/MonetDB/issues/1691/comments | 0 | 2020-11-30T09:52:39Z | 2024-06-27T11:30:22Z | https://github.com/MonetDB/MonetDB/issues/1691 | 753,327,694 | 1,691 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-01 07:18:00 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-06-02 10:18:19 +0200
## Comment 9559
Date: 2008-06-01 19:18:00 +0200
From: @drstmane
With the Algebra back-end, PFtijha tests qmil0 & qmil1 fail with
========
fatal error: attribute `iter' referenced in join not found
========
See, e.g.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/modules_pftijah/qmil0.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/modules_pftijah/qmil1.out.00.html
## Comment 9560
Date: 2008-06-02 10:18:19 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
fixed problem in proxy recognition.
@Stefan: If a test works and then starts failing with some error message like ``attribute ... not found'' then in most cases an optimization did something wrong.
## Comment 9561
Date: 2008-06-02 11:36:17 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Originator: NO
Is probably already fixed by Jan Rittinger. Await tonights tests before closing subject.
## Comment 9562
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981403 at http://sourceforge.net/support/tracker.php?aid=1981403
| PFtijah: tests qmil0 & qmil1 fail with Algebra back-end | https://api.github.com/repos/MonetDB/MonetDB/issues/1690/comments | 0 | 2020-11-30T09:52:36Z | 2024-06-27T11:30:21Z | https://github.com/MonetDB/MonetDB/issues/1690 | 753,327,658 | 1,690 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-01 05:26:07 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2008-06-02 08:36:00 +0200
## Comment 9555
Date: 2008-06-01 17:26:07 +0200
From: @drstmane
Some SQL tests that work(ed) fine with the previous "Feb2008" release (SQL_2-22 branch) fail in the latest SQL_2-24 branch --- *possibly*, they only require check and approval of modified stable output.
SQL/4:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests4103/Int.64.64.d-Fedora8/src_test_BugTracker/count_crash.SF-1918780.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests4103/GNU.32.32.d-Fedora8/src_test_BugTracker/jdbc_no_debug.SF-1739356.out.00.html
SQL/5:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests5103/GNU.32.32.d-Fedora8/src_test_BugTracker/jdbc_no_debug.SF-1739356.out.00.html
SQL/G (AlGebra):
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTestsG103/GNU.32.32.d-Fedora6/src_test_BugTracker/jdbc_no_debug.SF-1739356.out.00.html
## Comment 9556
Date: 2008-06-02 08:36:00 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
indeed only output approval, one table less in the catalog or previous tests.
## Comment 9557
Date: 2008-06-02 10:09:18 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
hmmm, the tests should actually be fixed not to use the catalog in such a way that they fail as soon as something changes there.
## Comment 9558
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981350 at http://sourceforge.net/support/tracker.php?aid=1981350
| SQL: tests fail with 2.24 that worked with 2.22 | https://api.github.com/repos/MonetDB/MonetDB/issues/1689/comments | 0 | 2020-11-30T09:52:34Z | 2024-06-27T11:30:20Z | https://github.com/MonetDB/MonetDB/issues/1689 | 753,327,624 | 1,689 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-06-01 05:12:00 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2008-06-04 11:28:03 +0200
## Comment 9552
Date: 2008-06-01 17:12:00 +0200
From: @drstmane
Loading module "sql" into mserver5 fails on Windows:
========
MonetDB server v5.6.0, based on kernel v1.24.0
Serving database 'mTests'
Compiled for i686-pc-win32/32bit with 32bit OIDs dynamically linked
Copyright (c) 1993-2008 CWI, all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Listening for connection requests on mapi:monetdb://tureluur:39649/
!MALException:MAL.getAddress:address of 'sql.sql_rank_grp' not found
!MALException:MAL.getAddress:address of 'sql.sql_rank' not found
!MALException:MAL.getAddress:address of 'sql.sql_dense_rank_grp' not found
!MALException:MAL.getAddress:address of 'sql.sql_dense_rank' not found
MonetDB/SQL module v2.24.0 loaded
function user.main():void;
clients.quit();
end main;
warning: please don't forget to set your vault key!
(see C:\cygwin\var\tmp\monet.Int.32.32.d.12408\MonetDB5\.Int.32.32.d-Windows5.1\etc\monetdb5.conf)
========
See also:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.Int.32.32.d-Windows5.1..2008.06.01_00-09-03/test510.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.Int.64.32.d-Windows5.2..2008.06.01_00-09-03/test510.out.html
## Comment 9553
Date: 2008-06-04 11:28:03 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed by Niels.
Thanks.
## Comment 9554
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1981344 at http://sourceforge.net/support/tracker.php?aid=1981344
| SQL/5: loading module SQL fails on Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/1688/comments | 0 | 2020-11-30T09:52:31Z | 2024-06-27T11:30:19Z | https://github.com/MonetDB/MonetDB/issues/1688 | 753,327,590 | 1,688 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-31 03:52:17 +0200
From: @skinkie
To: @sjoerdmullender
Version: -- development
Last updated: 2008-06-03 04:13:59 +0200
## Comment 9549
Date: 2008-05-31 15:52:17 +0200
From: @skinkie
http://homepages.cwi.nl/~mk/MonetDB/Mapi-Function-Reference.html
Maybe only stupid people make mistakes, but my suggestion is to rewrite:
Reset the row pointer to the requested row number. If whence is MAPI_SEEK_SET (0), rownr is the absolute row number (0 being the first row); if whence is MAPI_SEEK_CUR (1), rownr is relative to the current row; if whence is MAPI_SEEK_END (2), rownr is relative to the last row.
To:
Reset the row pointer to the requested row number. If whence is MAPI_SEEK_SET, rownr is the absolute row number (0 being the first row); if whence is MAPI_SEEK_CUR, rownr is relative to the current row; if whence is MAPI_SEEK_END, rownr is relative to the last row.
(removing the values)
Because the user should not use the value anyway, and it is to error prune to copy paste it as 'function'.
## Comment 9550
Date: 2008-06-03 16:13:59 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Done as suggested.
## Comment 9551
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1980625 at http://sourceforge.net/support/tracker.php?aid=1980625
| Remove (VALUE) from MAPI_SEEK functions | https://api.github.com/repos/MonetDB/MonetDB/issues/1687/comments | 0 | 2020-11-30T09:52:29Z | 2024-06-27T11:30:18Z | https://github.com/MonetDB/MonetDB/issues/1687 | 753,327,566 | 1,687 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-31 12:38:16 +0200
From: @drstmane
To: Lefteris Sidirourgos <<lsidir>>
Version: -- development
Last updated: 2008-06-12 02:33:03 +0200
## Comment 9542
Date: 2008-05-31 12:38:16 +0200
From: @drstmane
========
$ cat /tmp/pf:docname.xq
--------
pf:docname(doc("x"))
========
$ pf -M /tmp/pf:docname.xq > /dev/null
--------
========
$ pf -A /tmp/pf:docname.xq > /dev/null
--------
!ERROR: Segmentation fault.
The Pathfinder compiler experienced an internal problem.
You may want to report this problem to the Pathfinder
development team (pathfinder@pathfinder-xquery.org).
When reporting problems, please attach your XQuery input,
as well as the following information:
Compilation stage: 15
We apologize for the inconvenience...
Segmentation fault
========
For deetails, see attached log and
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/runtime/pf_docname.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/runtime/pf_docname.err.00.html
(as of tomorrow, provided compilation and hence testing will work fine tonight, again).
## Comment 9543
Date: 2008-05-31 12:56:53 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
Re-assigning this bug to me, since it is my fault:)
pf:docname is not fully implemented yet, since a different approach of implementation was decided recently, however it should produce an error message saying not implemented yet rather seg fault. I will leave this bug open until the implementation is finished.
lefteris
## Comment 9544
Date: 2008-05-31 13:34:41 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
File Added: error.log
## Comment 9545
Date: 2008-05-31 13:36:33 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
for other not yet implemented functions, PF/alg indeed correctly produces an error message, e.g.:
$ echo 'pf:log(1)' | pf -A
fatal error: Algebra implementation for function `pf:log' unknown.
halted in /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/pathfinder/compiler/algebra/core2alg.brg (reduce), line 2205
## Comment 9546
Date: 2008-06-01 22:38:59 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
The same seen to hold for / happen with fn:put():
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/put_to_tmp.SF-1718066.err.00.html
## Comment 9547
Date: 2008-06-12 14:33:03 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
Fixed the implementation of docname in the stable branch.
## Comment 9548
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1980464 at http://sourceforge.net/support/tracker.php?aid=1980464
| PF/alg: segfault when compiling 'pf:docname(doc("x"))' | https://api.github.com/repos/MonetDB/MonetDB/issues/1686/comments | 0 | 2020-11-30T09:52:26Z | 2024-06-27T11:30:17Z | https://github.com/MonetDB/MonetDB/issues/1686 | 753,327,533 | 1,686 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-31 05:28:07 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2008-06-02 01:19:57 +0200
## Comment 9538
Date: 2008-05-31 05:28:07 +0200
From: @skinkie
sql>select * from relation_tags where relation=4239539 and v='way';
+----------+-----+----+
| relation |k |v |
+==========+=====+====+
| 4239539 |type |way |
+----------+-----+----+
sql>select * from relation_tags where relation=4239539 and k like 'type';
+----------+-----+----+
| relation |k |v |
+==========+=====+====+
| 4239539 |type |way |
+----------+-----+----+
sql>select * from relation_tags where relation=4239539 and k = 'type';
sql>
Imported from:
4239539,'type','way'
## Comment 9539
Date: 2008-05-31 20:43:06 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
could you add the create table and copy into (or insert into) statements.
## Comment 9540
Date: 2008-06-02 13:19:57 +0200
From: @skinkie
Logged In: YES
user_id=533026
Originator: YES
Seems to be working now.
## Comment 9541
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1980111 at http://sourceforge.net/support/tracker.php?aid=1980111
| WHERE x='type' fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1685/comments | 0 | 2020-11-30T09:52:24Z | 2024-06-28T13:30:07Z | https://github.com/MonetDB/MonetDB/issues/1685 | 753,327,504 | 1,685 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-31 12:06:28 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2008-06-02 08:41:01 +0200
## Comment 9532
Date: 2008-05-31 00:06:28 +0200
From: @skinkie
I have three tables:
Usernames,
Relations,
Relation_tags
First; I want to lookup all Relations having Relation_tags with k='type' and v='way'
After this I want to do a left join, on relation_tags getting the other values of Relation_tags with that are semantically linked to Relations;
select relations.id, relations.visible, usernames.username, '2007-09-07T16:39:10+01:00' FROM relations, usernames, relation_tags AS constr WHERE relations.username = usernames.id AND constr.k='type' AND constr.v='way';
Works.
Adding the LEFT JOIN;
select relations.id, relations.visible, usernames.username, '2007-09-07T16:39:10+01:00' FROM relations, usernames, relation_tags AS constr LEFT JOIN relation_tags AS joiner ON relations.id = joiner.relation WHERE relations.username = usernames.id AND constr.k='type' AND constr.v='way';
!SELECT: no such column 'relations.id'
No such column? Isn't that strange?
## Comment 9533
Date: 2008-05-31 00:08:20 +0200
From: @skinkie
Logged In: YES
user_id=533026
Originator: YES
sql>select relations.id, relations.visible, usernames.username, '2007-09-07T16:39:10+01:00' FROM relations, usernames, relation_tags AS tags WHERE relations.username = usernames.id AND tags.k='type' AND tags.v='way';
sql>select relations.id, relations.visible, usernames.username, '2007-09-07T16:39:10+01:00' FROM relations, usernames, relation_tags AS constr WHERE relations.username = usernames.id AND constr.k='type' AND constr.v='way';
sql>select relations.id, relations.visible, usernames.username, '2007-09-07T16:39:10+01:00' FROM relations, usernames, relation_tags AS constr LEFT JOIN relation_tags AS joiner ON relations.id = joiner.relation WHERE relations.username = usernames.id AND constr.k='type' AND constr.v='way';
!SELECT: no such column 'relations.id'
sql>select relations.id, relations.visible, usernames.username, '2007-09-07T16:39:10+01:00' FROM relations, usernames LEFT JOIN relation_tags AS joiner ON relations.id = joiner.relation WHERE relations.username = usernames.id;
!SELECT: no such column 'relations.id'
sql>select relations.id, relations.visible, usernames.username, '2007-09-07T16:39:10+01:00' FROM relations, usernames LEFT JOIN relation_tags AS joiner ON id = joiner.relation WHERE relations.username = usernames.id;
sql>select relations.id, relations.visible, usernames.username, '2007-09-07T16:39:10+01:00' FROM relations, usernames, relation_tags AS constr LEFT JOIN relation_tags AS joiner ON id = joiner.relation WHERE relations.username = usernames.id AND constr.k='type' AND constr.v='way';
!SELECT: identifier 'id' unknown
## Comment 9534
Date: 2008-05-31 03:54:59 +0200
From: @skinkie
Logged In: YES
user_id=533026
Originator: YES
I see the leftjoinbug.sql example results in 'NULL's like my own queries with LEFT join. Maybe something changed lately, but not so long ago this all worked.
sql>SELECT id, X(g), Y(g), visible, usernames.username, '2007-09-07T16:39:10+01:00', node_tags.k, node_tags.v FROM nodes, usernames LEFT JOIN node_tags ON id = node WHERE id=44803343 LIMIT 2;
+----------+-----------------------+-----------------------+--------+---------+--------------------------+--+--+
| id |x_g |y_g |visible |username |single_value |k |v |
+==========+=======================+=======================+========+=========+==========================+==+==+
| 44803343 | 52.001168999999997 | 4.3722767999999999 |true |unknown |2007-09-07T16:39:10+01:00 |n |n |
: | | | | | |u |u |
: | | | | | |l |l |
: | | | | | |l |l |
+----------+-----------------------+-----------------------+--------+---------+--------------------------+--+--+
sql>SELECT id, X(g), Y(g), visible, usernames.username, '2007-09-07T16:39:10+01:00', node_tags.k, node_tags.v FROM nodes, usernames, node_tags WHERE id = node AND id=44803343 LIMIT 2;
+----------+-----------------------+-----------------------+--------+---------+--------------------------+---------+------+
| id |x_g |y_g |visible |username |single_value |k |v |
+==========+=======================+=======================+========+=========+==========================+=========+======+
| 44803343 | 52.001168999999997 | 4.3722767999999999 |true |unknown |2007-09-07T16:39:10+01:00 |'source' |'AND' |
+----------+-----------------------+-----------------------+--------+---------+--------------------------+---------+------+
## Comment 9535
Date: 2008-05-31 20:56:59 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
please add the create statements for you 3 tables.
## Comment 9536
Date: 2008-06-02 08:41:01 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
MonetDB is correctly complaining. The query is incorrect.
## Comment 9537
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1979819 at http://sourceforge.net/support/tracker.php?aid=1979819
| LEFT JOIN combined with same table | https://api.github.com/repos/MonetDB/MonetDB/issues/1684/comments | 0 | 2020-11-30T09:52:21Z | 2024-06-28T13:30:06Z | https://github.com/MonetDB/MonetDB/issues/1684 | 753,327,472 | 1,684 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-28 11:43:23 +0200
From: Wouter Alink <<alink>>
To: Wouter Alink <<alink>>
Version: -- development
Last updated: 2009-11-15 03:27:17 +0100
## Comment 9513
Date: 2008-05-28 11:43:23 +0200
From: Wouter Alink <<alink>>
Using todays stable build (preJune, May28, 2008) but it happens with earlier builds as well), the dbfarm isn't cleaned up as expected after deleting a document with 'pf:del-doc()'.
When repeatedly adding and deleting documents, the leftovers start piling up, and eventually the system runs out of disk-space.
See example below.
bash-3.2$ wc -c /tmp/aap.xml
292890833 /tmp/aap.xml
bash-3.2$ echo 'pf:add-doc("/tmp/aap.xml","aap.xml")' | mclient -lxq
bash-3.2$ du -sh /tmp/dbfolder/
367M /tmp/dbfolder/
bash-3.2$ echo 'pf:add-doc("/tmp/aap.xml","aap_1.xml")' | mclient -lxq
bash-3.2$ du -sh /tmp/dbfolder/
733M /tmp/dbfolder/
bash-3.2$ echo 'pf:add-doc("/tmp/aap.xml","aap_2.xml")' | mclient -lxq
bash-3.2$ du -sh /tmp/dbfolder/
1.1G /tmp/dbfolder/
bash-3.2$
bash-3.2$ echo 'pf:del-doc("aap_2.xml")' | mclient -lxq
bash-3.2$ du -sh /tmp/dbfolder/
997M /tmp/dbfolder/
bash-3.2$ echo 'pf:del-doc("aap_1.xml")' | mclient -lxq
bash-3.2$ du -sh /tmp/dbfolder/
895M /tmp/dbfolder/
bash-3.2$ du -sh /tmp/dbfolder/
895M /tmp/dbfolder/
bash-3.2$ du -sh /tmp/dbfolder/
895M /tmp/dbfolder/
bash-3.2$ echo 'pf:del-doc("aap.xml")' | mclient -lxq
bash-3.2$ du -sh /tmp/dbfolder/
794M /tmp/dbfolder/
bash-3.2$ du -sh /tmp/dbfolder/
794M /tmp/dbfolder/
bash-3.2$
## Comment 9514
Date: 2008-05-28 11:50:21 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
(increased priority a little, as it seems a showstopper for us)
additional information:
- restarting mserver does clean up the data as expected
## Comment 9515
Date: 2008-05-28 12:38:59 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Wouter,
could you please check
(1) which of the sub directories of /tmp/dbfolder/ contains the left-overs, and
(2) whether stopping and re-starting Mserver does change (reduce) the size of /tmp/dbfolder/ (and/or its subdirectories)
?
Thanks!
## Comment 9516
Date: 2008-05-28 12:40:46 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Moreover, does /tmp/dbfolder/ only contain the dbfarm or also the log directory?
How does the size of the log directory evolve/change in above example?
## Comment 9517
Date: 2008-05-29 12:01:19 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
Hi, I repeated this bug, and I am attaching the results. This is not a query compile time problem but a runtime, but because the mps and algebra use a slightly different "play docmgm tape" I did the experiments with both back-ends. The problem is there for both back-ends, and the disk is cleaned only when the mserver *starts* again (and not when it is killed). The document I used is around 280MB.
I am re-assigning this bug to Stefan:) (or Peter?)
File Added: leftovers_after_del.report
## Comment 9518
Date: 2008-05-29 12:12:02 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
could you please also report the results of
`find .../MonetDB4 -type d | xargs du -sh`
?
Thanks!
## Comment 9519
Date: 2008-05-29 15:28:59 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
Before adding the doc:
232K MonetDB4
12K MonetDB4/xquery_logs
8.0K MonetDB4/xquery_logs/demo
216K MonetDB4/dbfarm
212K MonetDB4/dbfarm/demo
204K MonetDB4/dbfarm/demo/bat
4.0K MonetDB4/dbfarm/demo/bat/LEFTOVERS
8.0K MonetDB4/dbfarm/demo/bat/BACKUP
4.0K MonetDB4/dbfarm/demo/bat/03
44K MonetDB4/dbfarm/demo/bat/01
4.0K MonetDB4/dbfarm/demo/bat/05
4.0K MonetDB4/dbfarm/demo/bat/04
After adding the doc:
366M MonetDB4
12K MonetDB4/xquery_logs
8.0K MonetDB4/xquery_logs/demo
366M MonetDB4/dbfarm
366M MonetDB4/dbfarm/demo
366M MonetDB4/dbfarm/demo/bat
4.0K MonetDB4/dbfarm/demo/bat/LEFTOVERS
8.0K MonetDB4/dbfarm/demo/bat/BACKUP
4.0K MonetDB4/dbfarm/demo/bat/03
44K MonetDB4/dbfarm/demo/bat/01
179M MonetDB4/dbfarm/demo/bat/05
188M MonetDB4/dbfarm/demo/bat/04
After deleting the doc:
265M MonetDB4
12K MonetDB4/xquery_logs
8.0K MonetDB4/xquery_logs/demo
265M MonetDB4/dbfarm
265M MonetDB4/dbfarm/demo
265M MonetDB4/dbfarm/demo/bat
4.0K MonetDB4/dbfarm/demo/bat/LEFTOVERS
8.0K MonetDB4/dbfarm/demo/bat/BACKUP
4.0K MonetDB4/dbfarm/demo/bat/03
44K MonetDB4/dbfarm/demo/bat/01
77M MonetDB4/dbfarm/demo/bat/05
188M MonetDB4/dbfarm/demo/bat/04
## Comment 9520
Date: 2008-05-29 18:09:41 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
first analysis seems to show that after a "pf:del-doc()", the BATs holding the document are (correctly) turned from "persistent" into "transient", and their "lrefcnt" is reduced from "2" to "1", but (most probably due to the "lrefcnt" of "1"), they stay "around" until this one reference to them is released, e.g., by stopping (and restarting) the server --- need to check, why/where this one lref comes from ...
## Comment 9521
Date: 2008-05-29 18:15:28 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
The previous release (Feb2008: MonetDB 4.22.0 + Pathfinder 0.22.0) shows the same behavior.
## Comment 9522
Date: 2008-06-04 02:16:43 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
See also
http://sourceforge.net/mailarchive/forum.php?thread_name=20080603233242.GA31340%40cwi.nl&forum_name=monetdb-developers
## Comment 9523
Date: 2008-06-06 00:47:42 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Well, as my checkin messages already suggested, my recent logger-related checkins do not fix this bug.
However, I guess/hope I managed to get close to the actual problem.
Thanks to Niels' hints, my recent changes helped to get the log-flush triggered as intended in pathfinder.
However, even during the flush (i.e., restart of the logger), the "left-over refcounts are not reduced.
As far as I can see, the reason is the fact that pathfinder "messes" with the logger's internal BATs (xquery_catalog, xquery_seqs, xquery_snapshots), in particular xquery_catalog:
The logger uses/exploits the delta mechanism of not yet committed changes to BATs to keep track of which BATs have been added to or removed from the logger's control via logger_add_bat() & logger_del_bat().
Pathfinder "messes" with this by committing also these BATs during its own commit of shredded document BATs, obviously "destroying" the deltas.
Once the log-flush/logger-retart is triggered, the logger's bm_commit() does/can not see the deleted BATs anymore and hence cannot reduce there refcounts.
Given this, I tried the obvious(?): keep pathfinder from committing the logger BATs via the followin patch:
========
--- pathfinder/runtime/pathfinder.mx 5 Jun 2008 21:18:51 -0000 1.416.2.6
+++ pathfinder/runtime/pathfinder.mx 5 Jun 2008 22:37:04 -0000
@@ -623,9 +623,6 @@
{
if (count(commitBAT) = 0) return false;
commitBAT := commitBAT.access(BAT_WRITE);
- commitBAT.append("xquery_catalog");
- commitBAT.append("xquery_seqs");
- commitBAT.append("xquery_snapshots");
commitBAT.append("collection_name");
commitBAT.append("collection_size");
commitBAT.append("doc_name");
========
Now, bm_commit() sees the delta and does its work reducing the refcount from 1 to 0 in its first loop ("/* remove the destroyed bats */").
However, bm_commit() finally calls bm_subcommit() still with the same catalog BAT.
bm_subcommit() itself then does also loop over the same delta of deleted BUNs in the catalog BAT ("/* first loop over deleted then over current and new */"),
which results in several
"!WARNING: BBPname: range error <bat_id>"
(one for each deleted BATs),
triggered by calling BBPname() (and thus BBPcheck()) on BATs with refcount 0 ...
Here, I'm (at least for now?) at the end of my "expertise".
Any help by the real logger and/or pathfinder expert(s) is now required and highly appreciated!
Thanks you very much in advance!
## Comment 9524
Date: 2008-06-06 08:20:52 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Indeed its incorrect that pf 'commits' xquery_catalog etc bats. But next to that it should also not do the subcommits on the to be deleted (bats or any other snapshot to be precise). This is all done by the logger.
## Comment 9525
Date: 2008-06-18 11:12:10 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
Niels,
I am truly lost. Please, either explain to me what XQuery must do, or fix the code yourself or (at least) document what logger does.
Let me try to explain what XQuery needs.
XQuery just wants to make bats persistent when shredded and TMsubcommit them. And on document delete, it wants to make bats transient and TMsubcommit that.
XQuery gives documents unique names, using a persistent sequence number.
But XQuery also wants to be able to update persistent bats, and log changes to them using the WAL (trans_start ... trans_end).
There is a really basic problem with mixing TMsubcommit and the WAL, like you seem to be doing. If you have a mechanism that relies both on a WAL write and a TMsubcommit, how are you going to achieve atomicity? What if the WAL write succeeds, but the TMsubcommit not? Atomicity cannot be guaranteed AFAICS.
Because TMsubcommit (i.e. checkpoint) is much more efficient for shred/delete-doc than logging all new data, XQuery uses separate mechanisms for updates vs. shredding/deleting, and actually forbids transactions that do both.
The fact that somehow the logger now performs subcommits (since when?) surprises me. But lacking any documentation of the logger, I am really at a loss how to proceed. Can you provide the functionality that we need?
So:
- I do not want to write in the WAL (log_start/log_end) for a document shred/delete. I just want TMsubcommit.
- After TMsubcommit, we do want to log update queries in the WAL. For this, I understand that the bats need to be somehow registered in the WAL. During recovery actually the WAL should not worry about how to get the bats. All bats for which updates have been logged, are known to have been succesfully TMsubcommit-ed previously (otherwise the shred had failed). So these bats are always there. And if they aren't present during recovery, it means that the document had been deleted already (bat names are unique and never re-appear in XQuery) -- thus such deltas can be ignored.
Maybe we should not register the XQuery bats at all in the logger (and the logger should be changed such to cope with that). Or there should be a form of "light" registering that does not cause any lrefcounts. This seems to be the problem here.
I feel a bit frustrated as we appear to be talking about this for two years, and things end up not working no matter how much talking is done. Besides, I really wonder about my original question regarding atomicity and the logger: how does SQL achieve atomicity if transactions require *both* a succesful WAL commit write *and* a TMsubcommit?
Peter
(I know I am agging a bit, but writing documentation really would help to avoid such questions/mysteries)
## Comment 9526
Date: 2008-06-18 11:18:18 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
I propose a meeting on this issue with Peter, Niels, Sjoerd (and possibly me), as soon as we find a common free slot in our agendas.
First suggestion:
Tomorrow (Thursday Jun 19 2008) after TTT.
## Comment 9527
Date: 2008-07-03 22:34:28 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Might be related to
[ 2009556 ] XQ: "Zombie" document in collection
http://sourceforge.net/tracker/index.php?func=detail&aid=2009556&group_id=56967&atid=482468
## Comment 9528
Date: 2008-09-29 16:23:10 +0200
From: @sjoerdmullender
Fixed on the development branch. Since the fix involves an API change, it cannot be done on the stable branch.
The bug
[ 2009556 ] XQ: "Zombie" document in collection
still exists, so I guess they're not related.
Note that it may take some time before the data is actually deleted from disk. Data is only really deleted when a logger restart is done, and that happens on server restart or once every 5 minutes if enough changes have accumulated.
Wouter, can you check whether this fixes your problem?
## Comment 9529
Date: 2009-02-17 01:40:08 +0100
From: @drstmane
re-opened to remind us that we should consider adding a test.
## Comment 9530
Date: 2009-11-15 15:27:17 +0100
From: Wouter Alink <<alink>>
it seems to be difficult to write a good testcase, because the cleanup of the dbfarm folder may not be done directly, but instead may dependent on the flushing of the log as Sjoerd pointed out.
If we want to be sure enough changes have accumulated, then we should use big documents, and furthermore wait for at least 5 minutes. As testing is already a slow process, I would opt to not add a test.
Closing bug.
## Comment 9531
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1976341 at http://sourceforge.net/support/tracker.php?aid=1976341
| XQ: leftovers after deleting document | https://api.github.com/repos/MonetDB/MonetDB/issues/1683/comments | 0 | 2020-11-30T09:52:18Z | 2024-06-27T11:30:14Z | https://github.com/MonetDB/MonetDB/issues/1683 | 753,327,433 | 1,683 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-27 10:05:08 +0200
From: @skinkie
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2008-05-28 11:45:47 +0200
## Comment 9510
Date: 2008-05-27 22:05:08 +0200
From: @skinkie
sql>drop table nodes;
sql>CREATE TABLE nodes (id serial, p POINT);
sql>insert into nodes (id, p) values (45111955, 'POINT(52.0697 4.3723)');
Rows affected 1
sql>COPY 1 RECORDS INTO nodes from '/tmp/insert/split/file0' USING DELIMITERS ',', '\n';
file0:
45111956, 'POINT(52.0697 4.3723)'
GDB:
(gdb) bt
0 0x00002ad4bb689f3e in memset () from /lib/libc.so.6
1 0x00002ad4b9b06a15 in GDKfree (blk=0xbc6ea8) at /usr/include/bits/string3.h:85
2 0x00002ad4b9a9309c in HEAPfree (h=0x13168e8) at gdk_heap.mx:252
3 0x00002ad4b9bae195 in BATdelete (b=0x13d0a18) at gdk_storage.mx:775
4 0x00002ad4b9a91ee8 in BBPdestroy (b=0x13d0a18) at gdk_bbp.mx:2435
5 0x00002ad4b9a902fd in decref (i=1421, logical=0, releaseShare=<value optimized out>) at gdk_bbp.mx:1383
6 0x00002aaaaf8763b3 in TABLETdestroy_format (as=0x42002910) at tablet.mx:1127
7 0x00002aaab3c13d7e in mvc_import_table (m=0x11e1308, bs=0x140b6f0, sname=<value optimized out>, tname=<value optimized out>,
sep=0x136d728 '�' <repeats 200 times>..., rsep=0x1398f28 '�' <repeats 200 times>..., ssep=0x11ccf38 '�' <repeats 200 times>...,
ns=0x1398e78 '�' <repeats 200 times>..., sz=1, offset=<value optimized out>) at sql_result.mx:484
8 0x00002aaab3bea3ea in mvc_import_table_wrap (res=0x13f9fa8, s=0x13f9f88, sname=0x13f9fb8, tname=0x13f9fc8, T=<value optimized out>,
R=<value optimized out>, S=0x13f9ff8, N=0x13fa008, sz=0x13fa018, offset=0x13fa028) at sql.mx:1779
9 0x00002ad4b9051494 in runMALsequence (cntxt=0x6046d0, mb=0x13fb048, startpc=1, stoppc=0, stk=0x13f9eb8, env=0x0, pcicaller=0x0)
at mal_interpreter.mx:1178
10 0x00002ad4b9056c95 in callMAL (cntxt=0x6046d0, mb=0x13fb048, env=0x42003018, argv=0x42002ff0, debug=0 '\0') at mal_interpreter.mx:412
11 0x00002aaab3c0a71d in SQLexecutePrepared (c=0x6046d0, be=<value optimized out>, q=0x13fae88) at sql_scenario.mx:1189
12 0x00002aaab3c0c9ca in SQLengineIntern (c=0x6046d0, be=0x134f2b8) at sql_scenario.mx:1300
13 0x00002ad4b9075b1d in runScenario (c=0x6046d0) at mal_scenario.mx:630
14 0x00002ad4b904d308 in MSserveClient (dummy=<value optimized out>) at mal_session.mx:471
15 0x00002ad4ba7cc067 in start_thread () from /lib/libpthread.so.0
16 0x00002ad4bb6d7bdd in clone () from /lib/libc.so.6
17 0x0000000000000000 in ?? ()
## Comment 9511
Date: 2008-05-28 11:45:47 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
fixed bug in wkb from string which didn't return atom nil on errors. Also added a test to geom/BugTracker/copy_into_crash.SF-1975402
## Comment 9512
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1975402 at http://sourceforge.net/support/tracker.php?aid=1975402
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.
| Copy into segfaults | https://api.github.com/repos/MonetDB/MonetDB/issues/1682/comments | 0 | 2020-11-30T09:52:15Z | 2024-06-27T11:30:13Z | https://github.com/MonetDB/MonetDB/issues/1682 | 753,327,402 | 1,682 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-27 07:14:11 +0200
From: @skinkie
To: @sjoerdmullender
Version: -- development
Last updated: 2008-06-03 05:06:25 +0200
## Comment 9507
Date: 2008-05-27 19:14:11 +0200
From: @skinkie
In the example [1], I found valgrid complaining about a few things. The actual leaking was solved by placing mapi_cache_freeup(hdl, 100); before the last mapi_close_handle.
The other problems can be find by running valgrind on the example.
by 0x5B564D2: stream_init (stream.mx:372)
The above is a starting point.
[1]http://monetdb.cwi.nl/projects/monetdb/SQL/Documentation/An-Example.htmlAn-Example
## Comment 9508
Date: 2008-06-03 17:06:24 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
The first paragraph of the report is a real memory leak which was fixed by freeing the allocated memory where the rest of the result handle was being freed.
The example doesn't have to be changed.
The "other problems" is not a true memory leak. Memory is allocated in stream_init() by the call to SSL_load_error_strings(). In principle this memory can be freed by a call to ERR_free_strings(), but there is no point in doing so: that call would happen when the program exits, and then the memory is freed by the system anyway. In addition, there is no call to close the stream library, and there is also no call to close the Mapi library which would have to close the stream library.
No test added since it is not really feasible to make one.
## Comment 9509
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1975196 at http://sourceforge.net/support/tracker.php?aid=1975196
| mapi_cache_freeup in example | https://api.github.com/repos/MonetDB/MonetDB/issues/1681/comments | 0 | 2020-11-30T09:52:13Z | 2024-06-27T11:30:12Z | https://github.com/MonetDB/MonetDB/issues/1681 | 753,327,372 | 1,681 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-27 06:12:44 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2008-06-01 07:14:22 +0200
## Comment 9501
Date: 2008-05-27 18:12:44 +0200
From: @drstmane
most PF/tijah tests fail (with both MPS & ALG back-end) due to property errors like
!WARNING: BATpropcheck: BAT tj_testcoll1_pfpre(1264)[oid,oid] with 48 tuples was incorrectly marked keyed!
e.g.:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora8/modules_pftijah/colltest2.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora8/modules_pftijah/qmil0.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/modules_pftijah/colltest2.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/modules_pftijah/qmil0.out.00.html
## Comment 9502
Date: 2008-05-28 16:13:30 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Originator: NO
This is a problem with the BAT containing the translation from term index to pathfinder index. The handling of this bat has not changed for a year.
The problem is the bat at the end of the indexing transaction contains the correct tuples but after commit and the start of the new transaction it is completely filled with 0's. The last time I had a similar problem (2 weeks ago) this was due to the new mmap() handling but we do not use this here. I will try to pinpoint the exact time of the transformation tomorrow.
## Comment 9503
Date: 2008-05-28 18:03:03 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Jan could you try to figure out the order of bat access, persistency and mmap allocation changes, ie
calls to access(BAT_READ/WRITE), commit and mmap? It seems the order in pftijah is different then the currently tested once. This will help us solve this data corruption problem.
## Comment 9504
Date: 2008-05-29 14:17:22 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Originator: NO
I checked the lifecycle of the BAT:
1. Creation of the bat:
$PF/modules/pftijah/pftijah.mx:613
new(oid,oid).persists(true).bbpname("tj_" + ftiName + "_pfpre");
2. Use of mmap:
$PF/modules/pftijah/pftijah.mx:1139
collBat.find("_pfpre").access(BAT_APPEND).mmap(1);
An then precommit(), location is not important.
When I remove the line "collBat.find("_pfpre").access(BAT_APPEND).mmap(1);"
which looks up the bat which causes the problems and does the access() and
mmap() call everything works fine. Doing only the .access() or the .mmap()
also works fine.
CONCLUSION FOR NIELS: the construction "BAT.access(BAT_APPEND).mmap(1);"
causes the problem here.
## Comment 9505
Date: 2008-06-01 19:14:22 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
After Niels' recent checkins, the PFtijah tests seem to work fine, again.
Thanks!
## Comment 9506
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1975133 at http://sourceforge.net/support/tracker.php?aid=1975133
| PF/tijah: most tests fail with property error | https://api.github.com/repos/MonetDB/MonetDB/issues/1680/comments | 0 | 2020-11-30T09:52:09Z | 2024-06-27T11:30:11Z | https://github.com/MonetDB/MonetDB/issues/1680 | 753,327,326 | 1,680 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-27 05:00:33 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2010-04-08 04:20:16 +0200
## Comment 9493
Date: 2008-05-27 17:00:33 +0200
From: Jan Rittinger <<jan.rittinger>>
The MIL proc get_root() incorrectly assumes that every attribute has a parent.
Examples queries are
root(attribute bar {"42"})
id("a42",attribute bar {"42"})
## Comment 9494
Date: 2008-05-27 17:01:21 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: YES
This problem arises in both mps and algebra.
## Comment 9495
Date: 2008-06-18 11:22:52 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
Until we actually move to a document representation where attributes are proper XML nodes, it will be hard to let get_root do something useful (what pre number should it return).
The only solution I can think of is generating a run-time error. Which is what happens now.
## Comment 9496
Date: 2009-04-07 10:25:29 +0200
From: @peterboncz
this is one that might eventually go away in the M5 XQuery port, where attributes will have pre numbers
## Comment 9497
Date: 2009-04-07 12:52:32 +0200
From: @drstmane
added test in pathfinder/tests/BugTracker/Tests/fn-root_fn-id_on_attribute_nodes.SF-1975028.* (CVS HEAD)
as monitor that it will indeed be fixed with future document representation changes
## Comment 9498
Date: 2009-11-14 23:44:07 +0100
From: @drstmane
===================================================================
2009/11/14 - stmane: All,1.146.2.5
Disabled test that is bound to fail.
Please re-enable once bug is fixed.
cf.
ID: 1975028 "XQ: get_root (and thus fn:id()) fails for special cases"
https://sourceforge.net/tracker/index.php?func=detail&aid=1975028&group_id=56967&atid=482468
===================================================================
## Comment 9499
Date: 2010-04-08 04:20:15 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
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 9500
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1975028 at http://sourceforge.net/support/tracker.php?aid=1975028
| XQ: get_root (and thus fn:id()) fails for special cases | https://api.github.com/repos/MonetDB/MonetDB/issues/1679/comments | 0 | 2020-11-30T09:52:07Z | 2024-06-28T13:30:05Z | https://github.com/MonetDB/MonetDB/issues/1679 | 753,327,297 | 1,679 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-27 04:50:51 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2008-05-29 08:35:31 +0200
## Comment 9488
Date: 2008-05-27 16:50:51 +0200
From: @drstmane
With the (supposedly deprecated) MonetDB4 server,
SQL tests in sql/src/test/Update_Delete_action/Tests/
fail possibly due to not properly dropped table(s):
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests4103/GNU.64.64.d-Fedora8/src_test_Update_Delete_action/delete_no_action.err.00.html
These tests do work fine with the MonetDB5 server:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests5103/GNU.64.64.d-Fedora8/src_test_Update_Delete_action/delete_no_action.err.00.html
## Comment 9489
Date: 2008-05-27 17:13:12 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: NO
I do not have M4 to solve the problem, but this might help...
These are the only 3 tests that might create the problem because they are the ones using table t3...
./null.sql
./BugTracker/Tests/alter_table_add_fkey.SF-1737668.sql
./add_column_with_seq.sql
Romulo
## Comment 9490
Date: 2008-05-27 18:05:35 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: NO
I got an example for you:
create table t1 (id int, name varchar(1024), PRIMARY KEY(id));
create table t2 (id int, age int, PRIMARY KEY (id), FOREIGN KEY(id) REFERENCES t1(id)); -- ON DELETE CASCADE);
insert into t1 values(1, 'monetdb');
insert into t1 values(2, 'mon');
insert into t2 values(1, 23);
insert into t2 values(2, 24);
drop table t2;
drop table t1;
If you now restart the mserver4 (stable optimized compilation) and create the same tables you will see that the tables are still there (or only the catalog information). However, if you invert the insertion order for t1:
insert into t1 values(2, 'mon');
insert into t1 values(1, 'monetdb');
Everything starts to work again...
Crazy?!?! :D
Only MonetDB can give you these kind of challenges...
Romulo
## Comment 9491
Date: 2008-05-29 08:35:31 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Thanks to Niels' fixes, these tests work fine, again.
## Comment 9492
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1975011 at http://sourceforge.net/support/tracker.php?aid=1975011
| SQL/4: tests in src/test/Update_Delete_action/ fail with M4 | https://api.github.com/repos/MonetDB/MonetDB/issues/1678/comments | 0 | 2020-11-30T09:52:05Z | 2024-06-27T11:30:09Z | https://github.com/MonetDB/MonetDB/issues/1678 | 753,327,260 | 1,678 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-27 04:25:59 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-09-25 11:00:13 +0200
## Comment 9482
Date: 2008-05-27 16:25:59 +0200
From: @drstmane
MonetDB5 tests recycle0[0-3] in src/mal/Tests/ fail on Windows;
looks like some premature end of output/operation:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.32.32.d-Windows5.1/src_mal/recycle00.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.64.32.d-Windows5.2/src_mal/recycle00.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.32.32.d-Windows5.1/src_mal/recycle01.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.64.32.d-Windows5.2/src_mal/recycle01.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.32.32.d-Windows5.1/src_mal/recycle02.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.64.32.d-Windows5.2/src_mal/recycle02.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.32.32.d-Windows5.1/src_mal/recycle03.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.64.32.d-Windows5.2/src_mal/recycle03.out.00.html
## Comment 9483
Date: 2008-05-27 18:57:22 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: NO
These tests are not to be executed on the stable branch...
I already deactivated them, so I think the bug can be closed...
Stefan if you do not agree, just open it again ;)
Romulo
## Comment 9484
Date: 2008-05-27 19:11:38 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Disabling the test (in the release branch, only) does obviously NOT *fix* the bug in the development trunk.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.mTests103/I
nt.32.32.d-Windows5.1/src_mal/recycle00.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.mTests103/I
nt.64.64.d-Windows5.2/src_mal/recycle00.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.mTests103/I
nt.32.32.d-Windows5.1/src_mal/recycle01.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.mTests103/I
nt.64.64.d-Windows5.2/src_mal/recycle01.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.mTests103/I
nt.32.32.d-Windows5.1/src_mal/recycle02.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.mTests103/I
nt.64.64.d-Windows5.2/src_mal/recycle02.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.mTests103/I
nt.32.32.d-Windows5.1/src_mal/recycle03.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.mTests103/I
nt.64.64.d-Windows5.2/src_mal/recycle03.out.00.html
## Comment 9485
Date: 2008-05-27 19:47:16 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: NO
I saw that the bug was opened for stable branch...
I did not realize that the current was also broken....
Thanks for the correction... ;)
Romulo
## Comment 9486
Date: 2008-09-25 11:00:13 +0200
From: @drstmane
Fixed --- most probably by
===================================================================
2008/09/03 - stmane: src/mal/mal_instruction.mx,1.351
src/modules/mal/recycle.mx,1.50
[ please read and learn ]
Fixing general bug that (correctly!) triggered a (so far ingnored)
segfault with the recycle tests on SunOS (compiler with Sun Studio compiler):
It is strongly recommended NOT to use type "long" as is defined and behaves
differently on different platform!
In case you need a 32-bit (signed) integer type, use "int";
in case you need a 64-bit (signed) integer type, use "lng";
in case you need a type that is 32-bit on 32-bit systems
and 64-bit on 64-bit systems, use "size_t" (unsigned) or "ssize_t" (signed).
In particular (and this triggered the segfault) it is (obviously) not possible
to use "LLFMT" as format string for values of type "long".
The fix:
in src/mal/mal_instruction.mx
use type "int" instead of "long" for "ProfRecord.counter"
(I hope 32-bit is large enough; otherwise, we should use "[s]size_t" or "lng"
and adapt the remaining code and format strings accordingly...)
in src/modules/mal/recycle.mx
use format string "%d" (int) instead of "LLFMT" (lng) for "recycleBlk->profiler[i].counter".
===================================================================
Closing.
## Comment 9487
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1974970 at http://sourceforge.net/support/tracker.php?aid=1974970
| M5: tests recycle0[0-3] fail on Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/1677/comments | 0 | 2020-11-30T09:52:02Z | 2024-06-27T11:30:08Z | https://github.com/MonetDB/MonetDB/issues/1677 | 753,327,232 | 1,677 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-27 04:22:40 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-09-25 11:00:00 +0200
## Comment 9476
Date: 2008-05-27 16:22:40 +0200
From: @drstmane
MonetDB5 tests recycle02 & recycle03 in src/mal/Tests/ fail on Gentoo;
looks like some "off-by-one" problem:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.32.32.d-Gentoo1.12.11.1/src_mal/recycle02.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.32.32.d-Gentoo1.12.11.1/src_mal/recycle03.out.00.html
## Comment 9477
Date: 2008-05-27 18:55:51 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: NO
These test should not be executed on the stable branch...
I already deactivated these tests so I think the bug can be closed...
Stefan if you do not agree, just open it again ;)
Romulo
## Comment 9478
Date: 2008-05-27 19:09:55 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Disabling the test (in the release branch, only) does obviously NOT *fix* the bug in the development trunk.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.mTests103/GNU.32.32.d-Gentoo1.12.11.1/src_mal/recycle02.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.mTests103/GNU.32.32.d-Gentoo1.12.11.1/src_mal/recycle03.out.00.html
## Comment 9479
Date: 2008-05-27 19:47:35 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: NO
I saw that the bug was opened for stable branch...
I did not realize that the current was also broken....
Thanks for the correction... ;)
Romulo
## Comment 9480
Date: 2008-09-25 11:00:00 +0200
From: @drstmane
Fixed --- most probably by
===================================================================
2008/09/03 - stmane: src/mal/mal_instruction.mx,1.351
src/modules/mal/recycle.mx,1.50
[ please read and learn ]
Fixing general bug that (correctly!) triggered a (so far ingnored)
segfault with the recycle tests on SunOS (compiler with Sun Studio compiler):
It is strongly recommended NOT to use type "long" as is defined and behaves
differently on different platform!
In case you need a 32-bit (signed) integer type, use "int";
in case you need a 64-bit (signed) integer type, use "lng";
in case you need a type that is 32-bit on 32-bit systems
and 64-bit on 64-bit systems, use "size_t" (unsigned) or "ssize_t" (signed).
In particular (and this triggered the segfault) it is (obviously) not possible
to use "LLFMT" as format string for values of type "long".
The fix:
in src/mal/mal_instruction.mx
use type "int" instead of "long" for "ProfRecord.counter"
(I hope 32-bit is large enough; otherwise, we should use "[s]size_t" or "lng"
and adapt the remaining code and format strings accordingly...)
in src/modules/mal/recycle.mx
use format string "%d" (int) instead of "LLFMT" (lng) for "recycleBlk->profiler[i].counter".
===================================================================
Closing.
## Comment 9481
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1974965 at http://sourceforge.net/support/tracker.php?aid=1974965
| M5: tests recycle02 & recycle03 fail on Gentoo | https://api.github.com/repos/MonetDB/MonetDB/issues/1676/comments | 0 | 2020-11-30T09:51:59Z | 2024-06-27T11:30:07Z | https://github.com/MonetDB/MonetDB/issues/1676 | 753,327,201 | 1,676 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-25 03:54:47 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2008-06-02 08:48:55 +0200
## Comment 9470
Date: 2008-05-25 03:54:47 +0200
From: @skinkie
Using basic.sql
sql>select X(g) from geoms ;
(gdb) bt
0 0x00002aaab3153c87 in GEOSCoordSeq_getOrdinate () from /usr/lib/libgeos_c.so.1
1 0x00002aaab2f26d04 in wkbgetcoordX (out=0x12e1e78, geom=<value optimized out>) at geom.mx:788
2 0x00002b37484c28ee in runMALsequence (cntxt=0x6046d0, mb=0x12e2328, startpc=1, stoppc=0, stk=0x12e1ac8, env=0x0, pcicaller=0x0)
at mal_interpreter.mx:1118
3 0x00002b37484c7c95 in callMAL (cntxt=0x6046d0, mb=0x12e2328, env=0x42003018, argv=0x42002ff0, debug=0 '\0') at mal_interpreter.mx:412
4 0x00002aaab3c0a71d in SQLexecutePrepared (c=0x6046d0, be=<value optimized out>, q=0x12e21a8) at sql_scenario.mx:1189
5 0x00002aaab3c0c9ca in SQLengineIntern (c=0x6046d0, be=0x12e0ec8) at sql_scenario.mx:1300
6 0x00002b37484e6b1d in runScenario (c=0x6046d0) at mal_scenario.mx:630
7 0x00002b37484be308 in MSserveClient (dummy=<value optimized out>) at mal_session.mx:471
8 0x00002b3749c3d067 in start_thread () from /lib/libpthread.so.0
9 0x00002b374ab48bdd in clone () from /lib/libc.so.6
10 0x0000000000000000 in ?? ()
## Comment 9471
Date: 2008-05-27 22:58:54 +0200
From: @skinkie
Logged In: YES
user_id=533026
Originator: YES
Interesting...
sql>select X(g) from nodes limit 1;
+------------------------+
| x_g |
+========================+
| 52.069699999999997 |
+------------------------+
sql>select Y(g) from nodes limit 1;
+------------------------+
| y_g |
+========================+
| 4.3723000000000001 |
+------------------------+
(I didn't update)
## Comment 9472
Date: 2008-05-28 11:06:17 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
only points and linestrings can have an Coord Sequence. So we now protect against GetCoord returning NULL.
## Comment 9473
Date: 2008-05-28 11:52:08 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
added a test X_crash.SF-1971632.sql to geom/BugTracker. The test output isn't correct as we do expect an error.
## Comment 9474
Date: 2008-06-02 08:48:54 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
after the m5 multiplex fix we now get the correct errors too, ie closing this bug.
## Comment 9475
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1971632 at http://sourceforge.net/support/tracker.php?aid=1971632
| X(g) / Y(g) segmentation fault | https://api.github.com/repos/MonetDB/MonetDB/issues/1675/comments | 0 | 2020-11-30T09:51:57Z | 2024-06-27T11:30:06Z | https://github.com/MonetDB/MonetDB/issues/1675 | 753,327,166 | 1,675 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-25 03:09:04 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2008-05-28 09:32:53 +0200
## Comment 9465
Date: 2008-05-25 03:09:04 +0200
From: @skinkie
Currently [1] (Installation) points to:
mclient -lsq < [PATH]/src/sql/geom.sql
I think it would be better to refer to a non-source package for this sql file. Hence:
mclient -lsq < [PATH]/share/MonetDB/sql/geom.sql
## Comment 9466
Date: 2008-05-25 03:10:27 +0200
From: @skinkie
Logged In: YES
user_id=533026
Originator: YES
[1] http://monetdb.cwi.nl/SQL/Documentation/SQL_002fGIS.html
## Comment 9467
Date: 2008-05-27 15:21:42 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
This is indeed a better path for in the documentation.
Niels, can you fix this whilst you're fixing the other bug?
## Comment 9468
Date: 2008-05-28 09:32:53 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
fixed in web site cvs repo
## Comment 9469
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1971612 at http://sourceforge.net/support/tracker.php?aid=1971612
| Geom.sql path in documentation | https://api.github.com/repos/MonetDB/MonetDB/issues/1674/comments | 0 | 2020-11-30T09:51:54Z | 2024-06-27T11:30:05Z | https://github.com/MonetDB/MonetDB/issues/1674 | 753,327,133 | 1,674 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-25 03:05:58 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2008-05-28 11:53:52 +0200
## Comment 9461
Date: 2008-05-25 03:05:58 +0200
From: @skinkie
The geom example that is written [1] seems to be non functional. The last query results in:
sql>SELECT forests.name,buildings.name
more>FROM forests,buildings
more>WHERE forests.name = 'Green Forest' and
more> Overlaps(forests.shape, buildings.outline) = true;
!types multipolygon(0,0) (wkb) and geometry(0,0) (wkb) are not equal
[1] http://monetdb.cwi.nl/SQL/Documentation/SQL_002fGIS.html
## Comment 9462
Date: 2008-05-27 15:20:34 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Totally reproduceable.
Niels, is the query at fault or the schema?
## Comment 9463
Date: 2008-05-28 11:53:52 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Problem fixed in sql, we now overload sql-external types when they use the same monetdb atom. Test added to src/sql example.sql
## Comment 9464
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1971610 at http://sourceforge.net/support/tracker.php?aid=1971610
| Geom example doesn't work | https://api.github.com/repos/MonetDB/MonetDB/issues/1673/comments | 0 | 2020-11-30T09:51:52Z | 2024-06-27T11:30:04Z | https://github.com/MonetDB/MonetDB/issues/1673 | 753,327,099 | 1,673 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-15 05:06:03 +0200
From: @MarcinZukowski
To: @sjoerdmullender
Version: -- development
Last updated: 2009-01-15 04:11:51 +0100
## Comment 9455
Date: 2008-05-15 17:06:03 +0200
From: @MarcinZukowski
I have a MIL operator that requires a bat name as a parameter. Later, this bat name is used to retrieve the actual bat and do something with it.
If I have a BAT as a variable in MIL, I typically do the following:
var batId := b.bbpname();
operator(batId);
However, if batId is a result of a reverse() operation, as in:
var a := bat(void, int);
var b := a.reverse();
now both a.bbpname() and b.bbpname() are the same. If I give b to the operator, and then search for it with BBPindex (in C), I get a, not b.
Any way to avoid this ambiguity? And please, I don't consider rename() the solution - it's just oh-so-unsafe, example:
var x := new(void, int);
x.rename("A");
x.info().find("batId").print(); A
var y := x.reverse();
y.info().find("batId").print(); A
y.rename("B");
y.info().find("batId").print(); B
var z := y.reverse();
z.info().find("batId").print(); A
z.rename("C");
z.info().find("batId").print(); C
x.info().find("batId").print(); C (!!!)
Above can be seen as a bug by itself probably
## Comment 9456
Date: 2009-01-15 10:46:06 +0100
From: @sjoerdmullender
If I understand correctly, there are two parts to this report.
- When the reverse bat has not been named explicitly, bbpname returns the name of the non reversed bat.
- When renaming a bat, the effect can be seen through other variables pointing to the same bat.
The latter is definitely not a bug. It is the bat that gets renamed, no matter how you refer to it. Naming is not a label that hangs on the variable, it is a label that hangs on the bat that is referenced through the variable. Remember, bats have an existence apart from any variables referring to it.
The former is, to say the least, unfortunate. The implementation is clear: The core of the BBPname macro is
((i) > 0 || BBP_logical(i))?BBP_logical(i):BBP_logical(-(i))
so if the reverse (i<0) does not have a name, the name for the non reversed bat is returned.
Various possible solutions come to mind:
- Leave as is; ;-)
- Return empty string, indicating no name;
- Give reverse bats their own names automatically (like tmp_XXX for non reversed bats).
This last solutions is probably the preferred solution for Marcin. It does involve some work since the automatically assigned name is used and interpreted in various places, and those places also need to work with an automatically created name for the reverse bat.
## Comment 9457
Date: 2009-01-15 15:16:49 +0100
From: @sjoerdmullender
I implemented my third option in the Development branch.
Marcin, does this solution satisfy you?
## Comment 9458
Date: 2009-01-15 15:28:59 +0100
From: @MarcinZukowski
I am not using it anymore, so I do not have an opinion.
## Comment 9459
Date: 2009-02-16 13:11:09 +0100
From: @drstmane
test added in MonetDB4/tests/BugTracker/Tests/names_of_reversed_BATs.SF-1964658.*
appears to work fine.
## Comment 9460
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1964658 at http://sourceforge.net/support/tracker.php?aid=1964658
| Problem with names of reverse()'d BATs. | https://api.github.com/repos/MonetDB/MonetDB/issues/1672/comments | 0 | 2020-11-30T09:51:49Z | 2024-06-27T11:30:03Z | https://github.com/MonetDB/MonetDB/issues/1672 | 753,327,065 | 1,672 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-15 03:29:06 +0200
From: @grobian
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-06-01 10:17:35 +0200
## Comment 9448
Date: 2008-05-15 15:29:06 +0200
From: @grobian
sql>create table test_property(subject integer, p1 integer, p2 integer,
unique(subject, p1), unique(subject, p2));
sql>\d test_property
CREATE TABLE "sys"."test_property" (
"subject" int,
"p1" int,
"p2" int,
CONSTRAINT "test_property_subject_p2_unique" UNIQUE ("subject"),
CONSTRAINT "test_property_subject_p1_unique" UNIQUE ("subject", "p2",
"p1")
);
Note that the two unique constraints are not dumped correctly, as one is dumped to be on "subject" alone, the other on "subject", "p2" and "p1". It is a dumping problem, as the same code works fine with JdbcClient:
(pegasus:~) fabian% JdbcClient -dAnton
Welcome to the MonetDB interactive JDBC terminal!
Database: MonetDB v5.5.0, 'Anton'
Driver: MonetDB Native Driver v1.7 (Canephora_p2 20080319 based on MCL v1.2)
Type \q to quit, \h for a list of available commands
auto commit mode: on
monetdb-> create table test_property(subject integer, p1 integer, p2 integer,
monetdb=( unique(subject, p1), unique(subject, p2));
Operation successful
monetdb-> \d test_property
CREATE TABLE "sys"."test_property" (
"subject" int,
"p1" int,
"p2" int,
CONSTRAINT "test_property_subject_p1_unique" UNIQUE ("subject", "p1"),
CONSTRAINT "test_property_subject_p2_unique" UNIQUE ("subject", "p2")
);
monetdb->
## Comment 9449
Date: 2008-05-15 16:19:53 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Fixed in CVS (stable branch--propagation will follow).
## Comment 9450
Date: 2008-05-15 18:11:41 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
I forgot to mention: there is also a test: src/test/BugTracker multi-column-constraint.SF-1964587
## Comment 9451
Date: 2008-05-27 18:07:04 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
re-opened as test fails --- possibly only requiring a stable output approval ...
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests4103/GNU.64.64.d-Fedora8/src_test_BugTracker/multi-column-constraint.SF-1964587.out.00.html
## Comment 9452
Date: 2008-05-27 23:04:26 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
The test fails because other tests do not clean up after themselves.
## Comment 9453
Date: 2008-06-01 22:17:35 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
"Fixed" by running this test as first in the sql/src/tests/BugTracker/Tests/ directory (and ensuring that this test cleans up after itself).
## Comment 9454
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1964587 at http://sourceforge.net/support/tracker.php?aid=1964587
| mclient doesn't dump multi-colum unique constraint correctly | https://api.github.com/repos/MonetDB/MonetDB/issues/1671/comments | 0 | 2020-11-30T09:51:47Z | 2024-06-27T11:30:02Z | https://github.com/MonetDB/MonetDB/issues/1671 | 753,327,040 | 1,671 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-15 10:11:34 +0200
From: @lsidir
To: Lefteris Sidirourgos <<lsidir>>
Version: -- development
Last updated: 2009-11-16 05:48:53 +0100
## Comment 9432
Date: 2008-05-15 10:11:34 +0200
From: @lsidir
Insert .. into, inserts attributes in wrong order.
Also, insert into as first/last/before/after should be tested individually in the test web with new tests for both elements and attributes.
## Comment 9433
Date: 2008-05-16 16:10:13 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Originator: NO
This report is too terse to exactly know what your problem is. But
be aware that
-- There is no order among attributes of the same element node.
-- The order in which `insert into ...' instructions are applied to
the store is undefined.
## Comment 9434
Date: 2008-05-16 16:32:56 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: YES
You are right that this report is too terse to exactly know what my problem is:) but it serves more as a remainder, since I assigned this to myself. The problem is that some tests on the testweb are failing because of different attribute order than the one approved, second that the order of the insert into in the update spec is defined now (http://www.w3.org/TR/xquery-update-10/id-upd-insert-into : The semantics of upd:insertInto are identical to the semantics of upd:insertBefore) and finally that there are not enough tests on the testweb to correctly check if insert before/as first is actually done correctly.
## Comment 9435
Date: 2008-05-16 22:58:01 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
The only time order matters when inserting attributes is when you're inserting the same attribute with different values multiple times into the same element. I don't know what the standard says here, but we would like the last one to stick (unless the standard prohibits this).
The different order of attributes on output is purely an inconvenience. It is no shape or fashion a bug.
(I would like to have an option to have the attributes produces in alphabetical order so that we can get consistent test results, but it is not a bug if the order is different. Not even if each run produces a different order.)
## Comment 9436
Date: 2008-05-17 17:11:44 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: YES
Let me give an example why this is a bug then:)
Test tests/Update/update fails for various reasons. One reason is the different order of attributes than the approved output, but this is not a bug indeed. However, for example, the element with text "element content 0020" fails because the approved output ends with
element content 0020<a/><b/></element>
while the algebra outputs
element content 0020<b/><a/></element>
which is a wrong order in inserting an element. Thats why I said we need also to add tests that just test the correct order (i.e., update.xq test is to big to track what goes wrong).
I am currently trying to debug this, and make more tests.
## Comment 9437
Date: 2008-05-17 19:59:00 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Originator: NO
It seems like I have to repeat:
The order in which `insert into ...' instructions are applied to the
store is undefined.
This means that
let $a := ...
return (insert <a/> as first into $a,
insert <b/> as first into $a)
is semantically equivalent to
let $a := ...
return (insert <b/> as first into $a,
insert <a/> as first into $a) .
(It's kind of strange that the Update Facility is defined this way.
Order is pervasive in XQuery, but undefined in the Update Facility. To
confuse things even more, the Update Facility talks about a ``pending
update list,'' whereas it actually is not a list. It is unordered.)
(Not sure whether XQuery's order indifference in that respect is the
case why the tests fail. Earlier versions of MonetDB/XQuery did
preserve the order of update instructions. Don't know whether it's
still supposed to do that.)
## Comment 9438
Date: 2008-05-17 21:15:37 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: YES
Sorry but I don't understand why we are having this conversation.
I was the one who implemented the update functionality of algebra, I saw that the test were failing, and given the fact that we are getting to a release, I wanted to document the fact that more detailed tests are needed and even try to make it compatible with MPS so the tests would work fine for both back-ends. I just didn't had time to investigate this further yet, thats why is still open (after all it is there only 2 days).
## Comment 9439
Date: 2008-06-04 09:30:21 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: YES
The case of an insert of a sequence of nodes (not a sequence of inserts) was inserting in wrong order. The bug was fixed and 2 tests were added in the testweb: insert_test_order and insert_test_order_seq.
## Comment 9440
Date: 2008-06-08 16:55:50 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Re-opened to remind us that ALG still/again produces different order/output than MPS with
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_Update/insert_test_order_seq.out.00.html
AFAIK, Lefteris is already aware of this ...
## Comment 9441
Date: 2008-12-12 00:16:32 +0100
From: @peterboncz
Lefteris: is the current output the correct one?
## Comment 9442
Date: 2009-02-15 19:12:00 +0100
From: @drstmane
status report:
ALG
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_Update/insert_test_order_seq.out.00.html
still produces different output than
MPS
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_Update/insert_test_order_seq.out.00.html
## Comment 9443
Date: 2009-02-15 19:43:46 +0100
From: @lsidir
This wrong order still appears in Algebra indeed. I lowered the priority since I am not going to fix this for the upcoming release. The wrong order here is a minimal problem since as Jens already said:
-- The order in which `insert into ...' instructions are applied to the store is undefined.
This is implementation defined.
## Comment 9444
Date: 2009-11-16 14:55:20 +0100
From: @drstmane
Lefteris (et. al),
what's you're preference for this one to clean-up (also) the Pathfinder TestWeb to a "usable" status?
Should we approve the Algebra-specific output next to the MPS output?
Or should we skip this test (for Algebra only) until this problem has been fixed?
Cf.,
ALG:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_Update/insert_test_order_seq.out.00.html
MPS:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora10/tests_Update/insert_test_order_seq.out.00.html
## Comment 9445
Date: 2009-11-16 16:45:27 +0100
From: @lsidir
Hi Stefan,
the algebra output should be approved and the bug should be closed as fixed. The output is not wrong since the order it turns out to be implementation specific.
## Comment 9446
Date: 2009-11-16 17:48:52 +0100
From: @drstmane
Approved Algebra-specific insert order.
Closing.
## Comment 9447
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1964365 at http://sourceforge.net/support/tracker.php?aid=1964365
| PF/Alg: insert..into inserts in wrong order | https://api.github.com/repos/MonetDB/MonetDB/issues/1670/comments | 0 | 2020-11-30T09:51:44Z | 2024-06-27T11:30:01Z | https://github.com/MonetDB/MonetDB/issues/1670 | 753,327,000 | 1,670 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-12 07:35:56 +0200
From: kephale <<kharrington>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2008-05-20 08:14:10 +0200
## Comment 9425
Date: 2008-05-12 19:35:56 +0200
From: kephale <<kharrington>>
After a fresh install of MonetDB via the install shell script merovingian will not start.
Installation command:
sh monetdb-install.sh --enable-sql --nightly=stable
merovingian execution command:
./MonetDB/bin/merovingian
Result:
unable to open '' for writing: No such file or directory
A quick trace into the MonetDB code leads me to believe that there is some issue with being assigned a PID.
Thanks,
Kyle
## Comment 9426
Date: 2008-05-12 19:46:32 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
I'm not very eager to fix this, as the latest I heard is that the current stable branch of sql is not going to be released ever, since a new feature release is scheduled.
Is the mero_pidfile= setting in your monetdb5.conf set to something non-empty?
## Comment 9427
Date: 2008-05-12 19:54:21 +0200
From: kephale <<kharrington>>
Logged In: YES
user_id=1686557
Originator: YES
Yes,
mero_pidfile=${prefix}/var/run/merovingian.pid
and the prefix is set to the MonetDB directory in my home directory
## Comment 9428
Date: 2008-05-14 14:44:31 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
can you please try with --nightly=current to see if the same problem is there as well?
## Comment 9429
Date: 2008-05-20 20:01:32 +0200
From: kephale <<kharrington>>
Logged In: YES
user_id=1686557
Originator: YES
I am not getting the error yet, but it appears sporadically. If it happens again I will post.
Thank you!
## Comment 9430
Date: 2008-05-20 20:14:10 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
If it's only in the "current" release branch, I won't fix it. I'm closing this bug now as it deals with that branch. If you see the bug again on the current development branch, please reopen and change the "group" accordingly. Thanks!
## Comment 9431
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1962530 at http://sourceforge.net/support/tracker.php?aid=1962530
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.
| merovingian fails to start | https://api.github.com/repos/MonetDB/MonetDB/issues/1669/comments | 0 | 2020-11-30T09:51:41Z | 2024-06-28T13:30:04Z | https://github.com/MonetDB/MonetDB/issues/1669 | 753,326,968 | 1,669 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-09 04:05:30 +0200
From: @lsidir
To: Lefteris Sidirourgos <<lsidir>>
Version: -- development
Last updated: 2008-05-13 02:43:06 +0200
## Comment 9421
Date: 2008-05-09 16:05:30 +0200
From: @lsidir
Hi,
A segmentation fault is thrown when the following query is ran for the second time (sometimes it needs a third time). This only happens for the algebra version of pathfinder when the query is run through mclient -lxq -G
count(doc("dblp.xml")/dblp/*[author="Michael Stonebraker" and author="Hector Garcia-Molina" and year > 1950]/title)
The document dblp.xml is the default one from http://dblp.uni-trier.de/xml/
I attach the trace obtained by gdb.
Thank you,
lefteris
## Comment 9422
Date: 2008-05-09 19:01:58 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
Lefteris,
I get a different segfault -- probably because MonetDB ran out of (address) space on my 32-bit machine.
If you want that bug fixed you probably have to investigate a little bit yourself (e.g., what is stored inside the literals).
Mserver: /local_tmp/work/MonetDB/src/gdk/gdk_utils.mx:1108: GDKfree: Assertion `size != 0' failed.
Program received signal SIGABRT, Aborted.
[Switching to Thread -1343362144 (LWP 20968)]
0xffffe410 in __kernel_vsyscall ()
(gdb) bt
0 0xffffe410 in __kernel_vsyscall ()
1 0xb728c8a0 in raise () from /lib/libc.so.6
2 0xb728dfc3 in abort () from /lib/libc.so.6
3 0xb7285feb in __assert_fail () from /lib/libc.so.6
4 0xb7a61b21 in GDKfree (blk=0x799a8010) at /local_tmp/work/MonetDB/src/gdk/gdk_utils.mx:1108
5 0xb79e2760 in HEAPfree (h=0x8b1f080) at /local_tmp/work/MonetDB/src/gdk/gdk_heap.mx:263
6 0xb7b39078 in BATdelete (b=0x8b1eff0) at /local_tmp/work/MonetDB/src/gdk/gdk_storage.mx:762
7 0xb79dfbfb in BBPdestroy (b=0x8b1eff0) at /local_tmp/work/MonetDB/src/gdk/gdk_bbp.mx:2439
8 0xb79df43b in decref (i=763, logical=0, releaseShare=0) at /local_tmp/work/MonetDB/src/gdk/gdk_bbp.mx:1383
9 0xb7eae1ba in Myyclean (t=0x8b20058) at /local_tmp/work/MonetDB4/src/monet/yytree.mx:766
10 0xb7eae031 in Myyclean (t=0x89d2320) at /local_tmp/work/MonetDB4/src/monet/yytree.mx:766
11 0xb7ea8bb1 in interpret_seqblock (stk=583, lt=0x810c5c0, res=0xafedd39c, scope=1) at /local_tmp/work/MonetDB4/src/monet/monet_interpreter.mx:1871
12 0xb7e9abe7 in interpret (stk=1, lt=0x8b1de58, res=0xafedd39c) at /local_tmp/work/MonetDB4/src/monet/monet_interpreter.mx:731
13 0xb7f4789e in CMDcatch (stk=1, lt=0x8b1de38, res=0xafedd39c) at /local_tmp/work/MonetDB4/src/modules/plain/builtin.mx:1045
14 0xb7e9a81c in interpret (stk=1, lt=0x8b1de38, res=0xafedd39c) at /local_tmp/work/MonetDB4/src/monet/monet_interpreter.mx:819
15 0xb7ea9049 in interpret_assignment (stk=<value optimized out>, lt=0x8b1ddf0, res=0xafedd39c) at /local_tmp/work/MonetDB4/src/monet/monet_interpreter.mx:1820
16 0xb7e9ab64 in interpret (stk=1, lt=0x8b1ddf0, res=0xafedd39c) at /local_tmp/work/MonetDB4/src/monet/monet_interpreter.mx:724
17 0xb7ea8b61 in interpret_seqblock (stk=1, lt=0x8771450, res=0xafedd39c, scope=0) at /local_tmp/work/MonetDB4/src/monet/monet_interpreter.mx:1870
18 0xb7e9abe7 in interpret (stk=1, lt=0x8a08910, res=0xafedd39c) at /local_tmp/work/MonetDB4/src/monet/monet_interpreter.mx:731
19 0xb19c2d24 in xquery_tree_exec (ctx=0x8147ac0, t=0x8a08910, repeat=20968) at /local_tmp/work/pathfinder/runtime/pathfinder.mx:4263
20 0xb19c2ec5 in xquery_mil_exec (ctx=0x8147ac0, buf=<value optimized out>) at /local_tmp/work/pathfinder/runtime/pathfinder.mx:4321
21 0xb19c52e8 in xquery_compile_exec (ctx=0x8147ac0, url=0x8b97e79 "count(doc(\"dblp.xml\")/dblp/*[author=\"Michael Stonebraker\" and\nauthor=\"Hector Garcia-Molina\" and year > 1950]/title)\n",
## Comment 9423
Date: 2008-05-13 14:43:06 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: YES
Bug fixed on the development branch and a test has been added. The solution was to initialize correct the la_empty_tbl constructor.
Closing the bug.
## Comment 9424
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1961027 at http://sourceforge.net/support/tracker.php?aid=1961027
| Segmentation fault in the compiler after second run | https://api.github.com/repos/MonetDB/MonetDB/issues/1668/comments | 0 | 2020-11-30T09:51:39Z | 2024-06-27T11:29:59Z | https://github.com/MonetDB/MonetDB/issues/1668 | 753,326,944 | 1,668 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-08 06:08:16 +0200
From: @sjoerdmullender
To: GDK devs <<bugs-common>>
Version: 11.17.9 (Jan2014)
CC: holger.pirk, @mlkersten
Last updated: 2015-11-11 09:16:09 +0100
## Comment 9410
Date: 2008-05-08 18:08:16 +0200
From: @sjoerdmullender
mil>var a := new(void,oid).append(oid(nil)).append(1@0).tunique();
mil>a.info().find("hkey").print();
[ "1" ]
mil>var b := kunion(a,a);
mil>b.info().find("hkey").print();
[ "1" ]
mil>b.print();
-----------------
h t name
oid void type
-----------------
[ nil, nil ]
[ 1@0, nil ]
[ nil, nil ]
If run with debugmask 10, BATpropcheck complains about b having hkey set.
The questions are:
- is tunique right in setting hkey, even in the presence of a nil?
- is kunion right in producing three values (since nil != nil)?
- is kunion right in setting hkey (again since nil != nil)?
- is BATpropcheck right in complaining that hkey is set (since nil = nil, or perhaps because hkey should never be set in the presence of nils)?
## Comment 9411
Date: 2008-06-05 16:22:09 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: YES
Peter, I'd like you to give your opinion on this issue.
## Comment 9412
Date: 2008-08-26 09:20:43 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
See also
[ 2075180 ] the unique column can't insert more than 1 row with null
http://sourceforge.net/tracker/index.php?func=detail&aid=2075180&group_id=56967&atid=482468
## Comment 9413
Date: 2008-08-26 09:35:05 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
tunion is right in setting hkey
Kunion is wrong in producing three results and in setting hkey.
Batpropcheck is right in complaining about it.
My answer is based on the historical situation where nil is just another value; that is before giving nil special treatment in select and join.
## Comment 9414
Date: 2008-08-26 09:51:00 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
so, the semantics of NIL is
- in case of select and join (I guess/hope):
NIL is not compareable to NIL; hence the result of comparing NIL to NIL is never TRUE (but actually not FALSE either)
- in case of [tk]unique:
NIL is comparable to NIL and the result of comparing NIL to NIL is TRUE
?
Shouldn't try to find a single consistent semantic for NILs?
## Comment 9415
Date: 2008-08-26 15:59:27 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
For SQL it would be best to support the 'ignore' nil option. Ie keyedness is n't affected by the nils in the column.
## Comment 9416
Date: 2008-08-29 09:05:05 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
one more interesting problem which is related. select (x, nil, val), ie less than handling breaks when val is nil. x < nil should return nothing but now it returns the full x (well except for nils). This case happens in sql were we get a nil when no value is returned from a sub query (see http://sourceforge.net/support/tracker.php?aid=2080168 for example).
Probably we need to add wrappers for the range and equality selects.
## Comment 9417
Date: 2008-09-10 11:17:35 +0200
From: @drstmane
See also
[ 2103348 ] unique problem with nulls
http://sourceforge.net/tracker/index.php?func=detail&aid=2103348&group_id=56967&atid=482468
[ 2075241 ] When the NULL is in a column,it shouldn't add primary key
http://sourceforge.net/tracker/index.php?func=detail&aid=2075241&group_id=56967&atid=482468
[ 2075180 ] the unique column can't insert more than 1 row with null
http://sourceforge.net/tracker/index.php?func=detail&aid=2075180&group_id=56967&atid=482468
## Comment 9418
Date: 2009-04-07 10:40:31 +0200
From: @peterboncz
I have been overruled before in nil matters (the in my eyes very confusing distinction between nil and void), I think it is not used consistently anyway now. So answering logical questions about nils has become impossible regrettably.
Maybe you can ask niels?
## Comment 9419
Date: 2009-04-08 17:47:17 +0200
From: @sjoerdmullender
To add to the confusion ;-)
Using the above variable a, we get:
mil>kdiff(a,a).print();
-----------------
h t name
oid void type
-----------------
[ nil, nil ]
This is actually the reason why kunion returns what it does, since internally it uses the implementation of kdiff.
There is an explicit comment in the implementation (gdk_setop.mx:425) about nils not matching. If this weren't the case, it could take a shortcut: if the two arguments happen to be the same pointer, return the empty bat. But that isn't how it currently works.
## Comment 9420
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1960373 at http://sourceforge.net/support/tracker.php?aid=1960373
## Comment 15665
Date: 2011-03-28 17:34:56 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
## Comment 16021
Date: 2011-07-29 10:58:43 +0200
From: @sjoerdmullender
Apr2011-SP2 has been released.
## Comment 16260
Date: 2011-09-16 15:08:30 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 18161
Date: 2012-11-27 17:26:19 +0100
From: Holger <<holger.pirk>>
still needs to be decided but has a test since revision e210609e0aaa
## Comment 18206
Date: 2012-11-28 13:45:51 +0100
From: Holger <<holger>>
Changeset [eab3b479ec4f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=eab3b479ec4f) made by Holger Pirk <holger@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=eab3b479ec4f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=eab3b479ec4f)
Changeset description:
* added a test for bug #1667
## Comment 18905
Date: 2013-07-06 21:41:37 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [84e331264f97](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=84e331264f97) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=84e331264f97](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=84e331264f97)
Changeset description:
kunion-and-nil.Bug-1667: backout changeset 48027:6b8b0867c049;
let' no approve output that's incomplete becasue an assertion was triggered
## Comment 21503
Date: 2015-11-11 09:16:09 +0100
From: @mlkersten
The kunion() (and friends) operation has been dropped altogether.
For that reason this issue can be closed.
| kunion and nil | https://api.github.com/repos/MonetDB/MonetDB/issues/1667/comments | 0 | 2020-11-30T09:51:36Z | 2024-06-28T07:37:03Z | https://github.com/MonetDB/MonetDB/issues/1667 | 753,326,917 | 1,667 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-08 03:59:47 +0200
From: Wouter Alink <<alink>>
To: Lefteris Sidirourgos <<lsidir>>
Version: -- development
Last updated: 2008-05-13 02:53:50 +0200
## Comment 9407
Date: 2008-05-08 15:59:47 +0200
From: Wouter Alink <<alink>>
The query:
let $proj :=
element project {
attribute name {"test"},
element notes {"beer"},
element description {"noot"}
}
return
do insert $proj as last into doc("aap.xml")/noot
Returns the following error when aap.xml is an updatable document with a single element "<noot/>":
problem: ERROR: fetch(29288150790572448) illegal position
90.
## Comment 9408
Date: 2008-05-13 14:53:50 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
Bug fixed on the development branch. No test needed because it is already been checked by the existing tests.
## Comment 9409
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1960271 at http://sourceforge.net/support/tracker.php?aid=1960271
| XQ (algebra): insert as last into | https://api.github.com/repos/MonetDB/MonetDB/issues/1666/comments | 0 | 2020-11-30T09:51:34Z | 2024-06-27T11:29:57Z | https://github.com/MonetDB/MonetDB/issues/1666 | 753,326,887 | 1,666 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-08 03:17:09 +0200
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-05-11 08:22:45 +0200
## Comment 9403
Date: 2008-05-08 15:17:09 +0200
From: @romulogoncalves
The example shows the problem:
sql>select * from tables where id = 0 = 1 = 0 = 1 LIMIT 1;
+-----+--------+----------+------+-----+-------+--------------+----------+
| id |name |schema_id |query |type |system |commit_action |temporary |
+=====+========+==========+======+=====+=======+==============+==========+
| 980 |schemas | 979 |null | 0 |true | 0 | 0 |
+-----+--------+----------+------+-----+-------+--------------+----------+
sql>
The problem is in the this part of the sql_parser:
predicate:
comparison_predicate
| between_predicate
| like_predicate
| test_for_null
| in_predicate
| all_or_any_predicate
| existence_test
| scalar_exp
;
pred_exp:
predicate
;
To compare we have the following cases:
comparison_predicate:
pred_exp COMPARISON pred_exp
| pred_exp '=' pred_exp
;
It not only allows infinite comparison using pred_exp, but it also has wrong semantics once the comparison is done to more than one value.
## Comment 9404
Date: 2008-05-08 15:24:00 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
Well,
The semantics might be correct because there is no table with id = 0 (id = 0 false), but if then I do "= 1 = 0 = 1" I make the clause id = 0 (which was false) true.
In this case I will get the first row of the table tables (because I used LIMIT 1).
Is this correct and accepted on SQL?
Romulo
## Comment 9405
Date: 2008-05-11 08:22:45 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
The semantics are indeed correct (and supported by sql). So closing this bug as invalid.
## Comment 9406
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1960253 at http://sourceforge.net/support/tracker.php?aid=1960253
| comparison with several values | https://api.github.com/repos/MonetDB/MonetDB/issues/1665/comments | 0 | 2020-11-30T09:51:31Z | 2024-06-28T07:37:02Z | https://github.com/MonetDB/MonetDB/issues/1665 | 753,326,868 | 1,665 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-07 11:41:35 +0200
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-05-09 11:30:26 +0200
## Comment 9398
Date: 2008-05-07 23:41:35 +0200
From: @romulogoncalves
The following sql functions crash mserver5
CREATE FUNCTION f2 ()
RETURNS TABLE (
fieldID bigint,
distance bigint
)
BEGIN
DECLARE TABLE cover(
htmidStart bigint, htmidEnd bigint
);
INSERT into cover
SELECT 1, 2;
RETURN TABLE (
SELECT htmidStart, 1 as distance
FROM cover H);
END;
CREATE FUNCTION f3 ()
RETURNS TABLE (
fieldID bigint
)
BEGIN
RETURN TABLE (
SELECT fieldID
FROM f2 () n
ORDER BY fieldID ASC LIMIT 1);
END;
drop function f2();
drop function f3();
some debug information:
Program received signal SIGABRT, Aborted.
[Switching to Thread 1107310928 (LWP 16859)]
0x0000003c6d030ec5 in raise () from /lib64/libc.so.6
(gdb) up
1 0x0000003c6d032970 in abort () from /lib64/libc.so.6
(gdb) up
2 0x0000003c6d02a11f in __assert_fail () from /lib64/libc.so.6
(gdb) up
3 0x00002aaabe745130 in find_order (s=0x30375e8)
at /ufs/goncalve/MonetDB/current/sql/src/server/sql_select.mx:3652
3652 assert(s->type == st_order || s->type == st_reorder);
(gdb) up
4 0x00002aaabe74517b in sql_reorder (order=0x30375e8, s=0x2fd5318)
at /ufs/goncalve/MonetDB/current/sql/src/server/sql_select.mx:3664
3664 stmt *o = find_order(order);
(gdb) up
5 0x00002aaabe73949b in flat_subquery (sql=0x2d71a68, sq=0x2d741e8)
at /ufs/goncalve/MonetDB/current/sql/src/server/sql_select.mx:294
294 n = sql_reorder(stmt_dup(s->op1.stval), stmt_dup(s->op2.stval));
(gdb) up
6 0x00002aaabe73dcff in sql_table_exp (sql=0x2d71a68, scp=0x0, sym=0x2d741e8)
at /ufs/goncalve/MonetDB/current/sql/src/server/sql_select.mx:1586
1586 stmt *ls = flat_subquery(sql, sym);
(gdb) up
7 0x00002aaabe73e35a in sql_value_exp (sql=0x2d71a68, scp=0x0, se=0x2d743e8,
grp=0x0, subset=0x0, f=3, ek=
{type = 0 '\0', card = 4 '\004', reduce = 0 '\0'})
at /ufs/goncalve/MonetDB/current/sql/src/server/sql_select.mx:1708
1708 return sql_table_exp(sql, scp, se->data.sym);
(gdb)
Romulo
## Comment 9399
Date: 2008-05-08 10:46:57 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
test added at:
sql/src/test/BugTracker/Tests/order_by_over_table_from_another_function.SF-1959822.sql
## Comment 9400
Date: 2008-05-08 17:16:55 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
A more simple example:
create table t2 (fieldID int);
CREATE FUNCTION f3 ()
RETURNS TABLE (
fieldID bigint
)
BEGIN
RETURN TABLE (
SELECT fieldID
FROM t2
ORDER BY fieldID ASC LIMIT 1);
END;
drop table t2;
drop function f3();
Here we can see that the reason is type of the statement when we check the order.
(gdb) p s
$1 = (stmt *) 0x4aad2c8
(gdb) p s->type
$2 = st_limit
(gdb) l
This happens only with select in the return clause of a function.
## Comment 9401
Date: 2008-05-09 11:30:25 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
Fixed on the check in:
[Monetdb-sql-checkins] sql/src/server sql_select.mx,,1.229,1.230
Modified Files:
sql_select.mx
Log Message:
Check if the check types worked fine (be defensive).
This was the problem for bug [ monetdb-Bugs-1959410 ] between with column
When we combine order by with limit within return statement, the ordered statement is
inside the limit statement.
This was the reason for bug [ monetdb-Bugs-1959410 ] between with column
## Comment 9402
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1959822 at http://sourceforge.net/support/tracker.php?aid=1959822
| order by over table from another function | https://api.github.com/repos/MonetDB/MonetDB/issues/1664/comments | 0 | 2020-11-30T09:51:29Z | 2024-06-27T11:29:55Z | https://github.com/MonetDB/MonetDB/issues/1664 | 753,326,833 | 1,664 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-07 02:19:01 +0200
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-05-22 03:15:17 +0200
## Comment 9394
Date: 2008-05-07 14:19:01 +0200
From: @romulogoncalves
The following sql statements gave an expected syntax error:
create function f1()
RETURNS int
BEGIN
return 0;
END;
create table t1 (id int);
select id from t1 where f1() IS NOT NULL;
drop function f1;
drop table t1;
MAPI = monetdb@localhost:50000
QUERY = select id from t1 where f1() IS NOT NULL;
ERROR = !syntax error, unexpected IS, expecting SCOLON in: "select id from t1 where f1() is"
Romulo
## Comment 9395
Date: 2008-05-08 10:45:43 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
test added at:
sql/src/test/BugTracker/Tests/is_not_null_syntax_error.SF-1959456.sql
## Comment 9396
Date: 2008-05-22 15:15:17 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
there where 2 bugs. 1) we didn't handle arbitrary expressions before the IS NOT NULL and this a special case predicate (return all or nothing).
Both problems are fixed.
## Comment 9397
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1959456 at http://sourceforge.net/support/tracker.php?aid=1959456
| is not null syntax error | https://api.github.com/repos/MonetDB/MonetDB/issues/1663/comments | 0 | 2020-11-30T09:51:26Z | 2024-06-27T11:29:54Z | https://github.com/MonetDB/MonetDB/issues/1663 | 753,326,795 | 1,663 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-07 02:13:47 +0200
From: @romulogoncalves
To: Romulo Goncalves <<goncalve>>
Version: -- development
Last updated: 2008-05-08 11:21:16 +0200
## Comment 9391
Date: 2008-05-07 14:13:47 +0200
From: @romulogoncalves
The following sql code gives an error which was not expected to happen.
create table t1 (id int);
select id from t1 where bit_and(id,0xFFFFFFFFFFFFFFF0000) > 0;
drop table t1;
MAPI = monetdb@localhost:50000
QUERY = select id from t1 where bit_and(id,0xFFFFFFFFFFFFFFF0000) > 0;
ERROR = !invalid hexadecimal number or hexadecimal too large (0xFFFFFFFFFFFFFFF0000) in: "select id from t1 where bit_and(id,0xFFFFFFFFFFFFFFF0000"
!syntax error, unexpected ')' in: ")"
Romulo
## Comment 9392
Date: 2008-05-08 11:21:15 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
This time MonetDB is right.
16^19 = 75557863725914323419136
2^64 = 18446744073709551616
So such hexadecimal does not fit into a 64 bit int.
I declare this bug closed...
## Comment 9393
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1959450 at http://sourceforge.net/support/tracker.php?aid=1959450
| hexadecimal too big | https://api.github.com/repos/MonetDB/MonetDB/issues/1662/comments | 0 | 2020-11-30T09:51:23Z | 2024-06-28T07:37:02Z | https://github.com/MonetDB/MonetDB/issues/1662 | 753,326,761 | 1,662 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-07 01:05:40 +0200
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-05-09 11:30:52 +0200
## Comment 9387
Date: 2008-05-07 13:05:40 +0200
From: @romulogoncalves
The following sql code crashes the mserver 5:
create table t4 (id int);
create table t5 (age float, yea int);
select yea from t4, t5 where age between 0.03 and id < 30 ;
drop table t4;
drop table t5;
Some debug information to help in the error location:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1107310928 (LWP 7995)]
0x00002aaabe743666 in sql_logical_exp_ (sql=0x24ff678, scp=0x2766cb8,
sc=0x2502008, grp=0x0, subset=0x0, f=1, ek=
{type = 0 '\0', card = 4 '\004', reduce = 1 '\001'})
at /ufs/goncalve/MonetDB/current/sql/src/server/sql_select.mx:3222
3222 if (rs1->nrcols > 0 || rs2->nrcols > 0 || f == sql_sel) {
(gdb) p rs1
$3 = (stmt *) 0x27707d8
(gdb) p rs2
$4 = (stmt *) 0x0
(gdb) up
1 0x00002aaabe744e97 in sql_logical_exp (sql=0x24ff678, scp=0x2766cb8,
sc=0x2502008, grp=0x0, subset=0x0, f=1, ek=
{type = 0 '\0', card = 4 '\004', reduce = 1 '\001'})
at /ufs/goncalve/MonetDB/current/sql/src/server/sql_select.mx:3595
3595 stmt *s = sql_logical_exp_(sql, scp, sc, grp, subset, f, ek);
(gdb) up
2 0x00002aaabe745ba3 in sql_select (sql=0x24ff678, scp=0x2766cb8,
sn=0x2502108, ek={type = 0 '\0', card = 4 '\004', reduce = 1 '\001'})
at /ufs/goncalve/MonetDB/current/sql/src/server/sql_select.mx:3848
3848 s = sql_logical_exp(sql, scp, sn->where, NULL, NULL, sql_where, iek);
(gdb)
Romulo
## Comment 9388
Date: 2008-05-08 10:43:00 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
test added at:
sql/src/test/BugTracker/between_with_column.SF-1959410.sql
## Comment 9389
Date: 2008-05-09 11:30:52 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
Fixed on the check in:
[Monetdb-sql-checkins] sql/src/server sql_select.mx,,1.229,1.230
Modified Files:
sql_select.mx
Log Message:
Check if the check types worked fine (be defensive).
This was the problem for bug [ monetdb-Bugs-1959410 ] between with column
When we combine order by with limit within return statement, the ordered statement is
inside the limit statement.
This was the reason for bug [ monetdb-Bugs-1959410 ] between with column
## Comment 9390
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1959410 at http://sourceforge.net/support/tracker.php?aid=1959410
| between with column | https://api.github.com/repos/MonetDB/MonetDB/issues/1661/comments | 0 | 2020-11-30T09:51:20Z | 2024-06-27T11:29:52Z | https://github.com/MonetDB/MonetDB/issues/1661 | 753,326,719 | 1,661 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-07 12:03:54 +0200
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-06-02 10:19:32 +0200
## Comment 9382
Date: 2008-05-07 12:03:54 +0200
From: @romulogoncalves
The following sql code crash Mserver5:
create table t3 (id float);
select id from t3 where (id between 0 and 62) having (id = id+.1 or id = id - .1);
drop table t3;
Some debug information to see where is the problem:
Program received signal SIGABRT, Aborted.
[Switching to Thread 1107310928 (LWP 6471)]
0x0000003c6d030ec5 in raise () from /lib64/libc.so.6
(gdb) up
1 0x0000003c6d032970 in abort () from /lib64/libc.so.6
(gdb) up
2 0x0000003c6d02a11f in __assert_fail () from /lib64/libc.so.6
(gdb) up
3 0x00002aaabe7ae64d in sql_ref_inc (r=0x26abf18)
at /ufs/goncalve/MonetDB/current/sql/src/common/sql_mem.mx:43
43 assert(r->refcnt > 0);
Romulo
## Comment 9383
Date: 2008-05-08 10:41:46 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
Test added at:
sql/src/test/BugTracker/between_having_problem.SF-1959391.sql
## Comment 9384
Date: 2008-06-01 21:56:23 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Update:
The problem seems to persist with the default SQL compiler on both M4 & M5:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests4103/GNU.64.64.d-Fedora8/src_test_BugTracker/between_having_problem.SF-1959391.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests5103/GNU.64.64.d-Fedora8/src_test_BugTracker/between_having_problem.SF-1959391.err.00.html
However, it seems to be solved with the new (not yet default) algebra-based SQL compiler --- on all platfroms except Solaris 10/x86:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTestsG103/GNU.64.64.d-Fedora8/src_test_BugTracker/between_having_problem.SF-1959391.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTestsG103/GNU.32.32.d-SunOS5.10/src_test_BugTracker/between_having_problem.SF-1959391.err.00.html
## Comment 9385
Date: 2008-06-02 10:19:32 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
having without group by defaults to a single aggregated result. The having is a filter on this result, ie it cannot use full columns but should use aggregated columns. This is now fixed.
## Comment 9386
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1959391 at http://sourceforge.net/support/tracker.php?aid=1959391
| between_having_problem | https://api.github.com/repos/MonetDB/MonetDB/issues/1660/comments | 0 | 2020-11-30T09:51:18Z | 2024-06-27T11:29:51Z | https://github.com/MonetDB/MonetDB/issues/1660 | 753,326,678 | 1,660 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-07 11:23:12 +0200
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-06-02 10:17:57 +0200
## Comment 9377
Date: 2008-05-07 11:23:12 +0200
From: @romulogoncalves
The following sql statements crash the mserver5:
sql>create table t1 (id int);
sql>create table t2 (age int);
sql>select age from t1, t2 where (age-id)/id<0.01;
Some debig information to see from where comes the crash:
Program received signal SIGABRT, Aborted.
[Switching to Thread 1107310928 (LWP 5293)]
0x0000003c6d030ec5 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install bzip2.x86_64 e2fsprogs.x86_64 glibc.x86_64 keyutils.x86_64 krb5.x86_64 libselinux.x86_64 ncurses.x86_64 openssl.x86_64 pcre.x86_64 readline.x86_64 zlib.x86_64
(gdb) up
1 0x0000003c6d032970 in abort () from /lib64/libc.so.6
(gdb) up
2 0x0000003c6d02a11f in __assert_fail () from /lib64/libc.so.6
(gdb) up
3 0x00002aaabe72364b in find_pivot (scp=0x4fe7308, t=0x50279e8)
at /ufs/goncalve/MonetDB/current/sql/src/server/sql_scope.mx:229
229 assert(0);
(gdb) up
4 0x00002aaabe72366e in scope_find_pivot (scp=0x4fe7308, t=0x50279e8)
at /ufs/goncalve/MonetDB/current/sql/src/server/sql_scope.mx:237
237 return find_pivot(scp, t);
(gdb) up
5 0x00002aaabe73b773 in sql_binop_ (sql=0x246d0d8, scp=0x4fe7308,
s=0xc1a808, fname=0x5029f58 "sql_div", ls=0x50ea698, rs=0x50dac18)
at /ufs/goncalve/MonetDB/current/sql/src/server/sql_select.mx:879
879 ls = stmt_join(scope_find_pivot(scp, ls->h), ls, cmp_equal);
(gdb) up
6 0x00002aaabe73c27f in sql_binop (sql=0x246d0d8, scp=0x4fe7308,
se=0x502a048, grp=0x0, subset=0x0, f=1)
at /ufs/goncalve/MonetDB/current/sql/src/server/sql_select.mx:1069
1069 return sql_binop_(sql, scp, s, fname, ls, rs);
(gdb) p fname
$1 = 0x5029f58 "sql_div"
Romulo
## Comment 9378
Date: 2008-05-08 11:24:39 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
test added at:
sql/src/test/BugTracker/Tests/sql_div.SF-1959357.sql
## Comment 9379
Date: 2008-06-01 22:01:57 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Update:
The problem seems to persist with the default SQL compiler on both M4 &
M5:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests4103/GNU.64.64.d-Fedora8/src_test_BugTracker/sql_div.SF-1959357.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests5103/GNU.64.64.d-Fedora8/src_test_BugTracker/sql_div.SF-1959357.err.00.html
However, it seems to be solved with the new (not yet default)
algebra-based SQL compiler:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTestsG103/GNU.64.64.d-Fedora8/src_test_BugTracker/sql_div.SF-1959357.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTestsG103/GNU.64.64.d-Fedora8/src_test_BugTracker/sql_div.SF-1959357.err.00.html
## Comment 9380
Date: 2008-06-02 10:17:57 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
now fixed even for the old sql compiler
## Comment 9381
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1959357 at http://sourceforge.net/support/tracker.php?aid=1959357
| sql_div | https://api.github.com/repos/MonetDB/MonetDB/issues/1659/comments | 0 | 2020-11-30T09:51:14Z | 2024-06-27T11:29:50Z | https://github.com/MonetDB/MonetDB/issues/1659 | 753,326,641 | 1,659 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-07 09:16:41 +0200
From: Wouter Alink <<alink>>
To: Wouter Alink <<alink>>
Version: -- development
Last updated: 2009-11-15 04:34:52 +0100
## Comment 9355
Date: 2008-05-07 09:16:41 +0200
From: Wouter Alink <<alink>>
The MonetDB/XQuery of yesterday seems indeed more stable than the last version. However, I have difficulty getting the java JDBC driver to work with MonetDB.
We use the JDBC connection extensively in the following way (which works perfectly with the old backend):
=====================
Connection xqConn = DriverManager.getConnection("jdbc:monetdb://localhost:50000/database?language=xquery", "monetdb","monetdb");
Statement st = xqConn.createStatement();
ResultSet rs = st.executeQuery("1+1,\"aap\",<noot/>");
try {
rs.next();
if (rs.getLong(1) != 2) fail("failed to receive expected integer");
rs.next();
if (!rs.getString(1).equals("aap")) fail("failed to receive expected string");
rs.next();
if (!rs.getString(1).equals("<noot/>")) fail("failed to receive expected element");
} finally {
rs.close();
}
=====================
However, it doesn't work with the new backend, each query gives a "protocol violated" SQLException.
## Comment 9356
Date: 2008-05-07 10:45:09 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
for the record:
it is a true violation, as the server returns:
2
which is clearly a violation, as it should have been
=2
or
[ 2 ]
or
[ "2" ]
NotMyBug.nl :)
## Comment 9357
Date: 2008-05-07 10:49:02 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
here is the communication log for above example:
RD 1210082838966: read final block: 20 bytes
RX 1210082838966: :mserver:8:plain:LIT
RD 1210082838966: inserting prompt
TD 1210082838966: write final block: 43 bytes
TX 1210082838966: BIG:monetdb:{plain}monetdb:xquery:database:
RD 1210082838968: read final block: 69 bytes
RX 1210082838968: MonetDB v4 doesn't have multiple database support, argument
ignored
RD 1210082838968: inserting prompt
TD 1210082838968: write final block: 11 bytes
TX 1210082838968: Xoutput seq
RD 1210082838968: read final block: 0 bytes
RX 1210082838968:
RD 1210082838968: inserting prompt
TD 1210082838996: write final block: 4 bytes
TX 1210082838996: s1+1
RD 1210082839002: read final block: 2 bytes
RX 1210082839002: 2
RD 1210082839002: inserting prompt
## Comment 9358
Date: 2008-05-07 10:57:38 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
Fabian is right. The problem arises in the server-side MIL code generation.
The dirty tricks Peter played with the variable of name genType (modifying the generated internal MIL tree) do not work for the algebra version (and I don't know why). Because the strange side-effects to the genType MIL variable do not affect the value of the variable the serialization always uses the serialization mode 'xml' instead of the JDBC or MAPI mode. (If I think some more I don't even know why client side querying works as the special '=' characters at the beginning of the line are not generated.)
## Comment 9359
Date: 2008-05-07 11:02:34 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
mapilib (mapiclient) is extremely lax towards the protocol. It can do that as it usually just dumps exactly what it received on the stream, not caring about the contents at all. JDBC on the other hand relies on the correctness of the protocol, as it needs to determine correct actions for each and every response it receives. Chances are big you just didn't notice the protocol is violated, because mclient didn't warn you something is wrong, but just dumped the output.
## Comment 9360
Date: 2008-05-07 14:27:11 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
Changed the priority to highest because this is an important bug.
## Comment 9361
Date: 2008-05-07 21:35:48 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
lefteris, i'm glad that you give this bug attention, but perhaps priority 9 is a little overdone.
some background information: fabian and i added the feature of communicating with MonetDB/XQuery through JDBC about three years ago. back then it looked to us as if XMLDB (the API proposed by others) wouldn't survive, and it seems that we were right. therefore we added the special serialization mode which would return a xquery sequence as a one-column sql resultset. difference with sql was the fact that different types could occur in a single column, but this didn't hurt mapi (as fabian already mentioned, it doesn't really care what it transmits either way). It is simple, it is simple, and it makes life easier. i don't know if there are any other MonetDB/XQuery-users who abuse JDBC the same way.
The algebra backend from the beginning only supported the 'xml' serialization (and this has been communicated). This serialization mode implies that a result always is a constructed element, and never a sequence. The reason for this bugreport is that I would like to see two features being implemented in the algebra version in the same way they are implemented in the mps version: 1) the 'dm' serialization mode, which allows xquery sequences to be returned, and 2) the ability to do xquery through JDBC.
I already tackled the first problem by compiling pathfinder after replacing xquery(...,"xml",....) by xquery(..., "dm",...) in (i believe it was) serialize_dflt.mx. I hope this can be made a (runtime?) configuration option. The second problem is a little bit more tricky and would require more knowledge about the current mapi-protocol (which i do not have anymore). I assume that Fabian is the one to ask here, but as he should stay focused on his thesis. I guess with some documentation on (or examples of) the current mapi protocol and by reading serialize*.mx you or i could do it in little time.
## Comment 9362
Date: 2008-05-07 21:53:51 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
Hi,
the reason I did this one priority 9 is because I understand that this is a show-stopper bug and because I understood from our initial e-mails that this problem emerged the last days, from some recent check-in. Unfortunately my knowledge is limited on how to fix this bug.
## Comment 9363
Date: 2008-05-07 22:24:12 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
Thanks Wouter.
quote:
>>>
The second problem is a little bit more tricky and would require
more knowledge about the current mapi-protocol (which i do not have
anymore). I assume that Fabian is the one to ask here, but as he should
stay focused on his thesis. I guess with some documentation on (or examples
of) the current mapi protocol and by reading serialize*.mx you or i could
do it in little time.
<<<
What needs to be done is trivial considering the protocol. Not much has changed since we (Wouter and I) made that JDBC support in pathfinder. Though, one needs to understand that what is emitted right now, IMHO does not conform to anything. It may work, and may be fast, but it has no way of reliably finding bounds (or doing sequences).
Therefore, regardless of JDBC, that situation needs to be fixed, unless there is no interest in any API accessibility for XQuery of course (apart from piping output of mclient).
That said, it's up to you guys to figure out your spaghetti ;) If you need help to construct a valid "ResultSet" for JDBC, drop me an email. The hard part of finding the sequence boundaries and serialising them in the right form is up to you.
## Comment 9364
Date: 2008-05-07 22:33:03 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
alternatively one could say that the BugTracker/JDBC* tests fail for pathfinder/G and should be fixed one way or another ;)
## Comment 9365
Date: 2008-05-08 09:33:35 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
Guys,
I think I did not make myself clear enough. There is no problem in the serialization. In the algebra we can still use all serialization modes may it be dm, mapi_dm, text, mapi_text, xml, mapi_xml, typed_xml, mapi_typed_xml, xrpc_xml, mapi_xrpc_xml, or seq. The only problem is that the MIL command print_result() decides which mode to use based on the value of a parameter. The algebra code generation like mps always generates code that uses the "xml" mode.
As the compiler (and the code generation) is decoupled from the runtime part (client side querying) Peter introduced a quite ugly hack that takes the internal representation of the generated MIL code, looks for a special variable (genType), and replaces its content with the mode the client-side querying asks for. This 'hack' does not work for the algebra generated code---that's the problem here.
The cleanest solution would be to extend the compiler (PFcompile*()) with an additional argument (client side options like the serialization mode) that are then used to directly generate the correct code. As this might break the mps code generation and is very low on 'my' priority list it is not implemented so far.
## Comment 9366
Date: 2008-05-08 10:19:21 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Jan,
while I agree that the genType (and alike!) HACK(s) should ("eventually") be raplaced by proper runtime parameters,
I'm wondering, whether there is any reason that the genType HACK does not work with the Algebra back-end other than that the algebra back-end does not introduce and use a "genType" variable in the generated MIL code.
I.e., would/could simply adding a 'var genType := "xml";' and using variable 'genType' instead of hard-wired "xml" in the generated 'print_result(...);' statement (and alike for 'genType = "...-timing-..."'; analogous to what MPS does) (at least temporarily) (and "quickly") "solve" the problem?
Stefan
## Comment 9367
Date: 2008-05-08 11:37:28 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
Stefan,
that's exactly what I already did some time ago :)
After some time I reached the core of the problem: In mps a single query consists of a prologue, a query, and an epilogue. Trying to understand how everything fits together definitely takes more time than I'm willing to invest. (Somehow there is a static prologue whose pointer to variable genType is looked up and later modified. In every query however there is also a new prologue, that gets magically modified by Peters MIL optimization. @Fabian: it's not Spaghetti but Maze code :))
...
The only feasible solution would be to build on the already active hacks, take the value from the genType variable of the unused static prologue, and use it as parameter for an explicit compiler argument. That's exactly what I just checked in.
@Wouter: could you please check if your problem is now fixed.
@Peter: Is this complexity really necessary or isn't there a much simpler solution?
## Comment 9368
Date: 2008-05-08 12:03:29 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
i found a solution to the problem after reading all the helpful messages: (thanks Fabian, Jan, Stefan)
it wasn't the 'dm' mode i was looking for, but the 'seq' mode. If i compile MonetDB so that it generates genType="seq", then XQuery through JDBC works fine with the algebra-backend.
this works for me at the moment, but i guess a permanent solution should be found eventually. (lowered priority to 3)
## Comment 9369
Date: 2008-05-08 12:26:06 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
cross-posted with Jan.
(@Jan: I can try to check the nightly build tomorrow to see whether your fix works)
As fabian already pointed out (and Stefan likes to hear): the testweb should tell us whether the JDBC tests succeed :)
## Comment 9370
Date: 2008-05-08 15:39:32 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Running Mtest by hand (yes, that is still possible! ;-)), seems to show that some (all?) Pathfinder-JDBC tests as well as some (all) of the non-"xml" (i.e., "dm", "seq", etc.) serialization test now also seem to work fine with the Algebra back-end.
More details will indeed we revealed by tomorrows TestWeb after tonight test run.
Thanks to Jan (and all others involved) for yet another step forward towards the upcoming "Algebra release".
## Comment 9371
Date: 2008-05-14 13:06:07 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Wouter,
did you check, whether Jan's fixes work for you?
If so, do you think, we can close this one?
The XQuery-JDBC tests seem to work fine with the ALG back-end, now:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTestsG103/GNU.32.32.d-Fedora8/tests_BugTracker/JDBC_250_results.SF-1730556.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTestsG103/GNU.32.32.d-Fedora8/tests_BugTracker/JDBC_250_results.SF-1730556.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTestsG103/GNU.32.32.d-Fedora8/tests_BugTracker/JDBC_0_results.SF-1886326.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTestsG103/GNU.32.32.d-Fedora8/tests_BugTracker/JDBC_0_results.SF-1886326.err.00.html
.
## Comment 9372
Date: 2008-05-14 14:37:51 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
sorry, yes i did check, and it now seems to work without problems. thanks jan.
i guess no new tests need to be added. i'm closing this bug.
## Comment 9373
Date: 2008-05-14 14:43:42 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
I think it makes sense to add your specific code sample as test. There are not so many JDBC tests in XQuery, and if you are heavily relying upon that, it may be wise to test some more on what you're doing.
## Comment 9374
Date: 2008-05-28 16:09:48 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
As Fabian suggested, if this is a feature that you (Wouter) rely on, then we should consider adding a respective test...
## Comment 9375
Date: 2009-11-15 16:34:52 +0100
From: Wouter Alink <<alink>>
added test (JDBC_5_results.SF-1959269). closing bug.
## Comment 9376
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1959269 at http://sourceforge.net/support/tracker.php?aid=1959269
| XQ+JDBC: protocol violation | https://api.github.com/repos/MonetDB/MonetDB/issues/1658/comments | 0 | 2020-11-30T09:51:11Z | 2024-06-27T11:29:49Z | https://github.com/MonetDB/MonetDB/issues/1658 | 753,326,607 | 1,658 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-06 11:18:26 +0200
From: Nick <<niftikhar>>
To: @njnes
Version: -- development
Last updated: 2008-06-04 10:36:57 +0200
## Comment 9352
Date: 2008-05-06 11:18:26 +0200
From: Nick <<niftikhar>>
I need to insert some null values into a table via a procedure.
I created the table and did insert two rows. One with (insert into) command and second with (insert into ..select) command. Both commands work well and
I could see two rows added in result.
When I used the same (insert into.. select) command in a procedure. It behaves in a strange fashion. It shows that a row has been affected, but does not show the newly added row. If the rows are counted, it gives the correct count which is (3) in this case but still I could not see the last row which is added via a procedure.
''''''''''''''''''''''''''''''''''''''''''''''''''''''
create sequence "ff" as integer start with 1;
CREATE TABLE t1(timeid INT DEFAULT NEXT VALUE FOR "ff" PRIMARY KEY,
a INT,
b INT,
c INT,
d INT,
e INT,
f VARCHAR(20),
g VARCHAR(20),
h INT,
i VARCHAR(10),
j VARCHAR(10),
k VARCHAR(10),
l INT,
m INT,
n VARCHAR(10),
o VARCHAR(10),
p VARCHAR(10),
q VARCHAR(15),
r INT
);
'''''''''''''''''''''''''''''''''''''''''''''''''''''
And then insert a row
'''''''''''''''''''''''''''''''''''''''''''''''''''''
insert into t1(a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p, q, r)
values(1, 1, 1, 1, 1, 'first row', 'first row',1, 'first row', 'first row',
'first row',1,1, 'first row', 'first row', 'first row', 'first row', 1);
select * from t1;
sql>Rows affected 1
sql>
+------+--+--+--+--+--+-----+-----+--+-----+------+------+--+--+------+------+------+------+--+
| time |a |b |c |d |e |f |g |h |i |j |k |l |m |n |o
|p |q |r |
: id | | | | | | | | | | | | | | |
| | | |
+======+==+==+==+==+==+=====+=====+==+=====+======+======+==+==+======+======+======+======+==+
| 1 |1 |1 |1 |1 |1 |firs |firs |1 |firs |first |first |1 |1 |first |first
|first |first |1 |
: | | | | | |t |t | |t |row |row | | |row |row
|row |row | |
: | | | | | |row |row | |row | | | | | |
| | | |
+------+--+--+--+--+--+-----+-----+--+-----+------+------+--+--+------+------+------+------+--+
'''''''''''''''''''''''''''''''''''''''''''''''''''''
Every thing is fine so far
'''''''''''''''''''''''''''''''''''''''''''''''''''''
sql>insert into t1(a, b, c, d, e, f, g, h) select a, b, c, d, e, f, g, h
from t1 where timeid = 1;
Rows affected 1
sql>select * from t1;
+------+--+--+--+--+--+-----+-----+--+-----+------+------+--+--+------+------+------+------+--+
| time |a |b |c |d |e |f |g |h |i |j |k |l |m |n |o
|p |q |r |
: id | | | | | | | | | | | | | | |
| | | |
+======+==+==+==+==+==+=====+=====+==+=====+======+======+==+==+======+======+======+======+==+
| 1 |1 |1 |1 |1 |1 |firs |firs |1 |firs |first |first |1 |1 |first |first
|first |first |1 |
: | | | | | |t |t | |t |row |row | | |row |row
|row |row | |
: | | | | | |row |row | |row | | | | | |
| | | |
| 2 |1 |1 |1 |1 |1 |firs |firs |1 |null |null |null |n |n |null |null
|null |null |n |
: | | | | | |t |t | | | | |u |u | |
| | |u |
: | | | | | |row |row | | | | |l |l | |
| | |l |
: | | | | | | | | | | | |l |l | |
| | |l |
+------+--+--+--+--+--+-----+-----+--+-----+------+------+--+--+------+------+------+------+--+
'''''''''''''''''''''''''''''''''''''''''''''''''''''
inserted another row and it works fine
'''''''''''''''''''''''''''''''''''''''''''''''''''''
sql>create procedure tt()
begin
insert into t1(a, b, c, d, e, f, g, h) select a, b, c, d, e, f, g, h from
t1 where timeid = 1;
end;
call tt();
select * from t1;
more>more>more>
sql>Rows affected 1
sql>+------+--+--+--+--+--+-----+-----+--+-----+------+------+--+--+------+------+------+------+--+
| time |a |b |c |d |e |f |g |h |i |j |k |l |m |n |o
|p |q |r |
: id | | | | | | | | | | | | | | |
| | | |
+======+==+==+==+==+==+=====+=====+==+=====+======+======+==+==+======+======+======+======+==+
| 1 |1 |1 |1 |1 |1 |firs |firs |1 |firs |first |first |1 |1 |first |first
|first |first |1 |
: | | | | | |t |t | |t |row |row | | |row |row
|row |row | |
: | | | | | |row |row | |row | | | | | |
| | | |
| 2 |1 |1 |1 |1 |1 |firs |firs |1 |null |null |null |n |n |null |null
|null |null |n |
: | | | | | |t |t | | | | |u |u | |
| | |u |
: | | | | | |row |row | | | | |l |l | |
| | |l |
: | | | | | | | | | | | |l |l | |
| | |l |
+------+--+--+--+--+--+-----+-----+--+-----+------+------+--+--+------+------+------+------+--+
''''''''''''''''''''''''''''''''''''''''''''''''''''''
The problem starts now: when I try to insert the
row via a procedure it shows that row effected
1 but does not show the row.
''''''''''''''''''''''''''''''''''''''''''''''''''''''
sql>select count(*) from t1;
+--------+
| count_ |
+========+
| 3 |
+--------+
sql>select timeid from t1;
+--------+
| timeid |
+========+
| 1 |
| 2 |
| 3 |
+--------+
sql>select * from t1;
+------+--+--+--+--+--+-----+-----+--+-----+------+------+--+--+------+------+------+------+--+
| time |a |b |c |d |e |f |g |h |i |j |k |l |m |n |o
|p |q |r |
: id | | | | | | | | | | | | | | |
| | | |
+======+==+==+==+==+==+=====+=====+==+=====+======+======+==+==+======+======+======+======+==+
| 1 |1 |1 |1 |1 |1 |firs |firs |1 |firs |first |first |1 |1 |first |first
|first |first |1 |
: | | | | | |t |t | |t |row |row | | |row |row
|row |row | |
: | | | | | |row |row | |row | | | | | |
| | | |
| 2 |1 |1 |1 |1 |1 |firs |firs |1 |null |null |null |n |n |null |null
|null |null |n |
: | | | | | |t |t | | | | |u |u | |
| | |u |
: | | | | | |row |row | | | | |l |l | |
| | |l |
: | | | | | | | | | | | |l |l | |
| | |l |
+------+--+--+--+--+--+-----+-----+--+-----+------+------+--+--+------+------+------+------+--+
sql>
''''''''''''''''''''''''''''''''''''''''''''''''''''''
I could not see the 3rd row
Regards,
## Comment 9353
Date: 2008-06-04 22:36:57 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
this bug is fixed. Also the test is added in src/test/BugTracker/Tests/proc_insert_into.SF-1958572.sql
## Comment 9354
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1958572 at http://sourceforge.net/support/tracker.php?aid=1958572
| (insert into ..select) statement Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/1657/comments | 0 | 2020-11-30T09:51:09Z | 2024-06-27T11:29:48Z | https://github.com/MonetDB/MonetDB/issues/1657 | 753,326,561 | 1,657 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-05 02:06:31 +0200
From: lxwandy <<lxwandy>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2008-05-06 11:09:31 +0200
## Comment 9350
Date: 2008-05-05 14:06:31 +0200
From: lxwandy <<lxwandy>>
Hi..
I want to know about the method of debugging MonetDB on Windows OS.
After compiering MonetDB use "namke" , how can I debug it. Is special debug tool needed?
## Comment 9351
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1957882 at http://sourceforge.net/support/tracker.php?aid=1957882
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.
| How to debug on Windows OS? | https://api.github.com/repos/MonetDB/MonetDB/issues/1656/comments | 0 | 2020-11-30T09:51:06Z | 2024-06-28T07:37:02Z | https://github.com/MonetDB/MonetDB/issues/1656 | 753,326,532 | 1,656 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-05-05 09:50:18 +0200
From: lxwandy <<lxwandy>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2008-05-05 10:30:31 +0200
## Comment 9347
Date: 2008-05-05 09:50:18 +0200
From: lxwandy <<lxwandy>>
Hi..
I want to know about the method of debugging MonetDB on Windows OS.
After compiering MonetDB use "namke" , how can I debug it. Is special debug tool needed?
## Comment 9348
Date: 2008-05-05 10:30:31 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
Hi,
this question will be answered if you post it to the monetdb-user mailing list. See http://monetdb.cwi.nl/projects/monetdb/Development/MailChannels/index.html about our mailing lists.
This is the bugtracker, a tool to submit bugs rather than questions.
## Comment 9349
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1957794 at http://sourceforge.net/support/tracker.php?aid=1957794
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.
| How to debug on Windows OS? | https://api.github.com/repos/MonetDB/MonetDB/issues/1655/comments | 0 | 2020-11-30T09:51:04Z | 2024-06-28T07:37:02Z | https://github.com/MonetDB/MonetDB/issues/1655 | 753,326,503 | 1,655 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-04-29 04:07:56 +0200
From: Wouter Alink <<alink>>
To: Lefteris Sidirourgos <<lsidir>>
Version: -- development
Last updated: 2008-04-29 04:31:44 +0200
## Comment 9344
Date: 2008-04-29 16:07:56 +0200
From: Wouter Alink <<alink>>
The current nightly build (2008-04-29, from SuperSourceTarBall with 64bit-oid) gives you roughly 7 tries before MonetDB with "--set xquery_backend=algebra" stops with a "Segmentation Fault"
It seems that this holds for any query, but some queries have more lives. A query '<aap/>' has about 7 lives. A 'concat("duck","cow","horse")' together have about a hundred lives. A query 'doc("rabbit")' can be executed about 5 times before the database crashes. It also seems to depend on the rate of executing queries. The system will crash quicker, if queries are fired at the database at a high rate.
## Comment 9345
Date: 2008-04-29 16:31:44 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
Hi Wouter,
Thank you for the bug report. There was a similar bug report yesterday [ monetdb-Bugs-1953446 ] Segmentation fault on pathfinder/algebra -- mclient/G and was fixed today. I don't know if it is the same problem, but since you used a yesterday's build, probably it was. I repeated the queries on todays cvs head, multiple times and I did not get any segmentation fault so it seems that it was the same bug. I will close this bug with a resolution duplicate.
lefteris
## Comment 9346
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1954210 at http://sourceforge.net/support/tracker.php?aid=1954210
This bug was marked DUPLICATE in the database it was moved from.
Changing resolution to "MOVED"
| XQ: algebra queries have 7 lives | https://api.github.com/repos/MonetDB/MonetDB/issues/1654/comments | 0 | 2020-11-30T09:51:01Z | 2024-06-28T07:37:01Z | https://github.com/MonetDB/MonetDB/issues/1654 | 753,326,483 | 1,654 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-04-28 04:22:15 +0200
From: @lsidir
To: Lefteris Sidirourgos <<lsidir>>
Version: -- development
Last updated: 2008-04-29 09:42:17 +0200
## Comment 9340
Date: 2008-04-28 16:22:15 +0200
From: @lsidir
Hi,
when run a couple of queries through mclient -lxq -G a segmentation fault is thrown. There is no specific scenario for this, the first time happened by doing pf:documents() and pf:collections() a couple times and the second time by calling string-length("lala") a couple of times. Attached is the file containing the gdb info for both cases, the problem appears to the same point (prop/prop_req_node.c:1027).
lefteris
## Comment 9341
Date: 2008-04-29 09:09:09 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
Hi Lefteris,
the problem should be fixed now in the CVS head. Could you please check.
## Comment 9342
Date: 2008-04-29 09:42:17 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: YES
Thank you Jan,
it works just fine. I wont submit any test because there was no specific scenario for that, it just happened randomly. Closing the bug.
## Comment 9343
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1953446 at http://sourceforge.net/support/tracker.php?aid=1953446
| Segmentation fault on pathfinder/algebra -- mclient/G | https://api.github.com/repos/MonetDB/MonetDB/issues/1653/comments | 0 | 2020-11-30T09:50:59Z | 2024-06-27T11:29:44Z | https://github.com/MonetDB/MonetDB/issues/1653 | 753,326,457 | 1,653 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-04-17 06:05:59 +0200
From: Brad Denney <<bdoglo>>
To: @sjoerdmullender
Version: -- development
Last updated: 2008-04-17 07:10:06 +0200
## Comment 9337
Date: 2008-04-17 18:05:59 +0200
From: Brad Denney <<bdoglo>>
I am running MS Win XP x64 SP2 with Intel Xeon CPU's. The ODBC driver appears to install but whenever I try to connect to a ODBC datasource I create, I get system error 193. This happens with the install from:
MonetDB5-SQL-Installer-x86_64-20080214.msi
I also tried not installing the ODBC driver in the installation and installing it seperately, but the same error occurs.
## Comment 9338
Date: 2008-04-17 19:10:05 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Duplicate of http://sourceforge.net/support/tracker.php?aid=1944336.
## Comment 9339
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1945070 at http://sourceforge.net/support/tracker.php?aid=1945070
This bug was marked DUPLICATE in the database it was moved from.
Changing resolution to "MOVED"
| x64 ODBC system error 193 | https://api.github.com/repos/MonetDB/MonetDB/issues/1652/comments | 0 | 2020-11-30T09:50:56Z | 2024-06-28T07:37:01Z | https://github.com/MonetDB/MonetDB/issues/1652 | 753,326,418 | 1,652 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-04-17 10:13:43 +0200
From: @grobian
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2008-04-17 10:22:46 +0200
## Comment 9333
Date: 2008-04-17 10:13:43 +0200
From: @grobian
MSG merovingian[15709]: starting database foo due to control signal
MSG foo[15715]: executing '/ufs/fabian/scratch/monetdb/stable/program-x86_64/bin/mserver5' for database 'foo'
MSG merovingian[15709]: starting database 'foo', up min/avg/max: 0/0/0, crash average: 0.00 0.00 0.00 (3-3=0)
MSG foo[15715]: MonetDB server v5.4.1, based on kernel v1.22.1
MSG foo[15715]: Serving database 'foo'
MSG foo[15715]: Compiled for x86_64-pc-linux-gnu/64bit with 64bit OIDs dynamically linked
MSG foo[15715]: Copyright (c) 1993-2008 CWI, all rights reserved
MSG foo[15715]: Visit http://monetdb.cwi.nl/ for further information
MSG foo[15715]: Listening for connection requests on mapi:monetdb://pegasus.ins.cwi.nl:50001/
MSG foo[15715]: MonetDB/SQL module v2.22.1 loaded
MSG foo[15715]: >!SyntaxException:parseError:10222 PID=15715 TIME=Wed Apr 16 21:21:15 2008
MSG foo[15715]: !SyntaxException:parseError:^<identifier> expected
MSG foo[15715]: >!SyntaxException:parseError: @ LOGON
MSG foo[15715]: !SyntaxException:parseError:^<identifier> expected
MSG merovingian[15709]: database 'foo' (15715) has exited with exit status 0
MSG merovingian[15709]: database 'foo' appears to have shut down already
ERR merovingian[15709]: failed to fork mserver: database 'foo' either needs a longer timeout to start up, or appears to cleanly shut itself down after starting
Black voodoo still as to why and how mserver5 reads the contents of .gdk_lock via filedescriptor 0.
## Comment 9334
Date: 2008-04-17 10:22:45 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
A fresh look just made me realise that merovingian didn't start the server in daemon mode any more. This is fixed now. It remains a question whether mserver should be able to cope with a closed stdin, or not (like it does now, and just reads whatever currently is opened on filedescriptor 0).
## Comment 9335
Date: 2008-05-08 16:12:05 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
I guess, automatic merovingian tests are still out of reach (for now?), right?
## Comment 9336
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1944717 at http://sourceforge.net/support/tracker.php?aid=1944717
| Merovingian: fail to start mservers | https://api.github.com/repos/MonetDB/MonetDB/issues/1651/comments | 0 | 2020-11-30T09:50:54Z | 2024-06-27T11:29:42Z | https://github.com/MonetDB/MonetDB/issues/1651 | 753,326,388 | 1,651 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-04-16 10:06:21 +0200
From: Brad Denney <<bdoglo>>
To: @sjoerdmullender
Version: -- development
Last updated: 2008-08-01 01:45:30 +0200
## Comment 9323
Date: 2008-04-16 22:06:21 +0200
From: Brad Denney <<bdoglo>>
I am running MS Win XP x64 SP2 with Intel Xeon CPU's. The ODBC driver appears to install but whenever I try to connect to a ODBC datasource I create, I get system error 193. This happens with the install from:
MonetDB5-SQL-Installer-x86_64-20080214.msi
I also tried not installing the ODBC driver in the installation and installing it seperately, but the same error occurs.
## Comment 9324
Date: 2008-04-18 16:57:43 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
I can't reproduce the error message. Can you produce details on what exactly you did to get this error message?
One of the things to keep in mind here is that if your ODBC using application is 32 bits, it needs the 32 bit ODBC driver. The driver that is part of the 64 bit SQL installer is a 64 bit driver, so can't be used with 32 bit applications.
However, I have found that there are some problems with the separate ODBC installers (both 32 and 64 bit). These installers are missing two DLLs that are essential for operation. Loading the driver by the ODBC driver manager will fail due to the fact that these DLLs are missing.
After I fixed the bug with the installer I was able to use both the 32 bit and 64 bit ODBC driver on a 64 bit system (Windows XP Professional x64 Edition). I have tried this with a small test program that is part of our sources (both compiled for 32 and 64 bits) and with Excel importing data from a database query. Excel with the 64 bit driver does not work since it is a 32 bit application (is there a 64 bit version of Microsoft Office?).
## Comment 9325
Date: 2008-04-18 18:28:15 +0200
From: Brad Denney <<bdoglo>>
Logged In: YES
user_id=1211469
Originator: YES
Thanks for the comment. Okay, so I need the 32 bit driver for my 32 bit apps. That makes sense. What are the missing files I need for the ODBC-32 driver working (when using the 64-bit server) and where do I find them? Or are the ODBC installers going to be updated?
## Comment 9326
Date: 2008-04-18 20:15:30 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
The missing DLLs are zlib1.dll and iconv.dll. You can get them from a 32 bit install of MonetDB5-SQL or MonetDB4-XQuery. They are in the lib subdirectory of the installation, and they should be placed in the lib subdirectory of the ODBC installation.
Do make sure you get the bit widths right!
You should probably also not have a 64 bit version of the ODBC driver installed next to the 32 bit version. In other words, when you install the 64 bit server, say No to the question whether you want to install the ODBC driver.
I hope this works. I haven't tested the official distributed versions. I compiled new ones and tested with those.
## Comment 9327
Date: 2008-04-18 22:08:01 +0200
From: Brad Denney <<bdoglo>>
Logged In: YES
user_id=1211469
Originator: YES
Okay, I installed MonetDB-SQL-64 without the ODBC drivers. I then ran the ODBC-32 installation. The lib folders of the ODBC files had the files you mentioned that were missing and the size and dates were identical. But just in case I copied over the two DLL's from a copy of them from a prior MonetDB-SQL-32 install. The problem I have is the 32-bit drivers never show up in the MS/ODBC Data Sources tool.
I would be happy using the 32 bit version of MonetDB-SQL if I could get the ODBC drivers working. When the 64-bit drivers were installed they showed up in the drivers list of the "Data Sources" tool even though I couldn't use them with my 32-bit apps.
Any ideas of how I can get this working?
## Comment 9328
Date: 2008-04-22 14:16:54 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
On Windowx XP x64 there are two versions of the ODBC Data Source Administrator program, a 32 bit version and a 64 bit version. Search for the file odbcad32.exe on your system. I found one in C:\WINDOWS\System32 and one in C:\WINDOWS\SysWOW64. The two give different lists of available ODBC drivers, so in only one of them you will find the MonetDB ODBC driver.
Of course, the program you get by default is the 64 bit one, so you won't see the 32 bit driver.
I hope this helps.
## Comment 9329
Date: 2008-04-22 22:29:38 +0200
From: Brad Denney <<bdoglo>>
Logged In: YES
user_id=1211469
Originator: YES
I still was having problems with this, but I seem to have a work-around solution which you could use as a guideline for future versions of the installer (if you think it is appropriate).
In order for everything to work properly, the 32-bit and 64-bit ODBC drivers should both be installed. To do this I first installed the SQL-64 version with the ODBC driver option checked. I then installed the 32-bit ODBC driver. The problem this creates is the installation causes ODBC to look for both drivers in the same place (and with the same name).
You need to fix where ODBC is looking by going into the registry and editing the following entries:
With regedit go to the registry heading:
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\MonetDB ODBC Driver
+ Change the "Driver" entry to the 32-bit installation path. In my installation this was:
"C:\Program Files (x86)\CWI\MonetDB ODBC Driver\lib\libMonetODBC.dll"
+ Change the "Setup" entry to the 32-bit setup dll path. For me this was:
"C:\Program Files (x86)\CWI\MonetDB ODBC Driver\lib\libMonetODBCs.dll"
+Also change
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\MonetDB\Driver
to the 32-bit driver installation path, which for me was:
"C:\Program Files (x86)\CWI\MonetDB ODBC Driver\lib\libMonetODBC.dll"
Next I changed the 64-bit driver and setup paths under the registry heading:
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\MonetDB ODBC Driver
+ Change the Driver entry to the 64-bit installation driver dll path. For me this was:
"C:\Program Files\CWI\MonetDB5\lib\libMonetODBC.dll"
+ Change the Setup entry to the 64-bit installation setup dll path. For me this was:
"C:\Program Files\CWI\MonetDB5\lib\libMonetODBCs.dll"
After all that you should be able to add working data sources from the ODBC administrator found in Control Panel/administrative Tools. I tested it in Excel with the example given in the documentation and it connected just fine.
## Comment 9330
Date: 2008-06-03 10:43:44 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
For the upcoming release (target: this month) I have removed the ODBC driver from the MonetDB5-SQL installer. Now you need to install the ODBC driver separately. I have also made the 32-bit and 64-bit versions into independent packages (so that installing the second doesn't remove the first).
I installed first the 64-bit version and then the 32-bit version, and I was able to use both the 32-bit and 64-bit versions of the test program I have without having to change any registry entries.
When I look with the registry editor, I see the entries you mention already contain the correct paths.
Brad, if I give you the two driver installers, can you test whether you still have problems?
## Comment 9331
Date: 2008-08-01 13:45:30 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Closing since it seems to work, for me at least, in the latest stable release.
## Comment 9332
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1944336 at http://sourceforge.net/support/tracker.php?aid=1944336
| x64 ODBC system error 193 | https://api.github.com/repos/MonetDB/MonetDB/issues/1650/comments | 0 | 2020-11-30T09:50:51Z | 2024-06-27T11:29:41Z | https://github.com/MonetDB/MonetDB/issues/1650 | 753,326,355 | 1,650 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-04-16 03:58:21 +0200
From: Kevin Y. Kim <<kykim>>
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2008-04-16 08:07:31 +0200
## Comment 9319
Date: 2008-04-16 15:58:21 +0200
From: Kevin Y. Kim <<kykim>>
OS: Mac OS X 10.4.11
Compiler: i686-apple-darwin8-gcc-4.0.1
bison: 2.3
autoconf: 2.61
automake: 1.10
libtool: 1.5.26
after creating a new database, user and schema
i am only able to login once.
after restarting mserver5, i am able to login in again.
also, password is send in the clear
> monetdb create foo create the db
> mserver5 --dbname=foo --dbinit="include sql;" start the db
> ./mclient -lsql
sql>CREATE USER "bar" WITH PASSWORD 'password' NAME 'Foobar User' SCHEMA "sys";
sql>CREATE SCHEMA "bar" AUTHORIZATION "bar";
sql>ALTER USER "bar" SET SCHEMA "bar";
> ./mclient -lsql -ubar
Password:password
sql>\q
> ./mclient -lsql -ubar
Password:password
!InvalidCredentialsException:checkCredentials:Invalid credentials for user 'bar'
## Comment 9320
Date: 2008-04-16 20:07:30 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
Fixed in stable CVS, thanks for the report!
Due to some braindamage, the actual password value in the underlying BAT was changed (non-persistent), resulting in the next login to fail. A restart would start fresh again, and hence succeed.
## Comment 9321
Date: 2008-05-08 16:12:35 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Would there (have) be(en) a simple test to monitor also this bug fix?
## Comment 9322
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1943995 at http://sourceforge.net/support/tracker.php?aid=1943995
| M5: only able to login once | https://api.github.com/repos/MonetDB/MonetDB/issues/1649/comments | 0 | 2020-11-30T09:50:49Z | 2024-06-27T11:29:39Z | https://github.com/MonetDB/MonetDB/issues/1649 | 753,326,321 | 1,649 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-04-15 02:42:23 +0200
From: marspluto
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2008-04-16 10:30:08 +0200
## Comment 9312
Date: 2008-04-15 14:42:23 +0200
From: marspluto
Hi all,
I am using MonetDB4 with XQuery. I use the function fn:matches. When I use it, I am getting this error now:
Error: !ERROR: Should not happen: error occurred while checking flags: !ERROR: pcre_match() not available as required version of libpcre was not found by configure. !ERROR: pcre_match: operation failed.
Strange, but it was working properly before. What is the required version for libpcre?
junte
## Comment 9313
Date: 2008-04-15 14:50:55 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Which operating system?
How was MonetDB created? Did you build it yourself or did you use a precompiled binary?
## Comment 9314
Date: 2008-04-15 15:14:00 +0200
From: marspluto
Logged In: YES
user_id=2016221
Originator: YES
I installed the latest stable 'February' version via CVS, so I compiled it from scratch. I am using Fedora Core 8. The problem is not PCRE I think. I have downgraded it from 7.3 tot 7.1 and I am still getting this problem. I have a machine that has Fedora 6, and I am not getting the bug there...
## Comment 9315
Date: 2008-04-15 16:02:15 +0200
From: marspluto
Logged In: YES
user_id=2016221
Originator: YES
If you want some extra information, please let me know. For now, I am using fn:contains to do the trick, which is working fine. However, with fn:contains it does not look as elegant as fn:matches, so I hope the bug can be fixed or a work-around for it can be created.
## Comment 9316
Date: 2008-04-15 17:14:30 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
If you have compiled it yourself, you should check the output of the configure step. It should say whether or not it found PCRE. We need version 4.5 or better.
## Comment 9317
Date: 2008-04-16 10:00:19 +0200
From: marspluto
Logged In: YES
user_id=2016221
Originator: YES
This bug report can be closed. I have fixed this by installing the PCRE library version 7.6 with UTF8 support. Then I reinstalled the February release from scratch. My libraries did not support UTF8, which was causing the error. fn:matches is much faster than fn:contains, so I am glad that that function is working again.
## Comment 9318
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1942938 at http://sourceforge.net/support/tracker.php?aid=1942938
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.
| libpcre error when using function fn:matches | https://api.github.com/repos/MonetDB/MonetDB/issues/1648/comments | 0 | 2020-11-30T09:50:46Z | 2024-06-28T07:37:01Z | https://github.com/MonetDB/MonetDB/issues/1648 | 753,326,283 | 1,648 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-28 05:11:07 +0100
From: Jan Rittinger <<jan.rittinger>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2008-06-03 01:52:42 +0200
## Comment 9303
Date: 2008-03-28 17:11:07 +0100
From: Jan Rittinger <<jan.rittinger>>
The following query:
doc("foo.xml")//text()/ancestor::b
does return the correct result (<b>textnode</b>) if run with --debug=0. With --debug=10 as during testing no results are returned (-- see also tests/XQuery/step_attr_nametest).
The problem arises in loop_lifted_ancestor_step_with_nsloc_test().
$ cat foo.xml
<a foo="bar"><b>textnode</b><d><e/><f/></d><c foo2="bar"/></a>
## Comment 9304
Date: 2008-03-30 01:58:23 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
thanks for the bug. turned out to be a very deep MonetDB problem coming from oids being stored as either int/lng but being treated as unsigned. Especially nil may cause surprises, since as an oid it seems > 0, however as a signed integer it is < 0.
This particular code happened to produce a bat with an oid column starting with nil. With debug=10, the sorting order would be detected on this column, such that in the leftfetchjon code a wrong direct oid comparison on the values was done. One should use ATOMcmp(TYPE_oid,x,y) instead.
## Comment 9305
Date: 2008-05-08 16:14:50 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Is this problem covered by any existing test?
Otherwise, we should consider adding one to monitor the fix ...
## Comment 9306
Date: 2008-05-08 18:22:40 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
As Jan just enlightened me via pm:
The original bug report already said "see also tests/XQuery/step_attr_nametest" ...
However, the repective test still (again?) fails, both with the MPS and the ALG beack-end;
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_XQuery/step_attr_nametest.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora8/tests_XQuery/step_attr_nametest.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora8/tests_XQuery/step_attr_nametest.err.00.html
...
## Comment 9307
Date: 2008-05-08 23:07:33 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Re-opening, as the test apparently (according to nightly testing logs) never worked correctly (with the default GDKdebug=10) ...
## Comment 9308
Date: 2008-05-08 23:45:36 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
I guess, I found the bug:
The same ATOMcmp(TYPE_oid,x,y) fix that Peter applied for NIL-aware comparisons of OIDs in BATfetchjoin also needs to be applied a couple of lines further on the gdk_relop.mx .
If SF allows me to check my fix in before testing starts (and SF allows testings to checkout the latest version) the TestWeb will tell us more tomorrow morning ...
## Comment 9309
Date: 2008-05-09 11:52:08 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
According to the TestWeb, the test now works fine with the ALG back-end.
With the (soon to be) deprecated MPS back-end, it says:
"
ERROR = !ERROR: path steps are only supported starting from non-attribute nodes
"
which IMHO is correct, since MPS did, does and will not support path steps starting from attribute nodes, right?
If so, we should consider approving the correct/expected error message as MPS-specific output and close this bug report (again).
## Comment 9310
Date: 2008-06-03 13:52:42 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
MPS error message has been approved.
Closing.
## Comment 9311
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1928084 at http://sourceforge.net/support/tracker.php?aid=1928084
| XQ: Ancestor step with debug=10 broken | https://api.github.com/repos/MonetDB/MonetDB/issues/1647/comments | 0 | 2020-11-30T09:50:44Z | 2024-06-27T11:29:37Z | https://github.com/MonetDB/MonetDB/issues/1647 | 753,326,240 | 1,647 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-27 03:36:39 +0100
From: @arjenderijke
To: @sjoerdmullender
Version: -- development
Last updated: 2008-03-27 03:56:30 +0100
## Comment 9295
Date: 2008-03-27 15:36:39 +0100
From: @arjenderijke
Using monetdb build from cvs of two days ago, mclient has a problem with the -Xdebug parameter.
If you try to connect to an mserver5 with the command
mclient -lsql -ddatabasename -Xdebug
you get the error
MAPI = monetdb@localhost:50000
ACTION= mapi_start_talking
ERROR = !database 'ebug' does not exist
if you try the command
mclient -Xdebug -lsql -ddatabasename
it works as expected.
OS = Fedora 8 linux, standard CWI desktop
## Comment 9296
Date: 2008-03-27 15:56:30 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Use --Xdebug, not -Xdebug. Count the minuses.
-X is equivalent to --Xdebug, but if you use -Xdebug, the option is parsed as -X -d ebug (or --Xdebug --database=ebug), so you get what you ask for.
## Comment 9297
Date: 2008-03-27 16:02:01 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
The confusion clearly comes from Java here, where the argument /is/ -Xdebug by convention. I'm not sure why --Xdebug or -X was chosen in mclient, but maybe it's wise to change that, since in Java -Xyyyy means "extended", as in not really an option you normally would use, and subject to change, hence the Java option is just debug, but flagged as don't use it if you have no clue what you're doing.
This convention obviously doesn't hold for mclient.
## Comment 9298
Date: 2008-03-27 16:04:46 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
by the way, even though the invocation is invalid, it is weird that as last argument it doesn't work, whereas it does if as first argument.
(i.e. mclient doesn't warn/error that multiple -d arguments won't ever work)
## Comment 9299
Date: 2008-03-27 16:39:53 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
You are right, both that --Xdebug (-X) is a weird option (--debug makes much more sense) and that multiple -d arguments could do with a warning.
--Xdebug: changing this to --debug is not hard, but what about -X? Both -d and -D are taken, -X does not make sense when the long option is --debug. Plus it's an interface change, so not suitable for the stable version.
-d -d: There are more options where it makes sense to warn about multiple occurrences.
## Comment 9300
Date: 2008-03-27 17:05:37 +0100
From: @arjenderijke
Logged In: YES
user_id=1836138
Originator: YES
For the record, for my original bugreport RTFM does apply. But the comments by mr-meltdown are valid. And the order of the parameters should not matter.
Combining short parameter with options can lead to confusing situations. I am not sure if that is allowed in other linux commands.
## Comment 9301
Date: 2008-03-27 17:14:43 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Combining options in this way is a standard getopt feature. Many, many commands do it the same way. It's an ancient Unix custom.
What do you mean with "the order of the parameters should not matter"? If you use all different parameters, it doesn't matter. But if you specify the database twice, what is a program to do? (Answering my own question: it should probably give a warning, but it should also give a warning for a host of other parameters.)
## Comment 9302
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1927153 at http://sourceforge.net/support/tracker.php?aid=1927153
| Problem with mclient -Xdebug parameter | https://api.github.com/repos/MonetDB/MonetDB/issues/1646/comments | 0 | 2020-11-30T09:50:41Z | 2024-06-28T07:37:00Z | https://github.com/MonetDB/MonetDB/issues/1646 | 753,326,164 | 1,646 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-27 03:31:51 +0100
From: @arjenderijke
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2008-03-27 03:54:47 +0100
## Comment 9291
Date: 2008-03-27 15:31:51 +0100
From: @arjenderijke
Using monetdb build from cvs of two days ago, mserver5 ignores the mapi_open setting in the MonetDB.conf file.
If you start an mserver with mapi_open = true in the MonetDB.conf file, you get an
!ERROR mapi_reconnect: connect: Connection refused
Setup connection failed
error if you do mclient -lsql -ddatabasename -hhostname
It works if you do mclient -lsql -ddatabasename
If you start a mserver with the --set mapi_open=true parameter it works as expected.
The error occur both when you start mclient on the server host and on a remote host.
nmap reports the port as closed in the first case and open in the second case. A firewall is not involved.
OS = Fedora 8 Linux, standard CWI desktop
## Comment 9292
Date: 2008-03-27 15:38:56 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
not sure if this is a typo, but MonetDB 5 uses etc/monetdb5.conf, not etc/MonetDB.conf.
## Comment 9293
Date: 2008-03-27 15:54:47 +0100
From: @arjenderijke
Logged In: YES
user_id=1836138
Originator: YES
It is not a typo, it is a mistake. My mistake. So not a bug.
## Comment 9294
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1927148 at http://sourceforge.net/support/tracker.php?aid=1927148
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-common@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| mapi_open setting in MonetDB.conf ignored | https://api.github.com/repos/MonetDB/MonetDB/issues/1645/comments | 0 | 2020-11-30T09:50:39Z | 2024-06-28T07:37:00Z | https://github.com/MonetDB/MonetDB/issues/1645 | 753,326,122 | 1,645 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-26 01:14:31 +0100
From: @arjenderijke
To: @njnes
Version: -- development
Last updated: 2008-05-28 04:57:40 +0200
## Comment 9284
Date: 2008-03-26 13:14:31 +0100
From: @arjenderijke
I have a table with one record (see bugreport.txt):
The query:
SELECT BESTANDSNAAM
FROM VIDEO_PRODUKTIE
WHERE IMPALA_GEREED IS NOT NULL
AND SQL_GEREED IS NOT NULL
AND DATABASE_GEREED IS NULL
should return 'cut.mpg', but it returns no records (or 'null' if you do this select inside a function)
If you do a select query on the table with 0, 1 or 2 of the clauses, it gives the correct result.
But if you do (2nd and 3rd clause switched)
SELECT BESTANDSNAAM
FROM VIDEO_PRODUKTIE
WHERE IMPALA_GEREED IS NOT NULL
AND DATABASE_GEREED IS NULL
AND SQL_GEREED IS NOT NULL
than it returns the correct result.
This was tested on a stable build from today and a cvs build from yesterday.
This problem existed in the MonetDB-Mars-SuperBall version and i thought it was fixed in the MonetDB-Feb2008-SuperBall version, but i was mistaken or the bug is reintroduced.
## Comment 9285
Date: 2008-04-17 09:07:56 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
arjen could you try with the stable cvs version?
## Comment 9286
Date: 2008-05-22 16:40:36 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
fixed ....
## Comment 9287
Date: 2008-05-28 16:12:52 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Re-opened as we should consider adding a test (also) for this one ...
## Comment 9288
Date: 2008-05-28 16:40:02 +0200
From: @arjenderijke
Logged In: YES
user_id=1836138
Originator: YES
The test is there, it was added some time ago:
sql/src/test/BugTracker/Tests/select_multiple_not_null_constraints.SF-1926074.sql
But maybe not in all the branches
## Comment 9289
Date: 2008-05-28 16:57:40 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Ok, I just saw that the bug report was closed without any test being mentioned.
It's indeed there, but was not activated in the "All" file, yet.
Just did that.
Seems to be working fine.
Closing, again.
## Comment 9290
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1926074 at http://sourceforge.net/support/tracker.php?aid=1926074
| SQL: Select with triple where clause error | https://api.github.com/repos/MonetDB/MonetDB/issues/1644/comments | 0 | 2020-11-30T09:50:36Z | 2024-06-27T11:29:34Z | https://github.com/MonetDB/MonetDB/issues/1644 | 753,326,085 | 1,644 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-25 01:33:03 +0100
From: Wouter Alink <<alink>>
To: @sjoerdmullender
Version: -- development
Last updated: 2008-04-22 07:50:36 +0200
## Comment 9276
Date: 2008-03-25 13:33:03 +0100
From: Wouter Alink <<alink>>
Using yesterdays stable nightly build superSourceBall. (using milprintsummer xquery compilation)
After a long series of xqueries (mixed read and update queries), the query:
if (not(doc("beer.xml")/a/b/noot[@name="aap"]))
then
do insert (<noot name="aap"/>,"
") as last into doc("beer.xml")/a/b
else
()
generates the following error :
ERROR: interpret: no matching MIL operator to '[insert](BAT[oid,oid], BAT[oid,BAT])'.
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]
insert(str, int, int, str) : str
ERROR: interpret_params: ssort(param 1): evaluation error.
I know this isn't a proper bug-report, but does anyone have a clue as to where to look? The bug is reproducable, but providing the full script is not feasible.
So far, i've managed to locate the error in the generated mil. The line "vx_lookup(...)" in the fragment below is where the error is generated:
{ translate pf:attribute($ctx as node()*, $elt_ns as xs:string, $elt_loc as xs:string, $attr_ns as xs:string, $attr_loc as xs:string, $hash as xs:double) as element()*
var id_pre := vx_lookup(ws, iter001, item001, kind001, item_str_, item_str_002, item_str_003, item_str_004, item_str_005, true);
iter := id_pre.hmark(0@0).leftfetchjoin(iter001);
kind := set_kind(get_container(id_pre.hmark(0@0).leftfetchjoin(kind001)),ELEM);
item := id_pre.tmark(0@0);
ipik := item;
}
## Comment 9277
Date: 2008-04-01 18:00:01 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
I believe I've nailed this bug. Can you check?
## Comment 9278
Date: 2008-04-02 15:50:46 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
Hmmm, strange.
Using todays downloaded nightly stable supersourceball (./monetdb-install.sh --enable-xquery):
2008-04-02 13:33 /home/wouter/Desktop/downloads/MonetDB-Feb2008-SuperBall-DB1.tar.bz2
The bug problem still exists on my machine (tested with the bug_insert.xq script and related files,
which still fail with the same error). Do you get better results?
## Comment 9279
Date: 2008-04-15 10:55:59 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
I just tried it again on the stable branch. It works flawlessly for me.
Please make sure that the files you downloaded are up-to-date. If compilation fails, you may perhaps get old files.
## Comment 9280
Date: 2008-04-22 14:39:58 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Wouter, any news?
## Comment 9281
Date: 2008-04-22 19:50:36 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
no news, haven't tried since 2008-04-02. if you say that it works for you, than it'll work for me.
i know there are still other bugs in the update-stuff, but they are hard to isolate.
## Comment 9282
Date: 2008-05-08 16:12:26 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Would there (have) be(en) a simple test to monitor also this bug fix?
## Comment 9283
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1925123 at http://sourceforge.net/support/tracker.php?aid=1925123
| XQ: insert fails after many queries | https://api.github.com/repos/MonetDB/MonetDB/issues/1643/comments | 0 | 2020-11-30T09:50:34Z | 2024-06-27T11:29:33Z | https://github.com/MonetDB/MonetDB/issues/1643 | 753,326,057 | 1,643 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-21 06:11:27 +0100
From: mmckennirey <<mmckennirey>>
To: @njnes
Version: -- development
Last updated: 2008-03-25 03:30:46 +0100
## Comment 9273
Date: 2008-03-21 18:11:27 +0100
From: mmckennirey <<mmckennirey>>
Using COPY fails when trying to upload data into a table within a schema
CREATE TABLE test (
column1 VARCHAR(32),
column2 VARCHAR(32)
);
COPY INTO test FROM '/location/file.csv' USING DELIMITERS ',', '\n';
succeeds.
CREATE SCHEMA abc;
CREATE TABLE abc.test (
column1 VARCHAR(32),
column2 VARCHAR(32)
);
COPY INTO abc.test FROM '/location/file.csv' USING DELIMITERS ',', '\n';
fails with
!SQLException:sql:table test not found
!SQLException:importTable:failed to import table
## Comment 9274
Date: 2008-03-21 18:42:51 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
We now pass the full schema and table to the import function. This test was added to the src/test/bugs directory.
## Comment 9275
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1922377 at http://sourceforge.net/support/tracker.php?aid=1922377
| COPY INTO using a schema fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1642/comments | 0 | 2020-11-30T09:50:31Z | 2024-06-27T11:29:33Z | https://github.com/MonetDB/MonetDB/issues/1642 | 753,326,023 | 1,642 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-21 04:34:26 +0100
From: Andrey Tovchigrechko <<andreyto>>
To: @njnes
Version: -- development
Last updated: 2008-05-22 03:31:22 +0200
## Comment 9269
Date: 2008-03-21 04:34:26 +0100
From: Andrey Tovchigrechko <<andreyto>>
This happens on both SuSe 10 x86_64 12GB RAM and Ubuntu Gutsy x86_32 3GB RAM: after COPY INTO is used against the same table several times, and the database is restarted, the majority of records get filled with zeros. Same results is when loading chunks from one file, or splitting this file into many small ones.
MonetDB was built with monetdb-install.sh --nightly=stable on Ubuntu, and both --nightly=stable and --nightly=current on SuSe
This bug has been reported before for extremely large batches, but here it appears on small ones (total records are 500000 in 50000 batches). The mclient session is shown below. I can send or upload the file with test data (11M gzipped).
I spend several days fighting with MonetDB SQL (mostly under SuSe 10 x86_64). It exhibits various other odd behaviors: 'select * from ...' stops printing any records in mclient (although 'select field_name from ... does', mclient suddenly starts to refuse logins with valid user, trivial 'union' selects zero number of records with non-zero number of records coming from each individual select. Although the query performance is spectacular, I am giving up and going back to MySQL. It looks that at least the SQL interface of MonetDB is in some early beta stage at best.
Andrey
./monetdb-install.sh --enable-sql --prefix=/home/andrey/monetdb --nightly=stable
export PATH=$PATH:/home/andrey/monetdb/bin
merovingian
monetdb create test
monetdb start test
mclient -l sql -d test < ../sql/bulk_test.sql
[ 50000 ]
[ 50000 ]
[ 50000 ]
[ 50000 ]
[ 50000 ]
[ 50000 ]
[ 50000 ]
[ 50000 ]
[ 50000 ]
[ 50000 ]
andrey@seven:~/work/mgtaxa/test_data$ mclient -l sql -d test
sql>select count(*) from test_bulk;
+--------+
| count_ |
+========+
| 500000 |
+--------+
sql>select count(*) from test_bulk where taxid = 0;
+--------+
| count_ |
+========+
| 3673 |
+--------+
sql>\q
andrey@seven:~/work/mgtaxa/test_data$ monetdb stop test
andrey@seven:~/work/mgtaxa/test_data$ monetdb start test
andrey@seven:~/work/mgtaxa/test_data$ mclient -l sql -d test
sql>select count(*) from test_bulk where taxid = 0;
+--------+
| count_ |
+========+
| 450003 |
+--------+
sql>
## Comment 9270
Date: 2008-03-21 09:09:57 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Thanks for the bug report. Could you indeed upload the 11MB file please. We could like to fix also the other problems you report but with out bug report and/or test script this is hard. Thanks again and hope to see you return to MonetDB/SQL soon.
## Comment 9271
Date: 2008-05-22 15:31:22 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
We found a bug in the handling of mmapped files, so this is now fixed. Could you check if this fixes the problem for you.
## Comment 9272
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1921884 at http://sourceforge.net/support/tracker.php?aid=1921884
| SQL:COPY INTO silently corrupts database even on small loads | https://api.github.com/repos/MonetDB/MonetDB/issues/1641/comments | 0 | 2020-11-30T09:50:28Z | 2024-06-27T11:29:32Z | https://github.com/MonetDB/MonetDB/issues/1641 | 753,325,989 | 1,641 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-20 10:58:34 +0100
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2008-03-22 09:38:59 +0100
## Comment 9261
Date: 2008-03-20 10:58:34 +0100
From: @drstmane
When giving the "?" command on mserver5's MAL console, I get the following parseError with both the latest 5.4 release and the latest 5.5 development version from CVS:
========
$ mserver5
MonetDB server v5.4.1, based on kernel v1.22.1
Serving database 'demo'
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Copyright (c) 1993-2008 CWI, all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
>?
? - show this message
! - show the history
<file - read input from file
>file - save response in file
> - response to terminal
cd - change directory
\q - terminate session
!SyntaxException:parseError:?
!SyntaxException:parseError:^<identifier> expected
========
## Comment 9262
Date: 2008-03-20 12:21:56 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
solved. no test needed.
## Comment 9263
Date: 2008-03-21 11:16:24 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
any reason why "no test needed"?
## Comment 9264
Date: 2008-03-21 11:21:01 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
too simple bug. A line was out of place, causing
the reader not to restart as it should
## Comment 9265
Date: 2008-03-21 11:23:03 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
with that argument, about half of all SQL tests could have been omitted
## Comment 9266
Date: 2008-03-21 11:25:01 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
and, you could take this exercise to finally fix that dreaded input/reader bug that makes whole lines being ignored after a syntax error.
## Comment 9267
Date: 2008-03-22 09:38:59 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
the dreaded input/reader bug is also fixed.
a test is added for the dreaded bug.
## Comment 9268
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1920819 at http://sourceforge.net/support/tracker.php?aid=1920819
| M5 console: "?" gives parseError | https://api.github.com/repos/MonetDB/MonetDB/issues/1640/comments | 0 | 2020-11-30T09:50:25Z | 2024-06-27T11:29:31Z | https://github.com/MonetDB/MonetDB/issues/1640 | 753,325,954 | 1,640 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-20 10:52:17 +0100
From: @djoerd
To: Lefteris Sidirourgos <<lsidir>>
Version: -- development
Last updated: 2008-04-12 12:01:41 +0200
## Comment 9255
Date: 2008-03-20 10:52:17 +0100
From: @djoerd
doc("buchenwald-mapping.xml")//document[@id="DVD_20"]
gives the following error message
MAPI = monetdb@localhost:50201
QUERY = doc("buchenwald-mapping.xml")//document[@id="DVD_20"]
ERROR = !ERROR: interpret: no matching MIL operator to '[insert](BAT[oid,oid], BAT[oid,BAT])'.
!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]
! insert(str, int, int, str) : str
!ERROR: interpret_params: ssort(param 1): evaluation error.
see attached file.
## Comment 9256
Date: 2008-03-20 11:42:58 +0100
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
With the latest checkout it works fine on my computer for both milprint_summer and the algebra. Which version are you using? milprint_summer or the algebra? On the other hand, if you are running this query with
"mclient -lxq -G", can you please restart MonetDB and mclient and see if you get the same error?
lefteris
## Comment 9257
Date: 2008-04-12 00:13:05 +0200
From: @djoerd
Logged In: YES
user_id=1730227
Originator: YES
Dear Lefteris,
Thanks for your reply. I am sorry. I restarted the server (and threw away the database) at the time, but now, a few weeks later, I cannot reproduce it anymore.
Not sure what happened.
Best, Djoerd.
## Comment 9258
Date: 2008-04-12 12:01:41 +0200
From: @lsidir
Logged In: YES
user_id=1856546
Originator: NO
I am closing this bug and not adding any test because it could not be reproduced.
## Comment 9259
Date: 2008-05-08 16:08:39 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Just as a side-note:
Test are (not only) to reproduce bug before they are fixed, but also to monitor/ensure that desired behavour does work as expected.
Hence, a test showing that the reported problem does not (no longer?) exist is also fine.
Next time ... ;-)
## Comment 9260
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1920813 at http://sourceforge.net/support/tracker.php?aid=1920813
| XQ: Simple attribute predicate fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1639/comments | 0 | 2020-11-30T09:50:22Z | 2024-06-28T07:37:00Z | https://github.com/MonetDB/MonetDB/issues/1639 | 753,325,918 | 1,639 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-19 03:04:42 +0100
From: @peterboncz
To: @mlkersten
Version: -- development
Last updated: 2008-03-20 02:09:41 +0100
## Comment 9245
Date: 2008-03-19 15:04:42 +0100
From: @peterboncz
not knowing about the MAL pattern
bbp.bind(:str) :bat[any::1,any::2]
I tried the MAL command
bat5.load(:str) :bat[any::1,any::2]
though the implementation and signature of that command appear to be fully correct, bat5.load() always give a type mismatch error whatever you do.
So, the problem is not so much bat5.load(), but (I assume) the function resolution of any MAL command that has :any::x or BAT[:any::x,:any::y] in its signature.
## Comment 9246
Date: 2008-03-19 16:42:02 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
MAL requires that all arguments are strongly typed.
you have to type the result variable upfront, e.g.
b:bat[:oid,:str]:= bat.load("mybat");
## Comment 9247
Date: 2008-03-19 16:49:16 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: YES
I was providing the correct types. Did you try it?
## Comment 9248
Date: 2008-03-19 17:17:27 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
can you give an example of what you're doing and what exact error messages you get?
## Comment 9249
Date: 2008-03-19 17:32:06 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
suite_00/Tests/test_40.mal
The number of tests for the bat.load is quite minimal.
A small test example to would be helpful.
## Comment 9250
Date: 2008-03-19 23:42:12 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
first, bat5.load() is not a function known to me.
We only have bat.load()
Another test has been added and shows
that basic type resolution should be more
restrictive, not allowing illegal type bindings.
We still need an example to illustrate the problem
## Comment 9251
Date: 2008-03-20 02:09:41 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: YES
sorry guys
these are my first steps in Monet5, and since I did not see a module named bat (in MonetDB5/src/*) but did see bat5 (and it contained functions similar to M4's bat) so I just tried to use it..
I am starting to understand, that bat5.mx is called bat in MAL
the documentation on the core modules is quite slim; would be nice to have for each module an machine-generated extract with exact module name and command/pattern signatures -- just to avoid such confusions.
## Comment 9252
Date: 2008-03-20 06:54:25 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
To solve the riddle, I feel free to provide the example that IMHO explains the situation:
========
>a:=bat5.load("abc");
!TypeException:user.main[1]:'bat5.load' undefined in: a:any := bat5.load(_2:str)
========
Obviously, the "TypeExeption" is/was the misleading suspect in this (and possibly other) case(s).
A clearer error message stating that module "bat5" might (have) be(en) helpful in this (and possibly other) case(s).
Using the existing "bat.load()" does indeed give a reasonable error message:
========
>b:=bat.load("abc");
!MALException:bat.unload: file name missing
function user.main():void;
b := bat.load("abc");
end main;
========
## Comment 9253
Date: 2008-03-20 06:56:49 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Sorry, obviously I meant to write:
A clearer error message stating that module "bat5" +++does not exist / is unknown+++ might (have) be(en) helpful in this (and possibly other) case(s).
## Comment 9254
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1919631 at http://sourceforge.net/support/tracker.php?aid=1919631
| MAL command resolution: BAT signatures with :any | https://api.github.com/repos/MonetDB/MonetDB/issues/1638/comments | 0 | 2020-11-30T09:50:19Z | 2024-06-28T07:36:59Z | https://github.com/MonetDB/MonetDB/issues/1638 | 753,325,876 | 1,638 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-18 10:19:18 +0100
From: Jorge Limon <<geolemo>>
To: @njnes
Version: -- development
Last updated: 2008-03-21 09:10:27 +0100
## Comment 9243
Date: 2008-03-18 22:19:18 +0100
From: Jorge Limon <<geolemo>>
If you try to run the following SQL statement agains VOC database:
sql>select count(1) from voyages;
you get the followinf error:
MAPI = voc@localhost:50000
ACTION= read_line
QUERY = select count(1) from voyages;
ERROR = Connection terminated
...and Monet Server down.
Operating System: Windows XP
## Comment 9244
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1918780 at http://sourceforge.net/support/tracker.php?aid=1918780
| Monet Server down with malformed sql statement | https://api.github.com/repos/MonetDB/MonetDB/issues/1637/comments | 0 | 2020-11-30T09:50:16Z | 2024-06-27T11:29:28Z | https://github.com/MonetDB/MonetDB/issues/1637 | 753,325,831 | 1,637 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-18 02:10:19 +0100
From: @arjenderijke
To: @njnes
Version: -- development
Last updated: 2008-03-25 03:32:01 +0100
## Comment 9240
Date: 2008-03-18 14:10:19 +0100
From: @arjenderijke
After compiling monetdb5 using yesterday's (20080317) source from cvs, the creation of tables will fail after one table.
If you perform this script:
CREATE TABLE TESTA (
TESTA_ID integer
);
CREATE TABLE TESTB (
TESTB_ID integer
);
using mclient -lsql < testscript.sql
and than connect to the database using mclient -lsql
This query
sql>select * from tables;
will give (as expected):
| 3882 |testa | 985 |null | 0 |false | 0 | 0 |
| 3884 |testb | 985 |null | 0 |false | 0 | 0 |
+------+-------------+------+----------------------+-----+------+------+------+
and
sql>\d testa
CREATE TABLE "sys"."testa" (
"testa_id" int
);
but
sql>\d testb
Table sys.testb does not exist.
similar thing happen if you try to create multiple tables within mclient, of if you dump the database with mclient -lsql -D
I found this when trying to make a simple testcase to reproduce an error with foreign key constraint. I now suspect that that error was a symptom of this problem. So i think this problem is at least a week old.
## Comment 9241
Date: 2008-03-25 15:32:01 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
problem is fixed by disabling the recycler. No tests needed as many sql create statements exists in the test set.
## Comment 9242
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1918135 at http://sourceforge.net/support/tracker.php?aid=1918135
| Cannot create more than one table | https://api.github.com/repos/MonetDB/MonetDB/issues/1636/comments | 0 | 2020-11-30T09:50:13Z | 2024-06-27T11:29:27Z | https://github.com/MonetDB/MonetDB/issues/1636 | 753,325,805 | 1,636 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-17 04:19:43 +0100
From: Andrey Tovchigrechko <<andreyto>>
To: @sjoerdmullender
Version: -- development
Last updated: 2008-04-21 04:38:39 +0200
## Comment 9237
Date: 2008-03-17 16:19:43 +0100
From: Andrey Tovchigrechko <<andreyto>>
MonetSQLdb.converters.escape(x, conv=None)
should return 'tuple' for any input sequence type (currently it returns tuple only if it receives tuple, and returns list if it receives list).
The return result is used as a second argument in expression 'query = query % self.connection.literal(args)' in cursors.py. The '%' operator raises an exception on anything but tuple.
Also, when 'escape()' cannot convert some argument, it should immediately raise a descriptive exception. Currently it silently drops the argument from the result sequence, which causes an exception to be raised later in the calling code. That exception reads like this:
"""ProgrammingError: not enough arguments for format string"""
This unnecessarily complicates debugging.
System:
2.6.16.27-0.6-smp 1 SMP Wed Dec 13 09:34:50 UTC 2006 x86_64 x86_64 x86_64 GNU/Linux
gcc 4.10
python 2.4.4
I attached test and patch files. Alternatively, Connection.literal() can convert 'escape()' result to a tuple.
## Comment 9238
Date: 2008-04-21 16:38:39 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Fixed in stable branch.
Test added as sql/src/test/BugTracker/Tests/python_escape.SF-1916844.SQL.py.
## Comment 9239
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1916844 at http://sourceforge.net/support/tracker.php?aid=1916844
| Bug in Python interface converters.py | https://api.github.com/repos/MonetDB/MonetDB/issues/1635/comments | 0 | 2020-11-30T09:50:10Z | 2024-06-27T11:29:26Z | https://github.com/MonetDB/MonetDB/issues/1635 | 753,325,765 | 1,635 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-14 07:04:47 +0100
From: Richard Eckart <<wyldfire>>
To: @sjoerdmullender
Version: -- development
Last updated: 2008-12-08 04:35:06 +0100
## Comment 9225
Date: 2008-03-14 19:04:47 +0100
From: Richard Eckart <<wyldfire>>
====== System ======
OS: OS X Tiger 10.4.11
gcc: powerpc-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5250)
MonetDB was compiled from the Feb 2008 Superball.
====== Problem ======
I start up MServer:
$ ./Mserver --dbinit="module(pathfinder);"
MonetDB Server v4.22.0
based on GDK v1.22.0
Copyright (c) 1993-2008, CWI. All rights reserved.
Compiled for powerpc-apple-darwin8.11.0/32bit with 32bit OIDs;
dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.5.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.22.0 loaded
XRPC administrative console at http://127.0.0.1:50001/admin
MonetDB>
On another terminal I run a simple test:
$ cat > test.xq
(1, 42.0, "Hello World", <node attr="value">test</node>)
$ ./mclient -lx test.xq
_ (blink blink blink ...)
and there it hangs. So I go back to the server to see what's up. I
tried the "threads()" and
"clients()" commands.
Well, to me all looks fine except that the "monetdb" client does not
seem to have actually sent any command ("").
Funnily when I got back to the first terminal, the mclient command
had completed. So I tried again.
It seems that the mclient command will complete as soon as I hit
"return" a couple of times on the MonetDB> prompt.
The same goes for the mjclient command.
## Comment 9226
Date: 2008-03-16 11:48:28 +0100
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: NO
(i posted this first at the users-mailinglist, but i guess it belongs here)
I witnessed a similar problem yesterday on freebsd (with the Feb2008
release). It was not my computer, and I do not really have more details.
somehow (when running Mserver in a shell) setting "deamon=yes" in the
MonetDB.conf seemed to help.
it doesn't solve the actual problem, but perhaps it might help finding it...?
## Comment 9227
Date: 2008-04-22 14:48:26 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
We do this kind of thing all the time without any problems. The difference seems to be that we use different O/S's and distributions.
I'm inclined to call this an O/S bug (or bug in the thread implementation).
I guess what would help is to attach a debugger while the Mserver is hanging and to look at what all the threads are doing. Then we know for sure.
So can you do
gdb -p <Mserver-pid>
and then at the gd prompt
thread apply all bt
## Comment 9228
Date: 2008-05-06 21:17:07 +0200
From: Richard Eckart <<wyldfire>>
Logged In: YES
user_id=398457
Originator: YES
I started the server:
$ ./Mserver --dbinit="module(pathfinder);"
Started the client to run the query:
$ ./MonetDB/bin/mclient -lx test.xq
Client hangs. Firing up GDB and showing the stack traces.
(gdb) thread apply all bt
Thread 6 (process 20279 thread 0x2403):
0 0x9002c3c8 in semaphore_wait_signal_trap ()
1 0x90001c10 in pthread_mutex_lock ()
2 0x9002dc04 in flockfile ()
3 0x90002094 in fileno ()
4 0x00473300 in yy_init_buffer (b=0x1100550, file=0xa0001b9c) at monet_parse.yy.c:1927
5 0x00473ab0 in yyrestart (input_file=0xa0001b9c) at monet_parse.yy.c:1804
6 0x00473ce4 in yy_get_next_buffer () at monet_parse.yy.c:1599
7 0x00477174 in yylex () at monet_parse.yy.c:1430
8 0x004715f0 in yyparse () at monet_parse.tab.c:1638
9 0x00447678 in parseClient (c=0x48601c, reschedule=5379) at monet_client.c:583
10 0x094065b0 in xquery_mil2tree (ctx=0x1403, buf=0x1503 "") at pathfinder.c:281
11 0x09406630 in xquery_mil_exec (ctx=0xa7b95c8, buf=0x10cd000 "time_shred := 0LL;\ntime_start := usec();\nvar err;\n{\n {\n var ws ;\n err := CATCH({\n ws := ws_create(0); get full picture on var_usage (and sort it)\n var usage ;\n {\n int_values.append(1LL);\n"...) at pathfinder.c:302
12 0x09407db4 in xquery_compile_exec (ctx=0xa7b95c8, url=0x0, is_url=0, prologue=0xf1403e4c, query=0xf1403e50, epilogue=0xf1403e54, nsurl=0x1 <Address 0x1 out of bounds>) at pathfinder.c:443
13 0x0940a270 in xquery_prepare (ctx=0xa7b95c8, usec=0, query=0x10c4009 "(1, 42.0, \"Hello World\", <node attr=\"value\">test</node>)\n") at pathfinder.c:2028
14 0x0940a648 in xquery_client_engine (mc=0x100e7ac) at pathfinder.c:2167
15 0x0100a568 in mapi_client_engine (FC=0x1403) at mapi.c:316
16 0x9002bd08 in _pthread_body ()
Thread 5 (process 20279 thread 0x2303):
0 0x900411f8 in mach_wait_until ()
1 0x90040fc4 in nanosleep ()
2 0x0251d504 in MT_sleep_ms (ms=0) at gdk_posix.c:1770
3 0x007b924c in CMDsleep (secs=0x0) at alarm.c:145
4 0x007b88f0 in CMDsleep_unpack522853172 (argc=0, argv=0xf1002d08) at alarm.glue.c:43
5 0x00432524 in interpret (stk=545, lt=0xb80e8a8, res=0xf1003da8) at monet_interpreter.c:1070
6 0x00440e18 in interpret_seqblock (stk=545, lt=0xb80dbc8, res=0xf1003da8, scope=175838360) at monet_interpreter.c:2194
7 0x00430f18 in interpret (stk=548, lt=0xb80dbc8, res=0xf1003da8) at monet_interpreter.c:652
8 0x00441b04 in interpret_while (stk=548, lt=0xb80db50, res=0xf1003da8) at monet_interpreter.c:1187
9 0x00431120 in interpret (stk=548, lt=0xb80db50, res=0xf1003da8) at monet_interpreter.c:719
10 0x00440e18 in interpret_seqblock (stk=548, lt=0xb80d988, res=0xf1003da8, scope=175838360) at monet_interpreter.c:2194
11 0x00430f18 in interpret (stk=4, lt=0xb80d988, res=0xf1003da8) at monet_interpreter.c:652
12 0x004321bc in interpret (stk=4, lt=0xb80d7a8, res=0xf1003da8) at monet_interpreter.c:1044
13 0x004433c8 in handleRequest (t=0x27389cc, q=0xb80d8d8, res=0xf1003da8) at monet_queue.c:342
14 0x00443bfc in doRequest (t=0x27389cc, preference=0x0) at monet_queue.c:368
15 0x00478070 in monetInterpreter (status=0x25c3090) at monet_process.c:45
16 0x9002bd08 in _pthread_body ()
Thread 4 (process 20279 thread 0x2203):
0 0x9001f88c in select ()
1 0x09d640e4 in shttpd_poll (ctx=0xf0c028b8, milliseconds=200) at shttpd.c:2962
2 0x09d65594 in CMDrpcd_start (port=0x0, open=0xf0c02ab8 "\001", option=0x68 <Address 0x68 out of bounds>) at xrpc_server.c:1183
3 0x09d64978 in CMDrpcd_start_unpack1996251672 (argc=0, argv=0xf0c02a98) at xrpc_server.glue.c:43
4 0x00432524 in interpret (stk=3, lt=0xb80bde8, res=0xf0c02da8) at monet_interpreter.c:1070
5 0x004433c8 in handleRequest (t=0x2738978, q=0xb80c008, res=0xf0c02da8) at monet_queue.c:342
6 0x00443bfc in doRequest (t=0x2738978, preference=0x0) at monet_queue.c:368
7 0x00478070 in monetInterpreter (status=0x25c3090) at monet_process.c:45
8 0x9002bd08 in _pthread_body ()
Thread 3 (process 20279 thread 0x1003):
0 0x9001f88c in select ()
1 0x0100b0e4 in MAPIlisten (stk=2, lt=0x3044401, res=0xffffffff) at mapi.c:729
2 0x00431594 in interpret (stk=2, lt=0xabc2b78, res=0xf0801da8) at monet_interpreter.c:806
3 0x004433c8 in handleRequest (t=0x2738924, q=0xabc2d98, res=0xf0801da8) at monet_queue.c:342
4 0x00443bfc in doRequest (t=0x2738924, preference=0x0) at monet_queue.c:368
5 0x00478070 in monetInterpreter (status=0x25c3090) at monet_process.c:45
6 0x9002bd08 in _pthread_body ()
Thread 2 (process 20279 thread 0xf03):
0 0x900411f8 in mach_wait_until ()
1 0x90040fc4 in nanosleep ()
2 0x0251d504 in MT_sleep_ms (ms=0) at gdk_posix.c:1770
3 0x023da720 in GDKvmtrim (limit=0x25c30bc) at gdk_utils.c:1350
4 0x9002bd08 in _pthread_body ()
Thread 1 (process 20279 thread 0xd03):
0 0x900148a4 in read ()
1 0x9001b0e8 in _sread ()
2 0x9001b05c in __srefill ()
3 0x9001ae44 in fread ()
4 0x0051333c in file_read (s=0x11079b0, buf=0x303ee08, elmsize=1, cnt=1) at stream.c:447
5 0x004470f0 in readClient (c=0x485fa8) at monet_client.c:428
6 0x004477cc in serveClient (stk=0, lt=0x1778000, res=0x485fa8) at monet_client.c:622
7 0x00431594 in interpret (stk=0, lt=0x1167a48, res=0xbffff3a8) at monet_interpreter.c:806
8 0x004433c8 in handleRequest (t=0x27388d0, q=0xb808268, res=0xbffff3a8) at monet_queue.c:342
9 0x00443bfc in doRequest (t=0x27388d0, preference=0x0) at monet_queue.c:368
10 0x00478070 in monetInterpreter (status=0x25c3090) at monet_process.c:45
11 0x00002f38 in main (argc=2, av=0xbffff570) at Mserver.c:234
(gdb)
## Comment 9229
Date: 2008-10-02 23:50:35 +0200
From: @drstmane
This appear to be a MacOS X (Darwin) and (free)BSD inherent problem. It seems that a read for input in one thread (here: Mserver's console prompt) block the whole program/process, as opposed to only blocking htis very thread; hence, also the thread that listens for client connections is unexpectedly (incorrectly?) blocked. While it seems to be beyond our control to fix this problem, a work-around is to start Mserver in daemon mode, to omit the Mserver (MIL-) console:
Mserver --dbinit='module(pathfinder);' --set monet_daemon=yes
## Comment 9230
Date: 2008-10-02 23:58:46 +0200
From: @drstmane
(Mainly for the MonetDB developers:)
The problems seems to occur only with "Mserver", i.e., MonetDB/4 (with all back-end: MIL, SQL, XQuery),
but not with "mserver5", i.e., MonetDB/5 (both MAL & SQL seems to work fine) ...
## Comment 9231
Date: 2008-10-31 14:00:31 +0100
From: Jan Rittinger <<jan.rittinger>>
I attached a trace with a simplified example. Perhaps it helps to solve the bug.
File Added: Mserver-OSX-analysis
## Comment 9232
Date: 2008-11-02 17:00:38 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: rustamabd@users.sourceforge.net ----
With MonetDB 4.25.0 build from CVS on 2008-11-02 the problem seems to be fixed.
$ Mserver --dbinit="module(pathfinder);"
MonetDB Server v4.25.0
based on GDK v1.25.0
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-, MonetDB B.V.. All rights reserved.
Compiled for i386-unknown-freebsd7.0/32bit with 32bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.9.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.25.0 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:50001/admin
MonetDB>
$ cat > test.xq
(1, 42.0, "Hello World", <node attr="value">test</node>)
$ mclient -lx test.xq
1,
42.000000,
"Hello World",
<node attr="value">test</node>
$
## Comment 9233
Date: 2008-11-03 22:34:21 +0100
From: @sjoerdmullender
For some reason flex wants to know whether it is running interactively. It does that by checking whether `yyin' points to a
tty (isatty(fileno(yyin))). We don't use `yyin', but flex doesn't care. It initializes yyin to stdin and does the above mentioned check.
On Linux and Windows this seems to work fine, however, on Darwin this check hangs because while one thread is trying to call fileno(yyin) (i.e. fileno(stdin)) another thread is actually reading from stdin (or rather, hanging in a read system call). This read is protected with a semaphore and fileno has to wait for this semaphore. Hence the fileno will only succeed once the read in the other thread returns.
All of this can be solved by circumventing the use of fileno (and isatty). We don't need it, so get rid of it!
This should fix this bug. The patch was only applied to the development (HEAD) branch.
Thanks to JanR for running the debugger and testing the solution.
## Comment 9234
Date: 2008-12-08 16:35:06 +0100
From: @sjoerdmullender
Closing.
We don't have a way to test this automatically.
## Comment 9235
Date: 2009-02-16 13:42:26 +0100
From: @drstmane
standard mclient tests on Darwin used to fail before this was fixed;
hence, it is tested --- at least when ever we happen to have access to Darwin machines during testing ...
## Comment 9236
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1914463 at http://sourceforge.net/support/tracker.php?aid=1914463
| Client hangs unless somebody presses enter at server prompt | https://api.github.com/repos/MonetDB/MonetDB/issues/1634/comments | 0 | 2020-11-30T09:50:07Z | 2024-06-27T11:29:24Z | https://github.com/MonetDB/MonetDB/issues/1634 | 753,325,718 | 1,634 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-13 03:51:55 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-03-21 09:14:29 +0100
## Comment 9222
Date: 2008-03-13 15:51:55 +0100
From: @romulogoncalves
The follwing code crash mserver5:
CREATE FUNCTION fGetNearbyObjEq (ra float, decim float, r float)
RETURNS TABLE (
objID bigint,
run int ,
camcol int ,
field int ,
rerun int ,
type int ,
cx float ,
cy float ,
cz float ,
htmID bigint,
distance float -- distance in arc minutes
)
BEGIN
DECLARE TABLE proxtab (
objID bigint,
run int ,
camcol int ,
field int ,
rerun int ,
type int ,
cx float ,
cy float ,
cz float ,
htmID bigint,
distance float -- distance in arc minutes
);
RETURN proxtab;
END;
create table t2 (objID bigint NULL);
SELECT * FROM t2 s, fGetNearbyObjEq(20.925,1.67,29.4) WHERE s.objID=n.objID;
drop function fGetNearbyObjEq;
drop table t2;
This debug information shows where and what is the problem...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1107310928 (LWP 18423)]
0x0000003c4bc79010 in strcmp () from /lib64/libc.so.6
(gdb) up
1 0x00002aaabe721157 in find_table_column (columns=0x424a518,
tname=0x41ff238 "n", cname=0x41ff248 "objid")
at /ufs/goncalve/MonetDB/sql/src/server/sql_scope.mx:371
371 if (strcmp(c->tname, tname) == 0 && strcmp(c->cname, cname) == 0) {
(gdb) p tname
$1 = 0x41ff238 "n"
(gdb) p c->tname
$2 = 0x0
(gdb)
Romulo
## Comment 9223
Date: 2008-03-21 09:14:29 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
test was added to the BugTracker directory
## Comment 9224
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1913572 at http://sourceforge.net/support/tracker.php?aid=1913572
| column from a table function | https://api.github.com/repos/MonetDB/MonetDB/issues/1633/comments | 0 | 2020-11-30T09:50:04Z | 2024-06-27T11:29:23Z | https://github.com/MonetDB/MonetDB/issues/1633 | 753,325,680 | 1,633 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-13 12:45:44 +0100
From: @grobian
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2008-03-13 01:17:45 +0100
## Comment 9217
Date: 2008-03-13 12:45:44 +0100
From: @grobian
Merovingian doesn't handle socket connections untill after the first command via its control channel has been executed. This is typically done via the monetdb utility. After the first control command, merovingian responds to TCP sockets properly.
## Comment 9218
Date: 2008-03-13 13:17:45 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
fixed in cvs revision 1.31
## Comment 9219
Date: 2008-05-08 16:15:16 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
I guess, automatic merovingian tests are still out of reach (for now?),
right?
## Comment 9220
Date: 2008-05-08 17:02:15 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
Technically they are possible, but mtest.py is not up for the job (yet). I need some modifications there, which we may want to talk about, so we can add trivial monetdb(1) and merovingian(1) tests.
## Comment 9221
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1913438 at http://sourceforge.net/support/tracker.php?aid=1913438
| Merovingian: no connections accepted untill first command | https://api.github.com/repos/MonetDB/MonetDB/issues/1632/comments | 0 | 2020-11-30T09:50:01Z | 2024-06-27T11:29:22Z | https://github.com/MonetDB/MonetDB/issues/1632 | 753,325,649 | 1,632 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-11 05:06:18 +0100
From: @arjenderijke
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-03-19 06:17:05 +0100
## Comment 9213
Date: 2008-03-11 17:06:18 +0100
From: @arjenderijke
If you have a table with a column ID with consecutive numbers say 1..100, the query
SELECT ID
FROM TABLE
WHERE (ID - 10) BETWEEN 0 AND 10;
gives the correct result but the query
SELECT ID
FROM TABLE
WHERE (10 - ID) BETWEEN 0 AND 10;
gives the wrong results.
## Comment 9214
Date: 2008-03-11 17:11:56 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Most probably, this one works fine with M4/SQL ;-)
I assume this fails due to a property propagation bug in M5's batcalc, which has already been fix in M4's bat_arith, but could now simply by propagated to M5's batcalc by diff|patch due to code incompatibilities. I'll re-align batcalc with bat_arith, and hence, fix the property propagation, once I find time for this "hobby"...
## Comment 9215
Date: 2008-03-19 18:17:05 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
fixed in CVS (MonetDB_5-4 release branch; propagation to development trunk pending):
re-aligned (and hence fixed) property propagation in M5's batcalc.mx with M4's bat_arith.mx
added test in sql/src/test/BugTracker/Tests/BETWEEN_error.SF-1911991.*
## Comment 9216
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1911991 at http://sourceforge.net/support/tracker.php?aid=1911991
| BETWEEN returns wrong results | https://api.github.com/repos/MonetDB/MonetDB/issues/1631/comments | 0 | 2020-11-30T09:49:58Z | 2024-06-27T11:29:21Z | https://github.com/MonetDB/MonetDB/issues/1631 | 753,325,610 | 1,631 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-10 05:37:11 +0100
From: Wouter Alink <<alink>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2009-11-18 10:45:25 +0100
## Comment 9202
Date: 2008-03-10 17:37:11 +0100
From: Wouter Alink <<alink>>
Using mps.
Querying 'pf:documents()' will never return ('hang') after having inserted a node and then querying for a non-existing doc a few times.
Reproduce by inserting a document "aap.xml" in the database (with content '<aap/>' and shred it updatable):
pf:add-doc("/tmp/aap.xml","aap.xml","aap.xml",10)
The following script will execute fine (can be run many times):
N=0
while [[ $N -lt 1000 ]]
do
echo "Step $N"
echo 'pf:documents()' | mclient -lxq > /dev/null
echo 'doc("aap.xml")' | mclient -lxq > /dev/null
N=$(($N + 1))
done
This script will execute fine (it returns an error for each document, can also be run many times):
N=0
while [[ $N -lt 1000 ]]
do
echo "Step $N"
echo 'pf:documents()' | mclient -lxq > /dev/null
echo 'doc("does_not_exist.xml")' | mclient -lxq > /dev/null
N=$(($N + 1))
done
perform the update:
do insert <beer/> into doc("aap.xml")/aap
now execute the above script again:
N=0
while [[ $N -lt 1000 ]]
do
echo "Step $N"
echo 'pf:documents()' | mclient -lxq > /dev/null
echo 'doc("does_not_exist.xml")' | mclient -lxq > /dev/null
N=$(($N + 1))
done
on my system this script 'hangs' on the 'pf:documents()' query after a few tries (between 10 and 250).
System: Fedora Core 8, 64bit, MonetDB 4.22 64bit-oids, Feb2008 supertarball.
## Comment 9203
Date: 2008-03-12 13:15:48 +0100
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
forgot to say: it doesn't happen with 4.20
## Comment 9204
Date: 2008-03-29 21:22:34 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
a recent checking in gdk_bbp.x (deadlock resolved) seems to solve this bug.
If you update MonetDB to the HEAD, I would expect the problem to disappear
## Comment 9205
Date: 2008-03-30 01:58:54 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
a recent checking in gdk_bbp.x (deadlock resolved) seems to solve this bug.
If you update MonetDB to the HEAD, I would expect the problem to disappear
## Comment 9206
Date: 2008-03-30 03:00:02 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
a recent checking in gdk_bbp.x (deadlock resolved) seems to solve this bug.
If you update MonetDB to the HEAD, I would expect the problem to disappear
## Comment 9207
Date: 2009-02-16 13:36:23 +0100
From: @drstmane
re-opened to remind us that we should consider adding a test
## Comment 9208
Date: 2009-07-31 10:03:06 +0200
From: @sjoerdmullender
Finally added test in pathfinder/tests/BugTracker: hang_non_existing_doc.SF-1911209.
## Comment 9209
Date: 2009-11-16 22:24:59 +0100
From: @drstmane
re-opened as the test fails since it has been added on 2009.08.01
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_BugTracker/hang_non_existing_doc.SF-1911209.out.00.html
## Comment 9210
Date: 2009-11-17 10:57:58 +0100
From: @drstmane
"fixed" by moving this test to be the second in this directory such that it runs on an empty DB and hence the output is identical as when run in isolation.
To be closed once nightly testing confirms the "fix".
## Comment 9211
Date: 2009-11-18 10:45:25 +0100
From: @drstmane
confirmed.
closing.
## Comment 9212
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1911209 at http://sourceforge.net/support/tracker.php?aid=1911209
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: MonetDB 'hangs' after requesting non-existing doc | https://api.github.com/repos/MonetDB/MonetDB/issues/1630/comments | 0 | 2020-11-30T09:49:55Z | 2024-06-27T11:29:20Z | https://github.com/MonetDB/MonetDB/issues/1630 | 753,325,565 | 1,630 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-09 11:26:39 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-03-21 09:53:58 +0100
## Comment 9198
Date: 2008-03-09 11:26:39 +0100
From: @romulogoncalves
If I create the following function:
CREATE FUNCTION fGetDiagChecksum()
RETURNS BIGINT
BEGIN
RETURN (select sum(count)+count(*) from tables);
END;
and then I drop it:
DROP FUNCTION fGetDiagChecksum;
I get:
MAPI = skyserver@localhost:50000
QUERY = DROP FUNCTION fGetDiagChecksum;
ERROR = !DROP FUNCTION: there are more than one function called 'fgetdiagchecksum', please use the full signature
This error message is not correct because there is only one function with this name. The functions can be dropped using only the name if there is not more functions with the same name, if there is, the full signature needs to be given. To drop all the functions with the same name we need to do
drop all <function_name>;
## Comment 9199
Date: 2008-03-14 14:05:12 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
this function is incorrect. I get
!SELECT: identifier 'count' unknown
## Comment 9200
Date: 2008-03-21 09:53:58 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
test added to BugTracker directory
## Comment 9201
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1910396 at http://sourceforge.net/support/tracker.php?aid=1910396
| drop function without arguments... | https://api.github.com/repos/MonetDB/MonetDB/issues/1629/comments | 0 | 2020-11-30T09:49:52Z | 2024-06-27T11:29:19Z | https://github.com/MonetDB/MonetDB/issues/1629 | 753,325,527 | 1,629 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-07 04:34:42 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-03-14 02:06:43 +0100
## Comment 9194
Date: 2008-03-07 16:34:42 +0100
From: @romulogoncalves
The following code:
CREATE FUNCTION fEq (ra float, decim float, r float)
RETURNS int
BEGIN
return 0;
END;
SELECT fEq(212.82496,1.27536,0.167);
SELECT fEq(134.44708,-0.2,0.167);
SELECT fEq(261,-90,0.167);
drop function fEq;
Gives the following error message:
MAPI = skyserver@localhost:50000
QUERY = SELECT fEq(261,-90,0.167);
ERROR = !SQLException:sql.prepare:wrong argument for prepared statement (expected decimal instead of tinyint)
## Comment 9195
Date: 2008-03-07 17:06:27 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
Test added in:
sql/src/test/BugTracker/Tests/sql_prepare_prob.SF-1909638.sql
## Comment 9196
Date: 2008-03-14 14:06:42 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
small problem in query matching. Some arguments checks weren't strict enough.
## Comment 9197
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1909638 at http://sourceforge.net/support/tracker.php?aid=1909638
| sql prepare problem.... | https://api.github.com/repos/MonetDB/MonetDB/issues/1628/comments | 0 | 2020-11-30T09:49:49Z | 2024-06-27T11:29:18Z | https://github.com/MonetDB/MonetDB/issues/1628 | 753,325,485 | 1,628 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-07 11:51:49 +0100
From: @sjoerdmullender
To: @mlkersten
Version: -- development
Last updated: 2008-03-07 12:46:02 +0100
## Comment 9191
Date: 2008-03-07 11:51:49 +0100
From: @sjoerdmullender
gcc -DHAVE_CONFIG_H -I. -I../.. -I/ufs/sjoerd/src/MonetDB/virgin/MonetDB5/src/mal -I/ufs/sjoerd/src/MonetDB/virgin/MonetDB5/src/mal -I../optimizer -I/ufs/sjoerd/src/MonetDB/virgin/MonetDB5/src/mal/../optimizer -I../scheduler -I/ufs/sjoerd/src/MonetDB/virgin/MonetDB5/src/mal/../scheduler -I../modules/kernel -I/ufs/sjoerd/src/MonetDB/virgin/MonetDB5/src/mal/../modules/kernel -I/ufs/sjoerd/Monet-virgin/include/MonetDB -I/ufs/sjoerd/Monet-virgin/include/MonetDB/common -I/ufs/sjoerd/Monet-virgin/include/MonetDB/gdk -DLIBMAL -Wall -Wextra -std=c99 -g -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2 -D_REENTRANT -c mal_recycle.c -fPIC -DPIC -o .libs/libmal_la-mal_recycle.o
/ufs/sjoerd/src/MonetDB/virgin/MonetDB5/src/mal/mal_recycle.mx: In function 'RECYCLEreuse':
/ufs/sjoerd/src/MonetDB/virgin/MonetDB5/src/mal/mal_recycle.mx:239: error: implicit declaration of function 'VALcmp'
I can't find any definition of VALcmp.
## Comment 9192
Date: 2008-03-07 12:46:01 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Committed the changes to MonetDB
## Comment 9193
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1909444 at http://sourceforge.net/support/tracker.php?aid=1909444
| M5 does not build | https://api.github.com/repos/MonetDB/MonetDB/issues/1627/comments | 0 | 2020-11-30T09:49:46Z | 2024-06-28T07:36:59Z | https://github.com/MonetDB/MonetDB/issues/1627 | 753,325,458 | 1,627 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-06 04:25:53 +0100
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
CC: @sjoerdmullender
Duplicates: #1697
Last updated: 2010-07-09 15:43:26 +0200
## Comment 9185
Date: 2008-03-06 16:25:53 +0100
From: @drstmane
Both in the XQuery_0-22 release branch and the development head,
the following 4-way join query compiles fine with `pf -M`, but fails to compile with `pf -A`:
========
$ cat /tmp/dblp3.XQ
--------
let $d := doc('dblp.xml')
for $a1 in $d//article,
$a2 in $d//article,
$a3 in $d//article,
$a4 in $d//article
where
$a1/author/text() = $a2/author/text() and
$a2/author/text() = $a3/author/text() and
$a3/author/text() = $a4/author/text() and
$a1/journal/text() = 'ACM Trans. Database Syst.' and
$a2/journal/text() = 'Bioinformatics' and
$a3/journal/text() = 'IEEE Trans. Knowl. Data Eng.' and
$a4/journal/text() = 'Nucleic Acids Research'
return $a3
========
$ pf -M /tmp/dblp3.XQ | wc
--------
4804 19899 227036
========
$ pf -A /tmp/dblp3.XQ | wc
--------
fatal error: Mapping unique name to an original name failed.
halted in /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/pathfinder/compiler/algebra/algebra.c (PFalg_ori_name), line 916
0 0 0
========
A slightly simpler version seems to compile well --- the warnings with `pf -A` occur only in the XQuery_0-22 branch:
========
$ cat /tmp/dblp2.XQ
--------
let $d := doc('dblp.xml')
for $a1 in $d//article,
$a2 in $d//article,
$a3 in $d//article
where
$a1/author/text() = $a2/author/text() and
$a2/author/text() = $a3/author/text() and
$a1/journal/text() = 'ACM Trans. Database Syst.' and
$a2/journal/text() = 'Bioinformatics' and
$a3/journal/text() = 'IEEE Trans. Knowl. Data Eng.'
return $a3
========
$ pf -M /tmp/dblp2.XQ | wc
--------
3431 14222 158281
========
$ pf -A /tmp/dblp2.XQ | wc
--------
warning: variable a0000 stilled pinned once.
warning: variable a0001 stilled pinned once.
warning: variable a0002 stilled pinned once.
warning: variable a0003 stilled pinned once.
warning: variable a0004 stilled pinned once.
warning: variable a0005 stilled pinned once.
warning: variable a0006 stilled pinned once.
warning: variable a0007 stilled pinned once.
warning: variable a0008 stilled pinned once.
warning: variable a0009 stilled pinned once.
warning: variable a0010 stilled pinned once.
warning: variable a0011 stilled pinned once.
warning: variable a0012 stilled pinned once.
warning: variable a0013 stilled pinned once.
warning: variable a0014 stilled pinned once.
warning: variable a0015 stilled pinned once.
warning: variable a0016 stilled pinned once.
warning: variable a0017 stilled pinned once.
warning: variable a0018 stilled pinned once.
warning: variable a0019 stilled pinned once.
warning: variable a0020 stilled pinned once.
warning: variable a0021 stilled pinned once.
warning: variable a0022 stilled pinned once.
warning: variable a0023 stilled pinned once.
warning: variable a0024 stilled pinned once.
warning: variable a0025 stilled pinned once.
warning: variable a0026 stilled pinned once.
warning: variable a0027 stilled pinned once.
warning: variable a0028 stilled pinned once.
warning: variable a0029 stilled pinned once.
warning: variable a0030 stilled pinned once.
warning: variable a0031 stilled pinned once.
2619 9795 83777
========
## Comment 9186
Date: 2008-05-29 13:55:29 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
I added a core rewrite that resolves the problem reported here.
A better solution would be to get rid of the bit-encoded column names in the algebra (as in some situations we need more than 32 columns).
The variable pinning problem was solved already a while ago.
A test that also checks the correctness of the resulting plan still needs to be added.
## Comment 9187
Date: 2008-05-29 16:46:07 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Added simple compilation test in pathfinder/tests/BugTracker/Tests/multi-join_query_compile_error.SF-1908822.*
Seems to be working fine, now.
Test for the actual correctness of the generated plan(s) is still pending ...
## Comment 9188
Date: 2008-06-02 10:48:07 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
The solution did not work out as expected (see also https://sourceforge.net/tracker/index.php?func=detail&aid=1981491&group_id=56967&atid=482468). For some queries the rewrites are so good that we run out of bit-encoded column names. A complete overhaul of the optimization and property inference phases is needed here.
For the release I checked in a fallback solution that at least avoids errors.
For the head the resolution is pending.
## Comment 9189
Date: 2008-06-02 13:01:42 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
This bug report is superseded by
http://sourceforge.net/tracker/index.php?func=detail&aid=1981762&group_id=56967&atid=482468
Only the test for the actual correctness of the generated plan(s) is still pending
...
## Comment 9190
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1908822 at http://sourceforge.net/support/tracker.php?aid=1908822
## Comment 14342
Date: 2010-07-09 15:43:26 +0200
From: @sjoerdmullender
*** This bug has been marked as a duplicate of bug #1697 ***
| PFalg: fails to compile multi-join query | https://api.github.com/repos/MonetDB/MonetDB/issues/1626/comments | 0 | 2020-11-30T09:49:43Z | 2024-06-28T07:36:59Z | https://github.com/MonetDB/MonetDB/issues/1626 | 753,325,418 | 1,626 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-06 11:35:19 +0100
From: Wouter Alink <<alink>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-03-06 11:40:32 +0100
## Comment 9181
Date: 2008-03-06 11:35:19 +0100
From: Wouter Alink <<alink>>
The following query:
doc("aap.xml")//*[self::a or self::b]
returns:
!ERROR: Segmentation fault.
The Pathfinder compiler experienced an internal problem.
You may want to report this problem to the Pathfinder
development team (pathfinder@pathfinder-xquery.org).
When reporting problems, please attach your XQuery input,
as well as the following information:
Invocation: command line
Compilation stage: 18
We apologize for the inconvenience...
(using MonetDB-4.22.0)
## Comment 9182
Date: 2008-03-06 11:40:32 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Works fine with MPS:
$ echo 'doc("aap.xml")//*[self::a or self::b]' | pf -M > /tmp/M.mil
$ wc /tmp/M.mil
460 1880 19733 /tmp/M.mil
Works also "fine" with the latest CVS version in the XQuery_0-22 branch (that includes post-release bug fixes):
$ echo 'doc("aap.xml")//*[self::a or self::b]' | pf -A > /tmp/A.mil
fatal error: self step not implemented yet.
$ wc /tmp/A.mil
0 0 0 /tmp/A.mil
## Comment 9183
Date: 2008-03-06 22:34:44 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Forgot to mention:
The "step_self?" tests in pathfinder/tests/XQuery/Tests/ cover this bug report.
## Comment 9184
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1908645 at http://sourceforge.net/support/tracker.php?aid=1908645
| XQ: segfault on "self::a or self::b" | https://api.github.com/repos/MonetDB/MonetDB/issues/1625/comments | 0 | 2020-11-30T09:49:40Z | 2024-06-27T11:29:15Z | https://github.com/MonetDB/MonetDB/issues/1625 | 753,325,379 | 1,625 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-06 10:48:40 +0100
From: Wouter Alink <<alink>>
To: Manuel Mayr <<mayrm>>
Version: -- development
Last updated: 2008-03-11 09:40:11 +0100
## Comment 9169
Date: 2008-03-06 10:48:40 +0100
From: Wouter Alink <<alink>>
The following query:
doc("aap.xml")//*[@a and @b and (@c[. > 10] or d[.="noot"])]
returns:
fatal error: This should not happen: no equal columns found
when using "pf -A". It compiles fine using "pf -M".
(MonetDB-4.22.0 (Feb2008))
## Comment 9170
Date: 2008-03-06 10:54:55 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Assigned to Jan, the "PF/ALG dispatcher"
## Comment 9171
Date: 2008-03-06 11:39:18 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
This query works fine in the CVS head.
Assigned to Manuel as the error message was triggered in his part of the code (opt_algebra_cse.c)
## Comment 9172
Date: 2008-03-06 11:41:57 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
MonetDB4 -> Pathfinder
## Comment 9173
Date: 2008-03-06 11:44:10 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Seems to work fine with the latest CVS version of the XQuery_0-22 branch (that includes post-release bug fixes):
$ echo 'doc("aap.xml")//*[@a and @b and (@c[. > 10] or d[.="noot"])]' | pf -A > /tmp/A.mil
$ wc /tmp/A.mil
759 3117 26023 /tmp/A.mil
## Comment 9174
Date: 2008-03-06 21:36:03 +0100
From: Manuel Mayr <<mayrm>>
Logged In: YES
user_id=1629542
Originator: NO
Sorry for my late answer, but the db2 certification course is quite arduous :|
I wonder why the bug is still open. As far as I can see the query is working on the latest cvs version.
Is there some investigation required from my side?
Best regards, Manuel
## Comment 9175
Date: 2008-03-06 22:49:05 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Manuel,
if you agree that this one is already fixed, then no further investigation is required.
"We" (preferably Wouter and/or you --- I do it all the time ...) should just add a (simple) test and then close this bug report.
## Comment 9176
Date: 2008-03-10 17:51:21 +0100
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
I don't have the cvs checkout at the moment (I work with 'stable' releases most of the time), and it would take me hours to get it to compile again and run the tests before being able to checkin the test.
Manuel, if it would take you little time, would you mind checking in the query and stable output of the given query:
doc("aap.xml")//*[@a and @b and (@c[. > 10] or d[.="noot"])]
as a test somewhere, probably as 'tests/BugsViaSourgeforce/Tests/no_equal_colums.SF-1908622.xq'?
Thanks in advance,
Wouter
## Comment 9177
Date: 2008-03-11 09:40:11 +0100
From: Manuel Mayr <<mayrm>>
Logged In: YES
user_id=1629542
Originator: NO
I added the new test no_equal_colums.SF-1908622 to the BugsViaSourceforge directory.
Best regards,
Manuel
## Comment 9178
Date: 2008-03-11 10:36:49 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Manual,
Thank you very much for the test!
Just two suggestion for the next time:
1) Since the bug was reported and "fixed" in the Stable release branch, the test should also (have) go(ne) there.
2) pathfinder/tests/BugsViaSourgeforce/Tests/All says
"
tests related to bug reports
should no longer be added here,
but rather in
../../BugTracker/Tests/
i.e.
.../pathfinder/tests/BugTracker/Tests/
"
Stefan
## Comment 9179
Date: 2008-03-11 19:59:53 +0100
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
sorry, i guess that's my fault. but Manuel, thanks very much anyway!
## Comment 9180
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1908622 at http://sourceforge.net/support/tracker.php?aid=1908622
| XQ: (algebra) no equal columns found | https://api.github.com/repos/MonetDB/MonetDB/issues/1624/comments | 0 | 2020-11-30T09:49:37Z | 2024-06-27T11:29:14Z | https://github.com/MonetDB/MonetDB/issues/1624 | 753,325,351 | 1,624 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-06 09:45:54 +0100
From: @sjoerdmullender
To: @mlkersten
Version: -- development
Last updated: 2008-04-15 05:15:33 +0200
## Comment 9163
Date: 2008-03-06 09:45:54 +0100
From: @sjoerdmullender
How long before it gets noticed?
M5 does not build on Windows, so all dependent projects also don't build.
You cannot have libraries that don't contain source.
## Comment 9164
Date: 2008-03-06 11:29:52 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
it was noticed, but no clue how to solve it by me.
## Comment 9165
Date: 2008-03-06 12:10:23 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: NO
Why you do not move the content of
sr/mal/mal_recycler.mx into modules/mal/recycler.mx ?
Why you declare the mal command in recycler.mx and all the functions called by that commands in mal_recycler,mx?
remote.mx is one example where everything is in one place...
Just my half cent opinion...
Romulo
## Comment 9166
Date: 2008-03-06 12:23:58 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
The core routines RECYCLE{entry,exit,new
all are directly used by the interpreter.
Only the admin stuff could be moved to modules/mal
## Comment 9167
Date: 2008-04-15 17:15:33 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: YES
It compiles now, so closing.
No test needed.
## Comment 9168
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1908591 at http://sourceforge.net/support/tracker.php?aid=1908591
| M5 does not build on Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/1623/comments | 0 | 2020-11-30T09:49:34Z | 2024-06-27T11:29:13Z | https://github.com/MonetDB/MonetDB/issues/1623 | 753,325,309 | 1,623 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-05 01:00:50 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-03-09 12:27:48 +0100
## Comment 9160
Date: 2008-03-05 13:00:50 +0100
From: @romulogoncalves
The following sql code crash mserver...
CREATE TABLE syscolumns(
id int,
length int,
uid int,
nme char(100),
xtype char(100)
);
CREATE TABLE spt_datatype_info(
length int,
ss_dtype varchar(100),
"AUTO_INCREMENT" varchar(100)
);
CREATE FUNCTION fDocColumnsWithRank(TableName varchar(400))
RETURNS float
BEGIN
return table ( SELECT
c.nme as nme
FROM
spt_datatype_info d,
syscolumns c
WHERE
coalesce(d."AUTO_INCREMENT",0) =
coalesce(ColumnProperty (c.id, c.nme, 'IsIdentity'),0) );
END;
Romulo
## Comment 9161
Date: 2008-03-09 00:27:48 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
Fixed :
[Monetdb-sql-checkins] sql/src/server sql_psm.mx, SQL_2-22, 1.50, 1.50.2.1 sql_select.mx, SQL_2-22, 1.219.2.5, 1.219.2.6
Modified Files:
Tag: SQL_2-22
sql_psm.mx sql_select.mx
Log Message:
fixes for the bugs
[ 1907905 ] coalesce = coalesce...
(added some more checks for semantic problems)
and
[ 1907006 ] range select....
Properly interpret 0<id>10 as a boolean (0<id) followed by the selection criteria (bool > 10).
test added in:
sql/src/test/BugTracker/Tests/coalesce_equal_coalesce.SF-1907905.sql
## Comment 9162
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1907905 at http://sourceforge.net/support/tracker.php?aid=1907905
| coalesce = coalesce... | https://api.github.com/repos/MonetDB/MonetDB/issues/1622/comments | 0 | 2020-11-30T09:49:31Z | 2024-06-27T11:29:12Z | https://github.com/MonetDB/MonetDB/issues/1622 | 753,325,265 | 1,622 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-05 11:41:30 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-03-07 05:10:14 +0100
## Comment 9157
Date: 2008-03-05 11:41:30 +0100
From: @romulogoncalves
The following sql function crashes mserver 5
CREATE FUNCTION fR(x float, types float)
RETURNS float
BEGIN
DECLARE TABLE typesTable(
type varchar(16)
);
INSERT into typesTable (type) values ('asdasd');
DECLARE TABLE region(
regionid bigint,
type varchar(16)
);
Return x;
END;
Romulo
## Comment 9158
Date: 2008-03-07 17:10:14 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
Bug fixed with check in:
[Monetdb-sql-checkins] sql/src/server sql_mvc.mx, SQL_2-22, 1.195.2.1, 1.195.2.2
Modified Files:
Tag: SQL_2-22
sql_mvc.mx
Log Message:
fixed bug [ 1907858 ] declaration of the second table in the function body
cased columns sometimes have no schema defined (declared tables). So we
cannot reuse the schema from it.
and test added in:
sql/src/test/BugTracker/Tests/decl_sec_tab_in_func_body.SF-1907858
## Comment 9159
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1907858 at http://sourceforge.net/support/tracker.php?aid=1907858
| declaration of the second table in the function body | https://api.github.com/repos/MonetDB/MonetDB/issues/1621/comments | 0 | 2020-11-30T09:49:28Z | 2024-06-27T11:29:11Z | https://github.com/MonetDB/MonetDB/issues/1621 | 753,325,220 | 1,621 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-05 11:00:04 +0100
From: @grobian
To: @sjoerdmullender
Version: -- development
Last updated: 2008-05-14 02:45:14 +0200
## Comment 9153
Date: 2008-03-05 11:00:04 +0100
From: @grobian
Currently, the building on Darwin (Mac OS X) forces the use of a flat namespace. This is a side-effect of the also issued -undefined suppress, which causes the linker not to complain about undefined symbols that it encounters. Since this is the default on GNU binutils (say, Linux), this flag is enabled by default.
Two-Level Namespaces
It's possible for more than one library to have a symbol of the same name. In early Mac OS X releases (before 10.1), there was a conflict if more than one library exported a particular name. Since the release of 10.1, Mac OS X has supported "two level" object files. These object files use both the source library (a "namespace") and the name of the symbol for dynamic references, thus eliminating the possibility of conflicts. Since Mac OS X 10.2, two level namespaces have been the default.
Note that this problem is still present in other dynamic linkers and flat namespaced programming languages (C, in particular), so most portable software attempts to workaround this deficiency at a higher level than the linker by manging the symbol names. In any case, two-level namespaces are highly recommended, as flat namespaces do NOT behave identially to the flat namespaces of other popular linkers. Most importantly: the first definition of a symbol is used, rather than the last, which can cause serious problems with plugin loading.
For this reason, I argue that on Darwin we should build for a 2-level namespace, and just deal with the missing symbols, which the linker finds. In the end they are serious problems anyway. Compiling the current code with -no-undefined in LDFLAGS (for libtool) results in this behaviour and builds 2-level namespace libraries without problems in our own code. This means we're doing fine. The only problem I found, is in php. At the linking there it looks as if -lphp is missing, causing the linker to complain about around 30 missing _php symbols.
I made this a bug, because I don't know what is the best way to inject -no-undefined in the LDFLAGS throughout the autotools process.
A few notes:
- on GNU binutils (Linux) "-no-undefined" does nothing, because on that plaform there simply doesn't exist a mode that checks symbols
- "-no-undefined" is not just some sort of 'strictness', when not defined, libtool just forces some last resort 'ignore this' flags onto the linker. Note that this can cause kernel traps during runtime if symbols are missing.
- the 2-level namespace is the default on Mac OS X
## Comment 9154
Date: 2008-03-05 11:06:35 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
another note:
- I realise that this is sort of deviating from libtool's default, so I could settle with a decision where "-no-undefined" is only used in --enable-strict
## Comment 9155
Date: 2008-05-14 14:45:14 +0200
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
this is a libtool default, so let's forget about it.
## Comment 9156
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1907829 at http://sourceforge.net/support/tracker.php?aid=1907829
| Building on Darwin should use 2-level namespace | https://api.github.com/repos/MonetDB/MonetDB/issues/1620/comments | 0 | 2020-11-30T09:49:25Z | 2024-06-28T13:30:04Z | https://github.com/MonetDB/MonetDB/issues/1620 | 753,325,181 | 1,620 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-04 03:59:05 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-03-09 12:20:47 +0100
## Comment 9150
Date: 2008-03-04 15:59:05 +0100
From: @romulogoncalves
First you need to load the files in
sql/src/sql:
math.sql and ms_functions.sql
then run this query:
sql>select ms_round(60.0 * (0.1-1),1,1);
!TypeException:user.ms_round[9]:'sql.round' undefined in: _13:any := sql.round(_10:dbl, _12:bte)
!TypeException:user.s0_1[22]:'sql.round' undefined in: _58:any := sql.round(_55:dbl, _57:bte)
!SQLException:dbl:conversion of string '-' failed
sql>
Romulo
## Comment 9151
Date: 2008-03-09 00:20:46 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
Fixed:
[Monetdb-sql-checkins] sql/src/backends/monet4 sql_server.mx, SQL_2-22, 1.189.2.5, 1.189.2.6
Modified Files:
Tag: SQL_2-22
sql_server.mx
Log Message:
fixed bug [ 1907063 ] ms_round....
The round function for dbl, bte was missing
Test added in:
sql/src/test/BugTracker/Tests/ms_round.SF-1907063.sql
## Comment 9152
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1907063 at http://sourceforge.net/support/tracker.php?aid=1907063
| ms_round.... | https://api.github.com/repos/MonetDB/MonetDB/issues/1619/comments | 0 | 2020-11-30T09:49:22Z | 2024-06-27T11:29:09Z | https://github.com/MonetDB/MonetDB/issues/1619 | 753,325,145 | 1,619 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-04 03:52:02 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-03-09 12:23:21 +0100
## Comment 9147
Date: 2008-03-04 15:52:02 +0100
From: @romulogoncalves
The following statements show the problem:
>create table t2 (id float);
>create table t1 (age float);
>select age from t1, t2 where id < 0.0 limit 10;
!TypeException:user.s0_0[29]:'algebra.join' undefined in: _42:any := algebra.join(_22:bat[:oid,:dbl], _41:bat[:oid,:oid])
!TypeException:user.s0_0[31]:'algebra.markT' undefined in: _45:any := algebra.markT(_42:any, _43:oid)
!TypeException:user.s0_0[32]:'bat.reverse' undefined in: _46:any := bat.reverse(_45:any)
!TypeException:user.s0_0[33]:'algebra.join' undefined in: _47:any := algebra.join(_46:any, _16:bat[:oid,:dbl])
&1 4 1 1 1
% sys.t1 table_name
% age name
% double type
% 22 length
[ 747 ]
>
Romulo
## Comment 9148
Date: 2008-03-09 00:23:21 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
Fixed:
[Monetdb-sql-checkins] sql/src/server sql_mvc.mx, SQL_2-22, 1.195.2.1, 1.195.2.2
Modified Files:
Tag: SQL_2-22
sql_mvc.mx
Log Message:
fixed bug [ 1907858 ] declaration of the second table in the function body
cased columns sometimes have no schema defined (declared tables). So we
cannot reuse the schema from it.
test added in:
sql/src/test/BugTracker/Tests/join_table_with_floats.SF-1907060.sql
## Comment 9149
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1907060 at http://sourceforge.net/support/tracker.php?aid=1907060
| join tables with floats... | https://api.github.com/repos/MonetDB/MonetDB/issues/1618/comments | 0 | 2020-11-30T09:49:19Z | 2024-06-27T11:29:08Z | https://github.com/MonetDB/MonetDB/issues/1618 | 753,325,112 | 1,618 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-04 03:44:01 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-03-09 12:25:28 +0100
## Comment 9144
Date: 2008-03-04 15:44:01 +0100
From: @romulogoncalves
The following sql statement gives a MAL exception:
>select name from tables where name LIKE '%????%';
!MALException:pcre_uselect:pcre compile of pattern (^.*????.*$) failed at 4 with
!'nothing to repeat'.
>
Romulo
## Comment 9145
Date: 2008-03-09 00:25:28 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
Fixed:
[Monetdb-checkins] MonetDB5/src/modules/mal pcre.mx, MonetDB_5-4, 1.53, 1.53.2.1
Modified Files:
Tag: MonetDB_5-4
pcre.mx
Log Message:
fixed bug [ 1907051 ] like '%????%'
need to escape the ? in patterns
test added in:
sql/src/test/BUgTracker/Tests/like_perl.SF-1907051.sql
## Comment 9146
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1907051 at http://sourceforge.net/support/tracker.php?aid=1907051
| like '%????%' | https://api.github.com/repos/MonetDB/MonetDB/issues/1617/comments | 0 | 2020-11-30T09:49:16Z | 2024-06-27T11:29:07Z | https://github.com/MonetDB/MonetDB/issues/1617 | 753,325,078 | 1,617 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-04 03:37:39 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-06-02 12:46:25 +0200
## Comment 9140
Date: 2008-03-04 15:37:39 +0100
From: @romulogoncalves
The following sql statements crash the mserver:
sql>create table t1 (z real);
sql>create table t2 (name string, dered_g real, dered_r real);
sql>SELECT p.name FROM t1 as s, t2 as p WHERE (-0.399*(dered_g-4.79*LOG10(s.z/0.03)-3.65*(dered_g-dered_r)-39.55))> 10.7 LIMIT 100000;
>[New Thread 1107310928 (LWP 15947)]
mserver5: /ufs/goncalve/MonetDB/sql/src/server/sql_scope.mx:229: find_pivot: Assertion `0' failed.
Program received signal SIGABRT, Aborted.
[Switching to Thread 1107310928 (LWP 15947)]
0x0000003c4bc30ec5 in raise () from /lib64/libc.so.6
(gdb)
Romulo
## Comment 9141
Date: 2008-06-01 21:49:43 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Update:
The problem seems to persist with the default SQL compiler on both M4 & M5:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests4103/GNU.64.64.d-Fedora8/src_test_BugTracker/huge_math_expre.SF-1907048.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests5103/GNU.64.64.d-Fedora8/src_test_BugTracker/huge_math_expre.SF-1907048.err.00.html
However, it seems to be solved with the new (not yet default) algebra-based SQL compiler:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTestsG103/GNU.64.64.d-Fedora8/src_test_BugTracker/huge_math_expre.SF-1907048.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTestsG103/GNU.64.64.d-Fedora8/src_test_BugTracker/huge_math_expre.SF-1907048.err.00.html
## Comment 9142
Date: 2008-06-02 12:46:25 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
now also the default SQL compiler works, ie closing.
## Comment 9143
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1907048 at http://sourceforge.net/support/tracker.php?aid=1907048
| a huge mathematical expression... | https://api.github.com/repos/MonetDB/MonetDB/issues/1616/comments | 0 | 2020-11-30T09:49:13Z | 2024-06-27T11:29:06Z | https://github.com/MonetDB/MonetDB/issues/1616 | 753,325,038 | 1,616 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-04 02:29:03 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-03-14 01:58:14 +0100
## Comment 9135
Date: 2008-03-04 14:29:03 +0100
From: @romulogoncalves
The following query is syntatically incorrect:
>select name from tables where 0<id>10;
!TypeException:user.s0_0[45]:'algebra.uselect' undefined in: _62:any := algebra.uselect(_59:bat[:oid,:oid], _61:int, _60:int, _48:bit, _48:bit)
!TypeException:user.s0_0[47]:'algebra.markT' undefined in: _64:any := algebra.markT(_62:any, _63:oid)
!TypeException:user.s0_0[48]:'bat.reverse' undefined in: _65:any := bat.reverse(_64:any)
!TypeException:user.s0_0[61]:'algebra.join' undefined in: _86:any := algebra.join(_65:any, _85:bat[:oid,:str])
&1 0 1 1 1
% sys.tables table_name
% name name
% varchar type
% 2 length
[ 725 ]
>
Romulo
## Comment 9136
Date: 2008-03-04 14:40:49 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: NO
The output is protocol-wise a violation as well. (Our transaction semantics define that even in a multi-statement query this cannot happen.)
## Comment 9137
Date: 2008-03-09 00:29:27 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
Fixed:
[Monetdb-sql-checkins] sql/src/server sql_psm.mx, SQL_2-22, 1.50, 1.50.2.1 sql_select.mx, SQL_2-22, 1.219.2.5, 1.219.2.6
Modified Files:
Tag: SQL_2-22
sql_psm.mx sql_select.mx
Log Message:
fixes for the bugs
[ 1907905 ] coalesce = coalesce...
(added some more checks for semantic problems)
and
[ 1907006 ] range select....
Properly interpret 0<id>10 as a boolean (0<id) followed by the selection criteria (bool > 10).
test added in:
sql/src/test/BugTracker/Tests/range_select.SF-1907006.sql
## Comment 9138
Date: 2008-03-09 00:33:18 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
The bug needs to be re-open...
In the after a test run I get this error messages...
ERROR = !TypeException:user.s0_1[45]:'algebra.uselect' undefined in: _62:any := algebra.uselect(_59:bat[:oid,:oid], _61:int, _60:int, _48:bit, _48:bit)
!TypeException:user.s0_1[47]:'algebra.markT' undefined in: _64:any := algebra.markT(_62:any, _63:oid)
!TypeException:user.s0_1[48]:'bat.reverse' undefined in: _65:any := bat.reverse(_64:any)
!TypeException:user.s0_1[61]:'algebra.join' undefined in: _86:any := algebra.join(_65:any, _85:bat[:oid,:str])
## Comment 9139
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1907006 at http://sourceforge.net/support/tracker.php?aid=1907006
| range select.... | https://api.github.com/repos/MonetDB/MonetDB/issues/1615/comments | 0 | 2020-11-30T09:49:10Z | 2024-06-27T11:29:05Z | https://github.com/MonetDB/MonetDB/issues/1615 | 753,324,998 | 1,615 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-03 03:27:54 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-05-28 11:55:25 +0200
## Comment 9130
Date: 2008-03-03 15:27:54 +0100
From: @romulogoncalves
If I start my mserver (M5-SQL) with the option --set sql_debug=64
and I create the following user and I set his default schema:
CREATE USER "skyserver" WITH PASSWORD 'skyserver' NAME 'sky server' SCHEMA "sys";
create schema "sky" authorization "skyserver";
alter user "skyserver" set schema "sky";
If I restarted my mserver and then I queried the users table. I saw that the default schema for user skyserver is again sys.
I think this is related with the load of the catalog. If I create a database with -set sql_debug=64 and then I restart the mserver without the option -set sql_debug=64 the mserver crash:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912518363936 (LWP 30327)]
0x00002aaabe4c1040 in temp_create (b=0x0) at /ufs/goncalve/MonetDB/sql/src/storage/bat/bat_utils.mx:133
133 temp_dup(b->batCacheid);
(gdb) up
1 0x00002aaabe4be5c9 in load_bat (sname=0xdad7c8 "sys", tname=0xdad9b8 "schemas", bname=0xdadad8 "id", type=6, sz=1024, cnt=0xdad900)
at /ufs/goncalve/MonetDB/sql/src/storage/bat/bat_storage.mx:449
449 bat->ubid = temp_create(b);
(gdb) up
2 0x00002aaabe4be94c in create_col (tr=0xdad688, c=0xdada68) at /ufs/goncalve/MonetDB/sql/src/storage/bat/bat_storage.mx:515
515 c->data = load_bat( c->t->s->base.name, c->t->base.name, c->base.name, type, c->t->sz, &c->t->cnt);
(gdb) up
3 0x00002aaabe4b0f67 in bootstrap_create_column (tr=0xdad688, t=0xdad8c8, name=0x2aaabe4f670f "id", sqltype=0x2aaabe4f6a1a "int", digi1970-01-01 01:00:32 +0100)
at /ufs/goncalve/MonetDB/sql/src/storage/store.mx:1076
1076 store_funcs.create_col(tr, col);
(gdb) up
4 0x00002aaabe4b1632 in store_init (debug=0, store=store_bat, logdir=0x62be40 "/ufs/goncalve/scratch/skyserver/", dbname=0x62be30 "demo", stk=0)
at /ufs/goncalve/MonetDB/sql/src/storage/store.mx:1214
1214 bootstrap_create_column(tr, t, "id", "int", 32);
(gdb)
Regards,
Romulo
## Comment 9131
Date: 2008-05-26 14:49:35 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
A mserver using the flag sql_debug=64 is a mserver for a single client connection, so in this case the update bat is not used/created.
If we start the mserver in this mode with empty database and execute the previous sql code, the update bat will not be created. Once we re-start the mserver for multi-client connections, where the schema table has modifications, the load of the update bat will fail because it does not exist.
To fix this I propose the following fix:
[goncalve@alviss bat]$ cvs diff bat_storage.mx
Index: bat_storage.mx
===================================================================
RCS file: /cvsroot/monetdb/sql/src/storage/bat/bat_storage.mx,v
retrieving revision 1.16
diff -u -r1.16 bat_storage.mx
--- bat_storage.mx 23 May 2008 08:02:38 -0000 1.16
+++ bat_storage.mx 26 May 2008 12:42:45 -0000
@@ -449,6 +449,8 @@
bat->uname = sql_message("U_%s", bat->name);
b = quick_descriptor(logger_find_bat(bat_logger, bat->uname));
+ if (!b)
+ b = bat_new(TYPE_oid, type, sz);
bat->ubid = temp_create(b);
bat->ibid = e_bat(type);
[goncalve@alviss bat]$
If the update bat does not exist just create it.
Niels do you agree? Ff yes I close the bug, create test, and check in it in the stable branch....
Regards,
Romulo
## Comment 9132
Date: 2008-05-26 16:16:00 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Originator: YES
The test for this bug was checked in at stable branch:
sql/src/test/BugTracker/Tests/set_sql_debug_64__breaking_the_DB.SF-1906287.py
plus the additional files:
set_sql_debug_64__breaking_the_DB.SF-1906287_create.sql
set_sql_debug_64__breaking_the_DB.SF-1906287_drop.sql
## Comment 9133
Date: 2008-05-28 11:55:25 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
The test succeeds now. The default (delta) storage now adds the needed update bats on load of the single user storage, which doesn't have update bats.
## Comment 9134
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1906287 at http://sourceforge.net/support/tracker.php?aid=1906287
| --set sql_debug=64 is breaking the DB... | https://api.github.com/repos/MonetDB/MonetDB/issues/1614/comments | 0 | 2020-11-30T09:49:07Z | 2024-06-27T11:29:04Z | https://github.com/MonetDB/MonetDB/issues/1614 | 753,324,961 | 1,614 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-03 12:10:55 +0100
From: @yzchang
To: @yzchang
Version: -- development
Last updated: 2008-05-16 03:16:34 +0200
## Comment 9125
Date: 2008-03-03 00:10:55 +0100
From: @yzchang
I declared two functions in a module with the same name, but one has 2 parameters and the other one has 7 parameters. When compiling my query, pf is not able to find the function signature with 7 parameters:
$ pf /tmp/tst.xq
error in function application: wrong number of arguments for function `f:comparenodes' (expected 2, got 7)
halted in /ufs/zhang/monet/dev/pathfinder/compiler/core/core.c (PFcore_apply), line 1345
The query and the module are the following:
$ cat /tmp/tst.xq
import module namespace tst = "foo" at "/tmp/foo.xq";
for $i in ("localhost", "andorea")
let $d := doc("proj1.xml"),
$u := $d//i,
$r := $d//k,
$used := $u,
$returned := $r,
$referred := ($u, $r),
$upath := ("./title", "./year"),
$rpath := ("./address", "./publisher")
return
tst:comparenodes( $used, $returned, $referred, $upath, $rpath, $u, $r)
$ cat /tmp/foo.xq
module namespace f = "foo";
declare function f:comparenodes(
$used as node()*, $returned as node()*, $referred as node()*,
$upath as xs:string*, $rpath as xs:string*,
$u as node()*, $r as node()* ) as node()*
{ f:comparenodes($u, $r) };
declare function f:comparenodes($u as node()*, $r as node()*) as node()*
{
for $i in $u, $j in $r
where $i is $j
return $j
};
However, if I switch the order these two functions are declared, the same query /tmp/tst.xq can be compiled:
$ cat /tmp/foo.xq
module namespace f = "foo";
declare function f:comparenodes($u as node()*, $r as node()*) as node()*
{
for $i in $u, $j in $r
where $i is $j
return $j
};
declare function f:comparenodes(
$used as node()*, $returned as node()*, $referred as node()*,
$upath as xs:string*, $rpath as xs:string*,
$u as node()*, $r as node()* ) as node()*
{ f:comparenodes($u, $r) };
$ pf /tmp/tst.xq
.... generated mil code
Jennie
## Comment 9126
Date: 2008-04-22 13:26:44 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Jan, can you comment on this?
## Comment 9127
Date: 2008-04-23 10:15:30 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
This is now fixed in the stable branch.
Jennie could you please verify and add the respective test.
## Comment 9128
Date: 2008-05-16 15:16:34 +0200
From: @yzchang
Logged In: YES
user_id=341633
Originator: YES
Test added in tests/BugTracker/Tests/order_of_declared_functions_matters, and it's green in the testweb.
## Comment 9129
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1905940 at http://sourceforge.net/support/tracker.php?aid=1905940
| PF: order of declared functions matters? | https://api.github.com/repos/MonetDB/MonetDB/issues/1613/comments | 0 | 2020-11-30T09:49:04Z | 2024-06-27T11:29:03Z | https://github.com/MonetDB/MonetDB/issues/1613 | 753,324,920 | 1,613 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-02 04:53:19 +0100
From: @yzchang
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2008-03-02 09:57:46 +0100
## Comment 9121
Date: 2008-03-02 16:53:19 +0100
From: @yzchang
Hi,
When compiling my query (see below), I get a parse error "stack empty". This happens with both stable and current branch.
$ pf /tmp/tst.xq
parse error: parsing problem: stack empty
halted in /ufs/zhang/monet/current/pathfinder/compiler/parser/scanner.l (popState), line 232
$ cat /tmp/tst.xq
import module namespace tst = "foo" at "/tmp/foo.xq";
for $i in ("abc", "xyz")
let $d := doc("proj.xml"),
$u := $d//i,
$r := $d//k,
$used := $u,
$returned := $r,
$referred := $u,
$upath := ("./title", "./year"),
$rpath := ("./address", "./publisher")
return
tst:comparenodes( $used, $returned, $referred, $upath, $rpath, $u, $r) }
$ cat /tmp/foo.xq
module namespace f = "foo";
declare function f:comparenodes($u as node()*, $r as node()*) as node()*
{
for $i in $u, $j in $r
where $i is $j
return $j
};
declare function f:comparenodes(
$used as node()*, $returned as node()*, $referred as node()*,
$upath as xs:string*, $rpath as xs:string*,
$u as node()*, $r as node()* ) as node()*
{ f:comparenodes($u, $r) };
Compiling /tmp/foo.xq does not have any problem. I'm using:
$ uname -a
Linux andorea.ins.cwi.nl 2.6.23.15-137.fc8 1 SMP Sun Feb 10 17:03:13 EST 2008 x86_64 x86_64 x86_64 GNU/Linux
Thanks!
Jennie
## Comment 9122
Date: 2008-03-02 17:32:31 +0100
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Originator: NO
Note that your query contains a syntax error. The `}' at
the end is too much. But I agree the Pathfinder's parser
should report this differently.
## Comment 9123
Date: 2008-03-02 21:57:46 +0100
From: @yzchang
Logged In: YES
user_id=341633
Originator: YES
The bug is invalid, sorry.
Thanks Jens.
## Comment 9124
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1905745 at http://sourceforge.net/support/tracker.php?aid=1905745
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: parsing problem: stack empty | https://api.github.com/repos/MonetDB/MonetDB/issues/1612/comments | 0 | 2020-11-30T09:49:01Z | 2024-06-28T13:30:03Z | https://github.com/MonetDB/MonetDB/issues/1612 | 753,324,891 | 1,612 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-03-01 10:17:27 +0100
From: mobigital <<mobigital>>
To: @njnes
Version: -- development
Last updated: 2008-08-02 07:16:27 +0200
## Comment 9115
Date: 2008-03-01 22:17:27 +0100
From: mobigital <<mobigital>>
Compiled with DEBUG on windows 2003 64 bit Enterprise edition.
I was importing records with COPY TO a staging table in batches of 250K rows. Then copying them into final table.
After completing 4,750,000 rows and importing a new batch the below exception occurs in GDKreallocmax at the last line of the snippet below:
Can someone point me in the right direction on how to debug this?
[from gdk_utils.mx]
ptr
GDKreallocmax(void *blk, size_t size, size_t * maxsize, int emergency)
{
ssize_t oldsize = 0, *s = (ssize_t *) blk;
if (s == NULL) {
return GDKmallocmax(size, maxsize, emergency);
}
ifdef GDK_MEM_NULLALLOWED
if (size == 0) {
GDKfree(blk);
*maxsize = 0;
return NULL;
}
endif
if (size <= 0) {
GDKfatal("GDKreallocmax: called with size %u", size);
}
size = (size + 7) & ~7; /* round up to a multiple of eight */
>>> exception occurs below >>>>>>
oldsize = GDK_MEM_BLKSIZE(s);
("s"=0x00000000100e0000)
Unhandled exception at 0x00c4c7b2 (libbat.dll) in mserver5.exe: 0xC0000005: Access violation reading location 0x00000000100dfff8.
libbat.dll!GDKreallocmax(void * blk=0x00000000100e0000, unsigned __int64 size=211952, unsigned __int64 * maxsize=0x000000000bc41c28, int emergency=0) Line 1164 + 0x5 bytes C
libbat.dll!HEAPextend(Heap * h=0x000000000bc41c28, unsigned __int64 size=211947) Line 205 + 0x24 bytes C
libbat.dll!strPut(Heap * h=0x000000000bc41c28, unsigned int * dst=0x0000000106666ffc, char * v=0x000000001d4852a8) Line 2060 + 0x12 bytes C
libbat.dll!BATappend(BAT * b=0x000000000e106968, BAT * n=0x000000000e3183a8, char force='') Line 353 + 0x58c bytes C
lib_sql.dll!tr_update_bat(sql_trans * tr=0x0000000008b57da8, sql_delta * obat=0x000000000c4974d8, sql_delta * cbat=0x000000000c482a18, __int64 * cnt=0x0000000008cb54d0) Line 909 C
lib_sql.dll!update_table(sql_trans * tr=0x0000000008b57da8, sql_table * ft=0x0000000008cb5498, sql_table * tt=0x0000000008cb55c8) Line 1001 C
lib_sql.dll!rollforward_update_table(sql_trans * tr=0x0000000008b57da8, sql_table * ft=0x0000000008cb5498, sql_table * tt=0x0000000008cb55c8) Line 2210 + 0x18 bytes C
lib_sql.dll!rollforward_changeset_updates(sql_trans * tr=0x0000000008b57da8, changeset * fs=0x00000000016611e8, changeset * 1970-01-01 01:00:00 +0100x00000000016610d8, sql_base * b=0x00000000016610b8, int (sql_trans *, sql_base *, sql_base *)* rollforward_updates=0x000000000b561cd0, sql_base * (sql_trans *, sql_base *)* rollforward_creates=0x000000000b561770, int (sql_trans *, sql_base *)* rollforward_deletes=0x000000000b5612b0, sql_base * (sql_trans *, int, sql_base *, sql_base *)* fd=0x000000000b562050) Line 1919 + 0x19 bytes C
lib_sql.dll!rollforward_update_schema(sql_trans * tr=0x0000000008b57da8, sql_schema * fs=0x00000000016611c8, sql_schema * 1970-01-01 01:00:00 +0100x00000000016610b8) Line 2278 + 0x57 bytes C
lib_sql.dll!rollforward_changeset_updates(sql_trans * tr=0x0000000008b57da8, changeset * fs=0x0000000008b57dd8, changeset * 1970-01-01 01:00:00 +0100x0000000008b57d28, sql_base * b=0x0000000008b57cf8, int (sql_trans *, sql_base *, sql_base *)* rollforward_updates=0x000000000b5619b0, sql_base * (sql_trans *, sql_base *)* rollforward_creates=0x000000000b561640, int (sql_trans *, sql_base *)* rollforward_deletes=0x000000000b5610d0, sql_base * (sql_trans *, int, sql_base *, sql_base *)* fd=0x000000000b55edc0) Line 1919 + 0x19 bytes C
lib_sql.dll!rollforward_trans(sql_trans * tr=0x0000000008b57da8) Line 2300 + 0x59 bytes C
lib_sql.dll!sql_trans_commit(sql_trans * tr=0x0000000008b57da8) Line 2658 + 0xa bytes C
lib_sql.dll!mvc_commit(mvc * m=0x0000000008e8e768, int chain=0, char * name=0x0000000000000000) Line 414 + 0xa bytes C
lib_sql.dll!SQLautocommit(CLIENT * c=0x00000001800919e8, mvc * m=0x0000000008e8e768) Line 694 + 0xf bytes C
lib_sql.dll!SQLreader(CLIENT * c=0x00000001800919e8) Line 751 + 0xf bytes C
libmal.dll!runPhase(CLIENT * c=0x00000001800919e8, int phase=0) Line 590 + 0x16 bytes C
libmal.dll!runScenarioBody(CLIENT * c=0x00000001800919e8) Line 612 + 0x1d bytes C
libmal.dll!runScenario(CLIENT * c=0x00000001800919e8) Line 653 + 0xa bytes C
libmal.dll!MSserveClient(void * dummy=0x00000001800919e8) Line 473 C
pthreadVC2d.dll!ptw32_threadStart(void * vthreadParms=0x000000000b8ec7a0) Line 219 + 0x9 bytes C
msvcr90d.dll!_callthreadstartex() Line 348 + 0x17 bytes C
msvcr90d.dll!_threadstartex(void * ptd=0x00000000015c3fa0) Line 331 C
kernel32.dll!0000000077d6b6da()
[Frames below may be incorrect and/or missing, no symbols loaded for kernel32.dll]
## Comment 9116
Date: 2008-03-02 22:54:11 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
this appears to be a memory management bug; like if memory that is allocated in memory mapped mode (hp->storage & STORE_MMAP) would be extended as if it were mallocced (hp->storage == STORE_MEM)
I say this because malloced memory in MonetDB is always preceded by 8 extra bytes that store the block size (GDKmalloc returns pointer+8). So the address being perfectly 0000 aligned (and -8 being fff8) is possible,but not likely. More likely is that the 0000 aligned address was produced by a memory map (GDKmmap).
If the problem was reproducable, I would try to break on the HEAPextend calls for this heap (set a conditional to h=0x000000000bc41c28 -- if it is reproducable) and figure out what the storage modes are (mmap or malloc before and after allocation). The relatively small size of the heap (211KB) makes me think it should be ony malloced..
In any case, what version of MonetDB are you using (really the head?)
## Comment 9117
Date: 2008-03-03 04:18:13 +0100
From: mobigital <<mobigital>>
Logged In: YES
user_id=2024528
Originator: YES
Yes this was reproduced using the HEAD of MonetDB.
should I add some type of member to Heap to store how it was allocated?
because when I get another access violation it would be after the fact.
## Comment 9118
Date: 2008-06-13 07:04:56 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
could you check if this still happens on todays stable (ie the soon to be released version, MonetDB 5.6
SQL 2.24
## Comment 9119
Date: 2008-08-02 19:16:27 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
closing this bug as no new reports were made. We assume this got fixed. when we changed the memory mmapped bat handling.
## Comment 9120
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1905467 at http://sourceforge.net/support/tracker.php?aid=1905467
| access violation in GDKreallocmax | https://api.github.com/repos/MonetDB/MonetDB/issues/1611/comments | 0 | 2020-11-30T09:48:57Z | 2024-06-27T11:29:01Z | https://github.com/MonetDB/MonetDB/issues/1611 | 753,324,848 | 1,611 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.