Hi Fabian, thanks for you response. I am now getting the following error: monetdb-> select 'hello world'; Error: MALException:chop.newChunkMoreElements:Cannot access 'bid' descriptor MALException:sql_cache.s6_2[480]:Exception not catched (for the "select hello world" command, I tried both single quotes and double quotes). When I try to view tables through DBVisualizer, I get the same exception. I started my client in the following manner: ./mjclient -lsql -u monetdb And my server in the following manner: ./mserver5
include sql;
I also attempted to add a "?debug=true" to jdbc url (as requested in one of the monetdb messages I found on google), as far as I can tell, it didn't produce any log file. Rest of my message is inlined below:
As we say in Dutch: "One shouldn't look into a given horse's mouth." We're very happy for what we get for free from SourceForge, even though it isn't perfect all the time. Also, sidenote: we evaluated switching to svn a while ago and came to the conclusion it is not giving us any benefit, so we'll stay with CVS for at least a long while.
In America we have the same saying about looking a gift horse in the mouth. Lately we have created a better one, "if you don't like your gift, return it and get a better one" :) SourceForge has served the open source community very well, but it is showing its age.
Lastly, how about an IRC channel for MonetDB!
Hehe... most of us don't have time to wast^H^Hspend on that.
What...you don't want to create your own fan club?? :)
When did you download the sources? If you have a good internet connection you might want to download the latest version of the script from here: http://koala.ins.cwi.nl:8000/projects/monetdb//Assets/monetdb-install.sh and run it like you did. It will download the necessary files, and should pass. Check that you get version 1.7.
The version I had was indeed old, even though I only downloaded MonetDB stuff within the last two or three days. Your script worked nicely. It took a while but everything was compiled and installed. My current issue is listed at the top of this email. Again, thanks.