An exception(see the bottom stack) was thrown when I use the JDBC
driver(monetdb-jdbc-2.10.jar, MonetDB Database Server v1.7 (Feb2013-SP4) )
on linux(Linux *** 2.6.18-164.11.1.el5 #1 SMP Wed Jan 6 13:26:04 EST 2010
x86_64 x86_64 x86_64 GNU/Linux), but with the same code no exceptions are
thrown on windows7
When DML SQL is executed by preparestatement(or Statement) I Just got the
exception on linux, can anyone tell me what happened.
Exception in thread "main" java.lang.IndexOutOfBoundsException
at java.nio.StringCharBuffer.subSequence(StringCharBuffer.java:92)
at
nl.cwi.monetdb.mcl.parser.StartOfHeaderParser.getNextAsString(StartOfHeaderP
arser.java:146)
at
nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.executeQuery(MonetConnectio
n.java:2394)
at
nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.processQuery(MonetConnectio
n.java:2284)
at
nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:508)
at
nl.cwi.monetdb.jdbc.MonetStatement.internalBatch(MonetStatement.java:261)
at
nl.cwi.monetdb.jdbc.MonetStatement.executeBatch(MonetStatement.java:230)
at MonetdbBenchmark.insert(MonetdbBenchmark.java:50)
at MonetdbBenchmark.main(MonetdbBenchmark.java:19)
Hello,
Has anyone out there done any work on extending MonetDB to support skyline queries natively? I may be interested in work along these lines but I'd rather not reinvent the wheel. If anyone has preceded me, I'd love to hear about your work.
Thanks,
Steve Morgan
HI,
We are using monetdb for some statistical analysis.
The queries are very fast (0.2 sec), but some times (not regularly) the queries get peeks of up to 32 sec for the same query.
CPU and RAM don't change and are way higher than actually needed.
Does any one have this same situation? Any idea what could be doing this?
Best regards and thanks to any help.
sebastian
The MonetDB team at CWI/MonetDB BV is pleased to announce the
Feb2013-SP6 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/>.
Feb 2013-SP6 bugfix release
MonetDB5 Server
* Fixed a possible buffer overflow in the COPY INTO code.
* Fixed a problem that when the server is using all available threads
for a query, it was not possible to attach another client and have
it execute even the smallest query. This is fixed by creating extra
threads for each client entering the fray at the cost of having
more threads that execute queries. But at least there is guaranteed
progress for all clients (modulo the operating system scheduler).
See bug #3258.
Merovingian
* monetdbd(1) now refuses to startup if it cannot read the properties
from the dbfarm, bug #3398
Client Package
* mclient: Fixed a bug where the -H option only worked if the
readline history file already existed. Now we properly create and
use the history file.
* ODBC: Fixed interpretation SQL_C_SLONG/SQL_C_ULONG/SQL_C_LONG to
refer to a 32 bit integer always (i.e. "int" on 64 bit
architectures despite the name and the Microsoft documentation).
This seems to be the consensus.
* ODBC: Fixed transaction level: MonetDB only supports the highest
level (SQL_TXN_SERIALIZABLE), so setting the transaction level can
be accepted and ignored.
MonetDB Common
* Stopped using the deprecated sbrk() system call.
* Fixed a problem when reverse sorting a sorted column.
* Fixed bugs that deal with problems that could possibly occur when
transactions are aborted and the server is restarted. See bug
#3243.
* A bug was fixed in the handling of grouped aggregates when all
values in a group are null. See bug #3388.
SQL
* Fixed a bug where the server at some point stopped saving compiled
queries in the SQL query cache.
Bug Fixes
* 3243: Segmentation fault (possible data corruption) after clean
shutdown
* 3258: Scheduling issues
* 3368: BAT sortedness info ignored on ORDER BY and TOPN
* 3374: UNIQUE constraint does not set tkey property on the
corresponding BAT
* 3382: Response to PREPARE emtpy if query contains a LIMIT
* 3385: Simple query fails with 'identifier not found'
* 3387: mclient does not properly double quote schema names when
using autofill tab
* 3388: case statement in "order by" clause doesn't work when used
together with "group by"
* 3389: median function with "group by" - SIGSEGV
* 3392: ODBC datatype conversion for INTEGER not working properly
* 3394: "Cannot find column type" error in temporary tables in
functions
* 3395: error occurred during a query: "'CASE WHEN" sentence
* 3396: Improper UDF expansion
* 3397: Error in ODBC-Driver when using Prepared Statements
* 3398: Cannot stop monetdbd after erroneously starting an
uninitialized dbfarm