developers-list May 2021

developers-list@monetdb.org

2 participants
2 discussions

sys.queue.query fields do not contain original query sent to the server

by Martin van Dinther

Hi developers, When viewing the queries sent to the server via SQL: select * from queue order by tag desc; I noticed that the column "query" does NOT lists the original queries sent to the server, but changed ones. It has replaced all single quote characters ' by prefixing them with a backslash \, so \' Also it appends a \n; after the SQL statement when no ; character was present at the end. Both changes are undesirable and unneeded. Due to the added \ characters the content of the query field can no longer be copied into an SQL client (such as mclient or JdbcClient or SQuirreL) and rerun easily. All the \ characters must be manually removed, which is very annoying and error-prone. Why isn't the original query received by the server stored and returned by sys.queue.query? Can it be changed to only store the exact received SQL query string, so without any changes/alterations made to the query string? Also no adding of \n; characters. I am using latest release MonetDB Oct2020-SP5. Regards, Martin

1 year, 2 months

Announcement: New Oct2020-SP5 Bugfix release of MonetDB suite

by Sjoerd Mullender

The MonetDB team at MonetDB BV is pleased to announce the Oct2020-SP5 bugfix release of the MonetDB suite of programs. More information about MonetDB can be found on our website at <https://www.monetdb.org/>. For details on this release, please see the release notes at <https://www.monetdb.org/Downloads/ReleaseNotes>. As usual, the download location is <https://www.monetdb.org/downloads/>. Oct2020-SP5 Bugfix Release (11.39.17) Windows Packaging * Added the monetdbe library to the Windows installer. MonetDB Common * A bug that would very occasionally produce an error "strPut: incorrectly encoded UTF-8", even when no incorrectly coded characters are used at all, has been fixed. It was the result of a rare combination of strings having been added to the column that caused essentially an off-by-one type of error to occur. SQL Frontend * A bug where a sequence of TRUNCATE TABLE and COPY INTO the just truncated table would result in success being reported to both queries, but the table still being empty afterwards, has been fixed. Merovingian * When stopping monetdbd using the `monetdbd stop' command, this command now waits for 5 seconds longer than the exittimeout value before it kills the monetdbd daemon instead of only 30 seconds total (or until that daemon stops earlier). This gives the daemon enough time to terminate the mserver5 processes that it is managing. If exittimeout is negative, the daemon and the monetdbd process initiating the stop wait indefinitely until the mserver5 processes have stopped. Bug Fixes * 3336: DB files not removed if all rows are deleted, even after restart * 7104: Monetdbe NTILE function does not produce correct ordering * 7108: Monetdb crashes on query execution * 7109: MERGE Statement incorrectly reports that input relation matches multiple rows * 7110: Monetdb Query parsing consistency issues in the latest release (Remote Table)

1 year, 2 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

developers-list May 2021