On Oct 3, 2006, at 1:22 PM, Stefan Manegold wrote:
On Tue, Oct 03, 2006 at 12:53:37PM +0200, Ronald Oussoren wrote:
On Oct 3, 2006, at 12:38 PM, Fabian Groffen wrote:
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();
does this happen with only MonetDB-4.12.1 present on your system, or with a "legacy" MonetDB-4.10.3 installed as well (cf. BTW3 below)?
This was with the wrong monetdb present, but the problem also exists with a correct installation. I managed to catch the head of the failure as well: Mtest.py: ERROR: 'Mtimeout -timeout 60 Mserver "--config=/home/ xsupport/src/monet/build/conf/MonetDB.conf" --debug=10 --set "monet_mod_path=/home/xsupport/src/monet/build/src/modules/ plain/.libs:/home/xsupport/src/monet/build/src/modules/plain:/home/ xsupport/src/monet/build/src/modules/contrib/.libs:/home/xsupport/src/ monet/build/src/modules/contrib:/home/xsupport/src/monet/build/src/ modules/calibrator/.libs:/home/xsupport/src/monet/build/src/modules/ calibrator:/home/xsupport/src/monet/build/src/modules/mnetcdf/.libs:/ home/xsupport/src/monet/build/src/modules/mnetcdf:/home/xsupport/src/ monet/build/src/mapi/.libs:/home/xsupport/src/monet/build/src/mapi" -- set "gdk_dbfarm=/home/xsupport/src/monet/build/dbfarm" --set "sql_logdir=/home/xsupport/src/monet/build/log" --set mapi_port=37305 --set monet_prompt= --trace --dbname=mTests` failed: !WARNING: GDKlockHome: ignoring empty or invalid .gdk_lock. !WARNING: BBPdir: initializing BBP. # Monet Database Server V4.12.1 # Copyright (c) 1993-2006, CWI. All rights reserved. # Compiled for i686-pc-linux-gnu/32bit with 32bit OIDs; dynamically linked. # Visit http://monetdb.cwi.nl/ for further information. !ERROR: moduleClient: module(builtin) load error. !ERROR: moduleClient: module(arith) load error. !ERROR: moduleClient: module(str) load error. !ERROR: moduleClient: module(constant) load error. !ERROR: moduleClient: module(bat) load error. !ERROR: moduleClient: module(algebra) load error. !ERROR: moduleClient: module(sys) load error. !ERROR: moduleClient: module(trans) load error. quit(); !ERROR: interpret: no matching MIL operator to 'quit()'. quit(); !ERROR: interpret: no matching MIL operator to 'quit()'. quit(); !ERROR: interpret: no matching MIL operator to 'quit()'. quit(); !ERROR: interpret: no matching MIL operator to 'quit()'. quit(); !ERROR: interpret: no matching MIL operator to 'quit()'. quit(); !ERROR: interpret: no matching MIL operator to 'quit()'. Something completely different: how do I coax the python DB-API implementation out of autocommit mode? import MonetSQLdb conn = MonetSQLdb.connect() cursor = conn.cursor() conn.commit() # -> raises RuntimeError Any updates you do through 'conn' are also instantationious, e.g. no transactions. I can use the 'START TRANSACTION' query to explictly start a transaction, but I then have to keep track of whether I've used 'START TRANSACTION' on one of the active cursors because executing START TRANSACTION inside a transaction seems to break that transaction. The effect I'm looking after is that of the interactive MapiClient when autocommit is disabled: you don't have to start transactions explicitly but are always in one. Ronald