- developers-list - monetdb.org

[Monetdb-developers] Compilation of M5 stable in windows
by Romulo Goncalves 11 Jun '07

11 Jun '07

During the compilation I got: copy ".\..\..\src\mal\Makefile.msc" "mal\Makefile" 1 file(s) copied. cd "mal" && nmake /nologo "prefix=C:\cygwin\home\goncalve\MonetDB\MonetDB_SQL\Stable\MonetDB5\NT" all cl -GF -W3 -wd4273 -wd4102 -MD -nologo -Zi -Ox -I. -I.\..\.. "-IC:\Pthreads\include" -I.\..\..\..\src\mal -I"C:\cygwi \home\goncalve\MonetDB\MonetDB_SQL\Stable\MonetDB\NT\include" -I"C:\cygwin\home\goncalve\MonetDB\MonetDB_SQL\Stable\MonetDB\N \include\common" -I"C:\cygwin\home\goncalve\MonetDB\MonetDB_SQL\Stable\MonetDB\NT\include\gdk" -I"C:\cygwin\home\goncalve\Mon tDB\MonetDB_SQL\Stable\MonetDB\NT\include\monet" -I"C:\cygwin\home\goncalve\MonetDB\MonetDB_SQL\Stable\MonetDB\NT\include\pla n" -I"C:\cygwin\home\goncalve\MonetDB\MonetDB_SQL\Stable\MonetDB\NT\include\mapi" "-I..\optimizer" "-I..\scheduler" "-I..\m dules\kernel" -DLIBMAL -DCOMPILE_DL_MAL -Fo"mal.obj" -c "mal.c" mal.c ..\..\mal_config.h(23) : fatal error C1083: Cannot open include file: 'monetdb_winconfig.h': No such file or directory NMAKE : fatal error U1077: 'cl' : return code '0x2' Stop. NMAKE : fatal error U1077: 'cd' : return code '0x2' Stop. NMAKE : fatal error U1077: 'cd' : return code '0x2' Stop. NMAKE : fatal error U1077: '"E:\Visual Studio .NET 2003\VC7\BIN\nmake.exe"' : return code '0x2' I am using the same environment as the one used for the cvs branch. Any idea in how to resolve this problem? Regards, Romulo

3 6

Re: [Monetdb-developers] Compilation of M5 stable in windows
by Romulo Goncalves 11 Jun '07

11 Jun '07

Niels Nes wrote: > On Mon, Jun 11, 2007 at 09:50:37PM +0200, Romulo Goncalves wrote: >> Sjoerd Mullender wrote: >>> On 06/11/2007 08:43 PM, Romulo Goncalves wrote: >>>> Sjoerd Mullender wrote: >>>>> On 06/11/2007 06:46 PM, Romulo Goncalves wrote: >>>> I just checked out everything. I think it is a PATH problem. >>> Did you also re-bootstrap? Another standard requirement if there has >>> been a change in buildtools. >> When you check out a clean version you also need a re-boostraap? I do >> not think so. > If new files are added (ie Makefile.ag changed) or buildtools > is changed it is needed. When I say checkout clean source I mean everything (buildtools, clients, MonetDB, MonetDB5, sql). Then bootstraap, configure make and make install ;) As I said the problem it is for sure some wrong PATH that I set. ;) It is a stupid error from my part. So discussion is closed .... :) Regards, Romulo > > Niels >> Regards, >> Romulo >> >> ------------------------------------------------------------------------- >> 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(a)lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/monetdb-developers >

1 0

[Monetdb-developers] M5 strict and optimized compilation...
by Romulo Goncalves 11 Jun '07

11 Jun '07

During the compilation I got the following error: cc1: warnings being treated as errors /ufs/goncalve/MonetDB/MonetDB5/src/modules/mal/bpm.mx: In function 'BPMadapt': /ufs/goncalve/MonetDB/MonetDB5/src/modules/mal/bpm.mx:1587: warning: 'vp' may be used uninitialized in this function make[7]: *** [lib_bpm_la-bpm.lo] Error 1 make[7]: Leaving directory `/net/amelia/export/scratch1/goncalve/MonetDB/Stable/MonetDB5/build/src/modules/mal' The function head is here: static str BPMadaptImpl(int *ret, bat *bid, ptr low, ptr hgh, bat *rs, int policy ) { BAT *b,*bs, *bs1, *bs2; Partition ps, p, p2; int (*cmp) (ptr, ptr); ptr nilptr; ValPtr vp; Can I initialize it to NULL? If someone disagree please fix it with the correct value. Regards, Romulo

1 0

Re: [Monetdb-developers] [Monetdb-sql-checkins] sql/src/test/Triggers cascaded_triggers.sql, SQL_2-18, 1.2, 1.2.4.1 recursive_triggers.sql, SQL_2-18, 1.2, 1.2.4.1 referencing_clause_new.sql, SQL_2-18, 1.4, 1.4.4.1 referencing_clause_old.sql, SQL_2-18, 1.4, 1.4.4.1
by Romulo Goncalves 08 Jun '07

08 Jun '07

Romulo Goncalves wrote: > Update of /cvsroot/monetdb/sql/src/test/Triggers > In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv21172 > > Modified Files: > Tag: SQL_2-18 > cascaded_triggers.sql recursive_triggers.sql > referencing_clause_new.sql referencing_clause_old.sql > Log Message: > The new tests for UPDATE/DELETE CASCADE The new tests for the Trigger tests... Sorry for the wrong log message > > > > > Index: referencing_clause_new.sql > =================================================================== > RCS file: /cvsroot/monetdb/sql/src/test/Triggers/referencing_clause_new.sql,v > retrieving revision 1.4 > retrieving revision 1.4.4.1 > diff -u -d -r1.4 -r1.4.4.1 > --- referencing_clause_new.sql 7 Dec 2006 15:26:06 -0000 1.4 > +++ referencing_clause_new.sql 8 Jun 2007 12:47:50 -0000 1.4.4.1 > @@ -1,101 +1,199 @@ > +--this test only tests the sintax > --the semantic should also be tested after the syntax test > > create table t1 (id int, name varchar(1024)); > +create table t2 (id int, name varchar(1024)); > > ---test when the trigger event is UPDATE > +--test when trigger event is UPDATE > insert into t1 values(10, 'monetdb'); > insert into t1 values(20, 'monet'); > > > create trigger test1 > after update on t1 referencing new row as new_row > - for each row insert into t1 values(0, 'update_new_row'); > + for each row insert into t2 values(0, 'update_new_row'); > > create trigger test2 > after update on t1 referencing new row new_row > - for each row insert into t1 values(1, 'update_new_row'); > + for each row insert into t2 values(1, 'update_new_row'); > > create trigger test3 > after update on t1 referencing new as new_row > - for each row insert into t1 values(2, 'update_new_row'); > + for each row insert into t2 values(2, 'update_new_row'); > > create trigger test4 > after update on t1 referencing new new_row > - for each row insert into t1 values(3, 'update_new_row'); > + for each row insert into t2 values(3, 'update_new_row'); > > > update t1 set name = 'mo' where id = 10; > > select * from t1; > +select * from t2; > + > +delete from t1 where id > -1; > +delete from t2 where id > -1; > + > +drop trigger test1; > +drop trigger test2; > +drop trigger test3; > +drop trigger test4; > + > +--test when trigger event is DELETE > +insert into t1 values(10, 'monetdb'); > +insert into t1 values(20, 'monet'); > + > +create trigger test1 > + after delete on t1 referencing new row as new_row > + for each row insert into t2 values(0, 'delete_new_row'); > + > +create trigger test2 > + after delete on t1 referencing new row new_row > + for each row insert into t2 values(1, 'delete_new_row'); > + > +create trigger test3 > + after delete on t1 referencing new as new_row > + for each row insert into t2 values(2, 'delete_new_row'); > + > +create trigger test4 > + after delete on t1 referencing new new_row > + for each row insert into t2 values(3, 'delete_new_row'); > + > > delete from t1 where id >-1; > > +select * from t1; > +select * from t2; > + > drop trigger test1; > drop trigger test2; > drop trigger test3; > drop trigger test4; > > ---test when the trigger event is INSERT > +delete from t2 where id >-1; > + > +--test error messages > +--new row and new table are not allowed if the Trigger event is INSERT > + > insert into t1 values(10, 'monetdb'); > > create trigger test1 > after insert on t1 referencing new row as new_row > - for each row insert into t1 values(0, 'insert_new_row'); > + for each row insert into t2 values(0, 'insert_new_row'); > > create trigger test2 > after insert on t1 referencing new row new_row > - for each row insert into t1 values(1, 'insert_new_row'); > + for each row insert into t2 values(1, 'insert_new_row'); > > create trigger test3 > after insert on t1 referencing new as new_row > - for each row insert into t1 values(2, 'insert_new_row'); > + for each row insert into t2 values(2, 'insert_new_row'); > > create trigger test4 > after insert on t1 referencing new new_row > - for each row insert into t1 values(3, 'insert_new_row'); > + for each row insert into t2 values(3, 'insert_new_row'); > + > > insert into t1 values(20, 'monet'); > > select * from t1; > +select * from t2; > > -delete from t1 where id > -1; > +delete from t1 where id >-1; > +delete from t2 where id >-1; > > drop trigger test1; > drop trigger test2; > drop trigger test3; > drop trigger test4; > > ---test error messages > ---new row and new table are not allowed if the Trigger event is DELETE > +--test with new row and new table and mixed > > insert into t1 values(10, 'monetdb'); > insert into t1 values(20, 'monet'); > > create trigger test1 > - after delete on t1 referencing new row as new_row > - for each row insert into t1 values(0, 'delete_new_row'); > + after update on t1 referencing new row as new_row new table as new_table > + for each row insert into t2 values(0, 'insert_new_row_table'); > > create trigger test2 > - after delete on t1 referencing new row new_row > - for each row insert into t1 values(1, 'delete_new_row'); > + after update on t1 referencing new row new_row new row as new_row > + for each row insert into t2 values(1, 'insert_new_new_row'); > > create trigger test3 > - after delete on t1 referencing new as new_row > - for each row insert into t1 values(2, 'delete_new_row'); > + after update on t1 referencing new table as new_table new table as new_table > + for each row insert into t2 values(2, 'insert_new__new_table'); > > create trigger test4 > - after delete on t1 referencing new new_row > - for each row insert into t1 values(3, 'delete_new_row'); > + after update on t1 referencing new row as new_row new table as new_table > + for each row insert into t2 values(3, 'insert_new_row_new_table'); > > +create trigger test5 > + after update on t1 referencing new table as new_table new row as new_row > + for each row insert into t2 values(4, 'insert_new_table_new_row'); > > -delete from t1 where id >1; > + > +update t1 set name = 'mo' where id = 10; > > select * from t1; > +select * from t2; > + > +delete from t1 where id >-1; > +delete from t2 where id >-1; > + > > drop trigger test1; > drop trigger test2; > drop trigger test3; > drop trigger test4; > +drop trigger test5; > + > +--test stanger combinations > + > +insert into t1 values(10, 'monetdb'); > + > +create trigger test1 > + after update on t1 referencing new row as new_row new table as new_table > + for each row insert into t2 values(0, 'update_new_row_new_table'); > + > +create trigger test2 > + after insert on t1 referencing new row new_row new row as new_row > + for each row insert into t2 values(1, 'insert_new_new_row'); > + > +create trigger test3 > + after delete on t1 referencing new row new_row new row as new_row > + for each row insert into t2 values(2, 'delete_new_new_row'); > + > +create trigger test4 > + after delete on t1 referencing new row as new_row new table as new_table > + for each row insert into t2 values(3, 'delete_new_row_new_table'); > + > +create trigger test5 > + after insert on t1 referencing new table as new_table new row as new_row > + for each row insert into t2 values(4, 'insert_new_table_new_row'); > + > +insert into t1 values(20, 'monet'); > +select * from t1; > +select * from t2; > + > +update t1 set name = 'mo' where id = 10; > +select * from t1; > +select * from t2; > + > +delete from t1 where id >5; > +select * from t1; > +select * from t2; > + > + > +drop trigger test1; > +drop trigger test2; > +drop trigger test3; > +drop trigger test4; > +drop trigger test5; > + > +delete from t1 where id >-1; > +delete from t2 where id >-1; > > --Cleanup > drop table t1; > +drop table t2; > > Index: cascaded_triggers.sql > =================================================================== > RCS file: /cvsroot/monetdb/sql/src/test/Triggers/cascaded_triggers.sql,v > retrieving revision 1.2 > retrieving revision 1.2.4.1 > diff -u -d -r1.2 -r1.2.4.1 > --- cascaded_triggers.sql 6 Dec 2006 10:27:38 -0000 1.2 > +++ cascaded_triggers.sql 8 Jun 2007 12:47:49 -0000 1.2.4.1 > @@ -1,53 +1,31 @@ > ---test the semantic of cascaded triggers > create table t1(id int, name varchar(1024), age int); > - > create table t2(id int, age int); > > create trigger test_0 after insert on t1 > - update t1 set id = 1, name = 'monetdb', age = 24 where id =1; > - > -insert into t1 values(1, 'mo', 25); > - > -select * from t1; > - > -select * from t2; > - > -create trigger test_1 after insert on t1 > insert into t2 select id,age from t1; > > -insert into t1 values(2, 'mo', 26); > - > -select * from t1; > - > -select * from t2; > - > -create trigger test_2 after insert on t1 > - insert into t2 values(1,23); > - > -insert into t1 values(3, 'mo', 27); > +insert into t1 values(1, 'mo', 25); > > select * from t1; > - > select * from t2; > > -create trigger test_3 after delete on t1 > - delete from t1 where id =3; > +create trigger test_1 after delete on t1 > + insert into t1 values(3, 'mo', 27); > > delete from t1 where id = 1; > > select * from t1; > - > select * from t2; > > -create trigger test_4 after update on t1 > - update t1 > - set age = 27 > - where id = 2; > +create trigger test_2 after update on t1 > + delete from t2; > + > +create trigger test_3 after delete on t2 > + insert into t1 values(1, 'mo', 25); > > update t1 set name = 'monet' where id = 2; > > select * from t1; > - > select * from t2; > > drop trigger test_0; > @@ -58,8 +36,6 @@ > > drop trigger test_3; > > -drop trigger test_4; > - > drop table t1; > > drop table t2; > > Index: referencing_clause_old.sql > =================================================================== > RCS file: /cvsroot/monetdb/sql/src/test/Triggers/referencing_clause_old.sql,v > retrieving revision 1.4 > retrieving revision 1.4.4.1 > diff -u -d -r1.4 -r1.4.4.1 > --- referencing_clause_old.sql 8 Dec 2006 12:17:42 -0000 1.4 > +++ referencing_clause_old.sql 8 Jun 2007 12:47:50 -0000 1.4.4.1 > @@ -2,6 +2,7 @@ > --the semantic should also be tested after the syntax test > > create table t1 (id int, name varchar(1024)); > +create table t2 (id int, name varchar(1024)); > > --test when trigger event is UPDATE > insert into t1 values(10, 'monetdb'); > @@ -10,26 +11,28 @@ > > create trigger test1 > after update on t1 referencing old row as old_row > - for each row insert into t1 values(0, 'update_old_row'); > + for each row insert into t2 values(0, 'update_old_row'); > > create trigger test2 > after update on t1 referencing old row old_row > - for each row insert into t1 values(1, 'update_old_row'); > + for each row insert into t2 values(1, 'update_old_row'); > > create trigger test3 > after update on t1 referencing old as old_row > - for each row insert into t1 values(2, 'update_old_row'); > + for each row insert into t2 values(2, 'update_old_row'); > > create trigger test4 > after update on t1 referencing old old_row > - for each row insert into t1 values(3, 'update_old_row'); > + for each row insert into t2 values(3, 'update_old_row'); > > > update t1 set name = 'mo' where id = 10; > > select * from t1; > +select * from t2; > > delete from t1 where id > -1; > +delete from t2 where id > -1; > > drop trigger test1; > drop trigger test2; > @@ -42,31 +45,32 @@ > > create trigger test1 > after delete on t1 referencing old row as old_row > - for each row insert into t1 values(0, 'delete_old_row'); > + for each row insert into t2 values(0, 'delete_old_row'); > > create trigger test2 > after delete on t1 referencing old row old_row > - for each row insert into t1 values(1, 'delete_old_row'); > + for each row insert into t2 values(1, 'delete_old_row'); > > create trigger test3 > after delete on t1 referencing old as old_row > - for each row insert into t1 values(2, 'delete_old_row'); > + for each row insert into t2 values(2, 'delete_old_row'); > > create trigger test4 > after delete on t1 referencing old old_row > - for each row insert into t1 values(3, 'delete_old_row'); > + for each row insert into t2 values(3, 'delete_old_row'); > > > delete from t1 where id >-1; > > select * from t1; > +select * from t2; > > drop trigger test1; > drop trigger test2; > drop trigger test3; > drop trigger test4; > > -delete from t1 where id >-1; > +delete from t2 where id >-1; > > --test error messages > --old row and old table are not allowed if the Trigger event is INSERT > @@ -75,26 +79,28 @@ > > create trigger test1 > after insert on t1 referencing old row as old_row > - for each row insert into t1 values(0, 'insert_old_row'); > + for each row insert into t2 values(0, 'insert_old_row'); > > create trigger test2 > after insert on t1 referencing old row old_row > - for each row insert into t1 values(1, 'insert_old_row'); > + for each row insert into t2 values(1, 'insert_old_row'); > > create trigger test3 > after insert on t1 referencing old as old_row > - for each row insert into t1 values(2, 'insert_old_row'); > + for each row insert into t2 values(2, 'insert_old_row'); > > create trigger test4 > after insert on t1 referencing old old_row > - for each row insert into t1 values(3, 'insert_old_row'); > + for each row insert into t2 values(3, 'insert_old_row'); > > > insert into t1 values(20, 'monet'); > > select * from t1; > +select * from t2; > > delete from t1 where id >-1; > +delete from t2 where id >-1; > > drop trigger test1; > drop trigger test2; > @@ -108,30 +114,33 @@ > > create trigger test1 > after update on t1 referencing old row as old_row old table as old_table > - for each row insert into t1 values(0, 'insert_old_row_table'); > + for each row insert into t2 values(0, 'insert_old_row_table'); > > create trigger test2 > after update on t1 referencing old row old_row new row as new_row > - for each row insert into t1 values(1, 'insert_old_new_row'); > + for each row insert into t2 values(1, 'insert_old_new_row'); > > create trigger test3 > after update on t1 referencing old table as old_table new table as new_table > - for each row insert into t1 values(2, 'insert_old__new_table'); > + for each row insert into t2 values(2, 'insert_old__new_table'); > > create trigger test4 > after update on t1 referencing old row as old_row new table as new_table > - for each row insert into t1 values(3, 'insert_old_row_new_table'); > + for each row insert into t2 values(3, 'insert_old_row_new_table'); > > create trigger test5 > after update on t1 referencing old table as old_table new row as new_row > - for each row insert into t1 values(3, 'insert_old_table_new_row'); > + for each row insert into t2 values(4, 'insert_old_table_new_row'); > > > update t1 set name = 'mo' where id = 10; > > select * from t1; > +select * from t2; > > delete from t1 where id >-1; > +delete from t2 where id >-1; > + > > drop trigger test1; > drop trigger test2; > @@ -145,32 +154,35 @@ > > create trigger test1 > after update on t1 referencing old row as old_row new table as new_table > - for each row insert into t1 values(0, 'update_old_row__new_table'); > + for each row insert into t2 values(0, 'update_old_row_new_table'); > > create trigger test2 > after insert on t1 referencing old row old_row new row as new_row > - for each row insert into t1 values(1, 'insert_old_new_row'); > + for each row insert into t2 values(1, 'insert_old_new_row'); > > create trigger test3 > after delete on t1 referencing old row old_row new row as new_row > - for each row insert into t1 values(1, 'delete_old_new_row'); > + for each row insert into t2 values(2, 'delete_old_new_row'); > > create trigger test4 > after delete on t1 referencing old row as old_row new table as new_table > - for each row insert into t1 values(3, 'delete_old_row_new_table'); > + for each row insert into t2 values(3, 'delete_old_row_new_table'); > > create trigger test5 > after insert on t1 referencing old table as old_table new row as new_row > - for each row insert into t1 values(3, 'insert_old_table_new_row'); > + for each row insert into t2 values(4, 'insert_old_table_new_row'); > > insert into t1 values(20, 'monet'); > select * from t1; > +select * from t2; > > update t1 set name = 'mo' where id = 10; > select * from t1; > +select * from t2; > > delete from t1 where id >5; > select * from t1; > +select * from t2; > > > drop trigger test1; > @@ -180,6 +192,8 @@ > drop trigger test5; > > delete from t1 where id >-1; > +delete from t2 where id >-1; > > --Cleanup > drop table t1; > +drop table t2; > > Index: recursive_triggers.sql > =================================================================== > RCS file: /cvsroot/monetdb/sql/src/test/Triggers/recursive_triggers.sql,v > retrieving revision 1.2 > retrieving revision 1.2.4.1 > diff -u -d -r1.2 -r1.2.4.1 > --- recursive_triggers.sql 6 Dec 2006 10:27:38 -0000 1.2 > +++ recursive_triggers.sql 8 Jun 2007 12:47:49 -0000 1.2.4.1 > @@ -1,57 +1,62 @@ > create table t1(id int, name varchar(1024), age int); > create table t2(id int, age int); > > +--the trigger calls itself > create trigger test_0 after insert on t1 > - insert into t1 values(1, 'monetdb', 24); > - > -insert into t1 values(1, 'mo', 25); > + insert into t1 values(3, 'mo', 27); > > -select * from t1; > -select * from t2; > +drop trigger test_0; > > -create trigger test_1 after insert on t1 > +--recursivity of 2 levels > +create trigger test_0 after insert on t1 > insert into t2 select id,age from t1; > +create trigger test_1 after insert on t2 > + insert into t1 values(3, 'mo', 27); > > -insert into t1 values(2, 'mo', 26); > > -select * from t1; > -select * from t2; > +drop trigger test_0; > +drop trigger test_1; > > -create trigger test_2 before insert on t1 > - insert into t2 values(1,23); > +--recursivity of n levels > +create trigger test_0 after insert on t1 > + insert into t2 select id,age from t1; > > -insert into t1 values(3, 'mo', 27); > +create trigger test_1 after insert on t2 > + delete from t2; > > -select * from t1; > -select * from t2; > +create trigger test_2 after delete on t2 > + insert into t1 values(3, 'mo', 27); > > -create trigger test_3 after delete on t1 > - delete from t1 where id =3; > > -delete from t1 where id = 1; > +drop trigger test_0; > +drop trigger test_1; > +drop trigger test_2; > > -select * from t1; > -select * from t2; > +--recursivity with procedure calls > +create PROCEDURE p1(id int, age int) > +BEGIN > + insert into t2 values(id, age); > +END; > > -create trigger test_4 after update on t1 > - update t1 > - set age = 27 > - where id = 2; > +create PROCEDURE p1() > +BEGIN > + declare id int, age int; > + set id = 1; > + set age = 23; > + call p1(id, age); > +END; > > -update t1 set name = 'monet' where id = 2; > +create trigger test_0 after insert on t2 > +BEGIN ATOMIC > + insert into t1 values(1, 'monetdb', 24); > + call p1(); > +END; > > -select * from t1; > -select * from t2; > +--insert into t2 values(0, 24); > > drop trigger test_0; > > -drop trigger test_1; > - > -drop trigger test_2; > - > -drop trigger test_3; > - > -drop trigger test_4; > +drop ALL procedure p1; > > drop table t1; > > > > ------------------------------------------------------------------------- > 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-sql-checkins mailing list > Monetdb-sql-checkins(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/monetdb-sql-checkins

1 0

Re: [Monetdb-developers] [Monetdb-pf-checkins] pathfinder/compiler/semantics xquery_fo.c, XQuery_0-18, 1.129.2.1, 1.129.2.2
by Stefan Manegold 08 Jun '07

08 Jun '07

On Thu, Jun 07, 2007 at 08:01:52PM +0000, Sjoerd Mullender wrote: > Update of /cvsroot/monetdb/pathfinder/compiler/semantics > In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv31053 > > Modified Files: > Tag: XQuery_0-18 > xquery_fo.c > Log Message: > Experiment: split up declaration of xquery_fo into smaller pieces in > multiple functions to see whether it then compiles with icc on Linux. Sjoerd, thanks for yoiur efforts! Unfortunately, it still does not help/work: /net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Stable/source/pathfinder/compiler/semantics/xquery_fo.c(1664): (col. 1)internal error: 0_0 Maybe, we should finally consider upgrading icc --- provided there is a newer (free) version available... Stefan > Index: xquery_fo.c > =================================================================== > RCS file: /cvsroot/monetdb/pathfinder/compiler/semantics/xquery_fo.c,v > retrieving revision 1.129.2.1 > retrieving revision 1.129.2.2 > diff -u -d -r1.129.2.1 -r1.129.2.2 > --- xquery_fo.c 7 Jun 2007 14:07:00 -0000 1.129.2.1 > +++ xquery_fo.c 7 Jun 2007 20:01:49 -0000 1.129.2.2 > @@ -97,8 +97,8 @@ > } > } > > -void > -PFfun_xquery_fo (void) > +static void > +PFfun_xquery_fo1 (void) > { > struct xquery_fo xquery_fo1[] = > /** > @@ -956,7 +956,15 @@ > .ret_ty = PFty_xs_double () } }, > .alg = PFbui_fn_floor_dbl } > , { .loc = 0 } > - }, xquery_fo2[] = { > + }; > + > + xquery_fo_initiaze(xquery_fo1); > +} > + > +static void > +PFfun_xquery_fo2 (void) > +{ > + struct xquery_fo xquery_fo2[] = { > /* fn:floor (integer?) as integer? */ > { .ns = PFns_fn, .loc = "floor", > .arity = 1, .sig_count = 1, .sigs = { { > @@ -1646,7 +1654,15 @@ > .ret_ty = PFty_opt (PFty_doc (PFty_xs_anyNode ())) } }, > .alg = PFbui_fn_doc } > , { .loc = 0 } > - }, xquery_fo3[] = { > + }; > + > + xquery_fo_initiaze(xquery_fo2); > +} > + > +static void > +PFfun_xquery_fo3 (void) > +{ > + struct xquery_fo xquery_fo3[] = { > /* fn:collection (string) as node* */ > { .ns = PFns_fn, .loc = "collection", > .arity = 1, .sig_count = 1, .sigs = { { > @@ -2241,11 +2257,17 @@ > , { .loc = 0 } > }; > > + xquery_fo_initiaze(xquery_fo3); > +} > + > +void > +PFfun_xquery_fo (void) > +{ > PFfun_env = PFenv (); > > - xquery_fo_initiaze(xquery_fo1); > - xquery_fo_initiaze(xquery_fo2); > - xquery_fo_initiaze(xquery_fo3); > + PFfun_xquery_fo1 (); > + PFfun_xquery_fo2 (); > + PFfun_xquery_fo3 (); > } > > /* vim:set shiftwidth=4 expandtab: */ > > > ------------------------------------------------------------------------- > 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-pf-checkins mailing list > Monetdb-pf-checkins(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/monetdb-pf-checkins -- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | 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 |

2 1

Re: [Monetdb-developers] [Monetdb-pf-checkins] pathfinder/modules/pftijah serialize_pftijah.mx, XQuery_0-18, 1.49, 1.49.2.1
by Stefan Manegold 07 Jun '07

07 Jun '07

Jan, property checking is quite expensive, hence, you might want to do it for debugging purposes, only, e.g, when property checking is enabled in Mserver via --debug=8 / --debug=10. To do so, just replace "if ( 1 )" by "PROPDEBUG" (which is defined as "if (GDKdebug & PROPMASK)" in MonetDB/src/gdk/gdk.mx) Stefan On Thu, Jun 07, 2007 at 12:50:55PM +0000, Jan Flokstra wrote: > Update of /cvsroot/monetdb/pathfinder/modules/pftijah > In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv12149 > > Modified Files: > Tag: XQuery_0-18 > serialize_pftijah.mx > Log Message: > - add a propcheck to our "C" generated ft-index BATs to see if they are correct > > > > Index: serialize_pftijah.mx > =================================================================== > RCS file: /cvsroot/monetdb/pathfinder/modules/pftijah/serialize_pftijah.mx,v > retrieving revision 1.49 > retrieving revision 1.49.2.1 > diff -u -d -r1.49 -r1.49.2.1 > --- serialize_pftijah.mx 1 Jun 2007 15:35:00 -0000 1.49 > +++ serialize_pftijah.mx 7 Jun 2007 12:50:49 -0000 1.49.2.1 > @@ -689,6 +689,16 @@ > BBPunfix(BBPcacheid(tjctx->b_collPre)); > BBPunfix(BBPcacheid(tjctx->b_collSize)); > BBPunfix(BBPcacheid(tjctx->b_collPfPre)); > + if ( 1 ) { > + BATpropcheck(tjctx->b_globalTerm,BATPROPS_ALL); > + BATpropcheck(tjctx->b_globalTag,BATPROPS_ALL); > + BATpropcheck(tjctx->b_docName,BATPROPS_ALL); > + BATpropcheck(tjctx->b_docFirstPre,BATPROPS_ALL); > + BATpropcheck(tjctx->b_collParam,BATPROPS_ALL); > + BATpropcheck(tjctx->b_collPre,BATPROPS_ALL); > + BATpropcheck(tjctx->b_collSize,BATPROPS_ALL); > + BATpropcheck(tjctx->b_collPfPre,BATPROPS_ALL); > + } > if ( tjctx->stemCtx->clear && !tjctx->stemCtx->clear(tjctx->stemCtx) ) > return GDK_FAIL; > free(tjctx); > > > ------------------------------------------------------------------------- > 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-pf-checkins mailing list > Monetdb-pf-checkins(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/monetdb-pf-checkins > > -- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | 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 |

1 0

Re: [Monetdb-developers] [Monetdb-pf-checkins] pathfinder/modules/pftijah pftijah.mx, XQuery_0-18, 1.134.2.1, 1.134.2.2
by Stefan Manegold 07 Jun '07

07 Jun '07

Jan, IMHO, this changes is not correct. Though being of type BIT (which is physically a signed char, hence 8 bit wide), the ordered flags use all 8 bits, only the lowest one (1) indicates sortedness, the highest one (1<<7=128) indicates reverse sortedness, and the remaining ones are "mis-"used for radix clustering. Hence, checking for sortedness shoudl alwasy be done with BAT[ht]ordered(b)&1 --- regardless of the endianess, this should alwasy check for the lowest bit, now matter whether this is located left or right --- anyway, endianess is about byte orde, not about bit order, right?? Hence, if the your change does fix the Itanium problems, than the bug is IMHO caused somewhere else (wrong setting of the ordered flag?), and only appears here... Stefan On Thu, Jun 07, 2007 at 09:28:20AM +0000, Jan Flokstra wrote: > Update of /cvsroot/monetdb/pathfinder/modules/pftijah > In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv29459 > > Modified Files: > Tag: XQuery_0-18 > pftijah.mx > Log Message: > - Try to fix Itanium bug [ 1732596 ] PFtijah tests fail on Itanium > Remove the bitwise AND in the check because it could be at the wrong side > of the word? > > > > Index: pftijah.mx > =================================================================== > RCS file: /cvsroot/monetdb/pathfinder/modules/pftijah/pftijah.mx,v > retrieving revision 1.134.2.1 > retrieving revision 1.134.2.2 > diff -u -d -r1.134.2.1 -r1.134.2.2 > --- pftijah.mx 4 Jun 2007 17:42:06 -0000 1.134.2.1 > +++ pftijah.mx 7 Jun 2007 09:28:18 -0000 1.134.2.2 > @@ -3745,8 +3745,10 @@ > /* --------------------------- checks ---------------------------------- */ > > BATcheck(tid, name); > - if (!(BATtordered(tid) & 1)) > + /* if (!(BATtordered(tid) & 1)) */ > + if ( !(BATtordered(tid) ) > { > + /* BUG#1732596 this test currently fails on Itanium */ > GDKerror("%s: index-bat must be ordered on tail.\n", name); > return GDK_FAIL; > } > > > ------------------------------------------------------------------------- > 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-pf-checkins mailing list > Monetdb-pf-checkins(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/monetdb-pf-checkins > -- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | 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 |

1 0

Re: [Monetdb-developers] [Monetdb-pf-checkins] pathfinder/runtime shredder.mx, XQuery_0-18, 1.126, 1.126.2.1
by Jens Teubner 07 Jun '07

07 Jun '07

Hi Jan F, thanks for looking into our shredder's entity handling. This has been bugging us for quite a while now. It feels a bit strange, though, that we really have to implement getEntity() ourselves. After all, this is exactly what I would expect to be handled automatically by an XML parsing library. I have just glanced briefly over the libxml2 documentation. And I saw that there is a replaceEntities field in libxml2's xmlParserCtxt struct. As usual, the documentation is very poor here, but this sounds to me like exactly what we need. Have you tried whether simply enabling this flag would handle entities automatically? (Sorry, I don't have the time to test this myself right now.) You find the documentation for xmlParserCtxt at http://xmlsoft.org/html/libxml-tree.html#xmlParserCtxt . Just my 2¢ (still Euro-Cents) Jens On Tue, Jun 05, 2007 at 07:30:50AM +0000, Jan Flokstra wrote: > Update of /cvsroot/monetdb/pathfinder/runtime > In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv2405 > > Modified Files: > Tag: XQuery_0-18 > shredder.mx > Log Message: > - A first attempt at making ENTITIES work. After long searching and > trying the final solution was very simple. The libxml2 package already > maintains a hashtable with defined entities. The only thing missing was > the lookup function which it mysteriously does not use. > I implemented the "getEntity()" function in the xmlSAXHandler structure and > now simple ENTITIES defined in the internal subset work. > This solves bug#1185932 XML: Entities by Wouter Alink > > - Change error handling. I noticed for some time that there were no error > messages generated anymore on my system. The xmlSetGenericErrorFunc() does > not work on my machine. I added the "error()" function in the xmlSAXHandler > structure and now I get descriptive error messages again. This may screw up > some testset output but I think this is a big system improvement. > > > > Index: shredder.mx > =================================================================== > RCS file: /cvsroot/monetdb/pathfinder/runtime/shredder.mx,v > retrieving revision 1.126 > retrieving revision 1.126.2.1 > diff -u -d -r1.126 -r1.126.2.1 > --- shredder.mx 24 Apr 2007 15:04:42 -0000 1.126 > +++ shredder.mx 5 Jun 2007 07:30:46 -0000 1.126.2.1 > @@ -1103,6 +1103,35 @@ > stream_printf(GDKerr, "%s", buf); > } > > +static void > +shred_warning(void *ctx, > + const char *msg, ...) > +{ > + /* IMPORTANT this function may be called multiple times for one error > + * message so it is not possible to use GDKerror() here. > + * Instead, we "mis-use" the ctx pointer to remember whether a newline > + * has occured in the error message, and thus be able to prefix each > + *(line of an) error message with GDKERROR("!Error: "), which is > + * required to properly get the error message through the MAPI > + * protocol... > + */ > + va_list args; > + int *print_error_newline =(int*)ctx; > + int len = 0; > + char buf[PFSHRED_BUFLEN]; > + > + if (*print_error_newline) { > + len += snprintf(buf+len, PFSHRED_BUFLEN-len-1, GDKERROR); > + } > + > + va_start(args, msg); > + len += vsnprintf(buf+len, PFSHRED_BUFLEN-len-1, msg, args); > + va_end(args); > + > + *print_error_newline =(strchr(buf,(int)'\n') != NULL); > + stream_printf(GDKerr, "!WARNING: %s", buf); > +} > + > /** > * The shred_attribute_defAttributeDef() handles the DTD attribute definition callbacks > * in the from the header of the XML file. This is used for the ID/IDREF > @@ -1163,6 +1192,44 @@ > } > } > > +static xmlEntityPtr > +shred_getEntity(void *xmlCtx, const xmlChar *name) > +{ > + /* the shredder is now able to handle ENTITY's from the internal > + * subset. I do not really understand yet why this had to be done > + * here and why it was not handled automagically > + * The functions used are defined in $LIBXML2INCLUDES/entities.h > + */ > +#if 0 > + stream_printf(GDKerr,"shred_getEntity(ctx,\"%s\") CALLED\n",name); > +#endif > + xmlParserCtxtPtr ctx = ((shredCtxStruct*) xmlCtx)->xmlCtx; > + /* lookup the entity in the document entity hash table */ > + return xmlGetDocEntity(ctx->myDoc,name); > + /* QUESTION: xmlGetDtdEntity() and xmlGetParameterEntity() were also > + * possible, whats the diff between the doc/dtd versions, they both > + * seem to work. */ > +} > + > +#if 0 > +/* My first try at building an entity table but this one was not necessary > + * because the internal subset table was already build. > + */ > +static void > +shred_entityDecl(void *xmlCtx, > + const xmlChar *name, > + int type, > + const xmlChar *publicId, > + const xmlChar *systemId, > + xmlChar *content) > +{ > + xmlParserCtxtPtr ctx = ((shredCtxStruct*) xmlCtx)->xmlCtx; > + if ( ! xmlAddDtdEntity(ctx->myDoc,name,type,publicId,systemId,content) ) > + stream_printf(GDKerr,"shred_entityDecl(ctx,\"%s\") FAIL\n",name); > +} > +#endif > + > + > /* ==================================================================================== > * the shredder and its data structures > * - shredder_create() create all data structures > @@ -1183,14 +1250,14 @@ > , .characters = shred_characters > , .processingInstruction = shred_pi > , .comment = shred_comment > - , .error = 0 > + , .error = shred_error > , .cdataBlock = shred_cdata > , .internalSubset = 0 > , .isStandalone = 0 > , .hasInternalSubset = 0 > , .hasExternalSubset = 0 > , .resolveEntity = 0 > - , .getEntity = 0 > + , .getEntity = shred_getEntity > , .entityDecl = 0 > , .notationDecl = 0 > , .attributeDecl = shred_attribute_def > @@ -1199,7 +1266,7 @@ > , .setDocumentLocator = 0 > , .reference = 0 > , .ignorableWhitespace = 0 > - , .warning = 0 > + , .warning = shred_warning > , .fatalError = 0 > , .getParameterEntity = 0 > , .externalSubset = shred_external_subset > @@ -1229,6 +1296,10 @@ > char buf[XMLCHUNK+1]; > > /* reset libxml2 error handling */ > + /* note JF: this does not have any effect on SuSe9.3. No error messages > + * are printed. I assigned the 'error' field in the xmlSAXHandler and > + * this works fine. > + */ > xmlSetGenericErrorFunc((void*)&print_error_newline, shred_error); > > /* parse XML input(receive SAX events) */ > @@ -1237,7 +1308,30 @@ > } else if (buffer) { > xmlCtx = xmlCreateMemoryParserCtxt(buffer, shredCtx->fileSize); > } else { > - xmlCtx = xmlCreateURLParserCtxt(location, XML_PARSE_XINCLUDE|XML_PARSE_NOXINCNODE); > + /* Possible options for the second arg are: > + * XML_PARSE_RECOVER = recover on errors > + * XML_PARSE_NOENT = substitute entities > + * XML_PARSE_DTDLOAD = load the external subset > + * XML_PARSE_DTDATTR = default DTD attributes > + * XML_PARSE_DTDVALID = validate with the DTD > + * XML_PARSE_NOERROR = suppress error reports > + * XML_PARSE_NOWARNING = suppress warning reports > + * XML_PARSE_PEDANTIC = pedantic error reporting > + * XML_PARSE_NOBLANKS = remove blank nodes > + * XML_PARSE_SAX1 = use the SAX1 interface internally > + * XML_PARSE_XINCLUDE = Implement XInclude substitition > + * XML_PARSE_NONET = Forbid network access > + * XML_PARSE_NODICT = Do not reuse the context dictionnary > + * XML_PARSE_NSCLEAN = rm redundant namespaces declarations > + * XML_PARSE_NOCDATA = merge CDATA as text nodes > + * XML_PARSE_NOXINCNODE= do not generate XINCLUDE START/END nodes > + */ > + /* > + * TODO: how to prevent expansion of entities? > + */ > + xmlCtx = xmlCreateURLParserCtxt(location, > + XML_PARSE_XINCLUDE| > + XML_PARSE_NOXINCNODE); > } > if (!xmlCtx) { > GDKerror("shredder_parse: libxml2 could not initialize a parser.\n"); > > > ------------------------------------------------------------------------- > 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-pf-checkins mailing list > Monetdb-pf-checkins(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/monetdb-pf-checkins -- Jens Teubner Technische Universitaet Muenchen, Department of Informatics D-85748 Garching, Germany Tel: +49 89 289-17259 Fax: +49 89 289-17263 >From /usr/src/linux/include/linux/kernel.h: #define STACK_MAGIC 0xdeadbeef

2 1

[Monetdb-developers] Release Branding?
by Stefan Manegold 05 Jun '07

05 Jun '07

Dear fellow developers, some time ago, we intorduced "nicknames" to be able to refer to our "mega-releases" (in particular MonetDB/XQuery, but in general all MonetDB related packages released together. Hence, what should be the name of this (final?) "mega-release"? (Future releases will preferably be release of individual packages such that a new release of a package work with the most recently released version of all related packages.) My suggestion: Starting the journey with (on) Valentijn('s day 2005), and after stop-overs at Mercury, Earth, Ceres, (being lost in Star Dust), and Venus, Pathfinder finally arrived at Mars (only to leave our own solar system hereafter to explore outer space...) Comments? Stefan -- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | 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 |

2 1

Re: [Monetdb-developers] [Monetdb-checkins] buildtools/conf MonetDB.m4, MonetDB_1-18, 1.16.2.2, 1.16.2.3
by Stefan Manegold 05 Jun '07

05 Jun '07

On Tue, Jun 05, 2007 at 09:24:10AM +0200, Fabian Groffen wrote: > On 05-06-2007 06:13:22 +0000, Stefan Manegold wrote: > > Update of /cvsroot/monetdb/buildtools/conf > > In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv17106/conf > > > > Modified Files: > > Tag: MonetDB_1-18 > > MonetDB.m4 > > Log Message: > > > > Java 1.6 seems to be (partly) incompatible with Java 1.4 & 1.5; > > we do not support Java 1.6, yet. > > Stefan, > > Thanks for doing this. It was on my todo-list, but I ended up > forgetting about it every time. no problem. same holds/held for me, just happened to recall it "by accident", and took the "early bird's" opportunity ;-) Stefan > ------------------------------------------------------------------------- > 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-checkins mailing list > Monetdb-checkins(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/monetdb-checkins -- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | 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 |

1 0