- users-list - monetdb.org

forward=redirect file descriptor leak
by Karl Seguin 28 Jan '21

28 Jan '21

It appears that when configured with forward=redirect, there's a leak for every connection. I've reproduced using the two latest releases: ./monetdbd create ./farm ./monetdbd set forward=redirect ./farm ./monetdbd set listenaddr=127.0.0.1 ./farm ./monetdbd start ./farm ./monetdb create test ./monetdb release test lsof -p $(pidof monetdbd) | wc -l 40 ./mclient -d test -s "select 1" lsof -p $(pidof monetdbd) | wc -l 41 ./mclient -d test -s "select 1" lsof -p $(pidof monetdbd) | wc -l 42 ./mclient -d test -s "select 1" lsof -p $(pidof monetdbd) | wc -l 43 Karl

2 1

Announcement: New Oct2020-SP2 Bugfix release of MonetDB suite
by Sjoerd Mullender 25 Jan '21

25 Jan '21

The MonetDB team at MonetDB BV is pleased to announce the Oct2020-SP2 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-SP2 Bugfix Release (11.39.11) SQL Frontend * CREATE [OR REPLACE] TRIGGER schema_name.trigger_name is now disallowed, because the trigger will be stored on the same schema as the table it refers to. Use a schema-qualified on the table reference (ie ON clause) when necessary. Bug Fixes * 6862: mserver5: crashes under update_table() when calling lib_sql.so ( max_clients = 2048) * 7002: monetdb stop fails * 7012: mclient enters an infinite loop when a file on the command line does not exist * 7013: Select * on grouped view: wrong error "cannot use non GROUP BY column 'a1' in query results without an aggregate function" * 7017: mal seems to leak in functions * 7020: release an older savepoint causes "BATproject2: does not match always" * 7021: savepoints crash mserver5 * 7022: transaction with an unreleased savepoint not properly persisted * 7023: CREATE VIEW: SELECT: cannot use non GROUP BY column '%1' in query results without an aggregate function * 7024: DELETE FROM or TRUNCATE on freshly created table leads to loosing all further inserts in same transaction * 7030: DROP TABLE with AUTO_INCREMENT doesn't drop sequence causing left-over dependency * 7034: User with sysadmin role cannot create another user * 7035: UPDATE and SELECT column privileges * 3772: Any user can grant a role.

1 0

Re: MonetDB-PHP Error on parameterized query with timestamp
by Kevork Vartanian 09 Dec '20

09 Dec '20

Thank you Ying and everyone involved. Regards, Kevork Vartanian ________________________________ From: users-list <users-list-bounces+kev=innotta.com.au(a)monetdb.org> on behalf of users-list-request(a)monetdb.org <users-list-request(a)monetdb.org> Sent: Thursday, 10 December 2020 1:56 AM To: users-list(a)monetdb.org <users-list(a)monetdb.org> Subject: users-list Digest, Vol 100, Issue 5 Send users-list mailing list submissions to users-list(a)monetdb.org To subscribe or unsubscribe via the World Wide Web, visit https://www.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: MonetDB-PHP Error on parameterized query with timestamp (Ying Zhang) ---------------------------------------------------------------------- Message: 1 Date: Wed, 9 Dec 2020 15:56:28 +0100 From: Ying Zhang <Y.Zhang(a)cwi.nl> To: Communication channel for MonetDB users <users-list(a)monetdb.org> Subject: Re: MonetDB-PHP Error on parameterized query with timestamp Message-ID: <6F309253-9D88-4E52-B079-2F2CBDCF1B81(a)cwi.nl> Content-Type: text/plain; charset="us-ascii" FYI, this error has really been resolved. Deployed a fix under version 1.1.3., for more info see Stack Overflow: - https://stackoverflow.com/questions/65077831/monetdb-php-error-on-parameter… <https://stackoverflow.com/questions/65077831/monetdb-php-error-on-parameter…> Updated the user doc: - https://github.com/MonetDB/MonetDB-PHP#example-3-parameterized-query-with-p… <https://github.com/MonetDB/MonetDB-PHP#example-3-parameterized-query-with-p…> And the protocol doc: - https://github.com/MonetDB/MonetDB-PHP/blob/master/protocol_doc/README.md#7… <https://github.com/MonetDB/MonetDB-PHP/blob/master/protocol_doc/README.md#7…> > On 8 Dec 2020, at 10:45, Ying Zhang <Y.Zhang(a)cwi.nl> wrote: > > Hai Kevork, > > Our MonetDB/PHP expert has answered this question in Stack Overflow: > > https://stackoverflow.com/questions/65077831/monetdb-php-error-on-parameter… <https://stackoverflow.com/questions/65077831/monetdb-php-error-on-parameter…> > > For users on this list, this is the Stack Overflow answer: > > the problem is that the "birth_date" field is not of a "date-time" type, but it's "date" only. So just remove "12:37:16" and it will work. The "char" type is converted to "date" by MonetDB itself, "date" doesn't have a specific literal in the SQL language. This works, I tested: > > $result = $connection->Query(<<<EOF > select > * > from > "cats" > where > "name" = ? > and "weight_kg" > ? > and "birth_date" < ? > limit > 10 > EOF > , [ "D'artagnan", 5.3, "2020-02-28" ]); > > Regards, > Jennie > >> On 7 Dec 2020, at 04:23, Kevork Vartanian <kev(a)innotta.com.au <mailto:kev@innotta.com.au>> wrote: >> >> Hi Sjoerd, >> >> Thank you for getting back to me. >> >> My colleague tested what you suggested and got the same error so it is still failing. He is certain he is passing the correct value as he is able to execute the same query in raw format, so he believed it has to do with the way params are implemented. I'm no expert but he said it looks like an error from C language. >> >> Please advise. >> >> Thank you. >> >> Regards, >> >> Kevork Vartanian >> >> From: users-list <users-list-bounces+kev=innotta.com.au(a)monetdb.org <mailto:users-list-bounces+kev=innotta.com.au@monetdb.org>> on behalf of users-list-request(a)monetdb.org <mailto:users-list-request@monetdb.org> <users-list-request(a)monetdb.org <mailto:users-list-request@monetdb.org>> >> Sent: Friday, 4 December 2020 10:00 PM >> To: users-list(a)monetdb.org <mailto:users-list@monetdb.org> <users-list(a)monetdb.org <mailto:users-list@monetdb.org>> >> Subject: users-list Digest, Vol 100, Issue 2 >> >> Send users-list mailing list submissions to >> users-list(a)monetdb.org <mailto:users-list@monetdb.org> >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://www.monetdb.org/mailman/listinfo/users-list <https://www.monetdb.org/mailman/listinfo/users-list> >> or, via email, send a message with subject or body 'help' to >> users-list-request(a)monetdb.org <mailto:users-list-request@monetdb.org> >> >> You can reach the person managing the list at >> users-list-owner(a)monetdb.org <mailto:users-list-owner@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. MonetDB-PHP Error on parameterized query with timestamp >> (Kevork Vartanian) >> 2. Re: MonetDB-PHP Error on parameterized query with timestamp >> (Sjoerd Mullender) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Fri, 4 Dec 2020 00:11:59 +0000 >> From: "Kevork Vartanian" <kev(a)innotta.com.au <mailto:kev@innotta.com.au>> >> To: "users-list(a)monetdb.org <mailto:users-list@monetdb.org>" <users-list(a)monetdb.org <mailto:users-list@monetdb.org>> >> Subject: MonetDB-PHP Error on parameterized query with timestamp >> Message-ID: >> <SYBP282MB0346DC1924EC1C610E29428B81F10(a)SYBP282MB0346.AUSP282.PROD.OUTLOOK.COM <mailto:SYBP282MB0346DC1924EC1C610E29428B81F10@SYBP282MB0346.AUSP282.PROD.OUTLOOK.COM>> >> >> Content-Type: text/plain; charset="iso-8859-1" >> >> Hi, >> >> The below is from my colleague who is not a member on this list, so I'm sending on his behalf. >> >> I'm using MonetDB with MonetDB-PHP library. >> >> >> I have followed the documentation from: https://github.com/MonetDB/MonetDB-PHP <https://github.com/MonetDB/MonetDB-PHP> >> >> >> Everything is working fine, but if I set parameter for timestamp type column I get the following error: >> >> Error from MonetDB: 42000!Wrong type for argument 1 of function call: char, expected timestamp >> >> For example, this is working: >> >> $result = $connection->Query(' >> select >> * >> from >> "cats" >> where >> "name" = ? >> and "weight_kg" > ? >> limit >> 10', [ "D'artagnan", 5.3 ]); >> >> but this will not work: >> >> $result = $connection->Query(' >> select >> * >> from >> "cats" >> where >> "name" = ? >> and "weight_kg" > ? >> and "birthdate" < ? // timestamp data type >> limit >> 10 >> ', [ "D'artagnan", 5.3, "2020-02-28 12:37:16" ]); >> >> >> The error occurs for any column that is of timestamp type and only when passing value as parameter. >> >> >> What am I doing wrong? >> >> Thank you. >> >> >> Regards, >> >> Kevork Vartanian >> >> This email correspondence may contain privileged information and it is intended to be transmitted to the addressee abovementioned. If you are not the intended recipient of this email correspondence, you must not distribute, copy, forward or rely upon its contents. We ask that you notify the sender of this error and immediately delete this email correspondence. >>

1 0

Re: MonetDB-PHP Error on parameterized query with timestamp
by Kevork Vartanian 09 Dec '20

09 Dec '20

Hi Sjoerd, Thank you for getting back to me. My colleague tested what you suggested and got the same error so it is still failing. He is certain he is passing the correct value as he is able to execute the same query in raw format, so he believed it has to do with the way params are implemented. I'm no expert but he said it looks like an error from C language. Please advise. Thank you. Regards, Kevork Vartanian ________________________________ From: users-list <users-list-bounces+kev=innotta.com.au(a)monetdb.org> on behalf of users-list-request(a)monetdb.org <users-list-request(a)monetdb.org> Sent: Friday, 4 December 2020 10:00 PM To: users-list(a)monetdb.org <users-list(a)monetdb.org> Subject: users-list Digest, Vol 100, Issue 2 Send users-list mailing list submissions to users-list(a)monetdb.org To subscribe or unsubscribe via the World Wide Web, visit https://www.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. MonetDB-PHP Error on parameterized query with timestamp (Kevork Vartanian) 2. Re: MonetDB-PHP Error on parameterized query with timestamp (Sjoerd Mullender) ---------------------------------------------------------------------- Message: 1 Date: Fri, 4 Dec 2020 00:11:59 +0000 From: "Kevork Vartanian" <kev(a)innotta.com.au> To: "users-list(a)monetdb.org" <users-list(a)monetdb.org> Subject: MonetDB-PHP Error on parameterized query with timestamp Message-ID: <SYBP282MB0346DC1924EC1C610E29428B81F10(a)SYBP282MB0346.AUSP282.PROD.OUTLOOK.COM> Content-Type: text/plain; charset="iso-8859-1" Hi, The below is from my colleague who is not a member on this list, so I'm sending on his behalf. I'm using MonetDB with MonetDB-PHP library. I have followed the documentation from: https://github.com/MonetDB/MonetDB-PHP Everything is working fine, but if I set parameter for timestamp type column I get the following error: Error from MonetDB: 42000!Wrong type for argument 1 of function call: char, expected timestamp For example, this is working: $result = $connection->Query(' select * from "cats" where "name" = ? and "weight_kg" > ? limit 10', [ "D'artagnan", 5.3 ]); but this will not work: $result = $connection->Query(' select * from "cats" where "name" = ? and "weight_kg" > ? and "birthdate" < ? // timestamp data type limit 10 ', [ "D'artagnan", 5.3, "2020-02-28 12:37:16" ]); The error occurs for any column that is of timestamp type and only when passing value as parameter. What am I doing wrong? Thank you. Regards, Kevork Vartanian This email correspondence may contain privileged information and it is intended to be transmitted to the addressee abovementioned. If you are not the intended recipient of this email correspondence, you must not distribute, copy, forward or rely upon its contents. We ask that you notify the sender of this error and immediately delete this email correspondence.

2 2

MonetDB-PHP Error on parameterized query with timestamp
by Kevork Vartanian 04 Dec '20

04 Dec '20

Hi, The below is from my colleague who is not a member on this list, so I'm sending on his behalf. I'm using MonetDB with MonetDB-PHP library. I have followed the documentation from: https://github.com/MonetDB/MonetDB-PHP Everything is working fine, but if I set parameter for timestamp type column I get the following error: Error from MonetDB: 42000!Wrong type for argument 1 of function call: char, expected timestamp For example, this is working: $result = $connection->Query(' select * from "cats" where "name" = ? and "weight_kg" > ? limit 10', [ "D'artagnan", 5.3 ]); but this will not work: $result = $connection->Query(' select * from "cats" where "name" = ? and "weight_kg" > ? and "birthdate" < ? // timestamp data type limit 10 ', [ "D'artagnan", 5.3, "2020-02-28 12:37:16" ]); The error occurs for any column that is of timestamp type and only when passing value as parameter. What am I doing wrong? Thank you. Regards, Kevork Vartanian This email correspondence may contain privileged information and it is intended to be transmitted to the addressee abovementioned. If you are not the intended recipient of this email correspondence, you must not distribute, copy, forward or rely upon its contents. We ask that you notify the sender of this error and immediately delete this email correspondence.

2 1

MonetDB bug tracker has moved to github
by Sjoerd Mullender 01 Dec '20

01 Dec '20

The MonetDB bug tracker has been moved from our self-hosted bugzilla instance to github issues. All bug IDs have remained the same in the transition, making referencing bugs easier. The new bug tracker can be found at https://github.com/MonetDB/MonetDB/issues Don't forget to follow this tracker (if you're interested in doing that) or follow individual bugs. Due to the way we had to do the move, the old stars that you may have given to the MonetDB github repo have been lost, so please, star it again (or for the first time) if you feel so inclined. The old bugzilla tracker will remain on-line for the time being but entry of new bugs has been turned off. Shortcuts to bugs are forwarded to github. (Shortcuts are URLs in the form of https://www.monetdb.org/bugzilla/<bugid> and https://bugs.monetdb.org/<bugid>.) -- Sjoerd Mullender

1 0

MonetDB bug tracker is going to move
by Sjoerd Mullender 29 Nov '20

29 Nov '20

LS, The MonetDB team wishes to announce the end of our reliance on Bugzilla for bug tracking and enhancement requests. Instead, we switch over to the MonetDB Github issues repo (https://github.com/monetdb/monetdb), which is an hourly based mirror of the Mercurial repository managed at the development group. The move will take place on Friday, November 27, 2020. The actual transfer of the Bugzilla archive into the Github Issues may take a number of hours. A redirect will be in place to send people from Bugzilla towards the MonetDB GitHub repository instead. -- Sjoerd Mullender

1 1

Announcement: New Oct2020-SP1 Bugfix release of MonetDB suite
by Sjoerd Mullender 24 Nov '20

24 Nov '20

The MonetDB team at MonetDB BV is pleased to announce the Oct2020-SP1 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/>. Oct 2020-SP1 bugfix release (11.39.7) Bug Fixes * 6890: Add support of xz/lzma (de)compression on MS Windows * 6891: Add support of lz4 (de)compression on MS Windows * 6971: Parsing table returning function on remote server fails * 6981: Oct2020: PREPARE DDL statement silently fails * 6983: monetdb allows to use non-existing optimizer pipe * 6998: MAL profiler buffer limitations * 7001: crossproduct generated for a simple (semi-)join * 7003: Segfault on large chain of constant decimal multiplication * 7005: Dropping a STREAM TABLE does not remove the associated column info from sys._columns * 7010: deallocate <id> results in all prepared statements being deallocated (not error-related) * 7011: uuid() called only once when used in projection list

1 0

Martin Kersten appointed Knight in the Royal Order of the Netherlands Lion and thanks for your support
by Ying Zhang 20 Nov '20

20 Nov '20

Dear list, Please allow me to proudly share with you the news that Martin Kersten, the founding father of MonetDB, has just been appointed Knight in the Royal Order of the Netherlands Lion [1] as a recognition for his 45+ years contribution to the research, innovation, education and development of database management systems, the results of which have been reflected in MonetDB. However, Martin and the MonetDB team have always been keenly aware that all achievements of Martin&MonetDB wouldn't have been possible without group efforts. So, taking this opportunity, the MonetDB team would like to thank all MonetDB users and contributors through the years for your support! Now, more than ever, the MonetDB team is motivated and determined to make MonetDB even better with every check-in 😀 Best regards, Jennie (a 15+ years MonetDB member and counting :)) [1] https://www.royal-house.nl/topics/decorations-and-honours/personal-decorati…

1 0

Need help using SQuirrel or another Windows SQL client
by marc＠scifinsys.com 19 Nov '20

19 Nov '20

Hi all -- Hopefully someone in this group can help me. :-) I am new to MonetDB and am having a problem setting up the connection for an SQL client. Part of me is wondering if the problem is related to using the latest version of MonetDB (Oct 2020) with this MonetDB JDBC driver (monetdb-jdbc-2.29.jre7.jar). I randomly chose SQuirrel on Windows and am open to alternatives. The connection I am trying to make is to MonetDB on Linux. I followed the instructions carefully at: https://www.monetdb.org/Documentation/ClientInterfaces/SQuirreL 1. From Linux, here is my connection. I have no problems logging in on the host using mclient. marc@HPZ620A: ip address inet 10.102.96.66/24 brd 10.102.96.255 scope global dynamic noprefixroute eno1 marc@HPZ620A:~/tmp/mydbfarm$ mclient -u monetdb -d voc password: Welcome to mclient, the MonetDB/SQL interactive terminal (Oct2020) Database: MonetDB v11.39.5 (Oct2020), 'mapi:monetdb://HPZ620A:50001/voc' sql> 2. Still on Linix, here is the Server Running. marc@HPZ620A: ps -auxw | grep 50001 marc 21727 0.2 0.2 2640864 92616 ? Ssl Nov13 2:50 /usr/bin/mserver5 --dbpath=/home/marc/tmp/mydbfarm/voc --set merovingian_uri mapi:monetdb://HPZ620A:50001/voc --set mapi_listenaddr none --set mapi_usock /home/marc/tmp/mydbfarm/voc/.mapi.sock --set monet_vault_key /home/marc/tmp/mydbfarm/voc/.vaultkey --set gdk_nr_threads 32 --set max_clients 64 --set sql_optimizer default_pipe 3. From Windows, I can ping that server. C:\Users\Admin>ping 10.102.96.66 Pinging 10.102.96.66 with 32 bytes of data: Reply from 10.102.96.66: bytes=32 time=59ms TTL=63 Reply from 10.102.96.66: bytes=32 time=55ms TTL=63 Reply from 10.102.96.66: bytes=32 time=58ms TTL=63 Reply from 10.102.96.66: bytes=32 time=58ms TTL=63 Ping statistics for 10.102.96.66: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 55ms, Maximum = 59ms, Average = 57ms 4. The Squirrel Setup. Note that I did download the jar file from MonetDB, per the instructions. 5. And finally.. The error message when I try to connect! Any suggestions on how I could solve this issue with SQuirrel or another Windows SQL client would be greatly appreciated. Thanks!! --- Marc

4 8