- developers-list - monetdb.org

Re: [Monetdb-developers] [Monetdb-sql-checkins] sql/src/sql random.sql, 1.1, NONE
by Romulo Goncalves 24 May '07

24 May '07

This means that it has to be removed from the Makefile (the compilation crash due this problem). I will remove it, if none disagree. Regards, Romulo Niels Nes wrote: > Update of /cvsroot/monetdb/sql/src/sql > In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv24021 > > Removed Files: > random.sql > Log Message: > removed as random functions moved into the default set (as they have > side effects, which currently cannot be specified in sql) > > > --- random.sql DELETED --- > > > ------------------------------------------------------------------------- > 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

2 1

[Monetdb-developers] Debian/Ubuntu not in testweb?
by Jan Flokstra 24 May '07

24 May '07

Hi All, Is there a specific reason why there is no Debian Linux version in the testweb or was there just no machine available. We are experiencing a couple of very strange compilation and runtime errors with student projects running Ubuntu Linux and wonder if the Pathfinder HEAD is even supposed to work on Ubuntu? Regards, JanF.

2 1

[Monetdb-developers] nightly current target missing
by Colin Foss 24 May '07

24 May '07

It appears something bad happened to the overnight builds. i.e. --22:27:57-- http://www.ins.cwi.nl/~fabian/monetdb/tars/latest/current/MonetDB.tar.gz => `/var/tmp/MonetDB-1179984476/MonetDB/MonetDB.tar.gz' Resolving www.ins.cwi.nl... 192.16.196.21 Connecting to www.ins.cwi.nl|192.16.196.21|:80... connected. HTTP request sent, awaiting response... 403 Forbidden 22:27:58 ERROR 403: Forbidden. also, http://monetdb.cwi.nl/testing/projects/monetdb/Current/.DailyBuilds./200705… is empty.

2 1

[Monetdb-developers] Infinite loop...
by Romulo Goncalves 23 May '07

23 May '07

Dear developers, I opened a bug related to an infinite loop created by this example: create table t1(id int, name varchar(1024), age int); create table t2(id int, age int); create PROCEDURE p1(id int, age int) BEGIN insert into t2 values(id, age); END; create PROCEDURE p1() BEGIN declare id int, age int; set id = 1; set age = 23; call p1(id, age); END; create trigger test_0 after insert on t2 BEGIN ATOMIC insert into t1 values(1, 'monetdb', 24); call p1(); END; insert into t2 values(0, 24); AS you can see the procedure p1() will do an insertion in t2 which will fire the trigger test_0 again and all the process will be repeated again. I decided to check what happen in another DBMS (I checked postgres because it is used as a reference). Looking to this example http://archives.postgresql.org/pgsql-general/2003-07/msg01530.php It seems postgres has the same problem, but should we consider this a problem or bug? SQL with procedures (function...) can almost be considered a programming language so it is not our responsibility to kill loops created by users SQL code. If an user see a infinite loop he has to construct the schema in such way that the infinite loops are avoided. Another point is the restriction that we created for recursive triggers (we only allow at least one call for each trigger in each statement execution) which I think it is not correct. Imagine that the user has an "if clause" to recursively fire a trigger 10 times and after that 10 times the trigger is not fired anymore. Should we restrict this example in our system? I do not think so. However, If the clause check is wrong and an infinite loop is created it is the user who has to correct his schema. The big conclusion of the day is: More programing language features do we offer to the user less control we have over his SQL code. If everyone agree I will close the bug infinite loop and remove the loop check for triggers. Regards, Romulo

2 1

[Monetdb-developers] nightly target contents
by Colin Foss 23 May '07

23 May '07

Sorry if this question is borderline user. Using monetdb-install.sh, what does --nightly=stable actually contain? What does --nightly=current contain? Do the nightly tar files contain source from a sucessful build or simply a CVS checkout? Is a cross-reference between bug number and --nightly=<target> maintained?

3 4

Re: [Monetdb-developers] possible bug regarding auto-commit mixing with start transaction?
by Martin Kersten 23 May '07

23 May '07

Hi, Alexandru Toth wrote: > Hi, > > Not in console. But if you create a file , it will show up with command > line bellow. > > mclient -lsql -umonetdb 1.sql Confirmed. > > Or, is Mac OS -speciffic ? No, also on Linux PC. You assume here that auto-commit is re-enabled when the statements fall outside the transaction brackets. The mode change and the consequences should be clearly documented in Mapi. It may indeed be useful to fall-back to auto-commit outside explicit transaction boundaries. regards, Martin > > BR, Alex > > On May 22, 2007, at 11:43 PM, Martin Kersten wrote: > >> Hi, >> >> Bug not confirmed on my Linux PC using >> direct execution at the console, nor >> using MapiClient. >> >> % sys.tbl_xy, sys.tbl_xy # table_name >> % x, y # name >> % int, int # type >> % 2, 4 # length >> [ 0, 0 ] >> [ 1, 1 ] >> [ 2, 2 ] >> [ 3, 3 ] >> [ 4, 4 ] >> [ 5, 5 ] >> [ 6, 6 ] >> [ 7, 7 ] >> [ -1, -100 ] >> [ 8, 8 ] >> [ 9, 9 ] >> [ 10, 10 ] >> >> >> >> Alexandru Toth wrote: >>> Hi, >>> Test script bellow has few transactions, and statements outside any >>> transaction which are not executed (INSERT negative numbers, easy to >>> spot). Is this a bug? Both MySQL and SQLite inserts the row with >>> negative numbers (after replacing "start transaction" with "begin"). >>> Save the script bellow as 1.sql >>> ----------------- >>> start transaction; >>> create table tbl_xy (x int , y int); >>> insert into tbl_xy values (0,0); >>> insert into tbl_xy values (1,1); >>> commit; >>> start transaction; >>> insert into tbl_xy values (2,2); >>> insert into tbl_xy values (3,3); >>> insert into tbl_xy values (4,4); >>> commit; >>> start transaction; >>> insert into tbl_xy values (5,5); >>> insert into tbl_xy values (6,6); >>> insert into tbl_xy values (7,7); >>> commit; >>> insert into tbl_xy values (-1, -100); >>> start transaction; >>> insert into tbl_xy values (8,8); >>> insert into tbl_xy values (9,9); >>> insert into tbl_xy values (10,10); >>> commit; >>> ---------------- >>> Execution of script: >>> macu:~/Desktop alex$ mclient -lsql -umonetdb ~/Desktop/1.sql >>> [ 1 ] >>> [ 1 ] >>> [ 1 ] >>> [ 1 ] >>> [ 1 ] >>> [ 1 ] >>> [ 1 ] >>> [ 1 ] >>> [ 1 ] >>> [ 1 ] >>> [ 1 ] >>> [ 1 ] >>> -------------------- >>> Looking for negative numbers, none found: >>> macu:~/Desktop alex$ mclient -lsql -umonetdb >>> sql>select * from tbl_xy; >>> % sys.tbl_xy, sys.tbl_xy # table_name >>> % x, y # name >>> % int, int # type >>> % 2, 2 # length >>> [ 0, 0 ] >>> [ 1, 1 ] >>> [ 2, 2 ] >>> [ 3, 3 ] >>> [ 4, 4 ] >>> [ 5, 5 ] >>> [ 6, 6 ] >>> [ 7, 7 ] >>> [ 8, 8 ] >>> [ 9, 9 ] >>> [ 10, 10 ] >>> Version: MonetDB Server v5.0.0_beta2_1 >>> BR, Alex >> >

3 2

[Monetdb-developers] usleep not portable
by Sjoerd Mullender 22 May '07

22 May '07

Jennie, you introduced a call to usleep in xrpc_client.mx. How important is that? The problem is, usleep is not portable. For one, it is not a Posix call (use nanosleep instead), and worse (in practice), it's not available on Windows (but neither is nanosleep). On Windows there is Sleep() which takes milliseconds as an argument (unlike sleep which takes seconds, usleep which takes microseconds, and nanosleep which has nanosecond precision). -- Sjoerd Mullender

2 1

[Monetdb-developers] MonetDB5 SQL installer for windows 32....
by Romulo Goncalves 21 May '07

21 May '07

During the installation of MonetDB5 SQL for windows 32 I got an error. The print screen is in the following link: http://homepages.cwi.nl/~goncalve/spool/Picture1.png Regards, Romulo

2 2

Re: [Monetdb-developers] [Monetdb-pf-checkins] pathfinder/runtime pf_support.mx, 1.233, 1.234
by Stefan Manegold 16 May '07

16 May '07

Peter, triggered by --enable-optimize compilation warning about ======== .../pathfinder/runtime/pf_support.mx: In function 'CMDws_bat': .../pathfinder/runtime/pf_support.mx:7122: warning: 'v' may be used uninitialized in this function ======== I changed BAT *v, *b = BBPdescriptor(bid); into BAT *v = 0, *b = BBPdescriptor(bid); in CMDws_bat(), and noticed that CMDws_bat() returns GDK_SUCCEED in any case, now, although *ret is initialized/set only in case b = BBPdescriptor(bid) is non-null. Is this --- i.e., returning GDK_SUCCEED and not initializing *ret in case b = BBPdescriptor(bid) return NULL --- intended / OK? Stefan On Wed, May 16, 2007 at 10:08:57AM +0000, Peter Boncz wrote: > Update of /cvsroot/monetdb/pathfinder/runtime > In directory sc8-pr-cvs16:/tmp/cvs-serv3794 > > Modified Files: > pf_support.mx > Log Message: > [ 1718066 ] PF: put() to /tmp crashes Mserver > - error in error message formatting > > > > Index: pf_support.mx > =================================================================== > RCS file: /cvsroot/monetdb/pathfinder/runtime/pf_support.mx,v > retrieving revision 1.233 > retrieving revision 1.234 > diff -u -d -r1.233 -r1.234 > --- pf_support.mx 16 May 2007 07:55:53 -0000 1.233 > +++ pf_support.mx 16 May 2007 10:08:54 -0000 1.234 > @@ -699,7 +699,7 @@ > } > var absolute := [or](filepath.[startsWith]("/"), filepath.[startsWith]("\\")).uselect(true).mirror().leftfetchjoin(sel); > if (count(absolute) > 0) { > - ERROR("fn_put: file URI '%s' must be a relative path (%d such errors).", backwards.fetch(0), count(backwards)); > + ERROR("fn_put: file URI '%s' must be a relative path (%d such errors).", absolute.fetch(0), count(absolute)); > } > var backwards := filepath.[search]("..").uselect(0,int_nil).mirror().leftfetchjoin(sel); > if (count(backwards) > 0) { > @@ -7118,13 +7118,19 @@ > int CMDws_bat(BAT **ret, lng* wsid) > { > bat bid = *wsid & 1073741823LL; > - BAT *v = NULL; > if (BBPfix(bid)) { > - BAT *b = BBPdescriptor(bid); > + BAT *v, *b = BBPdescriptor(bid); > if (b) *ret = v = VIEWcreate(b); > BBPunfix(bid); > + if (v) { > + /* give the view a name such that lng(bbname(v)) = lng(bbpname(b)) */ > + long_str buf; > + snprintf(buf, sizeof(buf), "%s-%d", BBP_logical(bid), ABS(b->batCacheid)); > + BBPrename(v->batCacheid, buf); > + return GDK_SUCCEED; > + } > } > - return v?GDK_SUCCEED:GDK_FAIL; > + return GDK_SUCCEED; > } > > #include "serialize.h" > > > ------------------------------------------------------------------------- > 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 with Perl in windows
by Steffen Goeldner 16 May '07

16 May '07

Romulo Goncalves wrote: > Hello, > > My name is Romulo (INS-1) and I am trying to create a windows installer > with Perl. My colleagues told me that you are the Perl expert in MonetDB... > > To compile PERL I did: > > install perl in C:\perl_5\ > and unzip the sources in same directory as MonetDB SQL MONETDB5 .... > (The same steps as we should do for php} > > In the MonetDB\conf\rules.msc I added: > > PERL_SRCDIR = $(TOPDIR)\..\..\perl-5.8.8 > PERL_INSTDIR = C:\perl-5 > # for these, also see configure.py > PERL_EXTENSIONDIR = lib\perl5 > > Note: I am compiling for M5 and sql from cvs branch. > > For the compilation I set the flag HAVE_PERL=1. > > Everything compiled. > > Now I need to know which files I have to add to the installer. > I was looking for a perl lib in cliens\NT\lib\ and It does not have such > lib. > > Could you help me a bit please? First and foremost, let me admit that I did not find time to implement the new protocol (8) yet - thus the perl modules may not work for M5 (at least the pure perl (MapiPP) client). Anyway, this has nothing to do with the installation procedure. In the spirit of Perl’s motto, "There’s More Than One Way To Do It" (TMTOWTDI), there are many perl modules in clients/src/perl: - Mapi.pm is a simple pure perl client, maintained by CWI and works (AFAIK) with the current protocol - MapiLib (in Cimpl) is a wrapper around libMapi and you need SWIG to build it - The modules in MonetDB-CLI* are maintained by me: - MonetDB::CLI::MapiPP is pure perl - MonetDB::CLI::MapiLib is pure perl but uses MapiLib - MonetDB::CLI::MapiXS is a XS (that is: C) wrapper around libMapi - MonetDB::CLI is a simple loader for one of the MonetDB::CLI::* modules above - DBD::monetdb (in DBD) is a DBI client on top of MonetDB::CLI In general, you install a perl module in the following way: perl Makefile.PL make make test make install In this way, perl saves you from all the drudgery. Installing by hand is easy for pure perl modules (though not recommended): simple copy all *.pm into your perl lib directory. Example (MonetDB::CLI::MapiPP): MonetDB-CLI-MapiPP/MapiPP.pm -> /perl/site/lib/MonetDB/CLI/MapiPP.pm (assuming /perl/site/lib is in the lib search path - try 'perl -V' and look for @INC and PERL5LIB. Later, if you try to load MonetDB::CLI::MapiPP, perl replaces '::' with '/', adds .pm and looks in every path from @INC.) However, installing an extension module (XS or SWIG) is difficult! Perl builds additional files (e.g. .dll) which have to be installed into different places. Best you call the standard 'make install' from the installer or at least watch what 'make install' would do. Regards, Steffen

2 5