- developers-list - monetdb.org

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

**Unlocking Success in Nursing Education: The Comprehensive Guide to BSN Writing Services**
by noheta1148＠morxin.com 15 Jun '24

15 Jun '24

**Unlocking Success in Nursing Education: The Comprehensive Guide to BSN Writing Services** The pursuit of a Bachelor of Science in Nursing (BSN) is a commendable endeavor, marking a significant step toward a rewarding and impactful career in healthcare. However, the journey is often challenging, demanding not only practical skills and <a href="https://bsnwritingservices.com/">take my online nursing class</a> clinical knowledge but also exceptional academic writing abilities. From research papers and essays to clinical case studies and capstone projects, the array of writing assignments can be overwhelming. This is where professional BSN writing services come into play, providing crucial support to nursing students striving for academic excellence. ### The Importance of Writing in BSN Programs Writing is a fundamental component of BSN programs, serving multiple purposes: 1. **Knowledge Application**: Writing assignments allow students to apply theoretical knowledge to real-world scenarios, enhancing their understanding and retention of nursing concepts. 2. **Critical Thinking**: Crafting well-structured papers fosters critical thinking and analytical skills, essential for clinical decision-making and problem-solving. 3. **Communication Skills**: Effective writing is integral to professional communication in nursing, whether it's documenting patient care, writing reports, or engaging in interdisciplinary collaboration. 4. **Professional Development**: Through reflective writing and research, students develop a deeper awareness of their practice, ethics, and professional growth. ### The Role of BSN Writing Services BSN writing services provide specialized assistance to nursing students, ensuring they can meet the rigorous academic standards of their programs while managing the demands of clinical practice and personal commitments. These services are typically offered by experienced writers with backgrounds in nursing and healthcare, who understand the intricacies of nursing education and the expectations of academic institutions. ### Benefits of BSN Writing Services 1. **Expertise and Experience**: Professional writers bring a wealth of knowledge and experience in nursing, ensuring that your assignments are accurate, relevant, and insightful. They are familiar with nursing terminology, evidence-based practice, and ethical considerations. 2. **Customized Support**: BSN writing services offer tailored assistance based on your specific requirements, academic level, and institutional guidelines. This personalized approach ensures that the content is aligned with your <a href="https://bsnwritingservices.com/capella-4050-assessment-1/">capella 4050 assessment 1</a> writing style and academic goals. 3. **Time Management**: Balancing coursework, clinical rotations, and personal life can be challenging. Writing services help alleviate this burden by delivering high-quality papers within stipulated deadlines, allowing you to focus on other critical aspects of your education. 4. **Plagiarism-Free Content**: Reputable writing services guarantee original, plagiarism-free content, supported by thorough research and proper citations. This ensures your work maintains academic integrity and meets the standards of your institution. 5. **Confidentiality**: Your privacy is paramount. Trustworthy BSN writing services prioritize confidentiality, protecting your personal information and academic reputation through secure communication channels and data protection measures. ### Types of BSN Writing Services BSN writing services cover a broad range of academic needs, including but not limited to: 1. **Research Papers**: Comprehensive research papers involve literature reviews, data analysis, and critical evaluation of nursing studies. Professional writers can help you develop a coherent and compelling argument, supported by current evidence and scholarly sources. 2. **Case Studies**: Writing detailed case studies requires an in-depth understanding of patient scenarios, diagnosis, treatment plans, and nursing interventions. Expert writers can assist in presenting these complex cases clearly and systematically. 3. **Essays and Reflection Papers**: Whether it's an opinion piece, a reflective essay on clinical experiences, or a discussion on nursing ethics, writing services can help articulate your thoughts and insights effectively. 4. **Capstone Projects**: Capstone projects are culminating assignments that integrate theoretical knowledge with practical application. Writing services can guide you through this comprehensive project, ensuring it showcases your mastery of nursing concepts and skills. 5. **Theses and Dissertations**: For those pursuing advanced research, writing a thesis or dissertation involves extensive research, critical analysis, and original contributions to the field of nursing. Professional writers can support you at every stage, from proposal development to final editing. ### How to Choose the Right BSN Writing Service Selecting the right BSN writing service is crucial for ensuring the quality <a href="https://bsnwritingservices.com/capella-4040-assessment-2/">capella 4040 assessment 2</a> and reliability of the assistance you receive. Here are key factors to consider: 1. **Reputation and Reviews**: Research the service provider’s reputation by reading reviews and testimonials from past clients. Positive feedback and high ratings are indicators of reliable and high-quality service. 2. **Writer Qualifications**: Ensure that the writers have relevant credentials, such as advanced degrees in nursing or related fields, and significant experience in academic writing. Qualified writers are better equipped to understand and meet the specific demands of nursing assignments. 3. **Customization and Communication**: Choose a service that offers direct communication with writers and allows for customization of assignments. The ability to request revisions and provide feedback ensures that the final product meets your expectations. 4. **Pricing and Payment Options**: Transparent pricing structures and secure payment methods are essential for a trustworthy service. Compare pricing among different providers to find a service that offers good value without compromising quality. 5. **Guarantees**: Look for guarantees such as plagiarism-free content, confidentiality, adherence to deadlines, and satisfaction guarantees. These assurances reflect the service’s commitment to quality and customer satisfaction. ### Specialized Writing Needs in BSN Programs 1. **Evidence-Based Practice**: BSN programs emphasize the importance of evidence-based practice (EBP) in nursing care. Writing services can help students analyze research studies, integrate evidence into practice, and discuss the implications for patient outcomes. This includes systematic reviews, meta-analyses, and clinical guidelines. 2. **Clinical Reflections**: Reflective writing is a key component of nursing education, promoting self-awareness and professional growth. BSN writing services can assist students in articulating their clinical experiences, exploring challenges, and identifying areas for improvement. 3. **Ethical Considerations**: Nursing ethics are integral to professional practice. Writing services ensure that assignments discussing ethical dilemmas, decision-making frameworks, and patient advocacy are well-researched and thoughtfully presented. ### The Process of Working with BSN Writing Services Engaging with a BSN writing service typically involves the following steps: 1. **Initial Consultation**: The process begins with an initial consultation where you discuss your assignment requirements, deadlines, and any specific guidelines provided by your institution. This helps the service understand your needs and tailor <a href="https://bsnwritingservices.com/capella-4060-assessment-1/">capella 4060 assessment 1</a> their assistance accordingly. 2. **Writer Assignment**: Based on your requirements, the service assigns a qualified writer with relevant expertise in nursing and academic writing. You may have the option to choose your writer based on their qualifications and past work. 3. **Research and Writing**: The writer conducts thorough research, utilizing credible sources to develop a well-structured and coherent paper. They ensure that the content is original, accurate, and aligns with your academic goals. 4. **Draft Review and Feedback**: You receive a draft of the assignment for review. This allows you to provide feedback, request revisions, and ensure that the paper meets your expectations. Direct communication with the writer facilitates this collaborative process. 5. **Final Delivery**: Once all revisions are made and you are satisfied with the final product, the completed assignment is delivered to you. The service ensures that the paper is properly formatted, cited, and ready for submission. ### Conclusion: Investing in Your Academic and Professional Future In conclusion, professional BSN writing services offer invaluable support to nursing students navigating the complexities of their academic journey. By leveraging the expertise of qualified writers, you can enhance your understanding of nursing concepts, improve your writing skills, and achieve academic success. Whether you're facing challenges with complex assignments, struggling with time management, or seeking to elevate your academic performance, BSN writing services provide practical solutions tailored to your educational needs. Choosing a reputable BSN writing service ensures that you receive high-quality, customized assistance that aligns with your academic goals and career aspirations. Embrace the opportunity to collaborate with experts who share your passion for nursing and are committed to your success in the field. By investing in BSN writing services, you’re not just completing assignments; you’re investing in your future as a competent and compassionate nursing professional. Seize the opportunity to excel in your BSN program, contribute to evidence-based practice, and make a positive impact in healthcare. With the right support and guidance, you can achieve your educational goals and embark on a rewarding career dedicated to improving patient outcomes and advancing the field of nursing. --- This extended content provides a comprehensive overview of BSN writing services, emphasizing their benefits, specialized services, and considerations for choosing the right provider, while also detailing the process of working with such services to support nursing students' academic and professional development.

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

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

New Dec2023 stable branch created
by Sjoerd Mullender 13 Nov '23

13 Nov '23

I have created a new stable branch for the next feature release. This branch was created in order to stabilize the code before the feature release. From now on *only* bug fixes may go to this new stable branch. I reserve the right to undo any changes that do not comply with this rule. I also reserve the right to admit changes that are not strictly bug fixes. The name for the branch is Dec2023. So in each of your stable checkout directories you can do hg pull hg update -rDec2023 to update to this new branch. -- Sjoerd Mullender

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

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