On 03-10-2006 11:55:52 +0200, Ronald Oussoren wrote:
On Oct 3, 2006, at 10:45 AM, Fabian Groffen wrote:
On 03-10-2006 10:42:24 +0200, Ronald Oussoren wrote:
The machine I was testing on is running 4.10.3 and is definitely listening on port 45123 and only that. I'll upgrade to the latest
Correct, that version is quite old.
'make check' for MonetDB-4.12.1 (downloaded today) complains a lot about:
!ERROR: interpret: no matching MIL operator to 'quit()'. quit();
That doesn't feel right.
This is on a linux system (SLES9). I aborted 'make check' because it didn't seem to make any progress except printing this error message a lot.
BTW. I also had to suply both '--enable-debug' and '--disable- optimize' to the configure script, without the latter configure claimed I couldn't have both --enable-optimze and --enable-debug.
There is a default involved here. In order to have monetdb's configure respect your CFLAGS, you have to axe out CFLAGS hackery from the configure script, e.g.: sed -i \ -e 's|CFLAGS="\$CFLAGS \\\$(X_CFLAGS)"||' \ configure || echo "Fixing configure failed!" Then configure with --disable-debug --disable-optimize
I'm building from source because I want to install into /opt/ monet-4.12.1 and link to a custom build of python.
That's fine and should work as expected (--prefix=/opt/monetdb-${PV})
BTW2. If monetdb is installed in a different prefix than python the python bindings won't end up on the default search path of the python interpreter. I've added a .pth file to site-packages to fix that, maybe 'make install' should do that automaticly. Building/installing using distutils would be even better :-)
I think that's what PYTHONPATH is for, but I leave that to the python experts. If your solution is to write in the non-prefix to make some sort of alias, then it won't work, as you don't have to be root. Maybe you don't even want to do that. (Using another version of python, for example.)
BTW3. The version info for the shared libraries is incorrect, which means you cannot have two versions of monetdb installed at the same time, I got a Mserver 4.12.1 that claimed it was 4.10 and didn't work at all. I guess this is "don't do that" territory ;-). Removing the older installation solved this.
I think slotting is not supported, and that the best way out of there is to just install into different prefixes.
Upgrading has solved the problem I was having. I can now perform SQL queries from Python.
That's great.
The MonetSQLdb module doesn't contain a callable named 'Binary'. Is that intentional? This callable is required according to PEP 249. The same is true for the value BINARY which isn't present as well (although it is listed in __all__). SQLObject needs the Binary callable, I'll send a patch when I have a working version of this.
I have no clue on this. Maybe some Python expert has.