July 2008 - users-list

[MonetDB-users] Repeated database corruption - v2.24.0
by Kirk Abbott 13 Jul '08

13 Jul '08

Hello, I am using Monetdb on Windows XP (see the server specs below). Unfortunately, I seem to corrupt the database very frequently involving a complete removal of the MonetDB5 directory (and all associated work). Corruption seems to occur if I hit a Ctrl-C (say on a long running query). Questions: 1) Is this a problem only on Windows? or is it a problem with this version of the server? 2) Is there a better way to kill a long running query? Clearly, corrupting the entire database (it won't restart!) just by killing a query, does not confidence build Any ideas? Kirk. # MonetDB server v5.6.0, based on kernel v1.24.0 # Serving database 'demo' # Compiled for i686-pc-win32/32bit with 32bit OIDs dynamically linked # Copyright (c) 1993-2008 CWI, all rights reserved # Visit http://monetdb.cwi.nl/ for further information #warning: please don't forget to set your vault key! #(see C:\Program Files\CWI\MonetDB5\etc\monetdb5.conf) # Listening for connection requests on mapi:monetdb://127.0.0.1:50000/ # MonetDB/SQL module v2.24.0 loaded >

2 2

[MonetDB-users] SQL Table partitioning in MonetDB
by Napoma 10 Jul '08

10 Jul '08

I have this problem... i have a table with 33.000.000 of records.. the table is named i_predicate with four columns as follows (oid, name, isubj, iobj)... i want to execute a physical partition on i-predicate respect to the values of name column.. in this way if i query i_predicate monetdb has to use only the respective partition with the respective value of name... does it exist a sql statement for creating partitions of i_predicate? does it exist a script for this partition on MonetDB? and if i create the partition... i have to define function to query correctly the partitions? Thanks -- View this message in context: http://www.nabble.com/SQL-Table-partitioning-in-MonetDB-tp18384206p18384206… Sent from the monetdb-users mailing list archive at Nabble.com.

3 2

[MonetDB-users] PF: warning: query will always return an error
by Ying Zhang 10 Jul '08

10 Jul '08

Hello, In stable branch + milprint_summer, executing the following query (you need to have a "hello.xml" doc shredded in collection "hello"): let $path := 'backup/test/hello/' let $index := element documents { for $document at $pos in pf:documents('hello') let $uri := concat($path, string(10000 + (($pos div 10000)) cast as xs:integer), '/', string($pos) , '.xml') return (text { "
 " }, element document { attribute uri {$uri}, $document/text() }), text { "
" } } return (put($index, concat($path,'documents.xml')), for $document in $index/document return put(exactly-one(doc(string($document))), exactly-one($document/@uri))) Results in the first 'put' is done, while the second 'put' is not executed, actually, the MIL code generated by 'pf' contains only translation of (the first) one 'put'. Also, the query gives a warning: query will always return an error If I comment out the first 'put', the second 'put' in the for-loop get executed, *without* the warning. Executing a similar query: (put(<a/>, "a.xml"), for $n in ("b.xml", "c.xml") return put(exactly-one(doc("hello.xml")), $n) ) also results in the warning, however, the generated MIL code contains translation of both 'put' and three documents are put in dbfarm. I'd like to know why the first query fails, and what has triggered the warning. Thanks a lot! Kind regards, Jennie

6 11

Re: [MonetDB-users] MonetDB/XQuery - Bug 1899258
by Ying Zhang 10 Jul '08

10 Jul '08

On Wed, Jul 09, 2008 at 06:29:08PM +0200, Andreas Meinl wrote: > Hi Ying Zhang, > > regarding bug 1899258 "PF: Error message with Administrative Console": I > still have the same problem, even with the current release of > MonetDB/XQuery, which I downloaded just today. The package is called > MonetDB4-XQuery-Installer-i386-20080624.msi. You have closed this bug on 20 > June 2008. How can I check which version of libxml2 I have installed (or, > is bundled with this release of MonetDB/XQuery)? I've attached two > screenshots with similar error messages. Thanks a lot! Hello Andreas, Given the second screenshot, it indeed looks like you are still having this problem. Is it true that if you click on one of the buttons for the first time, it will first hang for about 30 seconds, before you get this error message? In the current release, the Windows installer contains (should contain) an older version of libxml2 (2.6.30) due to this problem. So, this error should actually not happen. You can find the libxml2 DLL file in the lib directory of your installation dir, which is typically 'program files\cwi'. So please check you have the correct version of libxml2 in your installation. Regards, Jennie > > Regards, > > Andreas Meinl > > > > > >

1 0

[MonetDB-users] ODBC + non-ascii
by Pawel Lewicki 08 Jul '08

08 Jul '08

Hi, I don't know if problem is related to used interface (ODBC) but I have a problem with inserting non-ascii data. All data I insert seems broken. I started with 'utf-8' but tested 'cp1250' and 'iso8859-2' as well. No luck. All data I take back has broken non-ascii characters. Any clues? (Windows 32-bit "Jun 2008" release) Pawel Lewicki

2 4

[MonetDB-users] Update using two (2) tables
by Kirk Abbott 04 Jul '08

04 Jul '08

Hello, I am having trouble with the syntax for doing an update using 2 tables. In postgres, one can do something like: update table1 set name = table2.name from table2 where table1.id = table2.id ; In oracle (it's something like) update table1 a set name = (select b.name from table2 b where a.id = b.id) ; What is the correct way to do this in MonetDb (as both of the above fail) Thanks, Kirk.

3 2

[MonetDB-users] XQ: inconsistency between fn:collection and pf:collection after a del-doc
by luc touraille 03 Jul '08

03 Jul '08

Hi, Currently working on a big project with MonetDB XQuery, I stumbled upon an awkward bug (unless it is a *very* perturbing feature): after deleting a document in a collection "myColl", using the function pf:del-doc, this document is still displayed when calling fn:collection("myColl"), and not when using pf:collection("myColl"). I assume the latter result is the expected one, so why is the first query displaying data that is not supposed to be in the database anymore ? Have I misunderstood something or is it a true bug (maybe related to the http://www.nabble.com/--monetdb-Bugs-1976341---XQ%3A-leftovers-after-deleti… bug #1976341 : leftovers after deleting a document ) ? N.B.: this problem occured with the Feb 2008 release; I tried to reproduce it with the Jun 2008 release, and this time it's the pf:collection() function that gave me the wrong results (the fn: one being unsupported yet). Greetings, Luc Touraille -- View this message in context: http://www.nabble.com/XQ%3A-inconsistency-between-fn%3Acollection-and-pf%3A… Sent from the monetdb-users mailing list archive at Nabble.com.

2 2