- users-list - monetdb.org

[MonetDB-users] Granting TMP Table Creation Privileges to User
by Reeves, Matthew J. 30 Nov '10

30 Nov '10

I'm not sure what I'm missing but how does one grant permissions to a user to create temporary tables? I'm totally stumped. Thanks, Matt

1 0

[MonetDB-users] issue with concurrent access to MonetDB/SQL via JDBC
by Wouter Alink 26 Nov '10

26 Nov '10

Dear users, I'm currently struggling with concurrent access to MonetDB/SQL via JDBC. Version: MonetDB server v5.20.4 (64-bit), based on kernel v1.38.4 (64-bit oids). I might still have some concurrency issues with my own code, but somehow I frequently end up with the following error message: (while stress-testing by querying with 10 threads at the same time) class java.sql.SQLException: TypeException:user.s3_1[448]:'user.contains' undefined in: _1933:any := user.contains(_1929:str, _1931:str, _474:bit) TypeException:user.s3_1[449]:'bat.insert' undefined in: _1934:any := bat.insert(_1923:bat[:oid,:bit], _1928:oid, _1933:any) TypeException:user.s3_1[645]:'user.contains' undefined in: _1946:any := user.contains(_1942:str, _1944:str, _474:bit) TypeException:user.s3_1[646]:'bat.insert' undefined in: _1947:any := bat.insert(_1938:bat[:oid,:bit], _1941:oid, _1946:any) TypeException:user.s3_1[1042]:'user.contains' undefined in: _1959:any := user.contains(_1955:str, _1957:str, _474:bit) TypeException:user.s3_1[1043]:'bat.insert' undefined in: _1960:any := bat.insert(_1951:bat[:oid,:bit], _1954:oid, _1959:any) TypeException:user.s3_1[1226]:'user.contains' undefined in: _1974:any := user.contains(_1970:str, _1972:str, _474:bit) TypeException:user.s3_1[1227]:'bat.insert' undefined in: _1975:any := bat.insert(_1964:bat[:oid,:bit], _1969:oid, _1974:any) SQLException:SQLengine:Program contains errors nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.executeQuery(MonetConnection.java:2209) nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.processQuery(MonetConnection.java:1968) nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:506) nl.cwi.monetdb.jdbc.MonetStatement.execute(MonetStatement.java:347) nl.cwi.monetdb.jdbc.MonetStatement.executeUpdate(MonetStatement.java:542) Does anyone else have experienced such error messages before, or does anyone have a clue to where to look? (like too many open connections, concurrent access of the same connection, querying a closed connection, or perhaps a bug inside monetdb)? Thanks, Wouter

2 1

[MonetDB-users] MonetDB Debain and RDF
by Andreas Harth 25 Nov '10

25 Nov '10

Hi, I'd like to use Lefteris' RDF package on Debian. What do I have to do to create and connect to a database as user on Debian? I've installed the following packages: # dpkg -l | grep -e monetdb ii libmonetdb-client1 1.40.1-20101110 MonetDB database client libraries ii libmonetdb1 1.40.1-20101110 database system for high-performance applications, libraries ii libmonetdb5-server5 5.22.1-20101110 MonetDB database server version 5, libraries ii libmonetdb5-sql2 2.40.1-20101110 MonetDB SQL libraries for monetdb5-server ii monetdb-client 1.40.1-20101110 MonetDB database client ii monetdb5-server 5.22.1-20101110 MonetDB database server version 5 ii monetdb5-sql 2.40.1-20101110 MonetDB SQL support for monetdb5 I can start MonetDB: # /etc/init.d/monetdb5-sql start Starting MonetDB SQL server: merovingian. When I try do create the tables (as a user): $ mclient -lsql create_tables.sql user(aharth): password: merovingian: please specify a database $ $ mclient -lsql create_tables.sql -d demo user(aharth): password: merovingian: internal error while starting mserver, please refer to the logs $ The log says: 2010-11-25 16:20:19 MSG merovingian[3685]: starting database 'demo', up min/avg/max: 3s/4s/5s, crash average: 0.00 0.00 0.00 (2-2=0) 2010-11-25 16:20:19 ERR merovingian[3685]: client error: cannot start database 'demo': no .vaultkey found (did you create the database with `monetdb create demo`?) I'm stuck here. How can I create a database as a user? $ monetdb create demo2 permission denied $ As root, I only can create a database in maintainance mode: # monetdb create demo2 created database in maintenance mode: demo2 # Any pointers to howto's that'll help? Cheers, Andreas.

3 5

Re: [MonetDB-users] Querying date type column in MonetDB
by Stefan Manegold 23 Nov '10

23 Nov '10

I see --- if you consider it a bug, please file a detailed bug report including information & instructions to reporduce the problem as well as infornmation about the exact MonetDB version and OS you're using via http://bugs.MonetDB.org/ Stefan ----- Oorspronkelijk bericht ----- Van: Freddy Priyatna <freddy.priyatna(a)gmail.com> Verzonden: maandag 25 oktober 2010 16:32 Aan: Communication channel for MonetDB users <monetdb-users(a)lists.sourceforge.net> Onderwerp: Re: [MonetDB-users] Querying date type column in MonetDB Hi Stefan, Nope, the name of the column is "deliveryDays" :) Freddy 2010/10/25 Stefan Manegold <Stefan.Manegold(a)cwi.nl> > Hi Freddy, > > I don't think that the error you experience is triggered by the column > type, but rather by the fact that your date column ha? a name - say "date" - > that is a reserved key word in SQL an hence needs to be double-quoted > according to the SQL standard (this is not a MonetDB specific choice, but a > "feature" of the SQL standard) --- not knowing your table & column names, I > can only guess, though ... > > Stefan > > > ----- Oorspronkelijk bericht ----- > Van: Freddy Priyatna <freddy.priyatna(a)gmail.com> > Verzonden: maandag 25 oktober 2010 16:03 > Aan: MonetDB-users <monetdb-users(a)lists.sourceforge.net> > Onderwerp: [MonetDB-users] Querying date type column in MonetDB > > Dear All, > > I am new to MonetDB, so most likely my question will look obvious. > > I would like to ask, how can columns with date type is queried in monetdb. > Based on my experience, it seems that date type columns need special > treatment. It seems that the only way to query them is with the syntax > "column_name" while other columns seems to work with the format > table_name.column_name without the need of double quote. When I tried to > query date column with the syntax table_name.column_name, it gave me an > error "no such column" > > So my question is, is it true that the only way to query date columns is > using "column_name" format? Another question will be, what happen if I need > to query same name columns coming from different table? > > Thanks in advance, > Freddy > > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America > contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in > marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > MonetDB-users mailing list > MonetDB-users(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/monetdb-users >

4 6

[MonetDB-users] Copy into issues with mixed ascii / hex data
by paulr135 23 Nov '10

23 Nov '10

I have a tab-delimited data file that is mostly ascii, but has a few hex characters in it. For example: ... 3263640152 ABC<99> ... where <99> is a hex value for (tm) - trademark. When I try and load this data file into monetdb, I get the following error: [root@bidbtest ~]# /usr/local/MonetDB/bin/mclient -lsql --database=myschema -t -s "COPY 20603 records into test_table from '/tmp/testdata.txt' using delimiters '\t','\n','\"' null as '';" user(root):monetdb password: MAPI = (monetdb) /usr/local/MonetDB/var/MonetDB5/dbfarm/mapi_socket QUERY = COPY 20603 records into test_table from '/tmp/testdata.txt' using delimiters '\t','\n','"' null as ''; ERROR = !SQLException:importTable:value 'failed to import table Timer 790.415 msec The table def is: CREATE TABLE creative_dim ( id bigint NOT NULL, headline varchar(100) DEFAULT NULL ) How can I go about loading this file? Ideally, I would like to get these characters loaded as is. I saw that mclient has a -E flag that accepts an encoding type. However, I'm not sure what to set it to for a file with ascii / hex data. A complicating factor is that I don't know all the hex characters that are in my file. I luckily spotted the <99>/tm one above as it was one of the first lines in the file. But after replacing all instances of that character with the empty string, I still get a similar error to what I pasted above. I manually paged through the file and found different hex characters. It isn't practical for me to page through an entire file and monetdb doesn't tell me which line number the problem is on. By the way, I am using MonetDB v5.20.5. Thanks for the help! -- View this message in context: http://old.nabble.com/Copy-into-issues-with-mixed-ascii---hex-data-tp302389… Sent from the monetdb-users mailing list archive at Nabble.com.

2 3

[MonetDB-users] compiling from hg
by Dean Serenevy 18 Nov '10

18 Nov '10

Hello, I am attempting to compile from mercurial sources. I have tried from the Oct2010_1 tag as well as tip and both error out at the same point (I ran de-bootstrap between attempts). As far as I can tell i have all prerequisites installed. Full command output is included at the end of the message. Can anyone tell me what I am doing wrong? Thaks, Dean [MonetDB.hg/buildtools] (hg:default)$ hg update tip 0 files updated, 0 files merged, 0 files removed, 0 files unresolved [MonetDB.hg/buildtools] (hg:default)$ ./bootstrap [MonetDB.build/buildtools]$ ../MonetDB.hg/buildtools/configure --prefix=/opt/MonetDB --enable-burg --enable-mel --enable-debug=no --enable-assert=no --enable-optimize=yes [MonetDB.build/buildtools]$ make -j4 ... g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT mel.yy.o -MD -MP -MF .deps/mel.yy.Tpo -c -o mel.yy.o mel.yy.cc y.tab.c:178:1: warning: "MEL_MODULE" redefined In file included from /home/duelafn/MonetDB.hg/buildtools/mel/command.h:26, from /home/duelafn/MonetDB.hg/buildtools/mel/mel.yy:47: /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:1:1: warning: this is the location of the previous definition y.tab.c:179:1: warning: "MEL_PRELUDE" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:2:1: warning: this is the location of the previous definition y.tab.c:180:1: warning: "MEL_EPILOGUE" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:3:1: warning: this is the location of the previous definition y.tab.c:181:1: warning: "MEL_END" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:4:1: warning: this is the location of the previous definition y.tab.c:182:1: warning: "MEL_COMMAND" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:5:1: warning: this is the location of the previous definition y.tab.c:183:1: warning: "MEL_OPERATOR0" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:6:1: warning: this is the location of the previous definition y.tab.c:184:1: warning: "MEL_OPERATOR" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:7:1: warning: this is the location of the previous definition y.tab.c:185:1: warning: "MEL_OPERATOR1" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:8:1: warning: this is the location of the previous definition y.tab.c:186:1: warning: "MEL_FIXEDATOM" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:9:1: warning: this is the location of the previous definition y.tab.c:187:1: warning: "MEL_ATOM" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:10:1: warning: this is the location of the previous definition y.tab.c:188:1: warning: "MEL_USE" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:11:1: warning: this is the location of the previous definition y.tab.c:189:1: warning: "MEL_ATOMOP" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:12:1: warning: this is the location of the previous definition y.tab.c:190:1: warning: "MEL_STRING" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:13:1: warning: this is the location of the previous definition y.tab.c:191:1: warning: "MEL_IDENTIFIER" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:14:1: warning: this is the location of the previous definition y.tab.c:192:1: warning: "MEL_USED" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:15:1: warning: this is the location of the previous definition y.tab.c:193:1: warning: "MEL_NUMBER" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:16:1: warning: this is the location of the previous definition y.tab.c:194:1: warning: "MEL_ANY" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:17:1: warning: this is the location of the previous definition y.tab.c:195:1: warning: "MEL_BAT" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:18:1: warning: this is the location of the previous definition y.tab.c:196:1: warning: "MEL_TYPE" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:19:1: warning: this is the location of the previous definition y.tab.c:197:1: warning: "MEL_VOID" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:20:1: warning: this is the location of the previous definition y.tab.c:198:1: warning: "MEL_BUILTIN" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:21:1: warning: this is the location of the previous definition y.tab.c:199:1: warning: "MEL_OBJECT" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:22:1: warning: this is the location of the previous definition y.tab.c:200:1: warning: "MEL_VARARGS" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:23:1: warning: this is the location of the previous definition y.tab.c:201:1: warning: "MEL_SEP" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:24:1: warning: this is the location of the previous definition y.tab.c:202:1: warning: "MEL_ITERATOR" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:25:1: warning: this is the location of the previous definition mv -f .deps/glue.Tpo .deps/glue.Po g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT mil.o -MD -MP -MF .deps/mil.Tpo -c -o mil.o mil.cc y.tab.c:150: error: expected identifier before numeric constant y.tab.c:150: error: expected ‘}’ before numeric constant y.tab.c:150: error: expected unqualified-id before numeric constant y.tab.c:175: error: expected declaration before ‘}’ token make[3]: *** [mel.tab.o] Error 1 make[3]: *** Waiting for unfinished jobs.... mv -f .deps/mel.Tpo .deps/mel.Po mv -f .deps/mil.Tpo .deps/mil.Po mv -f .deps/mel.yy.Tpo .deps/mel.yy.Po make[3]: Leaving directory `/home/duelafn/MonetDB.build/mel' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/duelafn/MonetDB.build/mel' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/duelafn/MonetDB.build' make: *** [all] Error 2 FULL COMMAND OUTPUT [MonetDB.hg/buildtools] (hg:default)$ ./bootstrap configure.ac:24: installing `./install-sh' configure.ac:24: installing `./missing' Makefile.am: installing `./depcomp' configure.ac:24: installing `./install-sh' configure.ac:24: installing `./missing' Makefile.am: installing `./depcomp' configure.ac:24: installing `./install-sh' configure.ac:24: installing `./missing' Makefile.am: installing `./depcomp' configure.ac:25: installing `./install-sh' configure.ac:25: installing `./missing' [MonetDB.build/buildtools]$ ../MonetDB.hg/buildtools/configure --prefix=/opt/MonetDB --enable-burg --enable-mel --enable-debug=no --enable-assert=no --enable-optimize=yes checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for python... /usr/bin/python configure: WARNING: unrecognized options: --enable-burg, --enable-mel, --enable-debug, --enable-assert, --enable-optimize checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make sets $(MAKE)... (cached) yes checking for g++... g++ checking whether the C++ compiler works... yes checking for C++ compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for style of include used by make... GNU checking dependency style of g++... gcc3 checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking for lockfile... echo checking for flex... flex checking lex output file root... lex.yy checking lex library... -lfl checking whether yytext is a pointer... yes checking for bison... bison -y checking whether ln -s works... yes checking for rm... rm -f checking for mv... mv -f checking for flex version... flex 2.5.35 checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking whether time.h and sys/time.h may both be included... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking malloc.h usability... yes checking malloc.h presence... yes checking for malloc.h... yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking for unistd.h... (cached) yes checking for iostream... yes checking for cstdio... yes checking for an ANSI C-conforming const... yes checking for inline... inline checking for size_t... yes checking for stdlib.h... (cached) yes checking for GNU libc compatible malloc... yes checking for memset... yes checking for strchr... yes checking for strdup... yes checking for strrchr... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mel_config.h config.status: executing depfiles commands configure: WARNING: unrecognized options: --enable-burg, --enable-mel, --enable-debug, --enable-assert, --enable-optimize configure: creating ./config.status config.status: creating Makefile config.status: creating autogen/Makefile config.status: creating conf/Makefile config.status: creating conf/Mbootstrap config.status: creating conf/buildtools-config config.status: creating dummy.h === configuring in Mx (/home/duelafn/MonetDB.build/Mx) configure: running /bin/bash ../../MonetDB.hg/buildtools/Mx/configure --disable-option-checking '--prefix=/opt/MonetDB' '--enable-burg' '--enable-mel' '--enable-debug=no' '--enable-assert=no' '--enable-optimize=yes' --cache-file=/dev/null --srcdir=../../MonetDB.hg/buildtools/Mx checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for bash... /bin/bash checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking getopt.h usability... yes checking getopt.h presence... yes checking for getopt.h... yes checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking stddef.h usability... yes checking stddef.h presence... yes checking for stddef.h... yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for unistd.h... (cached) yes checking utime.h usability... yes checking utime.h presence... yes checking for utime.h... yes checking whether stat file-mode macros are broken... no checking for an ANSI C-conforming const... yes checking for size_t... yes checking for ptrdiff_t... yes checking for stdlib.h... (cached) yes checking for GNU libc compatible malloc... yes checking for stdlib.h... (cached) yes checking for GNU libc compatible realloc... yes checking whether lstat correctly handles trailing slash... yes checking whether stat accepts an empty string... no checking for utime.h... (cached) yes checking whether utime accepts a null argument... yes checking for vprintf... yes checking for _doprnt... no checking for memset... yes checking for mkdir... yes checking for strchr... yes checking for strcspn... yes checking for strrchr... yes checking for strstr... yes checking for utime... yes checking whether getopt is declared... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mx_config.h config.status: executing depfiles commands === configuring in burg (/home/duelafn/MonetDB.build/burg) configure: running /bin/bash ../../MonetDB.hg/buildtools/burg/configure --disable-option-checking '--prefix=/opt/MonetDB' '--enable-burg' '--enable-mel' '--enable-debug=no' '--enable-assert=no' '--enable-optimize=yes' --cache-file=/dev/null --srcdir=../../MonetDB.hg/buildtools/burg checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for flex... flex checking lex output file root... lex.yy checking lex library... -lfl checking whether yytext is a pointer... yes checking for bison... bison -y checking for lockfile... echo checking for rm... rm -f checking for mv... mv -f checking for flex version... flex 2.5.35 checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking stdbool.h usability... yes checking stdbool.h presence... yes checking for stdbool.h... yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for stdbool.h that conforms to C99... (cached) yes checking for _Bool... yes checking for an ANSI C-conforming const... yes checking for size_t... yes checking for long long... yes checking for __int64... no checking size of void *... 8 checking size of int... 4 checking size of long... 8 checking size of long long... 8 checking size of __int64... 0 checking for stdlib.h... (cached) yes checking for GNU libc compatible malloc... yes checking for memset... yes checking for strdup... yes configure: creating ./config.status config.status: creating Makefile config.status: creating burg_config.h config.status: executing depfiles commands [MonetDB.build/buildtools]$ make -j4 (CDPATH="${ZSH_VERSION+.}:" && cd ../MonetDB.hg/buildtools && /bin/bash /home/duelafn/MonetDB.hg/buildtools/missing --run autoheader) rm -f stamp-h1 touch ../MonetDB.hg/buildtools/dummy.h.in cd . && /bin/bash ./config.status dummy.h config.status: creating dummy.h config.status: dummy.h is unchanged /usr/bin/make all-recursive make[1]: Entering directory `/home/duelafn/MonetDB.build' Making all in autogen make[2]: Entering directory `/home/duelafn/MonetDB.build/autogen' mkdir -p /home/duelafn/MonetDB.build/autogen/autogen cp ../../MonetDB.hg/buildtools/autogen/setup.py /home/duelafn/MonetDB.build/autogen/setup.py cp ../../MonetDB.hg/buildtools/autogen/autogen.py /home/duelafn/MonetDB.build/autogen/autogen.py cp ../../MonetDB.hg/buildtools/autogen/autogen/am.py /home/duelafn/MonetDB.build/autogen/autogen/am.py cp ../../MonetDB.hg/buildtools/autogen/autogen/msc.py /home/duelafn/MonetDB.build/autogen/autogen/msc.py cp ../../MonetDB.hg/buildtools/autogen/autogen/var.py /home/duelafn/MonetDB.build/autogen/autogen/var.py cp ../../MonetDB.hg/buildtools/autogen/autogen/codegen.py /home/duelafn/MonetDB.build/autogen/autogen/codegen.py cp ../../MonetDB.hg/buildtools/autogen/autogen/__init__.py /home/duelafn/MonetDB.build/autogen/autogen/__init__.py /usr/bin/python setup.py build running build running build_py creating build creating build/lib.linux-x86_64-2.6 creating build/lib.linux-x86_64-2.6/autogen copying autogen/var.py -> build/lib.linux-x86_64-2.6/autogen copying autogen/codegen.py -> build/lib.linux-x86_64-2.6/autogen copying autogen/__init__.py -> build/lib.linux-x86_64-2.6/autogen copying autogen/am.py -> build/lib.linux-x86_64-2.6/autogen copying autogen/msc.py -> build/lib.linux-x86_64-2.6/autogen running build_scripts creating build/scripts-2.6 copying and adjusting autogen.py -> build/scripts-2.6 changing mode of build/scripts-2.6/autogen.py from 644 to 755 make[2]: Leaving directory `/home/duelafn/MonetDB.build/autogen' Making all in Mx make[2]: Entering directory `/home/duelafn/MonetDB.build/Mx' (CDPATH="${ZSH_VERSION+.}:" && cd ../../MonetDB.hg/buildtools/Mx && /bin/bash /home/duelafn/MonetDB.hg/buildtools/Mx/missing --run autoheader) rm -f stamp-h1 touch ../../MonetDB.hg/buildtools/Mx/mx_config.h.in cd . && /bin/bash ./config.status mx_config.h config.status: creating mx_config.h config.status: mx_config.h is unchanged /usr/bin/make all-am make[3]: Entering directory `/home/duelafn/MonetDB.build/Mx' gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT Mx.o -MD -MP -MF .deps/Mx.Tpo -c -o Mx.o ../../MonetDB.hg/buildtools/Mx/Mx.c gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT Def.o -MD -MP -MF .deps/Def.Tpo -c -o Def.o ../../MonetDB.hg/buildtools/Mx/Def.c gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT Form.o -MD -MP -MF .deps/Form.Tpo -c -o Form.o ../../MonetDB.hg/buildtools/Mx/Form.c gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT Tok.o -MD -MP -MF .deps/Tok.Tpo -c -o Tok.o ../../MonetDB.hg/buildtools/Mx/Tok.c mv -f .deps/Mx.Tpo .deps/Mx.Po mv -f .deps/Tok.Tpo .deps/Tok.Po gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT Code.o -MD -MP -MF .deps/Code.Tpo -c -o Code.o ../../MonetDB.hg/buildtools/Mx/Code.c gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT Display.o -MD -MP -MF .deps/Display.Tpo -c -o Display.o ../../MonetDB.hg/buildtools/Mx/Display.c mv -f .deps/Form.Tpo .deps/Form.Po gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT Print.o -MD -MP -MF .deps/Print.Tpo -c -o Print.o ../../MonetDB.hg/buildtools/Mx/Print.c mv -f .deps/Display.Tpo .deps/Display.Po gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT Io.o -MD -MP -MF .deps/Io.Tpo -c -o Io.o ../../MonetDB.hg/buildtools/Mx/Io.c mv -f .deps/Def.Tpo .deps/Def.Po gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT Sys.o -MD -MP -MF .deps/Sys.Tpo -c -o Sys.o ../../MonetDB.hg/buildtools/Mx/Sys.c mv -f .deps/Print.Tpo .deps/Print.Po gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT disclaimer.o -MD -MP -MF .deps/disclaimer.Tpo -c -o disclaimer.o ../../MonetDB.hg/buildtools/Mx/disclaimer.c mv -f .deps/Code.Tpo .deps/Code.Po mv -f .deps/Sys.Tpo .deps/Sys.Po mv -f .deps/disclaimer.Tpo .deps/disclaimer.Po mv -f .deps/Io.Tpo .deps/Io.Po gcc -g -O2 -o Mx Mx.o Def.o Form.o Tok.o Code.o Display.o Print.o Io.o Sys.o disclaimer.o make[3]: Leaving directory `/home/duelafn/MonetDB.build/Mx' make[2]: Leaving directory `/home/duelafn/MonetDB.build/Mx' Making all in mel make[2]: Entering directory `/home/duelafn/MonetDB.build/mel' (CDPATH="${ZSH_VERSION+.}:" && cd /home/duelafn/MonetDB.hg/buildtools/mel && /bin/bash /home/duelafn/MonetDB.hg/buildtools/mel/missing --run autoheader) rm -f stamp-h1 touch /home/duelafn/MonetDB.hg/buildtools/mel/mel_config.h.in cd . && /bin/bash ./config.status mel_config.h config.status: creating mel_config.h config.status: mel_config.h is unchanged /usr/bin/make all-am make[3]: Entering directory `/home/duelafn/MonetDB.build/mel' ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/any_arg.mx /home/duelafn/MonetDB.hg/buildtools/mel/any_arg.mx: ./any_arg.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/atom_arg.mx ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/atom.mx ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/atomops.mx /home/duelafn/MonetDB.hg/buildtools/mel/atom_arg.mx: ./atom_arg.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/bat_arg.mx /home/duelafn/MonetDB.hg/buildtools/mel/atom.mx: ./atom.cc - created /home/duelafn/MonetDB.hg/buildtools/mel/atomops.mx: ./atomops.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/builtin.mx ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/command.mx /home/duelafn/MonetDB.hg/buildtools/mel/bat_arg.mx: ./bat_arg.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/debug.mx ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/depend.mx /home/duelafn/MonetDB.hg/buildtools/mel/builtin.mx: ./builtin.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/dependency.mx /home/duelafn/MonetDB.hg/buildtools/mel/command.mx: ./command.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/epilogue.mx /home/duelafn/MonetDB.hg/buildtools/mel/debug.mx: ./debug.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/FileInfo.mx /home/duelafn/MonetDB.hg/buildtools/mel/depend.mx: ./depend.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/glue.mx /home/duelafn/MonetDB.hg/buildtools/mel/dependency.mx: ./dependency.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/html.mx /home/duelafn/MonetDB.hg/buildtools/mel/epilogue.mx: ./epilogue.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/iterator.mx /home/duelafn/MonetDB.hg/buildtools/mel/FileInfo.mx: ./FileInfo.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/link.mx /home/duelafn/MonetDB.hg/buildtools/mel/html.mx: ./html.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/ListIterator.mx /home/duelafn/MonetDB.hg/buildtools/mel/iterator.mx: ./iterator.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/mel.mx /home/duelafn/MonetDB.hg/buildtools/mel/ListIterator.mx: ./ListIterator.cc - created echo waiting /home/duelafn/MonetDB.hg/buildtools/mel/link.mx: ./link.cc - created flex /home/duelafn/MonetDB.hg/buildtools/mel/mel.ll waiting bison -y -d /home/duelafn/MonetDB.hg/buildtools/mel/mel.yy || { rm -f waiting ; exit 1 ; } /home/duelafn/MonetDB.hg/buildtools/mel/mel.mx: ./mel.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/mil.mx /home/duelafn/MonetDB.hg/buildtools/mel/glue.mx: ./glue.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/module.mx /home/duelafn/MonetDB.hg/buildtools/mel/mil.mx: ./mil.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/object.mx /home/duelafn/MonetDB.hg/buildtools/mel/module.mx: ./module.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/operator.mx conflicts: 32 reduce/reduce /home/duelafn/MonetDB.hg/buildtools/mel/object.mx: ./object.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/ops.mx /home/duelafn/MonetDB.hg/buildtools/mel/operator.mx: ./operator.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/prelude.mx /home/duelafn/MonetDB.hg/buildtools/mel/prelude.mx: ./prelude.cc - created /home/duelafn/MonetDB.hg/buildtools/mel/ops.mx: ./ops.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/proto.mx ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/symbol.mx if [ -f lex.yy.c ]; then mv lex.yy.c mel.yy.cc ; fi /home/duelafn/MonetDB.hg/buildtools/mel/proto.mx: ./proto.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/symtable.mx /home/duelafn/MonetDB.hg/buildtools/mel/symbol.mx: ./symbol.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/type_arg.mx mv mel.yy.cc mel.yy.cc.tmp /home/duelafn/MonetDB.hg/buildtools/mel/symtable.mx: ./symtable.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/use.mx /home/duelafn/MonetDB.hg/buildtools/mel/type_arg.mx: ./type_arg.cc - created ../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/var_arg.mx /home/duelafn/MonetDB.hg/buildtools/mel/use.mx: ./use.cc - created echo '#include <'"mel_config.h"'>' > mel.yy.cc grep -v '^#include.*[<"]'"mel_config.h"'[">]' mel.yy.cc.tmp >> mel.yy.cc g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT any_arg.o -MD -MP -MF .deps/any_arg.Tpo -c -o any_arg.o any_arg.cc /home/duelafn/MonetDB.hg/buildtools/mel/var_arg.mx: ./var_arg.cc - created g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT atom_arg.o -MD -MP -MF .deps/atom_arg.Tpo -c -o atom_arg.o atom_arg.cc rm -f mel.yy.cc.tmp g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT atom.o -MD -MP -MF .deps/atom.Tpo -c -o atom.o atom.cc if [ -f y.tab.c ]; then mv y.tab.c mel.tab.cc ; fi rm -f waiting g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT atomops.o -MD -MP -MF .deps/atomops.Tpo -c -o atomops.o atomops.cc mv -f .deps/atom.Tpo .deps/atom.Po g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT bat_arg.o -MD -MP -MF .deps/bat_arg.Tpo -c -o bat_arg.o bat_arg.cc mv -f .deps/any_arg.Tpo .deps/any_arg.Po g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT builtin.o -MD -MP -MF .deps/builtin.Tpo -c -o builtin.o builtin.cc mv -f .deps/atom_arg.Tpo .deps/atom_arg.Po g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT command.o -MD -MP -MF .deps/command.Tpo -c -o command.o command.cc mv -f .deps/atomops.Tpo .deps/atomops.Po g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT debug.o -MD -MP -MF .deps/debug.Tpo -c -o debug.o debug.cc mv -f .deps/bat_arg.Tpo .deps/bat_arg.Po g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT depend.o -MD -MP -MF .deps/depend.Tpo -c -o depend.o depend.cc mv -f .deps/builtin.Tpo .deps/builtin.Po g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT dependency.o -MD -MP -MF .deps/dependency.Tpo -c -o dependency.o dependency.cc mv -f .deps/command.Tpo .deps/command.Po g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT epilogue.o -MD -MP -MF .deps/epilogue.Tpo -c -o epilogue.o epilogue.cc mv -f .deps/debug.Tpo .deps/debug.Po g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT FileInfo.o -MD -MP -MF .deps/FileInfo.Tpo -c -o FileInfo.o FileInfo.cc mv -f .deps/depend.Tpo .deps/depend.Po g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT glue.o -MD -MP -MF .deps/glue.Tpo -c -o glue.o glue.cc mv -f .deps/dependency.Tpo .deps/dependency.Po g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT html.o -MD -MP -MF .deps/html.Tpo -c -o html.o html.cc mv -f .deps/epilogue.Tpo .deps/epilogue.Po g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT iterator.o -MD -MP -MF .deps/iterator.Tpo -c -o iterator.o iterator.cc mv -f .deps/FileInfo.Tpo .deps/FileInfo.Po g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT link.o -MD -MP -MF .deps/link.Tpo -c -o link.o link.cc mv -f .deps/iterator.Tpo .deps/iterator.Po g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT ListIterator.o -MD -MP -MF .deps/ListIterator.Tpo -c -o ListIterator.o ListIterator.cc mv -f .deps/ListIterator.Tpo .deps/ListIterator.Po g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT mel.o -MD -MP -MF .deps/mel.Tpo -c -o mel.o mel.cc mv -f .deps/html.Tpo .deps/html.Po g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT mel.tab.o -MD -MP -MF .deps/mel.tab.Tpo -c -o mel.tab.o mel.tab.cc mv -f .deps/link.Tpo .deps/link.Po g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT mel.yy.o -MD -MP -MF .deps/mel.yy.Tpo -c -o mel.yy.o mel.yy.cc y.tab.c:178:1: warning: "MEL_MODULE" redefined In file included from /home/duelafn/MonetDB.hg/buildtools/mel/command.h:26, from /home/duelafn/MonetDB.hg/buildtools/mel/mel.yy:47: /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:1:1: warning: this is the location of the previous definition y.tab.c:179:1: warning: "MEL_PRELUDE" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:2:1: warning: this is the location of the previous definition y.tab.c:180:1: warning: "MEL_EPILOGUE" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:3:1: warning: this is the location of the previous definition y.tab.c:181:1: warning: "MEL_END" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:4:1: warning: this is the location of the previous definition y.tab.c:182:1: warning: "MEL_COMMAND" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:5:1: warning: this is the location of the previous definition y.tab.c:183:1: warning: "MEL_OPERATOR0" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:6:1: warning: this is the location of the previous definition y.tab.c:184:1: warning: "MEL_OPERATOR" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:7:1: warning: this is the location of the previous definition y.tab.c:185:1: warning: "MEL_OPERATOR1" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:8:1: warning: this is the location of the previous definition y.tab.c:186:1: warning: "MEL_FIXEDATOM" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:9:1: warning: this is the location of the previous definition y.tab.c:187:1: warning: "MEL_ATOM" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:10:1: warning: this is the location of the previous definition y.tab.c:188:1: warning: "MEL_USE" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:11:1: warning: this is the location of the previous definition y.tab.c:189:1: warning: "MEL_ATOMOP" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:12:1: warning: this is the location of the previous definition y.tab.c:190:1: warning: "MEL_STRING" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:13:1: warning: this is the location of the previous definition y.tab.c:191:1: warning: "MEL_IDENTIFIER" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:14:1: warning: this is the location of the previous definition y.tab.c:192:1: warning: "MEL_USED" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:15:1: warning: this is the location of the previous definition y.tab.c:193:1: warning: "MEL_NUMBER" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:16:1: warning: this is the location of the previous definition y.tab.c:194:1: warning: "MEL_ANY" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:17:1: warning: this is the location of the previous definition y.tab.c:195:1: warning: "MEL_BAT" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:18:1: warning: this is the location of the previous definition y.tab.c:196:1: warning: "MEL_TYPE" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:19:1: warning: this is the location of the previous definition y.tab.c:197:1: warning: "MEL_VOID" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:20:1: warning: this is the location of the previous definition y.tab.c:198:1: warning: "MEL_BUILTIN" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:21:1: warning: this is the location of the previous definition y.tab.c:199:1: warning: "MEL_OBJECT" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:22:1: warning: this is the location of the previous definition y.tab.c:200:1: warning: "MEL_VARARGS" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:23:1: warning: this is the location of the previous definition y.tab.c:201:1: warning: "MEL_SEP" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:24:1: warning: this is the location of the previous definition y.tab.c:202:1: warning: "MEL_ITERATOR" redefined /home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:25:1: warning: this is the location of the previous definition mv -f .deps/glue.Tpo .deps/glue.Po g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT mil.o -MD -MP -MF .deps/mil.Tpo -c -o mil.o mil.cc y.tab.c:150: error: expected identifier before numeric constant y.tab.c:150: error: expected ‘}’ before numeric constant y.tab.c:150: error: expected unqualified-id before numeric constant y.tab.c:175: error: expected declaration before ‘}’ token make[3]: *** [mel.tab.o] Error 1 make[3]: *** Waiting for unfinished jobs.... mv -f .deps/mel.Tpo .deps/mel.Po mv -f .deps/mil.Tpo .deps/mil.Po mv -f .deps/mel.yy.Tpo .deps/mel.yy.Po make[3]: Leaving directory `/home/duelafn/MonetDB.build/mel' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/duelafn/MonetDB.build/mel' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/duelafn/MonetDB.build' make: *** [all] Error 2

3 7

[MonetDB-users] Large Database / Is there hope?
by Dean Serenevy 18 Nov '10

18 Nov '10

Hello, I am still having problems compiling from sources, however, I would like to determine whether these is hope in continuing. We have a corpus of about 18,000 documents averaging about 5000 words each. We additionally have stand-off annotations that we would like to add and query against. This totals about 300 million XML elements. We are running 64-bit Linux with 6GiB RAM. Database A: Loading the documents (in batches of 100) as separate collections takes about 30 min and consumes 30GiB disk space in var/MonetDB4/dbfarm. Simple queries against database A take a long time, consume only 5% CPU and heavily work kswapd count( for $d in pf:documents-unsafe() return doc($d)/tCorpus ) # killed after1 hour Database B: Loading the documents (in batches of 100) into a single huge collection takes about 6 hours and consumes 120GiB disk space in var/MonetDB4/dbfarm. Simple queries against Database B take a long time, consume only 5% CPU and heavily work pdflush count( pf:collection("tcorpus")//tCorpus ) # killed after 3 hours My questions: 1. Is there any hope of successfully performing non-trivial queries on either of these databases using MonetDB? 2. If so, Is loading into a single collection or separate collections likely to be preferable? 3. The above work was done using the Jun2010-SP2 SuperBall, which is the only version I have been able to compile. Has any relevant work been done since then on MonetDB4 or any of the XQuery code that might improve performance? Thank you, Dean

1 0

[MonetDB-users] MonetDB-client 1.40.1 without Python support?
by W-Mark Kubacki 16 Nov '10

16 Nov '10

Hi. I've noticed that MonetDB-client 1.40.1 doesn't ship with Python libraries anymore. Yet there is a --with-python configuration option and Python examples. The corresponding changelog page [1] says nothing about the matter. What happened? -- Mark [1] http://monetdb.cwi.nl/Development/Releases/Oct2010/ [2] https://github.com/wmark/ossdl-overlay

3 2

[MonetDB-users] Announcement: New Oct2010 feature release of MonetDB suite
by Sjoerd Mullender 15 Nov '10

15 Nov '10

It is not October anymore, but nevertheless, the MonetDB team at CWI/MonetDB BV is pleased to announce the Oct2010 feature release of the MonetDB suite of programs. More information (including release notes) on this release is available at <http://monetdb.cwi.nl/Development/Releases/Oct2010/>. The download location is <http://dev.monetdb.org/downloads/>. -- Sjoerd Mullender

1 0

[MonetDB-users] !MALException:setScenario:Scenario not initialized 'sql'
by Osmin Castillo 13 Nov '10

13 Nov '10

Hi guys, after install *MonetDB RPMs for Centos 5<http://code.google.com/p/monetdb-rhel-5/> * and mserver5 starts , I receive this error when execute the client: mclient -lsql !MALException:setScenario:Scenario not initialized 'sql' There's something missing?.. please help.

4 8

[MonetDB-users] MonetDB memory issue
by Andrey Timofeyev 12 Nov '10

12 Nov '10

Hello, All, We began to use MonetDB several weeks ago. As I can see people use monetdb several years and operate with millions of records. But we could not insert even several thousands records. After several minutes monetdb eat all 7 Gb memory and crush without any message. It seems that we use monetdb incorrectly. Do there exist any special options for start monetdb? MonetDB version: MonetDB server v5.20.5 (64-bit), based on kernel v1.38.5 (32-bit oids) Release Jun2010-SP2 Copyright (c) 1993-July 2008 CWI Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved Visit http://monetdb.cwi.nl/ for further information Found 7.9GiB available memory Configured for prefix: C:\Users\sjoerd\Documents\src\stable\vs64\NTv64 Libraries: libpcre: 7.9 2009-04-11 openssl: OpenSSL 1.0.0a 1 Jun 2010 libxml2: 2.7.7 Compiled by: sjoerd@ALGOL (i686-pc-win32) Compilation: cl -GF -W3 -WX -wd4273 -wd4102 -MD -nologo -Ox Linking : cl -GF -W3 -WX -wd4273 -wd4102 -MD -nologo -Ox OS: Windows 7 x64 (Версия 6.1.7600 Сборка 7600) (We also try it on the ubuntu 10.4 - same effect) -- Best regards, Andrey.

3 11

[MonetDB-users] Sept-2010 Release
by Henry Addington 11 Nov '10

11 Nov '10

Hello: Do you have an estimated release date for the Oct-2010 release? I thought the major releases came out every 3 to 4 months..... Thanks for the update. Best regards, Henry

2 3

Re: [MonetDB-users] Querying date type column in MonetDB
by Stefan Manegold 25 Oct '10

25 Oct '10

"T.c" != "T"."c" ;-) -- | Stefan.Manegold @ CWI .nl | DB Architectures (INS1) | | http://www.cwi.nl/~manegold/ | Science Park 123 (L321) | | Tel.: +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) | ----- Oorspronkelijk bericht ----- Van: Freddy Priyatna <freddy.priyatna(a)gmail.com> Verzonden: maandag 25 oktober 2010 17:11 Aan: Communication channel for MonetDB users <monetdb-users(a)lists.sourceforge.net> Onderwerp: Re: [MonetDB-users] Querying date type column in MonetDB Dear Arjen, Thanks. I did check the uppercase letter. With a date-type column "deliveryDays" in a table "bsbm.offer", here is the result - SELECT "deliveryDays" FROM bsbm.offer --> WORKS - SELECT "deliverydays" FROM bsbm.offer --> FAILS - SELECT "offer.deliveryDays" FROM bsbm.offer --> FAILS - SELECT deliveryDays FROM bsbm.offer --> FAILS - SELECT offer.deliveryDays FROM bsbm.offer --> FAILS - SELECT offer."deliveryDays" FROM bsbm.offer ---> WORKS The last query is the one I need :) Again, thanks for the help. Regards Freddy 2010/10/25 Arjen de Rijke <Arjen.de.Rijke(a)cwi.nl> > Stefan Manegold <Stefan.Manegold(a)cwi.nl> writes: > > > I see --- if you consider it a bug, please file a detailed bug report > including information & instructions to reporduce the problem as well as > infornmation about the exact MonetDB version and OS you're using via > http://bugs.MonetDB.org/ > > I would not consider it a bug. The catch is the uppercase letter in > deliveryDays. The default handling of upper/lowercase characters is > different than in other RDMBS. So in some cases the quotes are necessary. > > Arjen de Rijke > > > > Stefan > > > > > > ----- Oorspronkelijk bericht ----- > > Van: Freddy Priyatna <freddy.priyatna(a)gmail.com> > > Verzonden: maandag 25 oktober 2010 16:32 > > Aan: Communication channel for MonetDB users < > monetdb-users(a)lists.sourceforge.net> > > Onderwerp: Re: [MonetDB-users] Querying date type column in MonetDB > > > > Hi Stefan, > > > > Nope, the name of the column is "deliveryDays" :) > > > > Freddy > > > > 2010/10/25 Stefan Manegold <Stefan.Manegold(a)cwi.nl> > > > >> Hi Freddy, > >> > >> I don't think that the error you experience is triggered by the column > >> type, but rather by the fact that your date column ha? a name - say > "date" - > >> that is a reserved key word in SQL an hence needs to be double-quoted > >> according to the SQL standard (this is not a MonetDB specific choice, > but a > >> "feature" of the SQL standard) --- not knowing your table & column > names, I > >> can only guess, though ... > >> > >> Stefan > >> > >> > >> ----- Oorspronkelijk bericht ----- > >> Van: Freddy Priyatna <freddy.priyatna(a)gmail.com> > >> Verzonden: maandag 25 oktober 2010 16:03 > >> Aan: MonetDB-users <monetdb-users(a)lists.sourceforge.net> > >> Onderwerp: [MonetDB-users] Querying date type column in MonetDB > >> > >> Dear All, > >> > >> I am new to MonetDB, so most likely my question will look obvious. > >> > >> I would like to ask, how can columns with date type is queried in > monetdb. > >> Based on my experience, it seems that date type columns need special > >> treatment. It seems that the only way to query them is with the syntax > >> "column_name" while other columns seems to work with the format > >> table_name.column_name without the need of double quote. When I tried to > >> query date column with the syntax table_name.column_name, it gave me an > >> error "no such column" > >> > >> So my question is, is it true that the only way to query date columns is > >> using "column_name" format? Another question will be, what happen if I > need > >> to query same name columns coming from different table? > >> > >> Thanks in advance, > >> Freddy > >> > >> > >> > ------------------------------------------------------------------------------ > >> Nokia and AT&T present the 2010 Calling All Innovators-North America > >> contest > >> Create new apps & games for the Nokia N8 for consumers in U.S. and > Canada > >> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in > >> marketing > >> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > >> http://p.sf.net/sfu/nokia-dev2dev > >> _______________________________________________ > >> MonetDB-users mailing list > >> MonetDB-users(a)lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/monetdb-users > >> > > > > > ------------------------------------------------------------------------------ > > Nokia and AT&T present the 2010 Calling All Innovators-North America > contest > > Create new apps & games for the Nokia N8 for consumers in U.S. and > Canada > > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in > marketing > > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > > http://p.sf.net/sfu/nokia-dev2dev > > _______________________________________________ > > MonetDB-users mailing list > > MonetDB-users(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/monetdb-users > > -- > ==================================================================== > CWI, Kamer L330 Centrum voor Wiskunde en Informatica > Science Park 123 Email: arjen.de.rijke(a)cwi.nl > 1098 XG Amsterdam tel: +31-(0)20-5924305 > Nederland +31-(0)6-51899284 > fax: +31-(0)20-5924312 > ===================== http://www.cwi.nl/~rijke/ ==================== > > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America > contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in > marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > MonetDB-users mailing list > MonetDB-users(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/monetdb-users >

1 0

Re: [MonetDB-users] Querying date type column in MonetDB
by Stefan Manegold 25 Oct '10

25 Oct '10

Good point, Arjen! Indeed CaMeL case identifiers need to be double-quoted in MonetDB/SQL ... Stefan -- | Stefan.Manegold @ CWI .nl | DB Architectures (INS1) | | http://www.cwi.nl/~manegold/ | Science Park 123 (L321) | | Tel.: +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) | ----- Oorspronkelijk bericht ----- Van: Arjen de Rijke <Arjen.de.Rijke(a)cwi.nl> Verzonden: maandag 25 oktober 2010 17:00 Aan: Communication channel for MonetDB users <monetdb-users(a)lists.sourceforge.net> Onderwerp: Re: [MonetDB-users] Querying date type column in MonetDB Stefan Manegold <Stefan.Manegold(a)cwi.nl> writes: > I see --- if you consider it a bug, please file a detailed bug report including information & instructions to reporduce the problem as well as infornmation about the exact MonetDB version and OS you're using via http://bugs.MonetDB.org/ I would not consider it a bug. The catch is the uppercase letter in deliveryDays. The default handling of upper/lowercase characters is different than in other RDMBS. So in some cases the quotes are necessary. Arjen de Rijke > > Stefan > > > ----- Oorspronkelijk bericht ----- > Van: Freddy Priyatna <freddy.priyatna(a)gmail.com> > Verzonden: maandag 25 oktober 2010 16:32 > Aan: Communication channel for MonetDB users <monetdb-users(a)lists.sourceforge.net> > Onderwerp: Re: [MonetDB-users] Querying date type column in MonetDB > > Hi Stefan, > > Nope, the name of the column is "deliveryDays" :) > > Freddy > > 2010/10/25 Stefan Manegold <Stefan.Manegold(a)cwi.nl> > >> Hi Freddy, >> >> I don't think that the error you experience is triggered by the column >> type, but rather by the fact that your date column ha? a name - say "date" - >> that is a reserved key word in SQL an hence needs to be double-quoted >> according to the SQL standard (this is not a MonetDB specific choice, but a >> "feature" of the SQL standard) --- not knowing your table & column names, I >> can only guess, though ... >> >> Stefan >> >> >> ----- Oorspronkelijk bericht ----- >> Van: Freddy Priyatna <freddy.priyatna(a)gmail.com> >> Verzonden: maandag 25 oktober 2010 16:03 >> Aan: MonetDB-users <monetdb-users(a)lists.sourceforge.net> >> Onderwerp: [MonetDB-users] Querying date type column in MonetDB >> >> Dear All, >> >> I am new to MonetDB, so most likely my question will look obvious. >> >> I would like to ask, how can columns with date type is queried in monetdb. >> Based on my experience, it seems that date type columns need special >> treatment. It seems that the only way to query them is with the syntax >> "column_name" while other columns seems to work with the format >> table_name.column_name without the need of double quote. When I tried to >> query date column with the syntax table_name.column_name, it gave me an >> error "no such column" >> >> So my question is, is it true that the only way to query date columns is >> using "column_name" format? Another question will be, what happen if I need >> to query same name columns coming from different table? >> >> Thanks in advance, >> Freddy >> >> >> ------------------------------------------------------------------------------ >> Nokia and AT&T present the 2010 Calling All Innovators-North America >> contest >> Create new apps & games for the Nokia N8 for consumers in U.S. and Canada >> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in >> marketing >> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store >> http://p.sf.net/sfu/nokia-dev2dev >> _______________________________________________ >> MonetDB-users mailing list >> MonetDB-users(a)lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/monetdb-users >> > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > MonetDB-users mailing list > MonetDB-users(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/monetdb-users -- ==================================================================== CWI, Kamer L330 Centrum voor Wiskunde en Informatica Science Park 123 Email: arjen.de.rijke(a)cwi.nl 1098 XG Amsterdam tel: +31-(0)20-5924305 Nederland +31-(0)6-51899284 fax: +31-(0)20-5924312 ===================== http://www.cwi.nl/~rijke/ ==================== ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ MonetDB-users mailing list MonetDB-users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users

1 0

Re: [MonetDB-users] Querying date type column in MonetDB
by Stefan Manegold 25 Oct '10

25 Oct '10

Hi Freddy, I don't think that the error you experience is triggered by the column type, but rather by the fact that your date column ha? a name - say "date" - that is a reserved key word in SQL an hence needs to be double-quoted according to the SQL standard (this is not a MonetDB specific choice, but a "feature" of the SQL standard) --- not knowing your table & column names, I can only guess, though ... Stefan ----- Oorspronkelijk bericht ----- Van: Freddy Priyatna <freddy.priyatna(a)gmail.com> Verzonden: maandag 25 oktober 2010 16:03 Aan: MonetDB-users <monetdb-users(a)lists.sourceforge.net> Onderwerp: [MonetDB-users] Querying date type column in MonetDB Dear All, I am new to MonetDB, so most likely my question will look obvious. I would like to ask, how can columns with date type is queried in monetdb. Based on my experience, it seems that date type columns need special treatment. It seems that the only way to query them is with the syntax "column_name" while other columns seems to work with the format table_name.column_name without the need of double quote. When I tried to query date column with the syntax table_name.column_name, it gave me an error "no such column" So my question is, is it true that the only way to query date columns is using "column_name" format? Another question will be, what happen if I need to query same name columns coming from different table? Thanks in advance, Freddy

2 1

[MonetDB-users] Querying date type column in MonetDB
by Freddy Priyatna 25 Oct '10

25 Oct '10

Dear All, I am new to MonetDB, so most likely my question will look obvious. I would like to ask, how can columns with date type is queried in monetdb. Based on my experience, it seems that date type columns need special treatment. It seems that the only way to query them is with the syntax "column_name" while other columns seems to work with the format table_name.column_name without the need of double quote. When I tried to query date column with the syntax table_name.column_name, it gave me an error "no such column" So my question is, is it true that the only way to query date columns is using "column_name" format? Another question will be, what happen if I need to query same name columns coming from different table? Thanks in advance, Freddy

1 0

[MonetDB-users] calc.date in SQL to MAL.
by Guillaume Yziquel 22 Oct '10

22 Oct '10

Hi. I have resumed work on the OCaml binding for MonetDB. I have been playing a bit with it and with MonetDB, and noticed something rather weird when trying to explain a SQL statement to MAL. Compilation, and launching a small test in an OCaml toplevel: yziquel@seldon:~/data$ make ocamlbuild -use-ocamlfind import.cma Finished, 3 targets (0 cached) in 00:00:00. yziquel@seldon:~/data$ make test cp ocamlinit _build/ cd _build; ledit ocaml -init ocamlinit Objective Caml version 3.12.0 Findlib has been successfully loaded. Additional directives: #require "package";; to load a package #list;; to list the available packages #camlp4o;; to load camlp4 (standard syntax) #camlp4r;; to load camlp4 (revised syntax) #predicates "p,q,...";; to set these predicates Topfind.reset();; to force that packages will be reloaded #thread;; to enable threads /usr/lib/ocaml/csv: added to search path /usr/lib/ocaml/csv/csv.cma: loaded /usr/lib/ocaml/unix.cma: loaded /usr/lib/ocaml/monetdb5: added to search path /usr/lib/ocaml/monetdb5/monetDB5.cma: loaded /usr/lib/ocaml/dynlink.cma: loaded /usr/lib/ocaml/camlp4: added to search path /usr/lib/ocaml/pcre: added to search path /usr/lib/ocaml/pcre/pcre.cma: loaded /usr/local/lib/ocaml/3.12.0/tophide: added to search path /usr/local/lib/ocaml/3.12.0/tophide/tophide.cmo: loaded /usr/local/lib/ocaml/3.12.0/mikmatch_pcre: added to search path /usr/local/lib/ocaml/3.12.0/mikmatch_pcre/run_mikmatch_pcre.cma: loaded So much for the prologue, and dynamic loading. So the test starts here. Everytime you see "Asking", it is the statement that is fed to the connection handler in order to retrieve the query handler. (With mapilib). Asking: select name from tables; Asking: create table indu (Date date, Open decimal(15,2), High decimal(15,2), Low decimal(15,2), Close decimal(15,2), Volume decimal(15,2), OI decimal(15,2)); Asking: insert into indu (Date, Open, High, Low, Close, Volume, OI) values ('1920-02-01', 108.80, 108.80, 108.80, 108.80, 1156, 0); Asking: insert into indu (Date, Open, High, Low, Close, Volume, OI) values ('1920-05-01', 108.90, 108.90, 108.90, 108.90, 1305, 0); Asking: insert into indu (Date, Open, High, Low, Close, Volume, OI) values ('1920-06-01', 107.40, 107.40, 107.40, 107.40, 1251, 0); Asking: insert into indu (Date, Open, High, Low, Close, Volume, OI) values ('1920-07-01', 107.60, 107.60, 107.60, 107.60, 771, 0); Asking: insert into indu (Date, Open, High, Low, Close, Volume, OI) values ('1920-08-01', 107.20, 107.20, 107.20, 107.20, 843, 0); Asking: insert into indu (Date, Open, High, Low, Close, Volume, OI) values ('1920-09-01', 106.60, 106.60, 106.60, 106.60, 736, 0); Asking: insert into indu (Date, Open, High, Low, Close, Volume, OI) values ('1920-12-01', 104.20, 104.20, 104.20, 104.20, 1049, 0); Asking: insert into indu (Date, Open, High, Low, Close, Volume, OI) values ('1920-13-01', 104.50, 104.50, 104.50, 104.50, 908, 0); And on this last statement, the server doesn't seem happy at all: Exception: MonetDB5.Mapi.Error (Some (MonetDB5.Mapi.MSERVER, None)). So I've been trying to 'explain' the SQL to MAL. The first two work fine and output a very similar MAL statement. The third SQL statements, however, is getting translated to something somewhat different: You see a call to 'calc.date' on the 4th MAL line: # ask "explain insert into indu (Date, Open, High, Low, Close, Volume, # OI) values ('1920-07-01', 107.60, 107.60, 107.60, 107.60, 771, 0);";; Asking: explain insert into indu (Date, Open, High, Low, Close, Volume, OI) values ('1920-07-01', 107.60, 107.60, 107.60, 107.60, 771, 0); - : string option list list = [[Some "function user.s0_1{autoCommit=true}():void;"]; [Some " _2 := sql.mvc();"]; [Some "barrier _32 := language.dataflow();"]; [Some " _3 := sql.append(_2,\"sys\",\"indu\",\"date\",1920-07-01);"]; [Some " _7 := sql.append(_3,\"sys\",\"indu\",\"open\",10760:lng);"]; [Some " _9 := sql.append(_7,\"sys\",\"indu\",\"high\",10760:lng);"]; [Some " _11 := sql.append(_9,\"sys\",\"indu\",\"low\",10760:lng);"]; [Some " _13 := sql.append(_11,\"sys\",\"indu\",\"close\",10760:lng);"]; [Some " _15 := sql.append(_13,\"sys\",\"indu\",\"volume\",77100:lng);"]; [Some " sql.append(_15,\"sys\",\"indu\",\"oi\",0:lng);"]; [Some "exit _32;"]; [Some " sql.affectedRows(1:wrd,\"\");"]; [Some "end s0_1;"]] # ask "explain insert into indu (Date, Open, High, Low, Close, Volume, # OI) values ('1920-12-01', 104.20, 104.20, 104.20, 104.20, 1049, 0);";; Asking: explain insert into indu (Date, Open, High, Low, Close, Volume, OI) values ('1920-12-01', 104.20, 104.20, 104.20, 104.20, 1049, 0); - : string option list list = [[Some "function user.s1_1{autoCommit=true}():void;"]; [Some " _2 := sql.mvc();"]; [Some "barrier _32 := language.dataflow();"]; [Some " _3 := sql.append(_2,\"sys\",\"indu\",\"date\",1920-12-01);"]; [Some " _7 := sql.append(_3,\"sys\",\"indu\",\"open\",10420:lng);"]; [Some " _9 := sql.append(_7,\"sys\",\"indu\",\"high\",10420:lng);"]; [Some " _11 := sql.append(_9,\"sys\",\"indu\",\"low\",10420:lng);"]; [Some " _13 := sql.append(_11,\"sys\",\"indu\",\"close\",10420:lng);"]; [Some " _15 := sql.append(_13,\"sys\",\"indu\",\"volume\",104900:lng);"]; [Some " sql.append(_15,\"sys\",\"indu\",\"oi\",0:lng);"]; [Some "exit _32;"]; [Some " sql.affectedRows(1:wrd,\"\");"]; [Some "end s1_1;"]] # ask "explain insert into indu (Date, Open, High, Low, Close, Volume, # OI) values ('1920-13-01', 104.50, 104.50, 104.50, 104.50, 908, 0);";; Asking: explain insert into indu (Date, Open, High, Low, Close, Volume, OI) values ('1920-13-01', 104.50, 104.50, 104.50, 104.50, 908, 0); - : string option list list = [[Some "function user.s2_1{autoCommit=true}():void;"]; [Some " _2 := sql.mvc();"]; [Some "barrier _33 := language.dataflow();"]; [Some " _3 := calc.date(\"1920-13-01\");"]; [Some " _4 := sql.append(_2,\"sys\",\"indu\",\"date\",_3);"]; [Some " _8 := sql.append(_4,\"sys\",\"indu\",\"open\",10450:lng);"]; [Some " _10 := sql.append(_8,\"sys\",\"indu\",\"high\",10450:lng);"]; [Some " _12 := sql.append(_10,\"sys\",\"indu\",\"low\",10450:lng);"]; [Some " _14 := sql.append(_12,\"sys\",\"indu\",\"close\",10450:lng);"]; [Some " _16 := sql.append(_14,\"sys\",\"indu\",\"volume\",90800:lng);"]; [Some " sql.append(_16,\"sys\",\"indu\",\"oi\",0:lng);"]; [Some "exit _33;"]; [Some " sql.affectedRows(1:wrd,\"\");"]; [Some "end s2_1;"]] # Why is that happening? The SQL statements seem so similar that I do not see why it gets compiled differently to MAL. Best regards, -- Guillaume Yziquel http://yziquel.homelinux.org

2 4

[MonetDB-users] installation corrupted
by Nafees Ur Rehman 20 Oct '10

20 Oct '10

Hi, I am using monetDB/SQL for windows on an xp machine. Two days ago, the server stopped responding. Tried to repair and change it...but didn't work. Also got it formally un-installed and then tried re-installation...but no luck. Any hints. The server does not mount at all. Regards Nafees Ur Rehman Konstanz, Germany

1 0

[MonetDB-users] MonetDB performance question
by Tudor-Ioan Salomie 18 Oct '10

18 Oct '10

Hi, I have recently tried doing some experiments with MonetDB, measuring its performance for the following dataset+workload: * 1 table (50 attributes), 1GB, comprising 3.000.000 tuples * the attributes are fixed length strings and integer types * the workload is query (SELECT) only, where each query has the form: SELECT <list_of_projections> FROM MyTable WHERE <list_of_predicates>; * the list of predicates is a conjunction of equality operators * more than 99% of the queries predicate on the same attribute (let's call it A1) that has a *very* good selectivity * the average number of predicated attributes per query is 8 * for this workload, averaging over 4000 queries, there is 1 result tuple per query (actual result tuples per query are in the range 0-10) I have installed MonetDB on a 64-bit Debian machines, using the .deb files provided on the internet: * libmonetdb1_1.38.5-20100824_amd64.deb * libmonetdb5-server5_5.20.5-20100824_amd64.deb * libmonetdb5-sql2_2.38.5-20100824_amd64.deb * libmonetdb-client1_1.38.5-20100824_amd64.deb * monetdb5-server_5.20.5-20100824_amd64.deb * monetdb5-sql_2.38.5-20100824_amd64.deb * monetdb-client_1.38.5-20100824_amd64.deb For running the queries I use the SQL front end. I have run the queries both through "mclient" (directly on the server) and through the JDBC driver (from another client machine). The MonetDB server is bound to run on only one core on the machine (though I have not seen any difference if running it on multiple cores). To my surprise, the throughput for MonetDB for this workload is very low. I get about 3 queries per second, which seems to indicate that MonetDB does full table scanning only. Am I correct in this assumption? Is there anything that can be done to speed it up? Is this not a workload suitable for MonetDB? Looking forward to your input! Regards, Tudor.

2 1

[MonetDB-users] FW: Comment via CWI webform MonetDB
by Peter Boncz 15 Oct '10

15 Oct '10

Narayan Sujay, Thanks for your interest in MonetDB. Rather than directing technical questions to the CWI organization webmaster, you are supposed to post on one of the relevant mailing lists such as this one (monetdb-user(a)lists.sourceforge.net) Peter -----Original Message----- From: Minnie Middelberg [mailto:Minnie.Middelberg@cwi.nl] Sent: Friday, October 15, 2010 9:50 AM To: Peter Boncz Subject: Fwd: Comment via CWI webform MonetDB Hallo Peter, Onderstaand is binnengekomen via het CWI Comment formulier en het betreft MonetDB. Wetende dat jij en Marting Kersten achter MonetDB zitten forward ik het maar naar jou. Mocht er iemand zijn die dit soort vragen belast is dan hoor ik het graag van je. Mvg Minnie ----- Forwarded Message ----- From: "Narayan Sujay" <316sujay(a)gmail.com> To: voorlichting(a)cwi.nl, webmaster(a)cwi.nl Sent: Thursday, 14 October, 2010 6:15:15 PM Subject: Comment via CWI webform Submitted on 14.10.2010 - 18:15 Submitted by anonymous user: [198.134.51.12] Submitted values are: Name sender: Narayan Sujay Email address: 316sujay(a)gmail.com Telephone number: 4193780532 Your comment: Hello, I have downloaded MonetDB and the native client and server work well. I can write simple queries in the client cmd window. I am trying to connect MonetDB with one of the SQL frontends like DB visualizer etc and I am not able to do this. Please help me out with instructions. I followed the instructions on the webpage but still getting errors connecting through db visualizer. I think it is the problem with the JDBC drivers. Please let me know excatly where to find the driver on the local computer after I have installed Monet DB. My Main goal here is to load large Data sets in MonetDB. Please tell me a way to do this for Monet DB. The error I get in DB Visualizer is: Long Message: Cannot connect to ORB Details: Type: javax.naming.CommunicationException Stack Trace: javax.naming.CommunicationException: Cannot connect to ORB [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No] at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(Unknown Source) at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(Unknown Source) at com.sun.jndi.cosnaming.CNCtx.<init>(Unknown Source) at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(Unknown Source) at javax.naming.spi.NamingManager.getInitialContext(Unknown Source) at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source) at javax.naming.InitialContext.init(Unknown Source) at javax.naming.InitialContext.<init>(Unknown Source) at com.onseven.dbvis.db.A.G.Ą(Z:3155) at com.onseven.dbvis.db.A.G.Ĭ(Z:2675) at com.onseven.dbvis.db.A.E.Ĭ(Z:98) at com.onseven.dbvis.db.A.D.ā(Z:2056) at se.pureit.swing.A.O$2.run(Z:1192) at java.lang.Thread.run(Unknown Source) Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No at com.sun.corba.se.impl.logging.ORBUtilSystemException.connectFailure(Unknown Source) at com.sun.corba.se.impl.logging.ORBUtilSystemException.connectFailure(Unknown Source) at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.<init>(Unknown Source) at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.<init>(Unknown Source) at com.sun.corba.se.impl.transport.SocketOrChannelContactInfoImpl.createConnection(Unknown Source) at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(Unknown Source) at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.request(Unknown Source) at com.sun.corba.se.impl.resolver.BootstrapResolverImpl.invoke(Unknown Source) at com.sun.corba.se.impl.resolver.BootstrapResolverImpl.resolve(Unknown Source) at com.sun.corba.se.impl.resolver.CompositeResolverImpl.resolve(Unknown Source) at com.sun.corba.se.impl.resolver.CompositeResolverImpl.resolve(Unknown Source) at com.sun.corba.se.impl.resolver.CompositeResolverImpl.resolve(Unknown Source) at com.sun.corba.se.impl.orb.ORBImpl.resolve_initial_references(Unknown Source) ... 14 more Caused by: java.net.ConnectException: Connection refused: connect at sun.nio.ch.Net.connect(Native Method) at sun.nio.ch.SocketChannelImpl.connect(Unknown Source) at java.nio.channels.SocketChannel.open(Unknown Source) at com.sun.corba.se.impl.transport.DefaultSocketFactoryImpl.createSocket(Unknown Source) ... 25 more The results of this submission may be viewed at: http://www.cwi.nl/en/node/757/submission/3152

1 0

[MonetDB-users] upgrade notes: Feb2010 --> Jun2010
by Mark Bucciarelli 07 Oct '10

07 Oct '10

Hi, I'd like to upgrade to the June release. I'm running Feb 2010. Can I just build the June release and expect it will just work with my database? Or do I need to upgrade the data somehow? I poked around dev.monetdb.org/hg, looking for release notes, changelist, etc. but didn't find anything. Thanks, m

2 3

[MonetDB-users] bug #2634 in Jun2010? [was: upgrade notes: Feb2010 --> Jun2010]
by Mark Bucciarelli 07 Oct '10

07 Oct '10

On Thu, Oct 7, 2010 at 9:15 AM, Sjoerd Mullender <sjoerd(a)acm.org> wrote: > On 2010-10-07 14:41, Mark Bucciarelli wrote: > >> I poked around dev.monetdb.org/hg, looking for release >> notes, changelist, etc. but didn't find anything. > > http://monetdb.cwi.nl/Development/Releases/Jun2010/ > Thanks. Was the commit in bug #2634 in the release? I don't see it in the SQL notes. He closed as NEEDS MORE INFO (I think---I can't tell from ticket history) because I did not include a test case. But he did commit some change that fixed the issue (I was able to upload a test case this week, and verified his fix solved my case). Thanks, m http://bugs.monetdb.org/show_bug.cgi?id=2634

2 1

[MonetDB-users] Performance improvements over equal queries limits to operators?
by Stefan de Konink 06 Oct '10

06 Oct '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, I was quite surprised about the performance of some queries, that I expected to be heavy weighted, but actually performed pretty well. To show some things: sql>select * from kvk where postcode like '2265CA' and adres like '%7%'; 3 tuples (259.000ms) sql>select * from kvk where postcode like '2265CA' and adres like '%7%'; 3 tuples (259.000ms) sql>select * from kvk where postcode like '2265CA' and adres like '%7%'; 3 tuples (258.000ms) sql>select * from kvk where postcode like '2265CA' and adres like '%7%'; 3 tuples (257.000ms) sql>select * from kvk where postcode = '2265CA' and adres like '%7%'; 3 tuples (11.000ms) sql>select * from kvk where postcode = '2265CA' and adres like '%7%'; 3 tuples (6.000ms) sql>select * from kvk where postcode = '2265CA' and adres like '%7%'; 3 tuples (6.000ms) sql>select * from kvk where kvk = 273121520000; 1 tuple (473.000ms) sql>select * from kvk where kvk = 273121520000; 1 tuple (5.000ms) I wonder: what makes the 11ms to 6ms possible in the like vs = scenario? While a repeat of the like operator itself doesn't give a true improvement? As you can observe the like argument doesn't have any modifiers, so it should actually become a normal equal. (I noticed this later, goes beyond my original point, will file a bug for enhancement.) Also I'm quite surprised that the primary key lookup still takes a fair amount of time, could be i/o related obviously, but the performance on the second run is again huge, even for other arguments. Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREKAAYFAkysWw8ACgkQYH1+F2Rqwn19AgCgk9lkRBLcWdylxxz9M4B8a8f5 5JUAn1TOU1VxpvVfVWJMLwlwp9Pz4a0x =IqCY -----END PGP SIGNATURE-----

2 1

[MonetDB-users] Dump schema w/ mclient?
by Mark Bucciarelli 05 Oct '10

05 Oct '10

Is there a way to user mclient to dump the db schema without dumping the data? I tried creating a one line SQL file with \d <tablename> and piping to mclient stdin, but it didn't work. Thanks, m

3 2

[MonetDB-users] add a unique constraint, need to create index?
by Mark Bucciarelli 04 Oct '10

04 Oct '10

Hi, I added a unique constraint on two fields, and noticed there was not an index created on those two fields. Do I need to do a CREATE INDEX or is it implicit? I will be using those two fields a lot in WHERE clauses. Thanks, m

1 1