- users-list - monetdb.org

MonetDB Cross Partition Joins
by Wolf Rödiger 17 Jan '13

17 Jan '13

Hello, According to its man page MonetDB is able to work as a cluster. However, I found no documentation on cross partition joins. Is there a way to partition a relation in MonetDB across servers and perform a cross partition join? Regards Wolf _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

JDBC error: 'protocol violation: unexpected line in data block: .'
by Luis Neves 11 Jan '13

11 Jan '13

Hello all, Is this a known bug? Is there any workaround? * Stack Trace java.sql.SQLException: 'protocol violation: unexpected line in data block: .' at nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.executeQuery(MonetConnection.java:2535) at nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.processQuery(MonetConnection.java:2284) at nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:508) at nl.cwi.monetdb.jdbc.MonetStatement.execute(MonetStatement.java:349) at nl.cwi.monetdb.jdbc.MonetPreparedStatement.execute(MonetPreparedStatement.java:247) at nl.cwi.monetdb.jdbc.MonetPreparedStatement.executeQuery(MonetPreparedStatement.java:265) * Table definition sql>\d sys.wa_blogs_audience CREATE TABLE "sys"."wa_blogs_audience" ( "tid" CHAR(32) NOT NULL, "ts" BIGINT, "ts_hour" BIGINT, "ts_day" BIGINT, "ts_month" BIGINT, "s_site_name" VARCHAR(32), "s_hostname" VARCHAR(256), "n_pageviews" DOUBLE, "n_visits" DOUBLE, "n_visitors" DOUBLE, "h_visitors_register" VARCHAR(1881), CONSTRAINT "wa_blogs_audience_tid_pkey" PRIMARY KEY ("tid") ); * SQL SELECT ts, hllagg(h_visitors_register) FROM wa_blogs_audience WHERE ts>=1355172393000 AND ts<=1357764393000 GROUP BY ts; * Output from mclient $ mclient -p9701 kpi_v1 -f raw -s "SELECT ts, hllagg(h_visitors_register) FROM wa_blogs_audience WHERE ts>=1355172393000 AND ts<=1357764393000 GROUP BY ts;" at: <https://dl.dropbox.com/u/279023/misc/mclient_output.txt> * JDBC debug log at: <https://dl.dropbox.com/u/279023/misc/monet_1357773164928.log> Thanks in advance! -- Luis Neves _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 6

Perf. benchmark for monetdb
by nitin sharma 10 Jan '13

10 Jan '13

Hi there, I am evaluating monetdb and was wondering if there are performance bench mark numbers like the one published in C-store paper: http://people.csail.mit.edu/tdanford/6830papers/stonebraker-cstore.pdf I am looking for perf. number for 100 millions rows in fact table (500 GB) joined with couple of dimension tables. Does moentdb supports horizontal partitioning of data and joins across machine (distributed joins) ? Thanks!Nitin _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 3

Weird concurrency issue with JDBC getConnection
by Percy Wegmann 10 Jan '13

10 Jan '13

Dear Monet Team, I've been using the JDBC driver and have recently noticed that under load, calls to DriverManager.getConnection() will sometimes appear to hang. I was able to resolve this problem by serializing access to getConnection() using a synchronized block. I haven't had a chance to dig through the JDBC driver code to see what would account for this, but I figured I'd make you aware just in case someone else runs into this. Cheers, -- Percy Wegmann +1 512 637 8500 ext 148 _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 4

What is normally done to recover from 'crash'ed databases.
by Brandon Jackson 08 Jan '13

08 Jan '13

Hello, I have a toy database on my laptop that I've been using while testing development of a Pentaho Data Integration plugin for bulk loading. One day I shutdown my machine without stopping monetdb. When I turned on the computer and started monetdbd on the database everything seems to work fine. 'monetdb status' outputs the following: brandon-jacksons-macbook-pro:bin bjackson$ ./monetdb status name state uptime health demo crashed 0%, 0s crash 2013-01-05 00:29:20 brandon-jacksons-macbook-pro:bin bjackson$ ./monetdb start demo starting database 'demo'... done brandon-jacksons-macbook-pro:bin bjackson$ ./monetdb status name state uptime health demo running 5s 50%, 0s crash 2013-01-05 00:29:20 brandon-jacksons-macbook-pro:bin bjackson$ I cannot really tell if there is any real damage. What do people normally do to check the integrity of their databases and repair damage if it exists? Does a set of actions restore the health of the database? If I missed some documentation please feel free to refer me to some links. Thanks for the information. Brandon _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 3

Fwd: Re: c3p0 ConnectionTester socket read stuck after SQLException
by Hannes Mühleisen 08 Jan '13

08 Jan '13

Forwarding this to the list, please keep the discussion there... -------- Original Message -------- Subject: Re: c3p0 ConnectionTester socket read stuck after SQLException Date: Tue, 8 Jan 2013 08:17:35 -0800 (PST) From: Tapomay Dey <tapomay(a)yahoo.com> Reply-To: Tapomay Dey <tapomay(a)yahoo.com> To: Hannes.Muehleisen(a)cwi.nl <Hannes.Muehleisen(a)cwi.nl> My operations are as follows: 1. Create connections with auto-commit=false 2. Read queries from an external module. 3. Execute queries on the connection acquired in step 1 4. Update external module status as per result of queries. 5. If all is well, commit the connection. 6. If commit fails(optimistic locking is the culprit here), revert changes to the external module. All of these steps are implemented in a command chain pattern code. Thus I need to be able to pass around the connection. Thanks and Regards, Tapomay. ------------------------------------------------------------------------ *From:* Hannes Mühleisen <Hannes.Muehleisen(a)cwi.nl> *To:* Communication channel for MonetDB users <users-list(a)monetdb.org> *Sent:* Thursday, January 3, 2013 4:19 PM *Subject:* Re: c3p0 ConnectionTester socket read stuck after SQLException Hello Tapomay, after looking at your code, I was wondering why you chose the double management of connections in your Main/JdbcMonetdbTestClient classes. C3P0 provides a way to define "connection customizers" (com.mchange.v2.c3p0.ComboPooledDataSource.setConnectionCustomizerClassName(String)), which you can use to disable autocommit on new connections. This should simplify your example considerably. Nevertheless, I will try to provoke the exceptions you have mentioned and see how the JDBC driver handles them together with C3P0. Best, Hannes On 20/12/12 15:41, Tapomay Dey wrote: > As the source code has many unrelated dependencies I tried to extract > the relevant code. > Please find attached an eclipse project for the same. > However I haven't been able to reproduce the issue in this test project. > It should give you a fair idea of the sequence of calls made. Plz note > that a single insert query used in the live project is much much larger > (10K approx.) than the one in the test. > I reconfirmed that the issue is still there in the larger project. > > PS: I had sent this code long back and it got moderated just now(due to > some 40KB limit). Thus I have removed the dependencies > monetdb-jdbc-2.6.jar and c3p0-0.9.1.2.jar from lib. Plz add them to lib > folder and everything should work(after u set the correct DB names in > the code).(Anyways this code doesn't reproduce the issue I am facing so > I guess just a manual overview should suffice) > > Regards, > Tapomay. > > ------------------------------------------------------------------------ > *From:* Hannes Mühleisen <Hannes.Muehleisen(a)cwi.nl <mailto:Hannes.Muehleisen@cwi.nl>> > *To:* Communication channel for MonetDB users <users-list(a)monetdb.org <mailto:users-list@monetdb.org>> > *Sent:* Thursday, December 20, 2012 2:17 PM > *Subject:* Re: c3p0 ConnectionTester socket read stuck after SQLException > > Hello Tapomay, > > I will have a look later today, could you please also provide the source > code that you have used to provoke the issue? > > Thanks, > > Hannes > > On 20/12/12 08:26, Tapomay Dey wrote: > > Please find the thread dump below. > > Running MonetDB Database Server v1.6 (Oct2012-SP1). Compiled > > from MonetDB-11.13.5 src distribution. > > C3P0 version: 0.9.1.2. Also tried with 0.9.2. > > Occurs only after SQLException sometimes: INSERT INTO xyz : table xyz > > doesn't exist. > > Otherwise it works great. > > Also tried setting c3p0's preferredQuery for ConnectionTester to "select > > 1;". Problem persists. > > > > Name: pool-15-thread-2 > > State: RUNNABLE > > Total blocked: 0 Total waited: 1 > > > > Stack trace: > > java.net.SocketInputStream.socketRead0(Native Method) > > java.net.SocketInputStream.read(SocketInputStream.java:150) > > java.net.SocketInputStream.read(SocketInputStream.java:121) > > java.io.BufferedInputStream.fill(BufferedInputStream.java:235) > > java.io.BufferedInputStream.read1(BufferedInputStream.java:275) > > java.io.BufferedInputStream.read(BufferedInputStream.java:334) > > - locked java.io.BufferedInputStream@5cec5796 > > > nl.cwi.monetdb.mcl.net.MapiSocket$BlockInputStream._read(MapiSocket.java:846) > > > nl.cwi.monetdb.mcl.net.MapiSocket$BlockInputStream.readBlock(MapiSocket.java:895) > > > nl.cwi.monetdb.mcl.net.MapiSocket$BlockInputStream.read(MapiSocket.java:965) > > sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283) > > sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325) > > sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177) > > - locked java.io.InputStreamReader@206a6883 > > java.io.InputStreamReader.read(InputStreamReader.java:184) > > java.io.BufferedReader.fill(BufferedReader.java:154) > > java.io.BufferedReader.readLine(BufferedReader.java:317) > > - locked java.io.InputStreamReader@206a6883 > > java.io.BufferedReader.readLine(BufferedReader.java:382) > > > nl.cwi.monetdb.mcl.io.BufferedMCLReader.readLine(BufferedMCLReader.java:119) > > > nl.cwi.monetdb.mcl.io.BufferedMCLReader.waitForPrompt(BufferedMCLReader.java:196) > > - locked nl.cwi.monetdb.mcl.io.BufferedMCLReader@29f38115 > > > nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.executeQuery(MonetConnection.java:2296) > > - locked nl.cwi.monetdb.mcl.net.MapiSocket@319f9f37 > > > nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.processQuery(MonetConnection.java:2274) > > > nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:508) > > nl.cwi.monetdb.jdbc.MonetStatement.execute(MonetStatement.java:349) > > nl.cwi.monetdb.jdbc.MonetStatement.executeQuery(MonetStatement.java:525) > > > com.mchange.v2.c3p0.impl.DefaultConnectionTester.activeCheckConnection(DefaultConnectionTester.java:73) > > > com.mchange.v2.c3p0.impl.DefaultConnectionTester.statusOnException(DefaultConnectionTester.java:143) > > > com.mchange.v2.c3p0.AbstractConnectionTester.statusOnException(AbstractConnectionTester.java:82) > > > com.mchange.v2.c3p0.impl.NewPooledConnection.handleThrowable(NewPooledConnection.java:437) > > - locked com.mchange.v2.c3p0.impl.NewPooledConnection@3340302c > > > com.mchange.v2.c3p0.impl.NewProxyStatement.executeUpdate(NewProxyStatement.java:78) > > > com.sokrati.moneta.mclient.JdbcMonetdbClient.executeUpdate(JdbcMonetdbClient.java:154) > > > com.sokrati.moneta.multiplexer.MonetdbClientCallable.call(MonetdbClientCallable.java:46) > > > com.sokrati.moneta.multiplexer.MonetdbClientCallable.call(MonetdbClientCallable.java:1) > > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > > java.util.concurrent.FutureTask.run(FutureTask.java:166) > > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > > java.lang.Thread.run(Thread.java:722) > > > > Regards, > > Tapomay. > > > > > > _______________________________________________ > > users-list mailing list > > users-list(a)monetdb.org <mailto:users-list@monetdb.org> <mailto:users-list@monetdb.org <mailto:users-list@monetdb.org>> > > http://mail.monetdb.org/mailman/listinfo/users-list > > > > _______________________________________________ > users-list mailing list > users-list(a)monetdb.org <mailto:users-list@monetdb.org> <mailto:users-list@monetdb.org <mailto:users-list@monetdb.org>> > http://mail.monetdb.org/mailman/listinfo/users-list > > > > > _______________________________________________ > users-list mailing list > users-list(a)monetdb.org <mailto:users-list@monetdb.org> > http://mail.monetdb.org/mailman/listinfo/users-list > _______________________________________________ users-list mailing list users-list(a)monetdb.org <mailto:users-list@monetdb.org> http://mail.monetdb.org/mailman/listinfo/users-list _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 0

the dbname option disappeared
by Stefan de Konink 04 Jan '13

04 Jan '13

I have justed checked out the Feb2013 release and noticed that the dbname option is gone, is there a substitute? Stefan _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

5 8

c3p0 ConnectionTester socket read stuck after SQLException
by Tapomay Dey 03 Jan '13

03 Jan '13

Please find the thread dump below. Running MonetDB Database Server v1.6 (Oct2012-SP1). Compiled from MonetDB-11.13.5 src distribution. C3P0 version: 0.9.1.2. Also tried with 0.9.2. Occurs only after SQLException sometimes: INSERT INTO xyz : table xyz doesn't exist. Otherwise it works great. Also tried setting c3p0's preferredQuery for ConnectionTester to "select 1;". Problem persists. Name: pool-15-thread-2 State: RUNNABLE Total blocked: 0 Total waited: 1 Stack trace: java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:150) java.net.SocketInputStream.read(SocketInputStream.java:121) java.io.BufferedInputStream.fill(BufferedInputStream.java:235) java.io.BufferedInputStream.read1(BufferedInputStream.java:275) java.io.BufferedInputStream.read(BufferedInputStream.java:334) - locked java.io.BufferedInputStream@5cec5796 nl.cwi.monetdb.mcl.net.MapiSocket$BlockInputStream._read(MapiSocket.java:846) nl.cwi.monetdb.mcl.net.MapiSocket$BlockInputStream.readBlock(MapiSocket.java:895) nl.cwi.monetdb.mcl.net.MapiSocket$BlockInputStream.read(MapiSocket.java:965) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177) - locked java.io.InputStreamReader@206a6883 java.io.InputStreamReader.read(InputStreamReader.java:184) java.io.BufferedReader.fill(BufferedReader.java:154) java.io.BufferedReader.readLine(BufferedReader.java:317) - locked java.io.InputStreamReader@206a6883 java.io.BufferedReader.readLine(BufferedReader.java:382) nl.cwi.monetdb.mcl.io.BufferedMCLReader.readLine(BufferedMCLReader.java:119) nl.cwi.monetdb.mcl.io.BufferedMCLReader.waitForPrompt(BufferedMCLReader.java:196) - locked nl.cwi.monetdb.mcl.io.BufferedMCLReader@29f38115 nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.executeQuery(MonetConnection.java:2296) - locked nl.cwi.monetdb.mcl.net.MapiSocket@319f9f37 nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.processQuery(MonetConnection.java:2274) nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:508) nl.cwi.monetdb.jdbc.MonetStatement.execute(MonetStatement.java:349) nl.cwi.monetdb.jdbc.MonetStatement.executeQuery(MonetStatement.java:525) com.mchange.v2.c3p0.impl.DefaultConnectionTester.activeCheckConnection(DefaultConnectionTester.java:73) com.mchange.v2.c3p0.impl.DefaultConnectionTester.statusOnException(DefaultConnectionTester.java:143) com.mchange.v2.c3p0.AbstractConnectionTester.statusOnException(AbstractConnectionTester.java:82) com.mchange.v2.c3p0.impl.NewPooledConnection.handleThrowable(NewPooledConnection.java:437) - locked com.mchange.v2.c3p0.impl.NewPooledConnection@3340302c com.mchange.v2.c3p0.impl.NewProxyStatement.executeUpdate(NewProxyStatement.java:78) com.sokrati.moneta.mclient.JdbcMonetdbClient.executeUpdate(JdbcMonetdbClient.java:154) com.sokrati.moneta.multiplexer.MonetdbClientCallable.call(MonetdbClientCallable.java:46) com.sokrati.moneta.multiplexer.MonetdbClientCallable.call(MonetdbClientCallable.java:1) java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) java.util.concurrent.FutureTask.run(FutureTask.java:166) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) java.lang.Thread.run(Thread.java:722) Regards, Tapomay. _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 6

Re: users-list Digest, Vol 5, Issue 1
by swapnil joshi 03 Jan '13

03 Jan '13

Hi nitin, # Serving database 'demo', using 12 threads # Compiled for x86_64-pc-winnt/64bit with 64bit OIDs dynamically linked # Found 23.998 GiB available main-memory. # Copyright (c) 1993-July 2008 CWI. # Copyright (c) August 2008-2012 MonetDB B.V., all rights reserved # Visit http://www.monetdb.org/ for further information !IOException:mal_mapi.listen: operation failed: bind to stream socket port 50000 failed: solution 1 = It's an just port conflict error the port had assign to monetdb is already used by any other application please change the port of monetdb or find your another application which using same port and sopt it's service, then it will work. Solution 2 = If you are an student and if you are using your own system / personal computer then just shut down the system and restart it and first start monetdb server. If any only if you are studying monetdb on your personal computer . (solution 2 is foolish solution :) ) On Thu, Jan 3, 2013 at 4:30 PM, <users-list-request(a)monetdb.org> wrote: > nitin -- Regards, Swapnil K. Joshi _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 0

Error while starting monetdb on windows server 2008 R2
by nitin sharma 03 Jan '13

03 Jan '13

Hi there, I am getting following error while running monetdb server >>>># MonetDB 5 server v11.13.7 "Oct2012-SP2" # Serving database 'demo', using 12 threads # Compiled for x86_64-pc-winnt/64bit with 64bit OIDs dynamically linked # Found 23.998 GiB available main-memory. # Copyright (c) 1993-July 2008 CWI. # Copyright (c) August 2008-2012 MonetDB B.V., all rights reserved # Visit http://www.monetdb.org/ for further information !IOException:mal_mapi.listen:operation failed: bind to stream socket port 50000 failed: No error > Any pointer what could be the issue? thx,Nitin _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

failed to fork mserver: database 'lwg' started up, but failed to open up a communication channel
by Przemyslaw Wroblewski 28 Dec '12

28 Dec '12

hello, I'm trying to evaluate monetdb but I've failed at the beginning of the tutorial: http://www.monetdb.org/Documentation/monetdbd When I'm trying ot start up database I've got following: $ monetdb start lwg starting database 'lwg'... FAILED start: starting 'lwg' failed: database 'lwg' started up, but failed to open up a communication channel and in merovingian.log: 2012-12-27 16:43:26 MSG merovingian[29552]: startup of database under maintenance 'lwg' forced 2012-12-27 16:43:26 MSG merovingian[29552]: starting database 'lwg', up min/avg/max: 1s/1s/1s, crash average: 0.00 0.00 0.00 (1-1=0) 2012-12-27 16:43:27 MSG merovingian[29552]: sending process 9489 (database 'lwg') the TERM signal 2012-12-27 16:43:27 MSG lwg[9489]: arguments: /usr/bin/mserver5 --set gdk_dbfarm=/var/lib/monetdb --dbname=lwg --set merovingian_uri=mapi:monetdb://przemtest1:50000/lwg --set mapi_open=false --set mapi_port=0 --set mapi_usock=/var/lib/monetdb/lwg/.mapi.sock --set monet_vault_key=/var/lib/monetdb/lwg/.vaultkey --set gdk_nr_threads=8 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes 2012-12-27 16:43:27 MSG lwg[9489]: # MonetDB 5 server v11.13.7 "Oct2012-SP2" 2012-12-27 16:43:27 MSG lwg[9489]: # Serving database 'lwg', using 8 threads 2012-12-27 16:43:27 MSG lwg[9489]: # Compiled for x86_64-pc-linux-gnu/64bit with 64bit OIDs dynamically linked 2012-12-27 16:43:27 MSG lwg[9489]: # Found 23.591 GiB available main-memory. 2012-12-27 16:43:27 MSG lwg[9489]: # Copyright (c) 1993-July 2008 CWI. 2012-12-27 16:43:27 MSG lwg[9489]: # Copyright (c) August 2008-2012 MonetDB B.V., all rights reserved 2012-12-27 16:43:27 MSG lwg[9489]: # Visit http://www.monetdb.org/ for further information 2012-12-27 16:43:27 MSG lwg[9489]: !TypeException:batcalc.rank_grp[3]:object code for command sql.rank_grp missing 2012-12-27 16:43:27 MSG lwg[9489]: !TypeException:batcalc.rank_grp[1]:object code for command sql.rank missing 2012-12-27 16:43:27 MSG lwg[9489]: !TypeException:batcalc.dense_rank_grp[3]:object code for command sql.dense_rank_grp missing 2012-12-27 16:43:27 MSG lwg[9489]: !TypeException:batcalc.dense_rank_grp[1]:object code for command sql.dense_rank missing 2012-12-27 16:43:27 MSG lwg[9489]: !TypeException:aggr.median[7]:object code for command sql.middle missing 2012-12-27 16:43:27 MSG lwg[9489]: #WARNING: LoaderException:loadLibrary:Loading error could not locate library lsst (from within file 'lsst') 2012-12-27 16:43:27 MSG lwg[9489]: !TypeException:user.main[1240]:object code for command sql.prelude missing 2012-12-27 16:43:27 MSG lwg[9489]: !TypeException:user.main[1240]:'sql.prelude' undefined in: _1240:void := sql.prelude() 2012-12-27 16:43:27 MSG merovingian[29552]: database 'lwg' (9489) has exited with exit status 0 2012-12-27 16:43:27 MSG merovingian[29552]: database 'lwg' has shut down 2012-12-27 16:43:27 ERR control[29552]: (local): failed to fork mserver: database 'lwg' started up, but failed to open up a communication channel I'm on 64bit debian 6.0.4 in vserver container. It looks like exactly as http://bugs.monetdb.org/show_bug.cgi?id=3134 but I've latest version which should this bug already fixed. best regards Przemek _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

Fwd: Enhance Performance
by Arjun Harish 27 Dec '12

27 Dec '12

I am bench-marking monetDB against some other databases. I have a system with intel i-7 processor, 32GB Ram and 2 TB Harddisk on a Ubuntu 12.10 system. I have a data work load of 700 GB in monetdb now. How can i enhance the performance and speed up the querying process. Any Suggestions would we welcome and please reply in detail. I am a newbie to Monetdb. Arjun Data Scientist -- Arjun Harish Nadh Data Scientist Flutura Business Solutions Pvt. Ltd. +919972736428 arjun.harish(a)fluturasolutions.com _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

MonetDB Update: some problems while updating
by Miguel Ping 26 Dec '12

26 Dec '12

Hi all, We tried to update monetdb to the latest version, but encountered some problems. The prev version is working just fine. We're using Debian, and installed from the debs. See the log below. lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 6.0.4 (squeeze) Release: 6.0.4 Codename: squeeze ... 2012-12-26 11:43:42 MSG kpi_v1[13255]: # MonetDB 5 server v11.13.7 "Oct2012-SP2" 2012-12-26 11:43:42 MSG kpi_v1[13255]: # Serving database 'kpi_v1', using 24 threads 2012-12-26 11:43:42 MSG kpi_v1[13255]: # Compiled for x86_64-pc-linux-gnu/64bit with 64bit OIDs dynamically linked 2012-12-26 11:43:42 MSG kpi_v1[13255]: # Found 23.587 GiB available main-memory. 2012-12-26 11:43:42 MSG kpi_v1[13255]: # Copyright (c) 1993-July 2008 CWI. 2012-12-26 11:43:42 MSG kpi_v1[13255]: # Copyright (c) August 2008-2012 MonetDB B.V., all rights reserved 2012-12-26 11:43:42 MSG kpi_v1[13255]: # Visithttp://www.monetdb.org/ for further information 2012-12-26 11:43:42 MSG kpi_v1[13255]: !TypeException:batcalc.rank_grp[3]:object code for command sql.rank_grp missing 2012-12-26 11:43:42 MSG kpi_v1[13255]: !TypeException:batcalc.rank_grp[1]:object code for command sql.rank missing 2012-12-26 11:43:42 MSG kpi_v1[13255]: !TypeException:batcalc.dense_rank_grp[3]:object code for command sql.dense_rank_grp missing 2012-12-26 11:43:42 MSG kpi_v1[13255]: !TypeException:batcalc.dense_rank_grp[1]:object code for command sql.dense_rank missing 2012-12-26 11:43:42 MSG kpi_v1[13255]: !TypeException:aggr.median[7]:object code for command sql.middle missing 2012-12-26 11:43:42 MSG kpi_v1[13255]: #WARNING: LoaderException:loadLibrary:Loading error could not locate library lsst (from within file 'lsst') 2012-12-26 11:43:42 MSG kpi_v1[13255]: !TypeException:user.main[1240]:object code for command sql.prelude missing 2012-12-26 11:43:42 MSG kpi_v1[13255]: !TypeException:user.main[1240]:'sql.prelude' undefined in: _1240:void := sql.prelude() 2012-12-26 11:43:42 MSG merovingian[13238]: database 'kpi_v1' (13255) has exited with exit status 0 2012-12-26 11:43:42 MSG merovingian[13238]: database 'kpi_v1' has shut down 2012-12-26 11:43:42 ERR control[13238]: (local): failed to fork mserver: database 'kpi_v1' started up, but failed to open up a communication channel Thanks _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

UDF compilation
by Miguel Ping 21 Dec '12

21 Dec '12

What are the steps required to include additional .c and .h files in compiling user-defined functions? It was a long time since I used autotools and such; it seems to me that I would need to change the monetdb configuration files in order to regenerate the Makefile.* files within the UDF dir. My problem is that I require alot of code for my UDF, and right now I'm copy/paste'ing code to udf.c and udf.h; it would be easier to include additional .h and .c files for UDF compilation. Thanks _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 4

Announcement: New Oct2012-SP2 Bugfix release of MonetDB suite
by Sjoerd Mullender 21 Dec '12

21 Dec '12

The MonetDB team at CWI/MonetDB BV is pleased to announce the Oct2012-SP2 bugfix release of the MonetDB suite of programs. More information about MonetDB can be found on our website at <http://www.monetdb.org/>. For details on this release, please see the release notes at <http://www.monetdb.org/Downloads/ReleaseNotes>. As usual, the download location is <http://dev.monetdb.org/downloads/>. Oct 2012-SP2 bugfix release SQL * Fixed crash when performing an INSERT on a table with string-like column defaulting to NULL and omitting that column from VALUES, bug #3168 Java Module * Implemented type map support of Connection to allow custom mapping of UDTs to Java classes. By default the INET and URL UDTs are now mapped to nl.cwi.monetdb.jdbc.types.{INET,URL}. Most notably, ResultSet.getObject() and PreparedStatement.setObject() deal with the type map. * Fixed a problem in PreparedStatement where the prepared statement's ResultSetMetaData (on its columns to be produced) incorrectly threw exceptions about non existing columns. Bug #3192 Bug Fixes * 2291: small doubles end up as NULL after arithmetic * 2579: SQL: incorrect cast from double to int * 2659: tuples INTERSECT vs count (... INTERSECT ...) differs * 2805: row_number doesn't work in complex query * 2886: warning: Catalog parameter '' ignored * 2977: timestamp minus date results in program error * 2978: now() + 1 results in illegal argument * 2999: Up-cast from SQL drops order information? * 3048: algebra.join undefined when using multiple arithmetic operations in SQL where-clause * 3124: insert into table with two foreign keys crashes mserver5 * 3136: Memleak (in querycache?) while querying * 3143: Type resolution error in SQL procedural code * 3163: mserver5 crashes with large number of concurrent clients * 3168: crash when insert varchar/char/clob with default NULL * 3169: php driver uses call-time pass-by-reference * 3173: SQL queries with limit and offset clauses are unable to use bind parameters for either * 3181: Join query returns zero results when there is an index on the tables * 3185: inconsistency between documentation and implementation of command line options * 3186: case evaluted to early * 3188: Storage of client history * 3189: Overflow in calculation * 3190: When subtracting two columns of type "timestamp", no results are returned * 3191: rel_optimizer.c:5596: _rel_optimizer: Assertion `0' failed. * 3192: "No such column with index" error if CASE in SELECT clause * 3199: Inconspicuous sequence of prepare, execute, commit and close produces error * 3205: Inet datatype handling inconsistent between int, cast( as inet) and string _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 0

OLTP Benchmark on Monetdb
by Hassan, Ahmad 19 Dec '12

19 Dec '12

Hi Team, I am trying to run TPC-C benchmark provided by opensource oltpbenchmark (http://oltpbenchmark.com) on MonetDB. But I am getting JDBC Exception while loading the data set: java.sql.BatchUpdateException: Error(s) occurred while executing the batch, see next SQLExceptions for details at nl.cwi.monetdb.jdbc.MonetStatement.executeBatch(MonetStatement.java:209) Exception in thread "main" java.lang.ArithmeticException: / by zero at com.oltpbenchmark.benchmarks.tpcc.TPCCLoader.load(TPCCLoader.java:1857) Please can you let me know any TPC-C benchmark implementation that is compatible with monetdb? Thanks. Kind Regards, Ahmad _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 4

MonetDB compiling with CLANG/LLVM
by Hassan, Ahmad 18 Dec '12

18 Dec '12

Hi, I want to ask if someone has tried compiling MonetDB with Clang/LLVM compiler? I intend to compile MonetDB with LLVM for analysing the query execution at runtime. Does someone know the changes in the build process required for building Monetdb with clang/llvm? Thanks. Cheers, Ahmad _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 4

Unable to execute prepared statements with a large number of parameters (say over 140 or so)
by Percy Wegmann 14 Dec '12

14 Dec '12

I couldn't find any existing bugs that cover this, so I logged a new one: http://bugs.monetdb.org/show_bug.cgi?id=3208 This is kind of a show-stopper for me right now, so I'm hoping that someone might have some idea where to start looking for a solution. I'm debugging sql_scenario.c right now, but it'll take me some time to get familiar with the code. Cheers, -- Percy Wegmann +1 512 637 8500 ext 148 _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 0

Still searching to find the Octopus :-)
by Masood Mortazavi 13 Dec '12

13 Dec '12

I'm still searching for user documentation that would explain MonetDB/octopus usage/feature. Does any exist? Thanks, Masood P.S. My earlier e-mails regarding the octopus documentation was somewhat rushed, it seems. The documentation in the man pages are actually for remtoe access and funnel-multiplex features, which seem entirely different. _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 4

Does anybody know the endian ness (little, big) of BAT file?
by swapnil joshi 10 Dec '12

10 Dec '12

Hi, Does anybody know the endian ness (little, big) of BAT file? -- Regards, Swapnil K. Joshi _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

Adding group_concat support
by Tapomay Dey 07 Dec '12

07 Dec '12

Just confirming. Can we yet define functions without having to recompile. Planning to try adding group_concat support. Regards, Tapomay. _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 2

Re: Failed to load 128GB CSV file using Oct2012
by Stefan Manegold 05 Dec '12

05 Dec '12

Jennie, just to be sure: are you sure there is sufficient free disk space on your machine, say, twice the expected database size before starting the load? How large is your database (and sql_logs) just after the failure while the server is still running? How much disk space is still free at that time? Stefan Ying Zhang <Y.Zhang(a)cwi.nl> wrote: Hai all, I try to load a CVS file of ~128GB in the ssdb branch (based on Oct2012), but after quite sometime, it failed with: #GDKrealloc(19598973840) fails, try to free up space [memory in use=22695528216,virtual memory in use=138875848472] #GDKrealloc(19598973840) result [mem=22695528216,vm=138875848472] In the last Sep., I was able to execute the same query with the same data. But now it takes much longer and ends in a crash. For INS1-ers, the command to start the server: /export/scratch2/zhang/monet-install/ssdb/debug/bin/mserver5 --set gdk_dbfarm=/export/scratch2/zhang/dbfarm --dbname=ssdb --set mapi_usock=/export/scratch2/zhang/dbfarm/ssdb/.mapi.sock --set monet_vault_key=/export/scratch2/zhang/dbfarm/ssdb/.vaultkey --set gdk_nr_threads=8 --set max_clients=64 --set sql_optimizer=default_pipe --set mapi_port=60000 The command to start the query: cd /ufs/zhang/papers/ssdb/monetdb ./run.sh loadimg small output Does anyone have an idea? If anymore information is needed, please let me know. I'm re-running the query to get a GDB stack trace. Thanks! Jennie _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 2

Query takes too much time
by Ivan Videla 05 Dec '12

05 Dec '12

Hi All, I have a table with 268 millions of records from supermarket transactions tran_id, prod_id, quantity, price, cost and i want to make a calculation like sum(quantity*(price-cost)). But this query takes too much time. I want to know if i can improve the results using an index. Or monetdb itself use an index on-the-fly. If not i would like to know how can i make an index to improve the execution time. Regards, Ivan _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 12

Failed to load 128GB CSV file using Oct2012
by Ying Zhang 05 Dec '12

05 Dec '12

Hai all, I try to load a CVS file of ~128GB in the ssdb branch (based on Oct2012), but after quite sometime, it failed with: #GDKrealloc(19598973840) fails, try to free up space [memory in use=22695528216,virtual memory in use=138875848472] #GDKrealloc(19598973840) result [mem=22695528216,vm=138875848472] In the last Sep., I was able to execute the same query with the same data. But now it takes much longer and ends in a crash. For INS1-ers, the command to start the server: /export/scratch2/zhang/monet-install/ssdb/debug/bin/mserver5 --set gdk_dbfarm=/export/scratch2/zhang/dbfarm --dbname=ssdb --set mapi_usock=/export/scratch2/zhang/dbfarm/ssdb/.mapi.sock --set monet_vault_key=/export/scratch2/zhang/dbfarm/ssdb/.vaultkey --set gdk_nr_threads=8 --set max_clients=64 --set sql_optimizer=default_pipe --set mapi_port=60000 The command to start the query: cd /ufs/zhang/papers/ssdb/monetdb ./run.sh loadimg small output Does anyone have an idea? If anymore information is needed, please let me know. I'm re-running the query to get a GDB stack trace. Thanks! Jennie _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 0

INET query/type conversion issues
by Percy Wegmann 04 Dec '12

04 Dec '12

Hi MonetDB Team, I encountered a strange problem related to querying against an INET column. To reproduce: percy@percy-sandbox:~$ uname -a Linux percy-sandbox 3.2.0-33-generic #52-*Ubuntu* SMP Thu Oct 18 16:29:15 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux percy@percy-sandbox:~$ mclient -u monetdb -d click password: Welcome to mclient, the MonetDB/SQL interactive terminal (Oct2012) Database: *MonetDB v11.13.3 (Oct2012)*, 'mapi:monetdb://percy-sandbox:50000/click' Type \q to quit, \? for a list of available commands auto commit mode: on sql>create table test_table(col inet); operation successful (27.394ms) sql>insert into test_table values(*'127.0.0.1'*); 1 affected row (20.370ms) sql>insert into test_table values(*inet '127.0.0.1'*); 1 affected row (19.654ms) sql>insert into test_table values(*cast('127.0.0.1' as inet)*); 1 affected row (25.038ms) sql>select count(*) from test_table where col = '127.0.0.1'; +------+ | L1 | +======+ | *3* | +------+ 1 tuple (1.547ms) sql>select count(*) from test_table where col = inet '127.0.0.1'; +------+ | L1 | +======+ | *0* | +------+ 1 tuple (0.946ms) sql>select count(*) from test_table where col = cast('127.0.0.1' as inet); +------+ | L1 | +======+ | *2* | +------+ 1 tuple (0.982ms) sql>select count(*) from test_table where col = inet '127.0.0.1'; +------+ | L1 | +======+ | *2* | +------+ 1 tuple (0.937ms) sql>select count(*) from test_table where col = inet '127.0.0.1'; +------+ | L1 | +======+ | *0* | +------+ 1 tuple (0.801ms) Expected Result: All queries return a count of 3 Actual Result: Queries return different counts depending on how INET value was bound to query. Particularly interesting is that the output when using the inet '127.0.0.1' syntax is non-deterministic. Does this ring any bells? Should I log it? Cheers, -- Percy Wegmann +1 512 637 8500 ext 148 _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 1

Manually Loading all SQL Script
by swapnil joshi 04 Dec '12

04 Dec '12

Hi , My SQL Script is loaded only one's, When i am creating new database using following command I have copy and paste my terminal command swapnil@swapnil-lp:~$ sudo monetdb create test5 [sudo] password for swapnil: Sorry, try again. [sudo] password for swapnil: created database in maintenance mode: test5 swapnil@swapnil-lp:~$ sudo monetdb release test5 taken database out of maintenance mode: test5 swapnil@swapnil-lp:~$ sudo monetdb start test5 starting database 'test5'... done swapnil@swapnil-lp:~$ mclient test5 Welcome to mclient, the MonetDB/SQL interactive terminal (Jul2012-SP1) Database: MonetDB v11.11.7 (Jul2012-SP1), 'mapi:monetdb://swapnil-lp:50000/test5' Type \q to quit, \? for a list of available commands auto commit mode: on sql> After that if i am checking merovingian.log (Monetdb log file) 2012-12-04 17:57:20 MSG test2[11694]: # SQL catalog created, loading sql scripts once 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 09_like.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 10_math.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 11_times.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 12_url.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 13_date.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 14_inet.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 15_history.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 16_tracelog.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 17_compress.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 18_dictionary.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 19_cluster.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 20_vacuum.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 21_dependency_functions.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 22_clients.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 23_skyserver.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 24_zorder.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 25_debug.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 40_geom.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 80_udf.sql 2012-12-04 17:57:20 MSG test2[11694]: # loading sql script: 99_system.sql How will i manually Lode this script because if i have change in any *.sql file each time I need to create new database How will i avoid this manual work? Please help me!!!! :) -- Regards, Swapnil K. Joshi _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

Can Monetdb drop Calculation of dropped column?
by swapnil joshi 04 Dec '12

04 Dec '12

Hi I have executed following SQL Statement : *sql>select product_id, sum(unit_sales),avg(unit_sales), max(unit_sales), min(unit_sales),sum(store_sales),avg(store_sales), max(store_sales), min(store_sales), sum(store_cost),avg(store_cost), max(store_cost), min(store_cost) from sales_fact_1997 group by product_id; It Gives following result: (In my table very large data there for i have given starting and ending rows of result set) +-----------+--------------+--------------------------+--------------+--------------+--------------+--------------------------+--------------+--------------+ | product_i | L1 | L2 | L3 | L4 | L5 | L6 | L7 | L10 |> : d : : : : : : : : :> +===========+==============+==========================+==============+==============+==============+==========================+==============+==============+ | 337 | 333644.7415 | 3.4849771407382648 | 6.9998 | 0.0001 | 1145678.6601 | 11.966812134157813 | 23.9986 | 0.0005 | | 1512 | 336475.1207 | 3.4816655356884185 | 6.9999 | 0.0001 | 1158967.1049 | 11.992375001552128 | 23.9995 | 0.0011 | | 963 | 333727.8589 | 3.4994427668141643 | 6.9997 | 0.0003 | 1139917.6212 | 11.953082033429096 | 23.9998 | 0.0008 | | 181 | 334323.6059 | 3.4942578847801946 | 6.9999 | 0.0003 | 1145948.0178 | 11.977131815046297 | 23.9980 | 0.0002 | | 1383 | 334298.1724 | 3.4923130291254028 | 6.9999 | 0.0002 | 1145319.9025 | 11.964814492708198 | 23.9992 | 0.0015 | | 1116 | 337661.6147 | 3.4923165958195015 | 6.9999 | 0.0003 | 1161142.4618 | 12.009292477789144 | 23.9996 | 0.0003 | | 488 | 336083.8006 | 3.5025147266948111 | 7.0000 | 0.0008 | 1149952.2337 | 11.984286735448883 | 23.9992 | 0.0004 | | 121 | 336465.6749 | 3.486221285215461 | 6.9999 | 0.0001 | 1154632.2251 | 11.963489116492081 | 23.9998 | 0.0001 | | 1338 | 337204.2797 | 3.478592072170585 | 7.0000 | 0.0001 | 1162678.8747 | 11.994170179601195 | 23.9996 | 0.0015 | | 910 | 338799.1540 | 3.4927387758889044 | 6.9999 | 0.0001 | 1166834.3104 | 12.029095683549643 | 23.9996 | 0.0001 | | 438 | 335488.9579 | 3.5050823580421069 | 6.9999 | 0.0002 | 1150602.4234 | 12.021129639032544 | 23.9982 | 0.0005 | | 1560 | 338661.5694 | 3.4991844580143199 | 6.9997 | 0.0001 | 1154747.3055 | 11.93130307492018 | 23.9994 | 0.0019 | +-----------+--------------+--------------------------+--------------+--------------+--------------+--------------------------+--------------+--------------+ 1560 tuples (3m 55s) !4 columns dropped! note: to disable dropping columns and/or truncating fields use \w-1 Hear, Monetdb gives only 9 column in result table and gives message 4 columns dropped as i show in following query it gives result of only yellow highlighted statement / columns result. Monetdb can not show blue highlighted part's result. **sql>select product_id, sum(unit_sales),avg(unit_sales), max(unit_sales), min(unit_sales),sum(store_sales),avg(store_sales), max(store_sales), min(store_sales), sum(store_cost),avg(store_cost), max(store_cost), min(store_cost) from sales_fact_1997 group by product_id; my question is that, Monetdb calculate result of all SQL statement or it does not calculate dropped column value. My Next Question How will I see this Dropped result? I hope you will give me proper guidance. My Monetdb version : MonetDB-11.11.07 * * * -- Regards, Swapnil K. Joshi _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 2

Problems installing monet db in mountain lion
by Ivan Videla 03 Dec '12

03 Dec '12

Hello, i try to install monetdb under mac os x mountain lion. I downloaded monetdb for mac os x. X86_64 version. I copied monetdb folder to /usr/local, but i haven't been able to start a database. I have followed the instructions from here http://www.monetdb.org/Documentation/monetdbd when i get to this point ( monetdb release my-first-db ) after i try to do a monetdb status. I get that my-first-db is stopped. After i checked log file i get a message that the database appears to shutdown itself after start. I would like to know if someone has running succesfully monetdb in mac os x mountain lion. Regards, Ivan _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 2

Can each time it is accessing BAT from disk or from main memory? In my own UDF (xmin)
by swapnil joshi 02 Dec '12

02 Dec '12

Hi I have done some fun with Monetdb. i have created my own user define xmin function. objective of that function is find minimum value from specific column. I have writen some code as follow : /****************************************************************************************/ /* Function Name : xmin */ /****************************************************************************************/ #define UI sht #define UU unsigned short #define UO sht #include "impl_xmin.h" #undef UI #undef UU #undef UO #define UI int #define UU unsigned short #define UO int #include "impl_xmin.h" #undef UI #undef UU #undef UO #define UI lng #define UU unsigned short #define UO lng #include "impl_xmin.h" #undef UI #undef UU #undef UO #define UI dbl #define UU unsigned short #define UO dbl #include "impl_xmin.h" #undef UI #undef UU #undef UO static str UDFBATxmin_(BAT **ret, BAT *bone) { BAT *bres = NULL; bit two_tail_sorted_unsigned = FALSE; bit two_tail_revsorted_unsigned = FALSE; BUN n; str msg = NULL; /* assert calling sanity */ assert(ret != NULL); /* handle NULL pointer */ if (bone == NULL) throw(MAL, "batudf.xmin", RUNTIME_OBJECT_MISSING); n = BATcount(bone); /* allocate result BAT */ switch (bone->ttype) { case TYPE_sht: bres = BATnew(TYPE_void, TYPE_sht, TOTALTHREAD); break; case TYPE_int: bres = BATnew(TYPE_void, TYPE_int, TOTALTHREAD); break; case TYPE_lng: bres = BATnew(TYPE_void, TYPE_lng, TOTALTHREAD); break; case TYPE_dbl: bres = BATnew(TYPE_void, TYPE_dbl, TOTALTHREAD); break; default: throw(MAL, "batudf.xmin","tails of input BATs must be one of {sht, int, lng, dbl}"); } if (bres == NULL) throw(MAL, "batudf.xmin", MAL_MALLOC_FAIL); /* advice on sequential scan */ BATaccessBegin(bone, USE_TAIL, MMAP_SEQUENTIAL); /* call type-specific core algorithm */ switch (bone->ttype) { case TYPE_sht: msg = UDFBATxmin_sht_sht ( bres, bone, n,&two_tail_sorted_unsigned, &two_tail_revsorted_unsigned ); break; case TYPE_int: msg = UDFBATxmin_int_int ( bres, bone, n,&two_tail_sorted_unsigned, &two_tail_revsorted_unsigned ); break; case TYPE_lng: msg = UDFBATxmin_lng_lng ( bres, bone, n,&two_tail_sorted_unsigned, &two_tail_revsorted_unsigned ); break; case TYPE_dbl: msg = UDFBATxmin_dbl_dbl ( bres, bone, n,&two_tail_sorted_unsigned, &two_tail_revsorted_unsigned ); break; default: BBPreleaseref(bres->batCacheid); throw(MAL, "batudf.xmin","tails of input BATs must be one of {sht, int, lng, dbl}"); } BATaccessEnd(bone, USE_TAIL, MMAP_SEQUENTIAL); if (msg != MAL_SUCCEED) { BBPreleaseref(bres->batCacheid); } else { /* set number of tuples in result BAT */ BATsetcount(bres, 1); /* set result properties */ bres->hdense = TRUE; /* result head is dense */ BATseqbase(bres, bone->hseqbase); /* result head has same seqbase as input */ bres->hsorted = 1; /* result head is sorted */ bres->hrevsorted = (BATcount(bres) <= 1); BATkey(bres, TRUE); /* result head is key (unique) */ /* Result tail is sorted, if the left/first input tail is * sorted and key (unique), or if the left/first input tail is * sorted and the second/right input tail is sorted and the * second/right tail values are either all >= 0 or all < 0; * otherwise, we cannot tell. */ if (BATtordered(bone) && (BATtkey(bone) || two_tail_sorted_unsigned)) bres->tsorted = 1; else bres->tsorted = (BATcount(bres) <= 1); if (BATtrevordered(bone) && (BATtkey(bone) || two_tail_revsorted_unsigned)) bres->trevsorted = 1; else bres->trevsorted = (BATcount(bres) <= 1); /* result tail is key (unique), iff both input tails are */ /*BATkey(BATmirror(bres), BATtkey(bone) || BATtkey(btwo));*/ *ret = bres; } return msg; } /* MAL wrapper */ str UDFBATxmin(bat *ires, bat *ione) { // startTimer(); BAT *bres = NULL, *bone = NULL; str msg = NULL; /* assert calling sanity */ assert(ires != NULL && ione != NULL); /* bat-id -> BAT-descriptor */ if ((bone = BATdescriptor(*ione)) == NULL) throw(MAL, "batudf.xmin", RUNTIME_OBJECT_MISSING); /* do the work */ msg = UDFBATxmin_ ( &bres, bone); /* release input BAT-descriptors */ BBPreleaseref(bone->batCacheid); if (msg == MAL_SUCCEED) { /* register result BAT in buffer pool */ BBPkeepref((*ires = bres->batCacheid)); } // printf("Total time Required to UDFBATmin = %lf",endTimer()); return msg; } /****************************************************************************************/ /* Function Name : impl_xmin.h */ /****************************************************************************************/ * impl_xmin.h * * Created on: 23-Nov-2012 * Author: swapnil */ /* concatenate two or five tokens */ #define U_CONCAT_2(a,b) a##b #define U_CONCAT_5(a,b,c,d,e) a##b##c##d##e /* function names, *_nil & TYPE_* macros */ #define UF(p,i,o,s) U_CONCAT_5(p,i,_,o,s) #define UN(t) U_CONCAT_2(t,_nil) #define UT(t) U_CONCAT_2(TYPE_,t) static str UF(UDFBATxmin_,UI,UO,) ( BAT *bres, BAT *bone, BUN n, bit *two_tail_sorted_unsigned, bit *two_tail_revsorted_unsigned ) { UI *one = NULL; UO *res = NULL; BUN i; /* assert calling sanity */ assert(bres != NULL && bone != NULL); assert(BATcapacity(bres) >= 1); assert(BATcount(bone) >= n); assert(bone->ttype == UT(UI)); assert(bres->ttype == UT(UO)); /* get direct access to the tail arrays */ one = (UI*) Tloc(bone, BUNfirst(bone)); res = (UO*) Tloc(bres, BUNfirst(bres)); int loop; startTimer(); res[0]=one[0]; for(loop=1;loop<n;loop++) { if(res[0]>one[loop]) res[0]=one[loop]; } printf("Time for clReleaseMemObject = %lf\n",endTimer()); return MAL_SUCCEED; } /* undo local defines */ #undef UT #undef UN #undef UF #undef U_CONCAT_5 #undef U_CONCAT_2 //*************************************************************************************************/ when i am executing following SQL statement then it will give result but it takes 10 to 13 seconds I know where i am executing on single core of CPU but when i executing that above statement then, I think it will taking data from disk because disk access indicator led blow when i executing that above SQL statement. means, It was not using system main memory. I will be wrong. Can each time it is accessing BAT from disk or from main memory? Can you test me Program ? and Can you give me guidance for accessing BAT? I hope you will give me proper guidance. My SQL statement results are as follow sql>select xmin(v1) from demo; +---------+ | xmin_v1 | +=========+ | 1 | +---------+ 1 tuple (3.2s) sql>select xmin(v1) from demo; +---------+ | xmin_v1 | +=========+ | 1 | +---------+ 1 tuple (9.3s) sql>select xmin(v1) from demo; +---------+ | xmin_v1 | +=========+ | 1 | +---------+ 1 tuple (14.3s) sql>select xmin(v1) from demo; +---------+ | xmin_v1 | +=========+ | 1 | +---------+ 1 tuple (3.4s) -- Regards, Swapnil K. Joshi _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 2

Re: users-list Digest, Vol 4, Issue 1
by swapnil joshi 02 Dec '12

02 Dec '12

Hi Lefteris, You have asked me, which version of monetdb are you using? I am using* MonetDB-11.11.7 *version of monetdb. and my dbfarm is on my own system where i have executed this query. My System configuration is as follow: Hardware : Intel i7 2.3GHz Processor, DDR3 8GB RAM, 1TB hard disk S/W : Ubuntu 12.04, MonetDB-11.11.7 On Sat, Dec 1, 2012 at 4:30 PM, <users-list-request(a)monetdb.org> wrote: > Send users-list mailing list submissions to > users-list(a)monetdb.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.monetdb.org/mailman/listinfo/users-list > or, via email, send a message with subject or body 'help' to > users-list-request(a)monetdb.org > > You can reach the person managing the list at > users-list-owner(a)monetdb.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of users-list digest..." > > > Today's Topics: > > 1. Same SQL Statement with different throughput time. (swapnil joshi) > 2. Re: Same SQL Statement with different throughput time. > (Charalampos Nikolaou) > 3. Re: Same SQL Statement with different throughput time. (Lefteris) > 4. Re: Same SQL Statement with different throughput time. > (Stefan Manegold) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 30 Nov 2012 16:59:57 +0530 > From: swapnil joshi <webmaster.swapnil(a)gmail.com> > To: Stefan.Manegold(a)cwi.nl, users-list(a)monetdb.org > Subject: Same SQL Statement with different throughput time. > Message-ID: > < > CAFBccRCGURekT6sCL3SSvOGMWCBwaJv+kFD_bNnyVWEkmC8f3Q(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi Stefan, > If monetdb doesn't maintain any caching then when i am creating test1 > database > which contain demo table which contain 100 million records. > > When first time i am executing "SELECT SUM(V1) FROM DEMO;" > monetdb gives me result in (11.4s) > when immediate i am trying to execute same query "SELECT SUM(V1) FROM > DEMO;" > It gives me result in (31.065ms) > > How / why this happen? > > I have also checked my OS memory cache and I have erased OS Memory cache. > Now, I am trying same query "SELECT SUM(V1) FROM DEMO;" > now also he take same time in milliseconds approximate(30.723ms) > > why he first time take lot of time and every next time he take negligible > time. > > I hope you will clear my problem related of throughput time. > > -- > Regards, > Swapnil K. Joshi > _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 0

Octopus and
by Masood Mortazavi 02 Dec '12

02 Dec '12

Hi, Where would I find any documentation or instructions to try MonetDB's Octopus functionality, assuming it is still active at (or near) the tip? Regards, Masood P.S. I would also be interested in exploring Monet's any other distributed processing functionality, say Monet/Datacyclotron or Monet/MapReduce. _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 1

Re: Same SQL Statement with different throughput time.
by Stefan Manegold 30 Nov '12

30 Nov '12

I guess it's a good idea to run your query in both cases, slow & fast prefixed with TRACE to see where time is spent. BTW, are we talking about genuine MonetDB (as Letters asked: which version) and hence original MonetDB SUM()-implementation, or has the code been modified or extended; f the latter: where & how? S. -- | Stefan.Manegold @ CWI.nl | DB Architectures (INS1) | | http://CWI.nl/~manegold/ | Science Park 123 (L321) | | Tel.: +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) | ----- Reply message ----- From: "Lefteris" <lsidir(a)gmail.com> To: "Communication channel for MonetDB users" <users-list(a)monetdb.org> Subject: Same SQL Statement with different throughput time. Date: Fri, Nov 30, 2012 12:58 just restarting monetdb wont do it (OS will still keep in memory the data), you will also need to clean the memory, for example alloc all memory space, write 1's and then free again the memory. Swapnil, which version of monetdb are you using? IMO, 11 seconds vs. 30 milliseconds is too much of a difference to be just I/O. But maybe I am wrong, maybe your dbfarm is on a network? On Fri, Nov 30, 2012 at 12:42 PM, Charalampos Nikolaou <charnik(a)di.uoa.gr>wrote: > I think the reason is that for the first query the time is spent > mainly for loading your table in main memory. > Then, the second query has only the overhead of computing the sum over > column V1. > > To see this, you can run the query, restart monetdbd, and then run the > query again. You should get similar performance to that of the first > run. > > Babis > > On Fri, Nov 30, 2012 at 1:29 PM, swapnil joshi > <webmaster.swapnil(a)gmail.com> wrote: > > Hi Stefan, > > If monetdb doesn't maintain any caching then when i am creating > test1 > > database > > which contain demo table which contain 100 million records. > > > > When first time i am executing "SELECT SUM(V1) FROM DEMO;" > > monetdb gives me result in (11.4s) > > when immediate i am trying to execute same query "SELECT SUM(V1) FROM > DEMO;" > > It gives me result in (31.065ms) > > > > How / why this happen? > > > > I have also checked my OS memory cache and I have erased OS Memory cache. > > Now, I am trying same query "SELECT SUM(V1) FROM DEMO;" > > now also he take same time in milliseconds approximate(30.723ms) > > > > why he first time take lot of time and every next time he take negligible > > time. > > > > I hope you will clear my problem related of throughput time. > > > > -- > > Regards, > > Swapnil K. Joshi > > > > > > _______________________________________________ > > users-list mailing list > > users-list(a)monetdb.org > > http://mail.monetdb.org/mailman/listinfo/users-list > > > _______________________________________________ > users-list mailing list > users-list(a)monetdb.org > http://mail.monetdb.org/mailman/listinfo/users-list > _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 0

Same SQL Statement with different throughput time.
by swapnil joshi 30 Nov '12

30 Nov '12

Hi Stefan, If monetdb doesn't maintain any caching then when i am creating test1 database which contain demo table which contain 100 million records. When first time i am executing "SELECT SUM(V1) FROM DEMO;" monetdb gives me result in (11.4s) when immediate i am trying to execute same query "SELECT SUM(V1) FROM DEMO;" It gives me result in (31.065ms) How / why this happen? I have also checked my OS memory cache and I have erased OS Memory cache. Now, I am trying same query "SELECT SUM(V1) FROM DEMO;" now also he take same time in milliseconds approximate(30.723ms) why he first time take lot of time and every next time he take negligible time. I hope you will clear my problem related of throughput time. -- Regards, Swapnil K. Joshi _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 2

Monetdb Cacheing
by swapnil joshi 30 Nov '12

30 Nov '12

Hi, Is there monetdb maintain any SQL result cache. If yes, then How and where is it maintain? and If no then how he will get millions of rows result in millisecond. My System configuration is as follow : Hardware = Processor : Intel i7 2.3 GHz, RAM DDR3 8GB, HD 1 TB, OS = Ubuntu 12.04 I am new in IT world and i am doing some research on Monetdb. I have created my own user define function but it's result is not cached, every time it is doing operation on data and it take some in milli seconds. Please tell me about monetdb cacheing policy Can you give me some guide line? -- Regards, Swapnil K. Joshi _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

define your own user define function
by swapnil joshi 29 Nov '12

29 Nov '12

Hi, i am trying to define user define function which has argument integer bat and returning integer. step 1: i have added function defination in udf_80.sql as follow create function xtest(one integer) returns integer external name udf.xtest; step 2: i have added function defination in udf.mal module udf; command xtest(b:bat[:oid,:int]):int address UDFBATxtest comment "function xtest"; module batudf; command xtest(b:bat[:oid,:int]):int address UDFBATxtest comment "function xtest"; step 3: then i have define this function in udf.c file UDFBATxtest_(int *ret, BAT *src) { return MAL_SUCCEED; } str UDFBATxtest(int *ires, bat *ione) { BAT *bone = NULL; str msg = NULL; /* assert calling sanity */ assert(ione != NULL); /* bat-id -> BAT-descriptor */ if ((bone = BATdescriptor(*ione)) == NULL) throw(MAL, "batudf.xtest", RUNTIME_OBJECT_MISSING); /* do the work */ msg = UDFBATxtest_ ( ires, bone); return msg; } step 4: then i have compiled source code and installed it: step 5: i am try to execute xtest function on mclient but i got following error sql>select xtest(id) from student; TypeException:user.s23_1[16]:'udf.xtest' undefined in: _53:any := udf.xtest(_51:int) TypeException:user.s23_1[17]:'bat.insert' undefined in: _54:any := bat.insert(_45:bat[:oid,:int], _50:oid, _53:any) program contains errors step 6: write a mail and sent to you for getting help i hope you will give me. -- Regards, Swapnil K. Joshi _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 7

UDF aggregate?
by Miguel Ping 28 Nov '12

28 Nov '12

Greetings, We're currently evaluating MonetDB for a analytical DW and so far we are happy with the results. I am trying to implement a grouping function that calculates a a value over a set of strings, so that my queries would read like this: select metric, *udf_aggregate*(string_column) from table group by metric; for a bit of background, we're using a dinstinct value sketch called HyperLogLog http://metamarkets.com/2012/fast-cheap-and-98-right-cardinality-estimation-… http://blog.aggregateknowledge.com/2012/10/25/sketch-of-the-day-hyperloglog… and we're currently storing estimations for each time period (day). HLL lets you merge/aggregate a set of estimations (each estimation is a vector of numbers, we're currently storing it as a string) for an arbitrary range, and still have an accurate estimation. (I'm sure the literature doesn't call it estimations, sorry for my English) what I would like is a custom UDF like the one provided in MonetDB src (*reverse*)**but that would operate and behave like an aggregate function. Right now, I'm not considering using it for types other than /string/ (no need for polymorphic right now). Is this possible with an UDF? I found a way of registering aggregate functions on the mailing list, but the HLL is complex enough to warrant its own C impl, instead of a MAL function. Thanks, Miguel _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 3

Solid state drives for MonetDB
by Siddhartha Bagaria 28 Nov '12

28 Nov '12

Hello everyone! This is my second posting to this list and identical to the first because I am not sure if I was subscribed at the time. Please ignore if you have read this before. My apologies if this has been discussed elsewhere but a google search did not give me much. Let me give you a bit of background. We are planning to use a star schema in MonetDB as the backend for Pentaho BI reporting engine. We have a total of 2.4 B rows in the fact table and a maximum of 10 M rows in the dimension table. As you can see, this will be a read only database once the initial load is done. I was wondering what hardware architecture will give a reasonable performance over traditional BI queries. Let's define reasonable here by less than 1 minute turn-around time on joins between the fact table and the dimension table. On that note, what will be the expected performance on a machine with specs identical to the Amazon High I/O instance type which has two solid state drives - http://aws.amazon.com/ec2/instance-types/. I will of course combine the two drives in a software raid-0 configuration. My broader question is that columnar databases are typically optimized for hard drives to utilize the maximum possible disk transfer rate,; what advantages can a solid state drive offer over a traditional hard drive when used solely for MonetDB? I can imagine some advantages maybe in the swap-ins for VM pages but I am not really an expert. Also, some advantages in multi-threaded disk reads. Sid _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 0

Looking for advice on ways to limit Monet's RAM usage
by Percy Wegmann 28 Nov '12

28 Nov '12

Hello, We're running the Oct2012-SP1 release on Ubuntu 12.04.1. It's working great, but we need to constrain its RAM usage because it's not the only process running on its machine. >From the mailing list archives, it looks like ulimit is the recommended way of doing this, but we haven't been able to get it to do what we want. Specifically, we've tried: ulimit -Sm (max resident set size) ulimit -Sv (max virtual memory) Limiting the resident set size doesn't seem to have an effect - the mserver5 process's resident size seems to grow freely. Limiting the virtual memory does in fact manage to keep mserver5 from consuming more than the allocated amount, however when mserver5 hits the limit, it just crashes (which is what I would have expected based on this document <http://www.monetdb.org/Documentation/UserGuide/resources>). Our next step is to look at Linux Containers <http://lxc.sourceforge.net/>, but before going that route I figured I'd check and see how other folks have handled this. Thanks in advance, Percy -- Percy Wegmann +1 512 637 8500 ext 148 _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 3

!TypeException:user.s1_1[76]:'aggr.sum' undefined
by swapnil joshi 28 Nov '12

28 Nov '12

Hello Sir, I have some problem in MAL execution. *setp 1:* I have open [mclient -d test1] and {explain select sum(v1) from demo;} it show following result. swapnil@swapnil-lp:~$ mclient test1 Welcome to mclient, the MonetDB/SQL interactive terminal (Jul2012-SP1) Database: MonetDB v11.11.7 (Jul2012-SP1), 'mapi:monetdb://swapnil-lp:50000/test1' Type \q to quit, \? for a list of available commands auto commit mode: on sql>explain select sum(v1) from demo; +-------------------------------------------------------------------------------+ | mal | +===============================================================================+ | function user.s1_1{autoCommit=true}():void; | | X_13:lng := nil:lng; | | barrier X_141 := language.dataflow(); | | X_2 := sql.mvc(); | | X_35:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",0,0,8); | | X_71 := algebra.selectNotNil(X_35); | | X_60:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",2,0,8); | | X_83 := algebra.kdifference(X_71,X_60); | | X_95 := algebra.selectNotNil(X_60); | | X_104 := algebra.kunion(X_83,X_95); | | X_11:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","demo",1); | | X_12 := bat.reverse(X_11); | | X_117 := algebra.kdifference(X_104,X_12); | | X_131 := aggr.sum(X_117); | | X_39:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",0,1,8); | | X_73 := algebra.selectNotNil(X_39); | | X_62:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",2,1,8); | | X_84 := algebra.kdifference(X_73,X_62); | | X_97 := algebra.selectNotNil(X_62); | | X_106 := algebra.kunion(X_84,X_97); | | X_118 := algebra.kdifference(X_106,X_12); | | X_132 := aggr.sum(X_118); | | X_42:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",0,2,8); | | X_75 := algebra.selectNotNil(X_42); | | X_63:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",2,2,8); | | X_85 := algebra.kdifference(X_75,X_63); | | X_98 := algebra.selectNotNil(X_63); | | X_108 := algebra.kunion(X_85,X_98); | | X_119 := algebra.kdifference(X_108,X_12); | | X_133 := aggr.sum(X_119); | | X_45:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",0,3,8); | | X_77 := algebra.selectNotNil(X_45); | | X_64:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",2,3,8); | | X_86 := algebra.kdifference(X_77,X_64); | | X_99 := algebra.selectNotNil(X_64); | | X_110 := algebra.kunion(X_86,X_99); | | X_120 := algebra.kdifference(X_110,X_12); | | X_134 := aggr.sum(X_120); | | X_48:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",0,4,8); | | X_78 := algebra.selectNotNil(X_48); | | X_65:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",2,4,8); | | X_87 := algebra.kdifference(X_78,X_65); | | X_100 := algebra.selectNotNil(X_65); | | X_112 := algebra.kunion(X_87,X_100); | | X_121 := algebra.kdifference(X_112,X_12); | | X_135 := aggr.sum(X_121); | | X_51:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",0,5,8); | | X_80 := algebra.selectNotNil(X_51); | | X_66:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",2,5,8); | | X_89 := algebra.kdifference(X_80,X_66); | | X_101 := algebra.selectNotNil(X_66); | | X_113 := algebra.kunion(X_89,X_101); | | X_123 := algebra.kdifference(X_113,X_12); | | X_136 := aggr.sum(X_123); | | X_54:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",0,6,8); | | X_81 := algebra.selectNotNil(X_54); | | X_68:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",2,6,8); | | X_91 := algebra.kdifference(X_81,X_68); | | X_102 := algebra.selectNotNil(X_68); | | X_114 := algebra.kunion(X_91,X_102); | | X_125 := algebra.kdifference(X_114,X_12); | | X_137 := aggr.sum(X_125); | | X_58:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",0,7,8); | | X_82 := algebra.selectNotNil(X_58); | | X_70:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",2,7,8); | | X_93 := algebra.kdifference(X_82,X_70); | | X_103 := algebra.selectNotNil(X_70); | | X_115 := algebra.kunion(X_93,X_103); | | X_127 := algebra.kdifference(X_115,X_12); | | X_138 := aggr.sum(X_127); | | X_8:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",1); | | X_10 := algebra.selectNotNil(X_8); | | X_129 := algebra.kdifference(X_10,X_12); | | X_139 := aggr.sum(X_129); | | X_130 := mat.pack(X_131,X_132,X_133,X_134,X_135,X_136,X_137,X_138,X_139); | | X_140 := algebra.selectNotNil(X_130); | | X_13:lng := aggr.sum(X_140); | | exit X_141; | | sql.exportValue(1,"sys.demo","L1","bigint",32,0,6,X_13,""); | | end s1_1; | +-------------------------------------------------------------------------------+ 80 tuples (2.845ms) *Setp 2:* I have copy same mal program on another teminal [mclient -lmsql -dtest1] swapnil@swapnil-lp:~$ mclient -lmsql -dtest1 Welcome to mclient, the MonetDB interactive terminal (Jul2012-SP1) Type \q to quit, \? for a list of available commands msql>function user.s1_1{autoCommit=true}():void; msql> X_13:lng := nil:lng; msql> barrier X_141 := language.dataflow(); msql> X_2 := sql.mvc(); msql> X_35:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",0,0,8); msql> X_71 := algebra.selectNotNil(X_35); msql> X_60:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",2,0,8); msql> X_83 := algebra.kdifference(X_71,X_60); msql> X_95 := algebra.selectNotNil(X_60); msql> X_104 := algebra.kunion(X_83,X_95); msql> X_11:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","demo",1); msql> X_12 := bat.reverse(X_11); msql> X_117 := algebra.kdifference(X_104,X_12); msql> X_131 := aggr.sum(X_117); msql> X_39:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",0,1,8); msql> X_73 := algebra.selectNotNil(X_39); msql> X_62:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",2,1,8); msql> X_84 := algebra.kdifference(X_73,X_62); msql> X_97 := algebra.selectNotNil(X_62); msql> X_106 := algebra.kunion(X_84,X_97); msql> X_118 := algebra.kdifference(X_106,X_12); msql> X_132 := aggr.sum(X_118); msql> X_42:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",0,2,8); msql> X_75 := algebra.selectNotNil(X_42); msql> X_63:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",2,2,8); msql> X_85 := algebra.kdifference(X_75,X_63); msql> X_98 := algebra.selectNotNil(X_63); msql> X_108 := algebra.kunion(X_85,X_98); msql> X_119 := algebra.kdifference(X_108,X_12); msql> X_133 := aggr.sum(X_119); msql> X_45:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",0,3,8); msql> X_77 := algebra.selectNotNil(X_45); msql> X_64:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",2,3,8); msql> X_86 := algebra.kdifference(X_77,X_64); msql> X_99 := algebra.selectNotNil(X_64); msql> X_110 := algebra.kunion(X_86,X_99); msql> X_120 := algebra.kdifference(X_110,X_12); msql> X_134 := aggr.sum(X_120); msql> X_48:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",0,4,8); msql> X_78 := algebra.selectNotNil(X_48); msql> X_65:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",2,4,8); msql> X_87 := algebra.kdifference(X_78,X_65); msql> X_100 := algebra.selectNotNil(X_65); msql> X_112 := algebra.kunion(X_87,X_100); msql> X_121 := algebra.kdifference(X_112,X_12); msql> X_135 := aggr.sum(X_121); msql> X_51:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",0,5,8); msql> X_80 := algebra.selectNotNil(X_51); msql> X_66:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",2,5,8); msql> X_89 := algebra.kdifference(X_80,X_66); msql> X_101 := algebra.selectNotNil(X_66); msql> X_113 := algebra.kunion(X_89,X_101); msql> X_123 := algebra.kdifference(X_113,X_12); msql> X_136 := aggr.sum(X_123); msql> X_54:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",0,6,8); msql> X_81 := algebra.selectNotNil(X_54); msql> X_68:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",2,6,8); msql> X_91 := algebra.kdifference(X_81,X_68); msql> X_102 := algebra.selectNotNil(X_68); msql> X_114 := algebra.kunion(X_91,X_102); msql> X_125 := algebra.kdifference(X_114,X_12); msql> X_137 := aggr.sum(X_125); msql> X_58:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",0,7,8); msql> X_82 := algebra.selectNotNil(X_58); msql> X_70:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",2,7,8); msql> X_93 := algebra.kdifference(X_82,X_70); msql> X_103 := algebra.selectNotNil(X_70); msql> X_115 := algebra.kunion(X_93,X_103); msql> X_127 := algebra.kdifference(X_115,X_12); msql> X_138 := aggr.sum(X_127); msql> X_8:bat[:oid,:int] := sql.bind(X_2,"sys","demo","v1",1); msql> X_10 := algebra.selectNotNil(X_8); msql> X_129 := algebra.kdifference(X_10,X_12); msql> X_139 := aggr.sum(X_129); msql> X_130 := mat.pack(X_131,X_132,X_133,X_134,X_135,X_136,X_137,X_138,X_139); msql> X_140 := algebra.selectNotNil(X_130); msql> X_13:lng := aggr.sum(X_140); msql> exit X_141; msql> sql.exportValue(1,"sys.demo","L1","bigint",32,0,6,X_13,""); msql> end s1_1; MAPI = (monetdb) /tmp/.s.monetdb.50000 QUERY = end s1_1; ERROR = !TypeException:user.s1_1[76]:'aggr.sum' undefined in: X_13:lng := aggr.sum(X_140:bat[:oid,:dbl]) msql>user.s1_1 MAPI = (monetdb) /tmp/.s.monetdb.50000 QUERY = user.s1_1 ERROR = !SyntaxException:parseError: !'(' expected msql>user.s1_1(); MAPI = (monetdb) /tmp/.s.monetdb.50000 QUERY = user.s1_1(); ERROR = !TypeException:user.main[1]:'user.s1_1' undefined in: _1:void := user.s1_1() msql> It gives such error what is reason of giving such error by monetdb. i am really very frustrate what is reasone and how will i execute mal program. please help me !!!!!!!!!!!!! :) and another question is is Monetdb maintain any cache for storing result of SQL statment. -- Regards, Swapnil K. Joshi -- Regards, Swapnil K. Joshi _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

Support of nulls first / last in order clause
by Matthieu Guamis 23 Nov '12

23 Nov '12

Hello, "NULLS LAST" seems to be part of the SQL 99 standardbut is not implemented in Monetdb. Do you think it couldbe implemented in Monetdb? Can I fill a bug?Can I help you in some way? The syntax is as follows: ORDER BY [COLUMN NAME] [ASC | DESC] [NULLS FIRST | NULLS LAST] In different DBs, the sorting of nulls relative to other values is handled differently. PostgreSQL - Nulls are considered HIGHER than non-nulls. DB2 - Higher Oracle - Higher MySQL - Lower Monetdb - Lower Thanks -- *Matthieu Guamis* *Logo Axège <http://www.axege.com/>* /Axège// 22 bis, rue des Chazots 63170 Aubière/ Tél: +33 (0)4 63 05 95 40 Fax: +33 (0)4.73.70.65.29 Email: matthieu.guamis(a)axege.com <mailto:matthieu.guamis@axege.com> _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 0

database failing to start
by Flavio Coelho 22 Nov '12

22 Nov '12

Hi I had monetdb setup working for few months and recently, all of a sudden the database would not start any more. I have tried everything I could find in the docs: checking permissons reinstalling the packages, deleting and recreating the databases, Farm,, etc... Now I can't even start an new empty database. Here is the erro I get in the log: 2012-11-22 08:31:08 MSG control[15663]: (local): served status list 2012-11-22 08:31:08 MSG merovingian[15663]: startup of database under maintenance 'sapo' forced 2012-11-22 08:31:08 MSG merovingian[15663]: starting database 'sapo', up min/avg/max: 0s/0s/0s, crash average: 0.00 0.00 0.00 (0-0=0) 2012-11-22 08:31:08 MSG sapo[16066]: arguments: /usr/bin/mserver5 --set gdk_dbfarm=/Ldisco1/Monet_dbs/ SAP_farm --dbname=sapo --set merovingian_uri=mapi:monetdb:// bon051.cloud.fgv.br:50000/sapo --set mapi_open=false --set mapi_port=0 --set mapi_usock=/Ldisco1/Monet_dbs/SAP_farm/sapo/.mapi.sock --set monet_vault_key=/Ldisco1/Monet_dbs/SAP_farm/sapo/.vaultkey --set gdk_nr_threads=16 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes 2012-11-22 08:31:08 MSG merovingian[15663]: database 'sapo' (16066) has exited with exit status 127 2012-11-22 08:31:08 ERR control[15663]: (local): failed to fork mserver: database 'sapo' appears to shut itself down after starting, check monetdbd's logfile for possible hints Any ideas why this problem may be happening? I have another Ubuntu64 machine with the same versions of monet and it works normally. I must be overlooking some detail of configuration. It may be a good Idea to add a FAQ to the docs with possible causes for well known crashes. I am on an Ubuntu 64 bits with latest MOnetdb: $ uname -a Linux bon051.cloud.fgv.br 3.2.0-26-generic #41-Ubuntu SMP Thu Jun 14 17:49:24 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux administrador@bon051:~$ monetdb -v MonetDB Database Server Toolkit v1.0 (Oct2012-SP1) administrador@bon051:~$ monetdbd -v MonetDB Database Server v1.6 (Oct2012-SP1) thanks, -- Flávio Codeço Coelho ================ +55(21) 3799-5567 Professor Escola de Matemática Aplicada Fundação Getúlio Vargas Praia de Botafogo, 190 sala 312 Rio de Janeiro - RJ 22250-900 Brasil _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 11

Distributing databases/tables
by Pedro Salgueiro 22 Nov '12

22 Nov '12

Greetings! We have been testing MonetDB for use in AWS in the last couple of weeks and we are surprised with its overall performance, even when dealing with large tables and under-powered machines. Still, we were wondering if its possible in anyway to improve the performance by distributing the databases/tables through several machines. While looking at MonetDB documentation and the mailing list archives, I get some mixed answers about this topic and nothing very concrete. We noticed that it's possible to create a cluster of MonetDB instances, but it seems that it's main purpose is to ease the administration of several MonetDB instances and provide a single entrance point to several MonetDB instances. Still, we still have some questions about its use: Is it possible to partition a table across several MonetDB instances in order to improve the performance? Best regards, Pedro Salgueiro _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

Aggregation according to multiple criteria at once
by Адель Ризаев 22 Nov '12

22 Nov '12

Hello to Everybody, I'm doing an averaging over one column using some specific range in another column multiple times. Actually the query looks like: select avg(value) from myTable where time<N and time>M. i'm calling that query from the python script multiple times. Can i call the query once in order to reduce the number of requests to the monetDB? Best regards, Adel _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 3

Announcement: New Oct2012-SP1 Bugfix release of MonetDB suite
by Sjoerd Mullender 21 Nov '12

21 Nov '12

The MonetDB team at CWI/MonetDB BV is pleased to announce the Oct2012-SP1 bugfix release of the MonetDB suite of programs. More information about MonetDB can be found on our website at <http://www.monetdb.org/>. For details on this release, please see the release notes at <http://www.monetdb.org/Downloads/ReleaseNotes>. As usual, the download location is <http://dev.monetdb.org/downloads/>. Oct 2012-SP1 bugfix release Bug Fixes * 3155: Provide an option for setting discovery to false * 3161: invalid tuple received from server, got 138 columns, expected 476, ignoring * 3182: When using aggregate SQL functions, precision & decimal metadata for numeric/decimal type returned is 0,0 _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 0

Monet Upgrade--Degraded performance
by Jerry Ramey 19 Nov '12

19 Nov '12

Begin forwarded message: > From: Jerry Ramey <jerry.ramey(a)codefutures.com> > Subject: Monet Upgrade--Degraded performance > Date: November 19, 2012 11:51:34 AM MST > To: users-list(a)monetdb.org > > Hello, > > We had previously asked some advice on some slow Monet performance: > http://mail.monetdb.org/pipermail/users-list/2012-September/005765.html > > As per suggestion we upgraded to the Oct2012 release and we are seeing severely degraded performance. Many queries taking over an hour to complete--mostly they are not especially complicated SELECTs with some arithmetical computation, some concurrently though mostly in succession. > > The database is relationally spread across two servers, the most predominant table with approximately 300 million rows per server, the instances are 68.40 GB with 26 (8 cores x 3.25 units) and CentOS 5.4 x64. Each instance is overloaded with IO wait and minimal CPU usage. The available memory is quickly used and doesn't appear to be released. > > Any advice would be appreciated. Let me know what additional information you require. > > Thanks! > Drew M. _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

Cross-column time computation doesn't appear to work in Oct 2012 release
by Percy Wegmann 19 Nov '12

19 Nov '12

I couldn't find any existing bug logs for the below issue and want to make sure that it's not a known issue before I log it. Basically, performing time computation across columns doesn't work. percy@percy-sandbox:~$ uname -a Linux percy-sandbox 3.2.0-33-generic #52-*Ubuntu* SMP Thu Oct 18 16:29:15 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux percy@percy-sandbox:~$ monetdbd -v *MonetDB Database Server v1.6 (Oct2012)* * * percy@percy-sandbox:~$ mclient -u monetdb -d click password: Welcome to mclient, the MonetDB/SQL interactive terminal (Oct2012) Database: *MonetDB v11.13.3 (Oct2012)*, 'mapi:monetdb://percy-sandbox:50000/click' Type \q to quit, \? for a list of available commands auto commit mode: on sql>*create table time_table (atime timestamp, btime timestamp, ctime date); * operation successful (33.944ms) sql>*insert into time_table values(timestamp '1970-JAN-1', timestamp '1980-DEC-31', date '2012-JAN-1');* 1 affected row (20.649ms) sql>select * from time_table; +----------------------------+----------------------------+------------+ | atime | btime | ctime | +============================+============================+============+ | 1970-01-01 00:00:00.000000 | 1980-12-31 00:00:00.000000 | 2012-01-01 | +----------------------------+----------------------------+------------+ *1 tuple* (1.402ms) sql>select btime <> atime from time_table; +----------+ | <>_btime | +==========+ | true | +----------+ *1 tuple* (1.208ms) sql>select btime - timestamp '1975-JAN-01' from time_table; +---------------+ | sql_sub_btime | +===============+ | 189302400000 | +---------------+ *1 tuple* (1.389ms) sql>select btime - atime from time_table; +---------------+ | sql_sub_btime | +===============+ +---------------+ *0 tuples* (1.450ms) Expected result: All queries return 1 tuple Actual result: The query that performs date subtraction between two columns returns 0 tuples. Thanks, -- Percy Wegmann _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 2

Monetdb bulk copy crash
by Medha Atre 19 Nov '12

19 Nov '12

Hi, I am using the latest MonetDB (Oct 2012 release) and creating an RDF database of 1.33 billion triples as follows: $ monetdbd start /path/to/dbfarm $ monetdb create rdf1b $ monetdb release rdf1b $ monetdb start rdf1b _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 4

How do I interpret testweb listing for the latest patches the next release?
by Brandon Jackson 17 Nov '12

17 Nov '12

45868:949c8b8db28d Was suggested to me for fixing the recent error with aggregates and scaling. Which area is the best one to go to for receiving the patches going into the next release? Thanks for the guidance. Brandon _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

Client PHP too slow with many results
by Eduardo Oliveira 16 Nov '12

16 Nov '12

Hello, I'm finding php client too slow returning big result sets. I'm using php client i i downloaded from http://dev.monetdb.org/downloads/sources/Latest/ MonetDB-11.13.3.tar.bz2 Some benchmark down, anyway of get the results faster? LIMIT 50K [root@monetdb examples]# php simple_query.php *9* [root@monetdb examples]# time mclient -u adctest -d adctest --statement='SELECT * FROM summary_sent LIMIT 50000' > res.txt password: real 0m4.566s <- already counting with some time to password input user 0m1.272s sys 0m0.132s ---- LIMIT 100K [root@monetdb examples]# time mclient -u adctest -d adctest --statement='SELECT * FROM summary_sent LIMIT 100000' > res.txt password: *real 0m7.184s* user 0m2.545s sys 0m0.266s [root@monetdb examples]# php simple_query.php *18* ---------- Code: [root@monetdb examples]# cat simple_query.php <?php require '../lib/php_monetdb.php'; $db = monetdb_connect("sql", '127.0.0.1', 50000, 'adctest', 'adctest', 'adctest') or trigger_error(monetdb_last_error()); $start_query_monetdb = time(); $res = monetdb_query($db, monetdb_escape_string('SELECT * FROM summary_sent LIMIT 100000')) or trigger_error(monetdb_last_error()); while ( $row = monetdb_fetch_object($res) ) { } $time = time() - $start_query_monetdb; echo $time . "\n"; /* Free the result set */ monetdb_free_result($res); /* Disconnect from the database */ if (monetdb_connected($db)) { monetdb_disconnect($db); } -- *Eduardo Oliveira * *IT* ***Email:* eduardo.oliveira(a)adclick.pt <nuno.morais(a)adclick.pt> *Web: * www.adclickint.com ** <http://www.adclickint.com/> * * <http://www.adclickint.com/> <http://www.adclickint.com/> _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

4 5

Ubuntu compilation problem
by Matthieu Guamis 14 Nov '12

14 Nov '12

Hello, I'm tryingto compile MonetDB on Ubuntu 12.04 x64but It fails with alot of "../mapilib/.libs/libmapi.so: undefined reference to `SHA256'".I though it was related with a library linking problem,but I use LDFLAGS=-lssl -lcrypt and CFLAGS=-Wl,-verbose which give me : attempt to open /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libssl.so succeeded -lssl (/usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libssl.so) ... attempt to open /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypt.so succeeded -lcrypt (/usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libcrypt.so) I'm not very familiar with Make and C,so Iwould appreciate some help. PS: Could it be related to the packaging problem reported on the lastreleases notes "No Debian and Ubuntu packages were built for this release due to a packaging failure"? Thanks a lot -- *Matthieu Guamis* *Logo Axège <http://www.axege.com/>* /Axège// 22 bis, rue des Chazots 63170 Aubière/ Tél: +33 (0)4 63 05 95 40 Fax: +33 (0)4.73.70.65.29 Email: matthieu.guamis(a)axege.com <mailto:matthieu.guamis@axege.com> _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

5 5

growing size of database
by Medha Atre 14 Nov '12

14 Nov '12

Hi, I am running the latest MonetDB 11.13.3. I loaded a pretty tiny RDF dataset of 13 million triples and created some "vertical partitions" on predicate values. After having done dataset loading, I checked the size of the dataset folder and it showed to be _258 MB_. Then I ran about 6000+ bulk queries by periodically shutting down the server after about 1000 queries each time. The queries finished successfully and there was no crash. After the final query I stopped the database "monetdb stop dbname" and shutdown the main server too "monetdbd stop /path/to/dbfarm". After that I again checked the size of the database folder and then it showed it to be _5.8GB_ and the "HC" folder under "bat" was shown to have size of about 3 GB with some other files having sizes between 300-700 MBs. It seems mysterious to me why would the size of database go on increasing as much as 25 times the original size. I intend to load much larger data (> 1 billion triples), and want to avoid growing disk size of the dataset due to limited disk-space. Can someone please enlighten? Medha _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 6

Database Memory Usage
by Ashish Kumar Singh 12 Nov '12

12 Nov '12

HI All, While calculating monetdb size I am observing below : When I am inserting records to Monet DB using JDBC total memory and VM usage is going to 10 G + but when I see file system size of the database directory it is showing something like 1 GB . Is some compression coming to picture here while storing data in file system? Any pointers will be helpful. Regards, Ashish _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 3

Is there a way to define type aliases for internal types?
by Percy Wegmann 11 Nov '12

11 Nov '12

I'd like to define aliases for CLOB and would like to know if/how this is possible. I tried this: create type "array" external name "str"; create table atest(it array); insert into atest values('test'); Yielding the following error: TypeException:user.s2_27[3]:'calc.array' undefined in: _5:any := calc.array(_4:str) program contains errors So, that was probably not the right way to do it ... Thanks, -- Percy Wegmann +1 512 637 8500 ext 148 _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 2

Standard Deviation, Variance, and Quantile Functions
by Anthony Damico 08 Nov '12

08 Nov '12

Hi all, I'm trying to run a simple standard deviation function on a column using MonetDB -- select stdev( columnname ) from tablename -- is this possible with the current release? The only posts I can find about stdev() or variance() are quite old, such as a 2008 post requesting medians (which has been implemented) and quantiles (which I cannot find?) http://osdir.com/ml/db.monetdb.bugs/2008-06/msg00206.html a 2010 post offering to add these functions to the main release code. http://mail.monetdb.org/pipermail/users-list/2010-January/003836.html What would be the easiest way to get MonetDB to produce standard deviations, variances, and quantiles (let's say the 25th percentile)? >From the discussion list, it looks like people have succeeded in doing it, but they're probably much more advanced users than I am. ;) Thanks!!! _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 2

[MonetDB-users] Different results with same query
by Matthieu Guamis 08 Nov '12

08 Nov '12

Hello, Running the same query on the same data leeds to different results between postgresql and monetdb. I have not been able to get a simple example to reproduce the problem. So here is what I observe: the query: select temps_mois.rfoperdmo as c1, sum((case when dwhinv.dwhinv___rfodomide = 'RH' and dwhinv.dwhinv___rfoindide = 'tech_rh_effectif_rem_reel' then dwhinv.dwhinvqte else 0 end)) as m0 from rfoper_temps_mois as temps_mois, dwhinv as dwhinv, rfovsn as rfovsn_0, rrhamv as rrhamv_1, rrhcov as rrhcov_2, rfoadv as rfoadv_3 where temps_mois.rfoper___rforefide = 'HPLUS' and dwhinv.dwhinv___rforefide = 'HPLUS' and dwhinv.dwhinv___rfodomide = 'RH' and dwhinv.dwhinv___rfoindide = 'tech_rh_effectif_rem_reel' and dwhinv.dwhinvdtd = temps_mois.rfoperdtd and temps_mois.rfoperyea = '2011' and rfovsn___rforefide = 'HPLUS' and dwhinv.dwhinv___rfovsnide = rfovsn_0.rfovsnide and rfovsn_0.rfovsnide = '201111_reel' and rrhamv_1.rrhamv___rrhvemide='GRACOR' AND rrhamv_1.rrhamvrvs=1 AND rrhamv_1.rrhamv___rforefide= 'HPLUS' and dwhinv.dwhinv___rrhempide = rrhamv_1.rrhamvinf and rrhamv_1.rrhamvsup = 'CEMP' and rrhcov_2.rrhcov___rrhvcoide='CONTRATS' AND rrhcov_2.rrhcovrvs=1 AND rrhcov_2.rrhcov___rforefide= 'HPLUS' and dwhinv.dwhinv___rrhcntide = rrhcov_2.rrhcovinf and rrhcov_2.rrhcovsup = 'CONTRATS' and rfoadv_3.rfoadv___rfovdeide='STRC' AND rfoadv_3.rfoadvrvs=1 AND rfoadv_3.rfoadv___rforefide= 'HPLUS' and dwhinv.dwhinv_p2rfodstide = rfoadv_3.rfoadvinf and rfoadv_3.rfoadvsup = 'HPLUS' group by c1 order by c1 Postgresql result: c1 | m0 ----+----------------- 01 | 7111.5376967750 02 | 7100.9108821426 03 | 7150.2597967742 04 | 7151.4283666667 05 | 7109.1641451610 06 | 6976.2108421239 07 | 6329.7404193564 08 | 6302.9823032247 09 | 6426.9459633351 10 | 6519.6889580648 11 | 6549.5235033402 12 | 6492.5477161292 (12 lignes) Monetdb result: +------+----------------------+ | c1 | m0 | +======+======================+ | 12 | 1.000000 | | 11 | 1.000000 | | 10 | 2.000000 | | 09 | 0.366667 | | 08 | 1.000000 | | 07 | 1.000000 | | 06 | 1.000000 | | 05 | 3.000000 | | 04 | 4.000000 | | 03 | 15.000000 | | 02 | 9.964286 | | 01 | 1.000000 | +------+----------------------+ 12 tuples (212.346ms) As you see, all "m0" values are very different. I have no idea of what is causing this but if I modify the query in order to simplify the CASE...WHEN...ELSE part of the select, it produce the expected result: replacing sum((case when dwhinv.dwhinv___rfodomide = 'RH' and dwhinv.dwhinv___rfoindide = 'tech_rh_effectif_rem_reel' then dwhinv.dwhinvqte else 0 end)) as m0 by sum((case when dwhinv.dwhinv___rfoindide = 'tech_rh_effectif_rem_reel' then dwhinv.dwhinvqte else 0 end)) as m0 Its not exactly the same query but it must leeds to the same result due to my test datas (its the case in postgres) I join to this email two files with the TRACES, respectively for the request with bad/correct result (ko.txt/ok.txt) Config: Ubuntu Server 11.04 x64 MonetDB v11.7.9 (Dec2011-SP2), MonetDB Database Server v1.6 (Dec2011-SP2), MonetDB Database Server Toolkit v1.0 (Dec2011-SP2) Thank you very much for your help!! -- *Matthieu Guamis* *Logo Axège <http://www.axege.com/>* /Axège// 23,rue Saint-Simon 63000 Clermont-Ferrand/ Tél: +33 (0)4 63 05 95 40 Fax: +33 (0)4.73.70.65.29 Email: matthieu.guamis(a)axege.com <mailto:matthieu.guamis@axege.com>

3 4

JDBC and transaction serialization
by Tapomay Dey 08 Nov '12

08 Nov '12

Hi, I have written a multi-threaded app that consumes multiple logs simultaneously and generates DDL/DML statements for monetdb. It uses JDBC and the threads write to a single table. However I am getting "COMMIT: transaction is aborted because of concurency conflicts, will ROLLBACK instead" very frequently. Also when it retries the insert there is some inconsistency that I have not been able to try and debug yet. Eventually there are more rows than inserts. Weird thing is I also have a unique key constraint on the table. I am guessing this happen as monetdb doesn't use locking for serialization. I have tried connection.setAutoCommit(true) by itself and also with connection.setTransactionIsolation(NONE). But in vain. Please help. Thanks and Regards, Tapomay Dey. _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 2

Re: set sql_debug in monetdb configuration file
by Liwen -George- Zhang 06 Nov '12

06 Nov '12

Hi Fabian,Thanks for looking into this. The reason why i want this is that I can't figure out why my udf function does not work. I added a MAL function to the udf.c and related files, it works when i used it in mal client, but can't make it work in sql after creating a sql function. I checked the udf.reverse example, looks like it need only a SQL function for the scalar version of reverse, and the batudf.reverse will be used automatically if i "select reverse(colname) from table". Anyway, i tried different combination, my scalar version udf function works, but BAT version don't work, thinking that sql_debug might provide some info for me before i jump into gdb. As to setting this parameter, i know i can use mserver5 --config=filename, or just mserver5 --set sql_debug, but don't know how to let monetdbd to use a configuration file. thanks for your help!George > From: users-list-request(a)monetdb.org > Subject: users-list Digest, Vol 3, Issue 4 > To: users-list(a)monetdb.org > Date: Mon, 5 Nov 2012 12:00:01 +0100 > > Send users-list mailing list submissions to > users-list(a)monetdb.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.monetdb.org/mailman/listinfo/users-list > or, via email, send a message with subject or body 'help' to > users-list-request(a)monetdb.org > > You can reach the person managing the list at > users-list-owner(a)monetdb.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of users-list digest..." > > > Today's Topics: > > 1. Re: set sql_debug in monetdb configuration file (Fabian Groffen) > 2. Re: Standard Deviation, Variance, and Quantile Functions > (Fabian Groffen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 5 Nov 2012 08:35:51 +0100 > From: Fabian Groffen <Fabian.Groffen(a)cwi.nl> > To: Communication channel for MonetDB users <users-list(a)monetdb.org> > Subject: Re: set sql_debug in monetdb configuration file > Message-ID: <20121105073551.GF49556(a)cwi.nl> > Content-Type: text/plain; charset="utf-8" > > On 04-11-2012 23:10:22 -0800, Liwen -George- Zhang wrote: > > Hi, > > I want to set?sql_debug=16384 for mserver5, where can i set this value? I > > can't find any documentation on where's the monetdb configuration file. > > Why would you want that? > > If you're sure you want so, it should be clear to you how to do that as > well. This is absolutely not a supported mode of operation. > > Fabian > _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

Monet DB release schedule for Oct2012-SP1 Release
by Ashish Kumar Singh 06 Nov '12

06 Nov '12

Dear List, Can anyone let me know when we are planning to release Oct2012-SP1 release of monetdb? Also is there any release schedule tracking page which can be referred for the same? Regards, Ashish _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

set sql_debug in monetdb configuration file
by Liwen -George- Zhang 05 Nov '12

05 Nov '12

Hi,I want to set sql_debug=16384 for mserver5, where can i set this value? I can't find any documentation on where's the monetdb configuration file.thanks,George _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

can monetdb run on ibm aix system?
by liangmeng 05 Nov '12

05 Nov '12

we have a ibm machine using aix system, can monetdb run on this system? _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

MonetDb Feedback/Memory question
by Eduardo Oliveira 04 Nov '12

04 Nov '12

I work for a company Adclick on Portugal, and we are trying MonetDb and benchmarking it. We are doing it at AWS (Amazon Web Services), that IO is very low, so we didn't expect great numbers, but we are very surprised great numbers appear. Now we will benchmark on server with SSD disks. I'm really enjoying MonetDb, *very good work *developing team. I think if MonetDb team work in replication master-slave, on real delete's! more rpm's for CentOS, AMI to Amazon Cloud, MonetDb can become real a top commercial product (i already tried so many). I have a question regarding memory: "MonetDB excessively uses main memory for processing, but does not require that all data fit in the available physical memory. To handle dataset that exceed the available physical memory, MonetDB does not (only) rely on the available swap space, but (also) uses memory-mapped files to exploit disk storage beyond the swap space as virtual memory." "For example, while bulk-loading data (preferably via a COPY INTO statements from a (possibly compressed) CSV file), MonetDB need to have all columns of the table that is currently being loaded "active", i.e., accessable in the address space. However, during loading, parts of the data are continuously written to the persisten files on disk, i.e., the whole table does not have to fit into main memory. E.g., loading a 100 GB table works fine on a system with 8 GB RAM and 16 GB swap -- provided there is sufficient free disk space." Bulk-loading is not a problem since we split CSV in chunks of 2-5M, but i'm more concern about queries, our datasize will be around 100-150GB ~1B rows and we are thinking on 32GB Memory server. I think 32GB memory will be more than enough for any query below: Our queries will be select ..., sum(...) where senddate>X and senddate<Y group by K, [Z] Or select ..., sum(...) where somecolumn = T and senddate>X and senddate<Y group by K, [Z] We will have just one table, and we will have some concurrency, not a lot, we expect 50-200 (depending on the time of day) queries per minute. So it can happen 3-5 queries at the same time. MonetDb will be able to handle this with 32GB of memory without swapping? I watch http://www.youtube.com/watch?v=yrLd-3lnZ58 and in our cause with our queries with senddate>X and senddate<Y it looks like that concurrent queries will not be able to share data between. Of course i will test concurrency before putting on production, but if i can get a rough answer will be great. Thanks a lot in advance. -- *Eduardo Oliveira * *IT* ***Email:* eduardo.oliveira(a)adclick.pt <nuno.morais(a)adclick.pt> *Web: * www.adclickint.com <http://www.adclickint.com/> * * <http://www.adclickint.com/> <http://www.adclickint.com/> _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

unexpected IDENT
by Marcelo Lacerda 04 Nov '12

04 Nov '12

Hey there, when I run this create table dim_date (id integer autoincrement primary key, date date unique not null); I get this syntax error, unexpected IDENT, expecting ')' or ',' in: "create table dim_date (id integer autoincrement" Is that expected? I'm running a compiled version of monet 11.13.3 on a debian machine. -- Marcelo Lacerda _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

Add, alter, delete user syntax
by Marcelo Lacerda 03 Nov '12

03 Nov '12

Greetings, where can I find the syntax for the database maintenance commands? Is there anything similar to the postgresql documentation[1]? -- Marcelo Lacerda [1] - http://www.postgresql.org/docs/9.2/static/sql-createuser.html _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 2

JDBC bug with limit and offset?
by Percy Wegmann 02 Nov '12

02 Nov '12

I'm running MonetDB on Ubuntu 10.04, with Monet built from the Oct2012_release <http://dev.monetdb.org/hg/MonetDB/rev/3c157ea4be53> tag. I have a client program that connects using the JDBC driver and issues a simple SQL query using limit and offset. I see that: - limit and offset work when using literal parameters in the SQL string - limit works by itself when using a bind parameter - offset works by itself when using a bind parameter - when specifying both limit and offset and using a bind parameter for either or both, the merovingian segfaults with a message like this: database 'click' (2428) was killed by signal SIGSEGV Examples of queries that work: SELECT * FROM the_table LIMIT 5 OFFSET 100; SELECT * FROM the_table LIMIT ?; SELECT * FROM the_table OFFSET ?; Example of queries that don't work: SELECT * FROM the_table LIMIT ? OFFSET ?; SELECT * FROM the_table LIMIT 5 OFFSET ?; SELECT * FROM the_table LIMIT ? OFFSET 100; I've tried passing in the limit and offset as 64 bit integers (long), 32 bit integers (int) and strings, and none of these work. I also tried downgrading to MonetDB Database Server v1.6 (Jul2012-SP2) but had the same issue. Has anyone else run into this? Is this a new bug that I should file? Thanks, Percy Wegmann _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 5

Arrows in the sql command line
by Masood Mortazavi 30 Oct '12

30 Oct '12

For some reason, when I use > mclient -u voc -d voc going into the sql command interface, I am unable to recall earlier sql commands using the arrow keys on the keyboard. Some other friends and colleagues can do this. What gives? Regards, Masood _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 2

persistent MAL function
by Liwen -George- Zhang 30 Oct '12

30 Oct '12

Hi,A user MAL function created in one connection is destroyed when logoff. What's the correct way to persistent it? I finally want to create a SQL function based on this MAL function.For example: msql>function user.malhistogram(db:str,tablename:str, columnname:str):bat[:any_1,:int]; X_2 := sql.mvc(); X_3 := sql.bind(X_2,db,tablename,columnname,0); return aggr.histogram(X_3); end malhistogram; msql>h := malhistogram("voc","voyages","trip"); msql>io.print(h); #-----------------# # h t # name # int int # type #-----------------# [ 1, 3038 ] [ 2, 1907 ] [ 3, 1288 ] [ 4, 852 ] ... thanks a lot. George Zhang _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 0

#GDKrealloc(21474836496) fails when try TCP-H benchmark with scale factor 100 on 64 bit ubuntun
by joe cooper 29 Oct '12

29 Oct '12

Hi, I got #GDKrealloc(21474836496) fails error when I tried to run TPC-H benchmark with a scale factor 100. The error happened during loading tables. Here are information about my configuration: The monetdb version used: changeset: 45737:bfd558546498 tag: tip user: Martin Kersten <mk(a)cwi.nl> date: Thu Oct 25 21:55:38 2012 +0200 summary: Add missing variable. The machine used: 64 bit Ubuntu natty With 7.806 GiB available main-memory. Compiler option used: 64 bit OIDs used Runtime options used: /home/borgdb/monetdb/install/bin/mserver5 --set gdk_dbfarm=/home/borgdb/monetdb/dbfarm --dbname=tpch100 --set merovingian_uri=mapi:monetdb://sc-borgdb6:50000/tpch100 --set mapi_open=false --set mapi_port=0 --set mapi_usock=/home/borgdb/monetdb/dbfarm/tpch100/.mapi.sock --set monet_vault_key=/home/borgdb/monetdb/dbfarm/tpch100/.vaultkey --set gdk_nr_threads=8 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes I am new to monetdb, so I am not sure if that is a known issue. If it is a known issue, my question is: on a 64 bit machine with 7.8GiB memory, how big a scale factor(TPC-H benchmark) can be handled by monetdb with 64 bit OID? If there any runtime option that enables monetdb to handle a big scale factor when run TPC-H benchmark? On my configuration, I succeeded in running TPC-H with scale factor 10, but failed with every scale factor >= 15. Any comments will be greatly appreciated, Thanks, Joe _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

Funnel deployment
by Tapomay Dey 25 Oct '12

25 Oct '12

Do the funnel/"monetdb discover" features rely on UDP broadcast. I see there is no option to specify IP address-port while configuring a funnel. Also UDP broadcast is not so conducive to security in networks with large number of nodes. Is there any way discover and funnel features would work if there are VLANs on the switches that prevent UDP discovery. Regards, Tapomay. _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 2

log file not found after a crash
by Medha Atre 23 Oct '12

23 Oct '12

Hi, I am running MonetDB v. 11.9.7. I have a large RDF dataset loaded in it (800+ million triples) as separate predicate tables for each unique predicate. I am running some simple one join SPAQRL queries ("?s :p1 ?o JOIN ?o :p2 ?x" kind) in bulk through a shell script (echo "<some query>" | mclient -drdf -lsql >> results). Sometime overnight when the queries were running, an error occurred in the database run, and it crashed by spitting out messages "monetdbd: an internal error has occurred, refer to the logs for details, please try again later" and "monetdbd: internal error while starting mserver, please refer to the logs" for the rest of the queries after some query caused this error. But when I tried to open "<Path To MonetDB installation>/var/log/monetdb/merovingian.log", it said "no such file or directory". I restarted the server and the particular database. It shows me its status as "health 97%" and "crash <crash date and time>". I tried to find the logfile again, but it's not there. I am wondering how I can know what the problem was. _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

5 10

Re: PHP Connectivity
by Jeremy O'Sullivan 23 Oct '12

23 Oct '12

Hi Fabian, I changed the version of PHP from 5.4.4 to 5.2.17 and it worked. Thanks, Jeremy _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 0

MAPI - check if connection is usable
by Tapomay Dey 23 Oct '12

23 Oct '12

I am using MAPI C library to talk to multiple monetdb databases. I cache the connection (struct mapi) to reduce overhead. However if a database/machine restarts then the connection is not usable. How do I determine if a cached connection is usable before actually using it. I have tried mapi_is_connected() and mapi_ping(). But mapi_ping always returns 0 while mapi_is_connected always returns 1. Thansk and Regards, Tapomay. _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

PHP Connectivity
by Jeremy O'Sullivan 23 Oct '12

23 Oct '12

Hello, I have some issues connecting to monetDB, using PHP, see below. ==== <?php require '/usr/local/monetdb/share/php/monetdb/php_monetdb.php'; $db = monetdb_connect("sql", "localhost", 50000, "monetdb", "monetdb", "wifi_db"); $result = monetdb_query('SELECT count(*) FROM Summary_Stats'); ?> ==== I get the following error message in the browser: Fatal error: Call-time pass-by-reference has been removed in /usr/local/monetdb/share/php/monetdb/php_monetdb.php on line 302 Has anyone seen this error ? Regards, Jeremy _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

how to load a table in MAL client
by Liwen -George- Zhang 23 Oct '12

23 Oct '12

Hi, When using monetdb, one questions that I need your suggestions is how to load a table column to MAL client and manipulate it.For example,sql>create table gzhang_test (intcol1 int,varcharcol1 varchar(50));sql>insert into gzhang_test values (1,'value1'); sql>insert into gzhang_test values (2,'value2');I know how to load a BAT by name in MAL, but for this table, I don't know how to get the name.If I do:mal>X_3 := sql.mvc();mal>X_4:bat[:oid,:int] := sql.bind(X_3,"midas","gzhang_test","intcol1",0); mal>io.print(X_4);I will get ERROR = !SQLException:mvc:SQL module not initialized. Should I load the SQL module in a MAL session, what's the correct way to get the column if not? Thanks,George Zhang _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

How accurate and updated is the comparison: MonetDB-vs-PostgreSQL?
by Yinhe Cao 23 Oct '12

23 Oct '12

Hi, Recently I came across the following comparison: http://database-management-systems.findthebest.com/compare/28-43/MonetDB-vs… But I did not find out which version of MonetDB is used in the comparison. It seems to me that a good fraction of features listed there as unsupported are actually supported in MonetDB5. Any comments on the comparison? Thanks, Yinhe ________________________________ 华为技术有限公司 Huawei Technologies Co., Ltd. [Company_logo] Phone: Fax: Mobile: Email: 地址：深圳市龙岗区坂田华为基地邮编：518129 Huawei Technologies Co., Ltd. Bantian, Longgang District,Shenzhen 518129, P.R.China http://www.huawei.com ________________________________ 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！ This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 2

Re: users-list Digest, Vol 2, Issue 17
by Masood Mortazavi 22 Oct '12

22 Oct '12

If you're building on Unix flavors (Mac OS-X, Linux and any Unix, which I've tried), I think HowToStart.rst provides good information regarding the default settings. The sql front end is already enabled by default, as far as I can tell. I built with the default configuration settings (on Unix-based systems), and was able to run the sql front end and use it. Most sql I've written so far against the test database seem to work, and the explain command is fantastic, and now I would like to learn more about the internals. (VOC database here: http://www.monetdb.org/Downloads/Tutorial) Most significant issue to which I ran in building MonetDB (from a clone of its mercurial repository) on Unix flabors was ensuring that the right libraries were generally not already installed or only partially installed. On Mac OS-X, one uses MacPorts. On Linux/Debian, apt-get worked fine. It is time-consuming to install all the needed libraries on a brand-new, clean system. On Mac OS-X, I also had to change a symbolic link to a library because the library had two instances and the build system was picking it up from a place where the instance was compiled for the wrong architecture (under Lion). The "otool" command was useful in determining the architecture of the libraries on Mac, e.g. otool -fv /usr/lib/libiconv.dylib Best regards, Masood Message: 1 > Date: Sun, 21 Oct 2012 09:36:36 -0400 > From: Medha Atre <medha.atre(a)gmail.com> > To: Communication channel for MonetDB users <users-list(a)monetdb.org> > Subject: --enable-sql option at the time of compilation > Message-ID: > < > CAPsfZ1Tb7BioyJVrdsBx4V6G2iBM-UPRZmMCMLMOpPCCRi4wpg(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi, > > Is it necessary to give --enable-sql option at the time of compilation > if one wants to use SQL as the query language or does it have some > other connotation? The reason for asking is, if I give --enable-sql > option, the configure script compels me to give --enable-monetdb5 > option too. > > I am not sure how these options make difference internally to the > MonetDB server, since as per the MonetDB website SQL is the de facto > language for querying DBs and that is what is used by MonetDB as well. > > Can someone please enlighten? > > Thanks. > Medha > > _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 0

--enable-sql option at the time of compilation
by Medha Atre 21 Oct '12

21 Oct '12

Hi, Is it necessary to give --enable-sql option at the time of compilation if one wants to use SQL as the query language or does it have some other connotation? The reason for asking is, if I give --enable-sql option, the configure script compels me to give --enable-monetdb5 option too. I am not sure how these options make difference internally to the MonetDB server, since as per the MonetDB website SQL is the de facto language for querying DBs and that is what is used by MonetDB as well. Can someone please enlighten? Thanks. Medha _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 3

Re: Improving performance of "select * from table" ?
by Stefan Manegold 17 Oct '12

17 Oct '12

Hi Gordon, indeed, your experiments confirm that most of the time is spent in serializing, sending, and re-parsing your queries huge result. I am wondering what kind of application needs to see the entire database table? No user can seriously handle millions of result tuples with tens (or more) of columns? What is the purpose of using a DBMS if all it needs to do is select * from table ? In my/our opinion, as much as possible of the application logic should be expressed in SQL (plus domain-/application specific extension, if required) and (thus) performed in the DBMS, resulting in only small results that need to be sent back to the client/application. Then the efficiency and performance of the DBMS (server) itself is dominating and more important than the server-client communication. Best, Stefan Assaf Gordon <gordon(a)cshl.edu> wrote: Hello Stefan, > Stefan de Konink wrote, On 10/16/2012 06:49 PM: >> [...] >> What about: the time taken to serialise the results? For MonetDB this is done in a very 'plain text' wire-format. >> [...] >> Are you aware of the PostgreSQL \timing command? In that way you can see outputs similar to that of MonetDB with respect of time taken for a query. > I re-run one test using psql's and mclient's internal timing. === ## Postgres: Select all columns from table $ psql test test=# \o /dev/null test=# \timing Timing is on. test=# select * from bc251; Time: 5506.768 ms test=# select * from bc251; Time: 5446.689 ms test=# ## MonetDB: Select all columns from table $ mclient -d voc sql>\>/dev/null sql>\w-1 sql>select * from bc251; 1657032 tuples (3.8s) sql>select * from bc251; 1657032 tuples (3.8s) sql> === As you said, the reported durations are much shorter than in my previous timings (monetDb: 3.8s vs 2m16s, postgres 5.5s vs 21s). However, those numbers don't reveal the entire story: mclient reports 3.8 seconds, but it took more than 2 minutes (of wall time) for the result message to be printed. I understand that this quite possibly indicates a serialization/transfer bottle-neck, and it could be of lesser interest to the developers, but as an application developer I worry about the end-to-end timing of the query - the time it takes for my application to get the data back. If there are any recommendation on improving those queries, it would be much appreciated. Thanks, -gordon _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 4

RE: problem with monetdb functionality
by Stefan Manegold 17 Oct '12

17 Oct '12

Shajon, 1. Do you have any evidence in terms of experiments that shows that MonetDB is slow(er) due to not allowing to set multiple variables in a select clause? Can you give example queries and their performance? 2. >From you rather short description, we cannot say much about this. Beware that your systems state may have a significant influence on performance, e.g., - for point (single value select) predicates, the first query builds a has table, while subsequent queries benefit from this hash table; - the first query needs to load the data from disk, while subsequent queries might benefit from (parts of) the data already/still being in memory; in MonetDB itself while the server is running, or in the OS's filesystem cache even after a server restart; - etc. Best, Stefan Shajon <alam(a)finEngine.com> wrote: From: Shajon [mailto:alam@finEngine.com] Sent: Tuesday, October 09, 2012 1:47 PM To: 'users-list(a)monetdb.org' Subject: FW: problem with monetdb functionality From: Shajon [mailto:alam@finEngine.com] Sent: Tuesday, October 09, 2012 12:49 PM To: 'info(a)monetdb.com' Subject: problem with monetdb functionality Hi, I am using monetdb to process millions of records. now I am getting two problem 1. I could not set multiple variable in select query in a function or procedure. For example: select @var1=col1, @var2=col2 from table_name. as like sql server or Sybase database. If I could do ,it would reduce considerable amount of time for some function execution. So do I need to write MAL or any other way? 2. Sometimes same query takes different time in different moment. For example a query at the starting time of server takes 2ms and 10 hours later it takes 14s. if I close & restart server & client its ok. Can anyone suggest me what can I do? Thanks Shajon _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 2

Improving performance of "select * from table" ?
by Assaf Gordon 17 Oct '12

17 Oct '12

Hello, I'm getting phenomenal performance with MonetDB with almost all of my query types, except one: The most basic "SELECT * FROM mytable WHERE (SOMETHING)" query takes much longer than other RDBMs (mysql, postgresql). Even "SELECT * FROM mytable LIMIT 10;" takes significantly more time than with other databases (and the more columns the table has, the more time it takes). I understand this is not the scenario that MonetDB was designed to address, but perhaps there's a way to improve it? (It's a requirement for my project to be able to export some/all of the data in a table.) Thanks, -gordon _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 5

Re: Improving performance of "select * from table" ?
by Stefan Manegold 17 Oct '12

17 Oct '12

Assaf, do you have a specific reason to use an arbitrary snapshot of the instable development branch of MonetDB? If not, I'd strongly recommend to use the latest Jun2012-SP2 release, respectively the Jun2012 release branch. We'd be curious to learn whether the latest release work better for your data & queries than the development branch. Best, Stefan Assaf Gordon <gordon(a)cshl.edu> wrote: Hello Jennie, Ying Zhang wrote, On 10/16/2012 04:46 PM: > > How many columns and rows does you table have? How many rows does the first query return? what are the execution times of this query on mysql, postgresql and monetdb, respectively? > Below are some test results. Both servers (postgres and mserver) and clients (psql and mclient) are running on the same machine, with 8 cores and 16GB of RAM. The machine was not overloaded during the tests. The databases are stored on the same disk. I've run each test (except 5) couple of times, and listed most common result (so it's not about caching). Using PostgreSQL 9.2.1 (compiled from source) and MonetDB v11.14.0/unreleased (compiled from source). I can provide more technical details if needed. Assuming the "user" time is the time "wasted" by the client program (psql/mclient), and assuming "sys" time is negligible, then subtracting the "user" time from the "real" time gives an indication of how much time the server took to complete the query and transfer the results. It seems in most of those queries, the MonetDB server takes longer than PostgreSQL to complete. One striking difference is test #6 that needs to return just one line: the execution time for MonetDB is 9 seconds - I guess accessing 138 columns takes its toll... ## ## First table (bc251): 1,657,032 rows, 13 columns ## ## MonetDB Table size sql>select "schema", "table", sum("size") as size from storage() group by "schema","table" having "table" = 'bc251' ; +--------+-------+-----------+ | schema | table | size | +========+=======+===========+ | sys | bc251 | 132775936 | +--------+-------+-----------+ ## PostgreSQL Table Sql test=# SELECT pg_size_pretty(pg_relation_size('bc251')); pg_size_pretty ---------------- 212 MB (1 row) ## Test 1: select ONE column ## MonethDB $ time mclient -d voc -s "select seq from bc251;" > /dev/null real 0m15.981s user 0m5.653s sys 0m0.106s ## PostgreSQL $ time echo "select seq from bc251" | psql test > /dev/null real 0m3.565s user 0m2.698s sys 0m0.154s ## Test 2: select ALL columns ## MonetDB $ time mclient -d voc -s "select * from bc251;" > /dev/null real 2m16.388s user 0m38.468s sys 0m0.448s ## PostgreSQL $ time echo "select * from bc251" | psql test > /dev/null real 0m21.771s user 0m17.045s sys 0m0.843s ## Test 3: Select ONE row ## MonetDB $ time mclient -d voc -s "select * from bc251 limit 1" > /dev/null real 0m0.053s user 0m0.003s sys 0m0.004s ## PostgreSQL $ time echo "select * from bc251 limit 1" | psql test > /dev/null real 0m0.072s user 0m0.013s sys 0m0.009s ## ## Second table (NR102): 3,042,983 rows, 138 columns ## ## MonetDB Table Size sql>select "schema", "table", sum("size") as size from storage() group by "schema","table" having "table" = 'nr102' ; +--------+-------+------------+ | schema | table | size | +========+=======+============+ | sys | nr102 | 1408630784 | +--------+-------+------------+ 1 tuple (5.567ms) ## PostgreSQL Table Size test=# SELECT pg_size_pretty(pg_relation_size('NR102')); pg_size_pretty ---------------- 1850 MB (1 row) ## Test 4: Select ONE column ## MonetDB $ time mclient -d voc -s "select seq from NR102;" > /dev/null real 0m29.882s user 0m7.574s sys 0m0.107s ## PostgreSQL $ time echo "select seq from NR102" | psql test > /dev/null real 0m6.925s user 0m4.906s sys 0m0.268s ## Test 5: Select ALL columns ## MonetDB $ time mclient -d voc -s "select * from NR102;" > /dev/null real 39m58.618s user 10m9.066s sys 0m4.468s ## PostgreSQL $ time echo "select * from NR102" | psql test > /dev/null real 4m0.840s user 3m20.866s sys 0m12.592s ## Test 6: Select ONE row ## MonetDB $ time mclient -d voc -s "select * from NR102 limit 1" > /dev/null real 0m9.055s user 0m0.004s sys 0m0.008s ## PostgreSQL $ time echo "select * from NR102 limit 1" | psql test > /dev/null real 0m0.160s user 0m0.016s sys 0m0.006s _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

How to enable Datacell?
by Chang Ge 16 Oct '12

16 Oct '12

Hi, I am using MonetDB 11.11.11, and I am very interested in the data cell externsion. I followed the doc (http://www.monetdb.org/Documentation/Extensions/Streams) but at the first step when I tried to set datacell optimizer, it said sql>set optimizer='datacell_pipe'; SyntaxException:parseError: ';' expected Syntax error detected.See documentation for details Does anyone know how to use datacell? Thanks very much! Best regards, Chang _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

Confusion about concurrency with regards to DDL and Insert Into / Select From
by Percy Wegmann 14 Oct '12

14 Oct '12

I'm very new to MonetDB and am just starting to play around with it. One of the things I'm trying to get my head around is the concurrency model. I've observed some things that make sense and others that I don't understand. 1. Concurrent COPY commands into the same table will cause one or the other to roll back. This makes sense as MonetDB seems to lock at the table level. 2. SELECTing data from a table that concurrently has a COPY command running against it doesn't seem to produce any concurrency errors 3. However, if I INSERT INTO table_B (SELECT ... FROM table_A) while a COPY command is running against table_A, I do get concurrency conflicts 4. Also, if I have a COPY command running into table_A and concurrently issue DDL creating a new table_B, I get a concurrency conflict as well Observations 3+4 seem to indicate that DDL operations and INSERT ... SELECT FROM ... use some sort of database-wide lock. This begs the following questions: a) Is there in fact database-wide locking going on here? b) Is there a workaround that would allow me to issue DDL and make also internal copies of tables while concurrently loading data into other tables? c) Is there something fundamental about the architecture of the database that requires database-wide locking for these ops or is this just a detail of the current implementation that could potentially be ironed out? Thanks! Percy _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 2

invalid tuple received from server, got 138 columns, expected 476, ignoring
by Anthony Damico 13 Oct '12

13 Oct '12

Hi everyone, I just wanted to follow-up on a previous post (available at http://mail.monetdb.org/pipermail/users-list/2012-September/005773.html) about an odd 'invalid tuple received' problem with a bit more detail and a simplified way to replicate everything. I've attached the results of PLAN and EXPLAIN in case that's of any value. The behavior of MonetDB seems strange, since I am able to select count(*) from table; and select every individual column from the table, but not select * from table; I am using the alaska household file from the 2010 american community survey. This file can be downloaded from: http://www2.census.gov/acs2010_1yr/pums/csv_hak.zip Out of all of the commands posted below, only sql>select * from household limit 5 ; gives an error. It says: invalid tuple received from server, got 138 columns, expected 202, ignoring I assume this is a windows-related problem? I am using this in windows 7, x64. Any help would be appreciated! Thanks!!! Here are my SQL commands verbatim: drop table household; create table household ( RT VARCHAR(255), SERIALNO INT, DIVISION INT, PUMA INT, REGION INT, ST INT, ADJHSG INT, ADJINC INT, WGTP INT, NP INT, ZZZZ INT, ACR INT, AGS INT, BATH INT, BDSP INT, BLD INT, BUS INT, CONP INT, ELEP INT, FS INT, FULP INT, GASP INT, HFL INT, INSP INT, MHP INT, MRGI INT, MRGP INT, MRGT INT, MRGX INT, REFR INT, RMSP INT, RNTM INT, RNTP INT, RWAT INT, SINK INT, SMP INT, STOV INT, TEL INT, TEN INT, TOIL INT, VACS INT, VALP INT, VEH INT, WATP INT, YBL INT, FES INT, FINCP INT, FPARC INT, GRNTP INT, GRPIP INT, HHL INT, HHT INT, HINCP INT, HUGCL INT, HUPAC INT, HUPAOC INT, HUPARC INT, KIT INT, LNGI INT, MULTG INT, MV INT, NOC INT, NPF INT, NPP INT, NR INT, NRC INT, OCPIP INT, PARTNER INT, PLM INT, PSF INT, R18 INT, R60 INT, R65 INT, RESMODE INT, SMOCP INT, SMX INT, SRNT INT, SVAL INT, TAXP INT, WIF INT, WKEXREL INT, WORKSTAT INT, FACRP INT, FAGSP INT, FBATHP INT, FBDSP INT, FBLDP INT, FBUSP INT, FCONP INT, FELEP INT, FFSP INT, FFULP INT, FGASP INT, FHFLP INT, FINSP INT, FKITP INT, FMHP INT, FMRGIP INT, FMRGP INT, FMRGTP INT, FMRGXP INT, FMVP INT, FPLMP INT, FREFRP INT, FRMSP INT, FRNTMP INT, FRNTP INT, FRWATP INT, FSINKP INT, FSMP INT, FSMXHP INT, FSMXSP INT, FSTOVP INT, FTAXP INT, FTELP INT, FTENP INT, FTOILP INT, FVACSP INT, FVALP INT, FVEHP INT, FWATP INT, FYBLP INT, wgtp1 INT, wgtp2 INT, wgtp3 INT, wgtp4 INT, wgtp5 INT, wgtp6 INT, wgtp7 INT, wgtp8 INT, wgtp9 INT, wgtp10 INT, wgtp11 INT, wgtp12 INT, wgtp13 INT, wgtp14 INT, wgtp15 INT, wgtp16 INT, wgtp17 INT, wgtp18 INT, wgtp19 INT, wgtp20 INT, wgtp21 INT, wgtp22 INT, wgtp23 INT, wgtp24 INT, wgtp25 INT, wgtp26 INT, wgtp27 INT, wgtp28 INT, wgtp29 INT, wgtp30 INT, wgtp31 INT, wgtp32 INT, wgtp33 INT, wgtp34 INT, wgtp35 INT, wgtp36 INT, wgtp37 INT, wgtp38 INT, wgtp39 INT, wgtp40 INT, wgtp41 INT, wgtp42 INT, wgtp43 INT, wgtp44 INT, wgtp45 INT, wgtp46 INT, wgtp47 INT, wgtp48 INT, wgtp49 INT, wgtp50 INT, wgtp51 INT, wgtp52 INT, wgtp53 INT, wgtp54 INT, wgtp55 INT, wgtp56 INT, wgtp57 INT, wgtp58 INT, wgtp59 INT, wgtp60 INT, wgtp61 INT, wgtp62 INT, wgtp63 INT, wgtp64 INT, wgtp65 INT, wgtp66 INT, wgtp67 INT, wgtp68 INT, wgtp69 INT, wgtp70 INT, wgtp71 INT, wgtp72 INT, wgtp73 INT, wgtp74 INT, wgtp75 INT, wgtp76 INT, wgtp77 INT, wgtp78 INT, wgtp79 INT, wgtp80 INT ); copy 5000 offset 2 records into household from 'C:\Users\AnthonyD\Desktop\ss10hak.csv' using delimiters ',','\n','"' NULL as '' ; \w-1 select count(*) from household; select * from household limit 5 ; PLAN select * from household limit 5 ; EXPLAIN select * from household limit 5 ; select RT, SERIALNO, DIVISION, PUMA, REGION, ST, ADJHSG, ADJINC, WGTP, NP, ZZZZ, ACR, AGS, BATH, BDSP, BLD, BUS, CONP, ELEP, FS, FULP, GASP, HFL, INSP, MHP, MRGI, MRGP, MRGT, MRGX, REFR, RMSP, RNTM, RNTP, RWAT, SINK, SMP, STOV, TEL, TEN, TOIL, VACS, VALP, VEH, WATP, YBL, FES, FINCP, FPARC, GRNTP, GRPIP, HHL, HHT, HINCP, HUGCL, HUPAC, HUPAOC, HUPARC, KIT, LNGI, MULTG, MV, NOC, NPF, NPP, NR, NRC, OCPIP, PARTNER, PLM, PSF, R18, R60, R65, RESMODE, SMOCP, SMX, SRNT, SVAL, TAXP, WIF, WKEXREL, WORKSTAT, FACRP, FAGSP, FBATHP, FBDSP, FBLDP, FBUSP, FCONP, FELEP, FFSP, FFULP, FGASP, FHFLP, FINSP, FKITP, FMHP, FMRGIP, FMRGP, FMRGTP, FMRGXP, FMVP, FPLMP, FREFRP, FRMSP, FRNTMP, FRNTP, FRWATP, FSINKP, FSMP, FSMXHP, FSMXSP, FSTOVP, FTAXP, FTELP, FTENP, FTOILP, FVACSP, FVALP, FVEHP, FWATP, FYBLP, wgtp1, wgtp2, wgtp3, wgtp4, wgtp5, wgtp6, wgtp7, wgtp8, wgtp9, wgtp10, wgtp11, wgtp12, wgtp13, wgtp14, wgtp15, wgtp16, wgtp17, wgtp18, wgtp19, wgtp20, wgtp21, wgtp22, wgtp23, wgtp24, wgtp25, wgtp26, wgtp27, wgtp28, wgtp29, wgtp30, wgtp31, wgtp32, wgtp33, wgtp34, wgtp35, wgtp36, wgtp37, wgtp38, wgtp39, wgtp40, wgtp41, wgtp42, wgtp43, wgtp44, wgtp45, wgtp46, wgtp47, wgtp48, wgtp49, wgtp50, wgtp51, wgtp52, wgtp53, wgtp54, wgtp55, wgtp56, wgtp57, wgtp58, wgtp59, wgtp60, wgtp61, wgtp62, wgtp63, wgtp64, wgtp65, wgtp66, wgtp67, wgtp68, wgtp69, wgtp70, wgtp71, wgtp72, wgtp73, wgtp74, wgtp75, wgtp76, wgtp77, wgtp78, wgtp79, wgtp80 from household limit 5; select RT, SERIALNO, DIVISION, PUMA, REGION, ST, ADJHSG, ADJINC, WGTP, NP, ZZZZ, ACR, AGS, BATH, BDSP, BLD, BUS, CONP, ELEP, FS, FULP, GASP, HFL, INSP, MHP, MRGI, MRGP, MRGT, MRGX, REFR, RMSP, RNTM, RNTP, RWAT, SINK, SMP, STOV, TEL, TEN, TOIL, VACS, VALP, VEH, WATP, YBL, FES, FINCP, FPARC, GRNTP, GRPIP, HHL, HHT, HINCP, HUGCL, HUPAC, HUPAOC, HUPARC, KIT, LNGI, MULTG, MV, NOC, NPF, NPP, NR, NRC, OCPIP, PARTNER, PLM, PSF, R18, R60, R65, RESMODE, SMOCP, SMX, SRNT, SVAL, TAXP, WIF, WKEXREL, WORKSTAT, FACRP, FAGSP, FBATHP, FBDSP, FBLDP, FBUSP, FCONP, FELEP, FFSP, FFULP, FGASP, FHFLP, FINSP, FKITP, FMHP, FMRGIP, FMRGP, FMRGTP, FMRGXP, FMVP, FPLMP, FREFRP, FRMSP, FRNTMP, FRNTP, FRWATP, FSINKP, FSMP, FSMXHP, FSMXSP, FSTOVP, FTAXP, FTELP, FTENP, FTOILP, FVACSP, FVALP, FVEHP, FWATP, FYBLP from household limit 5; select wgtp1, wgtp2, wgtp3, wgtp4, wgtp5, wgtp6, wgtp7, wgtp8, wgtp9, wgtp10, wgtp11, wgtp12, wgtp13, wgtp14, wgtp15, wgtp16, wgtp17, wgtp18, wgtp19, wgtp20, wgtp21, wgtp22, wgtp23, wgtp24, wgtp25, wgtp26, wgtp27, wgtp28, wgtp29, wgtp30, wgtp31, wgtp32, wgtp33, wgtp34, wgtp35, wgtp36, wgtp37, wgtp38, wgtp39, wgtp40, wgtp41, wgtp42, wgtp43, wgtp44, wgtp45, wgtp46, wgtp47, wgtp48, wgtp49, wgtp50, wgtp51, wgtp52, wgtp53, wgtp54, wgtp55, wgtp56, wgtp57, wgtp58, wgtp59, wgtp60, wgtp61, wgtp62, wgtp63, wgtp64, wgtp65, wgtp66, wgtp67, wgtp68, wgtp69, wgtp70, wgtp71, wgtp72, wgtp73, wgtp74, wgtp75, wgtp76, wgtp77, wgtp78, wgtp79, wgtp80 from household limit 5; Here's the output of PLAN and EXPLAIN: operation successful (62.733ms) operation successful (88.682ms) 3335 affected rows (21.1s) +------+ | L1 | +======+ | 3335 | +------+ +------+----------+----------+------+--------+------+---------+---------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+--------+------+------+------+------+-------+-------+-------+-------+------+------+-------+-------+-------+--------+--------+------+------+-------+------+------+------+------+------+------+-------+---------+------+------+------+------+------+---------+-------+------+------+------+------+------+---------+----------+-------+-------+--------+-------+-------+-------+-------+-------+------+-------+-------+-------+-------+-------+------+--------+-------+--------+--------+------+-------+--------+-------+--------+-------+--------+--------+------+--------+--------+--------+-------+-------+-------+--------+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+ | rt | serialno | division | puma | region | st | adjhsg | adjinc | wgtp | np | zzzz | acr | ags | bath | bdsp | bld | bus | conp | elep | fs | fulp | gasp | hfl | insp | mhp | mrgi | mrgp | mrgt | mrgx | refr | rmsp | rntm | rntp | rwat | sink | smp | stov | tel | ten | toil | vacs | valp | veh | watp | ybl | fes | fincp | fparc | grntp | grpip | hhl | hht | hincp | hugcl | hupac | hupaoc | huparc | kit | lngi | multg | mv | noc | npf | npp | nr | nrc | ocpip | partner | plm | psf | r18 | r60 | r65 | resmode | smocp | smx | srnt | sval | taxp | wif | wkexrel | workstat | facrp | fagsp | fbathp | fbdsp | fbldp | fbusp | fconp | felep | ffsp | ffulp | fgasp | fhflp | finsp | fkitp | fmhp | fmrgip | fmrgp | fmrgtp | fmrgxp | fmvp | fplmp | frefrp | frmsp | frntmp | frntp | frwatp | fsinkp | fsmp | fsmxhp | fsmxsp | fstovp | ftaxp | ftelp | ftenp | ftoilp | fvacsp | fvalp | fvehp | fwatp | fyblp | wgtp1 | wgtp2 | wgtp3 | wgtp4 | wgtp5 | wgtp6 | wgtp7 | wgtp8 | wgtp9 | wgtp10 | wgtp11 | wgtp12 | wgtp13 | wgtp14 | wgtp15 | wgtp16 | wgtp17 | wgtp18 | wgtp19 | wgtp20 | wgtp21 | wgtp22 | wgtp23 | wgtp24 | wgtp25 | wgtp26 | wgtp27 | wgtp28 | wgtp29 | wgtp30 | wgtp31 | wgtp32 | wgtp33 | wgtp34 | wgtp35 | wgtp36 | wgtp37 | wgtp38 | wgtp39 | wgtp40 | wgtp41 | wgtp42 | wgtp43 | wgtp44 | wgtp45 | wgtp46 | wgtp47 | wgtp48 | wgtp49 | wgtp50 | wgtp51 | wgtp52 | wgtp53 | wgtp54 | wgtp55 | wgtp56 | wgtp57 | wgtp58 | wgtp59 | wgtp60 | wgtp61 | wgtp62 | wgtp63 | wgtp64 | wgtp65 | wgtp66 | wgtp67 | wgtp68 | wgtp69 | wgtp70 | wgtp71 | wgtp72 | wgtp73 | wgtp74 | wgtp75 | wgtp76 | wgtp77 | wgtp78 | wgtp79 | wgtp80 | +======+==========+==========+======+========+======+=========+=========+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+========+======+======+======+======+=======+=======+=======+=======+======+======+=======+=======+=======+========+========+======+======+=======+======+======+======+======+======+======+=======+=========+======+======+======+======+======+=========+=======+======+======+======+======+======+=========+==========+=======+=======+========+=======+=======+=======+=======+=======+======+=======+=======+=======+=======+=======+======+========+=======+========+========+======+=======+========+=======+========+=======+========+========+======+========+========+========+=======+=======+=======+========+========+=======+=======+=======+=======+=======+=======+=======+=======+=======+=======+=======+=======+=======+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+ | H | 1890 | 9 | 400 | 4 | 2 | 1000000 | 1007624 | 46 | 2 | 1 | null | null | 1 | 1 | 6 | null | null | 1 | 2 | 1 | 3 | 4 | null | null | null | null | null | null | 1 | 2 | 2 | 600 | 1 | 1 | null | 1 | 1 | 3 | 1 | null | null | 1 | 1 | 3 | null | null | null | 600 | 21 | 1 | 7 | 34700 | 0 | 4 | 4 | 4 | 1 | 1 | 1 | 3 | 0 | null | 0 | 1 | 0 | null | 0 | 1 | 0 | 0 | 0 | 0 | 2 | null | null | 1 | 0 | null | null | null | null | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 10 | 16 | 10 | 42 | 61 | 44 | 54 | 45 | 71 | 67 | 112 | 50 | 15 | 41 | 111 | 79 | 37 | 67 | 38 | 40 | 81 | 95 | 70 | 81 | 51 | 40 | 38 | 47 | 15 | 22 | 18 | 34 | 95 | 55 | 14 | 51 | 48 | 18 | 43 | 12 | 7 | 13 | 15 | 57 | 72 | 55 | 48 | 50 | 75 | 80 | 116 | 51 | 14 | 38 | 126 | 57 | 30 | 93 | 29 | 53 | 80 | 55 | 71 | 46 | 38 | 57 | 39 | 47 | 16 | 16 | 20 | 50 | 91 | 58 | 20 | 72 | 43 | 11 | 48 | 9 | | H | 2029 | 9 | 101 | 4 | 2 | 1000000 | 1007624 | 269 | 4 | 1 | 1 | null | 1 | 4 | 2 | 2 | null | 80 | 2 | 2 | 80 | 1 | 1500 | null | 1 | 920 | 1 | 1 | 1 | 7 | null | null | 1 | 1 | null | 1 | 1 | 1 | 1 | null | 200000 | 1 | 200 | 4 | 8 | 47100 | 2 | null | null | 1 | 3 | 47100 | 1 | 2 | 4 | 2 | 1 | 1 | 2 | 7 | 0 | 4 | 0 | 0 | 2 | 28 | 0 | 1 | 1 | 1 | 1 | 1 | 2 | 1097 | 3 | 0 | 1 | 34 | 1 | 15 | 15 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 252 | 470 | 264 | 430 | 228 | 243 | 192 | 107 | 265 | 79 | 266 | 268 | 68 | 335 | 503 | 116 | 95 | 389 | 228 | 114 | 254 | 71 | 225 | 116 | 289 | 291 | 233 | 539 | 310 | 423 | 262 | 346 | 511 | 235 | 79 | 407 | 420 | 121 | 223 | 90 | 250 | 70 | 240 | 101 | 259 | 326 | 245 | 461 | 241 | 480 | 315 | 275 | 286 | 338 | 118 | 363 | 409 | 87 | 238 | 418 | 278 | 322 | 297 | 486 | 376 | 262 | 198 | 95 | 259 | 104 | 238 | 309 | 135 | 230 | 408 | 117 | 83 | 497 | 244 | 418 | +------+----------+----------+------+--------+------+---------+---------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+--------+------+------+------+------+-------+-------+-------+-------+------+------+-------+-------+-------+--------+--------+------+------+-------+------+------+------+------+------+------+-------+---------+------+------+------+------+------+---------+-------+------+------+------+------+------+---------+----------+-------+-------+--------+-------+-------+-------+-------+-------+------+-------+-------+-------+-------+-------+------+--------+-------+--------+--------+------+-------+--------+-------+--------+-------+--------+--------+------+--------+--------+--------+-------+-------+-------+--------+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+ +-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | rel | +=========================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================+ | top N ( | | | project ( | | | | table(sys.household) [ household.rt, household.serialno, household.division, household.puma, household.region, household.st, household.adjhsg, household.adjinc, household.wgtp, household.np, household.zzzz, household.acr, household.ags, household.bath, household.bdsp, household.bld, household.bus, household.conp, household.elep, household.fs, household.fulp, household.gasp, household.hfl, household.insp, household.mhp, household.mrgi, household.mrgp, household.mrgt, household.mrgx, household.refr, household.rmsp, household.rntm, household.rntp, household.rwat, household.sink, household.smp, household.stov, household.tel, household.ten, household.toil, household.vacs, household.valp, household.veh, household.watp, household.ybl, household.fes, household.fincp, household.fparc, household.grntp, household.grpip, household.hhl, household.hht, household.hincp, household.hugcl, household.hupac, household.hupaoc, household.huparc, household.kit, household.lngi, household.multg, household.mv, household.noc, household.npf, household.npp, household.nr, household.nrc, household.ocpip, household.partner, household.plm, household.psf, household.r18, household.r60, household.r65, household.resmode, household.smocp, household.smx, household.srnt, household.sval, household.taxp, household.wif, household.wkexrel, household.workstat, household.facrp, household.fagsp, household.fbathp, household.fbdsp, household.fbldp, household.fbusp, household.fconp, household.felep, household.ffsp, household.ffulp, household.fgasp, household.fhflp, household.finsp, household.fkitp, household.fmhp, household.fmrgip, household.fmrgp, household.fmrgtp, household.fmrgxp, household.fmvp, household.fplmp, household.frefrp, household.frmsp, household.frntmp, household.frntp, household.frwatp, household.fsinkp, household.fsmp, household.fsmxhp, household.fsmxsp, household.fstovp, household.ftaxp, household.ftelp, household.ftenp, household.ftoilp, household.fvacsp, household.fvalp, household.fvehp, household.fwatp, household.fyblp, household.wgtp1, household.wgtp2, household.wgtp3, household.wgtp4, household.wgtp5, household.wgtp6, household.wgtp7, household.wgtp8, household.wgtp9, household.wgtp10, household.wgtp11, household.wgtp12, household.wgtp13, household.wgtp14, household.wgtp15, household.wgtp16, household.wgtp17, household.wgtp18, household.wgtp19, household.wgtp20, household.wgtp21, household.wgtp22, household.wgtp23, household.wgtp24, household.wgtp25, household.wgtp26, household.wgtp27, household.wgtp28, household.wgtp29, household.wgtp30, household.wgtp31, household.wgtp32, household.wgtp33, household.wgtp34, household.wgtp35, household.wgtp36, household.wgtp37, household.wgtp38, household.wgtp39, household.wgtp40, household.wgtp41, household.wgtp42, household.wgtp43, household.wgtp44, household.wgtp45, household.wgtp46, household.wgtp47, household.wgtp48, household.wgtp49, household.wgtp50, household.wgtp51, household.wgtp52, household.wgtp53, household.wgtp54, household.wgtp55, household.wgtp56, household.wgtp57, household.wgtp58, household.wgtp59, household.wgtp60, household.wgtp61, household.wgtp62, household.wgtp63, household.wgtp64, household.wgtp65, household.wgtp66, household.wgtp67, household.wgtp68, household.wgtp69, household.wgtp70, household.wgtp71, household.wgtp72, household.wgtp73, household.wgtp74, household.wgtp75, household.wgtp76, household.wgtp77, household.wgtp78, household.wgtp79, household.wgtp80, household.%TID% NOT NULL ] COUNT | | | ) [ household.rt, household.serialno, household.division, household.puma, household.region, household.st, household.adjhsg, household.adjinc, household.wgtp, household.np, household.zzzz, household.acr, household.ags, household.bath, household.bdsp, household.bld, household.bus, household.conp, household.elep, household.fs, household.fulp, household.gasp, household.hfl, household.insp, household.mhp, household.mrgi, household.mrgp, household.mrgt, household.mrgx, household.refr, household.rmsp, household.rntm, household.rntp, household.rwat, household.sink, household.smp, household.stov, household.tel, household.ten, household.toil, household.vacs, household.valp, household.veh, household.watp, household.ybl, household.fes, household.fincp, household.fparc, household.grntp, household.grpip, household.hhl, household.hht, household.hincp, household.hugcl, household.hupac, household.hupaoc, household.huparc, household.kit, household.lngi, household.multg, household.mv, household.noc, household.npf, household.npp, household.nr, household.nrc, household.ocpip, household.partner, household.plm, household.psf, household.r18, household.r60, household.r65, household.resmode, household.smocp, household.smx, household.srnt, household.sval, household.taxp, household.wif, household.wkexrel, household.workstat, household.facrp, household.fagsp, household.fbathp, household.fbdsp, household.fbldp, household.fbusp, household.fconp, household.felep, household.ffsp, household.ffulp, household.fgasp, household.fhflp, household.finsp, household.fkitp, household.fmhp, household.fmrgip, household.fmrgp, household.fmrgtp, household.fmrgxp, household.fmvp, household.fplmp, household.frefrp, household.frmsp, household.frntmp, household.frntp, household.frwatp, household.fsinkp, household.fsmp, household.fsmxhp, household.fsmxsp, household.fstovp, household.ftaxp, household.ftelp, household.ftenp, household.ftoilp, household.fvacsp, household.fvalp, household.fvehp, household.fwatp, household.fyblp, household.wgtp1, household.wgtp2, household.wgtp3, household.wgtp4, household.wgtp5, household.wgtp6, household.wgtp7, household.wgtp8, household.wgtp9, household.wgtp10, household.wgtp11, household.wgtp12, household.wgtp13, household.wgtp14, household.wgtp15, household.wgtp16, household.wgtp17, household.wgtp18, household.wgtp19, household.wgtp20, household.wgtp21, household.wgtp22, household.wgtp23, household.wgtp24, household.wgtp25, household.wgtp26, household.wgtp27, household.wgtp28, household.wgtp29, household.wgtp30, household.wgtp31, household.wgtp32, household.wgtp33, household.wgtp34, household.wgtp35, household.wgtp36, household.wgtp37, household.wgtp38, household.wgtp39, household.wgtp40, household.wgtp41, household.wgtp42, household.wgtp43, household.wgtp44, household.wgtp45, household.wgtp46, household.wgtp47, household.wgtp48, household.wgtp49, household.wgtp50, household.wgtp51, household.wgtp52, household.wgtp53, household.wgtp54, household.wgtp55, household.wgtp56, household.wgtp57, household.wgtp58, household.wgtp59, household.wgtp60, household.wgtp61, household.wgtp62, household.wgtp63, household.wgtp64, household.wgtp65, household.wgtp66, household.wgtp67, household.wgtp68, household.wgtp69, household.wgtp70, household.wgtp71, household.wgtp72, household.wgtp73, household.wgtp74, household.wgtp75, household.wgtp76, household.wgtp77, household.wgtp78, household.wgtp79, household.wgtp80 ] | | ) [ wrd "5" ] | +-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +----------------------------------------------------------------------------+ | mal | +============================================================================+ | function user.s4_1{autoCommit=true}():void; | | X_16 := nil:bat[:oid,:oid]; | | X_19 := nil:bat[:oid,:oid]; | | X_20 := nil:bat[:oid,:str]; | | barrier X_3105 := language.dataflow(); | | X_2 := sql.mvc(); | | X_3:bat[:oid,:str] := sql.bind(X_2,"sys","household","rt",0); | | X_8:bat[:oid,:str] := sql.bind(X_2,"sys","household","rt",2); | | X_10 := algebra.kdifference(X_3,X_8); | | X_11 := algebra.kunion(X_10,X_8); | | X_12:bat[:oid,:str] := sql.bind(X_2,"sys","household","rt",1); | | X_14 := algebra.kunion(X_11,X_12); | | X_15:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_16 := bat.reverse(X_15); | | X_17 := algebra.kdifference(X_14,X_16); | | X_18 := algebra.slice(X_17,0:wrd,4:wrd); | | X_19 := bat.mirror(X_18); | | X_20 := algebra.leftjoin(X_19,X_17); | | exit X_3105; | | X_2396 := sql.resultSet(202,1,X_20); | | X_31 := nil:bat[:oid,:int]; | | X_43 := nil:bat[:oid,:int]; | | X_54 := nil:bat[:oid,:int]; | | X_67 := nil:bat[:oid,:int]; | | X_77 := nil:bat[:oid,:int]; | | X_90 := nil:bat[:oid,:int]; | | X_100 := nil:bat[:oid,:int]; | | X_115 := nil:bat[:oid,:int]; | | X_125 := nil:bat[:oid,:int]; | | X_138 := nil:bat[:oid,:int]; | | X_149 := nil:bat[:oid,:int]; | | X_161 := nil:bat[:oid,:int]; | | X_172 := nil:bat[:oid,:int]; | | X_184 := nil:bat[:oid,:int]; | | X_195 := nil:bat[:oid,:int]; | | X_210 := nil:bat[:oid,:int]; | | X_220 := nil:bat[:oid,:int]; | | X_233 := nil:bat[:oid,:int]; | | X_243 := nil:bat[:oid,:int]; | | X_256 := nil:bat[:oid,:int]; | | X_266 := nil:bat[:oid,:int]; | | X_279 := nil:bat[:oid,:int]; | | X_289 := nil:bat[:oid,:int]; | | X_304 := nil:bat[:oid,:int]; | | X_315 := nil:bat[:oid,:int]; | | X_327 := nil:bat[:oid,:int]; | | X_338 := nil:bat[:oid,:int]; | | X_350 := nil:bat[:oid,:int]; | | X_361 := nil:bat[:oid,:int]; | | X_374 := nil:bat[:oid,:int]; | | X_384 := nil:bat[:oid,:int]; | | X_399 := nil:bat[:oid,:int]; | | X_409 := nil:bat[:oid,:int]; | | X_422 := nil:bat[:oid,:int]; | | X_432 := nil:bat[:oid,:int]; | | X_445 := nil:bat[:oid,:int]; | | X_455 := nil:bat[:oid,:int]; | | X_468 := nil:bat[:oid,:int]; | | X_479 := nil:bat[:oid,:int]; | | X_493 := nil:bat[:oid,:int]; | | X_504 := nil:bat[:oid,:int]; | | X_516 := nil:bat[:oid,:int]; | | X_527 := nil:bat[:oid,:int]; | | X_540 := nil:bat[:oid,:int]; | | X_550 := nil:bat[:oid,:int]; | | X_563 := nil:bat[:oid,:int]; | | X_573 := nil:bat[:oid,:int]; | | X_588 := nil:bat[:oid,:int]; | | X_598 := nil:bat[:oid,:int]; | | X_611 := nil:bat[:oid,:int]; | | X_621 := nil:bat[:oid,:int]; | | X_634 := nil:bat[:oid,:int]; | | X_645 := nil:bat[:oid,:int]; | | X_657 := nil:bat[:oid,:int]; | | X_668 := nil:bat[:oid,:int]; | | X_682 := nil:bat[:oid,:int]; | | X_693 := nil:bat[:oid,:int]; | | X_706 := nil:bat[:oid,:int]; | | X_716 := nil:bat[:oid,:int]; | | X_729 := nil:bat[:oid,:int]; | | X_739 := nil:bat[:oid,:int]; | | X_752 := nil:bat[:oid,:int]; | | X_762 := nil:bat[:oid,:int]; | | X_777 := nil:bat[:oid,:int]; | | X_787 := nil:bat[:oid,:int]; | | X_800 := nil:bat[:oid,:int]; | | X_811 := nil:bat[:oid,:int]; | | X_823 := nil:bat[:oid,:int]; | | X_834 := nil:bat[:oid,:int]; | | X_846 := nil:bat[:oid,:int]; | | X_857 := nil:bat[:oid,:int]; | | X_872 := nil:bat[:oid,:int]; | | X_882 := nil:bat[:oid,:int]; | | X_895 := nil:bat[:oid,:int]; | | X_905 := nil:bat[:oid,:int]; | | X_918 := nil:bat[:oid,:int]; | | X_928 := nil:bat[:oid,:int]; | | X_941 := nil:bat[:oid,:int]; | | X_951 := nil:bat[:oid,:int]; | | X_966 := nil:bat[:oid,:int]; | | X_977 := nil:bat[:oid,:int]; | | X_989 := nil:bat[:oid,:int]; | | X_1000 := nil:bat[:oid,:int]; | | X_1012 := nil:bat[:oid,:int]; | | X_1023 := nil:bat[:oid,:int]; | | X_1036 := nil:bat[:oid,:int]; | | X_1046 := nil:bat[:oid,:int]; | | X_1061 := nil:bat[:oid,:int]; | | X_1071 := nil:bat[:oid,:int]; | | X_1084 := nil:bat[:oid,:int]; | | X_1094 := nil:bat[:oid,:int]; | | X_1107 := nil:bat[:oid,:int]; | | X_1117 := nil:bat[:oid,:int]; | | X_1130 := nil:bat[:oid,:int]; | | X_1141 := nil:bat[:oid,:int]; | | X_1155 := nil:bat[:oid,:int]; | | X_1166 := nil:bat[:oid,:int]; | | X_1178 := nil:bat[:oid,:int]; | | X_1189 := nil:bat[:oid,:int]; | | X_1202 := nil:bat[:oid,:int]; | | X_1212 := nil:bat[:oid,:int]; | | X_1225 := nil:bat[:oid,:int]; | | X_1235 := nil:bat[:oid,:int]; | | X_1250 := nil:bat[:oid,:int]; | | X_1260 := nil:bat[:oid,:int]; | | X_1273 := nil:bat[:oid,:int]; | | X_1283 := nil:bat[:oid,:int]; | | X_1296 := nil:bat[:oid,:int]; | | X_1307 := nil:bat[:oid,:int]; | | X_1319 := nil:bat[:oid,:int]; | | X_1330 := nil:bat[:oid,:int]; | | X_1344 := nil:bat[:oid,:int]; | | X_1355 := nil:bat[:oid,:int]; | | X_1368 := nil:bat[:oid,:int]; | | X_1378 := nil:bat[:oid,:int]; | | X_1391 := nil:bat[:oid,:int]; | | X_1401 := nil:bat[:oid,:int]; | | X_1414 := nil:bat[:oid,:int]; | | X_1424 := nil:bat[:oid,:int]; | | X_1439 := nil:bat[:oid,:int]; | | X_1449 := nil:bat[:oid,:int]; | | X_1462 := nil:bat[:oid,:int]; | | X_1473 := nil:bat[:oid,:int]; | | X_1485 := nil:bat[:oid,:int]; | | X_1496 := nil:bat[:oid,:int]; | | X_1508 := nil:bat[:oid,:int]; | | X_1519 := nil:bat[:oid,:int]; | | X_1534 := nil:bat[:oid,:int]; | | X_1544 := nil:bat[:oid,:int]; | | X_1557 := nil:bat[:oid,:int]; | | X_1567 := nil:bat[:oid,:int]; | | X_1580 := nil:bat[:oid,:int]; | | X_1590 := nil:bat[:oid,:int]; | | X_1603 := nil:bat[:oid,:int]; | | X_1613 := nil:bat[:oid,:int]; | | X_1628 := nil:bat[:oid,:int]; | | X_1639 := nil:bat[:oid,:int]; | | X_1651 := nil:bat[:oid,:int]; | | X_1662 := nil:bat[:oid,:int]; | | X_1674 := nil:bat[:oid,:int]; | | X_1685 := nil:bat[:oid,:int]; | | X_1698 := nil:bat[:oid,:int]; | | X_1708 := nil:bat[:oid,:int]; | | X_1723 := nil:bat[:oid,:int]; | | X_1733 := nil:bat[:oid,:int]; | | X_1746 := nil:bat[:oid,:int]; | | X_1756 := nil:bat[:oid,:int]; | | X_1769 := nil:bat[:oid,:int]; | | X_1779 := nil:bat[:oid,:int]; | | X_1792 := nil:bat[:oid,:int]; | | X_1803 := nil:bat[:oid,:int]; | | X_1817 := nil:bat[:oid,:int]; | | X_1828 := nil:bat[:oid,:int]; | | X_1840 := nil:bat[:oid,:int]; | | X_1851 := nil:bat[:oid,:int]; | | X_1864 := nil:bat[:oid,:int]; | | X_1874 := nil:bat[:oid,:int]; | | X_1887 := nil:bat[:oid,:int]; | | X_1897 := nil:bat[:oid,:int]; | | X_1912 := nil:bat[:oid,:int]; | | X_1922 := nil:bat[:oid,:int]; | | X_1935 := nil:bat[:oid,:int]; | | X_1945 := nil:bat[:oid,:int]; | | X_1958 := nil:bat[:oid,:int]; | | X_1969 := nil:bat[:oid,:int]; | | X_1981 := nil:bat[:oid,:int]; | | X_1992 := nil:bat[:oid,:int]; | | X_2006 := nil:bat[:oid,:int]; | | X_2017 := nil:bat[:oid,:int]; | | X_2030 := nil:bat[:oid,:int]; | | X_2040 := nil:bat[:oid,:int]; | | X_2053 := nil:bat[:oid,:int]; | | X_2063 := nil:bat[:oid,:int]; | | X_2076 := nil:bat[:oid,:int]; | | X_2086 := nil:bat[:oid,:int]; | | X_2101 := nil:bat[:oid,:int]; | | X_2111 := nil:bat[:oid,:int]; | | X_2124 := nil:bat[:oid,:int]; | | X_2135 := nil:bat[:oid,:int]; | | X_2147 := nil:bat[:oid,:int]; | | X_2158 := nil:bat[:oid,:int]; | | X_2170 := nil:bat[:oid,:int]; | | X_2181 := nil:bat[:oid,:int]; | | X_2196 := nil:bat[:oid,:int]; | | X_2206 := nil:bat[:oid,:int]; | | X_2219 := nil:bat[:oid,:int]; | | X_2229 := nil:bat[:oid,:int]; | | X_2242 := nil:bat[:oid,:int]; | | X_2252 := nil:bat[:oid,:int]; | | X_2265 := nil:bat[:oid,:int]; | | X_2275 := nil:bat[:oid,:int]; | | X_2290 := nil:bat[:oid,:int]; | | X_2301 := nil:bat[:oid,:int]; | | X_2313 := nil:bat[:oid,:int]; | | X_2324 := nil:bat[:oid,:int]; | | X_2336 := nil:bat[:oid,:int]; | | X_2347 := nil:bat[:oid,:int]; | | X_2360 := nil:bat[:oid,:int]; | | X_2370 := nil:bat[:oid,:int]; | | X_2385 := nil:bat[:oid,:int]; | | X_2395 := nil:bat[:oid,:int]; | | barrier X_3114 := language.dataflow(); | | X_21:bat[:oid,:int] := sql.bind(X_2,"sys","household","serialno",0); | | X_23:bat[:oid,:int] := sql.bind(X_2,"sys","household","serialno",2); | | X_26 := algebra.kdifference(X_21,X_23); | | X_27 := algebra.kunion(X_26,X_23); | | X_28:bat[:oid,:int] := sql.bind(X_2,"sys","household","serialno",1); | | X_29 := algebra.kunion(X_27,X_28); | | X_30 := algebra.kdifference(X_29,X_16); | | X_31 := algebra.leftjoin(X_19,X_30); | | X_32:bat[:oid,:int] := sql.bind(X_2,"sys","household","division",0); | | X_35:bat[:oid,:int] := sql.bind(X_2,"sys","household","division",2); | | X_37 := algebra.kdifference(X_32,X_35); | | X_38 := algebra.kunion(X_37,X_35); | | X_39:bat[:oid,:int] := sql.bind(X_2,"sys","household","division",1); | | X_41 := algebra.kunion(X_38,X_39); | | X_42 := algebra.kdifference(X_41,X_16); | | X_43 := algebra.leftjoin(X_19,X_42); | | X_45:bat[:oid,:int] := sql.bind(X_2,"sys","household","puma",0); | | X_48:bat[:oid,:int] := sql.bind(X_2,"sys","household","puma",2); | | X_49 := algebra.kdifference(X_45,X_48); | | X_50 := algebra.kunion(X_49,X_48); | | X_51:bat[:oid,:int] := sql.bind(X_2,"sys","household","puma",1); | | X_52 := algebra.kunion(X_50,X_51); | | X_53 := algebra.kdifference(X_52,X_16); | | X_54 := algebra.leftjoin(X_19,X_53); | | X_55:bat[:oid,:int] := sql.bind(X_2,"sys","household","region",0); | | X_58:bat[:oid,:int] := sql.bind(X_2,"sys","household","region",2); | | X_60 := algebra.kdifference(X_55,X_58); | | X_61 := algebra.kunion(X_60,X_58); | | X_62:bat[:oid,:int] := sql.bind(X_2,"sys","household","region",1); | | X_64 := algebra.kunion(X_61,X_62); | | X_65 := algebra.kdifference(X_64,X_16); | | X_67 := algebra.leftjoin(X_19,X_65); | | X_68:bat[:oid,:int] := sql.bind(X_2,"sys","household","st",0); | | X_71:bat[:oid,:int] := sql.bind(X_2,"sys","household","st",2); | | X_72 := algebra.kdifference(X_68,X_71); | | X_73 := algebra.kunion(X_72,X_71); | | X_74:bat[:oid,:int] := sql.bind(X_2,"sys","household","st",1); | | X_75 := algebra.kunion(X_73,X_74); | | X_76 := algebra.kdifference(X_75,X_16); | | X_77 := algebra.leftjoin(X_19,X_76); | | X_78:bat[:oid,:int] := sql.bind(X_2,"sys","household","adjhsg",0); | | X_81:bat[:oid,:int] := sql.bind(X_2,"sys","household","adjhsg",2); | | X_83 := algebra.kdifference(X_78,X_81); | | X_84 := algebra.kunion(X_83,X_81); | | X_85:bat[:oid,:int] := sql.bind(X_2,"sys","household","adjhsg",1); | | X_88 := algebra.kunion(X_84,X_85); | | X_89 := algebra.kdifference(X_88,X_16); | | X_90 := algebra.leftjoin(X_19,X_89); | | X_91:bat[:oid,:int] := sql.bind(X_2,"sys","household","adjinc",0); | | X_94:bat[:oid,:int] := sql.bind(X_2,"sys","household","adjinc",2); | | X_95 := algebra.kdifference(X_91,X_94); | | X_96 := algebra.kunion(X_95,X_94); | | X_97:bat[:oid,:int] := sql.bind(X_2,"sys","household","adjinc",1); | | X_98 := algebra.kunion(X_96,X_97); | | X_99 := algebra.kdifference(X_98,X_16); | | X_100 := algebra.leftjoin(X_19,X_99); | | X_101:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp",0); | | X_104:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp",2); | | X_107 := algebra.kdifference(X_101,X_104); | | X_108 := algebra.kunion(X_107,X_104); | | X_109:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp",1); | | X_111 := algebra.kunion(X_108,X_109); | | X_112:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_113 := bat.reverse(X_112); | | X_114 := algebra.kdifference(X_111,X_113); | | X_115 := algebra.leftjoin(X_19,X_114); | | X_116:bat[:oid,:int] := sql.bind(X_2,"sys","household","np",0); | | X_119:bat[:oid,:int] := sql.bind(X_2,"sys","household","np",2); | | X_120 := algebra.kdifference(X_116,X_119); | | X_121 := algebra.kunion(X_120,X_119); | | X_122:bat[:oid,:int] := sql.bind(X_2,"sys","household","np",1); | | X_123 := algebra.kunion(X_121,X_122); | | X_124 := algebra.kdifference(X_123,X_113); | | X_125 := algebra.leftjoin(X_19,X_124); | | X_127:bat[:oid,:int] := sql.bind(X_2,"sys","household","zzzz",0); | | X_130:bat[:oid,:int] := sql.bind(X_2,"sys","household","zzzz",2); | | X_132 := algebra.kdifference(X_127,X_130); | | X_133 := algebra.kunion(X_132,X_130); | | X_134:bat[:oid,:int] := sql.bind(X_2,"sys","household","zzzz",1); | | X_136 := algebra.kunion(X_133,X_134); | | X_137 := algebra.kdifference(X_136,X_113); | | X_138 := algebra.leftjoin(X_19,X_137); | | X_139:bat[:oid,:int] := sql.bind(X_2,"sys","household","acr",0); | | X_142:bat[:oid,:int] := sql.bind(X_2,"sys","household","acr",2); | | X_143 := algebra.kdifference(X_139,X_142); | | X_144 := algebra.kunion(X_143,X_142); | | X_145:bat[:oid,:int] := sql.bind(X_2,"sys","household","acr",1); | | X_146 := algebra.kunion(X_144,X_145); | | X_147 := algebra.kdifference(X_146,X_113); | | X_149 := algebra.leftjoin(X_19,X_147); | | X_150:bat[:oid,:int] := sql.bind(X_2,"sys","household","ags",0); | | X_153:bat[:oid,:int] := sql.bind(X_2,"sys","household","ags",2); | | X_155 := algebra.kdifference(X_150,X_153); | | X_156 := algebra.kunion(X_155,X_153); | | X_157:bat[:oid,:int] := sql.bind(X_2,"sys","household","ags",1); | | X_159 := algebra.kunion(X_156,X_157); | | X_160 := algebra.kdifference(X_159,X_113); | | X_161 := algebra.leftjoin(X_19,X_160); | | X_162:bat[:oid,:int] := sql.bind(X_2,"sys","household","bath",0); | | X_165:bat[:oid,:int] := sql.bind(X_2,"sys","household","bath",2); | | X_166 := algebra.kdifference(X_162,X_165); | | X_167 := algebra.kunion(X_166,X_165); | | X_168:bat[:oid,:int] := sql.bind(X_2,"sys","household","bath",1); | | X_170 := algebra.kunion(X_167,X_168); | | X_171 := algebra.kdifference(X_170,X_113); | | X_172 := algebra.leftjoin(X_19,X_171); | | X_173:bat[:oid,:int] := sql.bind(X_2,"sys","household","bdsp",0); | | X_176:bat[:oid,:int] := sql.bind(X_2,"sys","household","bdsp",2); | | X_178 := algebra.kdifference(X_173,X_176); | | X_179 := algebra.kunion(X_178,X_176); | | X_180:bat[:oid,:int] := sql.bind(X_2,"sys","household","bdsp",1); | | X_182 := algebra.kunion(X_179,X_180); | | X_183 := algebra.kdifference(X_182,X_113); | | X_184 := algebra.leftjoin(X_19,X_183); | | X_185:bat[:oid,:int] := sql.bind(X_2,"sys","household","bld",0); | | X_189:bat[:oid,:int] := sql.bind(X_2,"sys","household","bld",2); | | X_190 := algebra.kdifference(X_185,X_189); | | X_191 := algebra.kunion(X_190,X_189); | | X_192:bat[:oid,:int] := sql.bind(X_2,"sys","household","bld",1); | | X_193 := algebra.kunion(X_191,X_192); | | X_194 := algebra.kdifference(X_193,X_113); | | X_195 := algebra.leftjoin(X_19,X_194); | | X_196:bat[:oid,:int] := sql.bind(X_2,"sys","household","bus",0); | | X_199:bat[:oid,:int] := sql.bind(X_2,"sys","household","bus",2); | | X_201 := algebra.kdifference(X_196,X_199); | | X_202 := algebra.kunion(X_201,X_199); | | X_203:bat[:oid,:int] := sql.bind(X_2,"sys","household","bus",1); | | X_205 := algebra.kunion(X_202,X_203); | | X_206:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_207 := bat.reverse(X_206); | | X_208 := algebra.kdifference(X_205,X_207); | | X_210 := algebra.leftjoin(X_19,X_208); | | X_211:bat[:oid,:int] := sql.bind(X_2,"sys","household","conp",0); | | X_214:bat[:oid,:int] := sql.bind(X_2,"sys","household","conp",2); | | X_215 := algebra.kdifference(X_211,X_214); | | X_216 := algebra.kunion(X_215,X_214); | | X_217:bat[:oid,:int] := sql.bind(X_2,"sys","household","conp",1); | | X_218 := algebra.kunion(X_216,X_217); | | X_219 := algebra.kdifference(X_218,X_207); | | X_220 := algebra.leftjoin(X_19,X_219); | | X_221:bat[:oid,:int] := sql.bind(X_2,"sys","household","elep",0); | | X_224:bat[:oid,:int] := sql.bind(X_2,"sys","household","elep",2); | | X_226 := algebra.kdifference(X_221,X_224); | | X_227 := algebra.kunion(X_226,X_224); | | X_228:bat[:oid,:int] := sql.bind(X_2,"sys","household","elep",1); | | X_230 := algebra.kunion(X_227,X_228); | | X_232 := algebra.kdifference(X_230,X_207); | | X_233 := algebra.leftjoin(X_19,X_232); | | X_234:bat[:oid,:int] := sql.bind(X_2,"sys","household","fs",0); | | X_237:bat[:oid,:int] := sql.bind(X_2,"sys","household","fs",2); | | X_238 := algebra.kdifference(X_234,X_237); | | X_239 := algebra.kunion(X_238,X_237); | | X_240:bat[:oid,:int] := sql.bind(X_2,"sys","household","fs",1); | | X_241 := algebra.kunion(X_239,X_240); | | X_242 := algebra.kdifference(X_241,X_207); | | X_243 := algebra.leftjoin(X_19,X_242); | | X_244:bat[:oid,:int] := sql.bind(X_2,"sys","household","fulp",0); | | X_247:bat[:oid,:int] := sql.bind(X_2,"sys","household","fulp",2); | | X_249 := algebra.kdifference(X_244,X_247); | | X_250 := algebra.kunion(X_249,X_247); | | X_251:bat[:oid,:int] := sql.bind(X_2,"sys","household","fulp",1); | | X_254 := algebra.kunion(X_250,X_251); | | X_255 := algebra.kdifference(X_254,X_207); | | X_256 := algebra.leftjoin(X_19,X_255); | | X_257:bat[:oid,:int] := sql.bind(X_2,"sys","household","gasp",0); | | X_260:bat[:oid,:int] := sql.bind(X_2,"sys","household","gasp",2); | | X_261 := algebra.kdifference(X_257,X_260); | | X_262 := algebra.kunion(X_261,X_260); | | X_263:bat[:oid,:int] := sql.bind(X_2,"sys","household","gasp",1); | | X_264 := algebra.kunion(X_262,X_263); | | X_265 := algebra.kdifference(X_264,X_207); | | X_266 := algebra.leftjoin(X_19,X_265); | | X_267:bat[:oid,:int] := sql.bind(X_2,"sys","household","hfl",0); | | X_270:bat[:oid,:int] := sql.bind(X_2,"sys","household","hfl",2); | | X_273 := algebra.kdifference(X_267,X_270); | | X_274 := algebra.kunion(X_273,X_270); | | X_275:bat[:oid,:int] := sql.bind(X_2,"sys","household","hfl",1); | | X_277 := algebra.kunion(X_274,X_275); | | X_278 := algebra.kdifference(X_277,X_207); | | X_279 := algebra.leftjoin(X_19,X_278); | | X_280:bat[:oid,:int] := sql.bind(X_2,"sys","household","insp",0); | | X_283:bat[:oid,:int] := sql.bind(X_2,"sys","household","insp",2); | | X_284 := algebra.kdifference(X_280,X_283); | | X_285 := algebra.kunion(X_284,X_283); | | X_286:bat[:oid,:int] := sql.bind(X_2,"sys","household","insp",1); | | X_287 := algebra.kunion(X_285,X_286); | | X_288 := algebra.kdifference(X_287,X_207); | | X_289 := algebra.leftjoin(X_19,X_288); | | X_291:bat[:oid,:int] := sql.bind(X_2,"sys","household","mhp",0); | | X_294:bat[:oid,:int] := sql.bind(X_2,"sys","household","mhp",2); | | X_296 := algebra.kdifference(X_291,X_294); | | X_297 := algebra.kunion(X_296,X_294); | | X_298:bat[:oid,:int] := sql.bind(X_2,"sys","household","mhp",1); | | X_300 := algebra.kunion(X_297,X_298); | | X_301:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_302 := bat.reverse(X_301); | | X_303 := algebra.kdifference(X_300,X_302); | | X_304 := algebra.leftjoin(X_19,X_303); | | X_305:bat[:oid,:int] := sql.bind(X_2,"sys","household","mrgi",0); | | X_308:bat[:oid,:int] := sql.bind(X_2,"sys","household","mrgi",2); | | X_309 := algebra.kdifference(X_305,X_308); | | X_310 := algebra.kunion(X_309,X_308); | | X_311:bat[:oid,:int] := sql.bind(X_2,"sys","household","mrgi",1); | | X_312 := algebra.kunion(X_310,X_311); | | X_313 := algebra.kdifference(X_312,X_302); | | X_315 := algebra.leftjoin(X_19,X_313); | | X_316:bat[:oid,:int] := sql.bind(X_2,"sys","household","mrgp",0); | | X_319:bat[:oid,:int] := sql.bind(X_2,"sys","household","mrgp",2); | | X_321 := algebra.kdifference(X_316,X_319); | | X_322 := algebra.kunion(X_321,X_319); | | X_323:bat[:oid,:int] := sql.bind(X_2,"sys","household","mrgp",1); | | X_325 := algebra.kunion(X_322,X_323); | | X_326 := algebra.kdifference(X_325,X_302); | | X_327 := algebra.leftjoin(X_19,X_326); | | X_328:bat[:oid,:int] := sql.bind(X_2,"sys","household","mrgt",0); | | X_331:bat[:oid,:int] := sql.bind(X_2,"sys","household","mrgt",2); | | X_332 := algebra.kdifference(X_328,X_331); | | X_333 := algebra.kunion(X_332,X_331); | | X_334:bat[:oid,:int] := sql.bind(X_2,"sys","household","mrgt",1); | | X_336 := algebra.kunion(X_333,X_334); | | X_337 := algebra.kdifference(X_336,X_302); | | X_338 := algebra.leftjoin(X_19,X_337); | | X_339:bat[:oid,:int] := sql.bind(X_2,"sys","household","mrgx",0); | | X_342:bat[:oid,:int] := sql.bind(X_2,"sys","household","mrgx",2); | | X_344 := algebra.kdifference(X_339,X_342); | | X_345 := algebra.kunion(X_344,X_342); | | X_346:bat[:oid,:int] := sql.bind(X_2,"sys","household","mrgx",1); | | X_348 := algebra.kunion(X_345,X_346); | | X_349 := algebra.kdifference(X_348,X_302); | | X_350 := algebra.leftjoin(X_19,X_349); | | X_351:bat[:oid,:int] := sql.bind(X_2,"sys","household","refr",0); | | X_355:bat[:oid,:int] := sql.bind(X_2,"sys","household","refr",2); | | X_356 := algebra.kdifference(X_351,X_355); | | X_357 := algebra.kunion(X_356,X_355); | | X_358:bat[:oid,:int] := sql.bind(X_2,"sys","household","refr",1); | | X_359 := algebra.kunion(X_357,X_358); | | X_360 := algebra.kdifference(X_359,X_302); | | X_361 := algebra.leftjoin(X_19,X_360); | | X_362:bat[:oid,:int] := sql.bind(X_2,"sys","household","rmsp",0); | | X_365:bat[:oid,:int] := sql.bind(X_2,"sys","household","rmsp",2); | | X_367 := algebra.kdifference(X_362,X_365); | | X_368 := algebra.kunion(X_367,X_365); | | X_369:bat[:oid,:int] := sql.bind(X_2,"sys","household","rmsp",1); | | X_371 := algebra.kunion(X_368,X_369); | | X_372 := algebra.kdifference(X_371,X_302); | | X_374 := algebra.leftjoin(X_19,X_372); | | X_375:bat[:oid,:int] := sql.bind(X_2,"sys","household","rntm",0); | | X_378:bat[:oid,:int] := sql.bind(X_2,"sys","household","rntm",2); | | X_379 := algebra.kdifference(X_375,X_378); | | X_380 := algebra.kunion(X_379,X_378); | | X_381:bat[:oid,:int] := sql.bind(X_2,"sys","household","rntm",1); | | X_382 := algebra.kunion(X_380,X_381); | | X_383 := algebra.kdifference(X_382,X_302); | | X_384 := algebra.leftjoin(X_19,X_383); | | X_385:bat[:oid,:int] := sql.bind(X_2,"sys","household","rntp",0); | | X_388:bat[:oid,:int] := sql.bind(X_2,"sys","household","rntp",2); | | X_390 := algebra.kdifference(X_385,X_388); | | X_391 := algebra.kunion(X_390,X_388); | | X_392:bat[:oid,:int] := sql.bind(X_2,"sys","household","rntp",1); | | X_394 := algebra.kunion(X_391,X_392); | | X_395:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_397 := bat.reverse(X_395); | | X_398 := algebra.kdifference(X_394,X_397); | | X_399 := algebra.leftjoin(X_19,X_398); | | X_400:bat[:oid,:int] := sql.bind(X_2,"sys","household","rwat",0); | | X_403:bat[:oid,:int] := sql.bind(X_2,"sys","household","rwat",2); | | X_404 := algebra.kdifference(X_400,X_403); | | X_405 := algebra.kunion(X_404,X_403); | | X_406:bat[:oid,:int] := sql.bind(X_2,"sys","household","rwat",1); | | X_407 := algebra.kunion(X_405,X_406); | | X_408 := algebra.kdifference(X_407,X_397); | | X_409 := algebra.leftjoin(X_19,X_408); | | X_410:bat[:oid,:int] := sql.bind(X_2,"sys","household","sink",0); | | X_413:bat[:oid,:int] := sql.bind(X_2,"sys","household","sink",2); | | X_415 := algebra.kdifference(X_410,X_413); | | X_416 := algebra.kunion(X_415,X_413); | | X_417:bat[:oid,:int] := sql.bind(X_2,"sys","household","sink",1); | | X_420 := algebra.kunion(X_416,X_417); | | X_421 := algebra.kdifference(X_420,X_397); | | X_422 := algebra.leftjoin(X_19,X_421); | | X_423:bat[:oid,:int] := sql.bind(X_2,"sys","household","smp",0); | | X_426:bat[:oid,:int] := sql.bind(X_2,"sys","household","smp",2); | | X_427 := algebra.kdifference(X_423,X_426); | | X_428 := algebra.kunion(X_427,X_426); | | X_429:bat[:oid,:int] := sql.bind(X_2,"sys","household","smp",1); | | X_430 := algebra.kunion(X_428,X_429); | | X_431 := algebra.kdifference(X_430,X_397); | | X_432 := algebra.leftjoin(X_19,X_431); | | X_433:bat[:oid,:int] := sql.bind(X_2,"sys","household","stov",0); | | X_436:bat[:oid,:int] := sql.bind(X_2,"sys","household","stov",2); | | X_439 := algebra.kdifference(X_433,X_436); | | X_440 := algebra.kunion(X_439,X_436); | | X_441:bat[:oid,:int] := sql.bind(X_2,"sys","household","stov",1); | | X_443 := algebra.kunion(X_440,X_441); | | X_444 := algebra.kdifference(X_443,X_397); | | X_445 := algebra.leftjoin(X_19,X_444); | | X_446:bat[:oid,:int] := sql.bind(X_2,"sys","household","tel",0); | | X_449:bat[:oid,:int] := sql.bind(X_2,"sys","household","tel",2); | | X_450 := algebra.kdifference(X_446,X_449); | | X_451 := algebra.kunion(X_450,X_449); | | X_452:bat[:oid,:int] := sql.bind(X_2,"sys","household","tel",1); | | X_453 := algebra.kunion(X_451,X_452); | | X_454 := algebra.kdifference(X_453,X_397); | | X_455 := algebra.leftjoin(X_19,X_454); | | X_457:bat[:oid,:int] := sql.bind(X_2,"sys","household","ten",0); | | X_460:bat[:oid,:int] := sql.bind(X_2,"sys","household","ten",2); | | X_462 := algebra.kdifference(X_457,X_460); | | X_463 := algebra.kunion(X_462,X_460); | | X_464:bat[:oid,:int] := sql.bind(X_2,"sys","household","ten",1); | | X_466 := algebra.kunion(X_463,X_464); | | X_467 := algebra.kdifference(X_466,X_397); | | X_468 := algebra.leftjoin(X_19,X_467); | | X_469:bat[:oid,:int] := sql.bind(X_2,"sys","household","toil",0); | | X_472:bat[:oid,:int] := sql.bind(X_2,"sys","household","toil",2); | | X_473 := algebra.kdifference(X_469,X_472); | | X_474 := algebra.kunion(X_473,X_472); | | X_475:bat[:oid,:int] := sql.bind(X_2,"sys","household","toil",1); | | X_476 := algebra.kunion(X_474,X_475); | | X_477 := algebra.kdifference(X_476,X_397); | | X_479 := algebra.leftjoin(X_19,X_477); | | X_480:bat[:oid,:int] := sql.bind(X_2,"sys","household","vacs",0); | | X_483:bat[:oid,:int] := sql.bind(X_2,"sys","household","vacs",2); | | X_485 := algebra.kdifference(X_480,X_483); | | X_486 := algebra.kunion(X_485,X_483); | | X_487:bat[:oid,:int] := sql.bind(X_2,"sys","household","vacs",1); | | X_489 := algebra.kunion(X_486,X_487); | | X_490:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_491 := bat.reverse(X_490); | | X_492 := algebra.kdifference(X_489,X_491); | | X_493 := algebra.leftjoin(X_19,X_492); | | X_494:bat[:oid,:int] := sql.bind(X_2,"sys","household","valp",0); | | X_497:bat[:oid,:int] := sql.bind(X_2,"sys","household","valp",2); | | X_498 := algebra.kdifference(X_494,X_497); | | X_499 := algebra.kunion(X_498,X_497); | | X_500:bat[:oid,:int] := sql.bind(X_2,"sys","household","valp",1); | | X_502 := algebra.kunion(X_499,X_500); | | X_503 := algebra.kdifference(X_502,X_491); | | X_504 := algebra.leftjoin(X_19,X_503); | | X_505:bat[:oid,:int] := sql.bind(X_2,"sys","household","veh",0); | | X_508:bat[:oid,:int] := sql.bind(X_2,"sys","household","veh",2); | | X_510 := algebra.kdifference(X_505,X_508); | | X_511 := algebra.kunion(X_510,X_508); | | X_512:bat[:oid,:int] := sql.bind(X_2,"sys","household","veh",1); | | X_514 := algebra.kunion(X_511,X_512); | | X_515 := algebra.kdifference(X_514,X_491); | | X_516 := algebra.leftjoin(X_19,X_515); | | X_517:bat[:oid,:int] := sql.bind(X_2,"sys","household","watp",0); | | X_521:bat[:oid,:int] := sql.bind(X_2,"sys","household","watp",2); | | X_522 := algebra.kdifference(X_517,X_521); | | X_523 := algebra.kunion(X_522,X_521); | | X_524:bat[:oid,:int] := sql.bind(X_2,"sys","household","watp",1); | | X_525 := algebra.kunion(X_523,X_524); | | X_526 := algebra.kdifference(X_525,X_491); | | X_527 := algebra.leftjoin(X_19,X_526); | | X_528:bat[:oid,:int] := sql.bind(X_2,"sys","household","ybl",0); | | X_531:bat[:oid,:int] := sql.bind(X_2,"sys","household","ybl",2); | | X_533 := algebra.kdifference(X_528,X_531); | | X_534 := algebra.kunion(X_533,X_531); | | X_535:bat[:oid,:int] := sql.bind(X_2,"sys","household","ybl",1); | | X_537 := algebra.kunion(X_534,X_535); | | X_538 := algebra.kdifference(X_537,X_491); | | X_540 := algebra.leftjoin(X_19,X_538); | | X_541:bat[:oid,:int] := sql.bind(X_2,"sys","household","fes",0); | | X_544:bat[:oid,:int] := sql.bind(X_2,"sys","household","fes",2); | | X_545 := algebra.kdifference(X_541,X_544); | | X_546 := algebra.kunion(X_545,X_544); | | X_547:bat[:oid,:int] := sql.bind(X_2,"sys","household","fes",1); | | X_548 := algebra.kunion(X_546,X_547); | | X_549 := algebra.kdifference(X_548,X_491); | | X_550 := algebra.leftjoin(X_19,X_549); | | X_551:bat[:oid,:int] := sql.bind(X_2,"sys","household","fincp",0); | | X_554:bat[:oid,:int] := sql.bind(X_2,"sys","household","fincp",2); | | X_556 := algebra.kdifference(X_551,X_554); | | X_557 := algebra.kunion(X_556,X_554); | | X_558:bat[:oid,:int] := sql.bind(X_2,"sys","household","fincp",1); | | X_560 := algebra.kunion(X_557,X_558); | | X_562 := algebra.kdifference(X_560,X_491); | | X_563 := algebra.leftjoin(X_19,X_562); | | X_564:bat[:oid,:int] := sql.bind(X_2,"sys","household","fparc",0); | | X_567:bat[:oid,:int] := sql.bind(X_2,"sys","household","fparc",2); | | X_568 := algebra.kdifference(X_564,X_567); | | X_569 := algebra.kunion(X_568,X_567); | | X_570:bat[:oid,:int] := sql.bind(X_2,"sys","household","fparc",1); | | X_571 := algebra.kunion(X_569,X_570); | | X_572 := algebra.kdifference(X_571,X_491); | | X_573 := algebra.leftjoin(X_19,X_572); | | X_574:bat[:oid,:int] := sql.bind(X_2,"sys","household","grntp",0); | | X_577:bat[:oid,:int] := sql.bind(X_2,"sys","household","grntp",2); | | X_579 := algebra.kdifference(X_574,X_577); | | X_580 := algebra.kunion(X_579,X_577); | | X_581:bat[:oid,:int] := sql.bind(X_2,"sys","household","grntp",1); | | X_584 := algebra.kunion(X_580,X_581); | | X_585:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_586 := bat.reverse(X_585); | | X_587 := algebra.kdifference(X_584,X_586); | | X_588 := algebra.leftjoin(X_19,X_587); | | X_589:bat[:oid,:int] := sql.bind(X_2,"sys","household","grpip",0); | | X_592:bat[:oid,:int] := sql.bind(X_2,"sys","household","grpip",2); | | X_593 := algebra.kdifference(X_589,X_592); | | X_594 := algebra.kunion(X_593,X_592); | | X_595:bat[:oid,:int] := sql.bind(X_2,"sys","household","grpip",1); | | X_596 := algebra.kunion(X_594,X_595); | | X_597 := algebra.kdifference(X_596,X_586); | | X_598 := algebra.leftjoin(X_19,X_597); | | X_599:bat[:oid,:int] := sql.bind(X_2,"sys","household","hhl",0); | | X_602:bat[:oid,:int] := sql.bind(X_2,"sys","household","hhl",2); | | X_605 := algebra.kdifference(X_599,X_602); | | X_606 := algebra.kunion(X_605,X_602); | | X_607:bat[:oid,:int] := sql.bind(X_2,"sys","household","hhl",1); | | X_609 := algebra.kunion(X_606,X_607); | | X_610 := algebra.kdifference(X_609,X_586); | | X_611 := algebra.leftjoin(X_19,X_610); | | X_612:bat[:oid,:int] := sql.bind(X_2,"sys","household","hht",0); | | X_615:bat[:oid,:int] := sql.bind(X_2,"sys","household","hht",2); | | X_616 := algebra.kdifference(X_612,X_615); | | X_617 := algebra.kunion(X_616,X_615); | | X_618:bat[:oid,:int] := sql.bind(X_2,"sys","household","hht",1); | | X_619 := algebra.kunion(X_617,X_618); | | X_620 := algebra.kdifference(X_619,X_586); | | X_621 := algebra.leftjoin(X_19,X_620); | | X_623:bat[:oid,:int] := sql.bind(X_2,"sys","household","hincp",0); | | X_626:bat[:oid,:int] := sql.bind(X_2,"sys","household","hincp",2); | | X_628 := algebra.kdifference(X_623,X_626); | | X_629 := algebra.kunion(X_628,X_626); | | X_630:bat[:oid,:int] := sql.bind(X_2,"sys","household","hincp",1); | | X_632 := algebra.kunion(X_629,X_630); | | X_633 := algebra.kdifference(X_632,X_586); | | X_634 := algebra.leftjoin(X_19,X_633); | | X_635:bat[:oid,:int] := sql.bind(X_2,"sys","household","hugcl",0); | | X_638:bat[:oid,:int] := sql.bind(X_2,"sys","household","hugcl",2); | | X_639 := algebra.kdifference(X_635,X_638); | | X_640 := algebra.kunion(X_639,X_638); | | X_641:bat[:oid,:int] := sql.bind(X_2,"sys","household","hugcl",1); | | X_642 := algebra.kunion(X_640,X_641); | | X_643 := algebra.kdifference(X_642,X_586); | | X_645 := algebra.leftjoin(X_19,X_643); | | X_646:bat[:oid,:int] := sql.bind(X_2,"sys","household","hupac",0); | | X_649:bat[:oid,:int] := sql.bind(X_2,"sys","household","hupac",2); | | X_651 := algebra.kdifference(X_646,X_649); | | X_652 := algebra.kunion(X_651,X_649); | | X_653:bat[:oid,:int] := sql.bind(X_2,"sys","household","hupac",1); | | X_655 := algebra.kunion(X_652,X_653); | | X_656 := algebra.kdifference(X_655,X_586); | | X_657 := algebra.leftjoin(X_19,X_656); | | X_658:bat[:oid,:int] := sql.bind(X_2,"sys","household","hupaoc",0); | | X_661:bat[:oid,:int] := sql.bind(X_2,"sys","household","hupaoc",2); | | X_662 := algebra.kdifference(X_658,X_661); | | X_663 := algebra.kunion(X_662,X_661); | | X_664:bat[:oid,:int] := sql.bind(X_2,"sys","household","hupaoc",1); | | X_666 := algebra.kunion(X_663,X_664); | | X_667 := algebra.kdifference(X_666,X_586); | | X_668 := algebra.leftjoin(X_19,X_667); | | X_669:bat[:oid,:int] := sql.bind(X_2,"sys","household","huparc",0); | | X_672:bat[:oid,:int] := sql.bind(X_2,"sys","household","huparc",2); | | X_674 := algebra.kdifference(X_669,X_672); | | X_675 := algebra.kunion(X_674,X_672); | | X_676:bat[:oid,:int] := sql.bind(X_2,"sys","household","huparc",1); | | X_678 := algebra.kunion(X_675,X_676); | | X_679:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_680 := bat.reverse(X_679); | | X_681 := algebra.kdifference(X_678,X_680); | | X_682 := algebra.leftjoin(X_19,X_681); | | X_683:bat[:oid,:int] := sql.bind(X_2,"sys","household","kit",0); | | X_687:bat[:oid,:int] := sql.bind(X_2,"sys","household","kit",2); | | X_688 := algebra.kdifference(X_683,X_687); | | X_689 := algebra.kunion(X_688,X_687); | | X_690:bat[:oid,:int] := sql.bind(X_2,"sys","household","kit",1); | | X_691 := algebra.kunion(X_689,X_690); | | X_692 := algebra.kdifference(X_691,X_680); | | X_693 := algebra.leftjoin(X_19,X_692); | | X_694:bat[:oid,:int] := sql.bind(X_2,"sys","household","lngi",0); | | X_697:bat[:oid,:int] := sql.bind(X_2,"sys","household","lngi",2); | | X_699 := algebra.kdifference(X_694,X_697); | | X_700 := algebra.kunion(X_699,X_697); | | X_701:bat[:oid,:int] := sql.bind(X_2,"sys","household","lngi",1); | | X_703 := algebra.kunion(X_700,X_701); | | X_704 := algebra.kdifference(X_703,X_680); | | X_706 := algebra.leftjoin(X_19,X_704); | | X_707:bat[:oid,:int] := sql.bind(X_2,"sys","household","multg",0); | | X_710:bat[:oid,:int] := sql.bind(X_2,"sys","household","multg",2); | | X_711 := algebra.kdifference(X_707,X_710); | | X_712 := algebra.kunion(X_711,X_710); | | X_713:bat[:oid,:int] := sql.bind(X_2,"sys","household","multg",1); | | X_714 := algebra.kunion(X_712,X_713); | | X_715 := algebra.kdifference(X_714,X_680); | | X_716 := algebra.leftjoin(X_19,X_715); | | X_717:bat[:oid,:int] := sql.bind(X_2,"sys","household","mv",0); | | X_720:bat[:oid,:int] := sql.bind(X_2,"sys","household","mv",2); | | X_722 := algebra.kdifference(X_717,X_720); | | X_723 := algebra.kunion(X_722,X_720); | | X_724:bat[:oid,:int] := sql.bind(X_2,"sys","household","mv",1); | | X_726 := algebra.kunion(X_723,X_724); | | X_728 := algebra.kdifference(X_726,X_680); | | X_729 := algebra.leftjoin(X_19,X_728); | | X_730:bat[:oid,:int] := sql.bind(X_2,"sys","household","noc",0); | | X_733:bat[:oid,:int] := sql.bind(X_2,"sys","household","noc",2); | | X_734 := algebra.kdifference(X_730,X_733); | | X_735 := algebra.kunion(X_734,X_733); | | X_736:bat[:oid,:int] := sql.bind(X_2,"sys","household","noc",1); | | X_737 := algebra.kunion(X_735,X_736); | | X_738 := algebra.kdifference(X_737,X_680); | | X_739 := algebra.leftjoin(X_19,X_738); | | X_740:bat[:oid,:int] := sql.bind(X_2,"sys","household","npf",0); | | X_743:bat[:oid,:int] := sql.bind(X_2,"sys","household","npf",2); | | X_745 := algebra.kdifference(X_740,X_743); | | X_746 := algebra.kunion(X_745,X_743); | | X_747:bat[:oid,:int] := sql.bind(X_2,"sys","household","npf",1); | | X_750 := algebra.kunion(X_746,X_747); | | X_751 := algebra.kdifference(X_750,X_680); | | X_752 := algebra.leftjoin(X_19,X_751); | | X_753:bat[:oid,:int] := sql.bind(X_2,"sys","household","npp",0); | | X_756:bat[:oid,:int] := sql.bind(X_2,"sys","household","npp",2); | | X_757 := algebra.kdifference(X_753,X_756); | | X_758 := algebra.kunion(X_757,X_756); | | X_759:bat[:oid,:int] := sql.bind(X_2,"sys","household","npp",1); | | X_760 := algebra.kunion(X_758,X_759); | | X_761 := algebra.kdifference(X_760,X_680); | | X_762 := algebra.leftjoin(X_19,X_761); | | X_763:bat[:oid,:int] := sql.bind(X_2,"sys","household","nr",0); | | X_766:bat[:oid,:int] := sql.bind(X_2,"sys","household","nr",2); | | X_769 := algebra.kdifference(X_763,X_766); | | X_770 := algebra.kunion(X_769,X_766); | | X_771:bat[:oid,:int] := sql.bind(X_2,"sys","household","nr",1); | | X_773 := algebra.kunion(X_770,X_771); | | X_774:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_775 := bat.reverse(X_774); | | X_776 := algebra.kdifference(X_773,X_775); | | X_777 := algebra.leftjoin(X_19,X_776); | | X_778:bat[:oid,:int] := sql.bind(X_2,"sys","household","nrc",0); | | X_781:bat[:oid,:int] := sql.bind(X_2,"sys","household","nrc",2); | | X_782 := algebra.kdifference(X_778,X_781); | | X_783 := algebra.kunion(X_782,X_781); | | X_784:bat[:oid,:int] := sql.bind(X_2,"sys","household","nrc",1); | | X_785 := algebra.kunion(X_783,X_784); | | X_786 := algebra.kdifference(X_785,X_775); | | X_787 := algebra.leftjoin(X_19,X_786); | | X_789:bat[:oid,:int] := sql.bind(X_2,"sys","household","ocpip",0); | | X_792:bat[:oid,:int] := sql.bind(X_2,"sys","household","ocpip",2); | | X_794 := algebra.kdifference(X_789,X_792); | | X_795 := algebra.kunion(X_794,X_792); | | X_796:bat[:oid,:int] := sql.bind(X_2,"sys","household","ocpip",1); | | X_798 := algebra.kunion(X_795,X_796); | | X_799 := algebra.kdifference(X_798,X_775); | | X_800 := algebra.leftjoin(X_19,X_799); | | X_801:bat[:oid,:int] := sql.bind(X_2,"sys","household","partner",0); | | X_804:bat[:oid,:int] := sql.bind(X_2,"sys","household","partner",2); | | X_805 := algebra.kdifference(X_801,X_804); | | X_806 := algebra.kunion(X_805,X_804); | | X_807:bat[:oid,:int] := sql.bind(X_2,"sys","household","partner",1); | | X_808 := algebra.kunion(X_806,X_807); | | X_809 := algebra.kdifference(X_808,X_775); | | X_811 := algebra.leftjoin(X_19,X_809); | | X_812:bat[:oid,:int] := sql.bind(X_2,"sys","household","plm",0); | | X_815:bat[:oid,:int] := sql.bind(X_2,"sys","household","plm",2); | | X_817 := algebra.kdifference(X_812,X_815); | | X_818 := algebra.kunion(X_817,X_815); | | X_819:bat[:oid,:int] := sql.bind(X_2,"sys","household","plm",1); | | X_821 := algebra.kunion(X_818,X_819); | | X_822 := algebra.kdifference(X_821,X_775); | | X_823 := algebra.leftjoin(X_19,X_822); | | X_824:bat[:oid,:int] := sql.bind(X_2,"sys","household","psf",0); | | X_827:bat[:oid,:int] := sql.bind(X_2,"sys","household","psf",2); | | X_828 := algebra.kdifference(X_824,X_827); | | X_829 := algebra.kunion(X_828,X_827); | | X_830:bat[:oid,:int] := sql.bind(X_2,"sys","household","psf",1); | | X_832 := algebra.kunion(X_829,X_830); | | X_833 := algebra.kdifference(X_832,X_775); | | X_834 := algebra.leftjoin(X_19,X_833); | | X_835:bat[:oid,:int] := sql.bind(X_2,"sys","household","r18",0); | | X_838:bat[:oid,:int] := sql.bind(X_2,"sys","household","r18",2); | | X_840 := algebra.kdifference(X_835,X_838); | | X_841 := algebra.kunion(X_840,X_838); | | X_842:bat[:oid,:int] := sql.bind(X_2,"sys","household","r18",1); | | X_844 := algebra.kunion(X_841,X_842); | | X_845 := algebra.kdifference(X_844,X_775); | | X_846 := algebra.leftjoin(X_19,X_845); | | X_847:bat[:oid,:int] := sql.bind(X_2,"sys","household","r60",0); | | X_851:bat[:oid,:int] := sql.bind(X_2,"sys","household","r60",2); | | X_852 := algebra.kdifference(X_847,X_851); | | X_853 := algebra.kunion(X_852,X_851); | | X_854:bat[:oid,:int] := sql.bind(X_2,"sys","household","r60",1); | | X_855 := algebra.kunion(X_853,X_854); | | X_856 := algebra.kdifference(X_855,X_775); | | X_857 := algebra.leftjoin(X_19,X_856); | | X_858:bat[:oid,:int] := sql.bind(X_2,"sys","household","r65",0); | | X_861:bat[:oid,:int] := sql.bind(X_2,"sys","household","r65",2); | | X_863 := algebra.kdifference(X_858,X_861); | | X_864 := algebra.kunion(X_863,X_861); | | X_865:bat[:oid,:int] := sql.bind(X_2,"sys","household","r65",1); | | X_867 := algebra.kunion(X_864,X_865); | | X_868:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_869 := bat.reverse(X_868); | | X_870 := algebra.kdifference(X_867,X_869); | | X_872 := algebra.leftjoin(X_19,X_870); | | X_873:bat[:oid,:int] := sql.bind(X_2,"sys","household","resmode",0); | | X_876:bat[:oid,:int] := sql.bind(X_2,"sys","household","resmode",2); | | X_877 := algebra.kdifference(X_873,X_876); | | X_878 := algebra.kunion(X_877,X_876); | | X_879:bat[:oid,:int] := sql.bind(X_2,"sys","household","resmode",1); | | X_880 := algebra.kunion(X_878,X_879); | | X_881 := algebra.kdifference(X_880,X_869); | | X_882 := algebra.leftjoin(X_19,X_881); | | X_883:bat[:oid,:int] := sql.bind(X_2,"sys","household","smocp",0); | | X_886:bat[:oid,:int] := sql.bind(X_2,"sys","household","smocp",2); | | X_888 := algebra.kdifference(X_883,X_886); | | X_889 := algebra.kunion(X_888,X_886); | | X_890:bat[:oid,:int] := sql.bind(X_2,"sys","household","smocp",1); | | X_892 := algebra.kunion(X_889,X_890); | | X_894 := algebra.kdifference(X_892,X_869); | | X_895 := algebra.leftjoin(X_19,X_894); | | X_896:bat[:oid,:int] := sql.bind(X_2,"sys","household","smx",0); | | X_899:bat[:oid,:int] := sql.bind(X_2,"sys","household","smx",2); | | X_900 := algebra.kdifference(X_896,X_899); | | X_901 := algebra.kunion(X_900,X_899); | | X_902:bat[:oid,:int] := sql.bind(X_2,"sys","household","smx",1); | | X_903 := algebra.kunion(X_901,X_902); | | X_904 := algebra.kdifference(X_903,X_869); | | X_905 := algebra.leftjoin(X_19,X_904); | | X_906:bat[:oid,:int] := sql.bind(X_2,"sys","household","srnt",0); | | X_909:bat[:oid,:int] := sql.bind(X_2,"sys","household","srnt",2); | | X_911 := algebra.kdifference(X_906,X_909); | | X_912 := algebra.kunion(X_911,X_909); | | X_913:bat[:oid,:int] := sql.bind(X_2,"sys","household","srnt",1); | | X_916 := algebra.kunion(X_912,X_913); | | X_917 := algebra.kdifference(X_916,X_869); | | X_918 := algebra.leftjoin(X_19,X_917); | | X_919:bat[:oid,:int] := sql.bind(X_2,"sys","household","sval",0); | | X_922:bat[:oid,:int] := sql.bind(X_2,"sys","household","sval",2); | | X_923 := algebra.kdifference(X_919,X_922); | | X_924 := algebra.kunion(X_923,X_922); | | X_925:bat[:oid,:int] := sql.bind(X_2,"sys","household","sval",1); | | X_926 := algebra.kunion(X_924,X_925); | | X_927 := algebra.kdifference(X_926,X_869); | | X_928 := algebra.leftjoin(X_19,X_927); | | X_929:bat[:oid,:int] := sql.bind(X_2,"sys","household","taxp",0); | | X_932:bat[:oid,:int] := sql.bind(X_2,"sys","household","taxp",2); | | X_935 := algebra.kdifference(X_929,X_932); | | X_936 := algebra.kunion(X_935,X_932); | | X_937:bat[:oid,:int] := sql.bind(X_2,"sys","household","taxp",1); | | X_939 := algebra.kunion(X_936,X_937); | | X_940 := algebra.kdifference(X_939,X_869); | | X_941 := algebra.leftjoin(X_19,X_940); | | X_942:bat[:oid,:int] := sql.bind(X_2,"sys","household","wif",0); | | X_945:bat[:oid,:int] := sql.bind(X_2,"sys","household","wif",2); | | X_946 := algebra.kdifference(X_942,X_945); | | X_947 := algebra.kunion(X_946,X_945); | | X_948:bat[:oid,:int] := sql.bind(X_2,"sys","household","wif",1); | | X_949 := algebra.kunion(X_947,X_948); | | X_950 := algebra.kdifference(X_949,X_869); | | X_951 := algebra.leftjoin(X_19,X_950); | | X_953:bat[:oid,:int] := sql.bind(X_2,"sys","household","wkexrel",0); | | X_956:bat[:oid,:int] := sql.bind(X_2,"sys","household","wkexrel",2); | | X_958 := algebra.kdifference(X_953,X_956); | | X_959 := algebra.kunion(X_958,X_956); | | X_960:bat[:oid,:int] := sql.bind(X_2,"sys","household","wkexrel",1); | | X_962 := algebra.kunion(X_959,X_960); | | X_963:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_964 := bat.reverse(X_963); | | X_965 := algebra.kdifference(X_962,X_964); | | X_966 := algebra.leftjoin(X_19,X_965); | | X_967:bat[:oid,:int] := sql.bind(X_2,"sys","household","workstat",0); | | X_970:bat[:oid,:int] := sql.bind(X_2,"sys","household","workstat",2); | | X_971 := algebra.kdifference(X_967,X_970); | | X_972 := algebra.kunion(X_971,X_970); | | X_973:bat[:oid,:int] := sql.bind(X_2,"sys","household","workstat",1); | | X_974 := algebra.kunion(X_972,X_973); | | X_975 := algebra.kdifference(X_974,X_964); | | X_977 := algebra.leftjoin(X_19,X_975); | | X_978:bat[:oid,:int] := sql.bind(X_2,"sys","household","facrp",0); | | X_981:bat[:oid,:int] := sql.bind(X_2,"sys","household","facrp",2); | | X_983 := algebra.kdifference(X_978,X_981); | | X_984 := algebra.kunion(X_983,X_981); | | X_985:bat[:oid,:int] := sql.bind(X_2,"sys","household","facrp",1); | | X_987 := algebra.kunion(X_984,X_985); | | X_988 := algebra.kdifference(X_987,X_964); | | X_989 := algebra.leftjoin(X_19,X_988); | | X_990:bat[:oid,:int] := sql.bind(X_2,"sys","household","fagsp",0); | | X_993:bat[:oid,:int] := sql.bind(X_2,"sys","household","fagsp",2); | | X_994 := algebra.kdifference(X_990,X_993); | | X_995 := algebra.kunion(X_994,X_993); | | X_996:bat[:oid,:int] := sql.bind(X_2,"sys","household","fagsp",1); | | X_998 := algebra.kunion(X_995,X_996); | | X_999 := algebra.kdifference(X_998,X_964); | | X_1000 := algebra.leftjoin(X_19,X_999); | | X_1001:bat[:oid,:int] := sql.bind(X_2,"sys","household","fbathp",0); | | X_1004:bat[:oid,:int] := sql.bind(X_2,"sys","household","fbathp",2); | | X_1006 := algebra.kdifference(X_1001,X_1004); | | X_1007 := algebra.kunion(X_1006,X_1004); | | X_1008:bat[:oid,:int] := sql.bind(X_2,"sys","household","fbathp",1); | | X_1010 := algebra.kunion(X_1007,X_1008); | | X_1011 := algebra.kdifference(X_1010,X_964); | | X_1012 := algebra.leftjoin(X_19,X_1011); | | X_1013:bat[:oid,:int] := sql.bind(X_2,"sys","household","fbdsp",0); | | X_1017:bat[:oid,:int] := sql.bind(X_2,"sys","household","fbdsp",2); | | X_1018 := algebra.kdifference(X_1013,X_1017); | | X_1019 := algebra.kunion(X_1018,X_1017); | | X_1020:bat[:oid,:int] := sql.bind(X_2,"sys","household","fbdsp",1); | | X_1021 := algebra.kunion(X_1019,X_1020); | | X_1022 := algebra.kdifference(X_1021,X_964); | | X_1023 := algebra.leftjoin(X_19,X_1022); | | X_1024:bat[:oid,:int] := sql.bind(X_2,"sys","household","fbldp",0); | | X_1027:bat[:oid,:int] := sql.bind(X_2,"sys","household","fbldp",2); | | X_1029 := algebra.kdifference(X_1024,X_1027); | | X_1030 := algebra.kunion(X_1029,X_1027); | | X_1031:bat[:oid,:int] := sql.bind(X_2,"sys","household","fbldp",1); | | X_1033 := algebra.kunion(X_1030,X_1031); | | X_1034 := algebra.kdifference(X_1033,X_964); | | X_1036 := algebra.leftjoin(X_19,X_1034); | | X_1037:bat[:oid,:int] := sql.bind(X_2,"sys","household","fbusp",0); | | X_1040:bat[:oid,:int] := sql.bind(X_2,"sys","household","fbusp",2); | | X_1041 := algebra.kdifference(X_1037,X_1040); | | X_1042 := algebra.kunion(X_1041,X_1040); | | X_1043:bat[:oid,:int] := sql.bind(X_2,"sys","household","fbusp",1); | | X_1044 := algebra.kunion(X_1042,X_1043); | | X_1045 := algebra.kdifference(X_1044,X_964); | | X_1046 := algebra.leftjoin(X_19,X_1045); | | X_1047:bat[:oid,:int] := sql.bind(X_2,"sys","household","fconp",0); | | X_1050:bat[:oid,:int] := sql.bind(X_2,"sys","household","fconp",2); | | X_1052 := algebra.kdifference(X_1047,X_1050); | | X_1053 := algebra.kunion(X_1052,X_1050); | | X_1054:bat[:oid,:int] := sql.bind(X_2,"sys","household","fconp",1); | | X_1056 := algebra.kunion(X_1053,X_1054); | | X_1057:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_1059 := bat.reverse(X_1057); | | X_1060 := algebra.kdifference(X_1056,X_1059); | | X_1061 := algebra.leftjoin(X_19,X_1060); | | X_1062:bat[:oid,:int] := sql.bind(X_2,"sys","household","felep",0); | | X_1065:bat[:oid,:int] := sql.bind(X_2,"sys","household","felep",2); | | X_1066 := algebra.kdifference(X_1062,X_1065); | | X_1067 := algebra.kunion(X_1066,X_1065); | | X_1068:bat[:oid,:int] := sql.bind(X_2,"sys","household","felep",1); | | X_1069 := algebra.kunion(X_1067,X_1068); | | X_1070 := algebra.kdifference(X_1069,X_1059); | | X_1071 := algebra.leftjoin(X_19,X_1070); | | X_1072:bat[:oid,:int] := sql.bind(X_2,"sys","household","ffsp",0); | | X_1075:bat[:oid,:int] := sql.bind(X_2,"sys","household","ffsp",2); | | X_1077 := algebra.kdifference(X_1072,X_1075); | | X_1078 := algebra.kunion(X_1077,X_1075); | | X_1079:bat[:oid,:int] := sql.bind(X_2,"sys","household","ffsp",1); | | X_1082 := algebra.kunion(X_1078,X_1079); | | X_1083 := algebra.kdifference(X_1082,X_1059); | | X_1084 := algebra.leftjoin(X_19,X_1083); | | X_1085:bat[:oid,:int] := sql.bind(X_2,"sys","household","ffulp",0); | | X_1088:bat[:oid,:int] := sql.bind(X_2,"sys","household","ffulp",2); | | X_1089 := algebra.kdifference(X_1085,X_1088); | | X_1090 := algebra.kunion(X_1089,X_1088); | | X_1091:bat[:oid,:int] := sql.bind(X_2,"sys","household","ffulp",1); | | X_1092 := algebra.kunion(X_1090,X_1091); | | X_1093 := algebra.kdifference(X_1092,X_1059); | | X_1094 := algebra.leftjoin(X_19,X_1093); | | X_1095:bat[:oid,:int] := sql.bind(X_2,"sys","household","fgasp",0); | | X_1098:bat[:oid,:int] := sql.bind(X_2,"sys","household","fgasp",2); | | X_1101 := algebra.kdifference(X_1095,X_1098); | | X_1102 := algebra.kunion(X_1101,X_1098); | | X_1103:bat[:oid,:int] := sql.bind(X_2,"sys","household","fgasp",1); | | X_1105 := algebra.kunion(X_1102,X_1103); | | X_1106 := algebra.kdifference(X_1105,X_1059); | | X_1107 := algebra.leftjoin(X_19,X_1106); | | X_1108:bat[:oid,:int] := sql.bind(X_2,"sys","household","fhflp",0); | | X_1111:bat[:oid,:int] := sql.bind(X_2,"sys","household","fhflp",2); | | X_1112 := algebra.kdifference(X_1108,X_1111); | | X_1113 := algebra.kunion(X_1112,X_1111); | | X_1114:bat[:oid,:int] := sql.bind(X_2,"sys","household","fhflp",1); | | X_1115 := algebra.kunion(X_1113,X_1114); | | X_1116 := algebra.kdifference(X_1115,X_1059); | | X_1117 := algebra.leftjoin(X_19,X_1116); | | X_1119:bat[:oid,:int] := sql.bind(X_2,"sys","household","finsp",0); | | X_1122:bat[:oid,:int] := sql.bind(X_2,"sys","household","finsp",2); | | X_1124 := algebra.kdifference(X_1119,X_1122); | | X_1125 := algebra.kunion(X_1124,X_1122); | | X_1126:bat[:oid,:int] := sql.bind(X_2,"sys","household","finsp",1); | | X_1128 := algebra.kunion(X_1125,X_1126); | | X_1129 := algebra.kdifference(X_1128,X_1059); | | X_1130 := algebra.leftjoin(X_19,X_1129); | | X_1131:bat[:oid,:int] := sql.bind(X_2,"sys","household","fkitp",0); | | X_1134:bat[:oid,:int] := sql.bind(X_2,"sys","household","fkitp",2); | | X_1135 := algebra.kdifference(X_1131,X_1134); | | X_1136 := algebra.kunion(X_1135,X_1134); | | X_1137:bat[:oid,:int] := sql.bind(X_2,"sys","household","fkitp",1); | | X_1138 := algebra.kunion(X_1136,X_1137); | | X_1139 := algebra.kdifference(X_1138,X_1059); | | X_1141 := algebra.leftjoin(X_19,X_1139); | | X_1142:bat[:oid,:int] := sql.bind(X_2,"sys","household","fmhp",0); | | X_1145:bat[:oid,:int] := sql.bind(X_2,"sys","household","fmhp",2); | | X_1147 := algebra.kdifference(X_1142,X_1145); | | X_1148 := algebra.kunion(X_1147,X_1145); | | X_1149:bat[:oid,:int] := sql.bind(X_2,"sys","household","fmhp",1); | | X_1151 := algebra.kunion(X_1148,X_1149); | | X_1152:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_1153 := bat.reverse(X_1152); | | X_1154 := algebra.kdifference(X_1151,X_1153); | | X_1155 := algebra.leftjoin(X_19,X_1154); | | X_1156:bat[:oid,:int] := sql.bind(X_2,"sys","household","fmrgip",0); | | X_1159:bat[:oid,:int] := sql.bind(X_2,"sys","household","fmrgip",2); | | X_1160 := algebra.kdifference(X_1156,X_1159); | | X_1161 := algebra.kunion(X_1160,X_1159); | | X_1162:bat[:oid,:int] := sql.bind(X_2,"sys","household","fmrgip",1); | | X_1164 := algebra.kunion(X_1161,X_1162); | | X_1165 := algebra.kdifference(X_1164,X_1153); | | X_1166 := algebra.leftjoin(X_19,X_1165); | | X_1167:bat[:oid,:int] := sql.bind(X_2,"sys","household","fmrgp",0); | | X_1170:bat[:oid,:int] := sql.bind(X_2,"sys","household","fmrgp",2); | | X_1172 := algebra.kdifference(X_1167,X_1170); | | X_1173 := algebra.kunion(X_1172,X_1170); | | X_1174:bat[:oid,:int] := sql.bind(X_2,"sys","household","fmrgp",1); | | X_1176 := algebra.kunion(X_1173,X_1174); | | X_1177 := algebra.kdifference(X_1176,X_1153); | | X_1178 := algebra.leftjoin(X_19,X_1177); | | X_1179:bat[:oid,:int] := sql.bind(X_2,"sys","household","fmrgtp",0); | | X_1183:bat[:oid,:int] := sql.bind(X_2,"sys","household","fmrgtp",2); | | X_1184 := algebra.kdifference(X_1179,X_1183); | | X_1185 := algebra.kunion(X_1184,X_1183); | | X_1186:bat[:oid,:int] := sql.bind(X_2,"sys","household","fmrgtp",1); | | X_1187 := algebra.kunion(X_1185,X_1186); | | X_1188 := algebra.kdifference(X_1187,X_1153); | | X_1189 := algebra.leftjoin(X_19,X_1188); | | X_1190:bat[:oid,:int] := sql.bind(X_2,"sys","household","fmrgxp",0); | | X_1193:bat[:oid,:int] := sql.bind(X_2,"sys","household","fmrgxp",2); | | X_1195 := algebra.kdifference(X_1190,X_1193); | | X_1196 := algebra.kunion(X_1195,X_1193); | | X_1197:bat[:oid,:int] := sql.bind(X_2,"sys","household","fmrgxp",1); | | X_1199 := algebra.kunion(X_1196,X_1197); | | X_1200 := algebra.kdifference(X_1199,X_1153); | | X_1202 := algebra.leftjoin(X_19,X_1200); | | X_1203:bat[:oid,:int] := sql.bind(X_2,"sys","household","fmvp",0); | | X_1206:bat[:oid,:int] := sql.bind(X_2,"sys","household","fmvp",2); | | X_1207 := algebra.kdifference(X_1203,X_1206); | | X_1208 := algebra.kunion(X_1207,X_1206); | | X_1209:bat[:oid,:int] := sql.bind(X_2,"sys","household","fmvp",1); | | X_1210 := algebra.kunion(X_1208,X_1209); | | X_1211 := algebra.kdifference(X_1210,X_1153); | | X_1212 := algebra.leftjoin(X_19,X_1211); | | X_1213:bat[:oid,:int] := sql.bind(X_2,"sys","household","fplmp",0); | | X_1216:bat[:oid,:int] := sql.bind(X_2,"sys","household","fplmp",2); | | X_1218 := algebra.kdifference(X_1213,X_1216); | | X_1219 := algebra.kunion(X_1218,X_1216); | | X_1220:bat[:oid,:int] := sql.bind(X_2,"sys","household","fplmp",1); | | X_1222 := algebra.kunion(X_1219,X_1220); | | X_1224 := algebra.kdifference(X_1222,X_1153); | | X_1225 := algebra.leftjoin(X_19,X_1224); | | X_1226:bat[:oid,:int] := sql.bind(X_2,"sys","household","frefrp",0); | | X_1229:bat[:oid,:int] := sql.bind(X_2,"sys","household","frefrp",2); | | X_1230 := algebra.kdifference(X_1226,X_1229); | | X_1231 := algebra.kunion(X_1230,X_1229); | | X_1232:bat[:oid,:int] := sql.bind(X_2,"sys","household","frefrp",1); | | X_1233 := algebra.kunion(X_1231,X_1232); | | X_1234 := algebra.kdifference(X_1233,X_1153); | | X_1235 := algebra.leftjoin(X_19,X_1234); | | X_1236:bat[:oid,:int] := sql.bind(X_2,"sys","household","frmsp",0); | | X_1239:bat[:oid,:int] := sql.bind(X_2,"sys","household","frmsp",2); | | X_1241 := algebra.kdifference(X_1236,X_1239); | | X_1242 := algebra.kunion(X_1241,X_1239); | | X_1243:bat[:oid,:int] := sql.bind(X_2,"sys","household","frmsp",1); | | X_1246 := algebra.kunion(X_1242,X_1243); | | X_1247:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_1248 := bat.reverse(X_1247); | | X_1249 := algebra.kdifference(X_1246,X_1248); | | X_1250 := algebra.leftjoin(X_19,X_1249); | | X_1251:bat[:oid,:int] := sql.bind(X_2,"sys","household","frntmp",0); | | X_1254:bat[:oid,:int] := sql.bind(X_2,"sys","household","frntmp",2); | | X_1255 := algebra.kdifference(X_1251,X_1254); | | X_1256 := algebra.kunion(X_1255,X_1254); | | X_1257:bat[:oid,:int] := sql.bind(X_2,"sys","household","frntmp",1); | | X_1258 := algebra.kunion(X_1256,X_1257); | | X_1259 := algebra.kdifference(X_1258,X_1248); | | X_1260 := algebra.leftjoin(X_19,X_1259); | | X_1261:bat[:oid,:int] := sql.bind(X_2,"sys","household","frntp",0); | | X_1264:bat[:oid,:int] := sql.bind(X_2,"sys","household","frntp",2); | | X_1267 := algebra.kdifference(X_1261,X_1264); | | X_1268 := algebra.kunion(X_1267,X_1264); | | X_1269:bat[:oid,:int] := sql.bind(X_2,"sys","household","frntp",1); | | X_1271 := algebra.kunion(X_1268,X_1269); | | X_1272 := algebra.kdifference(X_1271,X_1248); | | X_1273 := algebra.leftjoin(X_19,X_1272); | | X_1274:bat[:oid,:int] := sql.bind(X_2,"sys","household","frwatp",0); | | X_1277:bat[:oid,:int] := sql.bind(X_2,"sys","household","frwatp",2); | | X_1278 := algebra.kdifference(X_1274,X_1277); | | X_1279 := algebra.kunion(X_1278,X_1277); | | X_1280:bat[:oid,:int] := sql.bind(X_2,"sys","household","frwatp",1); | | X_1281 := algebra.kunion(X_1279,X_1280); | | X_1282 := algebra.kdifference(X_1281,X_1248); | | X_1283 := algebra.leftjoin(X_19,X_1282); | | X_1285:bat[:oid,:int] := sql.bind(X_2,"sys","household","fsinkp",0); | | X_1288:bat[:oid,:int] := sql.bind(X_2,"sys","household","fsinkp",2); | | X_1290 := algebra.kdifference(X_1285,X_1288); | | X_1291 := algebra.kunion(X_1290,X_1288); | | X_1292:bat[:oid,:int] := sql.bind(X_2,"sys","household","fsinkp",1); | | X_1294 := algebra.kunion(X_1291,X_1292); | | X_1295 := algebra.kdifference(X_1294,X_1248); | | X_1296 := algebra.leftjoin(X_19,X_1295); | | X_1297:bat[:oid,:int] := sql.bind(X_2,"sys","household","fsmp",0); | | X_1300:bat[:oid,:int] := sql.bind(X_2,"sys","household","fsmp",2); | | X_1301 := algebra.kdifference(X_1297,X_1300); | | X_1302 := algebra.kunion(X_1301,X_1300); | | X_1303:bat[:oid,:int] := sql.bind(X_2,"sys","household","fsmp",1); | | X_1304 := algebra.kunion(X_1302,X_1303); | | X_1305 := algebra.kdifference(X_1304,X_1248); | | X_1307 := algebra.leftjoin(X_19,X_1305); | | X_1308:bat[:oid,:int] := sql.bind(X_2,"sys","household","fsmxhp",0); | | X_1311:bat[:oid,:int] := sql.bind(X_2,"sys","household","fsmxhp",2); | | X_1313 := algebra.kdifference(X_1308,X_1311); | | X_1314 := algebra.kunion(X_1313,X_1311); | | X_1315:bat[:oid,:int] := sql.bind(X_2,"sys","household","fsmxhp",1); | | X_1317 := algebra.kunion(X_1314,X_1315); | | X_1318 := algebra.kdifference(X_1317,X_1248); | | X_1319 := algebra.leftjoin(X_19,X_1318); | | X_1320:bat[:oid,:int] := sql.bind(X_2,"sys","household","fsmxsp",0); | | X_1323:bat[:oid,:int] := sql.bind(X_2,"sys","household","fsmxsp",2); | | X_1324 := algebra.kdifference(X_1320,X_1323); | | X_1325 := algebra.kunion(X_1324,X_1323); | | X_1326:bat[:oid,:int] := sql.bind(X_2,"sys","household","fsmxsp",1); | | X_1328 := algebra.kunion(X_1325,X_1326); | | X_1329 := algebra.kdifference(X_1328,X_1248); | | X_1330 := algebra.leftjoin(X_19,X_1329); | | X_1331:bat[:oid,:int] := sql.bind(X_2,"sys","household","fstovp",0); | | X_1334:bat[:oid,:int] := sql.bind(X_2,"sys","household","fstovp",2); | | X_1336 := algebra.kdifference(X_1331,X_1334); | | X_1337 := algebra.kunion(X_1336,X_1334); | | X_1338:bat[:oid,:int] := sql.bind(X_2,"sys","household","fstovp",1); | | X_1340 := algebra.kunion(X_1337,X_1338); | | X_1341:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_1342 := bat.reverse(X_1341); | | X_1343 := algebra.kdifference(X_1340,X_1342); | | X_1344 := algebra.leftjoin(X_19,X_1343); | | X_1345:bat[:oid,:int] := sql.bind(X_2,"sys","household","ftaxp",0); | | X_1349:bat[:oid,:int] := sql.bind(X_2,"sys","household","ftaxp",2); | | X_1350 := algebra.kdifference(X_1345,X_1349); | | X_1351 := algebra.kunion(X_1350,X_1349); | | X_1352:bat[:oid,:int] := sql.bind(X_2,"sys","household","ftaxp",1); | | X_1353 := algebra.kunion(X_1351,X_1352); | | X_1354 := algebra.kdifference(X_1353,X_1342); | | X_1355 := algebra.leftjoin(X_19,X_1354); | | X_1356:bat[:oid,:int] := sql.bind(X_2,"sys","household","ftelp",0); | | X_1359:bat[:oid,:int] := sql.bind(X_2,"sys","household","ftelp",2); | | X_1361 := algebra.kdifference(X_1356,X_1359); | | X_1362 := algebra.kunion(X_1361,X_1359); | | X_1363:bat[:oid,:int] := sql.bind(X_2,"sys","household","ftelp",1); | | X_1365 := algebra.kunion(X_1362,X_1363); | | X_1366 := algebra.kdifference(X_1365,X_1342); | | X_1368 := algebra.leftjoin(X_19,X_1366); | | X_1369:bat[:oid,:int] := sql.bind(X_2,"sys","household","ftenp",0); | | X_1372:bat[:oid,:int] := sql.bind(X_2,"sys","household","ftenp",2); | | X_1373 := algebra.kdifference(X_1369,X_1372); | | X_1374 := algebra.kunion(X_1373,X_1372); | | X_1375:bat[:oid,:int] := sql.bind(X_2,"sys","household","ftenp",1); | | X_1376 := algebra.kunion(X_1374,X_1375); | | X_1377 := algebra.kdifference(X_1376,X_1342); | | X_1378 := algebra.leftjoin(X_19,X_1377); | | X_1379:bat[:oid,:int] := sql.bind(X_2,"sys","household","ftoilp",0); | | X_1382:bat[:oid,:int] := sql.bind(X_2,"sys","household","ftoilp",2); | | X_1384 := algebra.kdifference(X_1379,X_1382); | | X_1385 := algebra.kunion(X_1384,X_1382); | | X_1386:bat[:oid,:int] := sql.bind(X_2,"sys","household","ftoilp",1); | | X_1388 := algebra.kunion(X_1385,X_1386); | | X_1390 := algebra.kdifference(X_1388,X_1342); | | X_1391 := algebra.leftjoin(X_19,X_1390); | | X_1392:bat[:oid,:int] := sql.bind(X_2,"sys","household","fvacsp",0); | | X_1395:bat[:oid,:int] := sql.bind(X_2,"sys","household","fvacsp",2); | | X_1396 := algebra.kdifference(X_1392,X_1395); | | X_1397 := algebra.kunion(X_1396,X_1395); | | X_1398:bat[:oid,:int] := sql.bind(X_2,"sys","household","fvacsp",1); | | X_1399 := algebra.kunion(X_1397,X_1398); | | X_1400 := algebra.kdifference(X_1399,X_1342); | | X_1401 := algebra.leftjoin(X_19,X_1400); | | X_1402:bat[:oid,:int] := sql.bind(X_2,"sys","household","fvalp",0); | | X_1405:bat[:oid,:int] := sql.bind(X_2,"sys","household","fvalp",2); | | X_1407 := algebra.kdifference(X_1402,X_1405); | | X_1408 := algebra.kunion(X_1407,X_1405); | | X_1409:bat[:oid,:int] := sql.bind(X_2,"sys","household","fvalp",1); | | X_1412 := algebra.kunion(X_1408,X_1409); | | X_1413 := algebra.kdifference(X_1412,X_1342); | | X_1414 := algebra.leftjoin(X_19,X_1413); | | X_1415:bat[:oid,:int] := sql.bind(X_2,"sys","household","fvehp",0); | | X_1418:bat[:oid,:int] := sql.bind(X_2,"sys","household","fvehp",2); | | X_1419 := algebra.kdifference(X_1415,X_1418); | | X_1420 := algebra.kunion(X_1419,X_1418); | | X_1421:bat[:oid,:int] := sql.bind(X_2,"sys","household","fvehp",1); | | X_1422 := algebra.kunion(X_1420,X_1421); | | X_1423 := algebra.kdifference(X_1422,X_1342); | | X_1424 := algebra.leftjoin(X_19,X_1423); | | X_1425:bat[:oid,:int] := sql.bind(X_2,"sys","household","fwatp",0); | | X_1428:bat[:oid,:int] := sql.bind(X_2,"sys","household","fwatp",2); | | X_1431 := algebra.kdifference(X_1425,X_1428); | | X_1432 := algebra.kunion(X_1431,X_1428); | | X_1433:bat[:oid,:int] := sql.bind(X_2,"sys","household","fwatp",1); | | X_1435 := algebra.kunion(X_1432,X_1433); | | X_1436:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_1437 := bat.reverse(X_1436); | | X_1438 := algebra.kdifference(X_1435,X_1437); | | X_1439 := algebra.leftjoin(X_19,X_1438); | | X_1440:bat[:oid,:int] := sql.bind(X_2,"sys","household","fyblp",0); | | X_1443:bat[:oid,:int] := sql.bind(X_2,"sys","household","fyblp",2); | | X_1444 := algebra.kdifference(X_1440,X_1443); | | X_1445 := algebra.kunion(X_1444,X_1443); | | X_1446:bat[:oid,:int] := sql.bind(X_2,"sys","household","fyblp",1); | | X_1447 := algebra.kunion(X_1445,X_1446); | | X_1448 := algebra.kdifference(X_1447,X_1437); | | X_1449 := algebra.leftjoin(X_19,X_1448); | | X_1451:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp1",0); | | X_1454:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp1",2); | | X_1456 := algebra.kdifference(X_1451,X_1454); | | X_1457 := algebra.kunion(X_1456,X_1454); | | X_1458:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp1",1); | | X_1460 := algebra.kunion(X_1457,X_1458); | | X_1461 := algebra.kdifference(X_1460,X_1437); | | X_1462 := algebra.leftjoin(X_19,X_1461); | | X_1463:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp2",0); | | X_1466:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp2",2); | | X_1467 := algebra.kdifference(X_1463,X_1466); | | X_1468 := algebra.kunion(X_1467,X_1466); | | X_1469:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp2",1); | | X_1470 := algebra.kunion(X_1468,X_1469); | | X_1471 := algebra.kdifference(X_1470,X_1437); | | X_1473 := algebra.leftjoin(X_19,X_1471); | | X_1474:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp3",0); | | X_1477:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp3",2); | | X_1479 := algebra.kdifference(X_1474,X_1477); | | X_1480 := algebra.kunion(X_1479,X_1477); | | X_1481:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp3",1); | | X_1483 := algebra.kunion(X_1480,X_1481); | | X_1484 := algebra.kdifference(X_1483,X_1437); | | X_1485 := algebra.leftjoin(X_19,X_1484); | | X_1486:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp4",0); | | X_1489:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp4",2); | | X_1490 := algebra.kdifference(X_1486,X_1489); | | X_1491 := algebra.kunion(X_1490,X_1489); | | X_1492:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp4",1); | | X_1494 := algebra.kunion(X_1491,X_1492); | | X_1495 := algebra.kdifference(X_1494,X_1437); | | X_1496 := algebra.leftjoin(X_19,X_1495); | | X_1497:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp5",0); | | X_1500:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp5",2); | | X_1502 := algebra.kdifference(X_1497,X_1500); | | X_1503 := algebra.kunion(X_1502,X_1500); | | X_1504:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp5",1); | | X_1506 := algebra.kunion(X_1503,X_1504); | | X_1507 := algebra.kdifference(X_1506,X_1437); | | X_1508 := algebra.leftjoin(X_19,X_1507); | | X_1509:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp6",0); | | X_1513:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp6",2); | | X_1514 := algebra.kdifference(X_1509,X_1513); | | X_1515 := algebra.kunion(X_1514,X_1513); | | X_1516:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp6",1); | | X_1517 := algebra.kunion(X_1515,X_1516); | | X_1518 := algebra.kdifference(X_1517,X_1437); | | X_1519 := algebra.leftjoin(X_19,X_1518); | | X_1520:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp7",0); | | X_1523:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp7",2); | | X_1525 := algebra.kdifference(X_1520,X_1523); | | X_1526 := algebra.kunion(X_1525,X_1523); | | X_1527:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp7",1); | | X_1529 := algebra.kunion(X_1526,X_1527); | | X_1530:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_1531 := bat.reverse(X_1530); | | X_1532 := algebra.kdifference(X_1529,X_1531); | | X_1534 := algebra.leftjoin(X_19,X_1532); | | X_1535:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp8",0); | | X_1538:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp8",2); | | X_1539 := algebra.kdifference(X_1535,X_1538); | | X_1540 := algebra.kunion(X_1539,X_1538); | | X_1541:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp8",1); | | X_1542 := algebra.kunion(X_1540,X_1541); | | X_1543 := algebra.kdifference(X_1542,X_1531); | | X_1544 := algebra.leftjoin(X_19,X_1543); | | X_1545:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp9",0); | | X_1548:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp9",2); | | X_1550 := algebra.kdifference(X_1545,X_1548); | | X_1551 := algebra.kunion(X_1550,X_1548); | | X_1552:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp9",1); | | X_1554 := algebra.kunion(X_1551,X_1552); | | X_1556 := algebra.kdifference(X_1554,X_1531); | | X_1557 := algebra.leftjoin(X_19,X_1556); | | X_1558:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp10",0); | | X_1561:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp10",2); | | X_1562 := algebra.kdifference(X_1558,X_1561); | | X_1563 := algebra.kunion(X_1562,X_1561); | | X_1564:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp10",1); | | X_1565 := algebra.kunion(X_1563,X_1564); | | X_1566 := algebra.kdifference(X_1565,X_1531); | | X_1567 := algebra.leftjoin(X_19,X_1566); | | X_1568:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp11",0); | | X_1571:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp11",2); | | X_1573 := algebra.kdifference(X_1568,X_1571); | | X_1574 := algebra.kunion(X_1573,X_1571); | | X_1575:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp11",1); | | X_1578 := algebra.kunion(X_1574,X_1575); | | X_1579 := algebra.kdifference(X_1578,X_1531); | | X_1580 := algebra.leftjoin(X_19,X_1579); | | X_1581:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp12",0); | | X_1584:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp12",2); | | X_1585 := algebra.kdifference(X_1581,X_1584); | | X_1586 := algebra.kunion(X_1585,X_1584); | | X_1587:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp12",1); | | X_1588 := algebra.kunion(X_1586,X_1587); | | X_1589 := algebra.kdifference(X_1588,X_1531); | | X_1590 := algebra.leftjoin(X_19,X_1589); | | X_1591:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp13",0); | | X_1594:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp13",2); | | X_1597 := algebra.kdifference(X_1591,X_1594); | | X_1598 := algebra.kunion(X_1597,X_1594); | | X_1599:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp13",1); | | X_1601 := algebra.kunion(X_1598,X_1599); | | X_1602 := algebra.kdifference(X_1601,X_1531); | | X_1603 := algebra.leftjoin(X_19,X_1602); | | X_1604:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp14",0); | | X_1607:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp14",2); | | X_1608 := algebra.kdifference(X_1604,X_1607); | | X_1609 := algebra.kunion(X_1608,X_1607); | | X_1610:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp14",1); | | X_1611 := algebra.kunion(X_1609,X_1610); | | X_1612 := algebra.kdifference(X_1611,X_1531); | | X_1613 := algebra.leftjoin(X_19,X_1612); | | X_1615:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp15",0); | | X_1618:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp15",2); | | X_1620 := algebra.kdifference(X_1615,X_1618); | | X_1621 := algebra.kunion(X_1620,X_1618); | | X_1622:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp15",1); | | X_1624 := algebra.kunion(X_1621,X_1622); | | X_1625:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_1626 := bat.reverse(X_1625); | | X_1627 := algebra.kdifference(X_1624,X_1626); | | X_1628 := algebra.leftjoin(X_19,X_1627); | | X_1629:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp16",0); | | X_1632:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp16",2); | | X_1633 := algebra.kdifference(X_1629,X_1632); | | X_1634 := algebra.kunion(X_1633,X_1632); | | X_1635:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp16",1); | | X_1636 := algebra.kunion(X_1634,X_1635); | | X_1637 := algebra.kdifference(X_1636,X_1626); | | X_1639 := algebra.leftjoin(X_19,X_1637); | | X_1640:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp17",0); | | X_1643:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp17",2); | | X_1645 := algebra.kdifference(X_1640,X_1643); | | X_1646 := algebra.kunion(X_1645,X_1643); | | X_1647:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp17",1); | | X_1649 := algebra.kunion(X_1646,X_1647); | | X_1650 := algebra.kdifference(X_1649,X_1626); | | X_1651 := algebra.leftjoin(X_19,X_1650); | | X_1652:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp18",0); | | X_1655:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp18",2); | | X_1656 := algebra.kdifference(X_1652,X_1655); | | X_1657 := algebra.kunion(X_1656,X_1655); | | X_1658:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp18",1); | | X_1660 := algebra.kunion(X_1657,X_1658); | | X_1661 := algebra.kdifference(X_1660,X_1626); | | X_1662 := algebra.leftjoin(X_19,X_1661); | | X_1663:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp19",0); | | X_1666:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp19",2); | | X_1668 := algebra.kdifference(X_1663,X_1666); | | X_1669 := algebra.kunion(X_1668,X_1666); | | X_1670:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp19",1); | | X_1672 := algebra.kunion(X_1669,X_1670); | | X_1673 := algebra.kdifference(X_1672,X_1626); | | X_1674 := algebra.leftjoin(X_19,X_1673); | | X_1675:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp20",0); | | X_1679:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp20",2); | | X_1680 := algebra.kdifference(X_1675,X_1679); | | X_1681 := algebra.kunion(X_1680,X_1679); | | X_1682:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp20",1); | | X_1683 := algebra.kunion(X_1681,X_1682); | | X_1684 := algebra.kdifference(X_1683,X_1626); | | X_1685 := algebra.leftjoin(X_19,X_1684); | | X_1686:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp21",0); | | X_1689:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp21",2); | | X_1691 := algebra.kdifference(X_1686,X_1689); | | X_1692 := algebra.kunion(X_1691,X_1689); | | X_1693:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp21",1); | | X_1695 := algebra.kunion(X_1692,X_1693); | | X_1696 := algebra.kdifference(X_1695,X_1626); | | X_1698 := algebra.leftjoin(X_19,X_1696); | | X_1699:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp22",0); | | X_1702:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp22",2); | | X_1703 := algebra.kdifference(X_1699,X_1702); | | X_1704 := algebra.kunion(X_1703,X_1702); | | X_1705:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp22",1); | | X_1706 := algebra.kunion(X_1704,X_1705); | | X_1707 := algebra.kdifference(X_1706,X_1626); | | X_1708 := algebra.leftjoin(X_19,X_1707); | | X_1709:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp23",0); | | X_1712:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp23",2); | | X_1714 := algebra.kdifference(X_1709,X_1712); | | X_1715 := algebra.kunion(X_1714,X_1712); | | X_1716:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp23",1); | | X_1718 := algebra.kunion(X_1715,X_1716); | | X_1719:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_1721 := bat.reverse(X_1719); | | X_1722 := algebra.kdifference(X_1718,X_1721); | | X_1723 := algebra.leftjoin(X_19,X_1722); | | X_1724:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp24",0); | | X_1727:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp24",2); | | X_1728 := algebra.kdifference(X_1724,X_1727); | | X_1729 := algebra.kunion(X_1728,X_1727); | | X_1730:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp24",1); | | X_1731 := algebra.kunion(X_1729,X_1730); | | X_1732 := algebra.kdifference(X_1731,X_1721); | | X_1733 := algebra.leftjoin(X_19,X_1732); | | X_1734:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp25",0); | | X_1737:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp25",2); | | X_1739 := algebra.kdifference(X_1734,X_1737); | | X_1740 := algebra.kunion(X_1739,X_1737); | | X_1741:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp25",1); | | X_1744 := algebra.kunion(X_1740,X_1741); | | X_1745 := algebra.kdifference(X_1744,X_1721); | | X_1746 := algebra.leftjoin(X_19,X_1745); | | X_1747:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp26",0); | | X_1750:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp26",2); | | X_1751 := algebra.kdifference(X_1747,X_1750); | | X_1752 := algebra.kunion(X_1751,X_1750); | | X_1753:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp26",1); | | X_1754 := algebra.kunion(X_1752,X_1753); | | X_1755 := algebra.kdifference(X_1754,X_1721); | | X_1756 := algebra.leftjoin(X_19,X_1755); | | X_1757:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp27",0); | | X_1760:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp27",2); | | X_1763 := algebra.kdifference(X_1757,X_1760); | | X_1764 := algebra.kunion(X_1763,X_1760); | | X_1765:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp27",1); | | X_1767 := algebra.kunion(X_1764,X_1765); | | X_1768 := algebra.kdifference(X_1767,X_1721); | | X_1769 := algebra.leftjoin(X_19,X_1768); | | X_1770:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp28",0); | | X_1773:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp28",2); | | X_1774 := algebra.kdifference(X_1770,X_1773); | | X_1775 := algebra.kunion(X_1774,X_1773); | | X_1776:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp28",1); | | X_1777 := algebra.kunion(X_1775,X_1776); | | X_1778 := algebra.kdifference(X_1777,X_1721); | | X_1779 := algebra.leftjoin(X_19,X_1778); | | X_1781:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp29",0); | | X_1784:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp29",2); | | X_1786 := algebra.kdifference(X_1781,X_1784); | | X_1787 := algebra.kunion(X_1786,X_1784); | | X_1788:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp29",1); | | X_1790 := algebra.kunion(X_1787,X_1788); | | X_1791 := algebra.kdifference(X_1790,X_1721); | | X_1792 := algebra.leftjoin(X_19,X_1791); | | X_1793:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp30",0); | | X_1796:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp30",2); | | X_1797 := algebra.kdifference(X_1793,X_1796); | | X_1798 := algebra.kunion(X_1797,X_1796); | | X_1799:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp30",1); | | X_1800 := algebra.kunion(X_1798,X_1799); | | X_1801 := algebra.kdifference(X_1800,X_1721); | | X_1803 := algebra.leftjoin(X_19,X_1801); | | X_1804:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp31",0); | | X_1807:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp31",2); | | X_1809 := algebra.kdifference(X_1804,X_1807); | | X_1810 := algebra.kunion(X_1809,X_1807); | | X_1811:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp31",1); | | X_1813 := algebra.kunion(X_1810,X_1811); | | X_1814:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_1815 := bat.reverse(X_1814); | | X_1816 := algebra.kdifference(X_1813,X_1815); | | X_1817 := algebra.leftjoin(X_19,X_1816); | | X_1818:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp32",0); | | X_1821:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp32",2); | | X_1822 := algebra.kdifference(X_1818,X_1821); | | X_1823 := algebra.kunion(X_1822,X_1821); | | X_1824:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp32",1); | | X_1826 := algebra.kunion(X_1823,X_1824); | | X_1827 := algebra.kdifference(X_1826,X_1815); | | X_1828 := algebra.leftjoin(X_19,X_1827); | | X_1829:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp33",0); | | X_1832:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp33",2); | | X_1834 := algebra.kdifference(X_1829,X_1832); | | X_1835 := algebra.kunion(X_1834,X_1832); | | X_1836:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp33",1); | | X_1838 := algebra.kunion(X_1835,X_1836); | | X_1839 := algebra.kdifference(X_1838,X_1815); | | X_1840 := algebra.leftjoin(X_19,X_1839); | | X_1841:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp34",0); | | X_1845:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp34",2); | | X_1846 := algebra.kdifference(X_1841,X_1845); | | X_1847 := algebra.kunion(X_1846,X_1845); | | X_1848:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp34",1); | | X_1849 := algebra.kunion(X_1847,X_1848); | | X_1850 := algebra.kdifference(X_1849,X_1815); | | X_1851 := algebra.leftjoin(X_19,X_1850); | | X_1852:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp35",0); | | X_1855:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp35",2); | | X_1857 := algebra.kdifference(X_1852,X_1855); | | X_1858 := algebra.kunion(X_1857,X_1855); | | X_1859:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp35",1); | | X_1861 := algebra.kunion(X_1858,X_1859); | | X_1862 := algebra.kdifference(X_1861,X_1815); | | X_1864 := algebra.leftjoin(X_19,X_1862); | | X_1865:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp36",0); | | X_1868:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp36",2); | | X_1869 := algebra.kdifference(X_1865,X_1868); | | X_1870 := algebra.kunion(X_1869,X_1868); | | X_1871:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp36",1); | | X_1872 := algebra.kunion(X_1870,X_1871); | | X_1873 := algebra.kdifference(X_1872,X_1815); | | X_1874 := algebra.leftjoin(X_19,X_1873); | | X_1875:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp37",0); | | X_1878:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp37",2); | | X_1880 := algebra.kdifference(X_1875,X_1878); | | X_1881 := algebra.kunion(X_1880,X_1878); | | X_1882:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp37",1); | | X_1884 := algebra.kunion(X_1881,X_1882); | | X_1886 := algebra.kdifference(X_1884,X_1815); | | X_1887 := algebra.leftjoin(X_19,X_1886); | | X_1888:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp38",0); | | X_1891:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp38",2); | | X_1892 := algebra.kdifference(X_1888,X_1891); | | X_1893 := algebra.kunion(X_1892,X_1891); | | X_1894:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp38",1); | | X_1895 := algebra.kunion(X_1893,X_1894); | | X_1896 := algebra.kdifference(X_1895,X_1815); | | X_1897 := algebra.leftjoin(X_19,X_1896); | | X_1898:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp39",0); | | X_1901:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp39",2); | | X_1903 := algebra.kdifference(X_1898,X_1901); | | X_1904 := algebra.kunion(X_1903,X_1901); | | X_1905:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp39",1); | | X_1908 := algebra.kunion(X_1904,X_1905); | | X_1909:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_1910 := bat.reverse(X_1909); | | X_1911 := algebra.kdifference(X_1908,X_1910); | | X_1912 := algebra.leftjoin(X_19,X_1911); | | X_1913:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp40",0); | | X_1916:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp40",2); | | X_1917 := algebra.kdifference(X_1913,X_1916); | | X_1918 := algebra.kunion(X_1917,X_1916); | | X_1919:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp40",1); | | X_1920 := algebra.kunion(X_1918,X_1919); | | X_1921 := algebra.kdifference(X_1920,X_1910); | | X_1922 := algebra.leftjoin(X_19,X_1921); | | X_1923:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp41",0); | | X_1926:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp41",2); | | X_1929 := algebra.kdifference(X_1923,X_1926); | | X_1930 := algebra.kunion(X_1929,X_1926); | | X_1931:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp41",1); | | X_1933 := algebra.kunion(X_1930,X_1931); | | X_1934 := algebra.kdifference(X_1933,X_1910); | | X_1935 := algebra.leftjoin(X_19,X_1934); | | X_1936:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp42",0); | | X_1939:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp42",2); | | X_1940 := algebra.kdifference(X_1936,X_1939); | | X_1941 := algebra.kunion(X_1940,X_1939); | | X_1942:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp42",1); | | X_1943 := algebra.kunion(X_1941,X_1942); | | X_1944 := algebra.kdifference(X_1943,X_1910); | | X_1945 := algebra.leftjoin(X_19,X_1944); | | X_1947:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp43",0); | | X_1950:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp43",2); | | X_1952 := algebra.kdifference(X_1947,X_1950); | | X_1953 := algebra.kunion(X_1952,X_1950); | | X_1954:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp43",1); | | X_1956 := algebra.kunion(X_1953,X_1954); | | X_1957 := algebra.kdifference(X_1956,X_1910); | | X_1958 := algebra.leftjoin(X_19,X_1957); | | X_1959:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp44",0); | | X_1962:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp44",2); | | X_1963 := algebra.kdifference(X_1959,X_1962); | | X_1964 := algebra.kunion(X_1963,X_1962); | | X_1965:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp44",1); | | X_1966 := algebra.kunion(X_1964,X_1965); | | X_1967 := algebra.kdifference(X_1966,X_1910); | | X_1969 := algebra.leftjoin(X_19,X_1967); | | X_1970:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp45",0); | | X_1973:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp45",2); | | X_1975 := algebra.kdifference(X_1970,X_1973); | | X_1976 := algebra.kunion(X_1975,X_1973); | | X_1977:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp45",1); | | X_1979 := algebra.kunion(X_1976,X_1977); | | X_1980 := algebra.kdifference(X_1979,X_1910); | | X_1981 := algebra.leftjoin(X_19,X_1980); | | X_1982:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp46",0); | | X_1985:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp46",2); | | X_1986 := algebra.kdifference(X_1982,X_1985); | | X_1987 := algebra.kunion(X_1986,X_1985); | | X_1988:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp46",1); | | X_1990 := algebra.kunion(X_1987,X_1988); | | X_1991 := algebra.kdifference(X_1990,X_1910); | | X_1992 := algebra.leftjoin(X_19,X_1991); | | X_1993:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp47",0); | | X_1996:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp47",2); | | X_1998 := algebra.kdifference(X_1993,X_1996); | | X_1999 := algebra.kunion(X_1998,X_1996); | | X_2000:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp47",1); | | X_2002 := algebra.kunion(X_1999,X_2000); | | X_2003:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_2004 := bat.reverse(X_2003); | | X_2005 := algebra.kdifference(X_2002,X_2004); | | X_2006 := algebra.leftjoin(X_19,X_2005); | | X_2007:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp48",0); | | X_2011:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp48",2); | | X_2012 := algebra.kdifference(X_2007,X_2011); | | X_2013 := algebra.kunion(X_2012,X_2011); | | X_2014:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp48",1); | | X_2015 := algebra.kunion(X_2013,X_2014); | | X_2016 := algebra.kdifference(X_2015,X_2004); | | X_2017 := algebra.leftjoin(X_19,X_2016); | | X_2018:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp49",0); | | X_2021:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp49",2); | | X_2023 := algebra.kdifference(X_2018,X_2021); | | X_2024 := algebra.kunion(X_2023,X_2021); | | X_2025:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp49",1); | | X_2027 := algebra.kunion(X_2024,X_2025); | | X_2028 := algebra.kdifference(X_2027,X_2004); | | X_2030 := algebra.leftjoin(X_19,X_2028); | | X_2031:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp50",0); | | X_2034:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp50",2); | | X_2035 := algebra.kdifference(X_2031,X_2034); | | X_2036 := algebra.kunion(X_2035,X_2034); | | X_2037:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp50",1); | | X_2038 := algebra.kunion(X_2036,X_2037); | | X_2039 := algebra.kdifference(X_2038,X_2004); | | X_2040 := algebra.leftjoin(X_19,X_2039); | | X_2041:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp51",0); | | X_2044:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp51",2); | | X_2046 := algebra.kdifference(X_2041,X_2044); | | X_2047 := algebra.kunion(X_2046,X_2044); | | X_2048:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp51",1); | | X_2050 := algebra.kunion(X_2047,X_2048); | | X_2052 := algebra.kdifference(X_2050,X_2004); | | X_2053 := algebra.leftjoin(X_19,X_2052); | | X_2054:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp52",0); | | X_2057:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp52",2); | | X_2058 := algebra.kdifference(X_2054,X_2057); | | X_2059 := algebra.kunion(X_2058,X_2057); | | X_2060:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp52",1); | | X_2061 := algebra.kunion(X_2059,X_2060); | | X_2062 := algebra.kdifference(X_2061,X_2004); | | X_2063 := algebra.leftjoin(X_19,X_2062); | | X_2064:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp53",0); | | X_2067:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp53",2); | | X_2069 := algebra.kdifference(X_2064,X_2067); | | X_2070 := algebra.kunion(X_2069,X_2067); | | X_2071:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp53",1); | | X_2074 := algebra.kunion(X_2070,X_2071); | | X_2075 := algebra.kdifference(X_2074,X_2004); | | X_2076 := algebra.leftjoin(X_19,X_2075); | | X_2077:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp54",0); | | X_2080:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp54",2); | | X_2081 := algebra.kdifference(X_2077,X_2080); | | X_2082 := algebra.kunion(X_2081,X_2080); | | X_2083:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp54",1); | | X_2084 := algebra.kunion(X_2082,X_2083); | | X_2085 := algebra.kdifference(X_2084,X_2004); | | X_2086 := algebra.leftjoin(X_19,X_2085); | | X_2087:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp55",0); | | X_2090:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp55",2); | | X_2093 := algebra.kdifference(X_2087,X_2090); | | X_2094 := algebra.kunion(X_2093,X_2090); | | X_2095:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp55",1); | | X_2097 := algebra.kunion(X_2094,X_2095); | | X_2098:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_2099 := bat.reverse(X_2098); | | X_2100 := algebra.kdifference(X_2097,X_2099); | | X_2101 := algebra.leftjoin(X_19,X_2100); | | X_2102:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp56",0); | | X_2105:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp56",2); | | X_2106 := algebra.kdifference(X_2102,X_2105); | | X_2107 := algebra.kunion(X_2106,X_2105); | | X_2108:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp56",1); | | X_2109 := algebra.kunion(X_2107,X_2108); | | X_2110 := algebra.kdifference(X_2109,X_2099); | | X_2111 := algebra.leftjoin(X_19,X_2110); | | X_2113:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp57",0); | | X_2116:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp57",2); | | X_2118 := algebra.kdifference(X_2113,X_2116); | | X_2119 := algebra.kunion(X_2118,X_2116); | | X_2120:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp57",1); | | X_2122 := algebra.kunion(X_2119,X_2120); | | X_2123 := algebra.kdifference(X_2122,X_2099); | | X_2124 := algebra.leftjoin(X_19,X_2123); | | X_2125:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp58",0); | | X_2128:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp58",2); | | X_2129 := algebra.kdifference(X_2125,X_2128); | | X_2130 := algebra.kunion(X_2129,X_2128); | | X_2131:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp58",1); | | X_2132 := algebra.kunion(X_2130,X_2131); | | X_2133 := algebra.kdifference(X_2132,X_2099); | | X_2135 := algebra.leftjoin(X_19,X_2133); | | X_2136:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp59",0); | | X_2139:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp59",2); | | X_2141 := algebra.kdifference(X_2136,X_2139); | | X_2142 := algebra.kunion(X_2141,X_2139); | | X_2143:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp59",1); | | X_2145 := algebra.kunion(X_2142,X_2143); | | X_2146 := algebra.kdifference(X_2145,X_2099); | | X_2147 := algebra.leftjoin(X_19,X_2146); | | X_2148:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp60",0); | | X_2151:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp60",2); | | X_2152 := algebra.kdifference(X_2148,X_2151); | | X_2153 := algebra.kunion(X_2152,X_2151); | | X_2154:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp60",1); | | X_2156 := algebra.kunion(X_2153,X_2154); | | X_2157 := algebra.kdifference(X_2156,X_2099); | | X_2158 := algebra.leftjoin(X_19,X_2157); | | X_2159:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp61",0); | | X_2162:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp61",2); | | X_2164 := algebra.kdifference(X_2159,X_2162); | | X_2165 := algebra.kunion(X_2164,X_2162); | | X_2166:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp61",1); | | X_2168 := algebra.kunion(X_2165,X_2166); | | X_2169 := algebra.kdifference(X_2168,X_2099); | | X_2170 := algebra.leftjoin(X_19,X_2169); | | X_2171:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp62",0); | | X_2175:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp62",2); | | X_2176 := algebra.kdifference(X_2171,X_2175); | | X_2177 := algebra.kunion(X_2176,X_2175); | | X_2178:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp62",1); | | X_2179 := algebra.kunion(X_2177,X_2178); | | X_2180 := algebra.kdifference(X_2179,X_2099); | | X_2181 := algebra.leftjoin(X_19,X_2180); | | X_2182:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp63",0); | | X_2185:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp63",2); | | X_2187 := algebra.kdifference(X_2182,X_2185); | | X_2188 := algebra.kunion(X_2187,X_2185); | | X_2189:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp63",1); | | X_2191 := algebra.kunion(X_2188,X_2189); | | X_2192:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_2193 := bat.reverse(X_2192); | | X_2194 := algebra.kdifference(X_2191,X_2193); | | X_2196 := algebra.leftjoin(X_19,X_2194); | | X_2197:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp64",0); | | X_2200:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp64",2); | | X_2201 := algebra.kdifference(X_2197,X_2200); | | X_2202 := algebra.kunion(X_2201,X_2200); | | X_2203:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp64",1); | | X_2204 := algebra.kunion(X_2202,X_2203); | | X_2205 := algebra.kdifference(X_2204,X_2193); | | X_2206 := algebra.leftjoin(X_19,X_2205); | | X_2207:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp65",0); | | X_2210:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp65",2); | | X_2212 := algebra.kdifference(X_2207,X_2210); | | X_2213 := algebra.kunion(X_2212,X_2210); | | X_2214:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp65",1); | | X_2216 := algebra.kunion(X_2213,X_2214); | | X_2218 := algebra.kdifference(X_2216,X_2193); | | X_2219 := algebra.leftjoin(X_19,X_2218); | | X_2220:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp66",0); | | X_2223:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp66",2); | | X_2224 := algebra.kdifference(X_2220,X_2223); | | X_2225 := algebra.kunion(X_2224,X_2223); | | X_2226:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp66",1); | | X_2227 := algebra.kunion(X_2225,X_2226); | | X_2228 := algebra.kdifference(X_2227,X_2193); | | X_2229 := algebra.leftjoin(X_19,X_2228); | | X_2230:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp67",0); | | X_2233:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp67",2); | | X_2235 := algebra.kdifference(X_2230,X_2233); | | X_2236 := algebra.kunion(X_2235,X_2233); | | X_2237:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp67",1); | | X_2240 := algebra.kunion(X_2236,X_2237); | | X_2241 := algebra.kdifference(X_2240,X_2193); | | X_2242 := algebra.leftjoin(X_19,X_2241); | | X_2243:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp68",0); | | X_2246:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp68",2); | | X_2247 := algebra.kdifference(X_2243,X_2246); | | X_2248 := algebra.kunion(X_2247,X_2246); | | X_2249:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp68",1); | | X_2250 := algebra.kunion(X_2248,X_2249); | | X_2251 := algebra.kdifference(X_2250,X_2193); | | X_2252 := algebra.leftjoin(X_19,X_2251); | | X_2253:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp69",0); | | X_2256:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp69",2); | | X_2259 := algebra.kdifference(X_2253,X_2256); | | X_2260 := algebra.kunion(X_2259,X_2256); | | X_2261:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp69",1); | | X_2263 := algebra.kunion(X_2260,X_2261); | | X_2264 := algebra.kdifference(X_2263,X_2193); | | X_2265 := algebra.leftjoin(X_19,X_2264); | | X_2266:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp70",0); | | X_2269:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp70",2); | | X_2270 := algebra.kdifference(X_2266,X_2269); | | X_2271 := algebra.kunion(X_2270,X_2269); | | X_2272:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp70",1); | | X_2273 := algebra.kunion(X_2271,X_2272); | | X_2274 := algebra.kdifference(X_2273,X_2193); | | X_2275 := algebra.leftjoin(X_19,X_2274); | | X_2277:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp71",0); | | X_2280:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp71",2); | | X_2282 := algebra.kdifference(X_2277,X_2280); | | X_2283 := algebra.kunion(X_2282,X_2280); | | X_2284:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp71",1); | | X_2286 := algebra.kunion(X_2283,X_2284); | | X_2287:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_2288 := bat.reverse(X_2287); | | X_2289 := algebra.kdifference(X_2286,X_2288); | | X_2290 := algebra.leftjoin(X_19,X_2289); | | X_2291:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp72",0); | | X_2294:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp72",2); | | X_2295 := algebra.kdifference(X_2291,X_2294); | | X_2296 := algebra.kunion(X_2295,X_2294); | | X_2297:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp72",1); | | X_2298 := algebra.kunion(X_2296,X_2297); | | X_2299 := algebra.kdifference(X_2298,X_2288); | | X_2301 := algebra.leftjoin(X_19,X_2299); | | X_2302:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp73",0); | | X_2305:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp73",2); | | X_2307 := algebra.kdifference(X_2302,X_2305); | | X_2308 := algebra.kunion(X_2307,X_2305); | | X_2309:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp73",1); | | X_2311 := algebra.kunion(X_2308,X_2309); | | X_2312 := algebra.kdifference(X_2311,X_2288); | | X_2313 := algebra.leftjoin(X_19,X_2312); | | X_2314:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp74",0); | | X_2317:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp74",2); | | X_2318 := algebra.kdifference(X_2314,X_2317); | | X_2319 := algebra.kunion(X_2318,X_2317); | | X_2320:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp74",1); | | X_2322 := algebra.kunion(X_2319,X_2320); | | X_2323 := algebra.kdifference(X_2322,X_2288); | | X_2324 := algebra.leftjoin(X_19,X_2323); | | X_2325:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp75",0); | | X_2328:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp75",2); | | X_2330 := algebra.kdifference(X_2325,X_2328); | | X_2331 := algebra.kunion(X_2330,X_2328); | | X_2332:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp75",1); | | X_2334 := algebra.kunion(X_2331,X_2332); | | X_2335 := algebra.kdifference(X_2334,X_2288); | | X_2336 := algebra.leftjoin(X_19,X_2335); | | X_2337:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp76",0); | | X_2341:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp76",2); | | X_2342 := algebra.kdifference(X_2337,X_2341); | | X_2343 := algebra.kunion(X_2342,X_2341); | | X_2344:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp76",1); | | X_2345 := algebra.kunion(X_2343,X_2344); | | X_2346 := algebra.kdifference(X_2345,X_2288); | | X_2347 := algebra.leftjoin(X_19,X_2346); | | X_2348:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp77",0); | | X_2351:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp77",2); | | X_2353 := algebra.kdifference(X_2348,X_2351); | | X_2354 := algebra.kunion(X_2353,X_2351); | | X_2355:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp77",1); | | X_2357 := algebra.kunion(X_2354,X_2355); | | X_2358 := algebra.kdifference(X_2357,X_2288); | | X_2360 := algebra.leftjoin(X_19,X_2358); | | X_2361:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp78",0); | | X_2364:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp78",2); | | X_2365 := algebra.kdifference(X_2361,X_2364); | | X_2366 := algebra.kunion(X_2365,X_2364); | | X_2367:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp78",1); | | X_2368 := algebra.kunion(X_2366,X_2367); | | X_2369 := algebra.kdifference(X_2368,X_2288); | | X_2370 := algebra.leftjoin(X_19,X_2369); | | X_2371:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp79",0); | | X_2374:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp79",2); | | X_2376 := algebra.kdifference(X_2371,X_2374); | | X_2377 := algebra.kunion(X_2376,X_2374); | | X_2378:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp79",1); | | X_2380 := algebra.kunion(X_2377,X_2378); | | X_2381:bat[:oid,:oid] := sql.bind_dbat(X_2,"sys","household",1); | | X_2383 := bat.reverse(X_2381); | | X_2384 := algebra.kdifference(X_2380,X_2383); | | X_2385 := algebra.leftjoin(X_19,X_2384); | | X_2386:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp80",0); | | X_2389:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp80",2); | | X_2390 := algebra.kdifference(X_2386,X_2389); | | X_2391 := algebra.kunion(X_2390,X_2389); | | X_2392:bat[:oid,:int] := sql.bind(X_2,"sys","household","wgtp80",1); | | X_2393 := algebra.kunion(X_2391,X_2392); | | X_2394 := algebra.kdifference(X_2393,X_2383); | | X_2395 := algebra.leftjoin(X_19,X_2394); | | exit X_3114; | | sql.rsColumn(X_2396,"sys.household","rt","varchar",255,0,X_20); | | sql.rsColumn(X_2396,"sys.household","serialno","int",32,0,X_31); | | sql.rsColumn(X_2396,"sys.household","division","int",32,0,X_43); | | sql.rsColumn(X_2396,"sys.household","puma","int",32,0,X_54); | | sql.rsColumn(X_2396,"sys.household","region","int",32,0,X_67); | | sql.rsColumn(X_2396,"sys.household","st","int",32,0,X_77); | | sql.rsColumn(X_2396,"sys.household","adjhsg","int",32,0,X_90); | | sql.rsColumn(X_2396,"sys.household","adjinc","int",32,0,X_100); | | sql.rsColumn(X_2396,"sys.household","wgtp","int",32,0,X_115); | | sql.rsColumn(X_2396,"sys.household","np","int",32,0,X_125); | | sql.rsColumn(X_2396,"sys.household","zzzz","int",32,0,X_138); | | sql.rsColumn(X_2396,"sys.household","acr","int",32,0,X_149); | | sql.rsColumn(X_2396,"sys.household","ags","int",32,0,X_161); | | sql.rsColumn(X_2396,"sys.household","bath","int",32,0,X_172); | | sql.rsColumn(X_2396,"sys.household","bdsp","int",32,0,X_184); | | sql.rsColumn(X_2396,"sys.household","bld","int",32,0,X_195); | | sql.rsColumn(X_2396,"sys.household","bus","int",32,0,X_210); | | sql.rsColumn(X_2396,"sys.household","conp","int",32,0,X_220); | | sql.rsColumn(X_2396,"sys.household","elep","int",32,0,X_233); | | sql.rsColumn(X_2396,"sys.household","fs","int",32,0,X_243); | | sql.rsColumn(X_2396,"sys.household","fulp","int",32,0,X_256); | | sql.rsColumn(X_2396,"sys.household","gasp","int",32,0,X_266); | | sql.rsColumn(X_2396,"sys.household","hfl","int",32,0,X_279); | | sql.rsColumn(X_2396,"sys.household","insp","int",32,0,X_289); | | sql.rsColumn(X_2396,"sys.household","mhp","int",32,0,X_304); | | sql.rsColumn(X_2396,"sys.household","mrgi","int",32,0,X_315); | | sql.rsColumn(X_2396,"sys.household","mrgp","int",32,0,X_327); | | sql.rsColumn(X_2396,"sys.household","mrgt","int",32,0,X_338); | | sql.rsColumn(X_2396,"sys.household","mrgx","int",32,0,X_350); | | sql.rsColumn(X_2396,"sys.household","refr","int",32,0,X_361); | | sql.rsColumn(X_2396,"sys.household","rmsp","int",32,0,X_374); | | sql.rsColumn(X_2396,"sys.household","rntm","int",32,0,X_384); | | sql.rsColumn(X_2396,"sys.household","rntp","int",32,0,X_399); | | sql.rsColumn(X_2396,"sys.household","rwat","int",32,0,X_409); | | sql.rsColumn(X_2396,"sys.household","sink","int",32,0,X_422); | | sql.rsColumn(X_2396,"sys.household","smp","int",32,0,X_432); | | sql.rsColumn(X_2396,"sys.household","stov","int",32,0,X_445); | | sql.rsColumn(X_2396,"sys.household","tel","int",32,0,X_455); | | sql.rsColumn(X_2396,"sys.household","ten","int",32,0,X_468); | | sql.rsColumn(X_2396,"sys.household","toil","int",32,0,X_479); | | sql.rsColumn(X_2396,"sys.household","vacs","int",32,0,X_493); | | sql.rsColumn(X_2396,"sys.household","valp","int",32,0,X_504); | | sql.rsColumn(X_2396,"sys.household","veh","int",32,0,X_516); | | sql.rsColumn(X_2396,"sys.household","watp","int",32,0,X_527); | | sql.rsColumn(X_2396,"sys.household","ybl","int",32,0,X_540); | | sql.rsColumn(X_2396,"sys.household","fes","int",32,0,X_550); | | sql.rsColumn(X_2396,"sys.household","fincp","int",32,0,X_563); | | sql.rsColumn(X_2396,"sys.household","fparc","int",32,0,X_573); | | sql.rsColumn(X_2396,"sys.household","grntp","int",32,0,X_588); | | sql.rsColumn(X_2396,"sys.household","grpip","int",32,0,X_598); | | sql.rsColumn(X_2396,"sys.household","hhl","int",32,0,X_611); | | sql.rsColumn(X_2396,"sys.household","hht","int",32,0,X_621); | | sql.rsColumn(X_2396,"sys.household","hincp","int",32,0,X_634); | | sql.rsColumn(X_2396,"sys.household","hugcl","int",32,0,X_645); | | sql.rsColumn(X_2396,"sys.household","hupac","int",32,0,X_657); | | sql.rsColumn(X_2396,"sys.household","hupaoc","int",32,0,X_668); | | sql.rsColumn(X_2396,"sys.household","huparc","int",32,0,X_682); | | sql.rsColumn(X_2396,"sys.household","kit","int",32,0,X_693); | | sql.rsColumn(X_2396,"sys.household","lngi","int",32,0,X_706); | | sql.rsColumn(X_2396,"sys.household","multg","int",32,0,X_716); | | sql.rsColumn(X_2396,"sys.household","mv","int",32,0,X_729); | | sql.rsColumn(X_2396,"sys.household","noc","int",32,0,X_739); | | sql.rsColumn(X_2396,"sys.household","npf","int",32,0,X_752); | | sql.rsColumn(X_2396,"sys.household","npp","int",32,0,X_762); | | sql.rsColumn(X_2396,"sys.household","nr","int",32,0,X_777); | | sql.rsColumn(X_2396,"sys.household","nrc","int",32,0,X_787); | | sql.rsColumn(X_2396,"sys.household","ocpip","int",32,0,X_800); | | sql.rsColumn(X_2396,"sys.household","partner","int",32,0,X_811); | | sql.rsColumn(X_2396,"sys.household","plm","int",32,0,X_823); | | sql.rsColumn(X_2396,"sys.household","psf","int",32,0,X_834); | | sql.rsColumn(X_2396,"sys.household","r18","int",32,0,X_846); | | sql.rsColumn(X_2396,"sys.household","r60","int",32,0,X_857); | | sql.rsColumn(X_2396,"sys.household","r65","int",32,0,X_872); | | sql.rsColumn(X_2396,"sys.household","resmode","int",32,0,X_882); | | sql.rsColumn(X_2396,"sys.household","smocp","int",32,0,X_895); | | sql.rsColumn(X_2396,"sys.household","smx","int",32,0,X_905); | | sql.rsColumn(X_2396,"sys.household","srnt","int",32,0,X_918); | | sql.rsColumn(X_2396,"sys.household","sval","int",32,0,X_928); | | sql.rsColumn(X_2396,"sys.household","taxp","int",32,0,X_941); | | sql.rsColumn(X_2396,"sys.household","wif","int",32,0,X_951); | | sql.rsColumn(X_2396,"sys.household","wkexrel","int",32,0,X_966); | | sql.rsColumn(X_2396,"sys.household","workstat","int",32,0,X_977); | | sql.rsColumn(X_2396,"sys.household","facrp","int",32,0,X_989); | | sql.rsColumn(X_2396,"sys.household","fagsp","int",32,0,X_1000); | | sql.rsColumn(X_2396,"sys.household","fbathp","int",32,0,X_1012); | | sql.rsColumn(X_2396,"sys.household","fbdsp","int",32,0,X_1023); | | sql.rsColumn(X_2396,"sys.household","fbldp","int",32,0,X_1036); | | sql.rsColumn(X_2396,"sys.household","fbusp","int",32,0,X_1046); | | sql.rsColumn(X_2396,"sys.household","fconp","int",32,0,X_1061); | | sql.rsColumn(X_2396,"sys.household","felep","int",32,0,X_1071); | | sql.rsColumn(X_2396,"sys.household","ffsp","int",32,0,X_1084); | | sql.rsColumn(X_2396,"sys.household","ffulp","int",32,0,X_1094); | | sql.rsColumn(X_2396,"sys.household","fgasp","int",32,0,X_1107); | | sql.rsColumn(X_2396,"sys.household","fhflp","int",32,0,X_1117); | | sql.rsColumn(X_2396,"sys.household","finsp","int",32,0,X_1130); | | sql.rsColumn(X_2396,"sys.household","fkitp","int",32,0,X_1141); | | sql.rsColumn(X_2396,"sys.household","fmhp","int",32,0,X_1155); | | sql.rsColumn(X_2396,"sys.household","fmrgip","int",32,0,X_1166); | | sql.rsColumn(X_2396,"sys.household","fmrgp","int",32,0,X_1178); | | sql.rsColumn(X_2396,"sys.household","fmrgtp","int",32,0,X_1189); | | sql.rsColumn(X_2396,"sys.household","fmrgxp","int",32,0,X_1202); | | sql.rsColumn(X_2396,"sys.household","fmvp","int",32,0,X_1212); | | sql.rsColumn(X_2396,"sys.household","fplmp","int",32,0,X_1225); | | sql.rsColumn(X_2396,"sys.household","frefrp","int",32,0,X_1235); | | sql.rsColumn(X_2396,"sys.household","frmsp","int",32,0,X_1250); | | sql.rsColumn(X_2396,"sys.household","frntmp","int",32,0,X_1260); | | sql.rsColumn(X_2396,"sys.household","frntp","int",32,0,X_1273); | | sql.rsColumn(X_2396,"sys.household","frwatp","int",32,0,X_1283); | | sql.rsColumn(X_2396,"sys.household","fsinkp","int",32,0,X_1296); | | sql.rsColumn(X_2396,"sys.household","fsmp","int",32,0,X_1307); | | sql.rsColumn(X_2396,"sys.household","fsmxhp","int",32,0,X_1319); | | sql.rsColumn(X_2396,"sys.household","fsmxsp","int",32,0,X_1330); | | sql.rsColumn(X_2396,"sys.household","fstovp","int",32,0,X_1344); | | sql.rsColumn(X_2396,"sys.household","ftaxp","int",32,0,X_1355); | | sql.rsColumn(X_2396,"sys.household","ftelp","int",32,0,X_1368); | | sql.rsColumn(X_2396,"sys.household","ftenp","int",32,0,X_1378); | | sql.rsColumn(X_2396,"sys.household","ftoilp","int",32,0,X_1391); | | sql.rsColumn(X_2396,"sys.household","fvacsp","int",32,0,X_1401); | | sql.rsColumn(X_2396,"sys.household","fvalp","int",32,0,X_1414); | | sql.rsColumn(X_2396,"sys.household","fvehp","int",32,0,X_1424); | | sql.rsColumn(X_2396,"sys.household","fwatp","int",32,0,X_1439); | | sql.rsColumn(X_2396,"sys.household","fyblp","int",32,0,X_1449); | | sql.rsColumn(X_2396,"sys.household","wgtp1","int",32,0,X_1462); | | sql.rsColumn(X_2396,"sys.household","wgtp2","int",32,0,X_1473); | | sql.rsColumn(X_2396,"sys.household","wgtp3","int",32,0,X_1485); | | sql.rsColumn(X_2396,"sys.household","wgtp4","int",32,0,X_1496); | | sql.rsColumn(X_2396,"sys.household","wgtp5","int",32,0,X_1508); | | sql.rsColumn(X_2396,"sys.household","wgtp6","int",32,0,X_1519); | | sql.rsColumn(X_2396,"sys.household","wgtp7","int",32,0,X_1534); | | sql.rsColumn(X_2396,"sys.household","wgtp8","int",32,0,X_1544); | | sql.rsColumn(X_2396,"sys.household","wgtp9","int",32,0,X_1557); | | sql.rsColumn(X_2396,"sys.household","wgtp10","int",32,0,X_1567); | | sql.rsColumn(X_2396,"sys.household","wgtp11","int",32,0,X_1580); | | sql.rsColumn(X_2396,"sys.household","wgtp12","int",32,0,X_1590); | | sql.rsColumn(X_2396,"sys.household","wgtp13","int",32,0,X_1603); | | sql.rsColumn(X_2396,"sys.household","wgtp14","int",32,0,X_1613); | | sql.rsColumn(X_2396,"sys.household","wgtp15","int",32,0,X_1628); | | sql.rsColumn(X_2396,"sys.household","wgtp16","int",32,0,X_1639); | | sql.rsColumn(X_2396,"sys.household","wgtp17","int",32,0,X_1651); | | sql.rsColumn(X_2396,"sys.household","wgtp18","int",32,0,X_1662); | | sql.rsColumn(X_2396,"sys.household","wgtp19","int",32,0,X_1674); | | sql.rsColumn(X_2396,"sys.household","wgtp20","int",32,0,X_1685); | | sql.rsColumn(X_2396,"sys.household","wgtp21","int",32,0,X_1698); | | sql.rsColumn(X_2396,"sys.household","wgtp22","int",32,0,X_1708); | | sql.rsColumn(X_2396,"sys.household","wgtp23","int",32,0,X_1723); | | sql.rsColumn(X_2396,"sys.household","wgtp24","int",32,0,X_1733); | | sql.rsColumn(X_2396,"sys.household","wgtp25","int",32,0,X_1746); | | sql.rsColumn(X_2396,"sys.household","wgtp26","int",32,0,X_1756); | | sql.rsColumn(X_2396,"sys.household","wgtp27","int",32,0,X_1769); | | sql.rsColumn(X_2396,"sys.household","wgtp28","int",32,0,X_1779); | | sql.rsColumn(X_2396,"sys.household","wgtp29","int",32,0,X_1792); | | sql.rsColumn(X_2396,"sys.household","wgtp30","int",32,0,X_1803); | | sql.rsColumn(X_2396,"sys.household","wgtp31","int",32,0,X_1817); | | sql.rsColumn(X_2396,"sys.household","wgtp32","int",32,0,X_1828); | | sql.rsColumn(X_2396,"sys.household","wgtp33","int",32,0,X_1840); | | sql.rsColumn(X_2396,"sys.household","wgtp34","int",32,0,X_1851); | | sql.rsColumn(X_2396,"sys.household","wgtp35","int",32,0,X_1864); | | sql.rsColumn(X_2396,"sys.household","wgtp36","int",32,0,X_1874); | | sql.rsColumn(X_2396,"sys.household","wgtp37","int",32,0,X_1887); | | sql.rsColumn(X_2396,"sys.household","wgtp38","int",32,0,X_1897); | | sql.rsColumn(X_2396,"sys.household","wgtp39","int",32,0,X_1912); | | sql.rsColumn(X_2396,"sys.household","wgtp40","int",32,0,X_1922); | | sql.rsColumn(X_2396,"sys.household","wgtp41","int",32,0,X_1935); | | sql.rsColumn(X_2396,"sys.household","wgtp42","int",32,0,X_1945); | | sql.rsColumn(X_2396,"sys.household","wgtp43","int",32,0,X_1958); | | sql.rsColumn(X_2396,"sys.household","wgtp44","int",32,0,X_1969); | | sql.rsColumn(X_2396,"sys.household","wgtp45","int",32,0,X_1981); | | sql.rsColumn(X_2396,"sys.household","wgtp46","int",32,0,X_1992); | | sql.rsColumn(X_2396,"sys.household","wgtp47","int",32,0,X_2006); | | sql.rsColumn(X_2396,"sys.household","wgtp48","int",32,0,X_2017); | | sql.rsColumn(X_2396,"sys.household","wgtp49","int",32,0,X_2030); | | sql.rsColumn(X_2396,"sys.household","wgtp50","int",32,0,X_2040); | | sql.rsColumn(X_2396,"sys.household","wgtp51","int",32,0,X_2053); | | sql.rsColumn(X_2396,"sys.household","wgtp52","int",32,0,X_2063); | | sql.rsColumn(X_2396,"sys.household","wgtp53","int",32,0,X_2076); | | sql.rsColumn(X_2396,"sys.household","wgtp54","int",32,0,X_2086); | | sql.rsColumn(X_2396,"sys.household","wgtp55","int",32,0,X_2101); | | sql.rsColumn(X_2396,"sys.household","wgtp56","int",32,0,X_2111); | | sql.rsColumn(X_2396,"sys.household","wgtp57","int",32,0,X_2124); | | sql.rsColumn(X_2396,"sys.household","wgtp58","int",32,0,X_2135); | | sql.rsColumn(X_2396,"sys.household","wgtp59","int",32,0,X_2147); | | sql.rsColumn(X_2396,"sys.household","wgtp60","int",32,0,X_2158); | | sql.rsColumn(X_2396,"sys.household","wgtp61","int",32,0,X_2170); | | sql.rsColumn(X_2396,"sys.household","wgtp62","int",32,0,X_2181); | | sql.rsColumn(X_2396,"sys.household","wgtp63","int",32,0,X_2196); | | sql.rsColumn(X_2396,"sys.household","wgtp64","int",32,0,X_2206); | | sql.rsColumn(X_2396,"sys.household","wgtp65","int",32,0,X_2219); | | sql.rsColumn(X_2396,"sys.household","wgtp66","int",32,0,X_2229); | | sql.rsColumn(X_2396,"sys.household","wgtp67","int",32,0,X_2242); | | sql.rsColumn(X_2396,"sys.household","wgtp68","int",32,0,X_2252); | | sql.rsColumn(X_2396,"sys.household","wgtp69","int",32,0,X_2265); | | sql.rsColumn(X_2396,"sys.household","wgtp70","int",32,0,X_2275); | | sql.rsColumn(X_2396,"sys.household","wgtp71","int",32,0,X_2290); | | sql.rsColumn(X_2396,"sys.household","wgtp72","int",32,0,X_2301); | | sql.rsColumn(X_2396,"sys.household","wgtp73","int",32,0,X_2313); | | sql.rsColumn(X_2396,"sys.household","wgtp74","int",32,0,X_2324); | | sql.rsColumn(X_2396,"sys.household","wgtp75","int",32,0,X_2336); | | sql.rsColumn(X_2396,"sys.household","wgtp76","int",32,0,X_2347); | | sql.rsColumn(X_2396,"sys.household","wgtp77","int",32,0,X_2360); | | sql.rsColumn(X_2396,"sys.household","wgtp78","int",32,0,X_2370); | | sql.rsColumn(X_2396,"sys.household","wgtp79","int",32,0,X_2385); | | sql.rsColumn(X_2396,"sys.household","wgtp80","int",32,0,X_2395); | | X_2861 := io.stdout(); | | sql.exportResult(X_2861,X_2396); | | end s4_1; | +----------------------------------------------------------------------------+ +------+----------+----------+------+--------+------+---------+---------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+--------+------+------+------+------+-------+-------+-------+-------+------+------+-------+-------+-------+--------+--------+------+------+-------+------+------+------+------+------+------+-------+---------+------+------+------+------+------+---------+-------+------+------+------+------+------+---------+----------+-------+-------+--------+-------+-------+-------+-------+-------+------+-------+-------+-------+-------+-------+------+--------+-------+--------+--------+------+-------+--------+-------+--------+-------+--------+--------+------+--------+--------+--------+-------+-------+-------+--------+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+ | rt | serialno | division | puma | region | st | adjhsg | adjinc | wgtp | np | zzzz | acr | ags | bath | bdsp | bld | bus | conp | elep | fs | fulp | gasp | hfl | insp | mhp | mrgi | mrgp | mrgt | mrgx | refr | rmsp | rntm | rntp | rwat | sink | smp | stov | tel | ten | toil | vacs | valp | veh | watp | ybl | fes | fincp | fparc | grntp | grpip | hhl | hht | hincp | hugcl | hupac | hupaoc | huparc | kit | lngi | multg | mv | noc | npf | npp | nr | nrc | ocpip | partner | plm | psf | r18 | r60 | r65 | resmode | smocp | smx | srnt | sval | taxp | wif | wkexrel | workstat | facrp | fagsp | fbathp | fbdsp | fbldp | fbusp | fconp | felep | ffsp | ffulp | fgasp | fhflp | finsp | fkitp | fmhp | fmrgip | fmrgp | fmrgtp | fmrgxp | fmvp | fplmp | frefrp | frmsp | frntmp | frntp | frwatp | fsinkp | fsmp | fsmxhp | fsmxsp | fstovp | ftaxp | ftelp | ftenp | ftoilp | fvacsp | fvalp | fvehp | fwatp | fyblp | wgtp1 | wgtp2 | wgtp3 | wgtp4 | wgtp5 | wgtp6 | wgtp7 | wgtp8 | wgtp9 | wgtp10 | wgtp11 | wgtp12 | wgtp13 | wgtp14 | wgtp15 | wgtp16 | wgtp17 | wgtp18 | wgtp19 | wgtp20 | wgtp21 | wgtp22 | wgtp23 | wgtp24 | wgtp25 | wgtp26 | wgtp27 | wgtp28 | wgtp29 | wgtp30 | wgtp31 | wgtp32 | wgtp33 | wgtp34 | wgtp35 | wgtp36 | wgtp37 | wgtp38 | wgtp39 | wgtp40 | wgtp41 | wgtp42 | wgtp43 | wgtp44 | wgtp45 | wgtp46 | wgtp47 | wgtp48 | wgtp49 | wgtp50 | wgtp51 | wgtp52 | wgtp53 | wgtp54 | wgtp55 | wgtp56 | wgtp57 | wgtp58 | wgtp59 | wgtp60 | wgtp61 | wgtp62 | wgtp63 | wgtp64 | wgtp65 | wgtp66 | wgtp67 | wgtp68 | wgtp69 | wgtp70 | wgtp71 | wgtp72 | wgtp73 | wgtp74 | wgtp75 | wgtp76 | wgtp77 | wgtp78 | wgtp79 | wgtp80 | +======+==========+==========+======+========+======+=========+=========+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+========+======+======+======+======+=======+=======+=======+=======+======+======+=======+=======+=======+========+========+======+======+=======+======+======+======+======+======+======+=======+=========+======+======+======+======+======+=========+=======+======+======+======+======+======+=========+==========+=======+=======+========+=======+=======+=======+=======+=======+======+=======+=======+=======+=======+=======+======+========+=======+========+========+======+=======+========+=======+========+=======+========+========+======+========+========+========+=======+=======+=======+========+========+=======+=======+=======+=======+=======+=======+=======+=======+=======+=======+=======+=======+=======+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+ | H | 1890 | 9 | 400 | 4 | 2 | 1000000 | 1007624 | 46 | 2 | 1 | null | null | 1 | 1 | 6 | null | null | 1 | 2 | 1 | 3 | 4 | null | null | null | null | null | null | 1 | 2 | 2 | 600 | 1 | 1 | null | 1 | 1 | 3 | 1 | null | null | 1 | 1 | 3 | null | null | null | 600 | 21 | 1 | 7 | 34700 | 0 | 4 | 4 | 4 | 1 | 1 | 1 | 3 | 0 | null | 0 | 1 | 0 | null | 0 | 1 | 0 | 0 | 0 | 0 | 2 | null | null | 1 | 0 | null | null | null | null | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 10 | 16 | 10 | 42 | 61 | 44 | 54 | 45 | 71 | 67 | 112 | 50 | 15 | 41 | 111 | 79 | 37 | 67 | 38 | 40 | 81 | 95 | 70 | 81 | 51 | 40 | 38 | 47 | 15 | 22 | 18 | 34 | 95 | 55 | 14 | 51 | 48 | 18 | 43 | 12 | 7 | 13 | 15 | 57 | 72 | 55 | 48 | 50 | 75 | 80 | 116 | 51 | 14 | 38 | 126 | 57 | 30 | 93 | 29 | 53 | 80 | 55 | 71 | 46 | 38 | 57 | 39 | 47 | 16 | 16 | 20 | 50 | 91 | 58 | 20 | 72 | 43 | 11 | 48 | 9 | | H | 2029 | 9 | 101 | 4 | 2 | 1000000 | 1007624 | 269 | 4 | 1 | 1 | null | 1 | 4 | 2 | 2 | null | 80 | 2 | 2 | 80 | 1 | 1500 | null | 1 | 920 | 1 | 1 | 1 | 7 | null | null | 1 | 1 | null | 1 | 1 | 1 | 1 | null | 200000 | 1 | 200 | 4 | 8 | 47100 | 2 | null | null | 1 | 3 | 47100 | 1 | 2 | 4 | 2 | 1 | 1 | 2 | 7 | 0 | 4 | 0 | 0 | 2 | 28 | 0 | 1 | 1 | 1 | 1 | 1 | 2 | 1097 | 3 | 0 | 1 | 34 | 1 | 15 | 15 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 252 | 470 | 264 | 430 | 228 | 243 | 192 | 107 | 265 | 79 | 266 | 268 | 68 | 335 | 503 | 116 | 95 | 389 | 228 | 114 | 254 | 71 | 225 | 116 | 289 | 291 | 233 | 539 | 310 | 423 | 262 | 346 | 511 | 235 | 79 | 407 | 420 | 121 | 223 | 90 | 250 | 70 | 240 | 101 | 259 | 326 | 245 | 461 | 241 | 480 | 315 | 275 | 286 | 338 | 118 | 363 | 409 | 87 | 238 | 418 | 278 | 322 | 297 | 486 | 376 | 262 | 198 | 95 | 259 | 104 | 238 | 309 | 135 | 230 | 408 | 117 | 83 | 497 | 244 | 418 | +------+----------+----------+------+--------+------+---------+---------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+--------+------+------+------+------+-------+-------+-------+-------+------+------+-------+-------+-------+--------+--------+------+------+-------+------+------+------+------+------+------+-------+---------+------+------+------+------+------+---------+-------+------+------+------+------+------+---------+----------+-------+-------+--------+-------+-------+-------+-------+-------+------+-------+-------+-------+-------+-------+------+--------+-------+--------+--------+------+-------+--------+-------+--------+-------+--------+--------+------+--------+--------+--------+-------+-------+-------+--------+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+ +------+----------+----------+------+--------+------+---------+---------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+--------+------+------+------+------+-------+-------+-------+-------+------+------+-------+-------+-------+--------+--------+------+------+-------+------+------+------+------+------+------+-------+---------+------+------+------+------+------+---------+-------+------+------+------+------+------+---------+----------+-------+-------+--------+-------+-------+-------+-------+-------+------+-------+-------+-------+-------+-------+------+--------+-------+--------+--------+------+-------+--------+-------+--------+-------+--------+--------+------+--------+--------+--------+-------+-------+-------+--------+--------+-------+-------+-------+-------+ | rt | serialno | division | puma | region | st | adjhsg | adjinc | wgtp | np | zzzz | acr | ags | bath | bdsp | bld | bus | conp | elep | fs | fulp | gasp | hfl | insp | mhp | mrgi | mrgp | mrgt | mrgx | refr | rmsp | rntm | rntp | rwat | sink | smp | stov | tel | ten | toil | vacs | valp | veh | watp | ybl | fes | fincp | fparc | grntp | grpip | hhl | hht | hincp | hugcl | hupac | hupaoc | huparc | kit | lngi | multg | mv | noc | npf | npp | nr | nrc | ocpip | partner | plm | psf | r18 | r60 | r65 | resmode | smocp | smx | srnt | sval | taxp | wif | wkexrel | workstat | facrp | fagsp | fbathp | fbdsp | fbldp | fbusp | fconp | felep | ffsp | ffulp | fgasp | fhflp | finsp | fkitp | fmhp | fmrgip | fmrgp | fmrgtp | fmrgxp | fmvp | fplmp | frefrp | frmsp | frntmp | frntp | frwatp | fsinkp | fsmp | fsmxhp | fsmxsp | fstovp | ftaxp | ftelp | ftenp | ftoilp | fvacsp | fvalp | fvehp | fwatp | fyblp | +======+==========+==========+======+========+======+=========+=========+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+======+========+======+======+======+======+=======+=======+=======+=======+======+======+=======+=======+=======+========+========+======+======+=======+======+======+======+======+======+======+=======+=========+======+======+======+======+======+=========+=======+======+======+======+======+======+=========+==========+=======+=======+========+=======+=======+=======+=======+=======+======+=======+=======+=======+=======+=======+======+========+=======+========+========+======+=======+========+=======+========+=======+========+========+======+========+========+========+=======+=======+=======+========+========+=======+=======+=======+=======+ | H | 168 | 9 | 300 | 4 | 2 | 1000000 | 1007624 | 56 | 3 | 1 | 1 | null | 1 | 3 | 2 | 2 | null | 200 | 2 | 3500 | 3 | 4 | 760 | null | 1 | 1800 | 1 | 1 | 1 | 7 | null | null | 1 | 1 | null | 1 | 1 | 1 | 1 | null | 235000 | 2 | 1600 | 5 | 7 | 89500 | 4 | null | null | 1 | 3 | 89500 | 0 | 4 | 4 | 4 | 1 | 1 | 1 | 6 | 0 | 3 | 0 | 0 | 0 | 33 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 2425 | 3 | 0 | 1 | 43 | 3 | 14 | 13 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | H | 433 | 9 | 200 | 4 | 2 | 1000000 | 1007624 | 0 | 1 | 2 | null | null | null | null | null | null | null | null | 2 | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | 5 | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | 0 | null | null | null | null | null | null | null | null | null | null | 0 | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | null | | H | 650 | 9 | 200 | 4 | 2 | 1000000 | 1007624 | 57 | 0 | 1 | 2 | null | 1 | 2 | 2 | 2 | null | null | null | null | null | null | null | null | null | null | null | null | 1 | 6 | null | null | 1 | 1 | null | 1 | null | null | 1 | 5 | null | null | null | 7 | null | null | null | null | null | null | null | null | null | null | null | null | 1 | null | null | null | null | null | null | null | null | null | null | 1 | null | null | null | null | 2 | null | null | 0 | 0 | null | null | null | null | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | H | 1890 | 9 | 400 | 4 | 2 | 1000000 | 1007624 | 46 | 2 | 1 | null | null | 1 | 1 | 6 | null | null | 1 | 2 | 1 | 3 | 4 | null | null | null | null | null | null | 1 | 2 | 2 | 600 | 1 | 1 | null | 1 | 1 | 3 | 1 | null | null | 1 | 1 | 3 | null | null | null | 600 | 21 | 1 | 7 | 34700 | 0 | 4 | 4 | 4 | 1 | 1 | 1 | 3 | 0 | null | 0 | 1 | 0 | null | 0 | 1 | 0 | 0 | 0 | 0 | 2 | null | null | 1 | 0 | null | null | null | null | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | | H | 2029 | 9 | 101 | 4 | 2 | 1000000 | 1007624 | 269 | 4 | 1 | 1 | null | 1 | 4 | 2 | 2 | null | 80 | 2 | 2 | 80 | 1 | 1500 | null | 1 | 920 | 1 | 1 | 1 | 7 | null | null | 1 | 1 | null | 1 | 1 | 1 | 1 | null | 200000 | 1 | 200 | 4 | 8 | 47100 | 2 | null | null | 1 | 3 | 47100 | 1 | 2 | 4 | 2 | 1 | 1 | 2 | 7 | 0 | 4 | 0 | 0 | 2 | 28 | 0 | 1 | 1 | 1 | 1 | 1 | 2 | 1097 | 3 | 0 | 1 | 34 | 1 | 15 | 15 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | +------+----------+----------+------+--------+------+---------+---------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+------+--------+------+------+------+------+-------+-------+-------+-------+------+------+-------+-------+-------+--------+--------+------+------+-------+------+------+------+------+------+------+-------+---------+------+------+------+------+------+---------+-------+------+------+------+------+------+---------+----------+-------+-------+--------+-------+-------+-------+-------+-------+------+-------+-------+-------+-------+-------+------+--------+-------+--------+--------+------+-------+--------+-------+--------+-------+--------+--------+------+--------+--------+--------+-------+-------+-------+--------+--------+-------+-------+-------+-------+ +-------+-------+-------+-------+-------+-------+-------+-------+-------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+ | wgtp1 | wgtp2 | wgtp3 | wgtp4 | wgtp5 | wgtp6 | wgtp7 | wgtp8 | wgtp9 | wgtp10 | wgtp11 | wgtp12 | wgtp13 | wgtp14 | wgtp15 | wgtp16 | wgtp17 | wgtp18 | wgtp19 | wgtp20 | wgtp21 | wgtp22 | wgtp23 | wgtp24 | wgtp25 | wgtp26 | wgtp27 | wgtp28 | wgtp29 | wgtp30 | wgtp31 | wgtp32 | wgtp33 | wgtp34 | wgtp35 | wgtp36 | wgtp37 | wgtp38 | wgtp39 | wgtp40 | wgtp41 | wgtp42 | wgtp43 | wgtp44 | wgtp45 | wgtp46 | wgtp47 | wgtp48 | wgtp49 | wgtp50 | wgtp51 | wgtp52 | wgtp53 | wgtp54 | wgtp55 | wgtp56 | wgtp57 | wgtp58 | wgtp59 | wgtp60 | wgtp61 | wgtp62 | wgtp63 | wgtp64 | wgtp65 | wgtp66 | wgtp67 | wgtp68 | wgtp69 | wgtp70 | wgtp71 | wgtp72 | wgtp73 | wgtp74 | wgtp75 | wgtp76 | wgtp77 | wgtp78 | wgtp79 | wgtp80 | +=======+=======+=======+=======+=======+=======+=======+=======+=======+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+========+ | 74 | 14 | 62 | 94 | 47 | 55 | 45 | 72 | 60 | 120 | 18 | 58 | 31 | 61 | 54 | 52 | 15 | 20 | 88 | 58 | 20 | 60 | 107 | 57 | 110 | 115 | 16 | 47 | 17 | 72 | 55 | 18 | 63 | 19 | 89 | 70 | 47 | 43 | 56 | 86 | 81 | 20 | 70 | 94 | 68 | 47 | 57 | 94 | 80 | 78 | 39 | 61 | 12 | 51 | 63 | 47 | 21 | 14 | 95 | 72 | 16 | 50 | 79 | 73 | 82 | 79 | 16 | 53 | 24 | 35 | 54 | 16 | 39 | 12 | 118 | 135 | 66 | 47 | 50 | 76 | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 60 | 17 | 57 | 16 | 93 | 106 | 59 | 58 | 58 | 17 | 56 | 101 | 54 | 116 | 96 | 18 | 72 | 15 | 61 | 55 | 54 | 18 | 54 | 15 | 96 | 97 | 57 | 65 | 55 | 17 | 49 | 94 | 59 | 113 | 88 | 18 | 59 | 13 | 56 | 50 | 60 | 17 | 59 | 17 | 96 | 98 | 52 | 50 | 50 | 17 | 60 | 93 | 57 | 102 | 101 | 17 | 68 | 20 | 53 | 54 | 66 | 18 | 63 | 19 | 91 | 106 | 56 | 56 | 57 | 20 | 57 | 90 | 54 | 98 | 101 | 16 | 51 | 17 | 61 | 61 | | 10 | 16 | 10 | 42 | 61 | 44 | 54 | 45 | 71 | 67 | 112 | 50 | 15 | 41 | 111 | 79 | 37 | 67 | 38 | 40 | 81 | 95 | 70 | 81 | 51 | 40 | 38 | 47 | 15 | 22 | 18 | 34 | 95 | 55 | 14 | 51 | 48 | 18 | 43 | 12 | 7 | 13 | 15 | 57 | 72 | 55 | 48 | 50 | 75 | 80 | 116 | 51 | 14 | 38 | 126 | 57 | 30 | 93 | 29 | 53 | 80 | 55 | 71 | 46 | 38 | 57 | 39 | 47 | 16 | 16 | 20 | 50 | 91 | 58 | 20 | 72 | 43 | 11 | 48 | 9 | | 252 | 470 | 264 | 430 | 228 | 243 | 192 | 107 | 265 | 79 | 266 | 268 | 68 | 335 | 503 | 116 | 95 | 389 | 228 | 114 | 254 | 71 | 225 | 116 | 289 | 291 | 233 | 539 | 310 | 423 | 262 | 346 | 511 | 235 | 79 | 407 | 420 | 121 | 223 | 90 | 250 | 70 | 240 | 101 | 259 | 326 | 245 | 461 | 241 | 480 | 315 | 275 | 286 | 338 | 118 | 363 | 409 | 87 | 238 | 418 | 278 | 322 | 297 | 486 | 376 | 262 | 198 | 95 | 259 | 104 | 238 | 309 | 135 | 230 | 408 | 117 | 83 | 497 | 244 | 418 | +-------+-------+-------+-------+-------+-------+-------+-------+-------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+ _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 5

Insufficient priveleges while calling vaccum
by Ashish Kumar Singh 12 Oct '12

12 Oct '12

HI List, I have created a schema test user user testuser. While calling vacuum on one of its tables I am getting error : call vacuum(test,'testtable'); insufficient privileges Any examples on how to elevate priveleges for test user will be helpful! Regards, Ashish _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 0

Lock monetdb funnel behaviour
by Tapomay Dey 10 Oct '12

10 Oct '12

Hi, I have created two databases db1 and db2 and created a user "tapomay" on both with dedicated schema as given in the Getting Started page - http://www.monetdb.org/Downloads/Tutorial I have created a monetdb multiplex-funnel "testfunnel" pointing to them. When I do monetdb lock db1, I can access db1 using user "monetdb"(as expected) but not through user tapomay(as expected). But when I do monetdb lock testfunnel, I can still access it using user tapomay. I need it to stay unavailable. Also when I follow it by monetdb stop testfunnel and then try to access it using user tapomay, then it says that it's under maintenance. FYI, Regards, Tapomay _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 2

Question: How well does Monetdb support incremental updates?
by David Sisk 05 Oct '12

05 Oct '12

Question for you kind folks. I've tested another open source column-store database (Infinidb)...the query performance was very good, the bulk load performance was good, but where it fell down was on refreshing the data by updating a small percentage of the existing values. Bulk loads processed about 1000 rows/second...updating existing rows processed only about 1 row/second. We have growing 60-70Gb data warehouse, and we don't want to drop and re-load it every night, we want to just apply incremental updates at very short intervals throughout the day (say, every 5 mins). So, how well will Monetdb handle updates to existing rows in this scenario? One additional question: Are there any sources of commercial support for Monetdb? Thanks and best regards, -- Dave Sisk | Senior DBA dsisk(a)lulu.com | www.lulu.com [m] 919-744-1885 _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 0

Is there a MonetDB wiki ?
by Assaf Gordon 03 Oct '12

03 Oct '12

Hello, I'm new to MonetDB, and I find the documentation very terse. Is there a wiki for MonetDB ? Or perhaps a possibility to add comments on each of the manual-pages (like the PHP manual website, where users can elaborate and add examples on each function) ? Even a search on the mailing list archive would be helpful (but not the SourceForge search, it's very unfriendly). Thanks, -gordon _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

How to repair a database?
by Assaf Gordon 03 Oct '12

03 Oct '12

Hello, While loading a large file into a MonetDB database, my server crashed (the physical machine, not the MonetDB server process). After rebooting the machine and restarting MonetDB, almost every query crashes the MonetDB server: == $ mclient -d voc Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased) Database: MonetDB v11.14.0 (unreleased), 'mapi:monetdb://chachacha.cshl.edu:50000/voc' Type \q to quit, \? for a list of available commands auto commit mode: on sql>select * from bc251 limit 10 ; Connection terminated $ tail merovingian.log <snip> 2012-10-03 15:53:51 MSG merovingian[4001]: proxying client (local) for database 'voc' to mapi:monetdb:///localdata/gordon/monetdb/testdb4/voc/.mapi.sock?database=voc 2012-10-03 15:53:51 MSG merovingian[4001]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-10-03 15:53:58 MSG merovingian[4001]: database 'voc' (4043) was killed by signal SIGSEGV == The database contains several tables, and queries on all of them result in monetdb server crash. How do I fix the database ? I tried "monetdbd stop + start", and also "monetdb lock + release", but to no avail. Thanks, -gordon BTW, It is likely that some of the database files are corrupted (due to the physical server crash). _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 1

Need name of columns in unique key of a table
by Tapomay Dey 03 Oct '12

03 Oct '12

I have following table: CREATE TABLE "sys"."tapomay3" ( "id" INTEGER, "val" VARCHAR(20), "valnum" INTEGER NOT NULL, CONSTRAINT "pk3" PRIMARY KEY ("valnum"), CONSTRAINT "tapomay3_id_val_unique" UNIQUE ("id", "val") ); I need to get the list of column names that are part of any unique key. sql>select o.name from keys k, objects o where k.id in (select id from keys where table_id = (select id from tables where name='tapomay3') and name like '%unique') and o.id = k.id; +---------+ | name | +=========+ | id | | val | +---------+ select o.name from keys k, objects o where k.id in (select id from keys where table_id = (select id from tables where name='tapomay3') and name like '%unique') and o.id = k.id Is this the right approach? Thanks and Regards, Tapomay. _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

1 0

Question about temporary tables - empty data?
by Assaf Gordon 01 Oct '12

01 Oct '12

Hello, I need to create temporary tables, but using the statement "create temporary table AS select XXX WITH DATA" results in an empty table; ==== sql>CREATE TABLE table1 (a INTEGER); operation successful (1.320ms) sql>INSERT INTO table1 VALUES(1); 1 affected row (0.693ms) sql>INSERT INTO table1 VALUES(2); 1 affected row (0.511ms) sql> sql>CREATE TEMPORARY TABLE temp1 AS SELECT * FROM table1 WITH DATA ; operation successful (0.735ms) sql>SELECT * FROM temp1; +---+ | a | +===+ +---+ 0 tuples (1.032ms) === Whereas if I don't use "temporary" for the table creation, it works fine: === sql>CREATE TABLE temp2 AS SELECT * FROM table1 WITH DATA ; operation successful (1.842ms) sql>SELECT * FROM temp2; +------+ | a | +======+ | 1 | | 2 | +------+ 2 tuples (1.898ms) === The example above is contrived, but I need to create two temporary tables to facilitate a join. Does the "temporary" keyword have different meaning than in other databases ? I couldn't find a good explanation in the on-line documentation... I'm using MonetDB v11.14.0, compiled from source with revision 45564:14983b3e103e . Thanks, -gordon _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

2 2

users-list post from ajdamico@gmail.com requires approval
by users-list-owner＠monetdb.org 28 Sep '12

28 Sep '12

As list administrator, your authorization is requested for the following mailing list posting: List: users-list(a)monetdb.org From: ajdamico(a)gmail.com Subject: invalid tuple received from server, got 138 columns, expected 476, ignoring Reason: Post by non-member to a members-only list At your convenience, visit: http://mail.monetdb.org/mailman/admindb/users-list to approve or deny the request.

1 0

problem starting database
by Peter 28 Sep '12

28 Sep '12

Hello, I'm seeing this error when starting a database. Not sure if anyone has had the same issue and whether anyone had a fix? The following is what I did % monetdbd start ~/dbfarm % monetdbd start ~/dbfarm % monetdb create voc % monetdb start voc starting database 'voc'... FAILED start: starting 'voc' failed: database 'voc' appears to shut itself down after starting, check monetdbd's logfile for possible hints The log says the following 2012-09-27 16:56:04 MSG merovingian[14761]: database 'voc' (14801) has exited with exit status 1 2012-09-27 16:56:04 ERR control[14761]: (local): failed to fork mserver: database 'voc' appears to shut itself down after starting, check monetdbd's logfile for possible hints Any comments / suggestions? Thank you, Peter _______________________________________________ users-list mailing list users-list(a)monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

3 7

[MonetDB-users] Array database for large matrix
by Joshua Shuai Yuan 27 Sep '12

27 Sep '12

Hi All, I just tried monetdb with large tables (600,000 rows by 50,000 columns). There are two issues: 1. performance was low, it took about 4 seconds to insert a row of record when the number of columns was large (50,000). However it was pretty fast (about 100 rows per second) when the column number was small (for example, 10). 2. serious errors occurred very often. For example, after inserting random number of records (50, for example), monetdb started to report errors, like: monetdbd: internal error while starting mserver, please refer to the logs So I opened the log file, and the error was: 2012-09-14 08:26:36 ERR merovingian[13730]: client error: unknown or impossible state: 4 The Makefile (it is also contained in the attachments) listed below will start database server, create a database farm, create a database, create a big table and then insert records to the big table. Here it is: #=====start of Makefile===================== ROW_NUM=600000 COLUMN_NUM=50000 COLUMN_NUM_MINUS_ONE=$(shell echo $(COLUMN_NUM)-1 | bc) all: clean monetdbd create ./mydbfarm monetdbd start ./mydbfarm monetdb create test_big_db monetdb release test_big_db make create_table_sql -s > create_big_table.sql make insert_data_sql -s > insert_data.sql mclient -d test_big_db create_big_table.sql for i in $$(seq 1 $(ROW_NUM)); do \ mclient -d test_big_db insert_data.sql ;\ echo 'done inserting ' $$i ' rows'; \ done; mclient -d test_big_db -s "select * from test_big_table" > test_big_table.txt create_table_sql: @echo 'START TRANSACTION;' @echo 'CREATE TABLE "test_big_table" (' @for i in $$(seq 1 $(COLUMN_NUM_MINUS_ONE)); do \ echo ' "gen'$$i'" DOUBLE,'; \ done @echo ' "gen$(COLUMN_NUM)" DOUBLE' @echo ');' @echo 'COMMIT;' insert_data_sql: @echo -n 'INSERT INTO "test_big_table" VALUES (' ; @for j in $$(seq 1 $(COLUMN_NUM_MINUS_ONE)) ; do \ echo -n '0.323, '; \ done; @echo '0.324);'; insert_all_data_sql: @echo 'START TRANSACTION;' @for i in $$(seq 1 $(ROW_NUM)); do\ echo -n 'INSERT INTO "test_big_table" VALUES (' ;\ for j in $$(seq 1 $(COLUMN_NUM_MINUS_ONE)) ; do \ echo -n '0.323, '; \ done; \ echo '0.324);'; \ done @echo 'COMMIT;' clean: -killall mserver5 -killall monetdbd rm -rf ./mydbfarm rm -rf create_big_table.sql test_big_table.txt insert_data.sql #=====end of Makefile====================== Thank you very much ! Best wishes, Joshua Shuai Yuan On Thu, Sep 13, 2012 at 12:43 PM, Joshua Shuai Yuan < shuaiyuan.emory(a)gmail.com> wrote: > Sure, I will see what I can do. > > Best wishes, > Joshua Shuai Yuan > > > On Wed, Sep 12, 2012 at 11:40 PM, Wang, Fusheng <fusheng.wang(a)emory.edu>wrote: > >> Hi Joshua,**** >> >> ** ** >> >> The table we are managing is in the scale of 30K x 5K: 150M cells. If >> each table cell (double type) needs 8 bytes to represent (ideally), the >> space needed will be a couple of GB, or at most, in the scale of tens of >> GB. If that is the case, distributed setup may not be needed, as the data >> can be mostly cached by the database. MonetDB does support multi-cores >> and multi-disks, but setup across multiple machines is not supported based >> on my knowledge. **** >> >> ** ** >> >> Even though MonetDB claims unlimited number of columns, we should still >> be cautious on what performance we can achieve for the queries we want to >> provide. A pilot study on this could provide us some guideline. Do you >> think you can setup MonetDB, and create a benchmark table we can do some >> performance study?**** >> >> ** ** >> >> Interestingly, the large column issue is also discussed in a famous >> database blog:**** >> >> >> http://www.dbms2.com/2011/03/13/so-how-many-columns-can-a-single-table-have… >> **** >> >> ** ** >> >> One guy commented:**** >> >> ** ** >> >> “Genomics models were the primary driver. these folks typically have >> short but wide datasets of the order of 300,000 columns.”**** >> >> ** ** >> >> So we are not alone. And we have only a subset of the columns (30K >> versus 300K)? Then we are lucky!**** >> >> ** ** >> >> ** ** >> >> Fusheng**** >> >> ** ** >> >> ** ** >> >> ** ** >> >> ** ** >> >> *From:* Joshua Shuai Yuan [mailto:shuaiyuan.emory@gmail.com] >> *Sent:* Wednesday, September 12, 2012 11:14 PM >> *To:* Wang, Fusheng >> *Cc:* Qin, Zhaohui >> *Subject:* Re: Array database for large matrix**** >> >> ** ** >> >> Hi Dr. Wang,**** >> >> That's really a good news. Does it support distributed database? Or do >> we need distributed one?**** >> >> ** ** >> >> >> Best wishes, >> Joshua Shuai Yuan >> >> **** >> >> On Wed, Sep 12, 2012 at 3:54 PM, Wang, Fusheng <fusheng.wang(a)emory.edu> >> wrote:**** >> >> Hi guys,**** >> >> **** >> >> It looks like the matrix structure can be nicely supported by array >> databases, like MonetDB. It supports unlimited number of columns for a >> table. It’s also open source. **** >> >> http://www.monetdb.org/Home/Features**** >> >> **** >> >> I know the group quite well, and I will chat with them on the use case to >> see if it’s a good fit. **** >> >> **** >> >> Thanks,**** >> >> **** >> >> Fusheng**** >> >> **** >> >> **** >> >> ** ** >> ------------------------------ >> >> >> This e-mail message (including any attachments) is for the sole use of >> the intended recipient(s) and may contain confidential and privileged >> information. If the reader of this message is not the intended >> recipient, you are hereby notified that any dissemination, distribution >> or copying of this message (including any attachments) is strictly >> prohibited. >> >> If you have received this message in error, please contact >> the sender by reply e-mail message and destroy all copies of the >> original message (including attachments).**** >> >> ** ** >> > >

2 2

[MonetDB-users] MonetDB project will move to monetdb.org
by Fabian Groffen 26 Sep '12

26 Sep '12

We would like to inform you that as of Januari 2013, the monetdb project on SourceForge will be removed. All services that SourceForge has kindly provided us with in the past will be migrated to our monetdb.org infrastructure. Currently, the only remaining services hosted on SourceForge are the three mailing lists monetdb-announce, monetdb-users and monetdb-developers. As of this message, these lists are migrated to their equivalents on monetdb.org. The new lists are as follows: monetdb-announce(a)lists.sourceforge.net -> announce-list(a)monetdb.org monetdb-users(a)lists.sourceforge.net -> users-list(a)monetdb.org monetdb-developers(a)lists.sourceforge.net -> developers-list(a)monetdb.org We invite you to subscribe to the new lists on monetdb.org at your earliest convenience. Any posts to the old lists are rejected from now on. Posts to the new lists at monetdb.org are forwarded in batches to the old lists until the end of this year. The MonetDB team would like to take this opportunity to thank SourceForge for the services provided over the past years. We hope to welcome all current subscribers on our new lists at monetdb.org, see: http://mail.monetdb.org/mailman/listinfo The MonetDB team

1 0

[MonetDB-users] invalid tuple received from server, got 138 columns, expected 476, ignoring
by Anthony Damico 26 Sep '12

26 Sep '12

Hello, I'm pretty new to MonetDB and I'm trying to perform what seems like it should be a relatively straightforward inner join between two tables. I would like to merge the two Alaska files from the American Community Survey -- http://www2.census.gov/acs2010_1yr/pums/csv_hak.zip contains a CSV file with one record per household http://www2.census.gov/acs2010_1yr/pums/csv_pak.zip contains a CSV file with one record per personThese two files should be merged on the field "serialno" I am working on Windows 7 x64. Here's the contents of my mserver5.exe window: # MonetDB 5 server v11.11.11 "Jul2012-SP2" # Serving database 'demo', using 2 threads # Compiled for x86_64-pc-winnt/64bit with 64bit OIDs dynamically linked # Found 3.905 GiB available main-memory. # Copyright (c) 1993-July 2008 CWI. # Copyright (c) August 2008-2012 MonetDB B.V., all rights reserved # Visit http://www.monetdb.org/ for further information # Listening for connection requests on mapi:monetdb://127.0.0.1:50000/ # MonetDB/SQL module loaded > The following commands.. 1) create a person-level table 2) create a household-level table 3) read the person-level CSV into the person table 4) read the household-level CSV into the household table 5) attempt to print the first five records with "select * from tablename limit 5" -- sometimes these work, sometimes they don't. 6) merge the two tables together 7) attempt to print the first five records of the merged table Unfortunately, I'm getting an error that I can't find with web searches.. The only place I can even find this error is http://bugs.monetdb.org/show_bug.cgi?id=2963 -- and that seems both time-related and fixed long ago.. I doubt it's a bug, I'm probably just making a beginner's mistake. invalid tuple received from server, got 138 columns, expected 476, ignoring +------+------+------+------+-------+------+---------+---------+------+------+ 1 tuple (417.984ms) !466 columns dropped! note: to disable dropping columns and/or truncating fields use \w-1 Even after setting \w to -1, the number of columns returned gets limited, crashing my program. I am ultimately trying to work with the new R/MonetDB package (which uses Java and is available from http://sqlsurvey.r-forge.r-project.org/) but none of the table interactivity will work until I'm able to return all of the columns properly. Any advice would be appreciated! Thanks!!! Anthony Damico Kaiser Family Foundation Here are the SQL commands: CREATE TABLE person (RT VARCHAR(255), SERIALNO INT, SPORDER INT, PUMA INT, ST INT, ADJINC INT, PWGTP INT, AGEP INT, CIT INT, CITWP INT, COW INT, DDRS INT, DEAR INT, DEYE INT, DOUT INT, DPHY INT, DRAT INT, DRATX INT, DREM INT, ENG INT, FER INT, GCL INT, GCM INT, GCR INT, HINS1 INT, HINS2 INT, HINS3 INT, HINS4 INT, HINS5 INT, HINS6 INT, HINS7 INT, INTP INT, JWMNP INT, JWRIP INT, JWTR INT, LANX INT, MAR INT, MARHD INT, MARHM INT, MARHT INT, MARHW INT, MARHYP INT, MIG INT, MIL INT, MLPA INT, MLPB INT, MLPC INT, MLPD INT, MLPE INT, MLPF INT, MLPG INT, MLPH INT, MLPI INT, MLPJ INT, MLPK INT, NWAB INT, NWAV INT, NWLA INT, NWLK INT, NWRE INT, OIP INT, PAP INT, RELP INT, RETP INT, SCH INT, SCHG INT, SCHL INT, SEMP INT, SEX INT, SSIP INT, SSP INT, WAGP INT, WKHP INT, WKL INT, WKW INT, WRK INT, YOEP INT, ANC INT, ANC1P INT, ANC2P INT, DECADE INT, DIS INT, DRIVESP INT, ESP INT, ESR INT, FOD1P INT, FOD2P INT, HICOV INT, HISP INT, INDP INT, JWAP INT, JWDP INT, LANP INT, MIGPUMA INT, MIGSP INT, MSP INT, NAICSP VARCHAR(255), NATIVITY INT, NOP INT, OC INT, OCCP INT, PAOC INT, PERNP INT, PINCP INT, POBP INT, POVPIP INT, POWPUMA INT, POWSP INT, PRIVCOV INT, PUBCOV INT, QTRBIR INT, RAC1P INT, RAC2P INT, RAC3P INT, RACAIAN INT, RACASN INT, RACBLK INT, RACNHPI INT, RACNUM INT, RACSOR INT, RACWHT INT, RC INT, SCIENGP INT, SCIENGRLP INT, SFN INT, SFR INT, SOCP VARCHAR(255), VPS INT, WAOB INT, FAGEP INT, FANCP INT, FCITP INT, FCITWP INT, FCOWP INT, FDDRSP INT, FDEARP INT, FDEYEP INT, FDOUTP INT, FDPHYP INT, FDRATP INT, FDRATXP INT, FDREMP INT, FENGP INT, FESRP INT, FFERP INT, FFODP INT, FGCLP INT, FGCMP INT, FGCRP INT, FHINS1P INT, FHINS2P INT, FHINS3C INT, FHINS3P INT, FHINS4C INT, FHINS4P INT, FHINS5C INT, FHINS5P INT, FHINS6P INT, FHINS7P INT, FHISP INT, FINDP INT, FINTP INT, FJWDP INT, FJWMNP INT, FJWRIP INT, FJWTRP INT, FLANP INT, FLANXP INT, FMARHDP INT, FMARHMP INT, FMARHTP INT, FMARHWP INT, FMARHYP INT, FMARP INT, FMIGP INT, FMIGSP INT, FMILPP INT, FMILSP INT, FOCCP INT, FOIP INT, FPAP INT, FPOBP INT, FPOWSP INT, FRACP INT, FRELP INT, FRETP INT, FSCHGP INT, FSCHLP INT, FSCHP INT, FSEMP INT, FSEXP INT, FSSIP INT, FSSP INT, FWAGP INT, FWKHP INT, FWKLP INT, FWKWP INT, FWRKP INT, FYOEP INT, pwgtp1 INT, pwgtp2 INT, pwgtp3 INT, pwgtp4 INT, pwgtp5 INT, pwgtp6 INT, pwgtp7 INT, pwgtp8 INT, pwgtp9 INT, pwgtp10 INT, pwgtp11 INT, pwgtp12 INT, pwgtp13 INT, pwgtp14 INT, pwgtp15 INT, pwgtp16 INT, pwgtp17 INT, pwgtp18 INT, pwgtp19 INT, pwgtp20 INT, pwgtp21 INT, pwgtp22 INT, pwgtp23 INT, pwgtp24 INT, pwgtp25 INT, pwgtp26 INT, pwgtp27 INT, pwgtp28 INT, pwgtp29 INT, pwgtp30 INT, pwgtp31 INT, pwgtp32 INT, pwgtp33 INT, pwgtp34 INT, pwgtp35 INT, pwgtp36 INT, pwgtp37 INT, pwgtp38 INT, pwgtp39 INT, pwgtp40 INT, pwgtp41 INT, pwgtp42 INT, pwgtp43 INT, pwgtp44 INT, pwgtp45 INT, pwgtp46 INT, pwgtp47 INT, pwgtp48 INT, pwgtp49 INT, pwgtp50 INT, pwgtp51 INT, pwgtp52 INT, pwgtp53 INT, pwgtp54 INT, pwgtp55 INT, pwgtp56 INT, pwgtp57 INT, pwgtp58 INT, pwgtp59 INT, pwgtp60 INT, pwgtp61 INT, pwgtp62 INT, pwgtp63 INT, pwgtp64 INT, pwgtp65 INT, pwgtp66 INT, pwgtp67 INT, pwgtp68 INT, pwgtp69 INT, pwgtp70 INT, pwgtp71 INT, pwgtp72 INT, pwgtp73 INT, pwgtp74 INT, pwgtp75 INT, pwgtp76 INT, pwgtp77 INT, pwgtp78 INT, pwgtp79 INT, pwgtp80 INT); CREATE TABLE household (RT VARCHAR(255), SERIALNO INT, DIVISION INT, PUMA INT, REGION INT, ST INT, ADJHSG INT, ADJINC INT, WGTP INT, NP INT, TYPE INT, ACR INT, AGS INT, BATH INT, BDSP INT, BLD INT, BUS INT, CONP INT, ELEP INT, FS INT, FULP INT, GASP INT, HFL INT, INSP INT, MHP INT, MRGI INT, MRGP INT, MRGT INT, MRGX INT, REFR INT, RMSP INT, RNTM INT, RNTP INT, RWAT INT, SINK INT, SMP INT, STOV INT, TEL INT, TEN INT, TOIL INT, VACS INT, VALP INT, VEH INT, WATP INT, YBL INT, FES INT, FINCP INT, FPARC INT, GRNTP INT, GRPIP INT, HHL INT, HHT INT, HINCP INT, HUGCL INT, HUPAC INT, HUPAOC INT, HUPARC INT, KIT INT, LNGI INT, MULTG INT, MV INT, NOC INT, NPF INT, NPP INT, NR INT, NRC INT, OCPIP INT, PARTNER INT, PLM INT, PSF INT, R18 INT, R60 INT, R65 INT, RESMODE INT, SMOCP INT, SMX INT, SRNT INT, SVAL INT, TAXP INT, WIF INT, WKEXREL INT, WORKSTAT INT, FACRP INT, FAGSP INT, FBATHP INT, FBDSP INT, FBLDP INT, FBUSP INT, FCONP INT, FELEP INT, FFSP INT, FFULP INT, FGASP INT, FHFLP INT, FINSP INT, FKITP INT, FMHP INT, FMRGIP INT, FMRGP INT, FMRGTP INT, FMRGXP INT, FMVP INT, FPLMP INT, FREFRP INT, FRMSP INT, FRNTMP INT, FRNTP INT, FRWATP INT, FSINKP INT, FSMP INT, FSMXHP INT, FSMXSP INT, FSTOVP INT, FTAXP INT, FTELP INT, FTENP INT, FTOILP INT, FVACSP INT, FVALP INT, FVEHP INT, FWATP INT, FYBLP INT, wgtp1 INT, wgtp2 INT, wgtp3 INT, wgtp4 INT, wgtp5 INT, wgtp6 INT, wgtp7 INT, wgtp8 INT, wgtp9 INT, wgtp10 INT, wgtp11 INT, wgtp12 INT, wgtp13 INT, wgtp14 INT, wgtp15 INT, wgtp16 INT, wgtp17 INT, wgtp18 INT, wgtp19 INT, wgtp20 INT, wgtp21 INT, wgtp22 INT, wgtp23 INT, wgtp24 INT, wgtp25 INT, wgtp26 INT, wgtp27 INT, wgtp28 INT, wgtp29 INT, wgtp30 INT, wgtp31 INT, wgtp32 INT, wgtp33 INT, wgtp34 INT, wgtp35 INT, wgtp36 INT, wgtp37 INT, wgtp38 INT, wgtp39 INT, wgtp40 INT, wgtp41 INT, wgtp42 INT, wgtp43 INT, wgtp44 INT, wgtp45 INT, wgtp46 INT, wgtp47 INT, wgtp48 INT, wgtp49 INT, wgtp50 INT, wgtp51 INT, wgtp52 INT, wgtp53 INT, wgtp54 INT, wgtp55 INT, wgtp56 INT, wgtp57 INT, wgtp58 INT, wgtp59 INT, wgtp60 INT, wgtp61 INT, wgtp62 INT, wgtp63 INT, wgtp64 INT, wgtp65 INT, wgtp66 INT, wgtp67 INT, wgtp68 INT, wgtp69 INT, wgtp70 INT, wgtp71 INT, wgtp72 INT, wgtp73 INT, wgtp74 INT, wgtp75 INT, wgtp76 INT, wgtp77 INT, wgtp78 INT, wgtp79 INT, wgtp80 INT); copy 50000 offset 2 records into person from 'C:\Users\user\desktop\ss10pak.csv' using delimiters ',','\n','"' NULL as '' ; copy 25000 offset 2 records into household from 'C:\Users\user\desktop\ss10hak.csv' using delimiters ',','\n','"' NULL as '' ; select * from person limit 5; select * from household limit 5; create table merged as select 'M' as rt, a.serialno, a.division, a.puma, a.region, a.st, a.adjhsg, a.adjinc, a.wgtp, a.np, a.type, a.acr, a.ags, a.bath, a.bdsp, a.bld, a.bus, a.conp, a.elep, a.fs, a.fulp, a.gasp, a.hfl, a.insp, a.mhp, a.mrgi, a.mrgp, a.mrgt, a.mrgx, a.refr, a.rmsp, a.rntm, a.rntp, a.rwat, a.sink, a.smp, a.stov, a.tel, a.ten, a.toil, a.vacs, a.valp, a.veh, a.watp, a.ybl, a.fes, a.fincp, a.fparc, a.grntp, a.grpip, a.hhl, a.hht, a.hincp, a.hugcl, a.hupac, a.hupaoc, a.huparc, a.kit, a.lngi, a.multg, a.mv, a.noc, a.npf, a.npp, a.nr, a.nrc, a.ocpip, a.partner, a.plm, a.psf, a.r18, a.r60, a.r65, a.resmode, a.smocp, a.smx, a.srnt, a.sval, a.taxp, a.wif, a.wkexrel, a.workstat, a.facrp, a.fagsp, a.fbathp, a.fbdsp, a.fbldp, a.fbusp, a.fconp, a.felep, a.ffsp, a.ffulp, a.fgasp, a.fhflp, a.finsp, a.fkitp, a.fmhp, a.fmrgip, a.fmrgp, a.fmrgtp, a.fmrgxp, a.fmvp, a.fplmp, a.frefrp, a.frmsp, a.frntmp, a.frntp, a.frwatp, a.fsinkp, a.fsmp, a.fsmxhp, a.fsmxsp, a.fstovp, a.ftaxp, a.ftelp, a.ftenp, a.ftoilp, a.fvacsp, a.fvalp, a.fvehp, a.fwatp, a.fyblp, a.wgtp1, a.wgtp2, a.wgtp3, a.wgtp4, a.wgtp5, a.wgtp6, a.wgtp7, a.wgtp8, a.wgtp9, a.wgtp10, a.wgtp11, a.wgtp12, a.wgtp13, a.wgtp14, a.wgtp15, a.wgtp16, a.wgtp17, a.wgtp18, a.wgtp19, a.wgtp20, a.wgtp21, a.wgtp22, a.wgtp23, a.wgtp24, a.wgtp25, a.wgtp26, a.wgtp27, a.wgtp28, a.wgtp29, a.wgtp30, a.wgtp31, a.wgtp32, a.wgtp33, a.wgtp34, a.wgtp35, a.wgtp36, a.wgtp37, a.wgtp38, a.wgtp39, a.wgtp40, a.wgtp41, a.wgtp42, a.wgtp43, a.wgtp44, a.wgtp45, a.wgtp46, a.wgtp47, a.wgtp48, a.wgtp49, a.wgtp50, a.wgtp51, a.wgtp52, a.wgtp53, a.wgtp54, a.wgtp55, a.wgtp56, a.wgtp57, a.wgtp58, a.wgtp59, a.wgtp60, a.wgtp61, a.wgtp62, a.wgtp63, a.wgtp64, a.wgtp65, a.wgtp66, a.wgtp67, a.wgtp68, a.wgtp69, a.wgtp70, a.wgtp71, a.wgtp72, a.wgtp73, a.wgtp74, a.wgtp75, a.wgtp76, a.wgtp77, a.wgtp78, a.wgtp79, a.wgtp80, sporder, pwgtp, agep, cit, citwp, cow, ddrs, dear, deye, dout, dphy, drat, dratx, drem, eng, fer, gcl, gcm, gcr, hins1, hins2, hins3, hins4, hins5, hins6, hins7, intp, jwmnp, jwrip, jwtr, lanx, mar, marhd, marhm, marht, marhw, marhyp, mig, mil, mlpa, mlpb, mlpc, mlpd, mlpe, mlpf, mlpg, mlph, mlpi, mlpj, mlpk, nwab, nwav, nwla, nwlk, nwre, oip, pap, relp, retp, sch, schg, schl, semp, sex, ssip, ssp, wagp, wkhp, wkl, wkw, wrk, yoep, anc, anc1p, anc2p, decade, dis, drivesp, esp, esr, fod1p, fod2p, hicov, hisp, indp, jwap, jwdp, lanp, migpuma, migsp, msp, naicsp, nativity, nop, oc, occp, paoc, pernp, pincp, pobp, povpip, powpuma, powsp, privcov, pubcov, qtrbir, rac1p, rac2p, rac3p, racaian, racasn, racblk, racnhpi, racnum, racsor, racwht, rc, sciengp, sciengrlp, sfn, sfr, socp, vps, waob, fagep, fancp, fcitp, fcitwp, fcowp, fddrsp, fdearp, fdeyep, fdoutp, fdphyp, fdratp, fdratxp, fdremp, fengp, fesrp, fferp, ffodp, fgclp, fgcmp, fgcrp, fhins1p, fhins2p, fhins3c, fhins3p, fhins4c, fhins4p, fhins5c, fhins5p, fhins6p, fhins7p, fhisp, findp, fintp, fjwdp, fjwmnp, fjwrip, fjwtrp, flanp, flanxp, fmarhdp, fmarhmp, fmarhtp, fmarhwp, fmarhyp, fmarp, fmigp, fmigsp, fmilpp, fmilsp, foccp, foip, fpap, fpobp, fpowsp, fracp, frelp, fretp, fschgp, fschlp, fschp, fsemp, fsexp, fssip, fssp, fwagp, fwkhp, fwklp, fwkwp, fwrkp, fyoep, pwgtp1, pwgtp2, pwgtp3, pwgtp4, pwgtp5, pwgtp6, pwgtp7, pwgtp8, pwgtp9, pwgtp10, pwgtp11, pwgtp12, pwgtp13, pwgtp14, pwgtp15, pwgtp16, pwgtp17, pwgtp18, pwgtp19, pwgtp20, pwgtp21, pwgtp22, pwgtp23, pwgtp24, pwgtp25, pwgtp26, pwgtp27, pwgtp28, pwgtp29, pwgtp30, pwgtp31, pwgtp32, pwgtp33, pwgtp34, pwgtp35, pwgtp36, pwgtp37, pwgtp38, pwgtp39, pwgtp40, pwgtp41, pwgtp42, pwgtp43, pwgtp44, pwgtp45, pwgtp46, pwgtp47, pwgtp48, pwgtp49, pwgtp50, pwgtp51, pwgtp52, pwgtp53, pwgtp54, pwgtp55, pwgtp56, pwgtp57, pwgtp58, pwgtp59, pwgtp60, pwgtp61, pwgtp62, pwgtp63, pwgtp64, pwgtp65, pwgtp66, pwgtp67, pwgtp68, pwgtp69, pwgtp70, pwgtp71, pwgtp72, pwgtp73, pwgtp74, pwgtp75, pwgtp76, pwgtp77, pwgtp78, pwgtp79, pwgtp80 from household as a inner join person as b on a.serialno = b.serialno with data; select * from merged limit 5; invalid tuple received from server, got 138 columns, expected 476, ignoring

2 1

[MonetDB-users] Debug sqoop-monetdb
by Jeremy O'Sullivan 25 Sep '12

25 Sep '12

Hi, I am trying to insert data into monetdb using sqoop, via the monet jdbc interface. It keeps crashing 20 odd rows into the import, with a monetdb ROLLBACK. The debug info from Sqoop is poor. Does anyone know if the monetdb ROLLBACK can be disabled, so that I can see the last row imported. Has anyone tried Sqoop to Monetdb, are there any debugging tips that you can give ? Regards, Jeremy sqoop export --connect jdbc:monetdb://cluster-03/ngpm -driver nl.cwi.monetdb.jdbc.MonetDriver --num-mappers 1 --password monetdb --username monetdb --table query_start --export-dir /test/dash_test/QueryStart.Log --fields-terminated-by ',' 12/09/24 17:27:49 INFO mapreduce.Job: Task Id : attempt_1347971665109_0247_m_000000_1, Status : FAILED Error: java.io.IOException: java.sql.SQLException: EXEC: wrong number of arguments for prepared statement: 100, expected 102 at org.apache.sqoop.mapreduce.AsyncSqlRecordWriter.close(AsyncSqlRecordWriter.j ava:192) at org.apache.hadoop.mapred.MapTask$NewDirectOutputCollector.close(MapTask.java :610) at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:730) at org.apache.hadoop.mapred.MapTask.run(MapTask.java:332) at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:152) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:396) at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.ja va:1232) at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:147) Caused by: java.sql.SQLException: EXEC: wrong number of arguments for prepared statement: 100, expected 102 at nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.executeQuery(MonetConnectio n.java:2524) at nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.processQuery(MonetConnectio n.java:2274) at nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:508) at nl.cwi.monetdb.jdbc.MonetStatement.execute(MonetStatement.java:349) at nl.cwi.monetdb.jdbc.MonetPreparedStatement.execute(MonetPreparedStatement.ja va:247) at org.apache.sqoop.mapreduce.AsyncSqlOutputFormat$AsyncSqlExecThread.run(Async SqlOutputFormat.java:230)

1 0

[MonetDB-users] Announcement: New Jul2012-SP2 Bugfix release of MonetDB suite
by Sjoerd Mullender 21 Sep '12

21 Sep '12

The MonetDB team at CWI/MonetDB BV is pleased to announce the Jul2012-SP2 bugfix release of the MonetDB suite of programs. More information about MonetDB can be found on our website at <http://www.monetdb.org/>. For details on this release, please see the release notes at <http://www.monetdb.org/Downloads/ReleaseNotes>. As usual, the download location is <http://dev.monetdb.org/downloads/>. Jul 2012-SP2 bugfix release Java Module * Fixed a bug where DatabaseMetaData.getURL() did return null:0 for hostname:port. MonetDB5 Server * Changed the way nclients maximum was calculated to avoid 'out of client slots' errors way before the maximum was reached. Merovingian * Resolved a problem where monetdb could fail to start a database with the message "database 'X' started up, but failed to open up a communication channel". Bug #3134, comment #7. MonetDB Common * Fixed a bug in BATantijoin when either side is a singleton BAT. This fixes bug 3139. Bug Fixes * 3117: test sql/test/BugTracker-2011/Tests/history.Bug-2909.sql produces extra profiling output since changeset 817328b74e2f * 3134: Database gets killed by timeout during startup * 3139: Not equal evaluation does not work * 3144: Memleak when connecting to a database (mclient and mapi) * 3145: mclient error when enabling history * 3150: Multiple string equality tests fail to match (Test_JdbcClient)

1 0

[MonetDB-users] time for ssbm
by guangliang peng 18 Sep '12

18 Sep '12

hi, my query schema is SSBM.My database size is 65G.There are five tables : lineorder 600038145 rows part 1400000 date 2556 supplier 1000000 customer 3000000 and my host have enough memory space up to 500G when i run query select sum(lo_extendedprice*lo_discount) as revenue from voc.lineorder, voc.dates where lo_orderdate = d_datekey and d_weeknuminyear = 6 and d_year = 1994 and lo_discount between 5 and 7 and lo_quantity between 26 and 35; the result is below | revenue | +===============+ | 2605756481323 | +---------------+ 1 tuple (6.2s) but if i delete the condition of " lo_discount between 5 and 7" the run result is more faster than the original one. query select sum(lo_extendedprice*lo_discount) as revenue from voc.lineorder, voc.dates where lo_orderdate = d_datekey and d_weeknuminyear = 6 and d_year = 1994 and lo_quantity between 26 and 35; +---------------+ | revenue | +===============+ | 7990711777299 | +---------------+ 1 tuple (410.451ms) at the same time ,if i delete the condition of "lo_quantity between 26 and 35" the run result is more faster than the original one too. query select sum(lo_extendedprice*lo_discount) as revenue from voc.lineorder, voc.dates where lo_orderdate = d_datekey and d_weeknuminyear = 6 and d_year = 1994 and lo_quantity between 26 and 35; +---------------+ | revenue | +===============+ | 7990711777299 | +---------------+ 1 tuple (463.617ms) i am confused and if the semijoin costs a lot of execution time ? Thank you for your help. best reguards, guangliang peng

1 0

[MonetDB-users] Disk space cleanup policy
by Jukka 17 Sep '12

17 Sep '12

Hi, What is the disk space cleanup policy of MonetDb? If I remove all rows of table with delete command, the disk utilization of dbfarm is still the same. The storage() function is still reporting the same size for the table as before the delete command only count of rows was decreased to zero. Also executing drop table sql statement does not seem to release the disk space. -- Jukka

1 0

[MonetDB-users] MonetDb and too many open files
by Jukka 17 Sep '12

17 Sep '12

Hi, How many files MonetDb is keeping open during runtime? I have running some test on MonetDb on RedHat 6 environment and faced the problem with the too many open files error during the loading phase after having several tables created to the database. I managed to avoid the current error with increasing the file handle limit: vi /etc/security/limits.conf #add for file handle #see lsof -p pid monetdb soft nofile 65536 monetdb hard nofile 65536 Now the system is running, but after 500 tables in MonetDb, I see about 17000 file handle listed with lsof -p command. The most of those are pointing to files in dbfarm folder. Is the files of all columns of all tables kept all the time? Is there formula to estimate the number file handles needed? Is there any limit how many tables or columns we can have in one MonetDb instance? The version used is "MonetDB Database Server v1.6 (Jul2012-SP1)" compiled from sources for RedHat 6. -- Jukka jukkakar(a)iki.fi

1 0

[MonetDB-users] MonetDb slowing down
by Cory Isaacson 07 Sep '12

07 Sep '12

We have MonetDb running in the AWS cloud, with about 32GB of physical RAM. Our process uses COPY INTO every few minutes to load small chunks of data (usually 1000 rows at a time). That seems to work fine. There are a few users running queries against MonetDb, and now at least once/day we have to start/stop MonetDb. We see very high disk I/O (mainly I/O wait), so it appears that memory usage is high and does not get released. We are using the April 2012 release. The JDBC client is used for these queries. Overall MonetDb is doing a very good job, but this slowdown makes it appear unstable to end users. If there are any suggestions on how to improve this please let us know. cmi --

2 1

[MonetDB-users] Connecting from DBLite.com
by Medha Atre 06 Sep '12

06 Sep '12

Hello, I have successfully installed and used MonetDB in the past as a standalone server, by connecting/querying through "mclient" running on the same machine where server is running. I was trying out web-based access, in which I was trying DBLite's simple web interface http://user.dblite.com (running on the browser on the same machine). My MonetDB server was compiled with "enable-sql", "enable-mserver5", and other optimization options. Not compiled with JDBC/ODBC though (but DBLite is a PHP based interface). "Control" is set to YES and "passphrase" is set to "monetdb" too. While the server is running, I can very well connect and query through command line mclient, but if I give "localhost", port as 50000 and default user/passwd "monetdb/monetdb" on the http://user.dblite.com interface, it keeps giving me "access denied" error. I am wondering what I am missing! Thanks. Medha

2 1

[MonetDB-users] source code structure
by guangliang peng 06 Sep '12

06 Sep '12

hi, i prepare to look at the source code of monnetdb.Can you guys give me some advices which can help reduce the time on the source code .And what's the source code structure? thanks, guangliang

1 0

[MonetDB-users] costmodel
by guangliang peng 06 Sep '12

06 Sep '12

hello, how do i show costmodel where i run a query ?because i want to know the internal execution of a query . thanks, guangliang

2 1

[MonetDB-users] monetdb join path
by guangliang peng 05 Sep '12

05 Sep '12

I now still feel confused about join_path .I have tried the trace ,but the results show many lines with MAL language.It is very hard for me to find out the join path and order.can anyone help me?

2 1

[MonetDB-users] Is there IF(), IFNULL() in SELECT?
by Dmitry Insta 31 Aug '12

31 Aug '12

Sorry if it was asked before, I can't find a comprehensive list of functions available. Is it possible to somehow implement something like this: SELECT IF(col1>0,'Negative','Positive') as Sign, IFNULL(col2,'Empty',col2) as col2 FROM table; // it's just an example, not the exact query :) Thanx!

2 1

[MonetDB-users] how to set see mserver5 config
by guangliang peng 31 Aug '12

31 Aug '12

hi, I want to see mserver5 configure for example dbfarm,dbname. I don't know the command and hwo i set the gdk-vmtrim =no .I don't know hwo to set the GDK PARAMETERS .Can you guys help me? best reguards, guangliang

2 1

[MonetDB-users] Migration DW to MonetDB
by R＠quel 28 Aug '12

28 Aug '12

Hi, I have a question, i need comparison the execution query times between MonetDB and SQL 2008 in Data Warehouse (applying a different orientations database systems). But i have a problem, i used the AdventureWorkR2 2008 but i don't know how i can migrate the information to MonetDB. To compare the same data. Someone help me? Please. It's very important. Thanks, Raquel -- View this message in context: http://old.nabble.com/Migration-DW-to-MonetDB-tp34348184p34348184.html Sent from the monetdb-users mailing list archive at Nabble.com.

2 1

[MonetDB-users] what's the trigger of monetdb releasing memory
by guangliang peng 27 Aug '12

27 Aug '12

hi , when I ran some queries on monetdb,I found that the memory was automatically released by monetdb.And it needs extra time to load data into memory again.I don't know why and if there are some triggers in monetdb? Thank you for helps. best reguards, guangliang

1 0

[MonetDB-users] New Grouping Implementation
by David893 26 Aug '12

26 Aug '12

Hi Folks, I've seen that you re-implemented the grouping functions. Will it have effect on performance (on non-ordered columns)? Right now we're running MonetDB on a 1billion data set, mostly for grouping and aggregating, we're very happy with the performance, but of-course, any improvement is highly welcome :). If it does affect performance, we'll be the first to test and report. you guys rock!, keep up the great work. -- View this message in context: http://old.nabble.com/New-Grouping-Implementation-tp34348175p34348175.html Sent from the monetdb-users mailing list archive at Nabble.com.

1 0

[MonetDB-users] monetdb crashed when using copy into .... locked
by li, xiaohua 24 Aug '12

24 Aug '12

Hi: does anybody know what's the problem with the copy into of locked? we want to use concurrent copy into to a table, seems montdb not good at this. some body says add locked, we try, but the database crached. we just test like this copy 200 OFFSET 1 RECORDS into f_activity from 'd:\bcp.txt' USING DELIMITERS '|','\n' NULL AS '' LOCKED seems need single user mode, but how to set single user mode? Lixiaohua Shanghai,China

2 2

[MonetDB-users] help
by guangliang peng 23 Aug '12

23 Aug '12

hello, can I use mserver5 to control loading data into memory or removing data from memory ? I don't know how to configure or the command.I am fresh new about Monetdb so please forgive my unknowing.Thank you very much for the commands. best regards, guangliang

2 1

[MonetDB-users] Announcement: New Jul2012-SP1 Bugfix release of MonetDB suite
by Sjoerd Mullender 23 Aug '12

23 Aug '12

The MonetDB team at CWI/MonetDB BV is pleased to announce the Jul2012-SP1 bugfix release of the MonetDB suite of programs. More information about MonetDB can be found on our website at <http://www.monetdb.org/>. For details on this release, please see the release notes at <http://www.monetdb.org/Downloads/ReleaseNotes>. As usual, the download location is <http://dev.monetdb.org/downloads/>. Jul 2012-SP1 bugfix release Java Module * Fixed adaptive cache size used when retrieving results, not to cause divide by zero errors when memory gets short, bug #3119. Client Package * mclient no longer prints the SQLSTATE at the start of each error returned by the SQL-server. MonetDB5 Server * The server now distinguishes between starting and started states, such that monetdbd can wait for it to finish starting. Merovingian * Starting a server now waits for as long as the server needs to possibly recover, bug #3134. In case of a long wait, the monetdbd logfile gives extra information on what the server is doing to recover. * Fixed a crash of monetdbd when local databases were unshared, bug #3135 * Resolved a problem where automatic starting of a database initiated by multiple clients at the same time could cause failed starts. Bug #3107 Bug Fixes * 3075: inconsistent declaration of algebra.markH with 3 input arguments * 3090: crashed if using single identifier for where condition * 3093: sql fail if use scalar subquery with alias * 3107: concurrent connections to the same stopped database yield in multiple mserver5 starts by monetdbd * 3119: MonetConnection$ResultSetResponse throws java.lang.ArithmeticException: divide by zero * 3132: test/BugTracker-2011/func_iter_vs_bulk.Bug-2826 fails * 3134: Database gets killed by timeout during startup * 3135: monetdbd crash while creating & loading database

1 0

[MonetDB-users] case insensitive
by li, xiaohua 22 Aug '12

22 Aug '12

Does MonetDB has some parameter to modify the case insensitive option? when end user write sql, usually we want to case insensitive. lixiaohua Shanghai,China

2 3

[MonetDB-users] perl dbd error:
by Marc Salomon 20 Aug '12

20 Aug '12

Hello, I am able to install MonetDB-11.11.5 and set up a database just fine. However when I install the perl modules from CPAN, I encounter this error when I try to connect: 2012-08-20 09:02:54 ERR merovingian[56170]: client error: client localhost:35633 sent challenge in incomplete block: Any idea what's wrong here? Are the CPAN modules and the distro perl modules stepping on one another? best, -marc

2 1

[MonetDB-users] MonetDB GDK cache
by Allen Zhang 17 Aug '12

17 Aug '12

Hi, there, We noticed when query a big set of data, the BAT storage grows in the same directory as the database itself, is that mean the temporary result gets written to disk? Is it possible we can assign the location for this cache to point to a SSD to speed up things? Best Regards Allen

1 0

[MonetDB-users] Limit memory usage
by Christian Braun 09 Aug '12

09 Aug '12

Hello, i would like to limit the memory usage of MonetDB to half of the physical available memory. This is on Debian 6.0 64-bit with 48GB memory. I added to /etc/default/monetdb: ulimit -v 25165824 On startup MonetDB still reports: 2012-08-08 13:21:30 MSG db[15678]: # Found 47.262 GiB available main-memory. cat /proc/15687/limits shows the limit: Limit Soft Limit Hard Limit Units Max address space 25769803776 25769803776 bytes Unfortunately on the first query i run the database gets killed: 2012-08-08 13:21:54 MSG merovingian[15663]: database 'db' (15678) was killed by signal SIGSEGV Is there a way to limit the memory usage of MonetDB on Linux? Package: monetdb5-server Version: 11.11.5-20120710 Regards and thanks, Christian.

3 3

Re: [MonetDB-users] MonetDB Python client
by Минц Алексей 07 Aug '12

07 Aug '12

Dear Fabian! Attached is the code, that reproduces the bug. SQL file creates tables needed, python file hangs on trying to receive data. My version of mapi2.py is free of this problem - it raises an exception instead. Regards, Alexey Mints

1 0

[MonetDB-users] Incorrect Results from Very Simple Queries
by Henry Addington 07 Aug '12

07 Aug '12

We are seeing a very strange behavior from MonetDB from simple queries on a single table. In monthly_tou_avg_price table, we have monthly average aggregate data that were inserted from a very large table (> 2 billion) with hourly data. We have created the aggregate table to speed up certain queries. Strangely, we are getting incorrect results from very simple queries on the aggregate table. Q1 below returns 9,890 records with yyyy_mm column having empty value for the 2012-07 records. All of the 2012-07 records are missing the yyyy_mm value. We ran the SQL statement that inserted those records and it does not show any empty yyyy_mm values. If we check for empty string or null value in yyyy_mm column (Q2 and Q3) against the aggregate table, we do not get any hits. If we query for yyyy_mm= '2012-07' as in Q4, we get exactly 9890 records showing yyyy_mm populated with value 2012-07. How could this be possible, Q1 showing empty yyyy_mm values for the same 9,890 records and Q4 showing 2012-07 yyyy_mm values? Q1: select * from monthly_tou_avg_price where header_id = 6 Q2: select * from monthly_tou_avg_price where header_id = 6 and yyyy_mm = '' Q3: select * from monthly_tou_avg_price where header_id = 6 and yyyy_mm is null Q4: select * from monthly_tou_avg_price where header_id = 6 and yyyy_mm = '2012-07' Q5 below returns empty value for yyyy_mm even though yyyy_mm column does not have any empty or null values. Q6 does not return any empty or null yyyy_mm values and contradicts Q5 result by returning 2012-07. Furthermore, Q7 contradicts Q5 with 9,890 records with 2012-07 value in yyyy_mm column. Q5: select distinct yyyy_mm from monthly_tou_avg_price where header_id = 6 Q6: select distinct yyyy_mm from monthly_tou_avg_price Q7: select * from monthly_tou_avg_price where header_id = 6 and years = 2012 and months = 7 yyyy_mm L15 9890 2009-04 7574 2009-05 7574 2009-06 7750 2009-07 7786 2009-08 7788 2009-09 7828 2009-10 7814 2009-11 7844 2009-12 8322 2010-01 8317 2010-02 8363 2010-03 8361 2010-04 9214 2010-05 9124 2010-06 9156 2010-07 9165 2010-08 9195 2010-09 9197 2010-10 9198 2010-11 9234 2010-12 9232 2011-01 9246 2011-02 9238 2011-03 9696 2011-04 9672 2011-05 9670 2011-06 9668 2011-07 9656 2011-08 9698 2011-09 9682 2011-10 9724 2011-11 9706 2011-12 9768 2012-01 9766 2012-02 9764 2012-03 9832 2012-04 9824 2012-05 9826 2012-06 9902 We also ran an UPDATE statement to set yyyy_mm to 2012-07 for rows with header_id = 6 and years = 2012 and months = 7. And, 9,890 records were successfully updated. However, Q1 through Q8 returned same results as above with no improvement. We have not seen this kind of issues in other tables. This problem seems to be limited to a table that is populated with an INSERT INTO statement. We checked the result returned by the select portion of Q8 and yyyy_mm is populated with 2012-07. But, the aggregate table seems to end up in a weird state where it returns incorrect results. Q8: insert into "monthly_tou_avg_price" select a.header_id, extract(year from a.opr_date) as y, extract(month from a.opr_date) as m, b.yyyymm as yyyy_mm, b.svalue as TOU, a.resource_name, round(avg(a.lmp_cong_prc),5), round(avg(a.lmp_ene_prc),5), round(avg(a.lmp_loss_prc),5), round(avg(a.lmp_prc),5), round(avg(a.ns_clr_prc),5), round(avg(a.rd_clr_prc),5), round(avg(a.ru_clr_prc),5), round(avg(a.sp_clr_prc),5), round(avg(a.shadow_prc),5), round(avg(a.fuel_prc),5), count(lmp_cong_prc) as actual_lmpcong_tou_count from oasislive.price a join oasislive.time b on a.yyyymmddhh = b.yyyymmddhh where a.opr_date between '2012-07-01' and '2012-07-31' group by a.header_id, y, m, yyyy_mm, TOU, a.resource_name order by y, m, a.header_id, TOU, a.resource_name; We can see this INSERT INTO related issue with other queries. Q9 shows that we do not have any values for 2011-03 ON period which is incorrect. In fact, if we specify '2011-03' as in Q10, it shows that we do in fact have values for the 2011-03 ON period! Q9: select yyyy_mm, tou, avg(lmp_prc) from monthly_tou_avg_price group by yyyy_mm, tou order by yyyy_mm, tou yyyy_mm tou L6 . . 2011-03 OFF 16.721532797520894 2011-03 ON (null) 2011-04 OFF 15.427080074671187 . . Q10: select yyyy_mm, tou, avg(lmp_prc) from monthly_tou_avg_price where yyyy_mm = '2011-03' group by yyyy_mm, tou order by yyyy_mm, tou yyyy_mm tou L11 2011-03 OFF 16.72153279752101 2011-03 ON 30.276486575893575 I apologize for the long-winded email. I just wasn't sure how to describe what I was seeing.... Please let me know if there is any additional information that I can provide you with. By the way, we are currently using August 2011 -SP2 release, but saw this issue in older releases as well. Best regards, Henry We are currently running MonetDB August 2011 SP2 release on CentOS

2 4

[MonetDB-users] Trigger: BEFORE INSERT
by Tapomay Dey 02 Aug '12

02 Aug '12

create table tt(id int, name varchar(20), value int); create table t2(id int); CREATE TRIGGER trg BEFORE INSERT ON tt REFERENCING NEW as newrow FOR EACH ROW BEGIN ATOMIC INSERT INTO t2 (id) values (newrow.id); END insert into tt values(1, 'a', 10); insert into tt values(2, 'b', 20); insert into tt values(3, 'a', 30); insert into tt values(4, 'a', 40); The result vales in t2 are: After insert#1: EMPTY After insert#2: {1} After insert#3: {1, 1, 2} After insert#4: {1, 1, 2,1,2,3} Tested this in Mysql and the same trigger works well there. Expected t2 values after insert#4: {1,2,3,4} Regards, Tapomay.

1 1

[MonetDB-users] Monetdb compilation from source on 32 bit machine
by Tapomay Dey 01 Aug '12

01 Aug '12

I checked the code at location and found that "value" is of type long and its bit precision is 61. I am trying to perform make on an Ubuntu 10.04 i686 architecture which is 32-bit In file included from xid.c:23: xid.h:42: error: width of ‘value’ exceeds its type xid.c: In function ‘XIDcompress’: xid.c:138: warning: format ‘%ld’ expects type ‘long int’, but argument 4 has type ‘BUN’ xid.c:161: warning: format ‘%ld’ expects type ‘long int’, but argument 4 has type ‘BUN’ xid.c: In function ‘XIDcolumndump’: xid.c:298: warning: format ‘%lo’ expects type ‘long unsigned int’, but argument 4 has type ‘oid’ make[7]: *** [libmal_la-xid.lo] Error 1

2 1

[MonetDB-users] group by cube
by DADOU 01 Aug '12

01 Aug '12

hello, Have monetdb operator OLAP like group by cube as oracle have i don't find any operator from CUBE or ROLLUP. Thunks -- View this message in context: http://old.nabble.com/group-by-cube-tp34241097p34241097.html Sent from the monetdb-users mailing list archive at Nabble.com.

2 1

[MonetDB-users] Slowdown in Jul2012 release
by Viktor Rosenfeld 01 Aug '12

01 Aug '12

Hi, I've noticed a slowdown in the Jul2012 which appears to be due to disk I/O. Printed below is the output of TRACE on the Jul2012 (11.11.5) release and the Apr2012-SP2 release (11.9.7) of the following query: #+BEGIN_EXAMPLE WITH span1 AS ( SELECT node.id FROM node ), solutions AS ( SELECT DISTINCT span1.id AS id1 FROM span1 ) SELECT count(*) FROM solutions #+END_EXAMPLE Jul2012: #+BEGIN_EXAMPLE +---------+-----------------------------------------------------------------------------------+ | ticks | stmt | +---------+-----------------------------------------------------------------------------------+ | 3 | X_1 := sql.mvc(); | | 11 | X_2:bat[:oid,:int] =<tmp_1230>[1262014] := sql.bind(X_1=0,"annis","node","id",0); | | 5 | X_7:bat[:oid,:oid] =<tmp_1366>[0] := sql.bind_dbat(X_1=0,"annis","node",1); | | 6 | X_9=<tmpr_1366>[0] := bat.reverse(X_7=nil:bat[:oid,:oid]); | | 13 | X_10=<tmp_2126>[1262014] := algebra.kdifference(X_2=nil:bat[:oid,:int],X_9=nil); | | 3543662 | (ext22=<tmp_2127>[1262014],grp20) := group.done(X_10=<tmp_2126>[1262014]); | | 18 | X_13=<tmp_2130>[1262014] := bat.mirror(ext22=nil); | | 82193 | X_14=<tmp_2131>[1262014] := algebra.leftjoin(X_13=nil,X_10=nil); | | 2185 | X_15 := aggr.count(X_14=nil); | | 15 | sql.exportValue(1,"annis.solutions","L1","wrd",64,0,6,X_15=1262014:wrd,""); | | 8 | end s0_1; | | 18 | function user.s0_1(); | | 3629118 | X_5:void := user.s0_1(); | +---------+-----------------------------------------------------------------------------------+ #+END_EXAMPLE This query is accompanied by a lot of disk I/O (both reading and writing) Apr2012-SP2: #+BEGIN_EXAMPLE +-------+-----------------------------------------------------------------------------------+ | ticks | stmt | +-------+-----------------------------------------------------------------------------------+ | 4 | X_1 := sql.mvc(); | | 12 | X_2:bat[:oid,:int] =<tmp_1471>[1262014] := sql.bind(X_1=0,"annis","node","id",0); | | 6 | X_7:bat[:oid,:oid] =<tmp_1365>[0] := sql.bind_dbat(X_1=0,"annis","node",1); | | 6 | X_9=<tmpr_1365>[0] := bat.reverse(X_7=nil:bat[:oid,:oid]); | | 14 | X_10=<tmp_2074>[1262014] := algebra.kdifference(X_2=nil:bat[:oid,:int],X_9=nil); | | 12116 | (ext22=<tmp_2107>[1262014],grp20) := group.done(X_10=<tmp_2074>[1262014]); | | 2427 | X_13=<tmp_2106>[1262014] := bat.mirror(ext22=nil); | | 46 | X_14=<tmp_2111>[1262014] := algebra.leftjoin(X_13=nil,X_10=nil); | | 6 | X_15 := aggr.count(X_14=nil); | | 11 | sql.exportValue(1,"annis.solutions","L1","wrd",64,0,6,X_15=1262014:wrd,""); | | 6 | end s0_1; | | 16 | function user.s0_1(); | | 15566 | X_5:void := user.s0_1(); | +-------+-----------------------------------------------------------------------------------+ #+END_EXAMPLE There is no disk I/O during this query. Notice the difference in runtime of the group.done statement in line 5. This statement is introduced by the DISTINCT in the query. Cheers, Viktor

1 0

[MonetDB-users] Multiplex-funnel cluster failover: master-master replication
by Tapomay Dey 31 Jul '12

31 Jul '12

Hi, I have setup a cluster of 3 machines with following tags: mydb/1/master, mydb/2/master, mydb/3/master On a fourth machine I have created a multiplex funnel as follows: monetdb create -m monetdb+monetdb@*/mydb/1/master,monetdb+monetdb@*/mydb/2/master,monetdb+monetdb@*/mydb/3/master mydbmaster My objective here is that I use this multiplex for only DDL/INSERTS/UPDATES. This would ensure replication on all the 3 masters thus achieving a hacked form of master-master replication. Then I could use any one of the masters for analytics querying. However I am stuck with the following issues while handling fail-over. 1. I expect that if one of the boxes die, others keep getting the updates until I realize the failure. The I could lock the multiplex, sync the dbfarms to catch up the failing db and then release the multiplex. 2. If the box with tag mydb/3/master dies, then the updates go to 1 and 2. But if mydb/1/master dies the none of the dbs get any more updates. Looks like the multiplex returns on the first failure without trying rest of the dbs. Any pointers as to where do I change this sequential failure logic? Also what do you think about my replication approach? Thanks and Regards, Tapomay

1 0

[MonetDB-users] Incorrect Results from Very Simple Queries ---- Updated
by Henry Addington 31 Jul '12

31 Jul '12

Please ignore my earlier email. I accidently sent the email before it was completed! We are seeing a very strange behavior from MonetDB from simple queries on a single table. In monthly_tou_avg_price table, we have monthly average aggregate data that were inserted from a very large table (> 2 billion) with hourly data. We have created the aggregate table to speed up certain queries. Strangely, we are getting incorrect results from very simple queries on the aggregate table. Q1 below returns 9,890 records with yyyy_mm column having empty value for the 2012-07 records. All of the 2012-07 records are missing the yyyy_mm value. We ran the SQL statement that inserted those records and it does not show any empty yyyy_mm values. If we check for empty string or null value in yyyy_mm column (Q2 and Q3) against the aggregate table, we do not get any hits. If we query for yyyy_mm= '2012-07' as in Q4, we get exactly 9890 records showing yyyy_mm populated with value 2012-07. How could this be possible, Q1 showing empty yyyy_mm values for the same 9,890 records and Q4 showing 2012-07 yyyy_mm values? Q1: select * from monthly_tou_avg_price where header_id = 6 Q2: select * from monthly_tou_avg_price where header_id = 6 and yyyy_mm = '' Q3: select * from monthly_tou_avg_price where header_id = 6 and yyyy_mm is null Q4: select * from monthly_tou_avg_price where header_id = 6 and yyyy_mm = '2012-07' Q5 below returns empty value for yyyy_mm even though yyyy_mm column does not have any empty or null values. Q6 does not return any empty or null yyyy_mm values and contradicts Q5 result by returning 2012-07. Furthermore, Q7 contradicts Q5 with 9,890 records with 2012-07 value in yyyy_mm column. Q5: select distinct yyyy_mm from monthly_tou_avg_price where header_id = 6 Q6: select distinct yyyy_mm from monthly_tou_avg_price Q7: select * from monthly_tou_avg_price where header_id = 6 and years = 2012 and months = 7 We also ran an UPDATE statement to set yyyy_mm to 2012-07 for rows with header_id = 6 and years = 2012 and months = 7. And, 9,890 records were successfully updated. However, Q1 through Q8 returned same results as above with no improvement. We have not seen this kind of issues in other tables. This problem seems to be limited to a table that is populated with an INSERT INTO statement. We checked the result returned by the select portion of Q8 and yyyy_mm is populated with 2012-07. But, the aggregate table seems to end up in a weird state where it returns incorrect results. Q8: insert into "monthly_tou_avg_price" select a.header_id, extract(year from a.opr_date) as y, extract(month from a.opr_date) as m, b.yyyymm as yyyy_mm, b.svalue as TOU, a.resource_name, round(avg(a.lmp_cong_prc),5), round(avg(a.lmp_ene_prc),5), round(avg(a.lmp_loss_prc),5), round(avg(a.lmp_prc),5), round(avg(a.ns_clr_prc),5), round(avg(a.rd_clr_prc),5), round(avg(a.ru_clr_prc),5), round(avg(a.sp_clr_prc),5), round(avg(a.shadow_prc),5), round(avg(a.fuel_prc),5), count(lmp_cong_prc) as actual_lmpcong_tou_count from oasislive.price a join oasislive.time b on a.yyyymmddhh = b.yyyymmddhh where a.opr_date between '2012-07-01' and '2012-07-31' group by a.header_id, y, m, yyyy_mm, TOU, a.resource_name order by y, m, a.header_id, TOU, a.resource_name; We can see this INSERT INTO related issue with other queries. Q9 shows that we do not have any values for 2011-03 ON period which is incorrect. In fact, if we specify '2011-03' as in Q10, it shows that we do in fact have values for the 2011-03 ON period! Q9: select yyyy_mm, tou, avg(lmp_prc) from monthly_tou_avg_price group by yyyy_mm, tou order by yyyy_mm, tou yyyy_mm tou L6 . . 2011-03 OFF 16.721532797520894 2011-03 ON (null) 2011-04 OFF 15.427080074671187 . . Q10: select yyyy_mm, tou, avg(lmp_prc) from monthly_tou_avg_price where yyyy_mm = '2011-03' group by yyyy_mm, tou order by yyyy_mm, tou yyyy_mm tou L11 2011-03 OFF 16.72153279752101 2011-03 ON 30.276486575893575 I apologize for the long-winded email. I just wasn't sure how to describe what I was seeing.... Please let me know if there is any additional information that I can provide you with. By the way, we are currently using August 2011 -SP2 release, but saw this issue in older releases as well. Best regards, Henry We are currently running MonetDB August 2011 SP2 release on CentOS

1 0

[MonetDB-users] Repeatedly writing to MonetDB
by Jerry Ramey 29 Jul '12

29 Jul '12

We are encountering a frequent error when writing to MonetDb repeatedly using the Java MAPI socket. We are running the April 2012 release. The error is: [7/29/12 12:10:26 PM] Cory Isaacson: 000!TypeException:user.s0_2[2]:'calc.str' undefined in: _3:any := calc.str(_4:str) 22000!TypeException:user.s0_2[3]:'calc.str' undefined in: _5:any := calc.str(_6:str) 22000!TypeException:user.s0_2[4]:'calc.str' undefined in: _7:any := calc.str(_8:str) 22000!TypeException:user.s0_2[5]:'calc.str' undefined in: _9:any := calc.str(_10:str) 22000!TypeException:user.s0_2[6]:'calc.str' undefined in: _11:any := calc.str(_12:str) The only solution is to stop the farm and restart the farm/database. We have a single Java process writing to the database using MAPI, in batches of 1000 rows at a time (or less), using the COPY INTO syntax based on the example Java loader.We have a single Java process writing to the database using MAPI, in batches of 1000 rows at a time (or less), using the COPY INTO syntax based on the example Java loader. Here are the important snippets of the Java code. You can see that we are opening/closing a connection for each batch, and we have only a single thread performing this function, no other processes are writing to the database. We do have other connections reading from the database (but in the most recent case we only had idle connections). This is running on CentOS 5.4, with Java 1.6. There is no swap space configured on this server (we read that this may be a requirement). The data volumes are very small at this point, only a few million rows. String query = "COPY " + (dataRowList.size() + 10) + " RECORDS INTO " + tableName + " FROM STDIN USING DELIMITERS '\\t','\\n' NULL AS '\\\\N';"; if(TRACE) logger.trace("commit: query : " + query); // the leading 's' is essential, since it is a protocol // marker that should not be omitted, likewise the // trailing semicolon out.write('s'); out.write(query); out.newLine(); // Write all data rows. for(String dataRow : dataRowList) { if(TRACE) logger.trace("commit: Writing data row: " + dataRow + " dataRow ends in newline: " + dataRow.endsWith("\n")); // The dataRow is \n terminated, so no need to output newLine to output stream. out.write(dataRow); } out.writeLine(""); // need this one for synchronisation over flush() error = in.waitForPrompt(); if (error != null) throw new Exception(error); out.writeLine(""); // server wants more, we're going to tell it, this is it error = in.waitForPrompt(); if (error != null) throw new Exception(error); // // disconnect from server // server.close(); } catch (IOException e) { logger.error("Unable to connect", e); throw new RuntimeException("Unable to connect", e); } catch (Throwable th) { logger.error("Commit error", th); ... throw new RuntimeException("Commit error: tableName: " + tableName, th); } finally { try { if(server != null) { server.close(); server = null; } } catch (Throwable th) { logger.error("Error closing MonetDb server connection", th); } } Thanks, Jerry

1 0

[MonetDB-users] Repeatedly writing to MonetDB
by Jerry Ramey 29 Jul '12

29 Jul '12

We are encountering a frequent error when writing to MonetDb repeatedly using the Java MAPI socket. We are running the April 2012 release. The error is: [7/29/12 12:10:26 PM] Cory Isaacson: 000!TypeException:user.s0_2[2]:'calc.str' undefined in: _3:any := calc.str(_4:str) 22000!TypeException:user.s0_2[3]:'calc.str' undefined in: _5:any := calc.str(_6:str) 22000!TypeException:user.s0_2[4]:'calc.str' undefined in: _7:any := calc.str(_8:str) 22000!TypeException:user.s0_2[5]:'calc.str' undefined in: _9:any := calc.str(_10:str) 22000!TypeException:user.s0_2[6]:'calc.str' undefined in: _11:any := calc.str(_12:str) The only solution is to stop the farm and restart the farm/database. We have a single Java process writing to the database using MAPI, in batches of 1000 rows at a time (or less), using the COPY INTO syntax based on the example Java loader.We have a single Java process writing to the database using MAPI, in batches of 1000 rows at a time (or less), using the COPY INTO syntax based on the example Java loader. Here are the important snippets of the Java code. You can see that we are opening/closing a connection for each batch, and we have only a single thread performing this function, no other processes are writing to the database. We do have other connections reading from the database (but in the most recent case we only had idle connections). This is running on CentOS 5.4, with Java 1.6. There is no swap space configured on this server (we read that this may be a requirement). The data volumes are very small at this point, only a few million rows. String query = "COPY " + (dataRowList.size() + 10) + " RECORDS INTO " + tableName + " FROM STDIN USING DELIMITERS '\\t','\\n' NULL AS '\\\\N';"; if(TRACE) logger.trace("commit: query : " + query); // the leading 's' is essential, since it is a protocol // marker that should not be omitted, likewise the // trailing semicolon out.write('s'); out.write(query); out.newLine(); // Write all data rows. for(String dataRow : dataRowList) { if(TRACE) logger.trace("commit: Writing data row: " + dataRow + " dataRow ends in newline: " + dataRow.endsWith("\n")); // The dataRow is \n terminated, so no need to output newLine to output stream. out.write(dataRow); } out.writeLine(""); // need this one for synchronisation over flush() error = in.waitForPrompt(); if (error != null) throw new Exception(error); out.writeLine(""); // server wants more, we're going to tell it, this is it error = in.waitForPrompt(); if (error != null) throw new Exception(error); // // disconnect from server // server.close(); } catch (IOException e) { logger.error("Unable to connect", e); throw new RuntimeException("Unable to connect", e); } catch (Throwable th) { logger.error("Commit error", th); ... throw new RuntimeException("Commit error: tableName: " + tableName, th); } finally { try { if(server != null) { server.close(); server = null; } } catch (Throwable th) { logger.error("Error closing MonetDb server connection", th); } } Thanks, Jerry

1 0

[MonetDB-users] substing made monetdb very very slow
by li, xiaohua 27 Jul '12

27 Jul '12

Hi all: we are testing monetdb on a sql select substring(fact_bk,1,1) as aa,sum(1) as recordcount from f_activity group by aa the table f_activity have about 5 million rows. when i run this sql, monetdb need about 30 seconds . (if we use another no calculated column, it need only 1-3 seconds) when I run this sql on sql server, it needs only 7 seconds. is monetdb not good at calculated column? or we have made some mistake? please tell me the reason, thank you. lixiaohua Shanghai,China

2 4

[MonetDB-users] how to access remote server in windows
by li, xiaohua 26 Jul '12

26 Jul '12

Hi all: we want to copy a text file into a remote server, we don't know how to set the mapi_open = yes on windows. we try add --set "mapi_open= yes" in the M5server.bat . but we don't know whether it take effect. how can we know? when we use jdbc or odbc to access a remote monetdb database. we try to use jdbc:monetdb://dvs001:5000/demo. or change the odbc host to an ip address: 192.168.1.100. we can't connect to the database. only we use localhost can we connect to the database. does monetdb support remote access in windows? lixiaohua Shanghai,China

3 7

[MonetDB-users] can't copy into a remote server in windows
by li, xiaohua 26 Jul '12

26 Jul '12

Hi all: we want to copy a txt file into a remote monetdb (windows). if we copy into local monetdb via ipaddress, it's OK. but if we copy the same txt file into a remote monetdb, it can't. Error: could not open file 'd:\\share\\book1.csv': Operation not permitted SQLState: 22000 ErrorCode: 0 what's the problem? is it a bug? or something we don't know? lixiaohua Shanghai,China

3 3

[MonetDB-users] where is demo database physiquely in my SERVER
by DADOU 25 Jul '12

25 Jul '12

hello, i don't find in my PC the demo database, i had setup monetdb (MonetDB5-SQL-Installer-x86_64-20120607.msi) in my PC and in load the server with C:\Program Files\MonetDB\MonetDB5\M5server.bat I create user and connect with him in default database "demo", i created tables and loaded data. but i don't know where are data is stored in my machine, I want the path of database demo. thunks -- View this message in context: http://old.nabble.com/where-is-demo-database-physiquely-in-my-SERVER-tp3421… Sent from the monetdb-users mailing list archive at Nabble.com.

2 1

[MonetDB-users] COPY INTO: insufficient privileges: binary COPY INTO requires administrator rights
by 万萌 25 Jul '12

25 Jul '12

Hi guys, i got the following error when COPY INTO TABLE test: sql>COPY INTO test from ('/home/svom/log3'); COPY INTO: insufficient privileges: binary COPY INTO requires administrator rights the file "log3" is in mode 777, so i dont know why this happend, thanks for help! Wan meng SVOM, NAOC

5 6

[MonetDB-users] Billions of rows
by Benjie Chen 20 Jul '12

20 Jul '12

Hi >From one big dataset, we already have 0.7 billion rows. And we are looking at having 100 datasets eventually over the period of a year. That's 70 billion rows. From what I understand, column data are loaded into virtual address space, then dynamically indexed for querying? Does that mean that on a query "SELECT a FROM table WHERE b = N", it'd have to load all of 70 billion values of b, index, then provide results for a? Is this a case where statically created index would help? Does MonetDB use static created index? Thanks, Benjie

2 1

[MonetDB-users] CREATE AGGREGATE error
by Asterios Katsifodimos 18 Jul '12

18 Jul '12

Hello, I am trying to define an aggregate function as I have seen in an old message in this list: http://sourceforge.net/mailarchive/message.php?msg_id=20582949 I am trying to define it as: CREATE AGGREGATE group_concat (BASETYPE = text, SFUNC = _group_concat, STYPE = text); And I get this error: 42000!syntax error, unexpected '=' in: "create aggregate group_concat (basetype =" Any ideas on what I'm doing wrong? I have already defined the _group_concat function as described in the same message mentioned earlier. Running MonetDB v11.9.5 (Apr2012-SP1) on Linux. thank you, Asterios

3 4

[MonetDB-users] Announcement: New Jul2012 Feature release of MonetDB suite
by Fabian Groffen 17 Jul '12

17 Jul '12

The MonetDB team at CWI/MonetDB BV is pleased to announce the Jul2012 feature release of the MonetDB suite of programs. More information about MonetDB can be found on our website at <http://www.monetdb.org/>. For details on this release, please see the release notes at <http://www.monetdb.org/Downloads/ReleaseNotes>. As usual, the download location is <http://dev.monetdb.org/downloads/>. Jul 2012 feature release Build Environment * Created seperate RPM and DEB packages for MonetDB/JAQL. * Removed --enable-bits option from configure. * Split the MonetDB-client-ruby RPM package into two and named them in accordance with the Fedora packaging guidelines as rubygem-<gem-name>. SQL * COPY INTO now accepts optional parenthesis for file argument. Binary COPY INTO now requires 'COPY BINARY INTO'. Client Package * ODBC: Fixed a bug where SQLNativeSql expected a statment handle instead of a connection handle. MonetDB5 Server * Crackers code has been removed. Development continues in the holindex branch. Merovingian * Fixed misc memory leaks, which caused monetdbd to grow in memory size over time. * Removed erroneously (re-)added master and slave properties, this functionality is currently not working. MonetDB Common * Fixed intermittent problem that joins and selects return incorrect results and possibly inconsistent databases. The problems only occurred after a series of queries and updates, therefore it was hard to reproduce. * The sorted property, which was used to maintain whether a column in a BAT was sorted or reverse sorted, has been replaced by a pair of properties, sorted and revsorted. These new properties can be set independently (unlike the old sorted property), and so if both are set, the column must be constant. In addition, internal property checking has been overhauled. Now, when a property is set incorrectly, and when assertions are enabled, an assertion will go off. There is also a function which can derive properties. * Implemented proper overflow checking on all arithmetic operations. Bug Fixes * 3016: Overflowing double multiplication leads to incorrect result * 3091: Since Apr2012-SP1 !TypeException:user.s11_1[59]:'bat.reverse' undefined in: _89:any := bat.reverse(_86:wrd) * 3099: ambiguous attributes in query with WITH clause and EXISTS clause * 3100: charset problem with the odbc driver for windows * 3103: display_size and internal_size of Cursor.description or incorrect * 3105: Leaking using Python * 3109: Wrong order in autoload mal script causes warning on startup * 3111: memory leak, monetdb set/get command * 3112: Median over temporal domains * 3113: Cannot set value of indexed column when doing UPDATE * 3114: Foreign Key prblems * 3116: Segfault in SQL

1 0

[MonetDB-users] how to use DataCell
by Greg Aumann 17 Jul '12

17 Jul '12

I would like to start experimenting with MonetDB/DataCell but am having trouble getting started. I read M. Kersten, E. Liarou, and R. Goncalves. A Query Language for a Data Refinery Cell. In EDA-PS, 2007. In section 2.1 of that paper it has the following syntax for creating a basket: create basket X( tag timestamp default now(), id serial, payload integer ); When I input this to mclient (Apr2012-SP2 version) I get: 42000!syntax error, unexpected IDENT, expecting INDEX in: "create basket" In the source code in the file sql/test/BugTracker-2011/Tests/UDF_in_schema.Bug-2817.sql begins with: create schema datacell; create table datacell.basket_X( id integer auto_increment, tag timestamp default now(), payload integer ); This obviously resembles the above but seems like it is creating a normal table rather than a basket. Has the syntax for creating a basket changed? Or should I load/enable the datacell extension in some way? thanks Greg

2 1

[MonetDB-users] Arrays or BATs as SQL column?
by Stefan de Konink 13 Jul '12

13 Jul '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Is there currently any possibility to store arrays or full BATs in a MonetDB5/SQL column which can be referenced later on? I'm looking for a support "database native" serialisation. Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREKAAYFAlAAGyUACgkQYH1+F2Rqwn0mgwCdEBGeN+ULO0wH3nOG5SVhuna8 OqwAniKRa9qq6pr5pUnr90m+9MtlWbtH =XLkD -----END PGP SIGNATURE-----

2 3

[MonetDB-users] MonetDB connector for Matlab
by BOOM Bas 13 Jul '12

13 Jul '12

Hi, I developed a monetdb connector for matlab based on the mysql connector for matlab. If you have comments or suggestion how to improve it let me know. Cheers, Bas Below are the instruction how to compile and use the connector (hopes this is clear) Install Monetdb: ./configure --prefix=/usr/local/MonetDB --exec-prefix=/usr/local/MonetDB make make install Linux (not tested for Window yet): In matlab mex -I/usr/local/MonetDB/include/monetdb -L/usr/local/MonetDB/lib -lmapi monetdbv2.cpp monetdbv2(host,user,password,dbName,'OPEN'); monetdbv2(host,user,password,dbName,'INSERT INTO table VALUES (value1, 1)' ); [value1 value2] = monetdbv2(host,user,password,dbName,'SELECT * FROM table' ); monetdbv2(host,user,password,dbName,'CLOSE'); Simple matlab interface to MonetDB server Bastiaan Boom, University of Edinburgh, 13 July 2012 Based on the MySQL connector of Matlab (www.mathworks.com/matlabcentral/fileexchange/8663-mysql-database-connector) -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.

1 0

[MonetDB-users] Master-slave replication support
by Tapomay Dey 12 Jul '12

12 Jul '12

I found monetdb options in the docs to setup master and slave. However no documentation explaining what to do after setting the properties. I have an older monetdb setup with lot of data, set master=yes. I installed monetdb on another machine(nightly build says slave option not found, so using stable build for the new installation) set slave=mapi:monetdb://host:port/db I have no idea what to do next. I saw http://www.monetdb.org/Documentation/Cookbooks/Recipes/Cluster, but that's not what I want. I am guessing its a work in progress. If it is so, are you planning to release it in July? Regards, Tapomay.

3 3

Re: [MonetDB-users] MonetDB Python client
by Alexey Mints 12 Jul '12

12 Jul '12

Dear Fabian! The problem appears with "classical" mapi2.py when server drops the connection without closing it correctly. This happens with some incorrect SQLs (sometimes error diagnostics simply fails). recv(bytes) hangs in this case. I have faced this problem before with sockets, and the only solution I know so far is select() method. I raise socket.error only in the case of such hard connection failure. So it does not seem too harsh. At least it is better than thread-blocking. Regards, Alexey Mints

2 1

[MonetDB-users] Scale
by Benjie Chen 11 Jul '12

11 Jul '12

Hi We are currently setup to use MonetDB to capture data from our mass spec machines. We generate about 30GB of data per day, so looking at a few TB of data per year. We are curious to hear what others who have used MonetDB, handle storage scaling. What kind of hardware do you use? Is there distributed/federated support in MonetDB? Are there map/reduce techniques you've used over the data, etc. Thanks, Benjie

1 0

[MonetDB-users] mserver crash under load -16G data, 10 queries each from 2 remote clients
by Tapomay Dey 10 Jul '12

10 Jul '12

I have a database with Single table. 15 million rows. 16G of data. 58 columns. MonetDB stores it consuming 32G of data. mserver Machine specs: Main memory: 4G Processor: Intel(R) Xeon(R) CPU E5645 @ 2.40GHz. Single core. I am performing a test to see how much time it takes if I fire this query multiple times from different machines. Case 1: I fire an aggregation query 10 times from a remote machine with 5sec interval between each firing. The result hs 17000 rows with around 4 MB of data. Memory usage of mserver process reahes a peak of 73% mclients finish within 43 to 48 seconds. Case 2: I do the same as above but now from 2 remote machines simultaneously. Memory usage of mserver process reahes a peak of 73% again. It keeps fluctuating between 70 and 73%. But after some time mserver restarts and the clients terminate with all the 10 clients on each of both machines saying: ERROR = !Connection terminated MAPI = tapomay@54.251.11.181:3306 ACTION= read_line QUERY = select id1, id2, id3, id4, id5, count(*), sum(metric1), avg(metric2), sum(metric3), sum(metric4), sum(metric5), sum(metric6), sum(metric7), sum(metric8), sum(metric9), sum(metric9), sum(metric10), sum(metric11), sum(metric12), sum(metric13) from tablename group by id1, id2, id3, id4, id5; Each query terminates within 5 to 50 seconds with the above error. In both cases intial state of mserver consumes around 0.5% memory. Also tested the same under other competing columnar DBs. They complete the case 2 in around 350 or more seconds average. They complete case 1 in 200 seconds average. Following is a last few lines of tail of merovingian.log 2012-07-05 06:30:42 MSG merovingian[31153]: proxying client 1.compute.amazonaws.com:45476 for database 'tablename' to mapi:monetdb:/$ 2012-07-05 06:30:42 MSG merovingian[31153]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-07-05 06:30:45 MSG merovingian[31153]: proxying client 2.amazonaws.com:46225 for database 'tablename' to mapi:monetdb:///mnt/tapomay$ 2012-07-05 06:30:45 MSG merovingian[31153]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-07-05 06:30:47 MSG merovingian[31153]: proxying client 1.compute.amazonaws.com:45477 for database 'tablename' to mapi:monetdb:/$ 2012-07-05 06:30:47 MSG merovingian[31153]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-07-05 06:30:50 MSG merovingian[31153]: proxying client 2.amazonaws.com:46226 for database 'tablename' to mapi:monetdb:///mnt/tapomay$ 2012-07-05 06:30:50 MSG merovingian[31153]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-07-05 06:30:52 MSG merovingian[31153]: proxying client 1.compute.amazonaws.com:45478 for database 'tablename' to mapi:monetdb:/$ 2012-07-05 06:30:52 MSG merovingian[31153]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-07-05 06:30:55 MSG merovingian[31153]: proxying client 2.amazonaws.com:46241 for database 'tablename' to mapi:monetdb:///mnt/tapomay$ 2012-07-05 06:30:55 MSG merovingian[31153]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-07-05 06:30:59 MSG merovingian[31153]: database 'tablename' (1048) was killed by signal SIGKILL Is there a config that would ask mserver to not kill itself and keep processing at the cost of query execution time. A few more tens of seconds won't harm much. Thanks and Regards, Tapomay.

4 10

Re: [MonetDB-users] MonetDB Python client
by Alexey Mints 09 Jul '12

09 Jul '12

Hi, Fabian! Yeh, I have shifted try outside of loop. I am not a big expert in this, but does it make any difference? Alexey.

2 1

[MonetDB-users] Expected query to be much faster, but is actually two orders of magnitude slower!
by Shahbaz 05 Jul '12

05 Jul '12

Hi All, I did some experiments with monetdb over the weekend and found some strange and unexpected behavior. My database has a single table which stores stock trades. The table is defined as follows: create table trades( td varchar(2), // just a dummy field date int, time int, ticker varchar(17), price double, qty int, vol int, conditioncode int, exch varchar(8)); This table has a little under 1 Billion rows and takes up around 52 gigabytes. The source data is also around 48 gigabytes. I expected monetdb to aggressively compress the columns and reduce the disk usage by 10 fold or so! In any case, that is not the main issue. [select sum(date), sum(time), count(ticker) from trades where date = 20120501;] This query took 1.1 seconds the first time and around 173 ms the second two times (count(ticker) returned 31,268,285). [select sum(date), sum(time), count(ticker) from trades where date = 20120501 and time > 34200000;] This query took about 250 ms the first, second and third times I ran it. count(ticker) returned 31,176,190. (I doing the same thing as previous query, but asking to ignore all trades before the market opened...obviously very very few trades occur before the market opens). [select sum(date), sum(time), count(ticker) from trades where date = 20120501 and time > 34200000 and time < 37800000;] This query took 1 minute and 15 seconds! The second time I ran it, it took 1 minute and 11 seconds. Notice that count(ticker) in this query only returned 5,969,337. This query is essentially the same as the previous one, but now I am only looking to process trades between 9:30 am and 10:30 am. So this query processes 1 hours' worth of trades while previous queries process the whole day. Notice that all three queries process the same columns. Between the second and third columns, all the columns used in the select clause and where clause are exactly the same. The second query just add an additional filter on the time column. Why is the third query two orders of magnitude slower than the second query? This experiment was done on an ubuntu server: >uname -a Linux abcdefg 3.2.0-25-generic #40-Ubuntu SMP Wed May 23 20:30:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux >cat /proc/meminfo |fgrep Mem MemTotal: 8168280 kB MemFree: 3588848 kB >hdparm -t ...disk... Timing buffered disk reads: 510 MB in 3.00 seconds = 169.80 MB/sec Please let me know if you require more information. Thanks, Shahbaz

4 3

[MonetDB-users] MonetDB Python client
by Alexey Mints 05 Jul '12

05 Jul '12

Hello! I had a problem with Python client hanging up if MonetDB connection was closed unexpectedly. This happened for example, when I have passed a request that caused "ERROR = !Connection terminated" in mclient. Such things should not occur in a ideal life, but they do =( The problem was that socket.recv cannot handle this situation properly. The solution is to use select.select statement. I attach the diff to mapi2.py file that solves the problem. Regards, Alexey

2 1

[MonetDB-users] importing data from csv
by Flavio Coelho 30 Jun '12

30 Jun '12

I am trying to import data from a CSV file separated by ';' and with string values surrounded by double quotes: " but I keep getting the following error messages: missing separator ';' line 225387 expecting 8 got 7 fields missing separator ';' line 75129 expecting 8 got 7 fields missing separator ';' line 0 expecting 8 got 7 fields missing separator ';' line 450774 expecting 8 got 7 fields missing separator ';' line 300516 expecting 8 got 7 fields missing separator ';' line 150258 expecting 8 got 7 fields missing separator ';' line 525903 expecting 8 got 7 fields missing separator ';' line 375645 expecting 8 got 7 fields failed to import table I am using the following command: copy 300000000 offset 2 records into mobilidade.ligacoes from '/Users/fccoelho/Documents/dados_mobilidade/bilhetagem.txt' using delimiters ';','\n','"' ; after creating the table like this: sql dump of my table: CREATE TABLE "mobilidade"."ligacoes" ( "id" INTEGER NOT NULL DEFAULT next value for "mobilidade"."seq_5840", "DT_INI_ATIVIDADE_REDE" VARCHAR(10), "HR_INI_ATIVIDADE_REDE" VARCHAR(7), "NU_SETOR_CELULA_ORIG" INTEGER, "NU_AREA_CELULA_ORIG" INTEGER, "NU_DDD_ORIG" INTEGER, "NU_DDD_DESTINO" INTEGER, "CD_TELEFONE_ORIG_ALTER" INTEGER DEFAULT NULL, "CD_TELEFONE_DESTINO_ALTER" VARCHAR(16) DEFAULT NULL, CONSTRAINT "ligacoes_id_pkey" PRIMARY KEY ("id") ); Naturally, I checked line 0 and it does have 8 fields. What am I doing wrong? -- Flávio Codeço Coelho

2 2

[MonetDB-users] COPY INTO
by DADOU 29 Jun '12

29 Jun '12

COPY INTO test from '/tmp/bla'; COPY INTO: insufficient privileges: COPY INTO from file(s) requires administrator rights, use 'COPY INTO "test" FROM STDIN' instead can you help me -- View this message in context: http://old.nabble.com/COPY-INTO-tp34088907p34088907.html Sent from the monetdb-users mailing list archive at Nabble.com.

3 2

[MonetDB-users] COPY INTO
by DADOU 29 Jun '12

29 Jun '12

I have a Problem with copy into copy into "LINEORDER" from ('E:\TEST.tbl'); COPY INTO: insufficient privileges: binary COPY INTO requires administrator rights TEST.tbl is a file with 6 000 000 rows. these a format for two rows in file TEST.tbl 1|1|7381|155190|4137|19960102|TRUCK| 1|2|7381|67310|815|19960102|MAIL| can help me please -- View this message in context: http://old.nabble.com/COPY-INTO-tp34088847p34088847.html Sent from the monetdb-users mailing list archive at Nabble.com.

2 1

[MonetDB-users] Basic sum aggregation returning incorrect value
by Tapomay Dey 28 Jun '12

28 Jun '12

I performed the following operations sequentially. Please look at the result when I use SUM. Sum values are incorrect. They should be 60/600/6000/60000.AVG returns correct values though. What could be going wrong? Is it something I can fix? sql> sql>create table table1 (id int, value int); operation successful (64.427ms) sql>create table table2 (id int, value int); operation successful (78.679ms) sql>insert into table1 values(1, 10); 1 affected row (25.389ms) sql>insert into table1 values(1, 20); 1 affected row (28.254ms) sql>insert into table1 values(1, 30); 1 affected row (27.512ms) sql>insert into table1 values(2, 300); 1 affected row (28.255ms) sql>insert into table1 values(2, 200); 1 affected row (28.658ms) sql>insert into table1 values(2, 100); 1 affected row (29.606ms) sql>insert into table2 values(1, 1000); 1 affected row (25.144ms) sql>insert into table2 values(1, 2000); 1 affected row (26.130ms) sql>insert into table2 values(1, 3000); 1 affected row (27.490ms) sql>insert into table2 values(2, 30000); 1 affected row (18.623ms) sql>insert into table2 values(2, 20000); 1 affected row (40.441ms) sql>insert into table2 values(2, 20000); 1 affected row (29.716ms) sql>insert into table2 values(2, 10000); 1 affected row (25.907ms) sql>select t1.id, sum(t1.value) as v1, sum(t2.value) as v2 from table1 t1, table2 t2 where t1.id=t2.id group by t1.id; +------+------+--------+ | id | v1 | v2 | +======+======+========+ | 1 | 180 | 18000 | | 2 | 2400 | 240000 | +------+------+--------+ 2 tuples (1.769ms) sql>select t1.id, avg(t1.value) as v1, avg(t2.value) as v2 from table1 t1, table2 t2 where t1.id=t2.id group by t1.id; +------+--------------------------+--------------------------+ | id | v1 | v2 | +======+==========================+==========================+ | 1 | 20 | 2000 | | 2 | 200 | 20000 | +------+--------------------------+--------------------------+ 2 tuples (2.275ms) sql> Regards, Tapomay.

2 1

[MonetDB-users] last inserted id
by Tomas Mikula 26 Jun '12

26 Jun '12

Hi, how can I get the ID (value of an AUTO_INCREMENT column) of the last inserted row, from within an SQL script? I am able to get it through the Python API, so I suppose there is a way to get it inside an SQL script, too. Thanks, Tomas

2 1

[MonetDB-users] strange decrease in performance after some deletes
by Majid Azimi 25 Jun '12

25 Jun '12

Hi guys, I have loaded 80 million records in database. a very complex aggregate query(multiple COUNT, SUM, AVG, GROUP BY combined) runs deadly fast in about 30 seconds. But after deleting 700 records performance has been decreased alot. the same query runs in 8 minutes now. Is this usual? Thank you

1 0

[MonetDB-users] Changing SysV parameteres
by Majid Azimi 19 Jun '12

19 Jun '12

Hi guys, Does changing SysV parameters such as SHMMAX, SHMMIN, SHMSEG , ... affects MonetDB performance? How they affect? I mean the vanilla installation of MonetDB on a very powerful hardware needs massive optimization like what we see on other relational DBMS products?

1 0

[MonetDB-users] Announcement: New Apr2012-SP2 Bugfix release of MonetDB suite
by Sjoerd Mullender 19 Jun '12

19 Jun '12

The MonetDB team at CWI/MonetDB BV is pleased to announce the Apr2012-SP2 bugfix release of the MonetDB suite of programs. More information about MonetDB can be found on our website at <http://www.monetdb.org/>. For details on this release, please see the release notes at <http://www.monetdb.org/Downloads/ReleaseNotes>. As usual, the download location is <http://dev.monetdb.org/downloads/>. Apr 2012-SP2 bugfix release Client Package * Resolved a cosmetical error where tab-characters would cause misalignments in tabular result views. For the time being, tabs are now represented as a single space in tabular view. MonetDB Common * Limit number of detected CPU cores to 16 on 32-bits systems to avoid running quickly out of addressable resources followed by a kill from the OS. Bug Fixes * 2594: NULL cannot automatically be casted to every other type * 3085: assertion fails upon execution of a valid SQL query * 3086: Modulo function does not work in select from table * 3087: query causes "Not yet implemented" message * 3089: mserver5 crashed if join condition has two column and incorrect order * 3090: crashed if using single identifier for where condition * 3096: Type of median error

1 0

Re: [MonetDB-users] python-monetdb and pip
by Alexey Mints 18 Jun '12

18 Jun '12

Hallo! As far as Python question has been raised. There is a tiny thing that is (probably) missing in the client. Connection class (and other classes as well) are not inherited from the "object" class, therefore further inheritance and method overriding is problematic. I think, this might be corrected in future. Regards, Alexey Mints

3 2

[MonetDB-users] Locality Sensitive Hashing method for Image Retrieval
by BOOM Bas 18 Jun '12

18 Jun '12

Hi, Sorry, I am new to this mailinglist and not sure this question fits, but have I question how to optimize my queries I am experimenting with monetdb for image retrieval, having an image database of 300000 image. At the moment, I am using the Locality Sensitive Hashing method and because I understood from the monetdb documenation that monetdb supports indexing/hash tables, which makes the implementation quiet easy in monetdb. I have for each image 30 buckets with 24 bit strings (int) (should be indexed, assume automatically done by monetdb) I have for each image a feature vector of 1000 real values. I have for each image a unique id together with some info like file name. At the moment, my table is as follows image_id, filename, bucket_1, bucket_2, bucket_3 ... bucket_30, feature_value_1, feature_value_2, ..., feature_value_1000 For Locality Sensitive Hashing, I am performing the following sql query: select * from table where bucket_1 = bitstring or bucket_2 = bitstring or bucket_3 = bitstring or ... bucket_30 = bitstring (limit 1000) These bitstrings are quiet unique, giving me around the 500 images from the entire database. I would also like to obtain the feature vector (so all feature values). At the moment, query and data retrieval times depends but often take around 0.5-1 minute, what are ways to improve this. Does using 2 tables help or storing the feature vector in one column? Ideas are welcome. I am using the MAPI client to retrieve the data. Happy to provide more information if necessary Cheers, Bas Boom University of Edinburgh part of Fish4Knowledge consortium -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.

1 0

[MonetDB-users] charset problem with the odbc driver for windows
by liangmeng 18 Jun '12

18 Jun '12

hello, all, i installed monetdb in windows server 2008(64bit) , and installed the odbc for windows( 32bit intalled firstly, and 64bit the next), after insert some Chinese characters, i use oracle biee to show the table data, but biee can't show all the characters, just like below: 1��monetdb data showed in biee i also install mysql to test this, the database character set is utf8 too, and biee can show the data correctly: 2��mysql data showed in biee the data showed in command line tool are the same from monetdb and mysql monetdb command line tool return: sql>select * from test2; +------+ | nam | +======+ | 广州 | | 梅州 | +------+ 2 tuples (2.189ms) mysql commad line tool return: mysql> select * from test; +--------+ | nam | +--------+ | 广州 | | 梅州 | +--------+ 2 rows in set (0.00 sec) Does this mean that: the odbc driver of monetdb has some problems?

2 1

[MonetDB-users] monetdb--query is very slow on table about 1 billion rows
by liangmeng 16 Jun '12

16 Jun '12

hi, guys, i create a simple table , and the table is up to 1 billion rows, its structure as follow: create table test(Month_ID int not null, C_NAME varchar(10) not null, C_ID int not null, MSISDN varchar(15) not null, C_FLUX double not null); and the data looks like: “201201，name1, 123213, 13723213213, 12.12321" when i execute the query "select c_name,c_flux from test where c_id=**** order by c_flux desc", it takes more than 3 minute to get the result(more than 100 thousands rows returned, if limit 100 is used, the execute time is about 40s), is there any ways to optimize? Hardwares: intel xeon 2.12*8, 32G memory, 4*1T SATA(raid 0)

2 3

[MonetDB-users] How to see what query is running? kill long running queries?
by Majid Azimi 15 Jun '12

15 Jun '12

Hi guys, Is it possible to see what queries are running on the database? How to kill a query? I have a issued a SELECT * query and then looked at sys.querylog and sys.queryhistory, But they are empty. Is there any solution?

4 7

[MonetDB-users] RDF3x to MonetDB
by Hancel Gonzalez 15 Jun '12

15 Jun '12

Hi people, i have installed rdf-3x <http://www.mpi-inf.mpg.de/~neumann/rdf3x/>. This software have *buildmonetdb *that is for translate rdf queries to monetdb. The problem is that i dont know which arguments i have send in command line. I appreciate your help! Greettings, Hancel Gonzalez.

3 2

[MonetDB-users] monetdb do not release the memory
by liangmeng 15 Jun '12

15 Jun '12

hi, everyone i'am new here, i install monetdb of windows 64bit version, after copy into table from several very large files(about 10G each), i found that monetdb occupied too much momery, almost 100% of total 32G , and it keeps occupying, after 24hours, it still don't release the memory, what's the matter? Also, i found the same problem after query several times with large amount of records returned;

4 6

[MonetDB-users] how to find the foreign key relationships
by Molenaar, Gijs 14 Jun '12

14 Jun '12

Hi monetdb people, How do I find all foreign key relationships with MonetDB using SQL? I now have: "select idxs.name, tables.name from sys.tables, sys.idxs where tables.id = idxs.table_id and idxs.type=1;" But that doesn't give me the related table. Any suggestion? I can't find documentation of the sys tables on the website, does it exist? Thanks, -- Gijs Molenaar http://www.astro.uva.nl/people/gijs-molenaar/

3 7

[MonetDB-users] python-monetdb and pip
by Molenaar, Gijs 14 Jun '12

14 Jun '12

Hi Monetdb people, python-monetdb is now also in the pypi repo, which means you can easily install it with pip: $ pip install python-monetdb more info: http://pypi.python.org/pypi/python-monetdb/11.9.5 -- Gijs Molenaar http://www.astro.uva.nl/people/gijs-molenaar/

1 0

[MonetDB-users] python-monetdb and pip
by Molenaar, Gijs 13 Jun '12

13 Jun '12

Hi Monetdb people, python-monetdb is now also in the pypi repo, which means you can easily install it with pip: $ pip install python-monetdb -- Gijs Molenaar http://www.astro.uva.nl/people/gijs-molenaar/

1 1

Re: [MonetDB-users] hold cursors over commit in JDBC
by Majid Azimi 12 Jun '12

12 Jun '12

Let me ask it this way: How can we configure driver so it doesn't fetch all records at one time. for example 100 records per each fetch, So the application server doesn't get OutOfMemoryException. Thank you. >> hi guys, >> >> I have a very large table, which I should scan it and generate reports. My code is like this: >> >> Class.forName("nl.cwi.monetdb.jdbc.MonetDriver"); >> Connection conn = DriverManager.getConnection("jdbc:monetdb://localhost/online", "monetdb", "monetdb"); >> >> conn.setAutoCommit(false); >> conn.setHoldability(ResultSet.HOLD_CURSORS_OVER_COMMIT); >> >> Statement stmt = conn.createStatement(ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_READ_ONLY); >> stmt.setFetchSize(10); >> >> ResultSet rs = stmt.executeQuery("SELECT * FROM denorm"); >> >> while (rs.next()) { >> /* process line */ >> } >> >> conn.commit(); >> >> I do not use much ram inside while loop. I get OutOfMemeryException from JVM. >> So I think the driver ignores HOLD_CURSORS_OVER_COMMIT and fetches all records. Is there any solution? > HOLD_CURSORS_OVER_COMMIT means it keeps the cursor open, right? So what > else can the driver do but keep them open (including the memory > associated to that)? What would you have expected to happen with this > setting?

2 1

[MonetDB-users] hold cursors over commit in JDBC
by Majid Azimi 12 Jun '12

12 Jun '12

hi guys, I have a very large table, which I should scan it and generate reports. My code is like this: Class.forName("nl.cwi.monetdb.jdbc.MonetDriver"); Connection conn = DriverManager.getConnection("jdbc:monetdb://localhost/online", "monetdb", "monetdb"); conn.setAutoCommit(false); conn.setHoldability(ResultSet.HOLD_CURSORS_OVER_COMMIT); Statement stmt = conn.createStatement(ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_READ_ONLY); stmt.setFetchSize(10); ResultSet rs = stmt.executeQuery("SELECT * FROM denorm"); while (rs.next()) { /* process line */ } conn.commit(); I do not use much ram inside while loop. I get OutOfMemeryException from JVM. So I think the driver ignores HOLD_CURSORS_OVER_COMMIT and fetches all records. Is there any solution?

2 1

[MonetDB-users] Setting up replication
by Majid Azimi 12 Jun '12

12 Jun '12

Hi guys, I', trying to configure replication on single node(different ports). What I did is: 1. I have created 2 dbfarms 2. set port=50000 for master node and set port=50001 for slave node 3. set control=yes for both 4. set passphrase=master for master node and set passphrase=slave for second node My master node has already data in it, I just changed the configuration. then: moentdb -p 50000 set master=yes maindb --> for master node monetdb -p 50001 set slave=mapi:monetdb://127.0.0.1:50000/maindb slavedb --> on slave node(slavedb is empty database) Now there is no data in slave node. Can anyone help?

2 1

[MonetDB-users] Server socket stays 'open' after crash
by Stefan de Konink 11 Jun '12

11 Jun '12

Instead of using monetdbd I am using a very simple while [ 1 ]; do monetdb; sleep 2; done command to restart the database after an assertion failed or segmentation fault. For some reason even after a crash MonetDB complains at the start of the application that the port is already in use. Would could -unix wise- be the reason for this, that even after a crash and the program has been terminated resources are still claimed for the terminated program? Stefan

2 3

[MonetDB-users] MonetDB Clustering
by Majid Azimi 11 Jun '12

11 Jun '12

Hi guys, What types of clustering does monetdb support? Sharding? Master/Slave? if it is Master/Slave does it support multi master? or all writes must go to master node? In clustering documentation (http://www.monetdb.org/Documentation/Cookbooks/Recipes/Cluster) there is paragraph: willem% monetdb -h cruquius -P mypassphraseset shared=pump/2/harvey pump willem% monetdb -h lijnden -P mypassphraseset shared=pump/2/fox pump willem% monetdb -h leeghwater -P mypassphraseset shared=pump/1/harvey pump What are those 1, 2, fox, harvey?

2 1

[MonetDB-users] monetdb clustering
by Majid Azimi 10 Jun '12

10 Jun '12

Hi guys, What types of clustering does monetdb support? Sharding? Master/Slave? if it is Master/Slave does it support multi master? or all writes must go to master node? In clustering documentation (http://www.monetdb.org/Documentation/Cookbooks/Recipes/Cluster) there is paragraph: willem% monetdb -h cruquius -P mypassphraseset shared=pump/2/harvey pump willem% monetdb -h lijnden -P mypassphraseset shared=pump/2/fox pump willem% monetdb -h leeghwater -P mypassphraseset shared=pump/1/harvey pump What are those 1, 2, fox, harvey?

1 0

[MonetDB-users] Install MonetDB in CentOS 5
by Hancel Gonzalez 08 Jun '12

08 Jun '12

Hi people, i'm new here and i hope your help. I wanna install MonetDB in a computer with CentOS 5: download rpm packages from http://code.google.com/p/monetdb-rhel-5/downloads/list but i not work. Then, i tried compile the sourcecode http://dev.monetdb.org/downloads/sources/Latest/MonetDB-11.9.5.zip, command ./configure work but when i 'make' i have error of compilation. I dont know what to do! Please help me! Greetings, Hancel Gonzalez.

2 1

[MonetDB-users] Djonet
by Gijs Molenaar 08 Jun '12

08 Jun '12

Hi, I've updated the MonetDB Django backend created by Mark Bucciarelli and renamed it to Djonet. https://github.com/gijzelaerr/djonet basic stuff is working, but many Django tests are still failing, which i'm working on. Still it is already quite usable. If people want to help make it better, let me know. -- Gijs Molenaar http://www.astro.uva.nl/people/gijs-molenaar/

5 5

[MonetDB-users] Any plan to support Ubuntu Server 12.04
by Majid Azimi 28 May '12

28 May '12

hi guys, Is there any plan to build binaries for Ubuntu server 12.04(Precise Pangolin)? I didn't find debs for this release from repository?

2 1

[MonetDB-users] Changing time zone after getting GMT time from database
by Majid Azimi 27 May '12

27 May '12

Hi guys, I have MonetDB database with table containing user table: CREATE TABLE user ( birth_date TIMESTAMP NOT NULL ); birth_date is saved in GMT without DST. (This is the default behavior of MonetDB). So I should change the TimeZone in my application. Here is my code: Class.forName("nl.cwi.monetdb.jdbc.MonetDriver"); Connectioncon =DriverManager.getConnection("jdbc:monetdb://localhost/online","monetdb","monetdb"); Statementst =con.createStatement(); ResultSetrs; Calendar c = Calendar.getInstance(TimeZone.getTimeZone("UTC")); rs =st.executeQuery("SELECT * FROM user"); while(rs.next()){ c.setTime(rs.getTimestamp("birth_date")); c.setTimeZone(TimeZone.getTimeZone("Asia/Tehran")); System.out.println(c.get(Calendar.YEAR)+"-"+c.get(Calendar.MONTH)+"-"+c.get(Calendar.DAY_OF_MONTH)+" "+c.get(Calendar.HOUR_OF_DAY)+":"+c.get(Calendar.MINUTE)+":"+c.get(Calendar.SECOND)); } But there is no difference between timestamps in database and timestamps after converting time zone in application. Could anyone help? Is this the wrong way to convert TimeZone? I'm using MonetDB version 11.9.5-20120516 on Debian 6 with openjdk 6. Here is the monetdbd getall /home/dbfarm: dbfarm /home/dbfarm/ status monetdbd[4187]1.6(Apr2012-SP1)is serving thisdbfarm mserver /usr/bin/mserver5 logfile /home/dbfarm//merovingian.log pidfile /home/dbfarm//merovingian.pid sockdir /tmp port 50000 exittimeout 60 forward proxy discovery yes discoveryttl 600 control yes passphrase {SHA512}ba3253876aed6bc22d4a6ff53d8406c6ad864195ed144ab5c87621b6c233b548baeae6956df346ec8c17f5ea10f35ee3cbc514797ed7ddd3145464e2a0bab413 mapisock /tmp/.s.monetdb.50000 controlsock /tmp/.s.merovingian.50000

2 1

[MonetDB-users] Tuning MonetDB
by Majid Azimi 27 May '12

27 May '12

Hi guys, As MonetDB does rely on OS features to be tuned, Which settings should we optimize on OS specially on Linux? 1. Tuning network a. using jumbo b. socket buffer space c. TCP setting 2. Tuning VM a. huge page b. swappiness 3. Tuning File system a. which file system? ext3? ext4? XFS? b. using large blocks if database is almost read only does using ext2 make any benefit?

2 1

[MonetDB-users] Announcement: New Apr2012-SP1 Bugfix release of MonetDB suite
by Fabian Groffen 25 May '12

25 May '12

The MonetDB team at CWI/MonetDB BV is pleased to announce the Apr2012-SP1 bugfix release of the MonetDB suite of programs. More information about MonetDB can be found on our website at http://www.monetdb.org/. For details on this release, please see the release notes at <http://www.monetdb.org/Downloads/ReleaseNotes>. As usual, the download location is <http://dev.monetdb.org/downloads/>. Apr 2012-SP1 bugfix release Build Environment * Windows: we now use OpenSSL 1.0.1b. SQL * Databases that were upgraded from the Aug2011 release have an error in the catalog for SQL procedures. This is now fixed. Merovingian * Fixed a bug where connecting to a stopped multiplex-funnel would result in a 'there are no available connections' error. MonetDB Common * Implemented MT_getrss for Mac OS X systems, this allows the server to know about how much memory is currently in use. Bug Fixes * 2454: SQL: add various statistical functions * 2916: non admin user cannot create temporary tables * 2949: SQL exception during execution of a correct user defined function that just returns a relation table constructed by a simple SQL select query * 2958: Grant does't work with schema syntax * 2960: mclient terminates connection during insertion of a large number of records from a file * 2972: SQL URL functionality contains errors * 2987: Broken type inference when using sql round * 2992: SQL module truncates DECIMALS when passing integers to MAL module * 3000: Inconsistency between read-only and read-write modes after dropping a schema * 3028: Segmentation fault in seqscan_eq_bte_bte_tloc_void_void * 3046: mserver5 terminates with segmentation fault * 3063: datacell functions no longer work after restart of database * 3072: Database upgrade from Dec2011 to Apr2012 broken for storage() * 3073: VERY slow foreign key check (due to missing batcalc.isnil() ?) * 3074: Name resolution in procedures * 3077: No errors on UDF returning table with too many columns * 3079: Converting an Oracle schema DDL for MonetDB fails to create a column named "no".

1 0

Re: [MonetDB-users] Using monetdb and sqlalchemy
by Sabst 23 May '12

23 May '12

Still stuck. If you know the answer please share it. Also if you think the two are not meant to work together, share it too. Anyone? > ----- Message transféré de sabst(a)free.fr ----- > Date : Thu, 10 May 2012 15:07:17 +0200 > De : sabst(a)free.fr > Adresse de retour :sabst@free.fr > Sujet : Using monetdb and sqlalchemy > À : monetdb-users(a)lists.sourceforge.net > > Hi, > I am just starting using monetdb and, even if I could find discussions about > Python/SqlAlchemy integration, I could not make it work. > > I installed python-monetdb module and have a running monetdb server. > > Now I expect my client application to work with monetdb as it does with > postgresql and instead of passing a connection string like: > postgres://user:password@somehost:port/db > I use: > monetdb://user:password@somehost/db > > But I get this error: > ArgumentError: Could not determine dialect for 'monetdb'. > > What are the steps required to integrate monetdb into SqlAlchemy? > > Certainly missing the obvious but I'm currently stuck. > > Thank you in advance for any help, > Stephane. > > ----- Fin du message transféré ----- > > > >

2 4

[MonetDB-users] Monet on SUSE
by Hualin Wang 20 May '12

20 May '12

Dear All, I have trouble compliing the Monet on my SUSE 11 box. The server has an old PCRE installed, like 7.8. I download my own version of pcre 8.3, and complie it with utf-8 enabled. I set up the following three environment vars: pcre_LIBS, pcre_CFLAGS, PKG_CONFIG_PATH to point to the right place. But the Monet ./configure still complain utf-8 support no. By the way, the pcre check is yes. Which version of PCRE package I need install on SUSE? By the way, what this sentence means from monetdb.org "Make sure you install the xxx-dev versions on binary distributions of the necessary packages as well!" Thanks for any help/hints! Best Regards, Hualin

2 1

[MonetDB-users] Bad SELECT performance after deletion of 1 record
by suncpp 17 May '12

17 May '12

Hi everyone, I had added about 30,000,000 records in one MonetDB table. The performance of executing SELECT-queries was really great. But after the deletion of only 1 record from the table, the performance had slowed down considerably. I have seen the topics here with alike problem but I have not found the solution. Could anyone help me to understand what the problem is? -- View this message in context: http://old.nabble.com/Bad-SELECT-performance-after-deletion-of-1-record-tp3… Sent from the monetdb-users mailing list archive at Nabble.com.

2 2

[MonetDB-users] strange trigger behaviour
by Majid Azimi 16 May '12

16 May '12

Hi guys, I have created a table named users: CREATE TABLE names ( name VARCHAR(255) NOT NULL ); another table named names2 which is same as users. only table names are different. I have created a after insert trigger like this: CREATE TRIGGER trg_names_ai AFTER INSERT ON names REFERENCING NEW ROW AS new_row FOR EACH ROW WHEN new_row.name = '<some name>' INSERT INTO names2 VALUES(new_row.name); The problem is it doesn't care about WHEN clause. Any INSERT query will appear in names2. Can anyone help?

2 1

[MonetDB-users] timeout while waiting for database 'xxx' to initialise the sql scenario
by Brian J. Cardiff 11 May '12

11 May '12

Hi all, I'm trying monetdb among with other vertical databases. After some experiments I am unable to start the database again. I'm not sure what the things I did cause the issue, but happens twice already. I have restart monetdbd and server without luck. Is there any way to solve this issue? $ monetdb start xxx starting database 'xxx'... FAILED start: starting 'xxx' failed: timeout while waiting for database 'xxx' to initialise the sql scenario The experiments consist on: 1. Bulk load .csv file with ~ 20*10^6 records 2. Do some aggregate functions with "SELECT AVG(..) FROM TBL WHERE ID IN (...)" with different amount of ids in list (10 - 5000) (yeap, ugly). 3. Add columns to TBL, Massive update columns in TBL, Drop columns in TBL. [version] MonetDB Database Server Toolkit v1.0 (Apr2012) MonetDB Database Server v1.6 (Apr2012) [morovingian.log] 2012-05-11 15:05:55 MSG xxx[637]: # Listening for UNIX domain connection requests on mapi:monetdb:///Users/bcardiff/Work/Xxx/db/xxx/.mapi.sock 2012-05-11 15:05:55 MSG xxx[637]: # MonetDB/GIS module loaded 2012-05-11 15:05:55 MSG xxx[637]: # MonetDB/SQL module loaded 2012-05-11 15:06:05 MSG merovingian[588]: sending process 637 (database 'xxx') the TERM signal 2012-05-11 15:06:05 MSG merovingian[588]: database 'xxx' has shut down 2012-05-11 15:06:05 MSG merovingian[588]: database 'xxx' (637) has exited with exit status 0 2012-05-11 15:06:05 ERR control[588]: (local): failed to fork mserver: timeout while waiting for database 'xxx' to initialise the sql scenario -- Brian J. Cardiff - Manas Technology Solutions [ar.phone] 4796.0232 #BCR(227) [us.phone] 312.612.1050 #BCR(227) [email] bcardiff(a)manas.com.ar [web] www.manas.com.ar [weblog] http://weblogs.manas.com.ar/bcardiff/

1 0

[MonetDB-users] Using monetdb and sqlalchemy
by sabst＠free.fr 10 May '12

10 May '12

Hi, I am just starting using monetdb and, even if I could find discussions about Python/SqlAlchemy integration, I could not make it work. I installed python-monetdb module and have a running monetdb server. Now I expect my client application to work with monetdb as it does with postgresql and instead of passing a connection string like: postgres://user:password@somehost:port/db I use: monetdb://user:password@somehost/db But I get this error: ArgumentError: Could not determine dialect for 'monetdb'. What are the steps required to integrate monetdb into SqlAlchemy? Certainly missing the obvious but I'm currently stuck. Thank you in advance for any help, Stephane.

1 0

Re: [MonetDB-users] Strange things...
by Alexey Mints 07 May '12

07 May '12

Dear All! My old problem http://sourceforge.net/mailarchive/message.php?msg_id=29168305 strikes back on the new version. The situation is just the same - combination of two conditions gives empty result (that is wrong), while each condition alone gives correct resultset. The problem shows up only in the SECOND run of quite a huge set of queries (the first one runs Ok). Even more, there has to be some delay (~10 sec) before the second run, otherwise everything works. Deleting all records does not help, problem disappears only if I recreate the table. What on Earth can this be? It seems rather hard to pin down the problem with SQL-methods only. Just in case - I attach traces of correct and incorrect queries. Regards, Alexey Mints

1 0

[MonetDB-users] problem after upgrading (probably)
by Gijs Molenaar 04 May '12

04 May '12

Hi MonetDB people, greetings from the other side of the street. Long time no see. I just upgraded my monetdb installation to the April release. I use the Ubuntu repo. my database is running, but when I try to connect with the Python API or mclient I get the error: CREATE AGGREGATE: name 'median' (tinyint(8)) already in use Any suggestion how to figure out how to solve this problem? greetings, -- Gijs Molenaar http://www.astro.uva.nl/people/gijs-molenaar/

5 15

[MonetDB-users] bug tracker problems?
by Gijs Molenaar 04 May '12

04 May '12

Me again, I have some issues with the ubuntu packages that I would like to report, but I can't get access to the bug tracker. First of all, the machines seems to respond not really fast. But when I open a new account after the token verification the webserver gives an empty response (according to my browser). I tried this a couple of times now. Is it me? -- Gijs Molenaar http://www.astro.uva.nl/people/gijs-molenaar/

2 2

[MonetDB-users] MonetDB clustering
by Maik Strewe 03 May '12

03 May '12

Hi and good morning from Germany. My name is Maik Strewe and I want to test the performance of the monetDB in a cluster. My application needs millions of rows but few columns. I have to set up an monetDB cluster on 2 servers at an external server hoster. The single instances on the hosts are installed and running. Then I tried to use the "monetdb discover" command but the servers cant see each other. As far as I know the discovery is based on a UDP broadcast, right? Is it possible to configure the cluster members in a configuration file so that the monetdb instance can discover the cluster member by configuration?

4 5

[MonetDB-users] MonetDB clustering
by Maik Strewe 03 May '12

03 May '12

Hi and good morning from Germany. My name is Maik Strewe and I want to test the performance of the monetDB in a cluster. My application needs millions of rows but few columns. I have to set up an monetDB cluster on 2 servers at an external server hoster. The single instances on the hosts are installed and running. Then I tried to use the "monetdb discover" command but the servers cant see each other. As far as I know the discovery is based on a UDP broadcast, right? Is it possible to configure the cluster members in a configuration file so that the monetdb instance can discover the cluster member by configuration?

1 0

Re: [MonetDB-users] Strange things...
by Alexey Mints 02 May '12

02 May '12

Problem solved itself (for now) with the upgrade to the latest version.

1 0

[MonetDB-users] Selecting cracker update algorithms
by Stef Sijben 02 May '12

02 May '12

Hello, We are a group of students trying to repeat the experiments described in the paper Updating a Cracked Database [1]. We know how to use the cracking optimizer, but what we can't figure out is how to select one of the described algorithms to be used for updates. We found implementations of all the algorithms in the source code and I have been looking in documentation and the source code for a considerable time without any luck. Can someone please point us in the right direction? Thanks, Stef Sijben References [1] S. Idreos, M.L. Kersten, and S. Manegold. Updating a cracked database. In Proceedings of the 2007 ACM SIGMOD international conference on Management of data, pages 413–424. ACM, 2007.

1 0

[MonetDB-users] Announcement: New Apr2012 Feature release of MonetDB suite
by Sjoerd Mullender 27 Apr '12

27 Apr '12

The MonetDB team at CWI/MonetDB BV is pleased to announce the Apr2012 feature release of the MonetDB suite of programs. More information about MonetDB can be found on our website at http://www.monetdb.org/. For details on this release, please see the release notes at <http://www.monetdb.org/Downloads/ReleaseNotes>. As usual, the download location is <http://dev.monetdb.org/downloads/>. Apr 2012 feature release Build Environment * Fixed some of the package names for Debian/Ubuntu. Packages for libraries should contain the major number of the library version number. This was not always the case. * On Debian and Ubuntu, install Python modules in dist-packages instead of site-packages. This fixed bug 2997. SQL * Fixed a crash that happened at the end of a database upgrade to the Dec2011 database scheme. The crash happened during cleanup after the database was upgraded, so it was merely inconvenient. * Stripped off implementation-specific parts from error messages before they get presented to the user. Java Module * Password reading by JdbcClient no longer results in strange artifacts * JdbcClient now returns exit code 1 in case of failures * Implemented missing Number types support in PreparedStatement.setObject() * Fixed bug in DatabaseMetaData.getSchemas() method that caused an SQL error when called with catalog and schema argument. * Resolved a bug where JDBC and Control connections could terminate abruptly with 'Connection closed' messages Client Package * ODBC: Implemented the SQL_ATTR_CONNECTION_TIMEOUT attribute. * mclient now has a -a (--autocommit) option to turn off autocommit mode. MonetDB5 Server * The type "chr" has been removed. chr has long been superseded by bte for 1 byte arithmetic plus it is pretty useless to hold single characters since we use Unicode and thus only a tiny subset of the supported character set would fit. * Fixed potential crash by dealing better with non-standard types. * A couple of memory leaks have been plugged. Merovingian * The logfile and pidfile monetdbd properties are now displayed with dbfarm path when relative * Fixed a bug in the multiplex-funnel where certain clients would abort on responses for update queries. * Fixed problem where version and mserver properties for monetdbd were not always successfully retrieved. Bug #2982. * Fixed problem where shutdown of monetdbd would lead to shutting down database 'control' which does not exist. Bug #2983. * Fixed issue causing (harmless) 'error reading from control channel' messages. Bug #2984. * Resolved problem where remote start/stop/etc. commands with monetdb would report error 'OK'. Bug #2984. MonetDB Common * The type "chr" has been removed. chr has long been superseded by bte for 1 byte arithmetic plus it is pretty useless to hold single characters since we use Unicode and thus only a tiny subset of the supported character set would fit. Bug Fixes

1 0

Re: [MonetDB-users] Strange things...
by Alexey Mints 26 Apr '12

26 Apr '12

Hi Stefan! condition1 is like this: exists (select 1 from temp_assoc_counts tc where tc.xtrsrc_id = temp_associations.xtrsrc_id and tc.assoc_count = 1) condition 2 is like: kind is null I have also bumped in the same situation, when condition2 was like "kind = 2". But when "2" was replaced to a column name (with all values in this column were 2) - it worked fine. I.e. there is something wrong when constant appears in the condition. Traces can be seen in attachment.

1 0

[MonetDB-users] Strange things...
by Alexey Mints 23 Apr '12

23 Apr '12

Hello! I have a strange behavior of my MonetDB database. After some actions I run into situation, when queries select * from table1 where {condition1}; and select * from table1 where {condition2}; return the same results (same rows), but select * from table1 where {condition1} and {condition2}; is empty, which is definitely wrong. I cannot see any problems from SQL-side. I am still struggling to get a minimal code producing this bug. Even worse - it is not always occurring under the same conditions... How can I get more information on what's happened? Alexey

2 1

[MonetDB-users] Performance Degredation
by Joseph Brower 13 Apr '12

13 Apr '12

We discussed this a little bit before, but I was called away. Now that I have some time, I'm hoping to discuss this again and hopefully find resolution. Normally our MonetDB instance is running happily and doesn't have any problems. We've limited the number of queries being performed concurrently to the number of cores in the machine, and we do all of our inserts using COPY INTO statements. The problem is that, for no reason that we can see, suddenly MonetDB starts to perform incredibly slowly. This causes queries to stop returning, or, what used to return after less than a second starts to take over 30 seconds, and causes a timeout on our system that produces the graphs based on this information. We restart MonetDB and the problem goes away for a while. Sometimes it drops again after a short time (as little as a few hours) other times it will run fine for a few days. Does anyone have any ideas? What other information can I provide to get a closer look at why it is behaving this way? Thanks, Joseph Brower

1 0

[MonetDB-users] MonetDB driver for node.js?
by Robert Kosara 05 Apr '12

05 Apr '12

Hello, I am looking for a better database for a project where I am dealing with large numbers of data points, and MonetDB seems like a really interesting choice for that. This is for a web application that is written in JavaScript/node.js, though, so I'm wondering if anybody might be working on a MonetDB driver for node. I know that your focus is on scientific data, and JavaScript might not be a big factor there, but node is gaining a lot of momentum for web applications. Also, is there a way to search the mailing list archive? I can't seem to find a way to do that on the sourceforge website. Best, Robert

3 2

[MonetDB-users] Funnel
by Joseph Brower 02 Apr '12

02 Apr '12

We're looking at setting up the funnel. We've got 2 database servers that we're planning on using, and we simply want to balance the requests between the two. We don't want any of the multiplexing to take effect. I'm not seeing much as far as guides or how to set this up in the man pages. Does anyone have any good pointers on how to set things up this way? Thanks, Joseph Brower

3 7

[MonetDB-users] MonetDB - Mondrian connection
by Pedro Salgueiro 30 Mar '12

30 Mar '12

Hi guys! I have been trying MonetDB and it's awesome. I tried to connect MonetDB to Mondrian using olap4j. I managed to establish the connection using the MonetDB JDBC, but I have a problem: There are no errors, but it presents the wrong results. Every MDX query returns the right tables, but with all values "zeroed", something like this: ------------------------ Unit Sales ========== 0 ------------------------ I tried to make a simple JDBC connection, and it worked out ok. I am using the following connection string: String connectionProperties = "jdbc:mondrian:JdbcDrivers=nl.cwi.monetdb.jdbc.MonetDriver;" + "Jdbc=jdbc:monetdb://localhost/foodmart;" + "JdbcUser=monetdb;" + "JdbcPassword=monetdb;" + "Catalog=FoodMart.xml;"; Does anyone knows if I am doing anything wrong? Has anyone managed to make a working connection between Mondrian and Monet? If so, did you have to make something special? It would be great to have a working connection between Mondrian and MonetDB, since its much faster than MySQL or LucidDB, which I have already tried. Best regards, Pedro

2 5

[MonetDB-users] Fwd: Re: DB Corruption
by Joseph Brower 27 Mar '12

27 Mar '12

This is what one of my coworkers reports about the problem. both columns are varchar(24). We have confirmed that there are no null values. We have a theory… Approximately every 6 hours, monetdb stops responding to queries and starts thrashing the disk. This behavior has been confirmed without any inserts. Because of this behavior, we routinely stop and start the service. After a restart, the service returns to a normal state. This appears to be the core problem. Our guess is that we restarted the service in the middle of a massive import. We will make sure this doesn't happen again, however, we still cannot find any sort of resolution as to why monetdb routinely starts thrashing the disk (on the order of writing 150MB/s) without any inserts, only select queries. Sorry to change the topic, but we're moving on the assumption we corrupted our db by restarting the service in the middle of a massive "INSERT INTO FROM" query. Can you think of any reason why monetdb would need to write to the disk in such an aggressive manner while ONLY serving select queries? This appears to be the core problem. Thanks On Mar 26, 2012, at 9:23 AM, Joseph Brower wrote: > What would you like me to tell them? > > > -------- Original Message -------- > Subject: Re: [MonetDB-users] DB Corruption > Date: Sun, 25 Mar 2012 09:15:24 +0200 > From: Martin Kersten <Martin.Kersten(a)cwi.nl> > Reply-To: Martin.Kersten(a)cwi.nl, Communication channel for MonetDB > users <monetdb-users(a)lists.sourceforge.net> > To: Communication channel for MonetDB users > <monetdb-users(a)lists.sourceforge.net> > > > > What is the column type? > Is the situation repeatable using a fresh database? > > regards, Martin > > On 3/25/12 6:34 AM, Joseph Brower wrote: > > We just checked. There are no nulls in the database at all. > > Additionally, there is only one column that has a different count. > > > > Thanks, > > > > Joseph Brower > > > > On 03/24/2012 09:58 AM, Stefan Manegold wrote: > >> Joseph, > >> > >> since you did not specify your queries in more detail, I assume they are as > >> simple as > >> (1) select count(*) from<your_table>; > >> and > >> (2) select count(single_column) from<your_table>; > >> > >> In that case, you could try the following sanity check: > >> > >> (3) select count(*) from<your_table> where single_column is null; > >> > >> and check whether that returns the difference between your counts. > >> > >> If that indeed returns the difference between your global count(*) and > >> count(single_column), this would confirm the existence of NULL values, and > >> you'd need to invest which of the values in your CVS file have been > >> interpreted as NULL and why. > >> > >> In case the result of queries (2) and (3) do not add up to the number > >> returned by query (1), you might want to check the output(s) of > >> > >> TRACE select count(*) from<your_table>; > >> TRACE select count(single_column) from<your_table>; > >> TRACE select count(*) from<your_table> where single_column is null; > >> > >> (or have us check them, provided/once we find the time). > >> > >> Stefan > >> > >> On Sat, Mar 24, 2012 at 09:37:38AM -0600, Joseph Brower wrote: > >>> There shouldn't be any nulls. The records were all added by a "Copy > >>> Into" command. The files that we imported had no nulls in it at > >>> all. > >>> > >>> On 03/24/2012 01:57 AM, Sjoerd Mullender wrote: > >>>> On 2012-03-24 00:14, Joseph Brower wrote: > >>>>> We were troubleshooting some odd results coming back from our database, > >>>>> and found that it's missing some entries from a column. This appears to > >>>>> be causing some sort of offset. Does anyone have any ideas on what can > >>>>> be done to resolve it or what may have caused it? Is there any > >>>>> information we could send that would be helpful in troubleshooting this > >>>>> or for a bug report? > >>>>> > >>>>> If we do a count(*) and then a count('single_column') we are getting two > >>>>> different results (when they should be indentical) > >>>> count (*) counts all rows, whereas count(single_column) only count > >>>> non-null values. Are there any nulls in the single_column? > >>>> > >>>> > >>>> > >>>> > >>>> ------------------------------------------------------------------------------ > >>>> This SF email is sponsosred by: > >>>> Try Windows Azure free for 90 days Click Here > >>>> http://p.sf.net/sfu/sfd2d-msazure > >>>> > >>>> > >>>> _______________________________________________ > >>>> MonetDB-users mailing list > >>>> MonetDB-users(a)lists.sourceforge.net > >>>> https://lists.sourceforge.net/lists/listinfo/monetdb-users > >>> ------------------------------------------------------------------------------ > >>> This SF email is sponsosred by: > >>> Try Windows Azure free for 90 days Click Here > >>> http://p.sf.net/sfu/sfd2d-msazure > >>> _______________________________________________ > >>> MonetDB-users mailing list > >>> MonetDB-users(a)lists.sourceforge.net > >>> https://lists.sourceforge.net/lists/listinfo/monetdb-users > >> > > > > > > ------------------------------------------------------------------------------ > > This SF email is sponsosred by: > > Try Windows Azure free for 90 days Click Here > > http://p.sf.net/sfu/sfd2d-msazure > > _______________________________________________ > > MonetDB-users mailing list > > MonetDB-users(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/monetdb-users > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > MonetDB-users mailing list > MonetDB-users(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/monetdb-users

2 3

[MonetDB-users] DB Corruption
by Joseph Brower 26 Mar '12

26 Mar '12

We were troubleshooting some odd results coming back from our database, and found that it's missing some entries from a column. This appears to be causing some sort of offset. Does anyone have any ideas on what can be done to resolve it or what may have caused it? Is there any information we could send that would be helpful in troubleshooting this or for a bug report? If we do a count(*) and then a count('single_column') we are getting two different results (when they should be indentical) Thanks, Joseph Brower

5 6

[MonetDB-users] Example of GUI on top of MonetDB
by Ryad Ben-El-Kezadri 22 Mar '12

22 Mar '12

Hello, We've updated our Java GUI for analyzing network traces on top of MonetDB A HD video trailer is available here : http://www.youtube.com/watch?v=P8EEhttP-NU GPL Source is available here: https://sites.google.com/site/yavista/ Unfortunately it only works on top of MonetDB Xquery but we hope to port it on MonetDB SQL Regards Ryad

1 0

[MonetDB-users] Failure reading in negative bigint
by Nikhil Padmanabhan 22 Mar '12

22 Mar '12

Hello, I have recently started trying out monetdb and have been very impressed by its speed so far. However, I am hitting a failure trying to read in a large negative number (bitmask) into a bigint field; sql>\<test.sql operation successful value '-9223372036854775808' from line 1 field 17 not inserted, expecting type bigint failed to import table I've attached the sql commands to create the table and a test file to this message. As far as I can tell, this should be fine for being represented by a 64 bit integer.... I am running this on an OS X 10.6 64-bit system, this is the Dec-2011 SP2 version of the 64 bit binaries dowloaded from www.monetdb.org. Any help is much appreciated. Thanks in advance, -- Nikhil --------------------------------- Nikhil Padmanabhan nikhil.padmanabhan(a)yale.edu

2 1

[MonetDB-users] Problem with installation from sources
by Stathis Gkotsis 17 Mar '12

17 Mar '12

Hi all, trying to install the latest version of monetdb from sources, I just did: * ./configure --enable-debug --enable-monetdb5 --enable-sql * make and the make install I created a database and now that I try to connect to it, in the log I get: 2012-03-16 17:33:44 MSG merovingian[1729]: starting a proxy failed: cannot get address for hostname '10-04-64bit': Unknown host 2012-03-16 17:33:44 ERR merovingian[1729]: client error: cannot get address for hostname '10-04-64bit': Unknown host I tried defining 10-04-64bit in /etc/hosts as localhost / IP of the machine, but then I get: "Too many redirects" error. Any ideas on how to solve this? BR, Stathis

2 1