Re: [Monetdb-developers] [Monetdb-pf-checkins] pathfinder/modules/pftijah nexi.c, 1.57, 1.58 nexi_generate_mil.c, 1.27, 1.28 pftijah.mx, 1.116, 1.117
On Mon, May 07, 2007 at 07:01:43AM +, Jan Flokstra wrote: > Update of /cvsroot/monetdb/pathfinder/modules/pftijah > In directory sc8-pr-cvs16:/tmp/cvs-serv20990/modules/pftijah > > Modified Files: > nexi.c nexi_generate_mil.c pftijah.mx > Log Message: > * Implement private term- and tag dictionaries. Default is still the global > version so nothing changed yet in the format. I'm having terrible trouble > with the Mtest's again. This version could not be tested by our Mtest tests > because the first query executes OK but all queries after that seem to > 'forget' the instance variables of module pftijah. I will look if the same > happens on other machine and post a bugreport for it. does the same happen if you run the test(s) by hand i.e., without Mtest? How do the queries and the test script(s) look like? How do you (successfully?) run them by hand? How do you (unsuccesfully) run them via Mtest? Stefan -- | Dr. Stefan Manegold | mailto:[EMAIL PROTECTED] | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 | - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
Re: [Monetdb-developers] [Monetdb-pf-checkins] pathfinder/modules/pftijah nexi.c, 1.57, 1.58 nexi_generate_mil.c, 1.27, 1.28 pftijah.mx, 1.116, 1.117
On Monday 07 May 2007 09:09, Stefan Manegold wrote: > On Mon, May 07, 2007 at 07:01:43AM +, Jan Flokstra wrote: > > Update of /cvsroot/monetdb/pathfinder/modules/pftijah > > In directory sc8-pr-cvs16:/tmp/cvs-serv20990/modules/pftijah > > > > Modified Files: > > nexi.c nexi_generate_mil.c pftijah.mx > > Log Message: > > * Implement private term- and tag dictionaries. Default is still the > > global version so nothing changed yet in the format. I'm having terrible > > trouble with the Mtest's again. This version could not be tested by our > > Mtest tests because the first query executes OK but all queries after > > that seem to 'forget' the instance variables of module pftijah. I will > > look if the same happens on other machine and post a bugreport for it. > > does the same happen if you run the test(s) by hand i.e., without Mtest? No, without Mtest the queries run OK. eg, any FIRST query runs OK. Any query after this fails. > > How do the queries and the test script(s) look like? The normal 28 tests from $PF/modules/pftijah/Tests So a mix of mil scripts and .xq XQueries. > How do you (successfully?) run them by hand? Just run the scripts in a test directory using MapiClient (-lx) > How do you (unsuccesfully) run them via Mtest? Mtest.py -d0 --TSTSRCBASE /local/flokstra/software/pathfinder in directory /local/flokstra/software/pathfinder/modules/pftijah > > Stefan The text of the bug report I had in mind was: I am having Mtest module variable problems again with pftijah. It looks a little bit like the never really solved problem of bug: [ 1638729 ] Mtest/Mapi module load problem The problem here was that the module was loaded but the instance variables and the non-ADDHELP'ed functions were unknown. We solved this by loading pftijah always from pathfinder but did not find the cause of the problem. I'm now having the same problem but in a different form. When I use Mtest on the pftijah Testset the first test where module(pftijah) is used works fine. But all tests after this fail. The problem is again that the MIL functions in the module are executed but the functions do not know the instance variables of the module. Nearly all tests fail on the variables "verbose" and "dflt_ft_index". You can for instance check this by changing $PF/modules/pftijah/Tests/All The first test which normally fails is createcoll0 because it is the second test. But when you remove loadthesis from All createcoll0 succeeds and createcoll1, which is then the second, fails. Jan. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
Re: [Monetdb-developers] An XQuery question
On Sun, May 06, 2007 at 10:28:57PM +0200, Ying Zhang wrote:
> If I run the follwoing XQuery query with Galax:
>
> ==
> test.xq
> ==
> declare namespace t = "test";
>
> declare function t:echoVoid() { () };
> t:echoVoid()
> ==
>
> Galax gives a warning:
>
> $ galax-run ~/test.xq
> [WARNING]
> Expression '???' at File "/ufs/zhang/test.xq", line 3, characters 8-37
> has empty type, but is not the empty expression
Jennie,
it is a static type error when expressions can statically be determined
to return the empty sequence. The XQuery Formal Semantics allows such
empty sequences only in very rare cases (e.g., as the argument of a
function call). This is why Galax complains. Pathfinder's type
checker, unfortunately, is not smart enough to detect these kind of
things and does not complain.
The rationale behind the behavior as specified in the specs is that an
XQuery processor could detect typos in the user input query, e.g., if a
user mis-types tag names in XPath location steps. A fully schema-aware
system might be able to detect such things.
Jens
--
Jens Teubner
Technische Universitaet Muenchen, Department of Informatics
D-85748 Garching, Germany
Tel: +49 89 289-17259 Fax: +49 89 289-17263
Things are pretty mixed up, but I think the worst is over.
-- TeX Error Message
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Monetdb-developers mailing list
Monetdb-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/monetdb-developers
Re: [Monetdb-developers] [Monetdb-pf-checkins] pathfinder/modules/pftijah nexi.c, 1.57, 1.58 nexi_generate_mil.c, 1.27, 1.28 pftijah.mx, 1.116, 1.117
Jan,
On Mon, May 07, 2007 at 09:19:17AM +0200, Jan Flokstra wrote:
> On Monday 07 May 2007 09:09, Stefan Manegold wrote:
> > On Mon, May 07, 2007 at 07:01:43AM +, Jan Flokstra wrote:
> > > Update of /cvsroot/monetdb/pathfinder/modules/pftijah
> > > In directory sc8-pr-cvs16:/tmp/cvs-serv20990/modules/pftijah
> > >
> > > Modified Files:
> > > nexi.c nexi_generate_mil.c pftijah.mx
> > > Log Message:
> > > * Implement private term- and tag dictionaries. Default is still the
> > > global version so nothing changed yet in the format. I'm having terrible
> > > trouble with the Mtest's again. This version could not be tested by our
> > > Mtest tests because the first query executes OK but all queries after
> > > that seem to 'forget' the instance variables of module pftijah. I will
> > > look if the same happens on other machine and post a bugreport for it.
> >
> > does the same happen if you run the test(s) by hand i.e., without Mtest?
>
> No, without Mtest the queries run OK. eg, any FIRST query runs OK. Any query
> after this fails.
do they run OK or NOT ???
If also without Mtest only the first runs OK and any other fails (that what
I read here), it is NOT an Mtest problem, but a general problem, right???
> > How do the queries and the test script(s) look like?
>
> The normal 28 tests from $PF/modules/pftijah/Tests So a mix of mil scripts
> and .xq XQueries.
>
> > How do you (successfully?) run them by hand?
>
> Just run the scripts in a test directory using MapiClient (-lx)
> > How do you (unsuccesfully) run them via Mtest?
>
> Mtest.py -d0 --TSTSRCBASE /local/flokstra/software/pathfinder
>
> in directory /local/flokstra/software/pathfinder/modules/pftijah
Before this mornings changes, everything did work fine, right?
Hence, your latest changes seem to *trigger* (not necessarily cause) the
problem. Looking in detail in your changes might give a hint, which part in
fact triggers the problem, which in turn would help a lot to analyse, locate
and eventually fix the problem.
Speaking of debugging here's a little excercise thet shows that the second
call to tj_init_collection() on the same database does fail, i.e., only the
first call to tj_init_collection() on a virgin database does not fail:
.../pathfinder/modules/pftijah/Tests $ export TSTSRCDIR=$PWD
.../pathfinder/modules/pftijah/Tests $ echo 'module(pathfinder);
tj_init_collection("testcoll0",
new(str,str).insert("stemmer","snowball-english"));' | Mserver --dbname=DB-1
# Monet Database Server V4.17.1
# Copyright (c) 1993-2007, CWI. All rights reserved.
# Compiled for x86_64-redhat-linux-gnu/64bit with 64bit OIDs; dynamically
linked.
# Visit http://monetdb.cwi.nl/ for further information.
MonetDB># XRPC administrative console at http://localhost:50001/admin
.../pathfinder/modules/pftijah/Tests $ echo 'module(pathfinder);
tj_init_collection("testcoll0",
new(str,str).insert("stemmer","snowball-english"));' | Mserver --dbname=DB-1
# Monet Database Server V4.17.1
# Copyright (c) 1993-2007, CWI. All rights reserved.
# Compiled for x86_64-redhat-linux-gnu/64bit with 64bit OIDs; dynamically
linked.
# Visit http://monetdb.cwi.nl/ for further information.
MonetDB># XRPC administrative console at http://localhost:50001/admin
!ERROR: interpret: unknown variable 'verbose'.
so, let's "trace" the variables:
.../pathfinder/modules/pftijah/Tests $ echo 'module(pathfinder); vars();' |
Mserver --dbname=DB-2 > /tmp/vars.0
.../pathfinder/modules/pftijah/Tests $ echo 'module(pathfinder); vars();' |
Mserver --dbname=DB-2 > /tmp/vars.1
.../pathfinder/modules/pftijah/Tests $ echo 'module(pathfinder);
tj_init_collection("testcoll0",
new(str,str).insert("stemmer","snowball-english"));' | Mserver --dbname=DB-2
# Monet Database Server V4.17.1
# Copyright (c) 1993-2007, CWI. All rights reserved.
# Compiled for x86_64-redhat-linux-gnu/64bit with 64bit OIDs; dynamically
linked.
# Visit http://monetdb.cwi.nl/ for further information.
MonetDB># XRPC administrative console at http://localhost:50001/admin
.../pathfinder/modules/pftijah/Tests $ echo 'module(pathfinder); vars();' |
Mserver --dbname=DB-2 > /tmp/vars.2
.../pathfinder/modules/pftijah/Tests $ echo 'module(pathfinder);
tj_init_collection("testcoll0",
new(str,str).insert("stemmer","snowball-english"));' | Mserver --dbname=DB-2
# Monet Database Server V4.17.1
# Copyright (c) 1993-2007, CWI. All rights reserved.
# Compiled for x86_64-redhat-linux-gnu/64bit with 64bit OIDs; dynamically
linked.
# Visit http://monetdb.cwi.nl/ for further information.
MonetDB># XRPC administrative console at http://localhost:50001/admin
!ERROR: interpret: unknown variable 'verbose'.
.../pathfinder/modules/pftijah/Tests $ echo 'module(pathfinder); vars();' |
Mserver --dbname=DB-2 > /tmp/vars.3
.../pathfinder/modules/pftijah/Tests $ grep --color verbose /tmp/vars.?
/tmp/vars.0:[ "
Re: [Monetdb-developers] An XQuery question
On Mon, May 07, 2007 at 09:35:37AM +0200, Jens Teubner wrote:
> On Sun, May 06, 2007 at 10:28:57PM +0200, Ying Zhang wrote:
>
> > If I run the follwoing XQuery query with Galax:
> >
> > ==
> > test.xq
> > ==
> > declare namespace t = "test";
> >
> > declare function t:echoVoid() { () };
> > t:echoVoid()
> > ==
> >
> > Galax gives a warning:
> >
> > $ galax-run ~/test.xq
> > [WARNING]
> > Expression '???' at File "/ufs/zhang/test.xq", line 3, characters 8-37
> > has empty type, but is not the empty expression
>
> Jennie,
>
> it is a static type error when expressions can statically be determined
> to return the empty sequence. The XQuery Formal Semantics allows such
> empty sequences only in very rare cases (e.g., as the argument of a
> function call). This is why Galax complains. Pathfinder's type
> checker, unfortunately, is not smart enough to detect these kind of
> things and does not complain.
Hi Jens,
Thanks for the explanation. So I think I will have to live with this
warning :(
Jennie
>
> The rationale behind the behavior as specified in the specs is that an
> XQuery processor could detect typos in the user input query, e.g., if a
> user mis-types tag names in XPath location steps. A fully schema-aware
> system might be able to detect such things.
>
> Jens
>
> --
> Jens Teubner
> Technische Universitaet Muenchen, Department of Informatics
> D-85748 Garching, Germany
> Tel: +49 89 289-17259 Fax: +49 89 289-17263
>
> Things are pretty mixed up, but I think the worst is over.
> -- TeX Error Message
>
> -
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> ___
> Monetdb-developers mailing list
> Monetdb-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/monetdb-developers
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Monetdb-developers mailing list
Monetdb-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/monetdb-developers
Re: [Monetdb-developers] [Monetdb-checkins] MonetDB5/src/optimizer opt_partitions.mx, 1.6, 1.7
On Mon, May 07, 2007 at 07:48:22AM +, Martin Kersten wrote: > Update of /cvsroot/monetdb/MonetDB5/src/optimizer > In directory sc8-pr-cvs16:/tmp/cvs-serv3297 > > Modified Files: > opt_partitions.mx > Log Message: > The first version of the partition code generator. > The code produced looks reasonable. > The necessary list module is not yet implemented. Nevertheless, checked-in code should always compile --- at least on one platform (and with the most conservative settings); however: gcc -DHAVE_CONFIG_H -I. -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/optimizer -I../.. -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/optimizer -I../mal -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/optimizer/../mal -I../modules/mal -I/ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/optimizer/../modules/mal -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--enable-debug/include/MonetDB -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--enable-debug/include/MonetDB/common -I/ufs/manegold/_/scratch0/Monet/Testing/Current/prefix.--enable-strict_--disable-optimize_--enable-debug/include/MonetDB/gdk -DLIBOPTIMIZER -Wall -Wextra -std=c99 -g -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -D_REENTRANT -c opt_partitions.c -fPIC -DPIC -o .libs/lib_optimizer_la-opt_partiti ons.o /ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/optimizer/opt_partitions.mx: In function 'OPTpartitionStrategy': /ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/optimizer/opt_partitions.mx:269: error: 'TYPE_list' undeclared (first use in this function) /ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/optimizer/opt_partitions.mx:269: error: (Each undeclared identifier is reported only once /ufs/manegold/_/scratch0/Monet/Testing/Current/source/MonetDB5/src/optimizer/opt_partitions.mx:269: error: for each function it appears in.) make[5]: *** [lib_optimizer_la-opt_partitions.lo] Error 1 Stefan -- | Dr. Stefan Manegold | mailto:[EMAIL PROTECTED] | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 | - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
