- developers-list - monetdb.org

[Monetdb-developers] a little unicode fix in MapiClient.py
by Max 23 May '06

23 May '06

Steps to reproduce problem: 1. MonetDB-4.10.2, Python 2.3.4, Gentoo Linux 2005.0, LANG=ru_RU.KOI8-R 2. Start monetdb mil server 3. Start MapiClient.py 4. Type following command: vars(); 5. Script fails with the following output: #MapiClient (python) connected to localhost:50000 as max > vars(); Traceback (most recent call last): File "/usr/bin/MapiClient.py", line 77, in ? main(sys.argv) File "/usr/bin/MapiClient.py", line 60, in main res = s.cmd(line) File "/usr/share/MonetDB/python/Mapi.py", line 116, in cmd return self.result() File "/usr/share/MonetDB/python/Mapi.py", line 67, in result while buffer[-len(self.prompt1):] != self.prompt1 and \ UnicodeDecodeError: 'ascii' codec can't decode byte 0x81 in position 0: ordinal not in range(128) Possible patch: --- MonetDB-4.10.2/src/mapi/clients/python/MapiClient.py.in 2006-01-20 23:36:49.000000000 +0700 +++ MonetDB-4.10.2/src/mapi/clients/python/MapiClient.py.in.fixed 2006-05-14 15:15:19.000000000 +0800 @@ -57,7 +57,7 @@ sys.stdout.write(s.prompt) line = fi.readline() while line and line != "quit;\n": - res = s.cmd(line) + res = s.cmd(line).encode('utf-8') print res sys.stdout.write(s.prompt.encode('utf-8')) line = fi.readline()

3 2

[Monetdb-developers] Mserver crash during data import
by Peter Roozemaal 20 May '06

20 May '06

During database import Mserver crashes on my Gentoo (64 bit) Linux Athlon64 machine. After the crash the Monet database is so corrupted that recovery fails. I have appended gdb output of the server session; additional information, input data and scripts are available upon request. Greetings, Peter. ===== gdb `which Mserver` GNU gdb 6.4 Copyright 2005 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu"...(no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run monetdb-startup.mil Starting program: /usr/bin/Mserver monetdb-startup.mil (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 21057)] !WARNING: GDKlockHome: created directory /var/lib/MonetDB/dbfarm/default/ !WARNING: GDKlockHome: ignoring empty or invalid .gdk_lock. !WARNING: BBPdir: initializing BBP. [New Thread 32769 (LWP 21060)] [New Thread 16386 (LWP 21061)] # Monet Database Server V4.10.2 # Copyright (c) 1993-2006, CWI. All rights reserved. # Compiled for x86_64-pc-linux-gnu/64bit with 64bit OIDs; dynamically linked. # Visit http://monetdb.cwi.nl/ for further information. [New Thread 32771 (LWP 21063)] [New Thread 49156 (LWP 21064)] [New Thread 65541 (LWP 21065)] [New Thread 81926 (LWP 21066)] [New Thread 98311 (LWP 21067)] [New Thread 114696 (LWP 21068)] [New Thread 131081 (LWP 21069)] [New Thread 147466 (LWP 21070)] [New Thread 163851 (LWP 21071)] [New Thread 180236 (LWP 21072)] [New Thread 196621 (LWP 21073)] [New Thread 213006 (LWP 21074)] [New Thread 229391 (LWP 21075)] [New Thread 245776 (LWP 21076)] [New Thread 262161 (LWP 21077)] [New Thread 278546 (LWP 21078)] [New Thread 294931 (LWP 21079)] [New Thread 311316 (LWP 21080)] [New Thread 327701 (LWP 21081)] [New Thread 344086 (LWP 21082)] [New Thread 360471 (LWP 21083)] [New Thread 376856 (LWP 21084)] [New Thread 393241 (LWP 21085)] [New Thread 409626 (LWP 21086)] [New Thread 426011 (LWP 21087)] [New Thread 442396 (LWP 21088)] [New Thread 458781 (LWP 21089)] [New Thread 475166 (LWP 21090)] [New Thread 491551 (LWP 21091)] [New Thread 507936 (LWP 21092)] [New Thread 524321 (LWP 21093)] [New Thread 540706 (LWP 21094)] [New Thread 557091 (LWP 21095)] [New Thread 573476 (LWP 21096)] [New Thread 589861 (LWP 21101)] [Thread 147466 (LWP 21070) exited] [New Thread 606218 (LWP 21117)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 426011 (LWP 21087)] 0x00002aaaab9aa2c8 in GDKreallocmax () from /usr/lib/libbat.so.0 (gdb) where #0 0x00002aaaab9aa2c8 in GDKreallocmax () from /usr/lib/libbat.so.0 #1 0x00002aaaab9530f3 in HEAPextend () from /usr/lib/libbat.so.0 #2 0x00002aaaab9e6989 in BATextend () from /usr/lib/libbat.so.0 #3 0x00002aaaab91c1b2 in BATappend () from /usr/lib/libbat.so.0 #4 0x00002aaaaafcfdbf in BATappend_wrap () from /usr/lib64/MonetDB/lib_bat.so.0 #5 0x00002aaaaafccf83 in BATappend_wrap_unpack1034987346 () from /usr/lib64/MonetDB/lib_bat.so.0 #6 0x00002aaaaabdc39b in interpret () from /usr/lib/libmonet.so.0 #7 0x00002aaaaabe47ef in interpret_seqblock () from /usr/lib/libmonet.so.0 #8 0x00002aaaaabdbcb1 in interpret () from /usr/lib/libmonet.so.0 #9 0x00002aaaaabdd071 in interpret () from /usr/lib/libmonet.so.0 #10 0x00002aaaaabe47ef in interpret_seqblock () from /usr/lib/libmonet.so.0 #11 0x00002aaaaabdbcb1 in interpret () from /usr/lib/libmonet.so.0 #12 0x00002aaaaabe47ef in interpret_seqblock () from /usr/lib/libmonet.so.0 #13 0x00002aaaaabdbcb1 in interpret () from /usr/lib/libmonet.so.0 #14 0x00002aaaaabdbb69 in interpret () from /usr/lib/libmonet.so.0 #15 0x00002aaaaabe47ef in interpret_seqblock () from /usr/lib/libmonet.so.0 #16 0x00002aaaaabdbcb1 in interpret () from /usr/lib/libmonet.so.0 #17 0x00002aaaaabe7a99 in handleRequest () from /usr/lib/libmonet.so.0 #18 0x00002aaaaabe80c9 in doRequest () from /usr/lib/libmonet.so.0 #19 0x00002aaaaac2593a in monetInterpreter () from /usr/lib/libmonet.so.0 #20 0x00002aaaac013c09 in pthread_start_thread () from /lib/libpthread.so.0 ---Type <return> to continue, or q <return> to quit--- #21 0x00002aaaac013cb3 in pthread_start_thread_event () from /lib/libpthread.so.0 #22 0x00002aaaac5840a3 in clone () from /lib/libc.so.6 #23 0x0000000000000000 in ?? () (gdb) c Continuing. Program terminated with signal SIGKILL, Killed. The program no longer exists. (gdb) q

1 0

[Monetdb-developers] [noreply@sourceforge.net: [Bug 1490591] SSH host key change (new fingerprint)]
by Fabian Groffen 19 May '06

19 May '06

Hi all, FYI: ----- Forwarded message from "SourceForge.net" <noreply(a)sourceforge.net> ----- From: "SourceForge.net" <noreply(a)sourceforge.net> To: noreply(a)sourceforge.net Subject: [Bug 1490591] SSH host key change (new fingerprint) Date: Fri, 19 May 2006 00:47:32 -0700 url: https://sourceforge.net/tracker/?func=detail&atid=200001&aid=1490591&group_… burley changed: What | Value ---------------+--------------------------------- AssignedTo | David Burley (burley) Status | Closed --- Comment from David Burley (burley) 2006-05-19 03:47 --- Greetings, Per the site status page: ( 2006-05-17 12:04:02 - Project CVS Service ) As of 2006-05-17 at 12:00 Pacific we synchronized the SSH keys on all of the CVS hosts. This will cause SSH key mismatch errors for most projects. Please reconfirm the new SSH key against site doc G04 (https://www.sourceforge.net/docs/G04) and then accept the new key, if it matches per normal procedure. We apologize for the inconvenience, but this should be a one-time event and make future CVS infrastructure changes more seamless. Thank you, David Burley Quality of Service Analyst, SourceForge.net ----- End forwarded message -----

1 0

[Monetdb-developers] semantics of aggregation operations
by S.Idreos＠cwi.nl 18 May '06

18 May '06

Hi all, I would like to open a discussion on the semantics of operations. I just noticed for example that the sum operation will return nil if one or more of the BUNs in the BAT is nil. That is probably not the semantics that someone would expect, i.e., I would like to see the actual result by ignoring the nils. Given the current semantics the code that SQL generates has to first remove nils (with a select operation) and then apply the sum operation on a BAT. That costs more time and also results in one more intermediate result. What about updating the sum implementation to ignore nils? How much would affect that the various projects on top of MonetDB? Regards, Stratos

4 3

[Monetdb-developers] multiplex string-add returns empty BAT
by Peter Roozemaal 18 May '06

18 May '06

I am using monetdb 4.10.2 on an AMD64 Gentoo Linux system (the Gentoo ebuild). I suspect there's a bug in the handling of the multiplex string-add: The following mil code: var xxx := "aap noot mies".split(" "); (xxx [+] xxx).print(); prints an empty BAT: #-----------------# # h t # name # void str # type #-----------------# where I expected: [ nil, "aapaap" ] [ nil, "nootnoot" ] [ nil, "miesmies" ] It looks like every invocation of the string [+] gives an empty result. Greetings, Peter Roozemaal.

3 3

[Monetdb-developers] New vs. Existing Update Syntax
by Jens Teubner 18 May '06

18 May '06

Hi MonetDB/XQuery folks, I'm in the midst of implementing the support for the "official" XQuery Update Facility syntax. So far it looks like the current code is pretty good in line with the W3C draft. The update operations in the draft are very similar to the update functions we currently have. A few questions, however, appeared when implementing the new syntax: -- It seems to me like we do not (yet) have a rename() function that only changes the tag name of a given element, attribute, or processing-instruction node. -- It is not clear to me how our current insert-...() functions handle attributes in the new node list. The W3C draft provides separate upd:insertAttributes ($element, $attlist) and upd:insertBefore ($element, $nodelist) functions (and similar). The translation from the surface syntax to the update operations then takes care of invoking the right functions. Unfortunately, this translation (the split-up of attributes and the rest in particular) is non-trivial in XQuery Core. So we could--in line with the current implementation of element construction--push this treatment of attributes into the back-end. Any comments on this? How does the current code deal with attributes in the arguments of insert-...()? So far for now, Jens -- Jens Teubner Technische Universitaet Muenchen, Department of Informatics D-85748 Garching, Germany Tel: +49 89 289-17259 Fax: +49 89 289-17263 XQuery processing at the speed of light: MonetDB/XQuery http://www.monetdb-xquery.org/ http://www.pathfinder-xquery.org/

2 3

[Monetdb-developers] MonetDB website problem
by Fabian Groffen 18 May '06

18 May '06

http://monetdb.cwi.nl/TechDocs/APIs/Mapi/C/index.html Could someone *PLEASE* fix this? kthx.

1 0

[Monetdb-developers] New serialization routine
by Jan Rittinger 16 May '06

16 May '06

In the current version serialization takes 10 seconds for a 10 MB file (http://www-db.in.tum.de/~rittinge/files/mixed.xml) which contains only slightly more nodes (517448) then the auction xml file of the same size (472681). The difference however is the number of attribute nodes which is much higher in mixed.xml (517447 vs. 38266). While the serialization of doc("auction10MB.xml") takes 2.72 seconds, doc("mixed.xml") requires 10.34 seconds!! Removing the attributes in mixed.xml (by deleting all entries from the attr_own bat) speeds up the serialization to complete in 4.6 seconds. Some more calculations reveal that for the auction file we are able to serialize 187 nodes/sec (nodes = elements+textnodes+attributes) while for mixed.xml the serialization function (with and without attributes) was only able to generate about 100 nodes/sec. In all 3 cases the serialization seems way to slow... (at least for me). As in principle the serialization is only a dump of the tables (even in table order) and other approaches are really faster we should be able to come up with an appropriate fast serialization routine. I see at least three possibilities to increase the performance: * serialize.mx uses about 50 function calls until one node without attributes is serialized * serialize.mx does collect the nodes using random access with a lot of indirections * serialize.mx uses stream_printf which is probably slower than a fixed size print routine like stream_write. In the following two weeks (before the feature freeze) I will try to come up with a new prototypical print routine that should handle the serialization more efficiently. This prototype will be a proof of concept and probably will fall back to current routine whenever some conditions are not fulfilled (e.g. wrong serialization type or multiple namespaces). Let's see wether we can get a faster serialization routine for the average query result! I will probably need help for some gdk internals, changes introduced by the update facility (e.g. indirections), and for understanding parts of the current serialize.mx. I hope for your support :-) More information on the new serialization routine will be available at the pathfinder wiki. Cheers, Jan -- Jan Rittinger Database Systems Technische Universität München (Germany) http://www-db.in.tum.de/~rittinge/

2 1

[Monetdb-developers] Bug in MonetDBv4.10.2
by Bart Scheers 11 May '06

11 May '06

Beste lezer, Ik gebruik monetdb v 4.10.2 met de bijbehorende jdbc driver. Na het creëren van een tabel met kolom van type 'double' kan ik via een PreparedStatement geen setDouble(d) aanroepen. Ik krijg de foutmelding: SQLException Message: wrong argument for prepared statement (expected double instead of decimal) en het is toch echt een double (te zien via SQL front end met \d). Als ik de DBMetaData ophaal (ik dacht slim te zijn door hiet het DATA_TYPE op te halen) krijg ik een error: SQLException: syntax error, unexpected IDENT in: "select "sqlname" as "TYPE_NAME", cast(case "sqlname" when 'timetz' then 92 when 'table' then 2003 when 'blob' then 2004 when 'bigint' then -5 when 'time' then 92 when 'varchar' then 12 when 'clob' then 2005 when 'int' then 4 when 'timestamptz' then 93 when 'date' then 91 when 'sec_interval' then -5 when 'boolean' then 16 when 'decimal' then 3 when 'double' then 8 when 'char' then 1 when 'month_interval' then 4 when 'oid' then 1111 when 'smallint' then 5 when 'timestamp' then 93 when 'real' then 7 else 1111 end as smallint) as "DATA_TYPE", "digits" as "PRECISION", cast(case when "systemname" = 'str' then cast('\' AS char) ELSE cast(NULL AS char) END) AS "LITERAL_PREFIX", cast(CASE WHEN "systemname" = 'str" Haakje of kwootje verkeerd? Al met al betekent het dat ik dan geen PreparedStatement kan uitvoeren, wat het wel sneller zou maken. Is dit bekend bij jullie? Groeten Bart Scheers

2 1

Re: Re: [Monetdb-developers] MapiClient connet problem
by Fabian Groffen 10 May '06

10 May '06

Hi, I seems that the mil support is not started by default. You can do this by typing on the server prompt: mapi_start(); After this command MapiClient should work. Beware that mil mode (the default) does not allow you to easily express XQuery queries; instead use the -lxquery flag. I don't know how this is done in the Windows version, but unfortunately MapiClient can't do an interactive session with xquery, so you have to give the file you want to execute as argument. If someone using Windows knows how this can be done the best way, please fill me in. Regards On 10-05-2006 18:34:35 +0800, zhangxin525 wrote: > Hi, > Thanks for your reply! > > First, sorry for my careless. I did not give you an exact copy of the error message. > The exact error message is : > > !ERROR mapi_reconnect: connect: error 10061 > MAPI = anonymous@localhost:50000 > ACTION= mapi_reconnect > ERROR = Setup connection failed > > > I start the MonetDB/XQuery server, the message of the server windows: > > # Monet Database Server V4.10.2 > # Copyright (c) 1993-2006, CWI. All rights reserved. > # Compiled for i386-pc-mingw32/32bit with 32bit OIDs; dynamically linked. > # Visit http://monetdb.cwi.nl/ for further information. > MonetDB> > > I think the server is correct. > Other, when I install MonetDB/XQuery, I chose the user for everynoe. > > Thanks for your patient help again. > > > > > zhangxin525 > 2006-05-10 > > > > 发件人： Fabian Groffen > 发送时间： 2006-05-10 16:40:59 > 收件人： zhangxin525 > 抄送： monetdb-developers > 主题： Re: [Monetdb-developers] MapiClient connet problem > > Hi, > > Thanks for your interest in MonetDB/XQuery. > > On 10-05-2006 16:08:26 +0800, zhangxin525 wrote: > > Hello! > > > > I install MonetDB/XQuery in WindowsXP, and I have start the XUery Server, but when I start MapiClient through command, always get the message: > > > > !ERROR mapi_reconnect: connect: > > MAPI = anonymous@localhost:5000 > > Is this an exact copy of the error message? In case it is, there is a 0 > missing here, the port should be 50000 not 5000. I think you can change > that somewhere in the .bat script that's called from the start menu. > > Maybe this is just a copy/paste error, so if this is not the problem, > can you copy and paste what's in the MonetDB/XQuery server window? > > Regards

1 0