- developers-list - monetdb.org

Re: [Monetdb-developers] RDF data management in MonetDB/SQL
by wangx 17 Jul '10

17 Jul '10

Dear Lefteris, Thank you for your reply. Your explanation will help me much. In addition, would you give me some guidelines on how to make the 6 different indices of the triple table be understood by the SQL/SPARQL query optimizer and used accordingly. If I want to implement this feature by myself, in which files the code should be added or modified. BTW, in the future, will you implement the MonetDB/SPARQL as a new supported front-end language? Will you consider to translate SPARQL to MAL directly, instead of through SQL to MAL (but this way you have to develop a SPARQL specific optimizer, instead of making use of the SQL optimizer)? Thank you so much. Best regards, Xin Wang >From: Lefteris <lsidir(a)gmail.com> >Reply-To: >To: wangx <wangx(a)tju.edu.cn> >Subject: Re: [Monetdb-developers] RDF data management in MonetDB/SQL >Date:Fri, 16 Jul 2010 10:29:53 +0200 > >Hi, > >your understanding is in general correct. The availability of the six >different indices of the triple table should be understood by the >SQL/SPARQL query optimizer and used accordingly. However, the >MonetDB/RDF module has not been announced yet, and that is because it >has not finished yet. You are using a piece of code which is >experimental and unfinished. As such, the only way to test Monet and >its capabilities on RDF data is to manually write the SQL query in >such a way that you use the correct order of the triple table on the >correct join. > >In the future of course, this will be done by the optimizer and the >user will only have to write simple SPARQL queries referring to the >name of the graph, instead of the underlying storage schema, but until >then I am afraid you will have to do it by hand. The good news is that >if you are using RDF data and testing queries that have been published >previously on papers as benchmarks, most likely someone else will have >done already the translation to a correct SQL query (since most >experiments on newly build engines that do not support SPARQL use this >method). > >Hope this helps you a bit, > >lefteris > >2010/7/15 wangx : >> Hi MonetDB developers, >> I have a question about RDF data management in MonetDB/SQL. The comment of >> sql.rdfshred says "shredding an RDF data file from location results in 7 new >> tables (6 permutations of SPO and a mapping) ... We can then query with SQL >> queries the RDF triple store by quering tables gid_spo, gid_pso etc., ...". >> In my option, if the spo table is considered the triples table, the other 5 >> tables (sop, pso, pos, osp, ops) (except the mapping table) can be viewed as >> indexes of the triples table spo. >> When I writeSQLto query the shredded RDF data in the triples table, I >> have two ways.The first way is toonly use spo table tomake self-joins. >> The second way is touse all 6 tables to make joins. I noticed that >> "MonetDB/SQL Reference Manual" says that "The heart is the MonetDB server, >> which comes with the following innovative features. ... Index selection, >> creation and maintenance is automatic". IfI use6 tables (as indexes) >> explicitly to make joins, it seems that I write the query plan by myself. >> However, I think this work should be done by the SQL optimizer using >> statistics from the system catalog. I wondered if these tables have >> alreadybeen specified as indexes in the internal code, or if there is a way >> to specify it so that the optimizer can use them as indexes to generate >> query plans. I am not sure if my understanding is correct. I will appreciate >> any help from developers. Thank you in advance. >> >> Best regards, >> Xin Wang >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >> _______________________________________________ >> Monetdb-developers mailing list >> Monetdb-developers(a)lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/monetdb-developers >> >> >

2 1

Re: [Monetdb-developers] MonetDB: default - implement timing per server response for resu...
by Stefan Manegold 16 Jul '10

16 Jul '10

On Thu, Jul 15, 2010 at 03:25:39PM +0200, Fabian Groffen wrote: > Changeset: dfcab86b0cb0 for MonetDB > URL: http://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=dfcab86b0cb0 > Modified Files: > clients/ChangeLog > clients/src/mapiclient/mclient.mx > Branch: default > Log Message: > > implement timing per server response for results and updates for SQL formatter > [...] > diff -r df828b8fc84c -r dfcab86b0cb0 clients/src/mapiclient/mclient.mx > --- a/clients/src/mapiclient/mclient.mx Thu Jul 15 15:09:22 2010 +0200 > +++ b/clients/src/mapiclient/mclient.mx Thu Jul 15 15:11:07 2010 +0200 > @@ -342,6 +342,26 @@ > } > } > > +static char htimbuf[32]; > +static char * > +timerHuman() > +{ > + long t = t1 - t0; > + > + if (t / 1000 < 950) { > + snprintf(htimbuf, 32, "%ld.%03ldms", t / 1000, t % 1000); > + return(htimbuf); > + } > + t /= 1000; > + if (t / 1000 < 60) { > + snprintf(htimbuf, 32, "%ld.%02lds", t / 1000, t % 1000); > + return(htimbuf); > + } > + t /= 1000; > + snprintf(htimbuf, 32, "%ldm %lds", t / 60, t % 60); > + return(htimbuf); > +} > + > /* The Mapi library eats away the comment lines, which we need to > * detect end of debugging. We overload the routine to our liking. */ > [...] While I like the new timing feature as well as the convenient formatting for human readability, I am wondering about two potential changes / extensions: (a) While the time formatting is convenient for human readbility, it might be less convenient for automatic (post-)processing, e.g., creating performance figures. For that, plain unformatted microseconds (in addition to the human-readable format) might be more convenient. (b) The "old" (still existing) "Timer" information is sent to stderr, thus, one can seem the Timer output without the need to grep through (potentially large) output, e.g., by simply redirecting the output to a file or even /dev/null --- obviously, aligning stderr & stdout in case of large multi-query scripts is then left to the user. The new timing output goes (together with the queries status summary like how many result tuples were produced) to stdout (only). (c) As the announcement (changelog) says, the new timing output is only produced with the "sql" formatter (i.e., not with, e.g., "raw" or "test", and hence, also not by default with `-s <sql-statement>` (unless one explicitly requests `-f sql`). For (a) & (b) would it be an option to consider to also send the plain unformatted times in microseconds to stderr to (better) support automatic post-processing of the timings? To cover also (c), we could consider doing that with all formatters, not only with "sql". ... just some ideas to think about and discuss ... Stefan -- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4199 |

3 3

[Monetdb-developers] RDF data management in MonetDB/SQL
by wangx 16 Jul '10

16 Jul '10

Hi MonetDB developers, I have a question about RDF data management in MonetDB/SQL. The comment of sql.rdfshred says "shredding an RDF data file from location results in 7 new tables (6 permutations of SPO and a mapping) ... We can then query with SQL queries the RDF triple store by quering tables gid_spo, gid_pso etc., ...". In my option, if the spo table is considered the triples table, the other 5 tables (sop, pso, pos, osp, ops) (except the mapping table) can be viewed as indexes of the triples table spo. When I write SQL to query the shredded RDF data in the triples table, I have two ways. The first way is to only use spo table to make self-joins. The second way is to use all 6 tables to make joins. I noticed that "MonetDB/SQL Reference Manual" says that "The heart is the MonetDB server, which comes with the following innovative features. ... Index selection, creation and maintenance is automatic". If I use 6 tables (as indexes) explicitly to make joins, it seems that I write the query plan by myself. However, I think this work should be done by the SQL optimizer using statistics from the system catalog. I wondered if these tables have already been specified as indexes in the internal code, or if there is a way to specify it so that the optimizer can use them as indexes to generate query plans. I am not sure if my understanding is correct. I will appreciate any help from developers. Thank you in advance. Best regards, Xin Wang

2 1

[Monetdb-developers] TPC-H benchmark about MonetDB
by kun ren 16 Jul '10

16 Jul '10

Dear everyone, Recently,i am testing the performance of MonetDB. But I want to know the time of execution one sql. I type \t on CLI. and then it returns a execution time. But I found that the time include the print resultset time.I just only want to know the time of execution ,not include the print time. So please tell me what do i do? -----------------Best regards!

3 7

[Monetdb-developers] TPC-H Query-14
by Romulo Goncalves 15 Jul '10

15 Jul '10

Hello, I am running TPC-H in the default version, updated 1 minute ago. Compilation in Debug mode and I am running in my Desktop at CWI. I loaded TPC-H SF-10 without constraints. [goncalve@alviss queries]$ mclient -lsql < 14.sql MAPI = monetdb@localhost:55000 QUERY = select ERROR = !SQLException:convert:too many digits (20 > 19) #select * from optimizer_stats() stats; % .stats, .stats # table_name % rewrite, count # name % clob, int # type % 7, 1 # length [ "joinidx", 0 ] [goncalve@alviss queries]$ Why do I get an Exception when I got a result? Regards, Romulo

3 2

[Monetdb-developers] bug #2341 [was: MonetDB scalability]
by Mark Bucciarelli 15 Jul '10

15 Jul '10

[Moving thread from -users to -dev.] On Thu, Jul 8, 2010 at 6:28 PM, Niels Nes <Niels.Nes(a)cwi.nl> wrote: > On Thu, Jul 08, 2010 at 03:05:35PM -0400, Mark Bucciarelli wrote: >> >> Dropping a column corrupts DB (#2341). >> Same as above. > > Both were fixed some time ago and tests were added by sjoerd. > These run fine, ie I closed them. > By "some time ago" you must mean post-Feb2010 release. I just corrupted my database by deleting a column and a constraint. Could you link the changeset to the ticket so I can apply the patch manually? If you applied fix to Feb2010 branch, please link that changeset, as that's what I am running. Thanks, m

1 0

Re: [Monetdb-developers] MonetDB: Jun2010 - disable parallelism (mitosis & dataflow) to a...
by Stefan Manegold 13 Jul '10

13 Jul '10

This changeset accientally contains changes to file sql/src/server/sql_parser.mx that should have gone into a seperate checking / changeset: " Refined my earlier fix "fixed (restored) order_by over union_all" (http://dev.monetdb.org/hg/MonetDB/rev/35ebc65eb74c) we now also (re-)allow ORDER BY over EXCEPT & UNION . Note. though, that (as also in Feb2010 and most probably earlier releases, MonetDB incorrectly ignores ORDER BY over UNION, EXCEPT & INTERSECT. See also Bug 2606 (http://bugs.monetdb.org/2606) " Stefan On Tue, Jul 13, 2010 at 10:16:39AM +0200, Stefan Manegold wrote: > Changeset: e399a0ffae31 for MonetDB > URL: http://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e399a0ffae31 > Modified Files: > sql/src/server/sql_parser.mx > sql/src/test/BugTracker-2009/Tests/POWER_vs_prod.SF-2596114.sql > sql/src/test/BugTracker-2009/Tests/POWER_vs_prod.SF-2596114.stable.out > sql/src/test/BugTracker-2009/Tests/POWER_vs_prod.SF-2596114.stable.out.Debian > sql/src/test/BugTracker-2009/Tests/POWER_vs_prod.SF-2596114.stable.out.Windows > sql/src/test/BugTracker-2009/Tests/explain_gives_crash.SF-2741829.sql > sql/src/test/BugTracker-2009/Tests/explain_gives_crash.SF-2741829.stable.out > sql/src/test/BugTracker-2009/Tests/explain_gives_crash.SF-2741829.stable.out.Debian > sql/src/test/BugTracker-2009/Tests/explain_gives_crash.SF-2741829.stable.out.Windows > sql/src/test/BugTracker-2010/Tests/group-by_ordered_column.Bug-2564.sql > sql/src/test/BugTracker-2010/Tests/group-by_ordered_column.Bug-2564.stable.out > sql/src/test/BugTracker-2010/Tests/group-by_ordered_column.Bug-2564.stable.out.32bit > sql/src/test/BugTracker/Tests/explain.SF-1739353-data.sql > sql/src/test/BugTracker/Tests/explain.SF-1739353.stable.out > sql/src/test/Tests/trace.sql > sql/src/test/Tests/trace.stable.out > Branch: Jun2010 > Log Message: > > disable parallelism (mitosis & dataflow) to avoid ambiguous EXPLAIN results > > > diffs (truncated from 630 to 300 lines): > > diff -r 75116ec8f9a7 -r e399a0ffae31 sql/src/server/sql_parser.mx > --- a/sql/src/server/sql_parser.mx Tue Jul 13 01:09:49 2010 +0200 > +++ b/sql/src/server/sql_parser.mx Tue Jul 13 10:16:33 2010 +0200 > @@ -2922,7 +2922,11 @@ > { > $$ = $1; > if ($2 || $3 || $4) { > - if ($1 != NULL && ($1->token == SQL_SELECT || $1->token == SQL_UNION)) { > + if ($1 != NULL && > + ($1->token == SQL_SELECT || > + $1->token == SQL_UNION || > + $1->token == SQL_EXCEPT || > + $1->token == SQL_INTERSECT)) { > SelectNode *s = (SelectNode*)$1; > > s -> orderby = $2; > diff -r 75116ec8f9a7 -r e399a0ffae31 sql/src/test/BugTracker-2009/Tests/POWER_vs_prod.SF-2596114.sql > --- a/sql/src/test/BugTracker-2009/Tests/POWER_vs_prod.SF-2596114.sql Tue Jul 13 01:09:49 2010 +0200 > +++ b/sql/src/test/BugTracker-2009/Tests/POWER_vs_prod.SF-2596114.sql Tue Jul 13 10:16:33 2010 +0200 > @@ -1,3 +1,5 @@ > +-- disable parallelism (mitosis & dataflow) to avoid ambiguous results > +set optimizer='inline,remap,evaluate,costModel,coercions,emptySet,aliases,mergetable,deadcode,commonTerms,joinPath,reorder,deadcode,reduce,history,multiplex,garbageCollector'; > create table SF_2596114 (x double); > explain select power(x,2) from SF_2596114; > explain select x*x from SF_2596114; > diff -r 75116ec8f9a7 -r e399a0ffae31 sql/src/test/BugTracker-2009/Tests/POWER_vs_prod.SF-2596114.stable.out > --- a/sql/src/test/BugTracker-2009/Tests/POWER_vs_prod.SF-2596114.stable.out Tue Jul 13 01:09:49 2010 +0200 > +++ b/sql/src/test/BugTracker-2009/Tests/POWER_vs_prod.SF-2596114.stable.out Tue Jul 13 10:16:33 2010 +0200 > @@ -31,7 +31,6 @@ > % 0 # length > function user.s0_1{autoCommit=true}():void; > _2 := sql.mvc(); > -barrier _36 := language.dataflow(); > _3:bat[:oid,:dbl] := sql.bind(_2,"sys","sf_2596114","x",0); > _8:bat[:oid,:dbl] := sql.bind(_2,"sys","sf_2596114","x",2); > _10 := algebra.kdifference(_3,_8); > @@ -42,7 +41,6 @@ > _16 := bat.reverse(_15); > _17 := algebra.kdifference(_14,_16); > _18:bat[:oid,:dbl] := batmmath.pow(_17,2); > -exit _36; > _19 := sql.resultSet(1,1,_18); > sql.rsColumn(_19,"sys.","power_x","double",53,0,_18); > _25 := io.stdout(); > @@ -54,7 +52,6 @@ > % 0 # length > function user.s1_1{autoCommit=true}():void; > _2 := sql.mvc(); > -barrier _35 := language.dataflow(); > _3:bat[:oid,:dbl] := sql.bind(_2,"sys","sf_2596114","x",0); > _8:bat[:oid,:dbl] := sql.bind(_2,"sys","sf_2596114","x",2); > _10 := algebra.kdifference(_3,_8); > @@ -65,7 +62,6 @@ > _16 := bat.reverse(_15); > _17 := algebra.kdifference(_14,_16); > _18:bat[:oid,:dbl] := batcalc.*(_17,_17); > -exit _35; > _19 := sql.resultSet(1,1,_18); > sql.rsColumn(_19,"sys.","sql_mul_x","double",53,0,_18); > _25 := io.stdout(); > diff -r 75116ec8f9a7 -r e399a0ffae31 sql/src/test/BugTracker-2009/Tests/POWER_vs_prod.SF-2596114.stable.out.Debian > --- a/sql/src/test/BugTracker-2009/Tests/POWER_vs_prod.SF-2596114.stable.out.Debian Tue Jul 13 01:09:49 2010 +0200 > +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 > @@ -1,74 +0,0 @@ > -stdout of test 'POWER_vs_prod.SF-2596114` in directory 'src/test/BugTracker-2009` itself: > - > - > -# 23:02:29 > > -# 23:02:29 > mserver5 "--config=/ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/etc/monetdb5.conf" --debug=10 --set gdk_nr_threads=0 --set "monet_mod_path=/ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/lib64/MonetDB5:/ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/lib64/MonetDB5/lib:/ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/lib64/MonetDB5/bin" --set "gdk_dbfarm=/ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/var/MonetDB5/dbfarm" --set "sql_logdir=/ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/var/MonetDB5/sql_logs" --set mapi_open=true --set xrp > c_open=true --set mapi_port=33742 --set xrpc_port=44239 --set monet_prompt= --trace "--dbname=mTests_src_test_BugTracker-2009" --set mal_listing=0 "--dbinit= include sql;" ; echo ; echo Over.. > -# 23:02:29 > > - > -# MonetDB server v5.10.3, based on kernel v1.28.3 > -# Serving database 'mTests_src_test_BugTracker-2009', using 4 threads > -# Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked > -# Copyright (c) 1993-July 2008 CWI. > -# Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved > -# Visit http://monetdb.cwi.nl/ for further information > -# Listening for connection requests on mapi:monetdb://rig.ins.cwi.nl:33742/ > -# MonetDB/SQL module v2.28.1 loaded > - > -Ready. > -#function user.main():void; > -# clients.quit(); > -#end main; > - > -Over.. > - > -# 15:46:08 > > -# 15:46:08 > mclient -lsql -i -umonetdb -Pmonetdb --host=rig --port=35464 > -# 15:46:08 > > - > -% .explain # table_name > -% mal # name > -% clob # type > -% 0 # length > -function user.s0_1{autoCommit=true}():void; > - _2 := sql.mvc(); > - _3:bat[:oid,:dbl] := sql.bind(_2,"sys","sf_2596114","x",0); > - _8:bat[:oid,:dbl] := sql.bind(_2,"sys","sf_2596114","x",2); > - _10 := algebra.kdifference(_3,_8); > - _11 := algebra.kunion(_10,_8); > - _12:bat[:oid,:dbl] := sql.bind(_2,"sys","sf_2596114","x",1); > - _14 := algebra.kunion(_11,_12); > - _15:bat[:oid,:oid] := sql.bind_dbat(_2,"sys","sf_2596114",1); > - _16 := bat.reverse(_15); > - _17 := algebra.kdifference(_14,_16); > - _18:bat[:oid,:dbl] := batmmath.pow(_17,2); > - _19 := sql.resultSet(1,1,_18); > - sql.rsColumn(_19,"sys.","power_x","double",53,0,_18); > - _25 := io.stdout(); > - sql.exportResult(_25,_19); > -end s0_1; > -% .explain # table_name > -% mal # name > -% clob # type > -% 0 # length > -function user.s1_1{autoCommit=true}():void; > - _2 := sql.mvc(); > - _3:bat[:oid,:dbl] := sql.bind(_2,"sys","sf_2596114","x",0); > - _8:bat[:oid,:dbl] := sql.bind(_2,"sys","sf_2596114","x",2); > - _10 := algebra.kdifference(_3,_8); > - _11 := algebra.kunion(_10,_8); > - _12:bat[:oid,:dbl] := sql.bind(_2,"sys","sf_2596114","x",1); > - _14 := algebra.kunion(_11,_12); > - _15:bat[:oid,:oid] := sql.bind_dbat(_2,"sys","sf_2596114",1); > - _16 := bat.reverse(_15); > - _17 := algebra.kdifference(_14,_16); > - _18:bat[:oid,:dbl] := batcalc.*(_17,_17); > - _19 := sql.resultSet(1,1,_18); > - sql.rsColumn(_19,"sys.","sql_mul_x","double",53,0,_18); > - _25 := io.stdout(); > - sql.exportResult(_25,_19); > -end s1_1; > - > -# 23:02:30 > > -# 23:02:30 > Done. > -# 23:02:30 > > - > diff -r 75116ec8f9a7 -r e399a0ffae31 sql/src/test/BugTracker-2009/Tests/POWER_vs_prod.SF-2596114.stable.out.Windows > --- a/sql/src/test/BugTracker-2009/Tests/POWER_vs_prod.SF-2596114.stable.out.Windows Tue Jul 13 01:09:49 2010 +0200 > +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 > @@ -1,74 +0,0 @@ > -stdout of test 'POWER_vs_prod.SF-2596114` in directory 'src/test/BugTracker-2009` itself: > - > - > -# 23:02:29 > > -# 23:02:29 > mserver5 "--config=/ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/etc/monetdb5.conf" --debug=10 --set gdk_nr_threads=0 --set "monet_mod_path=/ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/lib64/MonetDB5:/ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/lib64/MonetDB5/lib:/ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/lib64/MonetDB5/bin" --set "gdk_dbfarm=/ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/var/MonetDB5/dbfarm" --set "sql_logdir=/ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/var/MonetDB5/sql_logs" --set mapi_open=true --set xrp > c_open=true --set mapi_port=33742 --set xrpc_port=44239 --set monet_prompt= --trace "--dbname=mTests_src_test_BugTracker-2009" --set mal_listing=0 "--dbinit= include sql;" ; echo ; echo Over.. > -# 23:02:29 > > - > -# MonetDB server v5.10.3, based on kernel v1.28.3 > -# Serving database 'mTests_src_test_BugTracker-2009', using 4 threads > -# Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked > -# Copyright (c) 1993-July 2008 CWI. > -# Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved > -# Visit http://monetdb.cwi.nl/ for further information > -# Listening for connection requests on mapi:monetdb://rig.ins.cwi.nl:33742/ > -# MonetDB/SQL module v2.28.1 loaded > - > -Ready. > -#function user.main():void; > -# clients.quit(); > -#end main; > - > -Over.. > - > -# 15:46:08 > > -# 15:46:08 > mclient -lsql -i -umonetdb -Pmonetdb --host=rig --port=35464 > -# 15:46:08 > > - > -% .explain # table_name > -% mal # name > -% clob # type > -% 0 # length > -function user.s0_1{autoCommit=true}():void; > - _2 := sql.mvc(); > - _3:bat[:oid,:dbl] := sql.bind(_2,"sys","sf_2596114","x",0); > - _8:bat[:oid,:dbl] := sql.bind(_2,"sys","sf_2596114","x",2); > - _10 := algebra.kdifference(_3,_8); > - _11 := algebra.kunion(_10,_8); > - _12:bat[:oid,:dbl] := sql.bind(_2,"sys","sf_2596114","x",1); > - _14 := algebra.kunion(_11,_12); > - _15:bat[:oid,:oid] := sql.bind_dbat(_2,"sys","sf_2596114",1); > - _16 := bat.reverse(_15); > - _17 := algebra.kdifference(_14,_16); > - _18:bat[:oid,:dbl] := batmmath.pow(_17,2); > - _19 := sql.resultSet(1,1,_18); > - sql.rsColumn(_19,"sys.","power_x","double",53,0,_18); > - _25 := io.stdout(); > - sql.exportResult(_25,_19); > -end s0_1; > -% .explain # table_name > -% mal # name > -% clob # type > -% 0 # length > -function user.s1_1{autoCommit=true}():void; > - _2 := sql.mvc(); > - _3:bat[:oid,:dbl] := sql.bind(_2,"sys","sf_2596114","x",0); > - _8:bat[:oid,:dbl] := sql.bind(_2,"sys","sf_2596114","x",2); > - _10 := algebra.kdifference(_3,_8); > - _11 := algebra.kunion(_10,_8); > - _12:bat[:oid,:dbl] := sql.bind(_2,"sys","sf_2596114","x",1); > - _14 := algebra.kunion(_11,_12); > - _15:bat[:oid,:oid] := sql.bind_dbat(_2,"sys","sf_2596114",1); > - _16 := bat.reverse(_15); > - _17 := algebra.kdifference(_14,_16); > - _18:bat[:oid,:dbl] := batcalc.*(_17,_17); > - _19 := sql.resultSet(1,1,_18); > - sql.rsColumn(_19,"sys.","sql_mul_x","double",53,0,_18); > - _25 := io.stdout(); > - sql.exportResult(_25,_19); > -end s1_1; > - > -# 23:02:30 > > -# 23:02:30 > Done. > -# 23:02:30 > > - > diff -r 75116ec8f9a7 -r e399a0ffae31 sql/src/test/BugTracker-2009/Tests/explain_gives_crash.SF-2741829.sql > --- a/sql/src/test/BugTracker-2009/Tests/explain_gives_crash.SF-2741829.sql Tue Jul 13 01:09:49 2010 +0200 > +++ b/sql/src/test/BugTracker-2009/Tests/explain_gives_crash.SF-2741829.sql Tue Jul 13 10:16:33 2010 +0200 > @@ -1,3 +1,5 @@ > +-- disable parallelism (mitosis & dataflow) to avoid ambiguous results > +set optimizer='inline,remap,evaluate,costModel,coercions,emptySet,aliases,mergetable,deadcode,commonTerms,joinPath,reorder,deadcode,reduce,history,multiplex,garbageCollector'; > \f csv > create table blabla(id integer); > select '#~BeginVariableOutput~#'; > diff -r 75116ec8f9a7 -r e399a0ffae31 sql/src/test/BugTracker-2009/Tests/explain_gives_crash.SF-2741829.stable.out > --- a/sql/src/test/BugTracker-2009/Tests/explain_gives_crash.SF-2741829.stable.out Tue Jul 13 01:09:49 2010 +0200 > +++ b/sql/src/test/BugTracker-2009/Tests/explain_gives_crash.SF-2741829.stable.out Tue Jul 13 10:16:33 2010 +0200 > @@ -28,8 +28,7 @@ > #~BeginVariableOutput~# > function user.s1_1{autoCommit=true}():void; > _2 := sql.mvc(); > -" sql.catalog(29\,\"sys\"\,139834807776504\,0);" > -barrier _37 := language.dataflow(); > +" sql.catalog(29\,\"sys\"\,140688029790296\,0);" > " _7:bat[:oid\,:int] := sql.bind(_2\,\"sys\"\,\"blabla\"\,\"id\"\,0);" > _10 := algebra.selectNotNil(_7); > " _11:bat[:oid\,:oid] := sql.bind_dbat(_2\,\"sys\"\,\"blabla\"\,1);" > @@ -43,13 +42,11 @@ > _21 := calc.isnil(_20); > " _23 := calc.ifthenelse(_21\,0:wrd\,_20);" > " _24 := calc.!=(_19\,_23);" > -exit _37; > " sql.assert(_24\,\"UPDATE: UNIQUE constraint 'blabla.dada' violated\");" > end s1_1; > function user.s2_1{autoCommit=true}():void; > _2 := sql.mvc(); > -" sql.catalog(29\,\"sys\"\,139834808040824\,0);" > -barrier _37 := language.dataflow(); > +" sql.catalog(29\,\"sys\"\,140688030052568\,0);" > " _7:bat[:oid\,:int] := sql.bind(_2\,\"sys\"\,\"blabla\"\,\"id\"\,0);" > _10 := algebra.selectNotNil(_7); > " _11:bat[:oid\,:oid] := sql.bind_dbat(_2\,\"sys\"\,\"blabla\"\,1);" > @@ -63,15 +60,13 @@ > _21 := calc.isnil(_20); > " _23 := calc.ifthenelse(_21\,0:wrd\,_20);" > " _24 := calc.!=(_19\,_23);" > -exit _37; > " sql.assert(_24\,\"UPDATE: UNIQUE constraint 'blabla.dada' violated\");" > end s2_1; > #~EndVariableOutput~# > #~BeginVariableOutput~# > function user.s1_1{autoCommit=true}():void; > _2 := sql.mvc(); > -" sql.catalog(29\,\"sys\"\,139834807056504\,0);" > -barrier _37 := language.dataflow(); > +" sql.catalog(29\,\"sys\"\,140688029790296\,0);" > " _7:bat[:oid\,:int] := sql.bind(_2\,\"sys\"\,\"blabla\"\,\"id\"\,0);" > _10 := algebra.selectNotNil(_7); > " _11:bat[:oid\,:oid] := sql.bind_dbat(_2\,\"sys\"\,\"blabla\"\,1);" > @@ -85,7 +80,6 @@ > _21 := calc.isnil(_20); > " _23 := calc.ifthenelse(_21\,0:wrd\,_20);" > " _24 := calc.!=(_19\,_23);" > -exit _37; > " sql.assert(_24\,\"UPDATE: UNIQUE constraint 'blabla.dada' violated\");" > end s1_1; > #~EndVariableOutput~# > diff -r 75116ec8f9a7 -r e399a0ffae31 sql/src/test/BugTracker-2009/Tests/explain_gives_crash.SF-2741829.stable.out.Debian > --- a/sql/src/test/BugTracker-2009/Tests/explain_gives_crash.SF-2741829.stable.out.Debian Tue Jul 13 01:09:49 2010 +0200 > +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 > @@ -1,90 +0,0 @@ > -stdout of test 'explain_gives_crash.SF-2741829` in directory 'src/test/BugTracker-2009` itself: > - > - > -# 22:45:54 > > -# 22:45:54 > mserver5 "--config=/ufs/niels/scratch/rc/Linux-x86_64/etc/monetdb5.conf" --debug=10 --set gdk_nr_threads=0 --set "monet_mod_path=/ufs/niels/scratch/rc/Linux-x86_64/lib/MonetDB5:/ufs/niels/scratch/rc/Linux-x86_64/lib/MonetDB5/lib:/ufs/niels/scratch/rc/Linux-x86_64/lib/MonetDB5/bin" --set "gdk_dbfarm=/ufs/niels/scratch/rc/Linux-x86_64/var/MonetDB5/dbfarm" --set mapi_open=true --set xrpc_open=true --set mapi_port=35519 --set xrpc_port=48894 --set monet_prompt= --trace "--dbname=mTests_src_test_BugTracker-2009" --set mal_listing=0 "--dbinit= include sql;" ; echo ; echo Over.. > -# 22:45:54 > > - > -# MonetDB server v5.12.0, based on kernel v1.30.0 > -# Serving database 'mTests_src_test_BugTracker-2009', using 4 threads > -# Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked > -# Copyright (c) 1993-July 2008 CWI. > -# Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved > -# Visit http://monetdb.cwi.nl/ for further information > -# Listening for connection requests on mapi:monetdb://alf.ins.cwi.nl:35519/ > -# MonetDB/SQL module v2.30.0 loaded > - > -Ready. > -#function user.main():void; > _______________________________________________ > Checkin-list mailing list > Checkin-list(a)monetdb.org > http://mail.monetdb.org/mailman/listinfo/checkin-list > -- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4199 |

1 0

Re: [Monetdb-developers] about import *.csv
by Stefan de Konink 12 Jul '10

12 Jul '10

On Mon, 12 Jul 2010, kun ren wrote: > I am new to Monetdb, I want to ask how to excute the statement mclient -lsql >> if i want to import many *.csv,such as a.csv,b.csv,,,, but i only have >> *.csv file,and don't know the type of every column,in order to universal, i >> want to write a progrom, if i want to load and import a *.csv,i only call my >> program.do you think it feasible and what do i do? You must know the number of column horizontally. You can make tables of strings, obviously it will limit you in your options. Stefan

1 0

[Monetdb-developers] about import *.csv
by kun ren 12 Jul '10

12 Jul '10

Dear all, I want to import *.csv into MonetDB,what interface do i will use？ Best regards

2 1

Re: [Monetdb-developers] MonetDB: Jun2010 - ignore varying address in error message
by Fabian Groffen 10 Jul '10

10 Jul '10

On 10-07-2010 09:00:21 +0200, Stefan Manegold wrote: > Changeset: f5cb2db5f58f for MonetDB > URL: http://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f5cb2db5f58f > Modified Files: > testing/src/Mfilter.py.in > Branch: Jun2010 > Log Message: > > ignore varying address in error message > of test for bug 2547 > > + r'^(ERROR = !sql_stmt symbol$)(.*)($->token = CREATE_SCHEMA)\n', # 26: 3 Stefan, What's the point of this? The error message obviously should disappear, so it doesn't matter it differs every time. (unless someone (perhaps even me) accidentially approved this as the correct output)

2 3