- users-list - monetdb.org

Python module not found on Windows Server 2022 Standard
by minhthanh.tran＠dataforce.de 13 May '25

13 May '25

Hi! Start MonetDB with "C:\Program Files\MonetDB\MonetDB\bin\mserver5.exe" --set embedded_py=true ... CRITICAL: LoaderException:loadLibrary:Loading error failed to open library pyapi3 (from within file 'C:\Program Files\MonetDB\MonetDB\lib\monetdb5\_pyapi3.dll'): The specified module could not be found. Can someone help me solve the issue? Thanks!

1 1

Announcement: New Mar2025 Feature release of MonetDB suite
by Sjoerd Mullender 27 Mar '25

27 Mar '25

The MonetDB Foundation is pleased to announce the Mar2025 feature 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/release-notes/mar2025/>. As usual, the download location is <https://www.monetdb.org/downloads/>. The Mar2025 documentation can be found [here](https://www.monetdb.org/documentation-Mar2025/). ## Mar2025 Feature Release (11.53.3) ### - There is a new shared library called libmutils that contains some utility functions that are used by several programs. - Hot snapshot: allow member files larger than 64 GiB. By member files we mean the files inside the resulting .tar file, not the tar file itself. Huge member files are written using a GNU tar extension to the original tar format, which doesn't support more than 8 GiB. ### Client Package - Support for dumping databases from servers from before Jul2021 (11.41.X) has been removed. ### MonetDB Common - The implementation for the imprints index on numeric columns has been removed. It hasn't been used in years, and when it is enabled, it doesn't really make queries go faster. ### Geom Module - Removed type geometryA (geometry array). It was deprecated in the Jun2023 release (11.47.X) because there was no use for the type. ### MonetDB5 Server - Removed function bat.attach since it wasn't used. - Removed the MAL type "identifier" and supporting functions. There has never been an SQL interface to this type. - Removed the MAL type "color" and supporting functions. There has never been an SQL interface to this type. ### SQL Frontend - Added scalar functions: dayname(d date) and monthname(d date) returns varchar(10). - ranking window functions are now optimized into topn's For the grouped case we added the missing grouped/heap based topn implementation. - Added support for reading external data in a generic way via table returning function: proto_loader(string uri). The uri string value must start with the scheme name, ending with : character. Supported schemes are: monetdb: and odbc:. The monetdb scheme allows you to connect to a remote MonetDB server and retrieve the data of a specific table or view in a specific schema. The uri syntax: monetdb://[<host>[:<port>]]/<database>/<schema>/<table> Example: SELECT * FROM proto_loader('monetdb://127.0.0.1:50000/demo_db/sys/tables'); The odbc scheme allows you to connect to any ODBC data source via an ODBC driver and retrieve the data of a supplied query. The uri syntax: odbc:{{DSN|FILEDSN}=<data source name>|DRIVER=<path_to_driver>}; [<ODBC connection parameters>;]QUERY=<SQL query> For ODBC you normally configure a data source first. This is done using the ODBC administrator (on windows: odbcad32.exe, on linux: odbcinst). Once a data source for a specific ODBC driver has been setup using a unique name, you can reference it as: DSN=my_bigdata; or FILE_DSN=/home/usernm/dsns/my_bigdata.dsn; If you do not want to setup a data source, you can use DRIVER=...; to specify the ODBC driver program to use. However this also means you have to specify all the required connection parameters yourself, such as UID=...;PWD=...;DATABASE=...; etc. The QUERY=<SQL query> part is mandatory and must be specified at the end of the uri string, after the optional ODBC connection parameters. Examples: SELECT * FROM proto_loader( 'odbc:DSN=Postgres;UID=claude;PWD=monet;QUERY=SELECT * FROM customers'); SELECT * FROM proto_loader('odbc:DRIVER=/usr/lib64/libsqlite3odbc.so; Database=/home/martin/sqlite3/chinook.db;QUERY=SELECT * FROM customers'); Note that the 'odbc:' scheme is experimental and not enabled by default. To enable it, the MonetDB server has to be started with argument: --loadmodule odbc_loader - Extended the constant aggregate optimizer in order to eliminate aggregates with constant arguments whenever possible. - REMOTE TABLES and REPLICA TABLES now fully support the monetdb:// and monetdbs:// URL's introduced in Aug2024. Any mapi:monetdb:// URL's are normalized to the new style. - Add function sa_msettings_create() to allocate an msettings object using the arena allocator. - Unused helper function mapiuri_database() has been removed from rel_remote.h. - Added support for aggregates which order within the group such as quantile and which potentially order within the group such as group_concat. The ordering for such operators in now handled once in the relational plan. For this the create function statements can now have an optional order specification, using the keywords 'ORDERED' and 'WITH ORDER'. - Added support for recursive CTE's. - The SQL parser was cleaned up. This resulted in some keywords being used more strictly. If any of these keywords are to be used as column names, they have to be quoted using double quotes: AS, TABLE, COLUMN, DISTINCT, EXEC, EXECUTE. - Introduce the RETURNING clause for INSERT, UPDATE and DELETE statements. Specifying a RETURNING clause causes the SQL statement to return the modified records which can be queried using SELECT like expressions in the RETURNING clause. Aggregate functions are allowed. This is a common non-standard SQL extension. Examples: INSERT INTO foo values (1,10), (-1,-10) RETURNING i+2*j AS bar ---- 21 -21 UPDATE foo SET i = -i WHERE i >0 RETURNING sum(j), count(j) ---- -60|3 - Introduce division_min_scale SQL environment variable for specifying minimum scale of the division result. The default value is 3. ### Bug Fixes - [7101](https://github.com/MonetDB/MonetDB/issues/7101): Feature request: nextafter() in SQL - [7159](https://github.com/MonetDB/MonetDB/issues/7159): CREATE LOCAL TEMPORARY VIEW - [7331](https://github.com/MonetDB/MonetDB/issues/7331): Support RETURNING clause - [7578](https://github.com/MonetDB/MonetDB/issues/7578): explain result in Mal is truncated in large UDFs and their input bats is not shown - [7609](https://github.com/MonetDB/MonetDB/issues/7609): Upgrade 11.49.11 to 11.51.7 issues - [7611](https://github.com/MonetDB/MonetDB/issues/7611): Not possible to create table with multiple composite UNIQUE NULLS NOT DISTINCT constraints - [7614](https://github.com/MonetDB/MonetDB/issues/7614): Filter function creates a cartesian product when used with a view - [7615](https://github.com/MonetDB/MonetDB/issues/7615): Filter function creates a cartesian product when used with a view (2) - [7616](https://github.com/MonetDB/MonetDB/issues/7616): Filter function disappears - [7618](https://github.com/MonetDB/MonetDB/issues/7618): Tables loose their columns - [7619](https://github.com/MonetDB/MonetDB/issues/7619): Resource leak in prepared statements - [7621](https://github.com/MonetDB/MonetDB/issues/7621): crash on aggregate with case statement - [7622](https://github.com/MonetDB/MonetDB/issues/7622): In PREPARE queries with many parameters, information about parameters is truncated when sent to client. - [7623](https://github.com/MonetDB/MonetDB/issues/7623): Database crashed when using UPDATE xxx SET xxx RETURNING xx

1 0

Announcement: New Aug2024-SP2 Bugfix release of MonetDB suite
by Sjoerd Mullender 20 Dec '24

20 Dec '24

The MonetDB Foundation is pleased to announce the Aug2024-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/release-notes/aug2024/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### Bug Fixes - [7112](https://github.com/MonetDB/MonetDB/issues/7112): Need keyboard shortcut to interrupt query execution rather than session - [7205](https://github.com/MonetDB/MonetDB/issues/7205): Unpredictable performance when performing joins over nested queries - [7574](https://github.com/MonetDB/MonetDB/issues/7574): Assertion failure at `rel2bin_select` when using `STARTSWITH` - [7588](https://github.com/MonetDB/MonetDB/issues/7588): incorrect output with single row inputs for var_samp(c) over() - [7589](https://github.com/MonetDB/MonetDB/issues/7589): "SELECT * FROM sessions" crashes monetdb/e - [7593](https://github.com/MonetDB/MonetDB/issues/7593): A value is being returned with unnecessary scientific notation - [7595](https://github.com/MonetDB/MonetDB/issues/7595): SQLTestCase leaks pymonetdb connections - [7597](https://github.com/MonetDB/MonetDB/issues/7597): Upgrade + quick restart causes database inconsistency - [7599](https://github.com/MonetDB/MonetDB/issues/7599): str_to_date fails when combined with SQL CASE clause - [7602](https://github.com/MonetDB/MonetDB/issues/7602): COPY INTO from multiple files causes an assertion error. - [7603](https://github.com/MonetDB/MonetDB/issues/7603): COPY INTO from three or more files crashes the server. - [7604](https://github.com/MonetDB/MonetDB/issues/7604): file_loader() causes server crash when csv file contains too few field separators or contains empty lines - [7607](https://github.com/MonetDB/MonetDB/issues/7607): Adding a column of serial type fails with "Access denied for <user> to schema 'sys'"

1 0

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

05 Nov '24

The MonetDB Foundation is pleased to announce the Aug2024-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/release-notes/aug2024/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### MonetDB5 Server - The server prints out an informative message for the case of a graceful termination. ### SQL Frontend - Improve casting to generic decimal type by choosing a better fit for precision and scale instead of defaulting to 18 and 3, respectively. - When for whatever reason the upgrade code produces an error, we now exit the server. Before the server would limp on with what is basically a broken database. - Improved the violation message of CHECK constraints when violated. It now includes the schema name of the constraint and the check clause. - Increase the buffer size used by hot snapshot from 64kiB to 1MiB, and make it configurable through setting 'hot_snapshot_buffer_size'. It must be a multiple of 512. ### Merovingian - Tweak socket parameters to simulate network activity on client connections. This prevents firewalls from killing connections that seem idle but are actually waiting for a long-running query. Can be controlled with a new 'keepalive' option to monetdbd. ### Bug Fixes - [7281](https://github.com/MonetDB/MonetDB/issues/7281): UDFs defined at compile time in a user schema should not become system functions - [7563](https://github.com/MonetDB/MonetDB/issues/7563): Unexpected result when using `IS DISTINCT FROM` in `VIEW` - [7567](https://github.com/MonetDB/MonetDB/issues/7567): creating remote table from subquery crashes the server - [7569](https://github.com/MonetDB/MonetDB/issues/7569): Column of temporary table changes when another is updated - [7570](https://github.com/MonetDB/MonetDB/issues/7570): BUG in the "str_to_timestamp" function - [7571](https://github.com/MonetDB/MonetDB/issues/7571): Crash when integer overflow in `ORDER BY` - [7572](https://github.com/MonetDB/MonetDB/issues/7572): column max length is not stored as specified and accepted at creation time - [7575](https://github.com/MonetDB/MonetDB/issues/7575): Incorrect BAT properties after mmapped BAT "leaks" to disk with restart. - [7576](https://github.com/MonetDB/MonetDB/issues/7576): unescaping UTF-16 code units goes wrong in json.text - [7577](https://github.com/MonetDB/MonetDB/issues/7577): Crash when using `CHECK` constraint - [7580](https://github.com/MonetDB/MonetDB/issues/7580): statistics optimizer handles date difference incorrectly - [7582](https://github.com/MonetDB/MonetDB/issues/7582): SIGSEGV when creating a SQL function with RETURN CASE WHEN EXISTS (..) - [7583](https://github.com/MonetDB/MonetDB/issues/7583): Query slowdown after deleting rows from large table - [7584](https://github.com/MonetDB/MonetDB/issues/7584): SO_KEEPALIVE should be configured sensibly - [7585](https://github.com/MonetDB/MonetDB/issues/7585): rel2bin_join: Assertion `sql->session->status == -10' failed. - [7587](https://github.com/MonetDB/MonetDB/issues/7587): Line/row numbers get out of sync with COPY INTO .. BEST EFFORT

1 0

The Impact of Gambling: Traditional vs. Online Methods
by Scott Mireles 27 Aug '24

27 Aug '24

Gambling has taken various forms throughout history, from traditional casinos and sports betting to lotteries and poker rooms. Each of these types of gambling offers its unique experiences, whether it be the thrill of spinning a roulette wheel or the anticipation of a card game. Slot machines, blackjack, and bingo are also popular choices, each with its own dedicated following. However, as technology advances, the gambling industry has shifted significantly toward online platforms, making it easier for people to engage in their favorite games from the comfort of their homes. In this evolving landscape, the role of online platforms like lokalno.mk has become increasingly important. They provide valuable information and updates on the latest trends in gambling, guiding players on where and how to engage in various types of gambling. As these online platforms grow, they contribute to a broader understanding of the industry and its environmental implications. One of the most significant developments in this regard is [url=https://lokalno.mk/kako-onlajn-kazinata-mozhat-da-pomognat-vo-zashtita-na-zhivotnata-sredina/]how online casinos reduce environmental damage [/url]. Traditional casinos require vast amounts of energy to operate, from lighting and air conditioning to powering slot machines and maintaining large infrastructures. In contrast, online casinos operate on virtual platforms, significantly reducing the need for physical resources. By eliminating the need for travel, online gambling also reduces carbon emissions associated with transportation. Furthermore, online platforms tend to adopt more sustainable practices, such as using energy-efficient servers and promoting responsible gambling through digital tools. As the world becomes more conscious of environmental issues, the shift towards online gambling represents a positive step in reducing the industry's ecological footprint.

1 0

The Impact of Gambling: Traditional vs. Online Methods
by Scott Mireles 27 Aug '24

27 Aug '24

Gambling has taken various forms throughout history, from traditional casinos and sports betting to lotteries and poker rooms. Each of these types of gambling offers its unique experiences, whether it be the thrill of spinning a roulette wheel or the anticipation of a card game. Slot machines, blackjack, and bingo are also popular choices, each with its own dedicated following. However, as technology advances, the gambling industry has shifted significantly toward online platforms, making it easier for people to engage in their favorite games from the comfort of their homes. In this evolving landscape, the role of online platforms like lokalno.mk has become increasingly important. They provide valuable information and updates on the latest trends in gambling, guiding players on where and how to engage in various types of gambling. As these online platforms grow, they contribute to a broader understanding of the industry and its environmental implications. One of the most significant developments in this regard is [url=https://lokalno.mk/kako-onlajn-kazinata-mozhat-da-pomognat-vo-zashtita-na-zhivotnata-sredina/]how online casinos reduce environmental damage [/url]. Traditional casinos require vast amounts of energy to operate, from lighting and air conditioning to powering slot machines and maintaining large infrastructures. In contrast, online casinos operate on virtual platforms, significantly reducing the need for physical resources. By eliminating the need for travel, online gambling also reduces carbon emissions associated with transportation. Furthermore, online platforms tend to adopt more sustainable practices, such as using energy-efficient servers and promoting responsible gambling through digital tools. As the world becomes more conscious of environmental issues, the shift towards online gambling represents a positive step in reducing the industry's ecological footprint.

1 0

The Impact of Gambling: Traditional vs. Online Methods
by Scott Mireles 27 Aug '24

27 Aug '24

Gambling has taken various forms throughout history, from traditional casinos and sports betting to lotteries and poker rooms. Each of these types of gambling offers its unique experiences, whether it be the thrill of spinning a roulette wheel or the anticipation of a card game. Slot machines, blackjack, and bingo are also popular choices, each with its own dedicated following. However, as technology advances, the gambling industry has shifted significantly toward online platforms, making it easier for people to engage in their favorite games from the comfort of their homes. In this evolving landscape, the role of online platforms like lokalno.mk has become increasingly important. They provide valuable information and updates on the latest trends in gambling, guiding players on where and how to engage in various types of gambling. As these online platforms grow, they contribute to a broader understanding of the industry and its environmental implications. One of the most significant developments in this regard is [url=https://lokalno.mk/kako-onlajn-kazinata-mozhat-da-pomognat-vo-zashtita-na-zhivotnata-sredina/]how online casinos reduce environmental damage [/url]. Traditional casinos require vast amounts of energy to operate, from lighting and air conditioning to powering slot machines and maintaining large infrastructures. In contrast, online casinos operate on virtual platforms, significantly reducing the need for physical resources. By eliminating the need for travel, online gambling also reduces carbon emissions associated with transportation. Furthermore, online platforms tend to adopt more sustainable practices, such as using energy-efficient servers and promoting responsible gambling through digital tools. As the world becomes more conscious of environmental issues, the shift towards online gambling represents a positive step in reducing the industry's ecological footprint.

1 0

The Impact of Gambling: Traditional vs. Online Methods
by Scott Mireles 27 Aug '24

27 Aug '24

Gambling has taken various forms throughout history, from traditional casinos and sports betting to lotteries and poker rooms. Each of these types of gambling offers its unique experiences, whether it be the thrill of spinning a roulette wheel or the anticipation of a card game. Slot machines, blackjack, and bingo are also popular choices, each with its own dedicated following. However, as technology advances, the gambling industry has shifted significantly toward online platforms, making it easier for people to engage in their favorite games from the comfort of their homes. In this evolving landscape, the role of online platforms like lokalno.mk has become increasingly important. They provide valuable information and updates on the latest trends in gambling, guiding players on where and how to engage in various types of gambling. As these online platforms grow, they contribute to a broader understanding of the industry and its environmental implications. One of the most significant developments in this regard is <a href="https://lokalno.mk/kako-onlajn-kazinata-mozhat-da-pomognat-vo-zashtita-na-z…">how online casinos reduce environmental damage </a>. Traditional casinos require vast amounts of energy to operate, from lighting and air conditioning to powering slot machines and maintaining large infrastructures. In contrast, online casinos operate on virtual platforms, significantly reducing the need for physical resources. By eliminating the need for travel, online gambling also reduces carbon emissions associated with transportation. Furthermore, online platforms tend to adopt more sustainable practices, such as using energy-efficient servers and promoting responsible gambling through digital tools. As the world becomes more conscious of environmental issues, the shift towards online gambling represents a positive step in reducing the industry's ecological footprint.

1 0

The Impact of Gambling: Traditional vs. Online Methods
by Scott Mireles 27 Aug '24

27 Aug '24

Gambling has taken various forms throughout history, from traditional casinos and sports betting to lotteries and poker rooms. Each of these types of gambling offers its unique experiences, whether it be the thrill of spinning a roulette wheel or the anticipation of a card game. Slot machines, blackjack, and bingo are also popular choices, each with its own dedicated following. However, as technology advances, the gambling industry has shifted significantly toward online platforms, making it easier for people to engage in their favorite games from the comfort of their homes. In this evolving landscape, the role of online platforms like lokalno.mk has become increasingly important. They provide valuable information and updates on the latest trends in gambling, guiding players on where and how to engage in various types of gambling. As these online platforms grow, they contribute to a broader understanding of the industry and its environmental implications. One of the most significant developments in this regard is <a href="https://lokalno.mk/kako-onlajn-kazinata-mozhat-da-pomognat-vo-zashtita-na-z…">how online casinos reduce environmental damage </a>. Traditional casinos require vast amounts of energy to operate, from lighting and air conditioning to powering slot machines and maintaining large infrastructures. In contrast, online casinos operate on virtual platforms, significantly reducing the need for physical resources. By eliminating the need for travel, online gambling also reduces carbon emissions associated with transportation. Furthermore, online platforms tend to adopt more sustainable practices, such as using energy-efficient servers and promoting responsible gambling through digital tools. As the world becomes more conscious of environmental issues, the shift towards online gambling represents a positive step in reducing the industry's ecological footprint.

1 0

Announcement: New Aug2024 Feature release of MonetDB suite
by Sjoerd Mullender 26 Aug '24

26 Aug '24

The MonetDB Foundation is pleased to announce the Aug2024 feature 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/release-notes/aug2024/>. As usual, the download location is <https://www.monetdb.org/downloads/>. The Aug2024 documentation can be found [here](https://www.monetdb.org/documentation-Aug2024/). ## Aug2024 Feature Release (11.51.3) ### - The CMake configuration files for building extensions have now been included in the various MonetDB development RPMs and debs. - Removed upgrade code for versions before Jul2021. - The shared library (.dll aka .so files) now have the version number as part of the name. This should allow the building of compatibility versions that can be installed in parallel to the latest version. - Some of the Debian/Ubuntu packages have been renamed. The old monetdb5 names have been changed to plain monetdb, and libmonetdb5-server-* packages have been renamed monetdb-*. - The names of some of the provided RPM files have been changed. References to the old MonetDB5 name have been removed. All packages are now just MonetDB. ### Client Package - Msqldump now accepts --output and --outputdir options. When the --outputdir option is used, the dump is placed in the file dump.sql in the specified directory and all tables are dumped to separate CSV files. In this way it is feasible to edit the dump script by hand if needed, even for a large database. - The --table (-t) option of msqldump now accepts SQL-style % wildcard characters to dump all tables that match the pattern. E.g. -t %test%.%test% dumps all tables with 'test' in both the schema and table name. - Implemented interrupt handling in mclient. When using mclient interactively, an interrupt (usually control-C) stops whatever the client is doing. When editing a line, the line is discarded; when editing a second or later line of a query, the whole query is discarded; when a query is being executed, the server is asked to stop the query at its earliest convenience. Stopping a running query can only be done with an up-to-date server. All of this does not work on Windows. ### Mapi Library - Add new columns to sys.sessions. Column 'language' is usually 'sql'. Column 'peer' is the network address of the client (something like '[::1]:46558' or '<UNIX SOCKET>'). Columns 'hostname', 'application', 'client', 'clientpid' and 'remark' can be set by the client. Libmapi/mclient, pymonetdb and monetdb-java have been modified to fill in sensible default values. ### ODBC Driver - Extended ODBC Data Source Setup program on Windows with fields to specify optional Client Information such as Application Name and Client Remark. - Extended ODBC Data Source Setup program on Windows with fields to specify new TLS Connection settings. - Extended ODBC Data Source Setup program on Windows with a Test-button to quickly test connectivity to a MonetDB server. - ODBC now supports TLS. It can be configured through the following DSN- or Connection String attributes (canonical name / user friendly name): TLS / Encrypt = ON/OFF CERT / Server Certificate = PATH CERTHASH / Server Certificate Hash = sha256:HEXDIGITS CLIENTKEY / Client Key = PATH CLIENTCERT / Client Certificate = PATH - Several more connection properties have been made configurable: SCHEMA / Schema = NAME TIMEZONE / Time Zone = Minutes East Of UTC REPLYSIZE / Reply Size = NUMBER LOGFILE / Log File = PATH LOGINTIMEOUT / Login Timeout = MILLISECONDS CONNECTIONTIMEOUT / Connection Timeout = MILLISECONDS AUTOCOMMIT / Autocommit = ON/OFF SOCK / Unix Socket = PATH (unix only) - SQLBrowseConnect() adds On/Off suggestions to boolean settings and prioritizes the DATABASE attribute if it notices monetdbd requires one. Apart from that only UID/User and PWD/Password are required, all others have sensible defaults. ### Stream Library - ICONV support has been removed from the stream library. The server itself only needs UTF-8 support. The client (mclient) does have iconv support. - CURL support has been removed from the stream library. If support is needed, look at the source code in either streamcat.c or mclient.c. ### MonetDB Common - Various changes were made having to do with things like case-insensitive comparisons and converting to upper or lower case. Case insensitive comparison (i.e. the ILIKE operator) uses case folding which is similar to converting to lower case, but changes more characters, also sometimes to multiple characters (e.g. German sharp s (ß) compares equal to SS). - Made some changes to how BAT descriptors are allocated. They are now allocated in bulk, meaning fewer malloc/free calls during processing. - Removed macro BBP_cache and its associated code. Checking whether a BAT is cached (loaded in memory) can be done by checking the BBPLOADED bit in the BBP_status value. Getting a pointer to the BAT descriptor can be done by using BBP_desc. - The SQL transaction ID is no longer saved in the BBP.dir file. - Made some changes to the TIMEOUT macros. Most importantly, they now get a pointer to a QryCtx structure as argument instead of the timeout value. ### SQL Frontend - The "phash" column in the sys.storage() table now indicates whether a hash exists. If the hash is not loaded but there is a hash available on disk, the phash value is "true", but the "hashes" value is 0. - Added execution privilege on all sys.generate_series(first, limit) and sys.generate_series(first, limit, stepsize) functions to public, so all users can now call these table producing generator functions. - Extend CREATE USER MAX_MEMORY and ALTER USER MAX_MEMORY to accept strings of the form '10MiB', '10G', etc. - Extended view sys.sessions and function sys.sessions() with new columns: language, peer, hostname, application, client, clientpid and remark. - All users now have SELECT privilege on view sys.sessions, but non-admin users only see their own sessions. - Added procedure sys.setclientinfo(property string, value string) to allow the client application to set a specific client info property. - Added system table sys.clientinfo_properties that lists the supported client info properties and their associated column name in sys.sessions view. It contains property names: ClientHostname, ApplicationName, ClientLibrary, ClientPid and ClientRemark. - Extended sys.generate_series() to generate dates. Added 2 new functions: sys.generate_series(first date, "limit" date, stepsize interval month) and sys.generate_series(first date, "limit" date, stepsize interval day). - Added support for select exp, count(*) group by 1 order by 1; ie. using numeric references in group by clause. - Added support for GROUP BY ALL. This finds all expressions from the selections which aren't aggregations and groups on those. At least one aggregation must be specified. The ALL keyword can also be replaced by '*', so: GROUP BY *. - Added support for ORDER BY ALL. This orders on all columns of the selection. The ALL keyword can also be replaced by '*', so: ORDER BY *. - Removed the obsolete ANALYZE statement syntax options: SAMPLE nn and MINMAX. Both options have been ignored since release Jan2022. Now they are no longer accepted in the ANALYZE statement. - The ANALYZE statement can now be used in procedures, functions and triggers. - Make schema renaming more permissive. A schema can be renamed if it does not contain objects that are a dependency for objects outside the schema. If such dependencies exist, they are shown in the table sys.dependencies. - Add a DECIMAL AS clause to COPY INTO that configures the decimal separator and thousands separator for decimals, temporal types and floats. - Introduce IS [NOT] DISTINCT FROM syntax. The syntax allows two values to be compared. The comparison always returns boolean FALSE or TRUE never NULL. - SQL2023 feature: Introduce UNIQUE NULLS [NOT] DISTINCT syntax which allows for NULLS to be treated as unique, i.e. a column with this constraint can have one NULL value at most. - SQL2023 feature: Allow project and ORDER BY expressions on UNIQUE constrained columns when the primary key column is used in a GROUP BY expression. ### Bug Fixes - [7045](https://github.com/MonetDB/MonetDB/issues/7045): A value filtered in a subquery finds its way to a later filter in the outer query - [7097](https://github.com/MonetDB/MonetDB/issues/7097): Add an 'ANY' or 'ARBITRARY' aggregate function - [7245](https://github.com/MonetDB/MonetDB/issues/7245): monetdbe silently importing 0 rows, at random - [7265](https://github.com/MonetDB/MonetDB/issues/7265): COPY INTO Not Reading in all records of fixed width delimited file - [7272](https://github.com/MonetDB/MonetDB/issues/7272): Missed rewrite to bulk operators in simple SQL UDF - [7312](https://github.com/MonetDB/MonetDB/issues/7312): Test Button for ODBC Driver - [7332](https://github.com/MonetDB/MonetDB/issues/7332): Support IS [NOT] DISTINCT FROM predicate - [7353](https://github.com/MonetDB/MonetDB/issues/7353): INTERVAL SECOND columns become incorrect when an INTERVAL HOUR column is present - [7367](https://github.com/MonetDB/MonetDB/issues/7367): Libraries linked more than once? - [7370](https://github.com/MonetDB/MonetDB/issues/7370): timestamp_to_str function not aware of timezone - [7374](https://github.com/MonetDB/MonetDB/issues/7374): Different date and time returns - [7392](https://github.com/MonetDB/MonetDB/issues/7392): Evaluate Profile-Guided Optimization - [7424](https://github.com/MonetDB/MonetDB/issues/7424): Performance issue in select-joins - [7459](https://github.com/MonetDB/MonetDB/issues/7459): Crash when using `CONTAINS` in `ORDER BY` clause - [7460](https://github.com/MonetDB/MonetDB/issues/7460): Crash when using `CAST` and `BETWEEN AND` - [7463](https://github.com/MonetDB/MonetDB/issues/7463): Unexpected result when using `CONTAINS` and type casting - [7466](https://github.com/MonetDB/MonetDB/issues/7466): Crash when `INNER JOIN` with `CONTAINS` - [7467](https://github.com/MonetDB/MonetDB/issues/7467): Conversion TIMESTAMPTZ to TIME does not take session TZ into account - [7474](https://github.com/MonetDB/MonetDB/issues/7474): MonetDB server crashes in `VLTgenerator_table_` - [7475](https://github.com/MonetDB/MonetDB/issues/7475): MonetDB server crashes in `__nss_database_lookup` - [7476](https://github.com/MonetDB/MonetDB/issues/7476): MonetDB server crashes in `subrel_bin` - [7477](https://github.com/MonetDB/MonetDB/issues/7477): MonetDB server crashes in `atom_cmp` - [7480](https://github.com/MonetDB/MonetDB/issues/7480): MonetDB server crashes in `get_rel_count` - [7481](https://github.com/MonetDB/MonetDB/issues/7481): MonetDB server crashes in `mvc_row_result_wrap` - [7482](https://github.com/MonetDB/MonetDB/issues/7482): MonetDB server crashes in `bin_find_smallest_column` - [7483](https://github.com/MonetDB/MonetDB/issues/7483): MonetDB server crashes in `rel_get_statistics_` - [7484](https://github.com/MonetDB/MonetDB/issues/7484): MonetDB server crashes in `rel_optimize_projections_` - [7485](https://github.com/MonetDB/MonetDB/issues/7485): MonetDB server crashes in `exp_setalias` - [7486](https://github.com/MonetDB/MonetDB/issues/7486): MonetDB server crashes in `ALGgroupby` - [7488](https://github.com/MonetDB/MonetDB/issues/7488): MonetDB server crashes in `strCmp` - [7497](https://github.com/MonetDB/MonetDB/issues/7497): Multi-column IN clause with value list produces syntax error - [7500](https://github.com/MonetDB/MonetDB/issues/7500): request: ANALYZE statement should be allowed to be used in the body of a procedure or function or trigger. - [7514](https://github.com/MonetDB/MonetDB/issues/7514): Nonexistent window function raises `ParseException:SQLparser:42000!Query too complex: running out of stack space` - [7517](https://github.com/MonetDB/MonetDB/issues/7517): UNLOGGED tables don't get cleaned up properly when DROPped. - [7521](https://github.com/MonetDB/MonetDB/issues/7521): Unexpected result when using `IS DISTINCT FROM` - [7522](https://github.com/MonetDB/MonetDB/issues/7522): Crash when creating view with `HAVING` - [7523](https://github.com/MonetDB/MonetDB/issues/7523): Assertion failure when using `CONTAINS` - [7524](https://github.com/MonetDB/MonetDB/issues/7524): Unexpected error when using `NATURAL RIGHT JOIN` - [7525](https://github.com/MonetDB/MonetDB/issues/7525): Related to bug #7422 (variadic arguments in aggregate UDFs) - [7527](https://github.com/MonetDB/MonetDB/issues/7527): Unexpected result when using `IS DISTINCT FROM` with `RIGHT JOIN` - [7528](https://github.com/MonetDB/MonetDB/issues/7528): Assertion failure when using `JAROWINKLER` in `ORDER BY` clause - [7529](https://github.com/MonetDB/MonetDB/issues/7529): Finding minimum value in reverse sorted column with NULL values at the end gives wrong result. - [7530](https://github.com/MonetDB/MonetDB/issues/7530): Assertion failure when using `JAROWINKLER` with empty string - [7533](https://github.com/MonetDB/MonetDB/issues/7533): DROP of a schema with CASCADE option drops tables, but bats are not removed. - [7534](https://github.com/MonetDB/MonetDB/issues/7534): Unexpected result when using `IS DISTINCT FROM` with `AND` - [7535](https://github.com/MonetDB/MonetDB/issues/7535): Assertion failure when using `GROUP BY` when `CREATE VIEW` - [7538](https://github.com/MonetDB/MonetDB/issues/7538): BUG with decimal values - [7539](https://github.com/MonetDB/MonetDB/issues/7539): Crash when using `IS DISTINCT FROM` with `SIN` - [7540](https://github.com/MonetDB/MonetDB/issues/7540): Assertion failure when using `STARTSWITH` - [7542](https://github.com/MonetDB/MonetDB/issues/7542): Nested query triggers an assert - [7543](https://github.com/MonetDB/MonetDB/issues/7543): Unexpected result when using `IS DISTINCT FROM` with constants - [7544](https://github.com/MonetDB/MonetDB/issues/7544): Unexpected result when using `STARTSWITH` - [7545](https://github.com/MonetDB/MonetDB/issues/7545): Crash when creating view with `GROUP BY` - [7547](https://github.com/MonetDB/MonetDB/issues/7547): drop login trigger causes server crash - [7550](https://github.com/MonetDB/MonetDB/issues/7550): non-admin user can no longer query sys.statistics or information_schema.tables - [7552](https://github.com/MonetDB/MonetDB/issues/7552): Unexpected result when using `NULL` constant in comparison - [7553](https://github.com/MonetDB/MonetDB/issues/7553): Assertion failure when using `INNER JOIN` on `STARTSWITH` - [7554](https://github.com/MonetDB/MonetDB/issues/7554): Unexpected result when using range comparison with `NULL` - [7555](https://github.com/MonetDB/MonetDB/issues/7555): Unexpected result when casting integer to boolean in comparison - [7556](https://github.com/MonetDB/MonetDB/issues/7556): Assertion failure when using `STARTSWITH` with view - [7562](https://github.com/MonetDB/MonetDB/issues/7562): Assertion failure when comparing `INTERVAL` value - [7566](https://github.com/MonetDB/MonetDB/issues/7566): After a while, all new sessions (connections) may get refused

1 0

Maximizing Success with Student Essay Help
by bettyydawson＠gmail.com 24 Aug '24

24 Aug '24

Student essay help is a valuable resource for those who find themselves overwhelmed by the demands of academic writing. Whether it's the pressure of producing high-quality content, meeting tight deadlines, or simply grappling with the intricacies of proper formatting and citation styles, many students find it beneficial to seek expert assistance. Essay help services provide students with the guidance and support they need to navigate the complexities of academic assignments. These services offer various levels of support, from brainstorming ideas and structuring arguments to editing and proofreading drafts. This support ensures that students not only meet their academic requirements but also develop their writing skills over time. To complement the benefits of student essay help, students need to adopt effective time management strategies. One key aspect of managing academic responsibilities is understanding how to make a daily routine for students. A well-structured routine helps students allocate their time efficiently, ensuring that all tasks, including essay writing, research, and revision, are given adequate attention. A daily routine can also incorporate breaks and leisure activities, which are essential for maintaining mental well-being and avoiding burnout. By following a consistent routine, students can develop good habits that contribute to their academic success, such as setting aside regular time slots for studying and completing assignments. In addition to creating a daily routine, students can benefit from using writing https://scamfighter.net/blog/how-to-make-a-daily-schedule-for-students services, which provide expert guidance on essay writing. These services are particularly useful for students who may struggle with writing or lack confidence in their abilities. However, with the multitude of writing services available online, it is crucial to choose a reliable and trustworthy service. This is where a writing service review comes into play. Reading reviews from other students can provide insights into the quality, reliability, and effectiveness of different writing services. Reviews can highlight important factors such as the quality of the work produced, adherence to deadlines, and the level of customer support provided. By taking the time to read and evaluate writing service reviews, students can make informed decisions about which service to use. This ensures that they receive high-quality assistance that meets their academic needs. In conclusion, the combination of student essay help, a well-structured daily routine, and carefully selected writing services can significantly enhance a student's ability to succeed in their academic endeavors. By leveraging these resources, students can improve their writing skills, manage their time effectively, and achieve better academic outcomes, leading to a more successful and fulfilling educational experience.

1 0

Understanding Global Plagiarism and How to Write an Essay
by g2uzmmman1opez＠gmail.com 21 Aug '24

21 Aug '24

Essay writing is a fundamental skill for students and professionals alike, often used to express ideas, analyze concepts, and convey arguments. A well-crafted essay not only demonstrates your understanding of a topic but also your ability to communicate effectively. However, in the realm of essay writing, it's crucial to be aware of issues like plagiarism. Global plagiarism is a significant concern that affects writers worldwide, making it essential to understand and avoid it. Plagiarism is the act of using someone else's work or ideas without proper attribution, presenting them as your own. This unethical practice undermines the integrity of academic and professional writing. In the global context, plagiarism can lead to severe consequences, including legal repercussions and damage to one's reputation. To ensure your work is original and credible, it is vital to understand what constitutes plagiarism and how to avoid it. For more detailed insights into the impact of plagiarism and how it affects the global academic community, you can visit c This resource provides valuable information on how plagiarism is defined, the various forms it can take, and strategies to prevent it. By familiarizing yourself with these aspects, you can better protect your work from being unintentionally compromised. When writing an essay, several key elements should be considered to avoid plagiarism and ensure the originality of your work. First, proper citation is crucial. Whenever you refer to someone else's ideas, research, or direct quotes, make sure to cite the sources accurately according to the required style guide (e.g., APA, MLA, Chicago). This not only gives credit to the original authors but also strengthens the credibility of your essay. Additionally, paraphrasing is an effective technique to avoid plagiarism. Instead of copying text verbatim, rewrite the information in your own words while retaining the original meaning. This demonstrates your understanding of the material and allows you to incorporate it into your essay seamlessly. However, even when paraphrasing, proper citation is still necessary. Another important aspect of writing an essay is creating original content. Start by developing a clear thesis statement that outlines the main argument or purpose of your essay. Conduct thorough research to support your thesis, and use a variety of sources to provide a well-rounded perspective. By synthesizing information from multiple sources and presenting your unique analysis, you contribute original insights to the topic. Organizing your essay effectively is also essential. Structure your essay with a clear introduction, body paragraphs, and conclusion. Each paragraph should focus on a specific point related to your thesis, with evidence and examples to support your arguments. A well-organized essay is easier to follow and demonstrates a logical progression of ideas. In conclusion, essay writing requires careful attention to originality and proper citation practices. Understanding global plagiarism and its implications is vital for maintaining the integrity of your work. By following best practices for citation, paraphrasing, and content creation, you can produce high-quality essays that reflect your own ideas and insights. For further guidance on avoiding plagiarism and ensuring your writing is original, refer to resources like https://speedypaper.com/blog/global-plagiarism Remember, a commitment to ethical writing practices enhances the credibility and impact of your essays.

1 0

A commitment to excellence
by jamesanton2342＠gmail.com 20 Aug '24

20 Aug '24

At the forefront of the IT industry, the Software Development Experts at Progatix Software Company are renowned for their ability to turn complex ideas into innovative and functional software solutions. With a deep understanding of the latest technologies and a commitment to excellence, these experts are the driving force behind Progatix’s success in delivering top-tier software to businesses across various sectors. The Software Development Experts at Progatix are highly skilled in a wide array of programming languages and technologies. This expertise allows them to craft customized software solutions that are both robust and scalable, tailored to meet the specific needs of each client. Whether it's developing a new application from scratch or enhancing an existing system, the Progatix team excels at creating software that aligns perfectly with the unique goals and challenges of businesses in industries such as finance, healthcare, retail, and manufacturing. https://progatix.com/

1 0

A commitment to excellence
by jamesanton2342＠gmail.com 20 Aug '24

20 Aug '24

At the forefront of the IT industry, the Software Development Experts at Progatix Software Company are renowned for their ability to turn complex ideas into innovative and functional software solutions. With a deep understanding of the latest technologies and a commitment to excellence, these experts are the driving force behind Progatix’s success in delivering top-tier software to businesses across various sectors. The Software Development Experts at Progatix are highly skilled in a wide array of programming languages and technologies. This expertise allows them to craft customized software solutions that are both robust and scalable, tailored to meet the specific needs of each client. Whether it's developing a new application from scratch or enhancing an existing system, the Progatix team excels at creating software that aligns perfectly with the unique goals and challenges of businesses in industries such as finance, healthcare, retail, and manufacturing. https://progatix.com/

1 0

Discover the Thrill of Legal Casinos and Exciting Slot Games
by lesliewest238＠gmail.com 17 Aug '24

17 Aug '24

Legal casinos are taking the gaming world by storm, offering a secure, regulated environment where players can enjoy a wide range of casino games and slots. These casinos operate under stringent regulations and licensing authorities to ensure fair play and protect players’ interests. By choosing legal casinos, players not only enjoy a safe gaming experience but also access to top-notch games developed by leading providers in the industry. With the rise of online gaming, legal casinos have evolved to offer a comprehensive suite of games, including classic table games, poker, and slots. Players are drawn to these casinos for the unique blend of entertainment and opportunity to win big. In addition, these casinos provide excellent customer support, robust security measures, and fair gaming practices, making them a preferred choice for millions of players worldwide. One of the standout offerings in legal casinos is the array of slot games available. These games are designed to cater to different preferences, ranging from traditional fruit machines to modern video slots with immersive graphics and engaging themes. Among the popular choices, the https://gamblerguide.org/slots/lady-robin-hood stands out as a captivating option for players seeking adventure and excitement. This slot game is based on the legendary figure of Robin Hood, with a twist that features a female protagonist. The Lady Robin Hood slot offers players a chance to embark on a thrilling journey through the Sherwood Forest, where they can join Lady Robin Hood in her quest to rob from the rich and give to the poor. The game features stunning visuals, a captivating soundtrack, and innovative gameplay mechanics that enhance the overall experience. Players can expect to find exciting features such as free spins, wild symbols, and bonus rounds that add an extra layer of excitement to the game. One of the reasons why the Lady Robin Hood slot is so popular among players is its unique theme and engaging storyline. The game transports players to a world of medieval adventure, where they can explore the forest, outsmart the sheriff’s men, and uncover hidden treasures. The game’s design is visually appealing, with detailed graphics that bring the characters and setting to life. The soundtrack complements the theme, immersing players in the atmosphere of the game and enhancing the overall gaming experience. In addition to the exciting gameplay and captivating theme, the Lady Robin Hood slot offers players the chance to win big. The game features multiple paylines, and players can choose their bet size and number of lines to play. With the right combination of symbols, players can trigger bonus rounds and free spins that increase their chances of hitting the jackpot. The game’s high payout potential and exciting features make it a popular choice among both new and experienced players. In conclusion, legal casinos provide a safe and enjoyable gaming environment for players to explore a wide range of games, including slots like the Lady Robin Hood slot. With its unique theme, engaging gameplay, and exciting features, this slot game offers players a chance to experience the thrill of adventure and win big rewards. Whether you are a seasoned player or new to the world of online gaming, the Lady Robin Hood slot is a must-try game that promises hours of entertainment and excitement.

2 1

[MonetDB-users] Books CDs
by CHARTS LICENSING 11 Aug '24

11 Aug '24

Everything you want to know this dynamic artist check. At blueberry hills duck, roomfull story gtgt getting. Intriguing, life in biography. Here music looking for lyrics maybe, youre find which! Download free wallpapers featuring business cmg worldwide is exclusive. Videos latest products been easier. Exclusive estate we consider request use name voice, image. List covered berries charts licensing message! Reelin and rockin about, has everything you? Many exciting, photos him stage click! Artist check, out some quotes read all intriguing. It alive he, did on occasion birthday wednesday? Has everything you want to know this? Quotes read all intriguing life, in biography or. Gtgt getting licks years reelin and. Click here, music looking for lyrics maybe, youre. News celebrates his th rock will never! Chuck berry news celebrates his th rock, will. Browse through many exciting, photos him stage click here. He did on occasion birthday wednesday night at blueberry. Wallpapers featuring business cmg worldwide. Worldwide is exclusive estate we consider, request use name. Want to know this dynamic artist check out. Awards fast, facts clips list covered. Music looking for lyrics maybe youre. Message board downloads tour dates fan, club inquiries. Other sites, download free wallpapers featuring, business cmg worldwide. Request use, name, voice.

2 1

Multi-column update based on joined table
by Lee Hachadoorian 11 Aug '24

11 Aug '24

I need to update multiple columns (~250) from one table to another based on a two-column key. In Postgres I would write this using the FROM clause, but since MonetDB doesn't support the FROM clause, I've successfully updated one column with: UPDATE census.acs2010_5yr SET b07401001 = ( SELECT CAST(b07401001 AS int) FROM acs2010_5yr.tmp_seq0001 WHERE acs2010_5yr.stusab = tmp_seq0001.stusab AND acs2010_5yr.logrecno = tmp_seq0001.logrecno ); My question is whether there is any benefit to writing a multiple column update into a single UPDATE statement: UPDATE target_table SET column1 = (SELECT column1 FROM source_table WHERE target_table.key = source_table.key), column2 = (SELECT column2 FROM source_table WHERE target_table.key = source_table.key), ..., columnN = (SELECT columnN FROM source_table WHERE target_table.key = source_table.key); On Postgres I believe the multi-column update using a table join would only have to do the sequential scan of each table once, but with the necessity of sub-selects in MonetDB, what is the backend doing? Is it already doing an index scan once for each row in the single column case, then doing it once for each row * column in the multi-column case? Best, --Lee -- Lee Hachadoorian Asst Professor of Geography, Dartmouth College http://freecity.commons.gc.cuny.edu/

3 3

Announcement: New Dec2023-SP4 Bugfix release of MonetDB suite
by Sjoerd Mullender 09 Jul '24

09 Jul '24

The MonetDB Foundation is pleased to announce the Dec2023-SP4 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/release-notes/dec2023/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### MonetDB5 Server - The mserver5 program has a new option: --without-geom. If the server was compiled with geom support (or the geom module was installed in a binary distribution), this option allows the server to start without the geom module, so that it can proceed with a database that was created without geom. ### SQL Frontend - When sys.persist_unlogged is called for a table, it may return that zero rows were persisted. If this is because the call was done too early, i.e. the table was recently created and the write-ahead log where this was logged has not been processed yet, the call will request an immediate write-ahead log rotation. This means that the WAL will be processed as soon as possible and a new call to sys.persist_unlogged soon after will likely return a positive result. ### Bug Fixes - [7509](https://github.com/MonetDB/MonetDB/issues/7509): MonetDB Dec2023-SP2 crashes at `sql_init_subtype` - [7511](https://github.com/MonetDB/MonetDB/issues/7511): MonetDB Dec2023-SP2 crashes with the `PASSWORD_HASH` function - [7512](https://github.com/MonetDB/MonetDB/issues/7512): MonetDB Dec2023-SP2 crashes with the `GET_MERGE_TABLE_PARTITION_EXPRESSIONS` function - [7513](https://github.com/MonetDB/MonetDB/issues/7513): MonetDB Dec2023-SP2 crashes with the `GETHOST` function - [7518](https://github.com/MonetDB/MonetDB/issues/7518): mserver reports errors when starting if geom module is enabled but database was created without - [7526](https://github.com/MonetDB/MonetDB/issues/7526): deadlock, causing new connections to hang indefinitely - [7531](https://github.com/MonetDB/MonetDB/issues/7531): loading more than 2147483647 rows gives issue. - [7536](https://github.com/MonetDB/MonetDB/issues/7536): Truncated file when dumping a table from mclient into a gzipped file - [7537](https://github.com/MonetDB/MonetDB/issues/7537): MonetDB crashes with a SIGSEGV due to a null pointer dereference when using prepared statements - [7541](https://github.com/MonetDB/MonetDB/issues/7541): Unexpected result when using `LEVENSHTEIN` - [7546](https://github.com/MonetDB/MonetDB/issues/7546): monetdbd leaks file descriptors when starting mserver5.

1 0

[MonetDB-users] XQuery API and XLink/XUpdate support
by Alexandra Mart�nez 27 Jun '24

27 Jun '24

Hello all, I was wondering if there is any documentation about the API for XQuery (i.e., how to write xqueries from a Java program). Also, I am interested in using some features of XLink and XUpdate on top of my XML database. Is support for any of these in progress? Thanks in advance, Alexandra ______________________________________________________ Click here to donate to the Hurricane Katrina relief effort. http://store.yahoo.com/redcross-donate3/

4 3

Enhancing Nursing Education: The Comprehensive Guide to BSN Writing Services
by noheta1148＠morxin.com 27 Jun '24

27 Jun '24

Enhancing Nursing Education: The Comprehensive Guide to BSN Writing Services Introduction The Bachelor of Science in Nursing (BSN) program is a rigorous academic pathway BSN Writing Services that prepares students for diverse roles in healthcare. Aspiring nurses undergo extensive training in nursing theory, clinical practice, and healthcare management. Integral to their academic journey are various writing assignments that hone critical thinking, research skills, and the ability to communicate effectively. BSN writing services play a crucial role in supporting students through these academic demands, offering specialized assistance that enhances learning outcomes and prepares them for successful careers in nursing. Understanding BSN Writing Services BSN writing services cater specifically to the needs of nursing students, providing expert guidance and support across a range of academic writing tasks. These services are staffed by professionals with backgrounds in nursing, healthcare, and academic writing, ensuring that students receive accurate, well-researched, and meticulously crafted assignments. Common types of writing assistance provided by BSN writing services include: Research Papers: Investigating and analyzing healthcare issues, nursing theories, and evidence-based practices. Literature Reviews: Synthesizing existing research literature to identify gaps, trends, and advancements in nursing practice. Case Studies: Analyzing patient scenarios, applying nursing theories, and proposing appropriate care interventions. Care Plans: Developing comprehensive care plans based on nursing assessments and evidence-based guidelines. Reflective Journals: Documenting personal insights and reflections on clinical experiences, ethical dilemmas, and professional growth. Presentations and Projects: Creating informative presentations and capella 4900 assessment 3 collaborative projects that demonstrate knowledge integration and teamwork skills. Benefits of BSN Writing Services Expertise and Specialization: BSN writing services employ writers with advanced degrees in nursing and healthcare. These professionals possess in-depth knowledge of nursing theories, clinical practices, and research methodologies, ensuring that assignments are accurate, relevant, and aligned with academic standards. Customized Support: Each student receives personalized assistance tailored to their specific academic needs. Whether it's refining a research topic, structuring a literature review, or formatting a care plan, BSN writing services help students enhance the clarity, coherence, and academic rigor of their assignments. Time Management: Nursing students often juggle multiple responsibilities, including coursework, clinical rotations, and personal commitments. BSN writing services assist in managing time effectively by taking on writing tasks, allowing students to focus on their studies and clinical practice without compromising the quality of their academic work. Improved Academic Performance: High-quality writing services contribute to better academic outcomes by showcasing students' understanding of nursing concepts, critical thinking skills, and ability to apply evidence-based practices. Well-crafted assignments receive higher grades, boosting students' confidence and overall academic standing. Skill Development: Collaborating with professional writers helps students improve their own writing skills. They learn effective research techniques, how to structure arguments logically, and the importance of using evidence to support their conclusions. These skills are essential for both academic success and professional practice in nursing. Ethical Considerations in Using BSN Writing Services While BSN writing services offer valuable support, ethical considerations are capella 4020 assessment 4 paramount to ensure academic integrity and responsible use: Originality: Students must ensure that all work submitted is original and properly cited to avoid plagiarism. BSN writing services should provide plagiarism-free content and emphasize the importance of academic honesty. Learning Enhancement: Writing services should be viewed as learning aids that supplement students' understanding and mastery of nursing concepts. Students are encouraged to actively engage with the material provided, ask questions, and integrate new knowledge into their academic journey. Collaborative Learning: Effective use of BSN writing services involves collaboration between students and professional writers. Students should review and understand the content provided, participate in discussions about their assignments, and use the feedback to improve their writing and critical thinking skills. Case Study: Impact of BSN Writing Services on Student Success Consider the case of Sarah, a third-year BSN student who struggled with writing a comprehensive care plan for a complex patient case study. Despite her clinical competence, Sarah found it challenging to articulate her assessment findings, develop appropriate nursing interventions, and justify her care decisions based on evidence-based practices. Sarah sought assistance from a reputable BSN writing service, providing the details of her patient case study, assessment data, and initial care plan draft. The writing service assigned a professional writer with expertise in nursing care plans to collaborate capella 4030 assessment 4 with Sarah. Together, they reviewed the patient's medical history, identified priority nursing diagnoses, and integrated evidence-based interventions into the care plan. Throughout the collaboration, Sarah actively participated in discussions with the writer, asking questions about care plan development, rationale for interventions, and best practices in nursing documentation. The writer provided valuable feedback on Sarah's draft, suggesting revisions to enhance clarity, specificity, and alignment with nursing standards. As a result of this collaboration, Sarah submitted a well-structured and evidence-based care plan that received praise from her instructor. The experience not only improved Sarah's understanding of care planning principles but also boosted her confidence in applying theoretical knowledge to clinical practice. Sarah credits the writing service for helping her achieve academic success while developing essential skills for her future career as a nurse. Conclusion BSN writing services play a vital role in supporting nursing students through their academic journey, enhancing learning outcomes, and preparing them for professional practice in healthcare. By providing expertise, personalized support, and promoting ethical academic practices, these services empower students to excel in their studies and contribute meaningfully to the field of nursing. As the healthcare landscape evolves, the demand for highly skilled and knowledgeable nurses continues to grow. BSN writing services, through their commitment to excellence and student-centered support, ensure that graduates are well-prepared to meet the challenges of modern healthcare and make significant contributions to patient care and nursing practice. In summary, BSN writing services are invaluable resources that enable nursing students to navigate the complexities of academic writing, enhance their learning experience, and develop critical skills necessary for success in their careers as healthcare professionals.

1 0

Enhancing Nursing Education: The Comprehensive Guide to BSN Writing Services
by noheta1148＠morxin.com 27 Jun '24

27 Jun '24

Enhancing Nursing Education: The Comprehensive Guide to BSN Writing Services Introduction The Bachelor of Science in Nursing (BSN) program is a rigorous academic pathway BSN Writing Services that prepares students for diverse roles in healthcare. Aspiring nurses undergo extensive training in nursing theory, clinical practice, and healthcare management. Integral to their academic journey are various writing assignments that hone critical thinking, research skills, and the ability to communicate effectively. BSN writing services play a crucial role in supporting students through these academic demands, offering specialized assistance that enhances learning outcomes and prepares them for successful careers in nursing. Understanding BSN Writing Services BSN writing services cater specifically to the needs of nursing students, providing expert guidance and support across a range of academic writing tasks. These services are staffed by professionals with backgrounds in nursing, healthcare, and academic writing, ensuring that students receive accurate, well-researched, and meticulously crafted assignments. Common types of writing assistance provided by BSN writing services include: Research Papers: Investigating and analyzing healthcare issues, nursing theories, and evidence-based practices. Literature Reviews: Synthesizing existing research literature to identify gaps, trends, and advancements in nursing practice. Case Studies: Analyzing patient scenarios, applying nursing theories, and proposing appropriate care interventions. Care Plans: Developing comprehensive care plans based on nursing assessments and evidence-based guidelines. Reflective Journals: Documenting personal insights and reflections on clinical experiences, ethical dilemmas, and professional growth. Presentations and Projects: Creating informative presentations and capella 4900 assessment 3 collaborative projects that demonstrate knowledge integration and teamwork skills. Benefits of BSN Writing Services Expertise and Specialization: BSN writing services employ writers with advanced degrees in nursing and healthcare. These professionals possess in-depth knowledge of nursing theories, clinical practices, and research methodologies, ensuring that assignments are accurate, relevant, and aligned with academic standards. Customized Support: Each student receives personalized assistance tailored to their specific academic needs. Whether it's refining a research topic, structuring a literature review, or formatting a care plan, BSN writing services help students enhance the clarity, coherence, and academic rigor of their assignments. Time Management: Nursing students often juggle multiple responsibilities, including coursework, clinical rotations, and personal commitments. BSN writing services assist in managing time effectively by taking on writing tasks, allowing students to focus on their studies and clinical practice without compromising the quality of their academic work. Improved Academic Performance: High-quality writing services contribute to better academic outcomes by showcasing students' understanding of nursing concepts, critical thinking skills, and ability to apply evidence-based practices. Well-crafted assignments receive higher grades, boosting students' confidence and overall academic standing. Skill Development: Collaborating with professional writers helps students improve their own writing skills. They learn effective research techniques, how to structure arguments logically, and the importance of using evidence to support their conclusions. These skills are essential for both academic success and professional practice in nursing. Ethical Considerations in Using BSN Writing Services While BSN writing services offer valuable support, ethical considerations are capella 4020 assessment 4 paramount to ensure academic integrity and responsible use: Originality: Students must ensure that all work submitted is original and properly cited to avoid plagiarism. BSN writing services should provide plagiarism-free content and emphasize the importance of academic honesty. Learning Enhancement: Writing services should be viewed as learning aids that supplement students' understanding and mastery of nursing concepts. Students are encouraged to actively engage with the material provided, ask questions, and integrate new knowledge into their academic journey. Collaborative Learning: Effective use of BSN writing services involves collaboration between students and professional writers. Students should review and understand the content provided, participate in discussions about their assignments, and use the feedback to improve their writing and critical thinking skills. Case Study: Impact of BSN Writing Services on Student Success Consider the case of Sarah, a third-year BSN student who struggled with writing a comprehensive care plan for a complex patient case study. Despite her clinical competence, Sarah found it challenging to articulate her assessment findings, develop appropriate nursing interventions, and justify her care decisions based on evidence-based practices. Sarah sought assistance from a reputable BSN writing service, providing the details of her patient case study, assessment data, and initial care plan draft. The writing service assigned a professional writer with expertise in nursing care plans to collaborate capella 4030 assessment 4 with Sarah. Together, they reviewed the patient's medical history, identified priority nursing diagnoses, and integrated evidence-based interventions into the care plan. Throughout the collaboration, Sarah actively participated in discussions with the writer, asking questions about care plan development, rationale for interventions, and best practices in nursing documentation. The writer provided valuable feedback on Sarah's draft, suggesting revisions to enhance clarity, specificity, and alignment with nursing standards. As a result of this collaboration, Sarah submitted a well-structured and evidence-based care plan that received praise from her instructor. The experience not only improved Sarah's understanding of care planning principles but also boosted her confidence in applying theoretical knowledge to clinical practice. Sarah credits the writing service for helping her achieve academic success while developing essential skills for her future career as a nurse. Conclusion BSN writing services play a vital role in supporting nursing students through their academic journey, enhancing learning outcomes, and preparing them for professional practice in healthcare. By providing expertise, personalized support, and promoting ethical academic practices, these services empower students to excel in their studies and contribute meaningfully to the field of nursing. As the healthcare landscape evolves, the demand for highly skilled and knowledgeable nurses continues to grow. BSN writing services, through their commitment to excellence and student-centered support, ensure that graduates are well-prepared to meet the challenges of modern healthcare and make significant contributions to patient care and nursing practice. In summary, BSN writing services are invaluable resources that enable nursing students to navigate the complexities of academic writing, enhance their learning experience, and develop critical skills necessary for success in their careers as healthcare professionals.

1 0

Enhancing Nursing Education: The Comprehensive Guide to BSN Writing Services
by noheta1148＠morxin.com 27 Jun '24

27 Jun '24

[b]Enhancing Nursing Education: The Comprehensive Guide to BSN Writing Services[/b] [b]Introduction[/b] The Bachelor of Science in Nursing (BSN) program is a rigorous academic pathway [url=https://bsnwritingservices.com/]BSN Writing Services[/url] that prepares students for diverse roles in healthcare. Aspiring nurses undergo extensive training in nursing theory, clinical practice, and healthcare management. Integral to their academic journey are various writing assignments that hone critical thinking, research skills, and the ability to communicate effectively. BSN writing services play a crucial role in supporting students through these academic demands, offering specialized assistance that enhances learning outcomes and prepares them for successful careers in nursing. [b]Understanding BSN Writing Services[/b] BSN writing services cater specifically to the needs of nursing students, providing expert guidance and support across a range of academic writing tasks. These services are staffed by professionals with backgrounds in nursing, healthcare, and academic writing, ensuring that students receive accurate, well-researched, and meticulously crafted assignments. Common types of writing assistance provided by BSN writing services include: [list=1] [*] [b]Research Papers[/b]: Investigating and analyzing healthcare issues, nursing theories, and evidence-based practices. [*] [b]Literature Reviews[/b]: Synthesizing existing research literature to identify gaps, trends, and advancements in nursing practice. [*] [b]Case Studies[/b]: Analyzing patient scenarios, applying nursing theories, and proposing appropriate care interventions. [*] [b]Care Plans[/b]: Developing comprehensive care plans based on nursing assessments and evidence-based guidelines. [*] [b]Reflective Journals[/b]: Documenting personal insights and reflections on clinical experiences, ethical dilemmas, and professional growth. [*] [b]Presentations and Projects[/b]: Creating informative presentations and [url=https://bsnwritingservices.com/capella-4900-assessment-3/]capella 4900 assessment 3[/url] collaborative projects that demonstrate knowledge integration and teamwork skills. [/list] [b]Benefits of BSN Writing Services[/b] [list=1] [*] [b]Expertise and Specialization[/b]: BSN writing services employ writers with advanced degrees in nursing and healthcare. These professionals possess in-depth knowledge of nursing theories, clinical practices, and research methodologies, ensuring that assignments are accurate, relevant, and aligned with academic standards. [*] [b]Customized Support[/b]: Each student receives personalized assistance tailored to their specific academic needs. Whether it's refining a research topic, structuring a literature review, or formatting a care plan, BSN writing services help students enhance the clarity, coherence, and academic rigor of their assignments. [*] [b]Time Management[/b]: Nursing students often juggle multiple responsibilities, including coursework, clinical rotations, and personal commitments. BSN writing services assist in managing time effectively by taking on writing tasks, allowing students to focus on their studies and clinical practice without compromising the quality of their academic work. [*] [b]Improved Academic Performance[/b]: High-quality writing services contribute to better academic outcomes by showcasing students' understanding of nursing concepts, critical thinking skills, and ability to apply evidence-based practices. Well-crafted assignments receive higher grades, boosting students' confidence and overall academic standing. [*] [b]Skill Development[/b]: Collaborating with professional writers helps students improve their own writing skills. They learn effective research techniques, how to structure arguments logically, and the importance of using evidence to support their conclusions. These skills are essential for both academic success and professional practice in nursing. [/list] [b]Ethical Considerations in Using BSN Writing Services[/b] While BSN writing services offer valuable support, ethical considerations are [url=https://bsnwritingservices.com/capella-4020-assessment-4/]capella 4020 assessment 4[/url] paramount to ensure academic integrity and responsible use: [list=1] [*] [b]Originality[/b]: Students must ensure that all work submitted is original and properly cited to avoid plagiarism. BSN writing services should provide plagiarism-free content and emphasize the importance of academic honesty. [*] [b]Learning Enhancement[/b]: Writing services should be viewed as learning aids that supplement students' understanding and mastery of nursing concepts. Students are encouraged to actively engage with the material provided, ask questions, and integrate new knowledge into their academic journey. [*] [b]Collaborative Learning[/b]: Effective use of BSN writing services involves collaboration between students and professional writers. Students should review and understand the content provided, participate in discussions about their assignments, and use the feedback to improve their writing and critical thinking skills. [/list] [b]Case Study: Impact of BSN Writing Services on Student Success[/b] Consider the case of Sarah, a third-year BSN student who struggled with writing a comprehensive care plan for a complex patient case study. Despite her clinical competence, Sarah found it challenging to articulate her assessment findings, develop appropriate nursing interventions, and justify her care decisions based on evidence-based practices. Sarah sought assistance from a reputable BSN writing service, providing the details of her patient case study, assessment data, and initial care plan draft. The writing service assigned a professional writer with expertise in nursing care plans to collaborate [url=https://bsnwritingservices.com/capella-4030-assessment-4/]capella 4030 assessment 4[/url] with Sarah. Together, they reviewed the patient's medical history, identified priority nursing diagnoses, and integrated evidence-based interventions into the care plan. Throughout the collaboration, Sarah actively participated in discussions with the writer, asking questions about care plan development, rationale for interventions, and best practices in nursing documentation. The writer provided valuable feedback on Sarah's draft, suggesting revisions to enhance clarity, specificity, and alignment with nursing standards. As a result of this collaboration, Sarah submitted a well-structured and evidence-based care plan that received praise from her instructor. The experience not only improved Sarah's understanding of care planning principles but also boosted her confidence in applying theoretical knowledge to clinical practice. Sarah credits the writing service for helping her achieve academic success while developing essential skills for her future career as a nurse. [b]Conclusion[/b] BSN writing services play a vital role in supporting nursing students through their academic journey, enhancing learning outcomes, and preparing them for professional practice in healthcare. By providing expertise, personalized support, and promoting ethical academic practices, these services empower students to excel in their studies and contribute meaningfully to the field of nursing. As the healthcare landscape evolves, the demand for highly skilled and knowledgeable nurses continues to grow. BSN writing services, through their commitment to excellence and student-centered support, ensure that graduates are well-prepared to meet the challenges of modern healthcare and make significant contributions to patient care and nursing practice. In summary, BSN writing services are invaluable resources that enable nursing students to navigate the complexities of academic writing, enhance their learning experience, and develop critical skills necessary for success in their careers as healthcare professionals.

1 0

Enhancing Nursing Education: The Comprehensive Guide to BSN Writing Services
by noheta1148＠morxin.com 27 Jun '24

27 Jun '24

<p> </p> <div class="flex-1 overflow-hidden"> <div class="h-full"> <div class="react-scroll-to-bottom--css-yjxxw-79elbk h-full"> <div class="react-scroll-to-bottom--css-yjxxw-1n7m0yu"> <div class="flex flex-col text-sm md:pb-9"> <div class="w-full text-token-text-primary" dir="auto" data-testid="conversation-turn-27" data-scroll-anchor="true"> <div class="py-2 juice:py-[18px] px-3 text-base md:px-4 m-auto md:px-5 lg:px-1 xl:px-5"> <div class="mx-auto flex flex-1 gap-3 text-base juice:gap-4 juice:md:gap-5 juice:lg:gap-6 md:max-w-3xl lg:max-w-[40rem] xl:max-w-[48rem]"> <div class="group/conversation-turn relative flex w-full min-w-0 flex-col agent-turn"> <div class="flex-col gap-1 md:gap-3"> <div class="flex flex-grow flex-col max-w-full"> <div class="min-h-[20px] text-message flex flex-col items-start whitespace-pre-wrap break-words [.text-message+&]:mt-5 juice:w-full juice:items-end overflow-x-auto gap-2" dir="auto" data-message-author-role="assistant" data-message-id="75d752ad-4671-4620-8b78-11346b44109d"> <div class="flex w-full flex-col gap-1 juice:empty:hidden juice:first:pt-[3px]"> <div class="markdown prose w-full break-words dark:prose-invert light"> <h3>Enhancing Nursing Education: The Comprehensive Guide to BSN Writing Services</h3> <h4>Introduction</h4> <p>The Bachelor of Science in Nursing (BSN) program is a rigorous academic pathway <a href="https://bsnwritingservices.com/">BSN Writing Services</a> that prepares students for diverse roles in healthcare. Aspiring nurses undergo extensive training in nursing theory, clinical practice, and healthcare management. Integral to their academic journey are various writing assignments that hone critical thinking, research skills, and the ability to communicate effectively. BSN writing services play a crucial role in supporting students through these academic demands, offering specialized assistance that enhances learning outcomes and prepares them for successful careers in nursing.</p> <h4>Understanding BSN Writing Services</h4> <p>BSN writing services cater specifically to the needs of nursing students, providing expert guidance and support across a range of academic writing tasks. These services are staffed by professionals with backgrounds in nursing, healthcare, and academic writing, ensuring that students receive accurate, well-researched, and meticulously crafted assignments. Common types of writing assistance provided by BSN writing services include:</p> <ol> <li> <p><strong>Research Papers</strong>: Investigating and analyzing healthcare issues, nursing theories, and evidence-based practices.</p> </li> <li> <p><strong>Literature Reviews</strong>: Synthesizing existing research literature to identify gaps, trends, and advancements in nursing practice.</p> </li> <li> <p><strong>Case Studies</strong>: Analyzing patient scenarios, applying nursing theories, and proposing appropriate care interventions.</p> </li> <li> <p><strong>Care Plans</strong>: Developing comprehensive care plans based on nursing assessments and evidence-based guidelines.</p> </li> <li> <p><strong>Reflective Journals</strong>: Documenting personal insights and reflections on clinical experiences, ethical dilemmas, and professional growth.</p> </li> <li> <p><strong>Presentations and Projects</strong>: Creating informative presentations and <a href="https://bsnwritingservices.com/capella-4900-assessment-3/">capella 4900 assessment 3</a> collaborative projects that demonstrate knowledge integration and teamwork skills.</p> </li> </ol> <h4>Benefits of BSN Writing Services</h4> <ol> <li> <p><strong>Expertise and Specialization</strong>: BSN writing services employ writers with advanced degrees in nursing and healthcare. These professionals possess in-depth knowledge of nursing theories, clinical practices, and research methodologies, ensuring that assignments are accurate, relevant, and aligned with academic standards.</p> </li> <li> <p><strong>Customized Support</strong>: Each student receives personalized assistance tailored to their specific academic needs. Whether it's refining a research topic, structuring a literature review, or formatting a care plan, BSN writing services help students enhance the clarity, coherence, and academic rigor of their assignments.</p> </li> <li> <p><strong>Time Management</strong>: Nursing students often juggle multiple responsibilities, including coursework, clinical rotations, and personal commitments. BSN writing services assist in managing time effectively by taking on writing tasks, allowing students to focus on their studies and clinical practice without compromising the quality of their academic work.</p> </li> <li> <p><strong>Improved Academic Performance</strong>: High-quality writing services contribute to better academic outcomes by showcasing students' understanding of nursing concepts, critical thinking skills, and ability to apply evidence-based practices. Well-crafted assignments receive higher grades, boosting students' confidence and overall academic standing.</p> </li> <li> <p><strong>Skill Development</strong>: Collaborating with professional writers helps students improve their own writing skills. They learn effective research techniques, how to structure arguments logically, and the importance of using evidence to support their conclusions. These skills are essential for both academic success and professional practice in nursing.</p> </li> </ol> <h4>Ethical Considerations in Using BSN Writing Services</h4> <p>While BSN writing services offer valuable support, ethical considerations are <a href="https://bsnwritingservices.com/capella-4020-assessment-4/">capella 4020 assessment 4</a> paramount to ensure academic integrity and responsible use:</p> <ol> <li> <p><strong>Originality</strong>: Students must ensure that all work submitted is original and properly cited to avoid plagiarism. BSN writing services should provide plagiarism-free content and emphasize the importance of academic honesty.</p> </li> <li> <p><strong>Learning Enhancement</strong>: Writing services should be viewed as learning aids that supplement students' understanding and mastery of nursing concepts. Students are encouraged to actively engage with the material provided, ask questions, and integrate new knowledge into their academic journey.</p> </li> <li> <p><strong>Collaborative Learning</strong>: Effective use of BSN writing services involves collaboration between students and professional writers. Students should review and understand the content provided, participate in discussions about their assignments, and use the feedback to improve their writing and critical thinking skills.</p> </li> </ol> <h4>Case Study: Impact of BSN Writing Services on Student Success</h4> <p>Consider the case of Sarah, a third-year BSN student who struggled with writing a comprehensive care plan for a complex patient case study. Despite her clinical competence, Sarah found it challenging to articulate her assessment findings, develop appropriate nursing interventions, and justify her care decisions based on evidence-based practices.</p> <p>Sarah sought assistance from a reputable BSN writing service, providing the details of her patient case study, assessment data, and initial care plan draft. The writing service assigned a professional writer with expertise in nursing care plans to collaborate <a href="https://bsnwritingservices.com/capella-4030-assessment-4/">capella 4030 assessment 4</a> with Sarah. Together, they reviewed the patient's medical history, identified priority nursing diagnoses, and integrated evidence-based interventions into the care plan.</p> <p>Throughout the collaboration, Sarah actively participated in discussions with the writer, asking questions about care plan development, rationale for interventions, and best practices in nursing documentation. The writer provided valuable feedback on Sarah's draft, suggesting revisions to enhance clarity, specificity, and alignment with nursing standards.</p> <p>As a result of this collaboration, Sarah submitted a well-structured and evidence-based care plan that received praise from her instructor. The experience not only improved Sarah's understanding of care planning principles but also boosted her confidence in applying theoretical knowledge to clinical practice. Sarah credits the writing service for helping her achieve academic success while developing essential skills for her future career as a nurse.</p> <h4>Conclusion</h4> <p>BSN writing services play a vital role in supporting nursing students through their academic journey, enhancing learning outcomes, and preparing them for professional practice in healthcare. By providing expertise, personalized support, and promoting ethical academic practices, these services empower students to excel in their studies and contribute meaningfully to the field of nursing.</p> <p>As the healthcare landscape evolves, the demand for highly skilled and knowledgeable nurses continues to grow. BSN writing services, through their commitment to excellence and student-centered support, ensure that graduates are well-prepared to meet the challenges of modern healthcare and make significant contributions to patient care and nursing practice.</p> <p>In summary, BSN writing services are invaluable resources that enable nursing students to navigate the complexities of academic writing, enhance their learning experience, and develop critical skills necessary for success in their careers as healthcare professionals.</p> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div>

1 0

Announcement: New Dec2023-SP3 Bugfix release of MonetDB suite
by Sjoerd Mullender 10 May '24

10 May '24

The MonetDB Foundation is pleased to announce the Dec2023-SP3 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/release-notes/dec2023/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### Bug Fixes - [7422](https://github.com/MonetDB/MonetDB/issues/7422): Aggregate functions with variadic arguments - [7472](https://github.com/MonetDB/MonetDB/issues/7472): MonetDB server crashes in `tail_type` - [7473](https://github.com/MonetDB/MonetDB/issues/7473): MonetDB server crashes in `SQLunionfunc` - [7478](https://github.com/MonetDB/MonetDB/issues/7478): MonetDB server crashes in `exp_equal` - [7496](https://github.com/MonetDB/MonetDB/issues/7496): Query on view fails to produce a resultset. Assertion triggered in rel2bin_select. - [7499](https://github.com/MonetDB/MonetDB/issues/7499): create schema + set schema inside a transaction that is rolled back causes the connection to be aborted - [7501](https://github.com/MonetDB/MonetDB/issues/7501): files remain in backup causing problems at restart - [7503](https://github.com/MonetDB/MonetDB/issues/7503): MonetDB server crashes using `WHEN MATCHED THEN UPDATE` - [7504](https://github.com/MonetDB/MonetDB/issues/7504): possible deadlock when a bat is made persistent when it is also getting unloaded - [7506](https://github.com/MonetDB/MonetDB/issues/7506): MonetDB Dec2023-SP2 crashes at `rel_value_exp2` - [7507](https://github.com/MonetDB/MonetDB/issues/7507): BBPextend: ERROR: trying to extend BAT pool beyond the limit (163840000) - [7508](https://github.com/MonetDB/MonetDB/issues/7508): MonetDB Dec2023-SP2 crashes at `exp_ref`

1 0

Announcement: New Dec2023-SP2 Bugfix release of MonetDB suite
by Sjoerd Mullender 15 Apr '24

15 Apr '24

The MonetDB Foundation is pleased to announce the Dec2023-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/release-notes/dec2023/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### MonetDB Common - Threads have their own list of free bats. The list was not returned to the system when a thread exited, meaning that the free bats that were in the list would not be reused by any thread. This has been fixed. - Fixed a couple of deadlock situations, one actually observed, one never observed. ### MonetDB5 Server - Fixed interaction between mserver5 and remote mserver5 when only one of the two has 128 bit integer support. ### SQL Frontend - Fixed issue where equal column aliases were created. When those aliases were parsed on the remote side it could give crashes. ### Bug Fixes - [7469](https://github.com/MonetDB/MonetDB/issues/7469): Crash when using `CONTAINS` - [7479](https://github.com/MonetDB/MonetDB/issues/7479): MonetDB server crashes in `exp_ref` - [7490](https://github.com/MonetDB/MonetDB/issues/7490): commonTerms optimizer no longer works - [7495](https://github.com/MonetDB/MonetDB/issues/7495): Crash when simultaneously querying and updating a string column.

1 0

Announcement: New Dec2023-SP1 Bugfix release of MonetDB suite
by Sjoerd Mullender 18 Mar '24

18 Mar '24

The MonetDB Foundation is pleased to announce the Dec2023-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/release-notes/dec2023/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### - The copyright for the MonetDB software has been transferred to the newly established MonetDB Foundation, a not-for-profit foundation with the express goal of furthering the MonetDB database system. The license for the software does not change: MonetDB remains fully open source. ### Client Package - Fixed an issue where mclient wouldn't exit if the server it had connected to exited for whatever reason while the client was waiting for a query result. ### MonetDB Common - The internal hash function for floating point types has been changed. It is now no longer based on the bit representation, but on the value, meaning that +0 and -0 (yes, they both exist in floating point) now hash to the same value. - Fixed a regression where bats weren't always cleaned up when they weren't needed anymore. In particular, after a DELETE FROM table query without a WHERE clause (which deletes all rows from the table), the bats for the table get replaced by new ones, and the old, now unused, bats weren't removed from the database. ### Geom Module - We switched over to using the reentrant interface of the geos library. This fixed a number of bugs that would occur sporadically. ### SQL Frontend - performance improvement of 'startswith' and 'endswith' filter functions for join operators - The function json.isvalid(json) incorrectly returned true if the argument was null. It should return null. ### Bug Fixes - [6800](https://github.com/MonetDB/MonetDB/issues/6800): Please add information_schema (ANSI SQL norm) - [7152](https://github.com/MonetDB/MonetDB/issues/7152): Occasional dbfarm corruption upon database restart - [7390](https://github.com/MonetDB/MonetDB/issues/7390): Some MonetDB Server crashes found - [7412](https://github.com/MonetDB/MonetDB/issues/7412): MonetDB server crashes in `vscanf` - [7415](https://github.com/MonetDB/MonetDB/issues/7415): MonetDB server crashes in `HEAP_malloc` - [7416](https://github.com/MonetDB/MonetDB/issues/7416): MonetDB server crashes in `atom_get_int` - [7417](https://github.com/MonetDB/MonetDB/issues/7417): MonetDB server crashes in `trimchars`. - [7418](https://github.com/MonetDB/MonetDB/issues/7418): MonetDB server crashes in `bind_col_exp` - [7420](https://github.com/MonetDB/MonetDB/issues/7420): Performance issue with lower(string) - [7425](https://github.com/MonetDB/MonetDB/issues/7425): The last statement, execution error, is a false positive? - [7426](https://github.com/MonetDB/MonetDB/issues/7426): Unexpected result for INNER JOIN with IS NOT NULL - [7428](https://github.com/MonetDB/MonetDB/issues/7428): Unexpected result when using BETWEEN operator - [7429](https://github.com/MonetDB/MonetDB/issues/7429): Unexpected result when using `CASE WHEN` - [7430](https://github.com/MonetDB/MonetDB/issues/7430): Unexpected result when using `AND` and `IS NOT NULL` - [7431](https://github.com/MonetDB/MonetDB/issues/7431): [bug] Error code found, please confirm - [7432](https://github.com/MonetDB/MonetDB/issues/7432): MonetDB server crashes in `dameraulevenshtein` - [7433](https://github.com/MonetDB/MonetDB/issues/7433): MonetDB server crashes in `exp_atom` - [7434](https://github.com/MonetDB/MonetDB/issues/7434): MonetDB server crashes in `exp_bin` - [7435](https://github.com/MonetDB/MonetDB/issues/7435): MonetDB server crashes in `exp_copy` - [7436](https://github.com/MonetDB/MonetDB/issues/7436): MonetDB server crashes in `exp_ref` - [7437](https://github.com/MonetDB/MonetDB/issues/7437): MonetDB server crashes in `exp_values_set_supertype` - [7438](https://github.com/MonetDB/MonetDB/issues/7438): MonetDB server crashes in `exps_bind_column` - [7439](https://github.com/MonetDB/MonetDB/issues/7439): MonetDB server crashes in `exps_card` - [7440](https://github.com/MonetDB/MonetDB/issues/7440): MonetDB server crashes in `gc_col` - [7441](https://github.com/MonetDB/MonetDB/issues/7441): MonetDB server crashes in `is_column_unique` - [7442](https://github.com/MonetDB/MonetDB/issues/7442): MonetDB server crashes in `mat_join2` - [7443](https://github.com/MonetDB/MonetDB/issues/7443): MonetDB server crashes in `merge_table_prune_and_unionize` - [7444](https://github.com/MonetDB/MonetDB/issues/7444): [bug] the table cannot be created because the reserved word is incorrectly set - [7447](https://github.com/MonetDB/MonetDB/issues/7447): Unexpected result when using `BETWEEN` in `INNER JOIN` - [7448](https://github.com/MonetDB/MonetDB/issues/7448): Unexpected result when using `AND`/`OR` chain - [7450](https://github.com/MonetDB/MonetDB/issues/7450): Unexpected result when `CREATE VIEW` with `WHERE NULL` - [7451](https://github.com/MonetDB/MonetDB/issues/7451): Unexpected result when using `BETWEEN` and `CAST` - [7453](https://github.com/MonetDB/MonetDB/issues/7453): Cannot recover an msqldump - [7455](https://github.com/MonetDB/MonetDB/issues/7455): Unexpected result when using `BETWEEN` with `BOOLEAN` values - [7456](https://github.com/MonetDB/MonetDB/issues/7456): Crash when `INNER JOIN` with `VIEW` - [7457](https://github.com/MonetDB/MonetDB/issues/7457): Unexpected result when using `AND` with `INTEGER` - [7458](https://github.com/MonetDB/MonetDB/issues/7458): Unexpected result when using `SIGN` - [7461](https://github.com/MonetDB/MonetDB/issues/7461): Crash by potentially use of bad escape characters - [7462](https://github.com/MonetDB/MonetDB/issues/7462): Crash when using `BETWEEN AND` - [7465](https://github.com/MonetDB/MonetDB/issues/7465): Unexpected result when using `NULL` in `BETWEEN`

1 0

[MonetDB-users] Proofreading your professional documents
by Richard Hounslow 24 Feb '24

24 Feb '24

Dear Professor/Lecturer Please excuse us for contacting you directly. We are offering an efficient service to help you ensure your academic and professional work is written in perfect English. We will check the grammar and style of your work and return it to you to meet your requirements and deadlines. Proof-Reading-Service.com can provide you with a professional proofreading service at a very reasonable rate. All our proofreaders are highly qualified native English speakers. Many work as leading academics in their fields and all have extensive experience of proofreading to the highest standards. If you are interested in our service, please take a look at our website: www.proof-reading-service.com All you have to do is send us your document as a word attachment with the deadline and we will guarantee delivery of a perfectly written document to give you complete confidence when you submit your work. The fee is worked out on a flat rate (£6.95 per thousand words or 0.695 pence per word), so you know exactly how much the proofreading will cost in advance. Once we have received your document(s) we will confirm the word count, the price and the deadline. If you have not heard from us within 2 hours during normal business hours after you have sent your work please resend it from a different email account or send the file to proofreadings(a)gmail.com. We look forward to hearing from you! Yours faithfully Proof-Reading-Service.com

2 2

Problem to install new fresh database
by Ariel Abadi 30 Dec '23

30 Dec '23

Hi! Im trying to install the latest version of Monetdb, and seems the repo has an error. Can anyone help!? or had an idea how to solve this? [root@tc-mn monetdb]# yum update Loaded plugins: fastestmirror Determining fastest mirrors epel/x86_64/metalink | 32 kB 00:00:00 * epel: mirror.de.leaseweb.net base | 3.6 kB 00:00:00 epel | 4.7 kB 00:00:00 extras | 2.9 kB 00:00:00 monetdb | 1.5 kB 00:00:00 updates | 2.9 kB 00:00:00 (1/5): epel/x86_64/group_gz | 100 kB 00:00:00 (2/5): epel/x86_64/updateinfo | 1.0 MB 00:00:00 (3/5): monetdb/7/x86_64/primary | 120 kB 00:00:00 (4/5): updates/7/x86_64/primary_db | 24 MB 00:00:00 (5/5): epel/x86_64/primary_db | 7.0 MB 00:00:01 One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true Parsing primary.xml error: Start tag expected, '<' not found [root@tc-mn monetdb]#

2 1

Announcement: New Dec2023 Feature release of MonetDB suite
by Sjoerd Mullender 28 Dec '23

28 Dec '23

The MonetDB team at MonetDB Solutions BV is pleased to announce the Dec2023 feature 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/release-notes/dec2023/>. As usual, the download location is <https://www.monetdb.org/downloads/>. The Dec2023 documentation can be found [here](https://www.monetdb.org/documentation-Dec2023/). ## Dec2023 Feature Release (11.49.1) ### - All binary packages are now signed with a new key with key fingerprint DBCE 5625 94D7 1959 7B54 CE85 3F1A D47F 5521 A603. - The ranges of merge partitions are now pushed down into the low level GDK operations, giving them a handle to sometimes execute more efficiently. - Removed the PYTHON MAP external language option, as after a fork the synchronization primitives could be in any state, leading to deadlocks. During the upgrade function definitions will fallback to the normal PYTHON language option. - Implemented direct masking for strimp construction. The strimps datastructure now keeps an array of 65K 64-bit integers that is zero everywhere except at the indexes that correspond to header pairs. The entry for the nth pair in order has the nth bit of the bitstring on. These can be used to quickly construct bitstrings. ### ODBC Driver - Corrected the output value of column CHAR_OCTET_LENGTH of ODBC functions SQLColumns() and SQLProcedureColumns(). ### MonetDB Common - Fixed a (rare) race condition between copying a bat (COLcopy) and updates happening in parallel to that same bat. This may only be an actual problem with string bats, and then only in very particular circumstances. - Introduced options wal_max_dropped, wal_max_file_age and wal_max_file_size that control the write-ahead log file rotation. - Removed function BATroles to set column names on BATs. - Removed the compiled-in limit on the number of threads that can be used. The number of threads are still limited, but the limit is dictated solely by the operating system and the availability of enough memory. - We now prevent accidental upgrades from a database without 128 bit integers to one with 128 bit integers (also known as HUGEINT) from happening. Upgrades will only be done if the server is started with the option --set allow_hge_upgrade=yes. ### Geom Module - Because recent changes to the geom module require the use of geos 3.10, the geom module is no longer available in older versions of Debian and Ubuntu. Specifically, Debian 10 and 11 (buster and bullseye) and Ubuntu 20.04 (Focal Fossa) are affected. There is no automatic upgrade available for databases that were geom enabled to databases that are not, so dump + restore is the only option (if no geom types are actually used). - Implements Rtree index in GDK layer based on librtree. The index is used in the implementation of the filter functions ST_Intersects and ST_Dwithin for geometric points. - Improves shapefile support by replacing functions SHPattach, SHPpartialimport, ahd SHPimport with SHPload. - Introduces functions ST_DistanceGeographic, ST_DwithinGeographic, ST_IntersectsGeographic, ST_CoversGeographic, ST_Collects with geodesic semantics. ST_Transform can be used to convert geodetic into geographic data using libPROJ. ### MonetDB5 Server - Removed MAL functions bat.reuse and bat.reuseMap. - The MAL functions io.import and io.export have been removed. - Removed MAL functions bat.getRole and bat.setColumn since the underlying function BATroles was removed. - Change how json is stored in the database: We now normalize json strings after parsing, removing whitespace and eliminating duplicate keys in objects. - The function json.filter now properly returns json scalars instead of wrapping them in an array. - Removed the MAL tokenizer module. It was never usable from SQL and in this form never would be. ### SQL Frontend - Introduction of table returning function `persist_unlogged(schema string, table string)` that attempts to persist data in disk if "schema"."table" is unlogged table in insert only mode. If persist attempt is successful, the count of the persisted rows is returned, otherwise the count is 0. - Added ISO/IEC 9075-11 SQL/Schemata (SQL:2011) with SQL system views: information_schema.schemata information_schema.tables information_schema.views information_schema.columns information_schema.character_sets information_schema.check_constraints information_schema.table_constraints information_schema.referential_constraints information_schema.routines information_schema.parameters information_schema.sequences For details see https://www.monetdb.org/documentation/user-guide/sql-catalog/information_sc… Most views have been extended (after the standard columns) with MonetDB specific information columns such as schema_id, table_id, column_id, etc. This simplifies filtering and joins with system tables/views in sys schema when needed. Note: MonetDB does NOT support catalog qualifiers in object names, so all the CATALOG columns in these information_schema views will always return NULL. - Added support for generated column syntax: GENERATED BY DEFAULT AS IDENTITY ... This allows the user to override the default generated sequence value during inserts. - Added SQL support for: <result offset clause> and <fetch first clause> in <query expression> ::= [ <with clause> ] <query expression body> [ <order by clause> ] [ <result offset clause> ] [ <fetch first clause> ] [ <sample clause> ] <result offset clause> ::= OFFSET <offset row count> [ {ROW|ROWS} ] <fetch first clause> ::= FETCH {FIRST|NEXT} <fetch first row count> {ROW|ROWS} ONLY ### Bug Fixes - [6933](https://github.com/MonetDB/MonetDB/issues/6933): Add support for scalar function IFNULL(expr1, expr2) - [7044](https://github.com/MonetDB/MonetDB/issues/7044): Improve error message regarding 3-level SQL names - [7261](https://github.com/MonetDB/MonetDB/issues/7261): Misleading error message - [7274](https://github.com/MonetDB/MonetDB/issues/7274): Aggregate function ST_Collect crashes mserver5 - [7376](https://github.com/MonetDB/MonetDB/issues/7376): Concurrency Issue: Second Python UDF Awaits Completion of First UDF - [7391](https://github.com/MonetDB/MonetDB/issues/7391): SQL 2023 : greatest/least functions with unlimited arguments (not only 2) - [7403](https://github.com/MonetDB/MonetDB/issues/7403): Join not recognized between two row_number() columns - [7413](https://github.com/MonetDB/MonetDB/issues/7413): MonetDB server crashes in `BATcalcbetween_intern`

1 0

Announcement: New Jun2023-SP3 Bugfix release of MonetDB suite
by Sjoerd Mullender 20 Nov '23

20 Nov '23

The MonetDB team at MonetDB Solutions BV is pleased to announce the Jun2023-SP3 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/release-notes/jun2023/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### MonetDB Common - Fixed a regression where after a while the write-ahead log files weren't being rotated, meaning from some point onwards, the newest file just kept on growing. - When saving the SQL catalog during a low-level commit, we should only save the part of the catalog that corresponds to the part of the write-ahead log that has been processed. What we did was save more, which resulted in the catalog containing references to tables and columns whose disk presence is otherwise only in the write-ahead log. - A bug was fixed where the administration of which bats were in use was interpreted incorrectly during startup, causing problems later. One symptom that has been observed was failure to startup with a message that the catalog tables could not be loaded. ### SQL Frontend - Added a missing interface function sys.timestamp_to_str with a TIMESTAMP (as opposed to TIMESTAMP WITH TIME ZONE) argument. The missing interface caused error messages being produced when the function was called with a TIMESTAMP argument, although it did give the correct result. ### Bug Fixes - [7300](https://github.com/MonetDB/MonetDB/issues/7300): Implement missing standard SQL DATE and TIMESTAMP functions - [7324](https://github.com/MonetDB/MonetDB/issues/7324): string_distance('method',str1, str2) as a generic distance function - [7409](https://github.com/MonetDB/MonetDB/issues/7409): Numpy table returning UDFs with variadic arguments - [7410](https://github.com/MonetDB/MonetDB/issues/7410): SIGSEGV cause database corruption

1 0

Hot Backup no longer working when restoring
by warren.master＠rohatyngroup.com 18 Nov '23

18 Nov '23

i have been using hot backups for a while now , they are fast and have been very reliable for creating new servers and restoreing existig ones today I tried a restore from our daily hot backup that used call sys.hot_snapshot('/home/monetdb/mdb_hotbackup_20231117-1355390956724.tar.lz4'); I use the following to set up a new server monetdbd create /home/dbFarm tar -I lz4 -C /home/dbFarm -axf mdb_hotbackup_20231117-1355390956724.tar.lz4 monetdb start trg log filles with thousands of the below message and the db crashes MSG trg[9744]: #main thread: cleanup_and_swap: WARNING: Failed to set bat(381716) transient Im using lastest build on all machines MonetDB 5 server v11.47.11 (Jun2023-SP2) 2023-11-18 04:58:15 MSG trg[9744]: # Serving database 'trg', using 8 threads 2023-11-18 04:58:15 MSG trg[9744]: # Compiled for x86_64-pc-linux-gnu/64bit with 128bit integers 2023-11-18 04:58:15 MSG trg[9744]: # Found 62.759 GiB available main-memory of which we use 51.149 GiB 2023-11-18 04:58:15 MSG trg[9744]: # Copyright (c) 1993 - July 2008 CWI. 2023-11-18 04:58:15 MSG trg[9744]: # Copyright (c) August 2008 - 2023 MonetDB B.V., all rights reserved

1 0

Announcement: New Jun2023-SP2 Bugfix release of MonetDB suite
by Sjoerd Mullender 03 Oct '23

03 Oct '23

The MonetDB team at MonetDB Solutions BV is pleased to announce the Jun2023-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/release-notes/jun2023/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### - Fixed an installation issue on Debian and Ubuntu introduced in the last build. - Do a lot more error checking, mostly for allocation failures. More is still needed, though. - Improve performance of the ILIKE operator when the pattern contains only ASCII characters. In this case we do not need to treat any characters as UTF-8 and we can use much faster routines that perform byte comparisons. ### MonetDB Common - Fixed a number of data races (race conditions). - Fixed a reference counting problem when a BAT could nog be loaded, e.g. because of resource limitations. - Only check for virtual memory limits when creating or growing bats, not for general memory allocations. There is (still) too much code that doesn't properly handle failing allocations, so we need to avoid those as much as possible. This has mostly an effect if there are virtual memory size restrictions imposed by cgroups (memory.swap.max in cgroups v2, memory.memsw.limit_in_bytes in cgroups v1). - The low-level commit turned out to always commit every persistent bat in the system. There is no need for that, it should only commit bats that were changed. This has now been fixed. - Implemented timeout/exit checks in a bunch more operators. Long(er) running operators occasionally check whether they're taking too long (past a user-specified timeout) or whether the server is exiting. This is now done in more places. ### Bug Fixes - [7094](https://github.com/MonetDB/MonetDB/issues/7094): Drop remote tables in transactions and rollback - [7303](https://github.com/MonetDB/MonetDB/issues/7303): Improve the performance of multi-column filters - [7400](https://github.com/MonetDB/MonetDB/issues/7400): VM max memory is not check correctly for cgroups v2 - [7401](https://github.com/MonetDB/MonetDB/issues/7401): Column aliases used incorrectly in UNION subqueries - [7402](https://github.com/MonetDB/MonetDB/issues/7402): Privileges on merge table not propagated to partition tables

1 0

rdf/sparql support in monetdb
by nguyenm9＠aol.com 08 Aug '23

08 Aug '23

Hey folks, new to monetdb and was wondering what the current support for rdf/sparql would be in the db? I can see mention of rdf support from years past but nothing recent. is this option still available? thanks!

1 0

Announcement: New Jun2023-SP1 Bugfix release of MonetDB suite
by Sjoerd Mullender 25 Jul '23

25 Jul '23

The MonetDB team at MonetDB Solutions BV is pleased to announce the Jun2023-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/release-notes/jun2023/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### MonetDB5 Server - There is now a new option --set tablet_threads=N to limit the number of threads used for a COPY INTO from CSV file query. This option can also be set for a specific database using the monetdb command using the ncopyintothreads property. ### SQL Frontend - An upgrade that both creates a new .snapshot user and extends the sys.db_user_info table with (among others) a password column did these in such a way that the passord value for the new user was NULL. This is fixed by updating the password. ### Bug Fixes - [7388](https://github.com/MonetDB/MonetDB/issues/7388): Query results in large cross product - [7394](https://github.com/MonetDB/MonetDB/issues/7394): BBPextend: ERROR: trying to extend BAT pool beyond the limit (163840000)

1 0

Announcement: New Jun2023 Feature release of MonetDB suite
by Panagiotis Koutsourakis 29 Jun '23

29 Jun '23

The MonetDB team at MonetDB Solutions BV is pleased to announce the Jun2023 feature 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/release-notes/jun2023/>. As usual, the download location is <https://www.monetdb.org/downloads/>. The Jun2023 documentation can be found [here](https://www.monetdb.org/documentation-Jun2023/). ## Jun2023 Feature Release (11.47.3) ### Client Package - The COPY INTO from file ON CLIENT was extended to also look for a relative path name relative to the file from which the query was read. This is only possible if the name of the query file is known, so when it is specified on the command line or read using the interactive \< command. ### Mapi Library - Deprecate mapi_setfilecallback() in favor of mapi_setfilecallback2() which can handle binary downloads. For the time being, the old callback still works. ### ODBC Driver - Extended Windows MonetDB ODBC Data Source setup program with option to specify a logfile to enable tracing of ODBC Driver API calls. On other platforms users can edit the odbc.ini file and add a line: logfile=/home/username/odbctrace.log When a logfile is specified it will start logging the ODBC Driver API calls to the logfile after a new connection is made via SQLConnect() or SQLDriverConnect() or SQLBrowseConnect(). Note that enabling ODBC logging will slow down the performance of ODBC applications, so enable it only for analysing ODBC Driver problems. - Enhanced SQLTables() by adding support for table type names: 'BASE TABLE', 'GLOBAL TEMPORARY' and 'LOCAL TEMPORARY' in parameter TableType. These are synonyms of: 'TABLE', 'GLOBAL TEMPORARY TABLE' and 'LOCAL TEMPORARY TABLE'. ### MonetDB5 Server - The MAL debugger code has been removed. ### SQL Frontend - Add MAX_MEMORY and MAX_WORKERS options to the ALTER USER statement - Function 'similarity(x string, y string)' marked as deprecated and will be removed in the next release. - New functionality for string matching and similarity: startswith, endswith, contains, Levenshtein distance and Jaro-Winkler similarity. The functions startswith, endswith and contains have a version where a case insentive flag can be used. Also, there are new custom join functionality for startswith, endswith, contains, Levenshtein distance and Jaro-Winkler similarity. - Renamed previous Levenshtein distance to Damerau-Levenshtein distance. - New string function that transform from UTF-8 encoding to Ascii called asciify. - Session timeout feature improvement to start evaluating from the moment the procedure is called, instead of beginning of the session. - Queries stopped with the stop procedure are now marked as 'aborted' 'finished'. - The DEBUG statement has been removed. - SQL function sys.queue() overloaded with sys.queue(username string), SYSADMIN only, allowing to filter the global queue by username or use 'ALL' to retrieve the global queue. Calling the function without arguments returns the queue for the current user. - SQL procedures sys.pause(tag bigint), sys.resume(tag bigint), sys.stop(tag bigint) overloaded with sys.pause(tag bigint, username string), sys.resume(tag bigint, username string) and sys.stop(tag bigint, username string), SYSADMIN only, allowing to pause, resume and stop query executions by TAG, USERNAME. The call without arguments is a public procedure giving access to users to pause, resume and stop their own query executions. - Added support of ODBC escape sequences syntax to SQL layer. Now all clients (including ODBC/JDBC/pymonetdb) can use them without further processing. For details on ODBC escape sequences syntax see: https://learn.microsoft.com/en-us/sql/odbc/reference/appendixes/odbc-escape… - It is no longer allowed to create a merge table or remote table or replica table or unlogged table in schema "tmp". The tmp schema is reserved for temporary objects only, such as local/global temp tables. - System views sys.dependency_tables_on_functions and dependency_views_on_functions have been extended with column: function_id. - When loading data using COPY BINARY INTO, apply default values instead of just inserting NULLs. - When loading data using COPY BINARY INTO, validate DECIMAL(prec,scale) and VARCHAR(n) column width. - When loading data using COPY BINARY INTO, string used to have their line endings converted from CR LF to LF. Do not do this, it is the responsibility of the client. - Implemented dumping binary data using COPY SELECT ... INTO BINARY <file(s)>. - Removed code for Workload Capture and Replace, including system schemas "wlc" and "wlr" and the objects in those schemas. The code was experimental, and it didn't work out. A different approach will be taken. ### Merovingian - The monetdb get, inherit, lock and release commands are extended with ‘apply-to-all’ syntax similar to related functionality: Usage: monetdb set property=value [database ...] sets property to value for the given database(s), or all Usage: monetdb inherit property [database ...] unsets property, reverting to its inherited value from the default configuration for the given database(s), or all Usage: monetdb lock [-a] database [database...] Puts the given database in maintenance mode. Options: -a locks all known databases Usage: monetdb release [-a] database [database ...] Brings back a database from maintenance mode. Options: -a releases all known databases ### Bug Fixes - [7311](https://github.com/MonetDB/MonetDB/issues/7311): Missing `REGEXP_REPLACE` function. - [7344](https://github.com/MonetDB/MonetDB/issues/7344): Database upgrade failure due to user object dependency on system procedure - [7348](https://github.com/MonetDB/MonetDB/issues/7348): Subquery inside case always evaluated - [7378](https://github.com/MonetDB/MonetDB/issues/7378): MonetDB server crashes at sql_trans_copy_key - [7379](https://github.com/MonetDB/MonetDB/issues/7379): MonetDB server 11.46.0 crashes at cs_bind_ubat - [7380](https://github.com/MonetDB/MonetDB/issues/7380): MonetDB server 11.46.0 crashes at `BLOBcmp` - [7381](https://github.com/MonetDB/MonetDB/issues/7381): MonetDB server 11.46.0 crashes at `log_create_delta` - [7382](https://github.com/MonetDB/MonetDB/issues/7382): MonetDB server 11.46.0 crashes at `gc_col` - [7383](https://github.com/MonetDB/MonetDB/issues/7383): MonetDB server 11.46.0 crashes at `list_append` - [7384](https://github.com/MonetDB/MonetDB/issues/7384): MonetDB server 11.46.0 crashes at `__nss_database_lookup` - [7386](https://github.com/MonetDB/MonetDB/issues/7386): MonetDB server 11.46.0 crashes in `rel_deps` - [7387](https://github.com/MonetDB/MonetDB/issues/7387): MonetDB server 11.46.0 crashes in `rel_sequences`

1 0

Announcement: New Sep2022-SP3 Bugfix release of MonetDB suite
by Sjoerd Mullender 08 Jun '23

08 Jun '23

The MonetDB team at MonetDB Solutions BV is pleased to announce the Sep2022-SP3 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/release-notes/sep2022/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### Client Package - If the number of rows in mclient is set to 0 (using either --rows=0 option or \r0 on the mclient command line), the internal pager is used and it then uses the height of the terminal window. ### MonetDB Common - Warnings and informational messages are now sent to stdout instead of stderr, which means that monetdbd will now log them with the tag MSG instead of ERR. - Fixed parsing of the BBP.dir file when BAT ids grow larger than 2**24 (i.e. 100000000 in octal). - Fixed yet another occurrence of a missing .tailN file. This one could happen if a string bat was appended to in stages so that between appends the column was committed. If an append caused both a realloc of the tail heap because it was getting longer and a realloc because it got wider, the file might get removed before the GDK level commit happened. - When processing the WAL, if a to-be-destroyed object cannot be found, don't stop, but keep processing the rest of the WAL. - A race condition was fixed where certain write-ahead log messages could get intermingled, resulting in a corrupted WAL file. - If opening of a file failed when it was supposed to get memory mapped, an incorrect value was returned to indicate the failure, causing crashes later on. This has been fixed. - A race condition was fixed that could result in a missing tail file for a string bat (i.e. a file with .tail1, .tail2, or .tail4 extension). - When saving a bat failed for some reason during a low-level commit, this was logged in the log file, but the error was then subsequently ignored, possibly leading to files that are too short or even missing. - The write-ahead log (WAL) is now rotated a bit more efficiently by doing multiple log files in one go (i.e. in one low-level transaction). ### MonetDB5 Server - Client connections are cleaned up better so that we get fewer instances of clients that cannot connect. ### SQL Frontend - Fixed a regression introduced in the previous build: when a table is dropped in the same transaction where it was created, the data wasn't removed from disk. - When creating a hot snapshot, allow other clients to proceed, even with updating queries. - Increased the size of a variable counting the number of changes made to the database (e.g. in case more than 2 billion rows are added to a table). - Improved cleanup after failures such as failed memory allocations. - An insert into a table from which a column was dropped in a parallel transaction was incorrectly not flagged as a transaction conflict. - Fix bug where boolean NULLs were not recognized by COPY BINARY INTO ### Bug Fixes - [7360](https://github.com/MonetDB/MonetDB/issues/7360): Aggregates returning string crash - [7361](https://github.com/MonetDB/MonetDB/issues/7361): Table data is lost on DB restart, but only when a table has 2147483647 or more rows.

1 0

Possible BUG??
by Ariel Abadi 08 Mar '23

08 Mar '23

Hi All! I used to have a query that was working in a prior version (11.39.13), but now that I have upgraded to the newest version (11.45.13) this same query is not working any more. The query is the following: SELECT nrm_tim_date AS nrm_tim_date, ( (SELECT SUM(nrm_rse_amount_usd * exc.exc_rate) from sb_glob.exc_exchange exc where exc.exc_currency = 'USD') ) AS net_profit, SUM(nrm_rse_amount_usd) AS nrm_rse_amount_usd FROM sb_traf.cubm_202303 AS nrm GROUP BY nrm_tim_date The error Im having is "SQL Error [42000]: SELECT: subquery uses ungrouped column "nrm.nrm_rse_amount_usd" from outer query" This exact same query does work on version 11.39.13. Can someone help me with this? Thks a lot in advance ARIEL ABADI Direct: +54 11 5279.2054 Mobile: +54 9 11 6050.0101 *Email*: aabadi(a)starbi.com *Web*: www.starbi.com

2 1

Announcement: New MonetDB JDBC driver and JdbcClient released
by Martin van Dinther 02 Mar '23

02 Mar '23

The MonetDB team at MonetDB Solutions BV is pleased to announce a bug fix release of the MonetDB JDBC driver (monetdb-jdbc-3.3.jre8.jar) and JdbcClient CLI program (jdbcclient.jre8.jar). Besides bug fixes the new release improves performance and compliance. For a list of all changes see: https://www.monetdb.org/downloads/Java/ChangeLog We recommend all users of MonetDB JDBC driver and JdbcClient program to download and use the latest jar files. The download location is: https://www.monetdb.org/downloads/Java/ For information and tips on using the MonetDB JDBC driver, read: https://www.monetdb.org/downloads/Java/release.txt For information on using the MonetDB JDBC driver to execute COPY INTO <table> FROM <file> ON CLIENT ... and/or COPY <SELECT query> INTO <file> ON CLIENT ... commands for fast client side CSV file data import and export, read: https://www.monetdb.org/downloads/Java/onclient.txt Reminder: since release monetdb-jdbc-3.0.jre8.jar the MonetDB JDBC Driver class name has been changed to: org.monetdb.jdbc.MonetDriver It used to be nl.cwi.monetdb.jdbc.MonetDriver which is marked as deprecated and will be removed in a future release. Please use the new driver class name asap in your configuration files/scripts and/or Java code.

1 0

Announcement: New Sep2022-SP2 Bugfix release of MonetDB suite
by Sjoerd Mullender 31 Jan '23

31 Jan '23

The MonetDB team at MonetDB Solutions BV is pleased to announce the Sep2022-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/release-notes/sep2022/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### ODBC Driver - A crash in the ODBC driver was fixed when certain unsupported functions where used in a {fn ...} escape. - Prepare of a query where the sum of the number of parameters (question marks in the query) and the number of output columns is larger than 100 could fail with an unexpected error. This has been fixed. ### MonetDB Common - Fixed a race condition that could lead to a bat being added to the SQL catalog but nog being made persistent, causing a subsequent restart of the system to fail (and crash). - Fixed a race condition where a hash could have been created on a bat using the old bat count while in another thread the bat count got updated. This would make the hash be based on too small a size, causing failures later on. - When extending a bat failed, the capacity had been updated already and was therefore too large. This could then later cause a crash. This has been fixed by only updating the capacity if the extend succeeded. ### SQL Frontend - Fixed a regression where when there are multiple concurrent transactions, the dependencies weren't checked properly. - Added some error checking to prevent crashes. Errors would mainly occur under memory pressure. - Fixed cleanup after a failed allocation where the data being cleaned up was unitialized but still used as pointers to memory that also had to be freed. - Fixed a double cleanup after a failed allocation in COPY INTO. The double cleanup could cause a crash due to a race condition it enabled. ### Bug Fixes - [7343](https://github.com/MonetDB/MonetDB/issues/7343): GDKmmap requesting 0 virtual memory - [7347](https://github.com/MonetDB/MonetDB/issues/7347): A bug where an exception occurs even though it is a query with normal syntax (Merge Table)

1 0

Announcement: New Sep2022-SP1 Bugfix release of MonetDB suite
by Sjoerd Mullender 09 Dec '22

09 Dec '22

The MonetDB team at MonetDB Solutions BV is pleased to announce the Sep2022-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/release-notes/sep2022/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### Client Package - Also dump the new options of CREATE USER. ### ODBC Driver - Fixed issue with generated raw strings prefix when ODBC driver is used against a server older than Jun2020 (11.37). ### MonetDB Common - On Windows, use the wide-character interface of system calls when dealing with the environment (i.e. file names and getenv()). - Memory leaks have been fixed. - Improved maintenance of the estimated number of distinct values in BATs. The estimate helps in deciding which low-level algorithm to use. - Offset heaps (.tailN files) were growing too fast and unnecessarily under certain conditions. This has been fixed. Also, when such too large files are now loaded into the system, it is recognized they are too large and they are truncated to a more reasonable size. ### MonetDB5 Server - Fixed a crash when the server runs out of client contexts (i.e. more concurrent clients than the server is configured to handle). - A race condition in the SHA hash code was fixed which resulted in occasional failed connection attempts when they occurred concurrently. - Fix a bug where the MAL optimizer would use the starttime of the previous query to determine whether a query timeout occurred. ### SQL Frontend - Improved the handling of the "idle" value in the sys.sessions function and view. ### Merovingian - Stop logging references to monetdbd's logfile in said logfile. ### Bug Fixes - [7330](https://github.com/MonetDB/MonetDB/issues/7330): Creating temporary table fails after reconnect - [7333](https://github.com/MonetDB/MonetDB/issues/7333): DLLs fail to load on Windows with accented characters in path - [7336](https://github.com/MonetDB/MonetDB/issues/7336): Selecting from a literal-value table returns wrong values - [7339](https://github.com/MonetDB/MonetDB/issues/7339): MonetDB corrupted state after SIGKILL - [7342](https://github.com/MonetDB/MonetDB/issues/7342): column which datatype is double couldn't group or aggregation in version 11.45.7

1 0

Re: JSON column disk space
by Panagiotis Koutsourakis 07 Oct '22

07 Oct '22

Hello Alberto, I am looking into this issue and I would like to give you a small update and ask a couple of questions. Some background first. JSON objects are stored in MonetDB as strings. This creates overhead from the object keys and from numeric values that are now stored as strings. If I understand your issue correctly you don't have the chance to commit the reconstructed JSON column. Is this correct? From some tests I performed, I noticed that even before committing, disk usage goes up slowly. This is probably unrelated to JSON itself although I have not had a chance to verify this yet. So I think the most relevant question at this stage is how long are the keys in the JSON objects? I think that these are the most likely cause for the large overhead you are observing. Best regards, Panos. On 2022-09-28 21:17, Alberto Ferrari wrote: > Niels, > It's hard to me to create a demo script, but at leats I'd want to know > if it's a known "issue" (maybe it's not an issue, just as Monet works > internally) > > I can tell you that a table with 100 columns (ints, varchars, dates, > etc) with 30 million records, may occupy 30 Gb of disk. > When I merge some of these columns into one new json column -(i.e. 5 > single columns into one object like {col1:value, col2:value...}- and > dropped the 5 old columns (already merged in json), the table now > grows upto 100 Gb of disk. > > Thanks > > > El jue, 22 sept 2022 a la(s) 10:35, Niels Nes > (niels.nes(a)monetdbsolutions.com) escribió: >> >> >> Alberto >> >> Do you have some script which replicates this issue? >> And could you post the issue on the github issues? >> >> Niels >> >> On Thu, Sep 22, 2022 at 07:57:07AM -0300, Alberto Ferrari wrote: >> > Hi all: >> > >> > Monet version 11.35.19 (Nov2019-SP3) >> > >> > We realized that json columns in any table produces bigger stored >> > disk, no matter how many rows has big data. >> > It seems like depends on rows with different values in same json >> > column: if many rows has different values, then the space on disk >> > increases exponentially. So we can't use jaon columns in big tables, >> > since we run out of space disk in short time. >> > (also tested with 11.43.5 -Jan2022, same issue) >> > >> > Is there any solution to this problem? >> > Tanks! >> > Alberto >> > _______________________________________________ >> > users-list mailing list -- users-list(a)monetdb.org >> > To unsubscribe send an email to users-list-leave(a)monetdb.org >> >> _______________________________________________ >> users-list mailing list -- users-list(a)monetdb.org >> To unsubscribe send an email to users-list-leave(a)monetdb.org > _______________________________________________ > users-list mailing list -- users-list(a)monetdb.org > To unsubscribe send an email to users-list-leave(a)monetdb.org

4 4

JSON column disk space
by Alberto Ferrari 28 Sep '22

28 Sep '22

Hi all: Monet version 11.35.19 (Nov2019-SP3) We realized that json columns in any table produces bigger stored disk, no matter how many rows has big data. It seems like depends on rows with different values in same json column: if many rows has different values, then the space on disk increases exponentially. So we can't use jaon columns in big tables, since we run out of space disk in short time. (also tested with 11.43.5 -Jan2022, same issue) Is there any solution to this problem? Tanks! Alberto

2 4

Announcement: New Sep2022 Feature release of MonetDB suite
by Sjoerd Mullender 26 Sep '22

26 Sep '22

The MonetDB team at MonetDB Solutions BV is pleased to announce the Sep2022 feature 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/documentation/admin-guide/release-notes/sep2022/>. As usual, the download location is <https://www.monetdb.org/downloads/>. The Sep2022 documentation can be found [here](https://www.monetdb.org/documentation-Sep2022/). ## Sep2022 Feature Release (11.45.7) ### Client Package - Dumping of function GRANTs was improved by adding the types of the function (and procedure) arguments. ### ODBC Driver - Improved SQLSetPos(). It now allows RowNumber to be 0 when Operation is SQL_POSITION. - Improved ODBC Error/Warning messages. They now include the name of the Data Source as required by the ODBC specification: [MonetDB][ODBC driver VERSION][data-source-name] data-source-supplied-text - Improved MonetDB ODBC Data Source Configuration dialog on MS Windows by hiding the typed in password text. It now shows dots for the characters. This fixes request https://github.com/MonetDB/MonetDB/issues/7314 - Changed output of TABLE_CAT or PROCEDURE_CAT result columns as returned by ODBC functions: SQLTables(), SQLColumns(), SQLPrimaryKeys(), SQLForeignKeys(), SQLStatistics(), SQLTablePrivileges(), SQLColumnPrivileges(), SQLProcedures() and SQLProcedureColumns(). They used to return the static database name but now they will return NULL as MonetDB does not support CATALOG objects or qualifiers. - Removed the possibility to retrieve or set the CURRENT_CATALOG via SQLGetConnectAttr(hdbc, SQL_ATTR_CURRENT_CATALOG, ...) and SQLSetConnectAttr(hdbc, SQL_ATTR_CURRENT_CATALOG, ...) as MonetDB does not support CATALOG objects (no SQL support for: CREATE CATALOG abc or SET CATALOG abc) and therefore there is no CURRENT_CATALOG. - Corrected ODBC functions SQLTablePrivileges() and SQLColumnPrivileges() for local temporary tables located in schema tmp. They did not return any rows when the temporary table had privileges set. Now they do return rows as expected. - Improved SQLProcedures() and SQLProcedureColumns(). They now list information also for all built-in system procedures and functions, not only those created via SQL. Also corrected the value of ORDINAL_POSITION for scalar function arguments. It would start at 2 instead of 1. - Extended output of SQLProcedures() and SQLProcedureColumns() resultsets with an extra column SPECIFIC_NAME. This column contains the name which uniquely identifies this procedure or function within its schema. As MonetDB supports overloaded procedures and functions, the combination of PROCEDURE_SCHEM and PROCEDURE_NAME is not enough to uniquely identify a procedure or function. This extra column allows you to correctly match the corresponding rows returned by SQLProcedureColumns() with the specific rows of SQLProcedures(). This extra column SPECIFIC_NAME is implemented similar to the JDBC DatabaseMetaData methods getProcedures() and getProcedureColumns(). - For SQLForeignKeys() corrected the output of columns UPDATE_RULE and DELETE_RULE. These columns used to always return 3 (= SQL_NO_ACTION) but now they will report the action codes as specified in the FOREIGN KEY CONSTRAINT construction. - Fixed issue in function SQLProcedureColumns(). When the argument ColumnName was not empty it generated an invalid SQL query which failed with error: SELECT: no such column 'c.name'. This has been resolved. - Corrected implementation of SQLGetInfo(hdbc, SQL_MAX_DRIVER_CONNECTIONS, ...). It used to always return 64. Now it returns the value from the MonetDB server. - Changed the column names case of the result sets as returned by SQLTables(), SQLColumns(), SQLSpecialColumns(), SQLPrimaryKeys(), SQLForeignKeys(), SQLStatistics(), SQLTablePrivileges(), SQLColumnPrivileges(), SQLProcedures() and SQLProcedureColumns(). The column names where all in lowercase but the ODBC specification defines them in uppercase, so changed them to uppercase. - Corrected SQLSpecialColumns(..., SQL_BEST_ROWID, ...). Previously it only returned rows when the table had a primary key. Now it also returns rows when a table has a unique constraint. - Corrected SQLStatistics(..., SQL_INDEX_ALL, ...). Previously it only returned rows when the table had a primary or unique key. Now it also returns rows for indices which are not based on a key. - Corrected SQLStatistics(..., SQL_ENSURE). It now returns CARDINALITY information for columns based on a primary/unique key. Previously it always returned NULL for the CARDINALITY result column. - Corrected ODBC functions SQLPrimaryKeys(), SQLSpecialColumns() and SQLStatistics() for local temporary tables located in schema tmp. They did not return any rows when the temp table had a primary or unique key or index. Now they do return rows as expected. ### MonetDB Common - Fixed a bug in ORDER BY with both NULLS LAST and LIMIT when the ordering was on an interger or integer-like column and NULL values are present. - The median_avg and quantile_avg returned bogus results in the non-grouped case (i.e. something like SELECT sys.median_avg(i) FROM t). - The abort_on_error parameter of all GDK-level functions has been removed. Errors (e.g. overflow) now also results in an error. - Implemented BC/AD (and BCE/CE) suffixes when parsing dates. - The interface for using strimps has not changed (create an imprint index on a column of a read only table), but now construction happens at the beginning of the first query that uses the strimp and is performed in a multithreaded manner. - Implemented the use of strimps for NOT LIKE queries. The idea is to run the corresponding LIKE query using strimps and take the complement of the result. We keep around NULL values both during strimp filtering and during the pcre part of the LIKE query so that they get discarded automatically when we take the complement. - The function BBPkeepref now gets a BAT pointer as argument instead of a bat id. - Get rid of macro Tsize, use ->twidth instead. - Get rid of macro BUNlast, just use BATcount instead. - The BLOB type has been moved into the GDK layer. - When adding or subtracting months from a date or timestamp value, clamp the result to the calculated month instead of wrapping to the beginning of the next month. See bug [7227](https://https://github.com/MonetDB/MonetDB/issues/7227). - The median_avg and quantile_avg returned bogus results in the non-grouped case (i.e. something like SELECT sys.median_avg(i) FROM t). ### MonetDB5 Server - Disabled volcano pipeline due to known issues. ### SQL Frontend - The function sys.tracelog is now executable by anyone. The function (and view of the same name) returns the tracing information of a query that was prepended with the TRACE keyword. - Fixed a bug in COPY BINARY INTO where the input wasn't checked thoroughly enough. - Extended the built-in profiler to emit non-MAL events related to query compilation, optimization, transactions and client connections. To minimize, simplify and optimize the process of generating and processing profiler output, only the events marking the end of an operation are emitted in most cases and the emitted json messages themselves are trimmed down to their essential fields. Furthermore, the MAL instruction profiler.openstream now requires an integer as a single argument, "0" for default behaviour or "4" to turn on the profiler in minimal mode, which causes it to only emit general events and excludes individual MAL instruction execution events from the profiler streams. The MAL instruction profiler.openstream with zero arguments is deprecated. - Extended system view sys.users with columns: schema_path, max_memory, max_workers, optimizer and default_role. Extended system table sys.db_user_info with columns: schema_path, max_memory, max_workers, optimizer, default_role and password. The password is encrypted. This table can only be queried when the user has been granted the select privilege from monetdb. - CREATE USER statement has been extended to take more optional arguments like MAX_MEMORY, MAX_WORKERS, OPTIMIZER, DEFAULT ROLE. ALTER USER statement has also been extended with DEFAULT ROLE. - A new function sys.url_extract_host(string, bool) which returns the host name from the given URL has been implemented. The bool argument, if true, causes the www. prefix to be removed. - The user authentication tables are now administered by the SQL layer instead of the MAL layer. This means that changing (adding, dropping, altering) user and role information is now transaction-safe. - Added the UNLOGGED TABLE feature. - Removed functions sys.index and sys.strings. ### Merovingian - Added "loglevel" property for monetdbd logging (to merovingian.log). The loglevel can be set to: error or warning or information or debug. The loglevel property can be changed dynamically via command: monetdbd set loglevel=warning /path/to/dbfarm Default the loglevel is set to: information When loglevel is error, only errors are logged. When loglevel is warning, errors and warnings are logged. When loglevel is information, errors and warnings and information messages are logged. When loglevel is debug, all messages are logged. - There is now a loadmodules property that can be used to add --loadmodule arguments to the mserver5 command line. See the monetdb and mserver5 manual pages. - In certain cases (when an mserver5 process exits right after producing a message) the log message was logged over and over again, causing monetdbd to use 100% CPU. This has been fixed. ### Bug Fixes - [6982](https://github.com/MonetDB/MonetDB/issues/6982): Wrong constraint name in error message of constraint violation - [7209](https://github.com/MonetDB/MonetDB/issues/7209): Configuration option for merovingian.log - [7225](https://github.com/MonetDB/MonetDB/issues/7225): Invalid memory access when extending a BAT during appends - [7227](https://github.com/MonetDB/MonetDB/issues/7227): Date calculations, bug or feature - [7273](https://github.com/MonetDB/MonetDB/issues/7273): Concurrent reads and writes causes "BATproject2: does not match always" error - [7282](https://github.com/MonetDB/MonetDB/issues/7282): call sys.dump_table_data(); fails - [7285](https://github.com/MonetDB/MonetDB/issues/7285): C-UDFs: aggr_group.count has wrong value (number of input rows instead of number of groups). - [7296](https://github.com/MonetDB/MonetDB/issues/7296): Implictly cast a timestamp string to DATE when appropriate - [7297](https://github.com/MonetDB/MonetDB/issues/7297): Parsing partial dates behaves unpredictable - [7306](https://github.com/MonetDB/MonetDB/issues/7306): ODBC Driver Assertion `stmt->Dbc->FirstStmt' Failed - [7314](https://github.com/MonetDB/MonetDB/issues/7314): ODBC Driver : please mask/hide password - [7318](https://github.com/MonetDB/MonetDB/issues/7318): distinct in a subquery not working properly

1 0

Announcement: New Sep2022 Feature release of MonetDB suite
by Sjoerd Mullender 26 Sep '22

26 Sep '22

The MonetDB team at MonetDB Solutions BV is pleased to announce the Sep2022 feature 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/documentation/admin-guide/release-notes/sep2022/>. As usual, the download location is <https://www.monetdb.org/downloads/>. The Sep2022 documentation can be found [here](https://www.monetdb.org/documentation-Sep2022/). ## Sep2022 Feature Release (11.45.7) ### Client Package - Dumping of function GRANTs was improved by adding the types of the function (and procedure) arguments. ### ODBC Driver - Improved SQLSetPos(). It now allows RowNumber to be 0 when Operation is SQL_POSITION. - Improved ODBC Error/Warning messages. They now include the name of the Data Source as required by the ODBC specification: [MonetDB][ODBC driver VERSION][data-source-name] data-source-supplied-text - Improved MonetDB ODBC Data Source Configuration dialog on MS Windows by hiding the typed in password text. It now shows dots for the characters. This fixes request https://github.com/MonetDB/MonetDB/issues/7314 - Changed output of TABLE_CAT or PROCEDURE_CAT result columns as returned by ODBC functions: SQLTables(), SQLColumns(), SQLPrimaryKeys(), SQLForeignKeys(), SQLStatistics(), SQLTablePrivileges(), SQLColumnPrivileges(), SQLProcedures() and SQLProcedureColumns(). They used to return the static database name but now they will return NULL as MonetDB does not support CATALOG objects or qualifiers. - Removed the possibility to retrieve or set the CURRENT_CATALOG via SQLGetConnectAttr(hdbc, SQL_ATTR_CURRENT_CATALOG, ...) and SQLSetConnectAttr(hdbc, SQL_ATTR_CURRENT_CATALOG, ...) as MonetDB does not support CATALOG objects (no SQL support for: CREATE CATALOG abc or SET CATALOG abc) and therefore there is no CURRENT_CATALOG. - Corrected ODBC functions SQLTablePrivileges() and SQLColumnPrivileges() for local temporary tables located in schema tmp. They did not return any rows when the temporary table had privileges set. Now they do return rows as expected. - Improved SQLProcedures() and SQLProcedureColumns(). They now list information also for all built-in system procedures and functions, not only those created via SQL. Also corrected the value of ORDINAL_POSITION for scalar function arguments. It would start at 2 instead of 1. - Extended output of SQLProcedures() and SQLProcedureColumns() resultsets with an extra column SPECIFIC_NAME. This column contains the name which uniquely identifies this procedure or function within its schema. As MonetDB supports overloaded procedures and functions, the combination of PROCEDURE_SCHEM and PROCEDURE_NAME is not enough to uniquely identify a procedure or function. This extra column allows you to correctly match the corresponding rows returned by SQLProcedureColumns() with the specific rows of SQLProcedures(). This extra column SPECIFIC_NAME is implemented similar to the JDBC DatabaseMetaData methods getProcedures() and getProcedureColumns(). - For SQLForeignKeys() corrected the output of columns UPDATE_RULE and DELETE_RULE. These columns used to always return 3 (= SQL_NO_ACTION) but now they will report the action codes as specified in the FOREIGN KEY CONSTRAINT construction. - Fixed issue in function SQLProcedureColumns(). When the argument ColumnName was not empty it generated an invalid SQL query which failed with error: SELECT: no such column 'c.name'. This has been resolved. - Corrected implementation of SQLGetInfo(hdbc, SQL_MAX_DRIVER_CONNECTIONS, ...). It used to always return 64. Now it returns the value from the MonetDB server. - Changed the column names case of the result sets as returned by SQLTables(), SQLColumns(), SQLSpecialColumns(), SQLPrimaryKeys(), SQLForeignKeys(), SQLStatistics(), SQLTablePrivileges(), SQLColumnPrivileges(), SQLProcedures() and SQLProcedureColumns(). The column names where all in lowercase but the ODBC specification defines them in uppercase, so changed them to uppercase. - Corrected SQLSpecialColumns(..., SQL_BEST_ROWID, ...). Previously it only returned rows when the table had a primary key. Now it also returns rows when a table has a unique constraint. - Corrected SQLStatistics(..., SQL_INDEX_ALL, ...). Previously it only returned rows when the table had a primary or unique key. Now it also returns rows for indices which are not based on a key. - Corrected SQLStatistics(..., SQL_ENSURE). It now returns CARDINALITY information for columns based on a primary/unique key. Previously it always returned NULL for the CARDINALITY result column. - Corrected ODBC functions SQLPrimaryKeys(), SQLSpecialColumns() and SQLStatistics() for local temporary tables located in schema tmp. They did not return any rows when the temp table had a primary or unique key or index. Now they do return rows as expected. ### MonetDB Common - Fixed a bug in ORDER BY with both NULLS LAST and LIMIT when the ordering was on an interger or integer-like column and NULL values are present. - The median_avg and quantile_avg returned bogus results in the non-grouped case (i.e. something like SELECT sys.median_avg(i) FROM t). - The abort_on_error parameter of all GDK-level functions has been removed. Errors (e.g. overflow) now also results in an error. - Implemented BC/AD (and BCE/CE) suffixes when parsing dates. - The interface for using strimps has not changed (create an imprint index on a column of a read only table), but now construction happens at the beginning of the first query that uses the strimp and is performed in a multithreaded manner. - Implemented the use of strimps for NOT LIKE queries. The idea is to run the corresponding LIKE query using strimps and take the complement of the result. We keep around NULL values both during strimp filtering and during the pcre part of the LIKE query so that they get discarded automatically when we take the complement. - The function BBPkeepref now gets a BAT pointer as argument instead of a bat id. - Get rid of macro Tsize, use ->twidth instead. - Get rid of macro BUNlast, just use BATcount instead. - The BLOB type has been moved into the GDK layer. - When adding or subtracting months from a date or timestamp value, clamp the result to the calculated month instead of wrapping to the beginning of the next month. See bug [7227](https://https://github.com/MonetDB/MonetDB/issues/7227). - The median_avg and quantile_avg returned bogus results in the non-grouped case (i.e. something like SELECT sys.median_avg(i) FROM t). ### MonetDB5 Server - Disabled volcano pipeline due to known issues. ### SQL Frontend - The function sys.tracelog is now executable by anyone. The function (and view of the same name) returns the tracing information of a query that was prepended with the TRACE keyword. - Fixed a bug in COPY BINARY INTO where the input wasn't checked thoroughly enough. - Extended the built-in profiler to emit non-MAL events related to query compilation, optimization, transactions and client connections. To minimize, simplify and optimize the process of generating and processing profiler output, only the events marking the end of an operation are emitted in most cases and the emitted json messages themselves are trimmed down to their essential fields. Furthermore, the MAL instruction profiler.openstream now requires an integer as a single argument, "0" for default behaviour or "4" to turn on the profiler in minimal mode, which causes it to only emit general events and excludes individual MAL instruction execution events from the profiler streams. The MAL instruction profiler.openstream with zero arguments is deprecated. - Extended system view sys.users with columns: schema_path, max_memory, max_workers, optimizer and default_role. Extended system table sys.db_user_info with columns: schema_path, max_memory, max_workers, optimizer, default_role and password. The password is encrypted. This table can only be queried when the user has been granted the select privilege from monetdb. - CREATE USER statement has been extended to take more optional arguments like MAX_MEMORY, MAX_WORKERS, OPTIMIZER, DEFAULT ROLE. ALTER USER statement has also been extended with DEFAULT ROLE. - A new function sys.url_extract_host(string, bool) which returns the host name from the given URL has been implemented. The bool argument, if true, causes the www. prefix to be removed. - The user authentication tables are now administered by the SQL layer instead of the MAL layer. This means that changing (adding, dropping, altering) user and role information is now transaction-safe. - Added the UNLOGGED TABLE feature. - Removed functions sys.index and sys.strings. ### Merovingian - Added "loglevel" property for monetdbd logging (to merovingian.log). The loglevel can be set to: error or warning or information or debug. The loglevel property can be changed dynamically via command: monetdbd set loglevel=warning /path/to/dbfarm Default the loglevel is set to: information When loglevel is error, only errors are logged. When loglevel is warning, errors and warnings are logged. When loglevel is information, errors and warnings and information messages are logged. When loglevel is debug, all messages are logged. - There is now a loadmodules property that can be used to add --loadmodule arguments to the mserver5 command line. See the monetdb and mserver5 manual pages. - In certain cases (when an mserver5 process exits right after producing a message) the log message was logged over and over again, causing monetdbd to use 100% CPU. This has been fixed. ### Bug Fixes - [6982](https://github.com/MonetDB/MonetDB/issues/6982): Wrong constraint name in error message of constraint violation - [7209](https://github.com/MonetDB/MonetDB/issues/7209): Configuration option for merovingian.log - [7225](https://github.com/MonetDB/MonetDB/issues/7225): Invalid memory access when extending a BAT during appends - [7227](https://github.com/MonetDB/MonetDB/issues/7227): Date calculations, bug or feature - [7273](https://github.com/MonetDB/MonetDB/issues/7273): Concurrent reads and writes causes "BATproject2: does not match always" error - [7282](https://github.com/MonetDB/MonetDB/issues/7282): call sys.dump_table_data(); fails - [7285](https://github.com/MonetDB/MonetDB/issues/7285): C-UDFs: aggr_group.count has wrong value (number of input rows instead of number of groups). - [7296](https://github.com/MonetDB/MonetDB/issues/7296): Implictly cast a timestamp string to DATE when appropriate - [7297](https://github.com/MonetDB/MonetDB/issues/7297): Parsing partial dates behaves unpredictable - [7306](https://github.com/MonetDB/MonetDB/issues/7306): ODBC Driver Assertion `stmt->Dbc->FirstStmt' Failed - [7314](https://github.com/MonetDB/MonetDB/issues/7314): ODBC Driver : please mask/hide password - [7318](https://github.com/MonetDB/MonetDB/issues/7318): distinct in a subquery not working properly

1 0

insert pandas df to monetdb
by heikal79＠live.com 06 Sep '22

06 Sep '22

Hi is it possible to insert pandas df to montedb?. I have used both sqlalchemy and df.to_sql( name='invoiceline', con=engine, schema='tst', if_exists='append',index=False, index_label=None) and it returns text() got an unexpected keyword argument 'bindparams'. Also used pymonetdb and cursor.executemany('INSERT INTO tst.invoiceline VALUES (%s)', [[x] for x, row in df.iterrows()]) and returned 21S01!INSERT INTO: number of values doesn't match number of columns of table 'invoiceline'. My table contins 5 columns. BR

3 2

Change server configuration on Windows
by heikal79＠live.com 01 Sep '22

01 Sep '22

Hi Is it possible to change the server configuration on Windows including datafarm location, port,... Regards

2 2

Recovering database after BBPcheckbats error
by imad hajj chahine 24 Aug '22

24 Aug '22

Hi, I am using version Jan2022-SP2, and after a server restart I had the BBPcheckbats error. I upgraded to the latest version Jan2022-SP4 as it has the fix for this reported bug, and I am still unable to start the database. After manually editing the BBP.dir file and removing the entries on which the database failed to load with messages similar to (BBPcheckbats file /bat/01/67/16774.tail1 too small (expected 143640, actual 0), I managed to make the database start and connect to it and query the tables successfully. Is this the right way to recover from this? what I am risking losing by deleting these entries, should I have corrupted tables that are affected by these entries? What is exactly the role of BBP.dir? any documentation describing the use of this file. Appreciate your help. Thank you.

2 3

Copy into from stdin hanging after upgrade to 11.43.21
by imad hajj chahine 23 Aug '22

23 Aug '22

Hi, I have a bunch of dump sql files generated using msqldump command, that I was loading without any error to the version 11.43.15. After upgrading to version 11.43.21 to avoid the BBPCheckbats bug, loading the dump started to hang the server. Downgrading back to 11.43.15 fixed the issue. the command I am using to load the dump: mclient -d dbname -f sql < "pathtofile/dump.sql" sample dump file: COPY 1 RECORDS INTO tablename FROM stdin USING DELIMITERS '\t','\n','"'; Thank you.

1 0

Announcement: New Jan2022-SP4 Bugfix release of MonetDB suite
by Sjoerd Mullender 22 Aug '22

22 Aug '22

The MonetDB team at MonetDB Solutions BV is pleased to announce the Jan2022-SP4 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/documentation/admin-guide/release-notes/jan2022/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### Client Package - Implemented dump of global grants, that is to say, grants for COPY INTO and COPY FROM which grant permission to users to write to or read from files on the server (COPY INTO queries without the ON CLIENT option). - Fixed a bug where when the semicolon at the end of a COPY INTO query that reads from STDIN is at exactly a 10240 byte boundary in a file, the data isn't read as input for the COPY INTO but instead as a new SQL query. ### MonetDB Common - A bug was fixed when upgrading a database from the Oct2020 releases (11.39.X) or older when the write-ahead log (WAL) was not empty and contained instructions to create new tables. - When destroying a bat, make sure there are no files left over in the BACKUP directory since they can cause problems when the bat id gets reused. - Fixed an off-by-one error in the logger which caused older log files to stick around longer in the write-ahead log than necessary. - When an empty BAT is committed, skip writing (and synchronizing to disk) the heap (tail and theap) files and write 0 for their sizes to the BBP.dir file. When reading the BBP.dir file, if an empty BAT is encountered, set the sizes of those files to 0. This fixes potential issues during startup of the server (BBPcheckbats reporting errors). - Make sure heap files of transient bats get deleted when the bat is destroyed. If the bat was a partial view (sharing the vheap but not the tail), the tail file wasn't deleted. - Various changes were made to satisfy newer compilers. - The batDirtydesc and batDirtyflushed Boolean values have been deprecated and are no longer used. They were both holdovers from long ago. - Various race conditions (data races) have been fixed. - All accesses to the BACKUP directory need to be protected by the same lock. The lock already existed (GDKtmLock), but wasn't used consistently. This is now fixed. Hopefully this makes the hot snapshot code more reliable. ### MonetDB5 Server - Various race conditions (data races) have been fixed. ### Merovingian - When multiple identical messages are written to the log, write the first one, and combine subsequent ones in a single message. - Fixed a leak where the log file wasn't closed when it was reopened after a log rotation (SIGHUP signal). - Try to deal more gracefully with "inherited" mserver5 processes. This includes not complaining about an "impossible state", and allowing such processes to be stopped by the monetdbd process. - When a transient failure occurs during processing of a new connection to the monetdbd server, sleep for half a second so that if the transient failure occurs again, the log file doesn't get swamped with error messages. ### Bug Fixes - [7040](https://github.com/MonetDB/MonetDB/issues/7040): Memory leak detected for MAPI interface - [7298](https://github.com/MonetDB/MonetDB/issues/7298): Irresponsive database server after reading incomplete SQL script. - [7308](https://github.com/MonetDB/MonetDB/issues/7308): Race condition in MVCC transaction management

1 0

Re: Define a cast function from day_interval to int
by yunus 08 Aug '22

08 Aug '22

Hello Imad, Without going into too much detail, you might want to start having a look at the MonetDB-extend <https://www.monetdb.org/hg/MonetDB-extend> repository. Also keep in mind, that the use of MAL scripts for declaring C functions in MAL is deprecated in favor of the command and pattern preprocessor macro's. Regards, Yunus

1 0

Aggregation on double column in different monetdb version
by imad hajj chahine 04 Aug '22

04 Aug '22

Hi, I am currently migrating monetdb from an old version to the current release, and I noticed that sum on double precision columns is returning a slightly different result between both versions. The only difference between the system is HugeInt enabled on the newer version. ex: To reproduce the mismatch (subset of values extracted from the table) SELECT sum(cast(c1 as double)) --, sum(c1) FROM (VALUES (218.5792349726776),(792.3497267759564),(846.9945355191256),(819.6721311475409),(846.9945355191256),(819.6721311475409),(846.9945355191256),(846.9945355191256),(819.6721311475409),(846.9945355191256),(819.6721311475409),(846.9945355191256),(657.5342465753424),(4109.58904109589),(4234.972677595628),(3961.748633879781),(4234.972677595628),(4098.360655737704),(4234.972677595628),(4098.360655737704),(4234.972677595628),(4234.972677595628),(4098.360655737704),(4234.972677595628),(4098.360655737704),(273.224043715847),(219.1780821917808),(821.917808219178),(849.3150684931506),(846.9945355191256),(792.3497267759564),(846.9945355191256),(819.6721311475409),(846.9945355191256),(819.6721311475409),(846.9945355191256),(846.9945355191256),(819.6721311475409),(655.7377049180328),(249.3150684931507),(1104.109589041096),(1101.092896174863),(1030.054644808743),(1101.092896174863),(1065.573770491803),(1101.092896174863),(1065.573770491803),(1101.092896174863),(1101.092896174863),(1065.573770491803),(1101.092896174863),(852.4590163934427),(219.1780821917808),(1698.630136986301),(1643.835616438356),(1698.630136986301),(1693.989071038251),(1584.699453551912),(1693.989071038251),(1639.344262295081),(1693.989071038251),(1639.344262295081),(1693.989071038251),(1693.989071038251),(1475.409836065573),(60.27397260273972),(1868.493150684931),(1808.219178082191),(1868.493150684931),(1863.387978142076),(1743.169398907103),(1863.387978142076),(1803.27868852459),(1863.387978142076),(1803.27868852459),(1863.387978142076),(1863.387978142076),(1803.27868852459),(258.9041095890410),(381.1475409836065),(356.5573770491803),(381.1475409836065),(368.8524590163934),(381.1475409836065),(368.8524590163934),(381.1475409836065),(381.1475409836065),(368.8524590163934),(381.1475409836065),(368.8524590163934),(135.2459016393442),(542.4657534246575),(904.1095890410959),(934.2465753424657),(931.6939890710382),(871.5846994535519),(931.6939890710382),(901.639344262295),(931.6939890710382),(901.639344262295) ) t1 (c1) old-V11.27.11: 137756.87551463424 new-V11.43.15: 137756.8755146343 ExactValue: 137756.87551463430452 The aggregation over double columns should return the same result regardless of the engine versions, as the double precision type did not change, unless there was a bug reported and it was fixed. Any idea what could affect the result difference. Regards.

2 2

Define a cast function from day_interval to int
by imad hajj chahine 03 Aug '22

03 Aug '22

Hi, I am currently migrating monetdb from an old version to the current release, and I noticed that the difference of 2 dates return a day_interval and cannot be cast to an int and I have to use the "day" function for this purpose. This is fine for newly written scripts, but for old scripts I am hoping to avoid a rewrite. ex: cast(date1-date2 as int) return an error: types day_interval(4,0) and int(32,0) are not equal How to define a cast function from day_interval to int to avoid any changes to the old scripts?

2 2

Procedure vanishing
by hyemi.jeong＠obzen.com 21 Jul '22

21 Jul '22

Hello, I have just started to use monetDB and something strange has happened. I've made 5 procedures and 2 of them are just gone... I don't know what happened, they've just disappeared. Does this normally happen? Is there any possible explanation for this? I cannot possibly imagine what causes for this vanishing. Hope to hearing from you. Thanks.

1 0

Monetdb odbc driver
by imad hajj chahine 22 Jun '22

22 Jun '22

Hi, Is it possible to use 2 versions of the odbc driver simultaneously on the same windows machine? Since the windows installer does not allow this, I copied the installation folder from another machine and register the driver using the following command: odbcconf /A {INSTALLDRIVER "MonetDB ODBC Driver Old|driver=C:\Program Files\MonetDB\MonetDB ODBC Driver Old\lib\MonetODBC.dll|Setup=C:\Program Files\MonetDB\MonetDB ODBC Driver Old\lib\MonetODBCs.dll|APILevel=1|ConnectFunctions=YYY|DriverODBCVer=03.52|SQLLevel=3"} In the registry and the ODBC datasources the driver "MonetDB ODBC Driver Old" is registered correctly, but when I try to create a DSN for the new driver I am getting Error "Invalid Driver name". Does the Monetdb odbc driver need to have the exact name "MonetDB ODBC Driver"? Thanks.

2 2

Variable scope in Mal function
by imad hajj chahine 16 Jun '22

16 Jun '22

Hi, I have a mal function defined as following: function halfofyear(pdate:bat[:date]):bat[:int]; hym:= batmtime.month(pdate); hy:= batcalc.-(hym, 1, nil:bat); hy:= batcalc./(hy, 6, nil:bat); return halfofyear:= batcalc.+(hy, 1, nil:bat); end halfofyear; and I am calling it twice on 2 date columns: select halfofyear(colDate1), halfofyear(colDate2) from table. My concern is the scope of variables defined (hym, hy), as I was expecting to have unique naming when executing. Is it a guarantee that internally they are different variables or these are shared across the calls from the same query. bellow is the trace produced: hym=[57530]:bat[:int] := batmtime.month(pdate=[57530]:bat[:date]); hym=[57530]:bat[:int] := batmtime.month(pdate=[57530]:bat[:date]); hy=[57530]:bat[:int] := batcalc.-(hym=[57530]:bat[:int], 1:int, nil:BAT); hy=[57530]:bat[:int] := batcalc.-(hym=[57530]:bat[:int], 1:int, nil:BAT); hy=[57530]:bat[:int] := batcalc./(hy=[57530]:bat[:int], 6:int, nil:BAT); hy=[57530]:bat[:int] := batcalc./(hy=[57530]:bat[:int], 6:int, nil:BAT); return halfofyear=[57530]:bat[:int] := batcalc.+(hy=[57530]:bat[:int], 1:int, nil:BAT); return halfofyear=nil:bat[:int] := batcalc.+(hy=nil:bat[:int], 1:int, nil:BAT); function batudf.halfofyear(pdate:bat[:date]):bat[:int]; X_22=[57530]:bat[:int] := batudf.halfofyear(X_20=[57530]:bat[:date]); return halfofyear=[57530]:bat[:int] := batcalc.+(hy=[57530]:bat[:int], 1:int, nil:BAT); return halfofyear=nil:bat[:int] := batcalc.+(hy=nil:bat[:int], 1:int, nil:BAT); function batudf.halfofyear(pdate:bat[:date]):bat[:int]; X_25=[57530]:bat[:int] := batudf.halfofyear(X_21=[57530]:bat[:date]); barrier X_76=false:bit := language.dataflow(); X_26=33:int := sql.resultSet(X_27=[2]:bat[:str], X_28=[2]:bat[:str], X_29=[2]:bat[:str], X_30=[2]:bat[:int], X_31=[2]:bat[:int], X_22=[57530]:bat[:int], X_25=[57530]:bat[:int]); Thanks.

2 3

change Mal function definition without server restart
by imad hajj chahine 16 Jun '22

16 Jun '22

Hi, Is it possible to change the Mal function definition while the server is running without restarting? I tried connecting with mclient -lmal and running the function in an attempt to override the previous definition with no luck. any similar syntax to sql create or replace in Mal? Thanks.

1 0

Possible Loss of data (11.27.9)
by imad hajj chahine 16 Jun '22

16 Jun '22

Hi, I still have a server running 2017-sp2 (11.27.9) version, we had several reports of tables becoming empty after no activity for a period of one month or more. These tables are loaded from csv using the copy command, and at the time of loading the tables contain the correct data. Querying sys.storage showed that the oid column has a count of 210852 while the others are empty. Digging into the release-notes i only found the following alarming issue: https://github.com/MonetDB/MonetDB/issues/6465 I know that release is not supported anymore and I am planning a migration. Any idea what's the reason behind this behavior, was this reported before? [image: image.png] Thanks. Regards.

2 2

Announcement: New Jan2022-SP3 Bugfix release of MonetDB suite
by Sjoerd Mullender 31 May '22

31 May '22

The MonetDB team at MonetDB Solutions BV is pleased to announce the Jan2022-SP3 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/documentation/admin-guide/release-notes/jan2022/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### MonetDB Common - All accesses to the BACKUP directory need to be protected by the same lock. The lock already existed (GDKtmLock), but wasn't used consistently. This is now fixed. Hopefully this makes the hot snapshot code more reliable. - When exiting, long running instructions are aborted using the same mechanism that is used for query timeouts. ### SQL Frontend - GLOBAL TEMPORARY tables are now treated like LOCAL TEMPORARY tables as far as the table content is concerned. The schema information stays global. This fixes an issue with concurrent access and cleanup of stale data. - The NO CONSTRAINT option of the COPY INTO query has been removed. It didn't work and it was never a good idea anyway. ### Bug Fixes - [7036](https://github.com/MonetDB/MonetDB/issues/7036): Generate column names instead of labels

1 0

DELETE INTO?
by Marc Lowenthal 25 Apr '22

25 Apr '22

Hi all -- Does anyone know if MonetDB has a way of doing "DELETE INTO". The use case is to delete records from a table and save those results into another table with a single query. Thanks! --- Marc [cid:image001.png@01D85569.F9F48BB0]<http://www.scifinsys.com/> Marc Lowenthal Chief Product Officer marc(a)scifinsys.com<mailto:marc@scifinsys.com> [facebook]<https://www.facebook.com/Scientific-Financial-Systems-105163315113238> [linkedin]<https://www.linkedin.com/company/scientific-financial-systems-inc/> [/e9a7975e-dda8-4271-afa6-992bc461e648/]<https://scifinsys.com/> SFS is hiring! https://www.linkedin.com/jobs/view/2995084707/?refId=W7U9EW8bJ8ZxuymdxbxPqw… The entire content of this email message is confidential. This also applies to any files attached to it. This email is intended for an individual or entity to whom they are addressed. In case you are not the addressee of this email, and you have received it in error, immediately contact the system manager. The information in this email is very sensitive, and it is intended for the specific addressee. This email should not be disseminated, distributed or copied. If you have received this email and it was not for you, make sure to immediately notify the sender by email and afterwards delete this email from your system. Disclosing, copying, distributing, or taking any action in reliance to the email content is strictly prohibited. Consider yourself notified.

2 1

CHANGE COLUMN DATA TYPE?
by Alberto Ferrari 21 Apr '22

21 Apr '22

Hi all, I need to change the data type of a column. (I know the trick of creating a new temp column, copy the data from old, etc...) But I expected newer versions already have a command equivalent to MySql "CHANGE COLUMN" or similar, but I can't found in monetdb documentation. All examples of "ALTER COLUMN" are for setting other attributes. Anybody knows a specific command to do what I need? Kind regards, Alberto

2 4

Announcement: New Jan2022-SP2 Bugfix release of MonetDB suite
by Sjoerd Mullender 08 Apr '22

08 Apr '22

The MonetDB team at MonetDB Solutions BV is pleased to announce the Jan2022-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/documentation/admin-guide/release-notes/jan2022/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### Client Package - Improved the handling of the \r (internal pager) command in mclient. It now properly counts the header of table, and when a (very) long table is being printed and aborted part way in the built-in pager, not all data is transferred to the client (and then discarded). Instead at most 1000 rows are transferred. ### MonetDB Common - Improved speed of BATappend to empty varsized bat: we now just copy the heaps instead of inserting individual values. - Improved speed of projection (BATproject) on varsized bats by sharing the data heap (vheap). - Fixed a race condition which could cause a too large size being written for a .theap file to the BBP.dir file after the correct size file had been saved to disk. - We now ignore the size and capacity columns in the BBP.dir file. These values are essential during run time, but not useful in the on-disk image of the database. - Fixed a bug in the append code for msk (bit mask) bats. - Conversions from floating point types to integral types that involve multiplication now use the "long double" as intermediate type, thereby loosing as few significant bits as is feasible. - Found and fixed another source for the now infamous BBPcheckbats error that sometimes occurs at startup of the server. ### MonetDB5 Server - Improved parsing speed of blob values, especially on Windows. On Windows, using the locale-aware functions isdigit and isxdigit is comparatively very slow, so we avoid them. ### Bug Fixes - [7252](https://github.com/MonetDB/MonetDB/issues/7252): Segmentation fault on second run - [7253](https://github.com/MonetDB/MonetDB/issues/7253): Extremely slow INSERT INTO <table> SELECT - [7254](https://github.com/MonetDB/MonetDB/issues/7254): Commit with deletions is very slow - [7263](https://github.com/MonetDB/MonetDB/issues/7263): PRIMARY KEY constraint is not persistent through server restarts - [7267](https://github.com/MonetDB/MonetDB/issues/7267): Update after delete does not update some rows - [7278](https://github.com/MonetDB/MonetDB/issues/7278): BUG when there is more than one field/filter in the having clause

1 0

wrong command on deb package installation page
by Manuel Pagliai 04 Mar '22

04 Mar '22

Hello, I was following these instructions: https://www.monetdb.org/downloads/deb/ I think there is a mistake in the page and the command sudo wget --output-document=/etc/apt/trusted.gpg.d/monetdb.gpg /downloads/MonetDB-GPG-KEY.gpg should be replaced with sudo wget --output-document=/etc/apt/trusted.gpg.d/monetdb.gpg https://www.monetdb.org/downloads/MonetDB-GPG-KEY.gpg Best regards, *Manuel Pagliai* Visokio Ltd www.visokio.com +44 20 7351 4646

2 1

Iterations in MonetDB
by Oxana Dolmatova 23 Feb '22

23 Feb '22

Hello MonetDB Team, I want to integrate iterations into MonetDB using the barrier symbols provided by MAL (here the variable list_of_updates is repeated body of the iteration and ex_cond is the exit condition): ======================================= res_body = stmt_list(sql->sa, list_of_updates); stmt *s_begin = stmt_begin(sql->sa); list_append(res_list, s_begin); list_append(res_list, ex_cond); stmt *s_check = stmt_check(sql->sa, ex_cond, s_begin); list_append(res_list, s_check); list_append(res_list, res_body); list_append(res_list, stmt_redo(sql->sa, s_check)); list_append(res_list, stmt_exit(sql->sa, s_begin)); return stmt_list(sql->sa, res_list); ======================================== Currently the implementation works, when the exit condition is true, but unfortunately never stops, if the exit condition is false (I assume that this happens due to non-updating computation of ex_cond). Could you please give the reference point in the documentation or code where I could look to check if my assumption is correct? Or point me to a proper mailing-list if this is the wrong one for such questions? :) Thank you and best regards, Oksana

1 0

Fwd: COPY SELECT INTO with problems on new version 11.43.5 (Jan2022)
by Ariel Abadi 16 Feb '22

16 Feb '22

Hi All! I'm resending to the new user list. BR Ariel ---------- Forwarded message --------- From: Ariel Abadi <aabadi(a)starbi.com> Date: Fri, Feb 4, 2022, 18:44 Subject: COPY SELECT INTO with problems on new version 11.43.5 (Jan2022) To: Communication channel for MonetDB users <users-list(a)monetdb.org> Hi All! We found a problem on the new version 11.43.5 (Jan2022). We have some processes that run the COPY SELECT INTO to "move" data from monetdb to other different databases. We are expecting to receive an "answer" from monetdb affected, when the export finishes, like in the example below that informes "3 affected rows" sql>COPY SELECT * FROM cars INTO '/tmp/cars_out.csv' USING DELIMITERS ',' , '\n' , '"';*3 affected rows* While we run the same query on the new server, mclient/monetdb is not returning anything like the image below. sql>COPY SELECT * FROM cars INTO '/tmp/cars_out.csv' USING DELIMITERS ',' , '\n' , '"'; sql> Does anybody have the same issue? Am i doing something wrong? Thks a lot in advance! Ariel

2 1

Announcement: New Jan2022-SP1 Bugfix release of MonetDB suite
by Sjoerd Mullender 14 Feb '22

14 Feb '22

The MonetDB team at MonetDB Solutions BV is pleased to announce the Jan2022-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/documentation/admin-guide/release-notes/jan2022/>. As usual, the download location is <https://www.monetdb.org/downloads/>. ### SQL Frontend - [This feature was already released in Jan2022 (11.43), but the ChangeLog was missing] Added SQL procedures sys.vacuum(sname string, tname string, cname string), sys.vacuum(sname string, tname string, cname string, interval int), sys.stop_vacuum(sname string, tname string, cname string). These can be used to vacuum string columns. ### Bug Fixes - [7228](https://github.com/MonetDB/MonetDB/issues/7228): COMMIT: transaction is aborted because of concurrency conflicts, will ROLLBACK instead - [7230](https://github.com/MonetDB/MonetDB/issues/7230): Prepared statement of INSERT with SELECT fails when types difer - [7232](https://github.com/MonetDB/MonetDB/issues/7232): False conflicts when inserting in a not null field - [7237](https://github.com/MonetDB/MonetDB/issues/7237): SELECT with concurrent writes rarely returns corrupt data - [7238](https://github.com/MonetDB/MonetDB/issues/7238): query with system function: "index"(varchar, boolean) fails with GDK error or assertion failure. - [7241](https://github.com/MonetDB/MonetDB/issues/7241): Replacing a view by a query on the view itself crashes the server.

1 0

mailing list software updated
by Sjoerd Mullender 10 Feb '22

10 Feb '22

I have updated the mailing list software on monetdb.org from mailman2 to mailman3. This means that the old accounts for managing list subscriptions do not work anymore. In order to manage your subscription using a web interface, you will need to create a new account at https://www.monetdb.org/lists/. You can associate multiple email addresses to this account and manage all your subscriptions at monetdb.org using a single account, even if they use different email addresses. Unlike in mailman2, in mailman3 the passwords are not saved in plaintext, and therefore they cannot be sent as a monthly reminder. Mailing list archives have been converted to the new system as well. The old web addresses (https://mail.monetdb.org/, https://www.monetdb.org/mailman/ and https://www.monetdb.org/pipermail/) now all get redirected to the new interface. -- Sjoerd Mullender

1 0

None
by None 10 Feb '22

10 Feb '22

keeping the BAT open (I always use "bat("name").XXX", or keep a ref variable in a block. So, as far as I can tell, I should not have 7500 BATs open at once. Am I misunderstanding? Or is there some underlying component/module keeping the BATs open? Or is this just the amount of memory MonetDB will use? I do not have a BAT of BATs (as I was sure that this would cause problems, and from your description, will indeed). Thanks! Ed

1 0

None
by None 10 Feb '22

10 Feb '22

columns in a BAT (ie, BAT[OID, any]), is this just the first BUN? For update operations, does this mean that in the middle of inserting into a set of BATs, that as the BUN count is different, a concurrent query may not realize that the two BATs are synced? (this gets back to multiple client isolation for changes) Thanks for your time! Regards! Ed

1 0

None
by None 10 Feb '22

10 Feb '22

"This is implemented by storing a very large OID for each column. An update to the column destroys this OID."

1 0

None
by None 10 Feb '22

10 Feb '22

"For BAT-sets that contain exactly the same sets of OIDs, those OID-columns can be marked synced(). This information is then used to use positional lookup (the i-th element in BAT1 corresponds with the i-th in BAT2) and to turn semijoin- into very cheap copy-operations, etc." almost makes it sound as if you need synched() to actual test and set this bit. Is this true? How is the "syncedness" ensured when I have a BAT[OID, any], or determined?

1 0

New MonetDB JDBC driver v3.2 and JdbcClient released
by Martin van Dinther 03 Feb '22

03 Feb '22

The MonetDB team at MonetDB BV is pleased to announce a feature release of the MonetDB JDBC driver (monetdb-jdbc-3.2.jre8.jar) and JdbcClient CLI program (jdbcclient.jre8.jar). The new release adds the capability to use the SQL: COPY ... INTO ... ON CLIENT statements via Java from the client side. This allows users and programmers to use the much faster COPY statements to load large data sets into MonetDB from a local client side CSV file or stream. The JDBC MonetConnection API has been extended with methods to register and use Upload and Download Handlers to stream the data from the Java client application to the server and/or from the server to the Java client. See <https://www.monetdb.org/downloads/Java/onclient.txt> for details. The new functionality has also been added to the JdbcClient CLI program, so you can now also use COPY ... INTO ... ON CLIENT statements from this CLI program, provided you have started it with a --csvdir argument. The CSV data files may also be gzip compressed (file name ends with: .gz). Besides this new functionality we also improved both the JDBC driver and JdbcClient to work optimal with the new MonetDB Jan2022 server release. For a list of all changes please read: <https://www.monetdb.org/downloads/Java/ChangeLog>. We recommend all users of MonetDB JDBC driver and/or JdbcClient program to upgrade to this new release. Especially if you use the new MonetDB Jan2022 server release, you should use the new jar files. The download location is as usual: <https://www.monetdb.org/downloads/Java/>. For information and tips on using the MonetDB JDBC driver, read: <https://www.monetdb.org/downloads/Java/release.txt>. Reminder: as of release monetdb-jdbc-3.0.jre8.jar the MonetDB JDBC Driver class name has been changed to: org.monetdb.jdbc.MonetDriver It used to be nl.cwi.monetdb.jdbc.MonetDriver which is marked as deprecated. Please use the new driver class name asap in your configuration files/scripts and/or Java code. The old driver class name is currently still included in the jdbc jar file but only to ease the transition for existing deployments. The old driver class will be removed in a future release of the MonetDB JDBC driver.

1 0

Announcement: New Jan2022 Feature release of MonetDB suite
by Sjoerd Mullender 24 Jan '22

24 Jan '22

The MonetDB team at MonetDB BV is pleased to announce the Jan2022 feature 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/>. ## Jan2022 Feature Release (11.43.5) ### - A couple of concurrency issues have been fixed. ### Windows Packaging - We now build Windows binaries using Visual Studio 2022. ### Client Package - A new output formatting mode was added to mclient. Use -fcsv-noquote to produce a CSV (comma-separated values) output where the quote characters have not been escapes. This can be useful when producing a single column string output that should be saved as is, e.g. when using the sys.dump_database() function. ### MonetDB Common - Implement string imprints (strimps for short) a pre-filter structure for strings in order to accelerate LIKE queries. If a strimp exists for a specific string column the strings are pre-filtered, rejecting strings that cannot possibly match, before the more expensive and accurate matching algorithms run. - On Windows, files and directories we create now get the attribute FILE_ATTIBUTE_NOT_CONTENT_INDEXED, meaning that they should not be indexed by indexing or search services. - Many (most) low level functions that could take a long time (such as BATjoin) can now be aborted with a timeout. When the function takes too long, the function will fail, and hence the whole SQL query will fail. - At some point in the past, string heaps were created where the hash value of the string was stored in the heap before the string. This hasn't been used in a long time. Now the code that could still read those old heaps has been removed. Bats that used the old format are converted automatically. - Some small interface changes to the atom functions: the atomPut function now returns (var_t) -1 on error instead of 0; the atomHeap function now returns success or failure as a gdk_return value. ### General - Reliance on the OpenSSL library has been removed. OpenSSL was used for the hash algorithms it contained (e.g. SHA512 and RIPEMD160) and for producing random numbers. The hash functions have been replaced by the original published functions, and random numbers are generated using system-specific random sources (i.e. not simply pseudo-random number generators). ### MonetDB5 Server - The storage cleanup in the 11.41.5 (Jul2021) release made the OLTP optimizer pipeline obsolete, thus it was removed. ### SQL Frontend - Add string imprints to the existing imprints index creation syntax. On string column "col" of a table "tbl" marked read only ("ALTER TABLE tbl SET READ ONLY") the user can create a string imprint using the syntax: "CREATE IMPRINTS INDEX index_name ON tbl(col);". - With the storage cleanup in the 11.41.5 (Jul2021) release, the ANALYZE statement was updated to accomodate those changes. The SAMPLE parameter is now ignored because ANALYZE generated statistics used by relational operators, are required to be precise. - In order to mitigate the I/O required to update the 'statistics' table, this table is no longer persisted. Alternately, it was changed into a computed view every time when queried. The 'stamp' and 'sample' fields were removed for the aforementioned reasons. The 'schema', 'table' and 'column' fields were added for convenience. - In previous versions there was no check that the INCREMENT BY value of a SEQUENCE was not zero. During the automatic upgrade of a database, INCREMENT BY values that are zero are set to one. - The method to compute the 'side_effect' effect property was changed for SQL functions defined in the backend engine (eg. ``CREATE FUNCTION ... EXTERNAL NAME "module"."function"''). It was changed from being computed by the SQL layer to the backend engine itself. As a consequence, the computed 'side_effect' value may be different, thus bringing incompatibilities. After an upgrade, if a 'side_effect' incompatibility arises, either the 'side_effect' value in the backend should be changed or the function should be re-created in SQL. - Removed deprecated system view sys.systemfunctions. It was marked as deprecated from release Apr2019 (11.33.3). Use query: select id as function_id from sys.functions where system; to get the same data as the old view. - Extended SQL system catalog with lookup table sys.fkey_actions and view sys.fkeys to provide user friendly querying of existing foreign keys and their ON UPDATE and ON DELETE referential action specifications. - Many improvements were done for REMOTE table plans. As a consequence, master or slave servers from this feature release are not compatible with older releases. - The view sys.ids has been changed to give more information about the objects in the system. In particular, there is an extra column added at the end that indicates whether the object is a system object. - The example modules opt_sql_append and udf are no longer loaded by default and no longer part of the binary release. If installed, they can be loaded using the --loadmodule option. - The built-in SQL functions to produce a dump that were added as a proof-of-concept in the previous release have been improved and are now usable. Use the query ``SELECT stmt FROM sys.dump_database(FALSE) ORDER BY o'' to produce a dump. The dump code built into mclient and msqldump is probably still more efficient, though. - The sys.epoch function has always been confusing. There are two versions, one with an INTEGER argument, and one with a BIGINT argument. The former accepted values as seconds, whereas the latter expected milliseconds. Also, the construct EXTRACT(EPOCH FROM value) returns a BIGINT with millisecond precision. This has now been overhauled. There is no longer a function sys.epoch with BIGINT argument, but instead there is a new function sys.epoch with DECIMAL(18,3) argument. The argument is seconds, but with 3 decimals, it provides millisecond accuracy. Also the EXTRACT(EPOCH FROM value) now returns a DECIMAL(18,3), again seconds with 3 decimals giving millisecond accuracy. Note that the internal, binary representation of DECIMAL(18,3) interpreted as seconds with 3 decimals and BIGINT with millisecond precision is exactly the same. ### Merovingian - Disabled logging into merovingian.log of next info message types: - proxying client <host>:<port> for database '<dbname>' to <url> - target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying These messages were written to the log file at each connection. In most cases this information is not used. The disabling reduces the log file size. - Removed the deprecated monetdb commands `profilerstart` and `profilerstop`. ### Bug Fixes - [7168](https://github.com/MonetDB/MonetDB/issues/7168): Loosing the documentation - [7180](https://github.com/MonetDB/MonetDB/issues/7180): GROUP BY-subquery crashes MonetDb - [7182](https://github.com/MonetDB/MonetDB/issues/7182): Queries against sys.querylog_catalog, sys.querylog_calls or sys.querylog_history fail after restore of a db created using call sys.hot_snapshot(R'\path\file.tar'); - [7201](https://github.com/MonetDB/MonetDB/issues/7201): Selection of a subquery with a LEFT JOIN returns the wrong result set - [7202](https://github.com/MonetDB/MonetDB/issues/7202): DISTINCT does not work when sorting by additional columns - [7215](https://github.com/MonetDB/MonetDB/issues/7215): ODBC Driver SQLStatistics returns duplicate rows/rows for other tables

1 0

BATsetaccess() returns NULL
by Roberto Cornacchia 30 Dec '21

30 Dec '21

Hi there, I'm moving some code to Jul2021, and I got a bit stuck on this. The issue can be simplified to this (make a copy and, append another bat, and make the result read-only): bn = COLcopy(b, b->ttype, true, TRANSIENT); ret = BATappend(bn,u, s, force ? *force : false); bn = BATsetaccess(bn, BAT_READ); The only superficial difference from Oct2020 is that now BATaccess returns the modified bat instead of a gdk_return. The issue I see is that BATsetaccess() returns NULL, due to m1 == STORE_INVALID. Am I using this wrong? Any help is appreciated. Cheers, Roberto

1 1

SELinux problems
by Arjen P. de Vries 29 Dec '21

29 Dec '21

Hi all, Not really a bug report because I did not manage to figure out the cause. However, after upgrading from FC31 to FC32 I could not login any more, due to SELinux problems. Auto-relabeling did not work, nothing really... ... until I did dnf uninstall MonetDB-selinux. I came to this point because trying to give systemd services the correct labels with restorecon failed with an error referencing a monetdb specific file. I do not have the details unfortunately, but if you get problems, beware that MonetDB SELinux package and systemd may interfere in some way beyond my knowledge of these services. Best regards, Arjen PS: Some output from logs: sudo ausearch -c monetdb -m AVC,SELINUX_ERR [..] ---- time->Sat May 2 20:57:01 2020 type=AVC msg=audit(1588445821.693:203): avc: denied { open } for pid=1232 comm="monetdbd" path="/etc/resolv.conf" dev="dm-0" ino=3409775 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:default_t:s0 tclass=file permissive=1 ---- time->Sat May 2 21:12:56 2020 type=AVC msg=audit(1588446776.043:1194): avc: denied { execute } for pid=2861 comm="(monetdbd)" name="monetdbd" dev="dm-0" ino=2147256 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1 trawcon="unconfined_u:object_r:monetdbd_exec_t:s0" ---- time->Sat May 2 21:12:56 2020 type=AVC msg=audit(1588446776.043:1195): avc: denied { execute_no_trans } for pid=2861 comm="(monetdbd)" path="/usr/bin/monetdbd" dev="dm-0" ino=2147256 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1 trawcon="unconfined_u:object_r:monetdbd_exec_t:s0" ---- time->Sat May 2 21:12:56 2020 type=AVC msg=audit(1588446776.044:1196): avc: denied { map } for pid=2861 comm="monetdbd" path="/usr/bin/monetdbd" dev="dm-0" ino=2147256 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1 trawcon="unconfined_u:object_r:monetdbd_exec_t:s0" ---- time->Sat May 2 21:12:56 2020 type=AVC msg=audit(1588446776.714:1197): avc: denied { remove_name } for pid=1232 comm="monetdbd" name="merovingian.pid" dev="tmpfs" ino=34369 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=dir permissive=1 trawcon="system_u:object_r:monetdbd_var_run_t:s0" ---- time->Sat May 2 21:12:56 2020 type=AVC msg=audit(1588446776.714:1198): avc: denied { unlink } for pid=1232 comm="monetdbd" name="merovingian.pid" dev="tmpfs" ino=34369 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1 ---- time->Sat May 2 21:12:56 2020 type=AVC msg=audit(1588446776.714:1199): avc: denied { write } for pid=1232 comm="monetdbd" name=".merovingian_lock" dev="dm-0" ino=5899443 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1 trawcon="system_u:object_r:monetdbd_lock_t:s0" ---- time->Sat May 2 21:13:15 2020 type=AVC msg=audit(1588446795.214:1209): avc: denied { read } for pid=2925 comm="(monetdbd)" name="passwd" dev="dm-0" ino=524514 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=file permissive=1 ---- time->Sat May 2 21:13:15 2020 type=AVC msg=audit(1588446795.214:1210): avc: denied { open } for pid=2925 comm="(monetdbd)" path="/var/lib/sss/mc/passwd" dev="dm-0" ino=524514 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=file permissive=1 ---- time->Sat May 2 21:13:15 2020 type=AVC msg=audit(1588446795.214:1211): avc: denied { map } for pid=2925 comm="(monetdbd)" path="/var/lib/sss/mc/passwd" dev="dm-0" ino=524514 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=file permissive=1 ---- time->Sat May 2 21:14:24 2020 type=AVC msg=audit(1588446864.487:1281): avc: denied { read } for pid=3072 comm="(monetdbd)" name="passwd" dev="dm-0" ino=524514 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=file permissive=1 ---- time->Sat May 2 21:14:24 2020 type=AVC msg=audit(1588446864.487:1282): avc: denied { open } for pid=3072 comm="(monetdbd)" path="/var/lib/sss/mc/passwd" dev="dm-0" ino=524514 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=file permissive=1 ---- time->Sat May 2 21:14:24 2020 type=AVC msg=audit(1588446864.487:1283): avc: denied { map } for pid=3072 comm="(monetdbd)" path="/var/lib/sss/mc/passwd" dev="dm-0" ino=524514 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=file permissive=1 -- ==================================================================== ICIS, office M1.00.05 Radboud University Mercator 1 Faculty of Science Toernooiveld 212 arjen(a)cs.ru.nl NL-6525 EC Nijmegen, The Netherlands +31-(0)24-365 2354 ===================== http://www.informagus.nl/ ==================== -- ==================================================================== ICIS, office M1.00.05 Radboud University Mercator 1 Faculty of Science Toernooiveld 212 arjen(a)cs.ru.nl NL-6525 EC Nijmegen, The Netherlands +31-(0)24-365 2354 ===================== http://www.informagus.nl/ ====================

2 6

Announcement: New Jul2021-SP2 Bugfix release of MonetDB suite
by Sjoerd Mullender 21 Dec '21

21 Dec '21

The MonetDB team at MonetDB BV is pleased to announce the Jul2021-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/>. Jul2021-SP2 Bugfix Release (11.41.13) Client Package * Dumping the database now also dumps the read-only and insert-only states of tables. MonetDB Common * Sometimes when the server was restarted, it wouldn't start anymore due to an error from BBPcheckbats. We finally found and fixed a (hopefully "the") cause of this problem. SQL Frontend * Number parsing for SQL was fixed. If a number was immediately followed by letters (i.e. without a space), the number was accepted and the alphanumeric string starting with the letter was interpreted as an alias (if aliases were allowed in that position). Bug Fixes * 7163: Multiple sql.mvc() invocations in the same query * 7167: sys.shutdown() problems * 7184: Insert into query blocks all other queries * 7185: GROUPING SETS on groups with aliases provided in the SELECT returns empty result * 7186: data files created with COPY SELECT .. INTO 'file.csv' fail to be loaded using COPY INTO .. FROM 'file.csv' when double quoted string data contains the field values delimiter character * 7191: [MonetDBe] monetdbe_cleanup_statement() with bound NULLs on variable-sized types bug * 7196: BATproject2: does not match always * 7198: Suboptimal query plan for query containing JSON access filter and two negative string comparisons * 7200: PRIMARY KEY unique constraint is violated with concurrent inserts * 7206: Python UDF fails when returning an empty table as a dictionary

1 0

Archiving of MonetDBLite repositories
by Panagiotis Koutsourakis 15 Dec '21

15 Dec '21

Hello all, We would like to announce that MonetDBLite has been replaced by MonetDB/e. On January we will archive the following repositories: https://github.com/MonetDB/MonetDBLite-C https://github.com/MonetDB/MonetDBLite-R https://github.com/MonetDB/MonetDBLite-Python https://github.com/MonetDB/MonetDBLite-Java We've moved the best bits of MonetDBLite to MonetDB/e (i.e. MonetDB embedded), which we continue to develop and maintain. MonetDB/e is developed in the same codebase as the MonetDB server. This means that all new features and bug fixes land automatically in MonetDB/e. You can find bindings for Python (https://github.com/MonetDBSolutions/MonetDBe-Python) and Java (https://github.com/MonetDBSolutions/MonetDBe-Java) and we are working on bindings for R. You can also find a repository with code examples (https://github.com/MonetDBSolutions/monetdbe-examples)

1 0

Monetdbe and functions
by Ioannis Foufoulas 03 Dec '21

03 Dec '21

Hi, this is a question for monetdbe, I am trying to use create function with monetdbe, I ‘m getting a 'pyapi3.eval' library error in: Embedded Python 3 has not been enabled. Start server with --set embedded_py=3, however I am running the embedded version and I don’t know how to enable pyapi. Is there any configuration file, or any other workaround to enable these extensions? Thanks

1 0

Loader functions with temporary tables
by Ioannis Foufoulas 02 Nov '21

02 Nov '21

Hello, It seems that python loader functions do not work with temporary tables. Is it something that will be supported? Otherwise, is there any workaround to create a temporary table using a UDF that does not require a static definition of returned schema? Yannis

1 0

Issue with JIT C udfs
by Ioannis Foufoulas 05 Oct '21

05 Oct '21

Hi, I have an issue with C udfs. While most of the examples at https://www.monetdb.org/blog/JIT_C_C%252B%252B_UDFs_in_MonetDB run without problem, the example with SNAPPY does not run. It seems that linking, and includes work but if I call a function from the external library it fails with “write error on stream” The same happens also with other external libraries. My version is v11.37.11. Is there any idea for this issue? Yannis

2 1

Announcement: New Jul2021-SP1 Bugfix release of MonetDB suite
by Sjoerd Mullender 05 Oct '21

05 Oct '21

The MonetDB team at MonetDB BV is pleased to announce the Jul2021-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/>. Jul2021-SP1 Bugfix Release (11.41.11) MonetDB Common * Some deadlock and race condition issues were fixed. * Handling of the list of free bats has been improved, leading to less thread contention. * A problem was fixed where the server wouldn't start with a message from BBPcheckbats about files being too small. The issue was not that the file was too small, but that BBPcheckbats was looking at the wrong file. * An issue was fixed where a "short read" error was produced when memory was getting tight. * When appending to a string bat, we made an optimization where the string heap was sometimes copied completely to avoid having to insert strings individually. This copying was still done too eagerly, so now the string heap is copied less frequently. In particular, when appending to an empty bat, the string heap is now not always copied whole. SQL Frontend * If the server has been idle for a while with no active clients, the write-ahead log is now rotated. * A problem was fixed where files belonging to bats that had been deleted internally were not cleaned up, leading to a growing database (dbfarm) directory. * A leak was fixed where extra bats were created but never cleaned up, each taking up several kilobytes of memory. * [This feature was already released in Jul2021 (11.41.5), but the ChangeLog was missing] Grant indirect privileges. With "GRANT SELECT ON <my_view> TO <another_user>" and "GRANT EXECUTE ON FUNCTION <my_func> TO <another_user>", one can grant access to "my_view" and "my_func" to another user who does not have access to the underlying database objects (e.g. tables, views) used in "my_view" and "my_func". The grantee will only be able to access data revealed by "my_view" or conduct operations provided by "my_func". * Improved error reporting in COPY INTO by giving the line number (starting with one) for the row in which an error was found. In particular, the sys.rejects() table now lists the line number of the CSV file on which the record started in which an error was found. Bug Fixes * 7140: SQL Query Plan Non Optimal with View * 7162: Extend sys.var_values table * 7165: `JOINIDX: missing '.'` when running distributed join query on merged remote tables * 7172: Unexpected query result with merge tables * 7173: If truncate is in transaction then after restart of MonetDB the table is empty * 7178: Remote Table Throws Error - createExceptionInternal: !ERROR: SQLException:RAstatement2:42000!The number of projections don't match between the generated plan and the expected one: 1 != 1200

1 0

DBSeeder Version 3.0.3
by Walter Weinmann 12 Sep '21

12 Sep '21

We are pleased to release version 3.0.3 of DBSeeder ( https://github.com/KonnexionsGmbH/db_seeder) DBSeeder also supports the latest version of MonetDB available on Docker Hub (DBMS Jul2021). [image: Perf_Snap_3.0.3_win10.png]

1 0

Announcement: New Jul2021 Feature release of MonetDB suite
by Sjoerd Mullender 09 Aug '21

09 Aug '21

The MonetDB team at MonetDB BV is pleased to announce the Jul2021 feature 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/>. Jul2021 Feature Release (11.41.5) Client Package * The MonetDB stethoscope has been removed. There is now a separate package available with PIP (monetdb_stethoscope) or as an RPM or DEB package (stethoscope) from the monetdb.org repository. Mapi Library * Add optional MAPI header field which can be used to immediately set reply size, autocommit, time zone and some other options, see mapi.h. This makes client connection setup faster. Support has been added to mapilib, pymonetdb and the jdbc driver. ODBC Driver * A typo that made the SQLSpecialColumns function unusable was fixed. MonetDB Common * A bug in the grouping code has been fixed. * Hash indexes are no longer maintained at all cost: if the number of distinct values is too small compared to the total number of values, the index is dropped instead of being maintained during updates. * A new type, called msk, was introduced. This is a bit mask type. In a bat with type msk, each row occupies a single bit, so 8 rows are stored in a single byte. There is no NULL value for this type. * The function of the BAT iterator (type BATiter, function bat_iterator) has been expanded. The iterator now contains more information about the BAT, and it contains a pointer to the heaps (theap and tvheap) that are stable, at least in the sense that they will remain available even when parallel threads update the BAT and cause those heaps to grow (and therefore possibly move in memory). A call to bat_iterator must now be accompanied by a call to bat_iterator_end. * Implemented function BUNreplacemultiincr to replace multiple values in a BAT in one go, starting at a given position. * Implemented new function BUNreplacemulti to replace multiple values in a BAT in one go, at the given positions. * Removed function BUNinplace, just use BUNreplace, and check whether the BAT argument is of type TYPE_void before calling if you don't want to materialize. * Implemented a function BUNappendmulti which appends an array of values to a BAT. It is a generalization of the function BUNappend. * Changed the interface of the atom read function. It now requires an extra pointer to a size_t value that gives the current size of the destination buffer, and when that buffer is too small, it receives the size of the reallocated buffer that is large enough. In any case, and as before, the return value is a pointer to the destination buffer. * Environment variables (sys.env()) must be UTF-8, but since they can contain file names which may not be UTF-8, there is now a mechanism to store the original values outside of sys.env() and store %-escaped (similar to URL escaping) values in the environment. The key must still be UTF-8. * We now save the location of the min and max values when known. MonetDB5 Server * When using the --in-memory option, mserver5 will run completely in memory, i.e. not create a database on disk. The server can still be connected to using the name of the in-memory database. This name is "in-memory". * By using the option "--dbextra=in-memory", mserver5 can be instructed to keep transient BATs completely in memory. SQL Frontend * The system view sys.ids has been updated to include some more system IDs. * The sys.storage() function now only returns meta data, i.e. data that can be calculated without access to the column contents. * Since STREAM tables support is removed, left over STREAM tables are dropped from the catalog. * Fix a warning emitted by some implementations of the tar(1) command when unpacking hot snapshot files. * support reading the concatenation of compressed files as a single compressed file. * COPY BINARY overhaul. Allow control over binary endianness using COPY [ (BIG | LITTLE | NATIVE) ENDIAN] BINARY syntax. Defaults to NATIVE. Strings are now \0 terminated rather than \n. Support for BOOL, TINYINT, SMALLINT, INT, LARGEINT, HUGEINT, with their respective "INTMIN" values as the NULL representation; 32 and 64 bit FLOAT/REAL, with NaN as the NULL representation; VARCHAR/TEXT, JSON and URL with \x80 as the NULL representation; UUID as fixed width 16 byte binary values, with (by default) all zeroes as the NULL representation; temporal type structs as defined in copybinary.h with any invalid value as the NULL representation. * In the Jul2021 release the storage and transaction layers have undergone major changes. The goal of these changes is robust performance under inserts/updates and deletes and lowering the transaction startup costs, allowing faster (small) queries. Where the old transaction layer duplicated a lot of data structures during startup, the new layer shares the same tree. Using object timestamps the isolation of object is guaranteed. On the storage side the timestamps indicate whether a row is visible (deleted or valid), to a transaction as well. The changes also give some slight changes on the perceived transactional behavior. The new implementation uses shared structures among all transactions, which do not allow multiple changes of the same object. And we then follow the principle of the first writer wins, i.e., if a transaction creates a table with name 'table_name', and concurrently one other transaction does the same the later of the two will fail with a concurrency conflict error message (even if the first writer never commits). We expect most users not to notice this change, as such schema changes aren't usually done concurrently. * There is now a function sys.current_sessionid() to return the session ID of the current session. This ID corresponds with the sessionid in the sys.queue() result. * Merge statements could not produce correct results on complex join conditions, so a renovation was made. As a consequence, subqueries now have to be disabled on merge join conditions. * preserve in-query comments * Use of CTEs inside UPDATE and DELETE statements are now more restrict. Previously they could be used without any extra specification in the query (eg. with "v1"("c1") as (...) delete from "t" where "t"."c1" = "v1"."c1"), however this was not conformant with the SQL standard. In order to use them, they must be specified in the FROM clause in UPDATE statements or inside a subquery. * Added 'schema path' property to user, specifying a list of schemas to be searched on to find SQL objects such as tables and functions. The scoping rules have been updated to support this feature and it now finds SQL objects in the following order: 1. On occasions with multiple tables (e.g. add foreign key constraint, add table to a merge table), the child will be searched on the parent's schema. 2. For tables only, declared tables on the stack. 3. 'tmp' schema if not listed on the 'schema path'. 4. Session's current schema. 5. Each schema from the 'schema path' in order. 6. 'sys' schema if not listed on the 'schema path'. Whenever the full path is specified, ie "schema"."object", no search will be made besides on the explicit schema. * To update the schema path ALTER USER x SCHEMA PATH y; statement was added. [SCHEMA PATH string] syntax was added to the CREATE USER statement. The schema path must be a single string where each schema must be between double quotes and separated with a single comma, e.g. '"sch1","sch2"' For every created user, if the schema path is not given, '"sys"' will be the default schema path. * Changes in the schema path won't be reflected on currently connected users, therefore they have to re-connect to see the change. Non existent schemas on the path will be ignored. * Leftover STREAM table definition from Datacell extension was removed from the parser. They had no effect anymore. Merovingian * Deprecate `profilerstart` and `profilerstop` commands. Since stethoscope is a separate project (https://github.com/MonetDBSolutions/monetdb-pystethoscope) the installation directory is not standard anymore. `profilerstart` and `profilerstop` commands assume that the stethoscope executable is in the same directory as `mserver5`. This is no longer necessarily true since stethoscope can now be installed in a python virtual environment. The commands still work if stethoscope is installed using the official MonetDB installers, or if a symbolic link is created in the directory where `mserver5` is located. * The exittimeout value can now be set to a negative value (e.g. -1) to indicate that when stopping the dbfarm (using monetdbd stop dbfarm), any mserver5 processes are to be sent a termination signal and then waited for until they terminate. In addition, if exittimeout is greater than zero, the mserver5 processes are sent a SIGKILL signal after the specified timeout and the managing monetdbd is sent a SIGKILL signal after another five seconds (if it didn't terminate already). The old situation was that the managing monetdbd process was sent a SIGKILL after 30 seconds, and the mserver5 processes that hadn't terminated yet would be allowed to continue their termination sequence. Bug Fixes * 2030: Temporary table is semi-persistent when transaction fails * 7031: I cannot start MoentDb, because the installation path has Chinese. * 7055: Table count returning function used inside other function gives wrong results. * 7075: Inconsistent Results using CTEs in Large Queries * 7079: WITH table AS... UPDATE ignores the WHERE conditions on table * 7081: Attempt to allocate too much space in UPDATE query * 7093: `current_schema` not in sys.keywords * 7096: DEBUG SQL statement broken * 7115: Jul2021: ParseException while upgrading Oct2020 database * 7116: Jul2021: Cannot create filter functions * 7125: MonetDB Round Function issues in the latest release * 7126: The "lower" and "upper" functions doesn't work for Cyrillic alphabet * 7127: Bug report: "write error on stream" that results in mclient crash * 7128: Bug report: strange error message "Subquery result missing" * 7129: Bug report: TypeException:user.main[19]:'batcalc.between' undefined * 7130: Bug report: TypeException:user.main[396]:'algebra.join' undefined * 7131: Bug report: TypeException:user.main[273]:'bat.append' undefined * 7133: WITH <alias> ( SELECT x ) DELETE FROM ... deletes wrong tuples * 7136: MERGE statement is deleting rows if the column is set as NOT NULL even though it should not * 7137: Segmentation fault while loading data * 7138: Monetdb Python UDF crashes because of null aggr_group_arr * 7141: COUNT(DISTINCT col) does not calculate correctly distinct values * 7142: Aggregates returning tables should not be allowed * 7144: Type up-casting (INT to BIGINT) doesn't always happen automatically * 7146: Query produces this error: !ERROR: Could not find %102.%102 * 7147: Internal error occurs and is not shown on the screen * 7148: Select distinct is not working correctly * 7151: Insertion is too slow * 7153: System UDFs lose their indentation - Python functions broken * 7158: Python aggregate UDF returns garbage when run on empty table * 7161: fix priority

1 0

DBSeeder Version 3.0.1
by Walter Weinmann 03 Aug '21

03 Aug '21

We are pleased to release version 3.0.1 of DBSeeder ( https://github.com/KonnexionsGmbH/db_seeder) The most important enhancement is the possibility to deactivate the constraints of the type FOREIGN, PRIMARY and UNIQUE KEY before the DML statements and to activate them again afterwards. The JDBC DatabaseMetaData class is used for this purpose. DBSeeder also supports the latest version of MonetDB available on Docker Hub (DBMS Oct2020-SP5) and Maven Repository (JDBC 3.1.jre8).

1 0

Unable to connect to Monetdb after Upgrade : Challenge string is not valid, it is empty
by AUBERT Simon 02 Jul '21

02 Jul '21

Hello all I had an old monetdb installation on my Windows laptop -Did the upgrade in Oct2020-SP5 Bugfix Release (11.39.17) It really looks like I can start the server C:\Program Files\MonetDB\MonetDB5\bin>mserver5 # MonetDB 5 server v11.39.17 (Oct2020-SP5) # Serving database 'demo', using 4 threads # Compiled for amd64-pc-windows-msvc/64bit # Found 15.862 GiB available main-memory of which we use 12.928 GiB # Copyright (c) 1993 - July 2008 CWI. # Copyright (c) August 2008 - 2021 MonetDB B.V., all rights reserved # Visit https://www.monetdb.org/ for further information # Listening for connection requests on mapi:monetdb://localhost:50000/ # MonetDB/GIS module loaded # MonetDB/SQL module loaded # MonetDB server is started. To stop server press Ctrl-C. But when I want to use the mclient, it asks the user and password and then... nothing and after a few minutes I have this message Challenge string is not valid, it is empty Same thing with an ODBC connection : after a long time, it fails. I have reinstalled Monetdb but nothing changed. I have no idea of what's wrong. Best regards, Simon Simon AUBERT [cid:image001.jpg@01D76D97.13BF6A80] Bourse Maritime - 1, place Lainé - 33 000 Bordeaux Mob : +33(0)6 63 83 76 29

2 2

Re: Re: RSS memory
by Vojtech Kurka 21 Jun '21

21 Jun '21

Hello Roberto, Sjoerd, I think I am hitting the same problem described in this thread. I am running MonetDB in Docker container on a server with 30GB of memory, allocating 21GB of it to MonetDB container. Sometimes, under heavier load I get OOM - process mserver5 uses more memory than is the memory.limit_in_bytes for a cgroup of this container. It looks like this: [Mon Jun 21 12:56:36 2021] memory: usage 20971484kB, limit 20971520kB, failcnt 48706810 [Mon Jun 21 12:56:36 2021] memory+swap: usage 0kB, limit 9007199254740988kB, failcnt 0 [Mon Jun 21 12:56:36 2021] kmem: usage 143696kB, limit 9007199254740988kB, failcnt 0 .. [Mon Jun 21 12:56:36 2021] Tasks state (memory values in pages): [Mon Jun 21 12:56:36 2021] [ pid ] uid tgid total_vm rss pgtables_bytes swapents oom_score_adj name [Mon Jun 21 12:56:36 2021] [ 26927] 0 26927 1371 151 53248 0 0 run.sh [Mon Jun 21 12:56:36 2021] [ 27054] 0 27054 134763 326 139264 0 0 monetdbd [Mon Jun 21 12:56:36 2021] [ 27068] 0 27068 40646510 5209845 64159744 0 0 mserver5 [Mon Jun 21 12:56:36 2021] [ 27289] 0 27289 1019 69 45056 0 0 tail [Mon Jun 21 12:56:36 2021] [ 29503] 0 29503 6425 547 86016 0 0 mclient [Mon Jun 21 12:56:36 2021] oom-kill:constraint=CONSTRAINT_MEMCG,nodemask=(null),cpuset=d37591a31d4d010a7b4e34ebb19ba11220a84a264733f70a00ee92899c7918fc,mems_allowed=0,oom_memcg=/docker/d37591a31d4d010a7b4e34ebb19ba11220a84a264733f70a00ee92899c7918fc,task_memcg=/docker/d37591a31d4d010a7b4e34ebb19ba11220a84a264733f70a00ee92899c7918fc,task=mserver5,pid=27068,uid=0 [Mon Jun 21 12:56:36 2021] Memory cgroup out of memory: Killed process 27068 (mserver5) total-vm:162586040kB, anon-rss:20823812kB, file-rss:15568kB, shmem-rss:0kB, UID:0 pgtables:62656kB oom_score_adj:0 Have you made any progress in resolving the OOMs? Things I am trying to test are (I am using docker-compose v2 for running the container, so settings are from there): mem_limit: 21G # this sets memory.limit_in_bytes for the cgroup of the container mem_reservation: 14G # this sets memory.soft_limit_in_bytes oom_score_adj: -1000 # to lower the chance OOM will kill this process Exploring "select * from env();" in MonetDB tells me that the gdk_mem_maxsize is 12251394211, which corresponds to the 81.5% of the mem_reservation, or memory.soft_limit_in_bytes. I am monitoring memory usage of the container and it still is spiking at 19G, which is uncomfortably high, very close to the hard limit of the cgroup. Is this normal? FYI, originally meant only for PostgreSQL, but it became our standard - we are using vm.overcommit = 2 and vm.overcommit_ration = 100, if it changes anything. I would be thankful for any clue on how to run MonetDB in the container reliably as right now it is causing me quite a headache. Running it on a host solely for the MonetDB would be a last resort for me. Thank you and have a great day!

2 1

New MonetDB JDBC driver released
by Sjoerd Mullender 16 Jun '21

16 Jun '21

The MonetDB team at MonetDB BV is pleased to announce a bugfix release of the MonetDB Java jars and JDBC driver. We recommend all users of MonetDB JDBC driver to upgrade to version: monetdb-jdbc-3.1.jre8.jar The download location is as usual: <https://www.monetdb.org/downloads/Java/>. For a list of changes please read: <https://www.monetdb.org/downloads/Java/ChangeLog>. For information and tips on using the MonetDB JDBC driver, see: <https://www.monetdb.org/downloads/Java/release.txt>. Note: as of release monetdb-jdbc-3.0.jre8.jar the MonetDB JDBC Driver class name has been changed to: org.monetdb.jdbc.MonetDriver It used to be nl.cwi.monetdb.jdbc.MonetDriver which is now marked as deprecated. Please use the new driver class name asap in your configuration files/scripts and/or Java code. The old driver class name is still included in the jar file to ease the transition for existing deployments. However it will be removed in a future release of the MonetDB JDBC driver. -- Sjoerd Mullender

1 0

DBSeeder Version 2.9.1
by Walter Weinmann 12 Jun '21

12 Jun '21

The latest version of DBSeeder is now available on GitHub: https://github.com/KonnexionsGmbH/db_seeder. This also includes from MonetDB the latest available versions on Docker Hub (Oct2020-SP5) and https://www.monetdb.org/downloads/Java (JDBC monet-jdbc-3.0.jre8). MonetDB now shows a huge performance improvement after a manual commit (instead of autocommit) is executed in DBSeeder after each batch of insert operations. [image: Company_9.9.9_win10.png]

1 0

Linux kernel vm settings
by Roberto Cornacchia 06 Jun '21

06 Jun '21

Hi there, I looked around but couldn't find any recommendation about kernel vm settings in Linux for MonetDB. In particular: - vm.overcommit_memory: 0 (default) : a heuristics decides whether overcommitting is allowed 1: no check, overcommit is always allowed 2: overcommitting is regulated by vm.overcommit_ratio (default = 50%) Do I understand correctly that using vm.overcommit_memory=1 will only make the OOM kill mserver5 when the total VM available is exhausted? If that is true, should it be reasonably safe to use on a server that is mainly intended for MonetDB, as long as sufficient disk space is available? - vm.swappiness Generic recommendations are usually 60 for a desktop and 30 for a server. Oracle recommends 10. Redis recommends 1. Are there studies / recommendations for MonetDB?

5 8

DBSeeder Version 2.9.0
by Walter Weinmann 05 Jun '21

05 Jun '21

We are happy to announce that version 2.9.0 of DBSeeder ( https://github.com/KonnexionsGmbH/db_seeder) is now available for general use. DBSeeder also supports the latest version of MonetDB available on DockerHub (Oct2020-SP5).

1 0

for the Cyrillic alphabet, lower does not work
by Илья Хайбуллин 17 May '21

17 May '21

2 3

gcc optimization level?
by Roberto Cornacchia 14 May '21

14 May '21

I was wondering, -DCMAKE_BUILD_TYPE=Release (or RelWithDebInfo) doesn't seem to enable -O2 on gcc. Is there a good reason for it or was it just forgotten?

2 2

Announcement: New Oct2020-SP5 Bugfix release of MonetDB suite
by Sjoerd Mullender 10 May '21

10 May '21

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 0

Announcement: New Oct2020-SP4 Bugfix release of MonetDB suite
by Sjoerd Mullender 12 Apr '21

12 Apr '21

The MonetDB team at MonetDB BV is pleased to announce the Oct2020-SP4 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-SP4 Bugfix Release (11.39.15) ODBC Driver * When connecting using a DSN (Data Source Name), information about the data source is retrieved from the ODBC.INI file. Now we also get the location of the LOGFILE from this file. The logfile can be used to log all calls to the MonetDB ODBC driver to a file which can be used for debugging. * The ODBC driver now only passes on information about HUGEINT columns as HUGEINT when the application has indicated interest by querying about the SQL_HUGEINT extension type using the SQLGetTypeInfo function or by specifying the type in a call to SQLSetDescField. Otherwise the driver silently translates the HUGEINT type to BIGINT. This means that most application will see BIGINT columns when the server produced a HUGEINT column and only give an error if the value in the HUGEINT column didn't fit into a BIGINT. Bug Fixes * 6786: function json.isvalid(js json) is not useful, could be removed * 7016: Database crashes when use similarity function on a table with more than 200k records * 7037: Clearer err msg for ALTER USER with insufficient privileges * 7042: AddressSanitizer:DEADLYSIGNAL in Oct2020/gdk/gdk_tracer.c:494 * 7050: file descriptor leak when forward=redirect * 7057: ODBC driver installer on Windows is missing some DLLs * 7058: MonetDBe: COPY INTO csv file does not produce any output * 7059: MonetDBe: 'reverse' C UDF crashes * 7061: Have bulk load support combined gzip files * 7064: Temporary hashes created in hash and unique logic should try to use transient data farm first * 7066: percent_rank function with wrong results * 7070: double free error when running MonetDBe Example * 7076: mserver5 ignores memory.low from cgroups v2 * 7077: Oct2020: new default privileges not effectively communicated * 7083: MonetDBe C++ Compiling Error * 7085: Mitosis and filter functions * 7087: SIGSEGV caused by error in subquery's function being ignored by top-level query * 7089: Data consistency problem of query results in the latest release of Monetdb (Remote Table)

1 0

Need info about --in-memory option
by Lakshmipathy Jois 09 Apr '21

09 Apr '21

Hi All, I am new to MonetDB and this is my first email to this group. I came across the option --in-memory for mserver5. I understood that if this option is set, then MonetDB operates out of memory and data is not persisted. I wanted to know more details about the working of MonetDB if this option is set: 1. If this option is set, what is the maximum data size that MonetDB can operate with? 2. If this option is set, will MonetDB use mmap only for reading purposes or not use mmap at all? Any other information is really welcome. Thanks in advance. Lakshmi Pathy S N

2 1

Problems installing October2020 version
by Ioannis Foufoulas 31 Mar '21

31 Mar '21

Hi, It seems that releases from October2020 have a different structure (and size) and instructions here https://www.monetdb.org/Documentation/ServerAdministration/Installation/Ins… <https://www.monetdb.org/Documentation/ServerAdministration/Installation/Ins…> are not working as expected. Is there any documentation on how to install the latest versions? Best, Yannis

2 1

Bug with remote tables in transactions
by Ioannis Foufoulas 30 Mar '21

30 Mar '21

Hi, We encounter a bug with remote tables as part of transactions: sql>CREATE REMOTE TABLE rmt_tbl (id int, name varchar(20)) ON ‘mapi:monetdb://remote.host.url:50000/dbname/scm1/l_tbl <monetdb://remote.host.url:50000/dbname/scm1/l_tbl>’; operation successful sql>BEGIN TRANSACTION; auto commit mode: off sql>DROP TABLE rmt_tbl; operation successful sql>ROLLBACK; auto commit mode: on sql>DROP TABLE if exists rmt_tbl; no such table: ‘sys.rmt_tbl’ sql> It seems that after rollback the table exists in the catalogue but it does not actually exists so that drop table fails even if we have ‘if exists’ This happens only with remote tables. Best, Yannis

2 1

RSS memory
by Roberto Cornacchia 11 Mar '21

11 Mar '21

Hi, I would appreciate some help interpreting the following memory-related issues. I've got a mserver5 instance running with cgroups v1 constraints - memory.limit_in_bytes = 17179869184 (16g) - memory.memsw.limit_in_bytes = 9223372036854771712 gdk_mem_maxsize is initialised as 0.815 * 17179869184 = 14001593384. So I get: sql>select * from env() where name in ('gdk_mem_maxsize', 'gdk_vm_maxsize'); +-----------------+---------------+ | name | value | +=================+===============+ | gdk_vm_maxsize | 4398046511104 | | gdk_mem_maxsize | 14001593384 | +-----------------+---------------+ That looks good. To my surprise, this instance gets frequently OOM-killed for reaching 16g of RSS (no swap used): memory: usage 16777216kB, limit 16777216kB, failcnt 244063804 memory+swap: usage 16777964kB, limit 9007199254740988kB, failcnt 0 kmem: usage 0kB, limit 9007199254740988kB, failcnt 0 Memory cgroup out of memory: Kill process 975803 (mserver5) score 1003 or sacrifice child Now, there are two different aspects: giving a process a memory cap and making the process respect that cap without getting killed. - if the process allocates more than defined with cgroups, then it gets killed. That is fine, it doesn't surprise me - the question is: why did monetDB surpass the 16g limit? Even more surprising, given that it "prudently" initialises itself at 80% of the available memory. Perhaps I was under the wrong assumption that MonetDB would never allocate more than gdk_mem_maxsize, but now I seem to realise that it simply uses this value to optimise its memory management (e.g. to decide how early to mmap). So, am I correct that setting gdk_mem_maxsize (indirectly via gcroups or directly via memmaxsize parameter) does not guarantee rss memory will stay underthat value? If that is true, I am back at square 1 in my quest for how to cap rss usage (without getting the process killed). Thanks for your help. Roberto

2 6

Structure of error messages and comprehensive list of errors
by imad hajj chahine 10 Mar '21

10 Mar '21

Hi, I am trying to understand the error messages and codes reported by MonetDB, to be able to better handle error reporting, monitoring and logging. What I understand so far about the structure of an error message, it starts with error code placed between '!' and after the error message, for ex: !42000! SELECT: identifier 'xyz' unknown. and sometimes a part of the query is included. I found the list of ODBCError in "clients/odbc/driver/ODBCError.c" file, but I am not sure if this is the complete list and if it's aligned with the error codes reported by MonetDB. Is there any standard for the message error structure and where can I find the list of errors with their descriptions? Thanks.

1 0

MonetDB development feedback and contribution
by Jamie Wang 19 Feb '21

19 Feb '21

Hi, I work for Opentext corporation and one of my dev team is heavily using MonetDB and would like to explore if there's common interest on certain functionalities that we have developed. We would be interested to exchange information, solicit feedback and the possibility to contribute to the community. Can someone please provide a few pointers as to how to proceed? Thanks in advance for your time and assistance. Jamie

1 0

Announcement: New Oct2020-SP3 Bugfix release of MonetDB suite
by Sjoerd Mullender 19 Feb '21

19 Feb '21

The MonetDB team at MonetDB BV is pleased to announce the Oct2020-SP3 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-SP3 Bugfix Release (11.39.13) Bug Fixes * 7049: Implement DISTINCT for GROUP_CONCAT

1 0