The MonetDB team at CWI/MonetDB BV is pleased to announce the
Feb2013 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/>.
Feb 2013 feature release
Testing Environment * enabled "top-level" Mtest.py So far, while
Mtest.py could be called in any subdirectory of
the MonetDB source tree (and could then run all
tests in the entire sub-tree), it was not possible
to call Mtest.py in the top-level MonetDB source
directory to run all tests. Instead, to run all
tests, Mtest.py had to be called at least 4 times,
once in each of these directories: "clients",
"monetdb5", "sql", "geom". Now, it is possible to
call Mtest.py once in the top-level MonetDB source
directory to run all tests in one go. The
behaviour of calling Mtest.py in any subdirectory,
including the four mentioned above, did not
changed, other than that now obsolete command line
options "-p / --package <package>" and "-5 /
--monetdb5" have been removed.
Java Module * merocontrol was changed to return server URIs, and
lastStop time. Connections and dbpath were
removed.
* Mapi protocol v8 support was removed from
MapiSocket. Protocol v8 has not been used by the
servers any more since Apr2012 release
Client Package * Mapi protocol v8 support was removed from all
client drivers. Protocol v8 has not been used by
the servers any more since Apr2012 release
* The tool mnc was removed from installations
* msqldump: Implmented an option (--table/-t) to
dump a single table.
* Changed msqdump's trace option to be in line with
mclient. In both cases, the long option is
--Xdebug and the short option is -X.
MonetDB5 Server * mserver5: The --dbname and --dbfarm options have
been replaced by the single --dbpath option.
* The scheduler of mserver5 was changed to use a
fixed set of workers to perform the work for all
connected clients. Previously, each client
connection had its own set of workers, easily
causing resource problems upon multiple
connections to the server.
Merovingian * Upgrade support for dbfarms from Mar2011 and
Aug2011 was dropped
* monetdb status now uses a more condensed output,
to cater for the uris being shown, and prints how
long a database is stopped, or how long ago it
crashed
* monetdb status now prints the connection uri for
each database, when available. The connections and
database path properties have been dropped.
* monetdb status now prints last crash date only if
the database has not been started since.
Bug Fixes * 2291: small doubles end up as NULL after
arithmetic
* 3215: Calculation Date function using interval and
year
* 3033: stethoscope needs better documentation
* 3084: Timestamp arithmetic very slow (especially
on Windows)
* 3125: Python tests fail after recent Python API
changes
* 3172: assertion fails on table function with
subselects as parameters
* 3178: one scan is enough to implement ALGstdev_@1
in monetdb5/modules/kernel/algebra.mx
* 3179: LIKE: batstr.like+algebra.uselect called
instead of pcre.like_filter
* 3193: Expressions not supported in the GROUP BY or
ORDER BY clause.
* 3216: "unknown property" error setting format and
width in .monetdb file
* 3217: gdk_posix fails to compile under NetBSD
* 3221: can no execute large statements
* 3227: MT_set_lock() call on an non-initialized
lock
Bonsoir,
Je travaille depuis peu de temps sur MonetDB et je rencontre des difficultés à comprendre le principe de fonctionnement, pour cela j'ai des questions à vous poser.
1 - Où puis-je trouver le code source;
2 - Comment le compiler;
3 - Pour information j'utilise Windows comme système d'exploitation.
Merci de me répondre.
Cordialement
a.bouslah(a)yahoo.fr
Hi,
The name of the coercions optimizer in the codes array in opt_wrapper.c is
wrong (currently it's "coercion"), and so it is never run.
This patch fixes:
diff -r 6e9b305e92e2 monetdb5/optimizer/opt_wrapper.c
--- a/monetdb5/optimizer/opt_wrapper.c Sun Feb 10 17:39:23 2013 +0100
+++ b/monetdb5/optimizer/opt_wrapper.c Tue Feb 12 11:33:20 2013 +0000
@@ -84,7 +84,7 @@
{"aliases", &OPTaliasesImplementation},
{"centipede", &OPTcentipedeImplementation},
{"cluster", &OPTclusterImplementation},
- {"coercion", &OPTcoercionImplementation},
+ {"coercions", &OPTcoercionImplementation},
{"commonTerms", &OPTcommonTermsImplementation},
{"compression", &OPTcompressionImplementation},
{"costModel", &OPTcostModelImplementation},
Regards,
Pete
I have started facing issues when trying to connect to the DB using mclient remotely/locally.
All my services have started failing as the DB is no longer responding(using JDBC).
There is hardly any load on the DB - no memory/cpu usage.
Although the monetdb status shows a health of only 47%(What does this mean?)
When I do a sockstat on the merovingian I can see the client's socket.
But when I sockstat on the mserver5 process I don't see that. (FYI- when I am able to connect using mclient I see this socket in mserver's sockstat instead of monetdbd)
I do get the mclient prompt sometimes with full functionality. But most of the times it just gets stuck and the prompt never occurs.
Any more diagnostics that I can perform to resolve this?
When I ctrl+c on the mclient the mclient process stops but socket stays in ESTABLISHED state on server. Verified it by comparign port no. before and after killing mclient and making sure no one else is connected.
Regards,
Tapomay.
Hi,
I may have found a bug in sql.Binary(). Here is the patch:
--- pythonize.py 2013-02-03 15:22:09.217186598 +0100
+++ pythonize.py.fix 2013-02-03 15:23:34.613187703 +0100
@@ -119,7 +119,7 @@
def Binary(data):
"""returns binary encoding of data"""
- return ''.join([hex(ord(i))[2:] for i in data]).upper()
+ return ''.join(["%02X" % ord(i) for i in data])
def DateFromTicks(ticks):
"""Convert ticks to python Date"""
The hex() built-in returns three character string for integers lower than
15. This combined with the original code's [2:] results in corrupt string
representations of binary objects having bytes with these values.
cheers
Mate