June 2011 - users-list

[MonetDB-users] Proofreading your professional documents
by Richard Hounslow 24 Feb '24

24 Feb '24

Dear Professor/Lecturer Please excuse us for contacting you directly. We are offering an efficient service to help you ensure your academic and professional work is written in perfect English. We will check the grammar and style of your work and return it to you to meet your requirements and deadlines. Proof-Reading-Service.com can provide you with a professional proofreading service at a very reasonable rate. All our proofreaders are highly qualified native English speakers. Many work as leading academics in their fields and all have extensive experience of proofreading to the highest standards. If you are interested in our service, please take a look at our website: www.proof-reading-service.com All you have to do is send us your document as a word attachment with the deadline and we will guarantee delivery of a perfectly written document to give you complete confidence when you submit your work. The fee is worked out on a flat rate (£6.95 per thousand words or 0.695 pence per word), so you know exactly how much the proofreading will cost in advance. Once we have received your document(s) we will confirm the word count, the price and the deadline. If you have not heard from us within 2 hours during normal business hours after you have sent your work please resend it from a different email account or send the file to proofreadings(a)gmail.com. We look forward to hearing from you! Yours faithfully Proof-Reading-Service.com

2 2

[MonetDB-users] MonetDB JDBC 1.9 question
by Charalampos Nikolaou 23 Feb '12

23 Feb '12

Hi, I am getting some strange exceptions using MonetDB JDBC 1.8/1.9, and I decided to look into the code. While inspecting the code I came across these strange lines in MonetConnection.executeQuery(String[] templ, String query) method (http://dev.monetdb.org/hg/MonetDB/file/718da8ca0a1a/java/src/nl/cwi/monetdb…). In my case, these lines are executed for sure when doing a batch insert. So, suppose that the batch contains the following commands (as constructed by the MonetStatement.executeBatch() method): exec 1(1, 957339737330229055); exec 1(2, 278262503670654331); exec 1(805306369, 3763943296910752235) The lines in question take the above commands as a string, prepend a 's' character and append a ';' at the end. The resulting commands, which are written in the server's socket, are the following: sexec 1(1, 957339737330229055); exec 1(2, 278262503670654331); exec 1(805306369, 3763943296910752235); First of all, I am not familiar with the internals of JDBC drivers. Taking this into account, is this what it should be? From a symmetric point of view, I would assume that the correct would be the following: sexec 1(1, 957339737330229055); sexec 1(2, 278262503670654331); sexec 1(805306369, 3763943296910752235); That is, it should prepend a 's' character before an exec command. Last, are these exec commands (with or without a prepending 's') specific to MonetDB? In either case, is there any documentation to get familiar with their meaning? Thanks a lot, Babis

6 20

[MonetDB-users] protocol violation: unexpected line in data block
by tangray 27 Dec '11

27 Dec '11

the whole log file : RD 1298855541531: read final block: 57 bytes RX 1298855541531: onxRWd3Yv:mserver:9:RIPEMD160,SHA256,SHA1,MD5:LIT:SHA512: RD 1298855541531: inserting prompt TD 1298855541531: write final block: 92 bytes TX 1298855541531: BIG:risk:{SHA256}01fa94fefcadb5918473e49aaa8e425538f8d40960b2d649348cb17c599031ae:sql:krisk: RD 1298855541546: read final block: 0 bytes RX 1298855541546: RD 1298855541546: inserting prompt TD 1298855541546: write final block: 48 bytes TX 1298855541546: sSET TIME ZONE INTERVAL '+08:00' HOUR TO MINUTE; RD 1298855541546: read final block: 0 bytes RX 1298855541546: RD 1298855541546: inserting prompt TD 1298855541546: write final block: 15 bytes TX 1298855541546: Xreply_size 250 RD 1298855541546: read final block: 0 bytes RX 1298855541546: RD 1298855541546: inserting prompt TD 1298855541546: write final block: 46 bytes TX 1298855541546: sSELECT "name", "value" FROM sys.env() as env; RD 1298855541546: read final block: 4246 bytes RX 1298855541546: &1 0 46 2 46 % .env, .env # table_name % name, value # name % varchar, varchar # type % 18, 203 # length [ "gdk_arch", "32biti686-pc-win32" ] [ "gdk_version", "1.40.3" ] [ "prefix", "D:\\Program Files\\MonetDB\\MonetDB5" ] [ "exec_prefix", "D:\\Program Files\\MonetDB\\MonetDB5" ] [ "gdk_dbname", "krisk" ] [ "gdk_dbfarm", "C:\\Documents and Settings\\swordtan\\Application Data\\MonetDB5\\dbfarm" ] [ "gdk_debug", "0" ] [ "gdk_alloc_map", "no" ] [ "gdk_vmtrim", "yes" ] [ "monet_admin", "adm" ] [ "monet_prompt", ">" ] [ "monet_welcome", "yes" ] [ "monet_mod_path", "D:\\Program Files\\MonetDB\\MonetDB5\\lib\\MonetDB5;D:\\Program Files\\MonetDB\\MonetDB5\\lib\\MonetDB5\\lib;D:\\Program Files\\MonetDB\\MonetDB5\\lib\\MonetDB5\\bin" ] [ "monet_daemon", "no" ] [ "host", "localhost" ] [ "mapi_port", "50000" ] [ "mapi_clients", "2" ] [ "mapi_open", "true" ] [ "mapi_autosense", "false" ] [ "default_pipe", "inline,remap,evaluate,costModel,coercions,emptySet,aliases,mitosis,mergetable,deadcode,commonTerms,joinPath,reorder,deadcode,reduce,dataflow,history,multiplex,garbageCollector" ] [ "minimal_pipe", "inline,remap,deadcode,multiplex,garbageCollector" ] [ "sql_optimizer", "default_pipe" ] [ "sql_debug", "0" ] [ "standoff_ns", "" ] [ "standoff_start", "start" ] [ "standoff_end", "end" ] [ "config", "D:\\Program Files\\MonetDB\\MonetDB5\\etc\\monetdb5.conf" ] [ "mero_pidfile", "D:\\Program Files\\MonetDB\\MonetDB5\\var\\run\\MonetDB\\merovingian.pid" ] [ "mero_controlport", "50001" ] [ "nov2009_pipe", "inline,remap,evaluate,costModel,coercions,emptySet,aliases,mergetable,deadcode,constants,commonTerms,joinPath,deadcode,reduce,dataflow,history,multiplex,garbageCollector" ] [ "replication_pipe", "inline,remap,evaluate,costModel,coercions,emptySet,aliases,mergetable,deadcode,constants,commonTerms,joinPath,deadcode,reduce,dataflow,history,replication,multiplex,garbageCollector" ] [ "accumulator_pipe", "inline,remap,evaluate,costModel,coercions,emptySet,aliases,mergetable,deadcode,constants,commonTerms,joinPath,deadcode,reduce,accumulators,dataflow,history,multiplex,garbageCollector" ] [ "recycler_pipe", "inline,remap,evaluate,costModel,coercions,emptySet,aliases,deadcode,constants,commonTerms,joinPath,deadcode,recycle,reduce,dataflow,history,multiplex,garbageCollector" ] [ "cracker_pipe", "inline,remap,evaluate,costModel,coercions,emptySet,aliases,selcrack,deadcode,constants,commonTerms,joinPath,deadcode,reduce,dataflow,history,multiplex,garbageCollector" ] [ "sidcrack_pipe", "inline,remap,evaluate,costModel,coercions,emptySet,aliases,sidcrack,deadcode,constants,commonTerms,joinPath,deadcode,reduce,dataflow,history,multiplex,garbageCollector" ] [ "datacell_pipe", "inline,remap,evaluate,costModel,coercions,emptySet,aliases,deadcode,constants,commonTerms,joinPath,datacell,deadcode,reduce,dataflow,history,multiplex,garbageCollector" ] [ "octopus_pipe", "inline,remap,evaluate,costModel,coercions,emptySet,aliases,mitosis,mergetable,deadcode,constants,commonTerms,joinPath,octopus,deadcode,reduce,dataflow,history,multiplex,garbageCollector" ] [ "mapreduce_pipe", "inline,remap,evaluate,costModel,coercions,emptySet,aliases,mapreduce,mergetable,deadcode,commonTerms,joinPath,reorder,deadcode,reduce,dataflow,history,multiplex,garbageCollector" ] [ "datacyclotron_pipe", "inline,remap,evaluate,costModel,coercions,emptySet,aliases,datacyclotron,mergetable,deadcode,constants,commonTerms,joinPath,reorder,deadcode,reduce,dataflow,history,replication,multiplex,garbageCollector" ] [ "derive_pipe", "inline,remap,evaluate,costModel,coercions,emptySet,aliases,mergetable,deadcode,constants,commonTerms,derivePath,joinPath,deadcode,reduce,dataflow,history,multiplex,garbageCollector" ] [ "dictionary_pipe", "inline,remap,dictionary,evaluate,costModel,coercions,emptySet,aliases,mergetable,deadcode,constants,commonTerms,joinPath,deadcode,reduce,dataflow,history,multiplex,garbageCollector" ] [ "compression_pipe", "inline,remap,evaluate,costModel,coercions,emptySet,aliases,mergetable,deadcode,constants,commonTerms,joinPath,deadcode,reduce,dataflow,compression,dataflow,history,multiplex,garbageCollector" ] [ "gdk_mem_pagebits", "16" ] [ "gdk_mem_bigsize", "1048576" ] [ "monet_pid", "984" ] [ "monet_version", "5.22.3" ] RD 1298855541546: inserting prompt TD 1298855541562: write final block: 60 bytes TX 1298855541562: sselect * from risk.td_ind_security_held where id = 1560000; RD 1298855541578: read final block: 1600 bytes RX 1298855541578: &1 1 1 30 1 % risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held # table_name % id, bizdate, painnercode, currency, exchange, seccode, basickind, unrealizedgainchange, unrealizedgain, margingain, interestgain, othergain, yieldrate, accrualinterest, allgain, fullmv, marketvalue, lastfullmv, lastmarketvalue, lastcost, cost, buysum, sellsum, realizedgain, holdingqty, lastholdingqty, mvweight, lastmvweight, fullmvweight, lastfullmvweight # name % int, varchar, varchar, varchar, varchar, varchar, varchar, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal # type % 7, 8, 8, 3, 5, 6, 3, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 14, 14, 14, 14 # length RD 1298855541578: inserting prompt TD 1298855762109: write final block: 60 bytes TX 1298855762109: sselect * from risk.td_ind_security_held where id = 1560000; RD 1298855762125: read final block: 1600 bytes RX 1298855762125: &1 2 1 30 1 % risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held # table_name % id, bizdate, painnercode, currency, exchange, seccode, basickind, unrealizedgainchange, unrealizedgain, margingain, interestgain, othergain, yieldrate, accrualinterest, allgain, fullmv, marketvalue, lastfullmv, lastmarketvalue, lastcost, cost, buysum, sellsum, realizedgain, holdingqty, lastholdingqty, mvweight, lastmvweight, fullmvweight, lastfullmvweight # name % int, varchar, varchar, varchar, varchar, varchar, varchar, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal, decimal # type % 7, 8, 8, 3, 5, 6, 3, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 20, 14, 14, 14, 14 # length RD 1298855762125: inserting prompt TD 1298856279453: write final block: 69 bytes TX 1298856279453: sselect id,bizdate from risk.td_ind_security_held where id = 1560000; RD 1298856279453: read final block: 162 bytes RX 1298856279453: &1 3 1 2 1 % risk.td_ind_security_held, risk.td_ind_security_held # table_name % id, bizdate # name % int, varchar # type % 7, 8 # length [ 1560000, "20090702" ] RD 1298856279453: inserting prompt TD 1298856279468: write final block: 1797 bytes TX 1298856279468: sSELECT 'krisk' AS "TABLE_CAT", "schemas"."name" AS "TABLE_SCHEM", "tables"."name" AS "TABLE_NAME", "columns"."name" AS "COLUMN_NAME", cast(CASE "columns"."type" WHEN 'wrd' THEN -5 WHEN 'sec_interval' THEN -5 WHEN 'bigint' THEN -5 WHEN 'timetz' THEN 92 WHEN 'char' THEN 1 WHEN 'int' THEN 4 WHEN 'clob' THEN 2005 WHEN 'month_interval' THEN 4 WHEN 'tinyint' THEN -6 WHEN 'table' THEN 2003 WHEN 'date' THEN 91 WHEN 'double' THEN 8 WHEN 'decimal' THEN 3 WHEN 'timestamptz' THEN 93 WHEN 'timestamp' THEN 93 WHEN 'blob' THEN 2004 WHEN 'real' THEN 7 WHEN 'time' THEN 92 WHEN 'oid' THEN 1111 WHEN 'boolean' THEN 16 WHEN 'smallint' THEN 5 WHEN 'varchar' THEN 12 ELSE 1111 END AS smallint) AS "DATA_TYPE", "columns"."type" AS "TYPE_NAME", "columns"."type_digits" AS "COLUMN_SIZE", "columns"."type_scale" AS "DECIMAL_DIGITS", 0 AS "BUFFER_LENGTH", 10 AS "NUM_PREC_RADIX", cast(CASE "null" WHEN true THEN 1 WHEN false THEN 0 END AS int) AS "NULLABLE", cast(null AS varchar(1)) AS "REMARKS", "columns"."default" AS "COLUMN_DEF", 0 AS "SQL_DATA_TYPE", 0 AS "SQL_DATETIME_SUB", 0 AS "CHAR_OCTET_LENGTH", "columns"."number" + 1 AS "ORDINAL_POSITION", cast(null AS varchar(1)) AS "SCOPE_CATALOG", cast(null AS varchar(1)) AS "SCOPE_SCHEMA", cast(null AS varchar(1)) AS "SCOPE_TABLE", cast(1111 AS smallint) AS "SOURCE_DATA_TYPE", CASE "null" WHEN true THEN CAST ('YES' AS varchar(3)) WHEN false THEN CAST ('NO' AS varchar(3)) END AS "IS_NULLABLE" FROM "sys"."columns" AS "columns", "sys"."tables" AS "tables", "sys"."schemas" AS "schemas" WHERE "columns"."table_id" = "tables"."id" AND "tables"."schema_id" = "schemas"."id" AND LOWER("schemas"."name") LIKE 'risk' AND LOWER("tables"."name") LIKE 'td_ind_security_held' AND LOWER("columns"."name") LIKE 'id' ORDER BY "TABLE_SCHEM", "TABLE_NAME", "ORDINAL_POSITION"; RD 1298856279484: read final block: 853 bytes RX 1298856279484: &1 4 1 22 1 % ., sys.schemas, .tables, .columns, ., .columns, .columns, .columns, ., ., ., ., .columns, ., ., ., ., ., ., ., ., . # table_name % TABLE_CAT, TABLE_SCHEM, TABLE_NAME, COLUMN_NAME, DATA_TYPE, TYPE_NAME, COLUMN_SIZE, DECIMAL_DIGITS, BUFFER_LENGTH, NUM_PREC_RADIX, NULLABLE, REMARKS, COLUMN_DEF, SQL_DATA_TYPE, SQL_DATETIME_SUB, CHAR_OCTET_LENGTH, ORDINAL_POSITION, SCOPE_CATALOG, SCOPE_SCHEMA, SCOPE_TABLE, SOURCE_DATA_TYPE, IS_NULLABLE # name % char, varchar, varchar, varchar, smallint, varchar, int, int, tinyint, tinyint, int, varchar, varchar, tinyint, tinyint, tinyint, int, varchar, varchar, varchar, smallint, varchar # type % 5, 4, 20, 2, 1, 3, 2, 1, 1, 2, 1, 0, 0, 1, 1, 1, 1, 0, 0, 0, 4, 2 # length [ "krisk", "risk", "td_ind_security_held", "id", 4, "int", 32, 0, 0, 10, 0, NULL, NULL, 0, 0, 0, 1, NULL, NULL, NULL, 1111, "NO" ] RD 1298856279484: inserting prompt TD 1298856279500: write final block: 1802 bytes TX 1298856279500: sSELECT 'krisk' AS "TABLE_CAT", "schemas"."name" AS "TABLE_SCHEM", "tables"."name" AS "TABLE_NAME", "columns"."name" AS "COLUMN_NAME", cast(CASE "columns"."type" WHEN 'wrd' THEN -5 WHEN 'sec_interval' THEN -5 WHEN 'bigint' THEN -5 WHEN 'timetz' THEN 92 WHEN 'char' THEN 1 WHEN 'int' THEN 4 WHEN 'clob' THEN 2005 WHEN 'month_interval' THEN 4 WHEN 'tinyint' THEN -6 WHEN 'table' THEN 2003 WHEN 'date' THEN 91 WHEN 'double' THEN 8 WHEN 'decimal' THEN 3 WHEN 'timestamptz' THEN 93 WHEN 'timestamp' THEN 93 WHEN 'blob' THEN 2004 WHEN 'real' THEN 7 WHEN 'time' THEN 92 WHEN 'oid' THEN 1111 WHEN 'boolean' THEN 16 WHEN 'smallint' THEN 5 WHEN 'varchar' THEN 12 ELSE 1111 END AS smallint) AS "DATA_TYPE", "columns"."type" AS "TYPE_NAME", "columns"."type_digits" AS "COLUMN_SIZE", "columns"."type_scale" AS "DECIMAL_DIGITS", 0 AS "BUFFER_LENGTH", 10 AS "NUM_PREC_RADIX", cast(CASE "null" WHEN true THEN 1 WHEN false THEN 0 END AS int) AS "NULLABLE", cast(null AS varchar(1)) AS "REMARKS", "columns"."default" AS "COLUMN_DEF", 0 AS "SQL_DATA_TYPE", 0 AS "SQL_DATETIME_SUB", 0 AS "CHAR_OCTET_LENGTH", "columns"."number" + 1 AS "ORDINAL_POSITION", cast(null AS varchar(1)) AS "SCOPE_CATALOG", cast(null AS varchar(1)) AS "SCOPE_SCHEMA", cast(null AS varchar(1)) AS "SCOPE_TABLE", cast(1111 AS smallint) AS "SOURCE_DATA_TYPE", CASE "null" WHEN true THEN CAST ('YES' AS varchar(3)) WHEN false THEN CAST ('NO' AS varchar(3)) END AS "IS_NULLABLE" FROM "sys"."columns" AS "columns", "sys"."tables" AS "tables", "sys"."schemas" AS "schemas" WHERE "columns"."table_id" = "tables"."id" AND "tables"."schema_id" = "schemas"."id" AND LOWER("schemas"."name") LIKE 'risk' AND LOWER("tables"."name") LIKE 'td_ind_security_held' AND LOWER("columns"."name") LIKE 'bizdate' ORDER BY "TABLE_SCHEM", "TABLE_NAME", "ORDINAL_POSITION"; RD 1298856279515: read final block: 862 bytes RX 1298856279515: &1 5 1 22 1 % ., sys.schemas, .tables, .columns, ., .columns, .columns, .columns, ., ., ., ., .columns, ., ., ., ., ., ., ., ., . # table_name % TABLE_CAT, TABLE_SCHEM, TABLE_NAME, COLUMN_NAME, DATA_TYPE, TYPE_NAME, COLUMN_SIZE, DECIMAL_DIGITS, BUFFER_LENGTH, NUM_PREC_RADIX, NULLABLE, REMARKS, COLUMN_DEF, SQL_DATA_TYPE, SQL_DATETIME_SUB, CHAR_OCTET_LENGTH, ORDINAL_POSITION, SCOPE_CATALOG, SCOPE_SCHEMA, SCOPE_TABLE, SOURCE_DATA_TYPE, IS_NULLABLE # name % char, varchar, varchar, varchar, smallint, varchar, int, int, tinyint, tinyint, int, varchar, varchar, tinyint, tinyint, tinyint, int, varchar, varchar, varchar, smallint, varchar # type % 5, 4, 20, 7, 2, 7, 1, 1, 1, 2, 1, 0, 0, 1, 1, 1, 1, 0, 0, 0, 4, 2 # length [ "krisk", "risk", "td_ind_security_held", "bizdate", 12, "varchar", 8, 0, 0, 10, 0, NULL, NULL, 0, 0, 0, 2, NULL, NULL, NULL, 1111, "NO" ] RD 1298856279515: inserting prompt TD 1298856508906: write final block: 77 bytes TX 1298856508906: sselect id,bizdate,allgain from risk.td_ind_security_held where id = 1560000; RD 1298856508906: read final block: 187 bytes RX 1298856508906: &1 6 1 3 1 % risk.td_ind_security_held, risk.td_ind_security_held, risk.td_ind_security_held # table_name % id, bizdate, allgain # name % int, varchar, decimal # type % 7, 8, 20 # length RD 1298856508906: inserting prompt

2 1

[MonetDB-users] Installation problem in Fedora 15
by elarios＠liacs.nl 06 Jul '11

06 Jul '11

Hi, I'm interested in using MonetDB in my project and I'm a beginner in this topic, so I'm sorry for the silly questions that I can make. The problem is: I'm trying to install MonetDB-SQL Server in Fedora 15, but when I execute the command: yum install MonetDB-SQL-server5 MonetDB-client The output makes reference to a repository that doesn't exist: http://dev.monetdb.org/downloads/Fedora/15/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found : http://dev.monetdb.org/downloads/Fedora/15/x86_64/repodata/repomd.xml Trying other mirror. http://dev.monetdb.org/downloads/Fedora/15/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found : http://dev.monetdb.org/downloads/Fedora/15/x86_64/repodata/repomd.xml Trying other mirror. Error: Cannot retrieve repository metadata (repomd.xml) for repository: monetdb. Please verify its path and try again Should I downgrade my operating system to Fedora 14? Do you have any suggestions? Thanks for your time and help, Best regards, Enrique.

3 5

[MonetDB-users] PhD opening at CWI - Adaptive indexing techniques for modern database systems
by Stratos Idreos 23 Jun '11

23 Jun '11

Subject: Adaptive indexing techniques for modern database systems. The Centrum Wiskunde & Informatica (CWI) has a full time vacancy for a talented PhD candidate in the Database Architectures group (http://www.cwi.nl/en/research-groups/Database-Architectures). The position is in the broad area of adaptive indexing techniques for modern database systems. Adaptive indexing is a major challenge in database research; it tries to completely alleviate the need for indexing and tuning steps leading to database systems that require no physical design set-up and can cope immediately with any workload. This leads to database systems that are instantly usable and thus more applicable to numerous new applications that now consider databases too slow, too complex and too old. This position will focus specifically on adaptive indexing for extremely large databases where traditional indexing represents a major bottleneck. The Database Architectures group is one of the world-wide leading groups in system-oriented database research, e.g., it received the 10-year best paper award at VLDB 2009 for their pioneering research on hardware-aware database technology and the column-store model and the 2011 ACM SIGMOD Jim Gray Dissertation award for the database cracking work. The group has a unique methodology that combines fundamental database research with active participation of all group members in database engineering, centred around the open-source analytical database system MonetDB (http://www.monetdb.org/). An internship at one of the partnering database research labs world-wide is considered part of the PhD track. REQUIREMENTS The PhD candidates must have a master degree in computer science (or a 5 year diploma), (specialisation databases, distributed systems, software engineering) mathematics, or related fields. Preferable qualifications for candidates include proven research talent, system programming skills (C/C++), practical experience with using and implementing database systems, and software development in a team. Candidates are expected to have an excellent command of English, and good academic writing and presentation skills. CENTRUM WISKUNDE & INFORMATICA (CWI) Founded in 1946, the Centrum Wiskunde & Informatica (CWI) is the national research institute for mathematics and computer science in the Netherlands. It is located at the Science Park Amsterdam and is part of the “Netherlands Organisation for Scientific Research” (NWO). The institute is internationally focused and renowned for its high quality research, a substantial fraction of which is carried out in the framework of (inter)national programs. Over 160 researchers conduct pioneering research and share their acquired knowledge with society. More than 30 researchers are employed as professors at universities. The institute has generated twenty-one spin-off companies. CWI maintains excellent relations with industry and the academic world, both in the Netherlands as well as abroad. After their research careers at CWI, an increasing number of young staff members find employment in these sectors or in spin-off companies that are based on research results from CWI. Of course, library and computing facilities are first-rate. CWI's non-scientific services to its personnel include career planning, training and courses, assistance in finding housing, and tailor-made solutions to problems that may occasionally arise. TERMS AND CONDITIONS The terms of employment are in accordance with the Dutch Collective Labour Agreement for Research Institutes ("CAO-onderzoeksinstellingen"). Moreover CWI offers attractive working conditions, including flexible scheduling and help with housing for expat employees. The gross monthly salary, for an employee on a full time basis, is €2,037 during the first year and increases to €2,610 over a four year period. CWI also offers excellent and flexible terms of employment, including an employee pension fund. INFORMATION Additional information can be obtained from: dr. Stratos Idreos, email stratos.idreos(a)cwi.nl, telephone +31(0)20 592 4169. or dr. Stefan Manegold, email stefan.manegold(a)cwi.nl, telephone +31(0)20 592 4212, or prof. dr. Martin Kersten, email martin.kersten(a)cwi.nl, telephone +31(0)20 592 4066. APPLICATION Please send your application before 31 July 2011 to: pd(a)cwi.nl. Applications should include a detailed CV, a motivation letter, a list of your M.SC. courses and grades, a copy of your master thesis, and preferably a list of publications.

1 0

[MonetDB-users] Parallelization
by Michael Kusber 20 Jun '11

20 Jun '11

Hi, I'm playing with parallization of databases and I am a little confused about my result on MonetDB. Scenario: 15 Millions of Entries and i want to find the number of entries where the attributes are in a certain sector (i know, a simple select would do the work but i wanted a simple example) i have java code that get all 15 Mio. Data from the database via JDBC and iterates over them with a loop without multithreading. --> 13 ms then i created a stored function: CREATE FUNCTION isInRangexy(x DECIMAL(10,7), y DECIMAL(10,7)) RETURNS BOOL BEGIN ATOMIC IF x > 50 AND y < 50 THEN RETURN true; ELSE RETURN false; END IF; END Then I call it with: SELECT COUNT(*) FROM location WHERE isInRange(x,y) It works, but it is more than 3 times slower than the first java option. I had thought i would get benefit from the fact that i don't need to transfer all the data to the application and of some parallelization and other optimization from monetdb. Did I made a mistake? Can I use another example to get the anticipated results? thanks, michael

2 1

[MonetDB-users] Stored procedures
by Michael Kusber 19 Jun '11

19 Jun '11

Hi, is it possible to achieve the following using SQL stored procedures à la "CREATE PROCEDURE XYZ"? I want to write a function that iterates over a table and adds 2 on a certain attribute. i am realizing that i could do this by an UPDATE, but I wanted to see, whether it would be executed more parallel inside a stored procedure. Is there a way of formulating this in a procedure? do i need to define a function in MAL? would this result in more parallel execution? thanks, michael

2 1

[MonetDB-users] Data compression in MonetDB
by Ken Cheng 18 Jun '11

18 Jun '11

Hi All, I am going to build a DW based on MonetDB. After check on the internet I found that MonetDB does not do data compression. Same data set in MonetDb is much bigger than MySQL and infoBright. Are there any plan to do data compression in the MonetDB? Yours sincerely, Ken Cheng

2 3

[MonetDB-users] Windowing functions ?
by Fabian Pijcke 15 Jun '11

15 Jun '11

Hello everyone, After visiting the MonetDB website, I didn't saw any information about the windowing functions of SQL (ranking, selecting max according to a defined order, etc.) A (very) short introduction can be found on wikipedia: http://en.wikipedia.org/wiki/Select_%28SQL%29#Window_function I know it is implemented into PostGreSQL, Oracle and Microsoft SQL Server. Is there any chance to see this function in MonetDB in the future ? Thanks in advance, sorry for my poor english ... :( Fabian Pijcke

2 2

[MonetDB-users] Create Database - Load Data
by Lowterm 14 Jun '11

14 Jun '11

Hi, how can I create a new Database under Windows and how can I load data in a table form a external file? Thanks -- View this message in context: http://old.nabble.com/Create-Database---Load-Data-tp31653813p31653813.html Sent from the monetdb-users mailing list archive at Nabble.com.

8 24