- 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