Hi All
I installed pymonetdb v 1.2.1 and trying to connect to remote server MonetDB v11.35.3 (Nov2019) listening on IPV6 only. I have got next error in python client:
>>> mapi_connection.connect(hostname="<server_name>", port=xxxxx, username="monetdb", password="monetdb", database="demo", language="sql", unix_socket=None, connect_timeout=-1)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/lib/python3.7/site-packages/pymonetdb/mapi.py", line 143, in connect
self.socket.connect((hostname, port))
socket.gaierror: [Errno -2] Name or service not known
>>>
My pc client is also using ipv6 to connect to MonetDB server. I also have jdbc connection that works fine.
Question:
Does it mean pymonetdb does not support ipv6 only environment?
What would be the reason if it has nothing to do with protocol?
Thanks
Alex
The MonetDB team at CWI/MonetDB BV is pleased to announce the
Nov2019-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://dev.monetdb.org/downloads/>.
Nov 2019-SP1 bugfix release (11.35.9)
Bug Fixes
* 6723: columns aliases duplicates should not be allowed. automatic
aliasing required.
* 6724: Prepare confuses types when more than one argument is used
* 6726: Python aggregation does not create aggr_group when
aggregating over all rows
* 6765: GRANT SELECT privilege on a subset of table columns results
in access denied error when selecting the same columns from the
table
* 6790: Count distinct giving wrong results
* 6791: str_to_time('11:40', '%H:%M') creates wrong time value
* 6792: JSON path compiler accepts invalid input
* 6793: cast(interval second value to int or decimal) is wrong (by a
factor of 1000), cast(interval month value to decimal or floating
point) fails
* 6794: external name fits.listdir not bound (sys.listdir) Fatal
error during initialization:
* 6796: Incorrect crash time reported by monetdb tool after crash of
mserver5
* 6798: json.text off by one error
* 6804: DNS resolution of 0.0.0.0 fails on recent Ubuntus
Hello,
I had tried changing the password on my monetdb server (MonetDB 5 server
v11.29.3 "Mar2018") but after rebooting it seems I am locked out from
mclient. Is there any way I can change the monetdb user password from
mserver5?
Thank you for your help
Jon
-------- Original Message --------
Subject: starting database 'tpch'... FAILED
Date: 16/12/2019 12:58
From: DEMBELE Simon Pierre <simon-pierre.dembele(a)ensma.fr>
To: mailman-owner(a)monetdb.org
Bonjour, Hello
I need help;
Why can solve this issue
starting database 'tpch'... FAILED
start: starting 'tpch' failed: database 'tpch' has crashed after
starting, manual intervention needed, check monetdbd's logfile
(merovingian.log) for details
Thank
--
Simon
Hi!
I'm still having issue dropping internal tables from the MERGE TABLE. I
used to have this problem on a previous version.
I have created a new DB, imported all the data... and now I need to delete
a partition (NOT a table).
I'm still facing the same problem, which is that I cannot remove it from
the merge table. (as you can see below)..
Is there anything I can do?
Rgds
Ariel
Welcome to mclient, the MonetDB/SQL interactive terminal (Apr2019)
Database: MonetDB v11.33.3 (Apr2019), 'mapi:monetdb://dt-mn:54321/cli_dg'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>ALTER TABLE sb_traf.cub15_cubo DROP TABLE sb_traf.cub8_20190801;
operation successful
sql>ALTER TABLE sb_traf.cub15_cubo DROP TABLE sb_traf.cub8_20190801;
operation successful
sql>ALTER TABLE sb_traf.cub15_cubo DROP TABLE sb_traf.cub8_20190801;
operation successful
sql>ALTER TABLE sb_traf.cub15_cubo DROP TABLE sb_traf.cub8_20190801;
operation successful
sql>ALTER TABLE sb_traf.cub15_cubo DROP TABLE sb_traf.cub8_20190801;
operation successful
sql>ALTER TABLE sb_traf.cub15_cubo DROP TABLE sb_traf.cub8_20190801;
operation successful
sql>ALTER TABLE sb_traf.cub15_cubo DROP TABLE sb_traf.cub8_20190801;
operation successful
sql>ALTER TABLE sb_traf.cub15_cubo DROP TABLE sb_traf.cub8_20190801;
operation successful
Hi!
Im trying to start a new fresh database ..
I am creating with the following commands:
monetdbd create /opt/starbi/mm/
monetdbd start /opt/starbi/mm/
monetdb create cli_dg
monetdb start cli_dg
When I try to start the new database... the database is NOT starting.
starting database 'cli_dg'... FAILED
start: starting 'cli_dg' failed: database 'cli_dg' has crashed after
starting, manual intervention needed, check monetdbd's logfile
(merovingian.log) for details
*Here is the log:*
2019-12-09 15:59:07 MSG cli_dg[385]: # loading sql script: 72_fits.sql
2019-12-09 15:59:07 ERR cli_dg[385]: #main
thread:!ERROR:ParseException:SQLparser:3F000!CREATE PROCEDURE: external
name fits.listdir not bound (sys.listdir)
2019-12-09 15:59:07 ERR cli_dg[385]: ParseException:SQLparser:3F000!CREATE
PROCEDURE: external name fits.listdir not bound (sys.listdir)Fatal error
during initialization:
2019-12-09 15:59:07 ERR cli_dg[385]: ParseException:SQLparser:3F000!CREATE
PROCEDURE: external name fits.listdir not bound (sys.listdir)
2019-12-09 15:59:11 MSG merovingian[370]: database 'cli_dg' (385) has
exited with exit status 1
2019-12-09 15:59:11 ERR control[370]: (local): failed to fork mserver:
database 'cli_dg' has crashed after starting, manual intervention needed,
check monetdbd's logfile (merovingian.log) for details
Can you please help!?
Hi,
The documentation about the LOCKED modifier for COPY INTO mentions:
*When using the LOCKED mode, it is the responsibility of the database user
to make sure that there is currently only a single client
connection accessing the database*
I was assuming (and the syntax suggests, I think) that the LOCKED refers to
the table being copied into, not to the entire database. That is, only that
table is updated without the overhead of logging.
But the documentation imposes the very restrictive condition that only one
connection is active on the database. That seems to suggest that the entire
database is being updated without logging, not only that table.
Could you please clarify? Can I do COPY INTO LOCKED safely with more than
one connection, as long as only 1 connection touches that table?
Roberto