- 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/). … [View More] ## 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 [View Less]

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 … [View More]

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 … [View More]

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 … [View More]

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 … [View More]

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 … [View More]

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 … [View More]

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 … [View More]

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/). … [View More]

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 … [View More]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. [View Less]

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 … [View More]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. [View Less]

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 … [View More]

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 … [View More]

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 … [View More]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. [View Less]

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! … [View More]

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 … [View More]

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 … [View More]

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 … [View More]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. [View Less]

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 … [View More]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. [View Less]

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 … [View More]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. [View Less]

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"> &… [View More]lt;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> [View Less]

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 … [View More]

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 … [View More]

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 … [View More]

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 … [View More]

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 … [View More]

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/… [View More]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` [View Less]

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-… [View More]

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 … [View More]

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 … [View More]

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 … [View More]

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/… [View More]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` [View Less]

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 … [View More]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. [View Less]

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 … [View More]

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.… [View More]

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 … [View More]

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 … [View More]

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 … [View More]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 [View Less]

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](… [View More]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 [View Less]

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](… [View More]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 [View Less]

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 … [View More]

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 … [View More]

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 … [View More]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 [View Less]

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.… [View More]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. [View Less]

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 … [View More]

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|… [View More]

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 … [View More]

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/… [View More]

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 … [View More]

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/… [View More]

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 … [View More]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 [View Less]

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); … [View More]

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. … [View More]

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 … [View More]

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 … [View More]

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 … [View More]

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 … [View More]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 [View Less]

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 == … [View More]

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, … [View More]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/ ==================== [View Less]

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 … [View More]

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 … [View More]

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 … [View More]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 [View Less]

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 … [View More]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 [View Less]

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 … [View More]

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+… [View More]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! [View Less]

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/… [View More]

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 … [View More]

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 … [View More]

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 … [View More]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) [View Less]

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? … [View More]

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 … [View More]

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 | +=================+=… [View More]

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 … [View More]

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

MonetDB-.Net
by Mitchell Weggemans 11 Feb '21

11 Feb '21

Hey, MonetDB.Net is an entirely community driven project. Therefore, I cannot 100% guarantee it is production ready. I made some effort into testing it however, and it worked fine. If you encounter any problems, please feel free to post them here or on StackOverflow, or even to propose changes over on the GitHub repo. Regards, Mitchell.

4 4

MonetDB-.Net
by imad hajj chahine 09 Feb '21

09 Feb '21

Hi, I am currently using Windows Monetdb ODBC driver to connect from .Net to a running monetdb server. Recently I found the github repo https://github.com/MonetDB/MonetDB-.Net and do some initial testing and it's far better in error reporting and support connection pooling. How mature is this .Net connector and is it recommended for usage in production environments and replace the ODBC driver? Is it the official connector for .Net and backed by the Monetdb team? Many thanks.

1 0

ODBC driver Error on Windows
by imad hajj chahine 08 Feb '21

08 Feb '21

Hi, After upgrading to the Oct 2020-SP2 (11.39.11) version the ODBC driver started to throw the following exception: ERROR [IM003] Specified driver could not be loaded due to system error 126: The specified module could not be found. (MonetDB ODBC Driver, C:\Program Files\MonetDB\MonetDB ODBC Driver\lib\MonetODBC.dll) Rolling back the driver to the version june 2020-SP1(11.37.11.01) the driver is working fine. Previously some driver releases missed the 2 libraries "libeay32.dll" and "… [View More]

2 3

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

28 Jan '21

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

2 1

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

25 Jan '21

The MonetDB team at MonetDB BV is pleased to announce the Oct2020-SP2 bugfix release of the MonetDB suite of programs. More information about MonetDB can be found on our website at <https://www.monetdb.org/>. For details on this release, please see the release notes at <https://www.monetdb.org/Downloads/ReleaseNotes>. As usual, the download location is <https://www.monetdb.org/downloads/>. Oct2020-SP2 Bugfix Release (11.39.11) SQL Frontend * CREATE [OR REPLACE] … [View More]

1 0

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

09 Dec '20

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

1 0

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

09 Dec '20

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

2 2

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

04 Dec '20

Hi, The below is from my colleague who is not a member on this list, so I'm sending on his behalf. I'm using MonetDB with MonetDB-PHP library. I have followed the documentation from: https://github.com/MonetDB/MonetDB-PHP Everything is working fine, but if I set parameter for timestamp type column I get the following error: Error from MonetDB: 42000!Wrong type for argument 1 of function call: char, expected timestamp For example, this is working: $result = $connection->Query(' … [View More]

2 1

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

01 Dec '20

The MonetDB bug tracker has been moved from our self-hosted bugzilla instance to github issues. All bug IDs have remained the same in the transition, making referencing bugs easier. The new bug tracker can be found at https://github.com/MonetDB/MonetDB/issues Don't forget to follow this tracker (if you're interested in doing that) or follow individual bugs. Due to the way we had to do the move, the old stars that you may have given to the MonetDB github repo have been lost, so please, … [View More]

1 0

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

29 Nov '20

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

1 1

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

24 Nov '20

The MonetDB team at MonetDB BV is pleased to announce the Oct2020-SP1 bugfix release of the MonetDB suite of programs. More information about MonetDB can be found on our website at <https://www.monetdb.org/>. For details on this release, please see the release notes at <https://www.monetdb.org/Downloads/ReleaseNotes>. As usual, the download location is <https://www.monetdb.org/downloads/>. Oct 2020-SP1 bugfix release (11.39.7) Bug Fixes * 6890: Add support of xz/… [View More]

1 0

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

20 Nov '20

Dear list, Please allow me to proudly share with you the news that Martin Kersten, the founding father of MonetDB, has just been appointed Knight in the Royal Order of the Netherlands Lion [1] as a recognition for his 45+ years contribution to the research, innovation, education and development of database management systems, the results of which have been reflected in MonetDB. However, Martin and the MonetDB team have always been keenly aware that all achievements of Martin&MonetDB … [View More]

1 0

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

19 Nov '20

Hi all -- Hopefully someone in this group can help me. :-) I am new to MonetDB and am having a problem setting up the connection for an SQL client. Part of me is wondering if the problem is related to using the latest version of MonetDB (Oct 2020) with this MonetDB JDBC driver (monetdb-jdbc-2.29.jre7.jar). I randomly chose SQuirrel on Windows and am open to alternatives. The connection I am trying to make is to MonetDB on Linux. I followed the instructions carefully at: https://… [View More]

4 8

sub-second epoch precision
by Karl Seguin 17 Nov '20

17 Nov '20

I couldn't find a nice way to turn a timestamp into a sub-second epoch value. What I came up with was: sys.epoch(t) * 1000000 + cast((("second"(t) - floor("second"(t)))) * 1000000 as int) Most functions seem to treat seconds as the lowest unit, e.g. extract(seconds...) and time_to_str Is there a better option that I'm missing? Thanks, Karl

1 0

changes with temporal types
by Roberto Cornacchia 03 Nov '20

03 Nov '20

Hi team, I like the Oct2020 release very much. It has some discontinuities with past releases, and that's ok. One that I find a bit too painful though is the stricter time and interval typing. Not that I am against it, it is now more SQL compliant. But perhaps the transition could have been a bit softer. It boils down to date arithmetics between temporal and numeric types. Something like this was allowed before: 1 + (date1 - date2) (integer + interval) As the release notes say, a new … [View More]

3 3

Github mirror
by Roberto Cornacchia 26 Oct '20

26 Oct '20

Hello, I was wondering, is the syncing of the github repository mirror not scheduled? I see that the latest commit on master is from today, but the latest commit on Oct2020 branch is from 14 days ago.

2 2

Announcement: New Oct2020 Feature release of MonetDB suite
by Sjoerd Mullender 19 Oct '20

19 Oct '20

The MonetDB team at MonetDB BV is pleased to announce the Oct2020 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/>. Oct 2020 feature release (11.39.5) MonetDB5 Server * The settings for … [View More]specifying how mserver5 should listen to "The Internet" have been overhauled. See the manual for details. In brief, mapi_autosense, mapi_ipv6 and mapi_open are gone. If mapi_listenaddr equals "localhost" or "all", we listen to both IPv4 and IPv6 (if available), if "127.0.0.1" or "0.0.0.0", we listen to IPv4 only, if "::1" or "::" we listen to IPv6 only. The first of each pair is loopback interface only, the second is all interfaces. If mapi_listenaddr is "none", then no IP port is opened, you need to use a UNIX domain socket. If mapi_port is 0, we let the operating system choose a free port (like mapi_autosense). Default behavior has not changed. Whole System * Finished a first version of the new monitoring function user_statistics(), which is only intended for the DBAs. For each database user who has logged in during the current mserver5 session, it returns "username": login name of the database user, "querycount": the number of queries this user has executed since his/her first login, "totalticks": the total execution time (in microsecond) of the queries ran by this user, "maxquery": the query with the longest execution time (if two queries have the same execution time, the newer overwrites the older), "maxticks": the execution time of the 'maxquery' (in microsecond), "started": the start timestamp of the 'maxquery', "finished": the finish timestamp of the 'maxquery'. * Removed support for LiDAR data, that is the SQL procedures sys.lidarattach, sys.lidarload, and sys.lidarexport. * The sys.queue() has been turned into a circular buffer to allow for inspection of both active, paused and recently executed queries. Client Package * mclient and msqldump now also look in $XDG_CONFIG_HOME for the monetdb configuration file. SQL Frontend * Extended the system monitor with a table-returning function user_statistics() which keeps some statistics for each SQL user, e.g. the user's query count, total time spent, and maximal query seen. * Removed '@' syntax used to refer into a variable in a query. It was a non-standard method, which was replaced by a schema addition to variables. Variables in the global scope now have schema. All default global variables are set under schema "sys". However variables inside PSM don't have a schema, because there are no transaction semantics inside PSM at the moment. * Removed declared variables and tables from the global scope. They were transaction agnostic and incompatible with the SQL standard, i.e. they are valid exclusively under PSM (e.g. functions, procedures and triggers). * Scoping semantics were added for both variables and tables. Variables with the same name at a query are now resolved under the following precedence rules: 1. Tables, Views and CTEs at the FROM clause. 2. Variable declared in the body of function/procedure, i.e. local variable. 3. Function/procedure parameter. 4. Variable from the global scope. Tables with the same name now have the following precedence rules at a SQL query: 1. Table declared in the body of function/procedure, ie local table. 2. Temporary table. 3. Table from the current session schema. This means the query: SELECT * FROM "keys"; will list keys from temporary tables instead of persisted ones, because "keys" table is available for both "sys" and "tmp" schemas. * The table returning function "var" was extended with more details about globally declared variables, namely their schema, type and current value. * Removed obsolete sys.getContent(url) function. * Removed obsolete json.output(json) function. * Removed compatibility between interval types and other numeric types in favor for a more strict SQL standard compliance. This means operations between temporal types and other numeric types such as INT and DECIMAL are no longer possible, instead use interval types. e.g. SELECT date '2020-01-01' + 1; now gives the error. Instead do: SELECT date '2020-01-01' + interval '1' day; if 1 was meant to be a day interval. Setting an interval variable such as the session's current timezone with a number e.g. SET current_timezone = 1; is no longer possible. Instead do SET current_timezone = interval '1' hour; Casting between interval and other numeric types is no longer possible as well, because they are not compatible. * Because of incompatibilities this change may create, if a user intends to convert a numeric value to an interval, the multiplication function can be used in the form: <numeric value> * interval '1' <interval length> e.g. 10 * interval '1' second = interval '10' second. As for the other way around, the 'EPOCH' option was added to the extract syntax. This option returns the number of milliseconds since the UNIX epoch 1970-01-01 00:00:00 UTC for date, timestamp and time values (it can be negative). Meanwhile, for day and second intervals, it returns the total number of milliseconds in the interval. As a side note, the 'EPOCH' option is not available for month intervals, because this conversion is not transparent for this type. * Made general logarithm function log(x,base) compliant with the SQL standard, by swapping the input parameters. Instead of log(x,base), now is log(base,x). Bug Fixes * 3553: All schema access to ubiquitous functions * 3815: Incorrect results when expression contains implicit float/integer conversions * 6415: Date arithmetic types are inconsistent * 6814: provide native implementations for scalar functions sys.degrees(rad) and sys.radians(deg) * 6843: function sys.getcontent(url) always returns "Feature not supported" * 6857: remove not implemented aggregate function json.output(js json) * 6870: Missing bulk operators * 6878: SQL Connection Error when running SELECT queries containing AND command * 6910: SQLancer query: 'bat.append' undefined * 6930: SQLancer crash on join with coalesce * 6931: Allow EDITOR to be used for the current command in mclient * 6935: Wrong result when dividing interval by literal float * 6937: Lost the microsecond precisions * 6938: Segmentation fault in MalOptimizer * 6939: Error in optimizer multiplex when selecting profiler.getlimit() or wlc.clock() or wlc.tick() or wlr.clock() or wlr.tick() * 6941: SELECT queries on remote table fail when using LIKE in WHERE conditions * 6943: JSON parser is too permissive * 6948: msqldump with Empty BLOBs cannot be imported * 6949: Loosing timing precision * 6950: redundant/replicated code line in gdk/gdk_hash.c * 6951: Use a different naming scheme for MAL blocks * 6954: FILTER functions no longer find their implementation * 6955: ROUND(DECIMAL, PRECISION) gives incorrect result with non-scalar precision parameter * 6960: implementation of log(arg1,arg2) function is not compliant with the SQL standard, arguments are switched * 6962: "SELECT * FROM ids LIMIT 1" produces: exp_bin: !ERROR: Could not find %173.id * 6964: Table returning function: Cannot access column descriptor * 6965: Crash when using distinct on the result of a table returning function * 6974: Oct2020-branch cannot attach and load FITS files * 6976: Oct2020: default dbfarm cannot be started * 6978: Oct2020: \d shows empty result in schema created by include sql script * 6979: timestamp add integer * 6980: Oct2020: wrong mel definition for str.epilogue [View Less]

1 0

Thread safety in python UDFs
by Ioannis Foufoulas 01 Oct '20

01 Oct '20

Hi, One question on python udfs. What about thread safety? In case of concurrent execution of numpy UDFs should the UDF developer use thread-safe structures or Monetdb handles this in some way? For example, pandas is not thread safe. This means that it should not be used in a UDF? Best, Yannis

2 1

Building MonetDBe from source
by Avik Sengupta 24 Sep '20

24 Sep '20

Hi, I've been trying to build MoneDBe from source, using Github master. I do not want to build the full executables, so I have used cmake --build . --target monetdbe With this, I am able to successfully build libmonetdbe.so. So that is great. However there does not seem to be an install-monetdbe or similar target. Running the `install` target tries to compile the whole application, which is not what I want. How do I copy the compiled artifacts (libmonetdbe.so and dependencies) to my install … [View More]

1 0

.mal and .sql files in Oct2020 lib folder
by Roberto Cornacchia 24 Sep '20

24 Sep '20

Hi there, I'm trying to compile from the Oct2020 branch and I have a question about the /lib64/monetdb5 folder. This folder used to contain .mal files. It also contained an autoload/ subfolder and a createdb/ subfolder (with .sql files). I don't see the same in the Oct2020 installation. I see that the content of /sql/scripts/CMakeLists.txt is entirely commented out. Is the installation of all these files temporarily disabled during development, or is this handled differently now? Roberto

4 4

Re: Internals of intermediate results in MonetDB
by Guodong Jin 24 Sep '20

24 Sep '20

Thanks! The point to MAL plan really helps me out! Best, Guodong On Sep 21, 2020, 06:00 -0400, users-list-request(a)monetdb.org, wrote: > Send users-list mailing list submissions to > users-list(a)monetdb.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.monetdb.org/mailman/listinfo/users-list > or, via email, send a message with subject or body 'help' to > users-list-request(a)monetdb.org > > You can reach the person managing the list … [View More]at > users-list-owner(a)monetdb.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of users-list digest..." > > > Today's Topics: > > 1. Internals of intermediate results in MonetDB (Guodong Jin) > 2. Re: Internals of intermediate results in MonetDB (Martin Kersten) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 20 Sep 2020 23:31:50 -0400 > From: Guodong Jin <guod.jin(a)gmail.com> > To: users-list(a)monetdb.org > Subject: Internals of intermediate results in MonetDB > Message-ID: <932d01d5-a742-4f57-8e19-ba7599667e42@Spark> > Content-Type: text/plain; charset="utf-8" > > Hi all, > > Thanks for your hard works on this great open source project. > I?m a student newly working on MonetDB to implement some research ideas, and I want to understand internals of how MonetDB chooses to materialize and how it represents intermediate results. > As I understand, table data and intermediate results in MonetDB are all stored as BATs, but I?m not sure if there are some special optimizations on BATs, rather than just array(s) of atoms. Here are two simple examples to elaborate my questions a little bit: > > ?? ?1.Given two tables,?Items(id, order, price, tax), and?Orders(id, discount). > ?? ? ? ? ?Items > ?? ? ? ? ? ? ? ? ?[I1, I2, I3, I4, I5, I6, I7, I8, I9, I10, I11...] > ?? ? ? ? ? ? ? ? ?[O3, O3, O3, O3, O3, O3, O3, O3, O3, O3, O4...] > ?? ? ? ? ? ? ? ? ?[10, 11, 20, 15, 110, 80, 90, 12, 13, 88, 30...] > ?? ? ? ? ? ? ? ? ?[0.1, 0.15, 0, 0.1, 0.1, 0.15, 0.11, 0.18, 0.10, 0.15, 0.20, ...] > ?? ? ? ? ?Orders > ?? ? ? ? ? ? ? ? ?[O1, O2, O3] > ?? ? ? ? ? ? ? ? ?[0.8, 0.9, 0.95] > > ?? ? ? ? ?When we perform a join between these two tables on the field `order` (one-to-many relationship represented by the primary-foreign key, O3 matches with [I1, I2, ?, I10]),?in the output intermediate BATs of the join, will MonetDB duplicate `O3` 10 times? Are there any optimizations currently in MonetDB to remove/reduce the duplication? > > ?? ?2. Given a table?item(id, price, tax), when MonetDB performs the filter `price<10` on the table,?will MonetDB actually copy all matched tuples into intermediate BATs? Or just keep a list of OIDs of matched tuples as references? > > Thanks! > > Best, > Guodong > [View Less]

1 0

Internals of intermediate results in MonetDB
by Guodong Jin 21 Sep '20

21 Sep '20

Hi all, Thanks for your hard works on this great open source project. I’m a student newly working on MonetDB to implement some research ideas, and I want to understand internals of how MonetDB chooses to materialize and how it represents intermediate results. As I understand, table data and intermediate results in MonetDB are all stored as BATs, but I’m not sure if there are some special optimizations on BATs, rather than just array(s) of atoms. Here are two simple examples to elaborate my … [View More]

2 1

Merge table error with one table
by Ioannis Foufoulas 17 Sep '20

17 Sep '20

Hi, we encounter an error when only one table is added to a merge table definition During a query like "select * from merge table” we get: “Table: missing ')'" Probably merge tables cannot contain just one table but the returned error looks like a syntax error. Some more info to reproduce: the table that has been added to the merge table is a remote table. Best, Yannis

3 4

Recommended compiler version and flags for Linux x86_64
by Daniel Glöckner 15 Sep '20

15 Sep '20

Hi, I'm currently building and testing MonetDB on CentOS7, x86_64. I was wondering about the recommended compiler version and compiler flags. So far I'm using gcc 9 and specifically enabled SSE3 extensions (though I did not notice any performance gain). Here's my cmake command cmake3 -DCMAKE_C_FLAGS="pthread -msse3 -O -Wall" -DCMAKE_INSTALL_PREFIX=../install ../MonetDB Is there a list of recommended compiler flags? Kind regards, Daniel

4 4

Nested tables?
by louie＠gmx.cn 14 Sep '20

14 Sep '20

Hi, Does MonetDB support nested tables? Oracle diagram for reference: https://docs.oracle.com/cd/B10501_01/appdev.920/a96594/adobjdes.htm#441615 Thanks, Louie

2 1

Default username and password: documented?
by Stefan Manegold 14 Sep '20

14 Sep '20

Hi, I just realize that, while the default (system-/admin-)username and password for a newly generated database in MonetDB are well known in the experienced MonetDB community, where do novice users find this information? I cannot find any explicit (or at least implicit?) documentation of this information, but maybe it's just that I fail to search properly? Any help is highly appreciated! Thanks! Best, Stefan -- | Stefan.Manegold(a)CWI.nl | DB Architectures (DA) | | www.CWI.nl/~manegold/ … [View More]

3 3

Why MonetDB uses Materialization
by Amit Pandey 11 Sep '20

11 Sep '20

Hey All, Thanks for the great open source project. So while going through some materials in a CMU DB course I saw it mentioned that MonetDB uses full materialization, and this is a bit weird since in c-store potentially scanning a billion columns a full materialization may take a lot of time and the classic volcano model might be better. Can you guys please explain the rationale ? These are the slides :- https://15445.courses.cs.cmu.edu/fall2019/slides/12-queryexecution1.… [View More]

3 7

Bad query performance after lots of updates
by Daniel Glöckner 01 Sep '20

01 Sep '20

Hi, select count(*) from table where field = 'some value'; --> a few ms update table set field = 'value'; --> update 2 million rows out of 1 billion rows select count(*) from table where field = 'some value'; --> almost a minute :( Analyze did not help and sys.vacuum could not be used as the table has indexes (foreign key). Re-starting the DB helped ;) What's the recommended way to make MonetDB perform well after lots of updates? Kind regards, Daniel

2 1

compilers
by Roberto Cornacchia 01 Sep '20

01 Sep '20

Hi, I was wondering whether anyone has run any benchmarks with MonetDB for testing the effect of compilation options. For example, any combination of * gcc vs clang * -O1 vs -O2 vs -O3 * -march and -mtune I am actually planning to do this myself, but knowing about any previous evidence (even anecdotal) would be helpful. Cheers, Roberto

1 0

custom joins in Jun2020
by Roberto Cornacchia 27 Aug '20

27 Aug '20

This is a question about join order. In general, about how it changed from Nov2019 to Jun2020 releases. In particular, with respect to custom joins (filter functions). With a schema: CREATE TABLE t1(s string); CREATE TABLE t2(s string); Consider the following 2 queries, which only differ for having swapped conditions: Q1: SELECT t1.s, t2.s FROM t1, t2 WHERE t1.s <> t2.s AND [t1.s] maxlevenshtein [t2.s, 1]; Q2: SELECT t1.s, t2.s FROM t1, t2 WHERE [t1.s] maxlevenshtein [t2.s, 1] AND t1.s … [View More]

1 1

Loading timestamps via Python loader functions
by Daniel Glöckner 26 Aug '20

26 Aug '20

Hi, there seems to be a limitation for Python-based loader functions wrt timestamps. Looking at the implementation in sql/backends/monet5/UDF/pyapi3/convert_loops.h suggests that timestamps are indeed not covered. Both of the the 2 following examples fail with "Failed conversion: MALException:pyapi3.eval:PY000!Unrecognized type. Could not convert to NPY_UNICODE.". CREATE LOADER array_loader() LANGUAGE PYTHON { from datetime import datetime _emit.emit( { 'a': [1,2,3], 'b': [datetime.… [View More]

1 0

result properties in pcre.c
by Roberto Cornacchia 25 Aug '20

25 Aug '20

Hi, I was looking at pcre.c for some inspiration and found something suspicious. At the end of both pcre_likeselect() and re_likeselect(): if (bn && !msg) { BATsetcount(bn, BATcount(bn)); /* set some properties */ bn->tsorted = true; bn->trevsorted = bn->batCount <= 1; bn->tkey = true; bn->tseqbase = bn->batCount == 0 ? 0 : bn->batCount == 1 ? * (oid *) Tloc(bn, 0) : oid_nil; } Which I read as: if everything went well, then the result is sorted and … [View More]

2 2

Re: Re: MonetDB on IBM Power architecture
by Daniel Glöckner 20 Aug '20

20 Aug '20

Hi, This looks very promising so far. Building on Power 8 was easy, just following the official guide from the wiki. https://www.monetdb.org/wiki/MonetDB:Building_from_sources So far I’ve only loaded larger amounts of data and the timings look good. Will perform more tests over the next days but overall this looks like absolutely usable for production. Kind regards, Daniel

1 0

JDBC Driver
by Walter Weinmann 19 Aug '20

19 Aug '20

Including the JDBC driver with gradle implementation 'monetdb:monetdb-java-lite:2.38' gives me: FAILURE: Build failed with an exception. * Where: Build file 'D:\SoftDevelopment\Projects\Konnexions\db_seeder\build.gradle' line: 66 * What went wrong: Could not determine the dependencies of task ':fatJar'. > Could not resolve all files for configuration ':runtimeClasspath'. > Could not find monetdb:monetdb-jdbc-new:2.37-SNAPSHOT. Searched in the following locations: - … [View More]

3 2

Re: Re: MonetDB on IBM Power architecture
by Daniel Glöckner 19 Aug '20

19 Aug '20

Hi, Thanks a lot for confirming this. We’ll perform some basic tests on our Power 8 system to see if we’re able to build and run it. Kind regards, Daniel

1 0

MonetDB on IBM Power architecture
by Daniel Glöckner 19 Aug '20

19 Aug '20

Hi folks, I was wondering if one could run MonetDB on IBM Power architecture (Power 8 and later). I guess there's no official build for this? Did anyone try this out? Kind regards, Daniel

2 1

java.sql.BatchUpdateException: Error(s) occurred while executing the batch, see next SQLExceptions for details
by Walter Weinmann 18 Aug '20

18 Aug '20

*Without addBatch / executeBatch my program runs without problems:* [main] Start [main] tickerSymbolExtern='monetdb' [main] Start MonetDB [main] database table COUNTRY - 200 rows in total [main] database table TIMEZONE - 11 rows in total [main] database table COUNTRY_STATE - 500 rows so far [main] database table COUNTRY_STATE - 600 rows in total [main] database table CITY - 500 rows so far [main] database table CITY … [View More] - 1000 rows so far [main] database table CITY - 1500 rows so far [main] database table CITY - 1800 rows in total [main] database table COMPANY - 500 rows so far [main] database table COMPANY - 1000 rows so far [main] database table COMPANY - 1500 rows so far [main] database table COMPANY - 2000 rows so far [main] database table COMPANY - 2500 rows so far [main] database table COMPANY - 3000 rows so far [main] database table COMPANY - 3500 rows so far [main] database table COMPANY - 4000 rows so far [main] database table COMPANY - 4500 rows so far [main] database table COMPANY - 5000 rows so far [main] database table COMPANY - 5400 rows in total [main] duration in seconds: 52 [main] End MonetDB [main] End *With addBatch / executeBatch and a batch size of 1000 I get the following error:* [main] Start [main] tickerSymbolExtern='monetdb' [main] Start MonetDB [main] database table COUNTRY - 200 rows in total [main] database table TIMEZONE - 11 rows in total [main] database table COUNTRY_STATE - 500 rows so far [main] database table COUNTRY_STATE - 600 rows in total [main] database table CITY - 500 rows so far [main] database table CITY - 1000 rows so far [main] database table CITY - 1500 rows so far java.sql.BatchUpdateException: Error(s) occurred while executing the batch, see next SQLExceptions for details at nl.cwi.monetdb.jdbc.MonetStatement.executeBatch(Unknown Source) at ch.konnexions.db_seeder.jdbc.AbstractJdbcSeeder.createDataInsert(AbstractJdbcSeeder.java:501) at ch.konnexions.db_seeder.jdbc.AbstractJdbcSeeder.createData(AbstractJdbcSeeder.java:404) at ch.konnexions.db_seeder.jdbc.AbstractJdbcSeeder.createData(AbstractJdbcSeeder.java:362) at ch.konnexions.db_seeder.DatabaseSeeder.main(DatabaseSeeder.java:141) Processing of the script was aborted, error code=1 *Both times the connection runs with autoCommit.* [View Less]

3 2

java.sql.SQLException: DROP USER: 'kxn_user' owns a schema
by Walter Weinmann 18 Aug '20

18 Aug '20

*The following SQL statements are executed successfully:* SELECT count(*) FROM sys.users WHERE name = 'kxn_user' DROP SCHEMA IF EXISTS kxn_schema CASCADE CREATE USER kxn_user WITH UNENCRYPTED PASSWORD 'monetdb' NAME 'Dbseeder User' SCHEMA sys CREATE SCHEMA kxn_schema AUTHORIZATION kxn_user ALTER USER kxn_user SET SCHEMA kxn_schema CREATE TABLE COUNTRY ( PK_COUNTRY_ID BIGINT NOT NULL PRIMARY … [View More]

2 1

New Elixir driver + some questions and feedback
by Karl Seguin 02 Aug '20

02 Aug '20

I've been working on a driver for Elixir (https://github.com/karlseguin/monet) It's immature, but in a decent enough state for our prototyping. Overall, I've been very pleased and excited about MonetDB. I wanted to share some observations from the perspective of both a newcomer and having developed a driver. First though, a couple questions: 1. I understand what a Q_BLOCK is, but I don't understand under what circumstances it happens. 2. Aside from the initial challenge response, it seems … [View More]like all messages from the server are _always_ in response to a query. This is different than, say, PostgreSQL which can push data to signal some change, outside of the typical request->response flow. Correct? As for my feedback: 1. The first and, by far, single biggest issue is with the text-base protocol. I'm sure this has been discussed before, and I doubt that I can add any new insight. But it was tedious to implement and error prone. We were initially considering storing large blobs in MonetDB (for a secondary purpose), but I'm now rethinking that idea because of the performance for serializing and deserializing the data. The rest of these issues are in no particular order. 2. I'm pretty sure if you send an invalid x command, the server goes haywire. The simplest way I found to reproduce this is to change the 's' to 'x' in the official Node client (https://github.com/MonetDB/monetdb-nodejs/blob/19f24ec16db70a26d0b11e51d77b…) and connect. The CPU load spikes and the logs are filled with: "createExceptionInternal: !ERROR: SQLException:SQLparser:42000!Unrecognized X command: SET TIME ZONE INTERVAL '-480' MINUTE;"" (I'm running: 17ab9b680ec55b342c08d034f2c5659a073cc74a) 3. Maybe this is naive, but I don't understand why this works: insert into x (time_col) values ('10:30:50') but this doesn't: exec 7('10:30:50') I was hoping I could ignore the response from a "prepare" (except for getting the id from the first line) and just encode based on the argument types, but no. I need the type AND precision so that I can do "time(3) '...'" or "blob '....'" etc. 4. Point 3 is made marginally worse because: prepare select 1 - ? returns 2 rows. I look for the suffix "NULL,\tNULL,\tNULL\t]" to tell which are "real" placeholders. I'm not sure if that's correct. 5. I was surprised to see dates with 1, 2 and 3 digit years. Making it 4 digits would make it ISO8601 compliant. 6. I was caught off guard by the fact that ab error can show up as part of what seems like a healthy response. Initially, I was just looking for a response that stars with !. But while testing, a concurrent create table failed and I got "&3 X Y\n!CODE!ERR\n". Is there a rule that can help me parse these efficiently? (like they'll always be on the first or 2nd line), or can they really show up anywhere? 7. Some of the drivers appear to be in bad shape. The node driver gets confused by my point 4 above and fails to handle it. It also doesn't support time or blob values, and tries to JSON the built-in Date object. I couldn't get the go driver to work at all (nil referencse trying to read rows). The ruby driver has no support for prepared statements and I'm pretty sure it doesn't return the correct value for: db.query("select '\\\\'") 8. While I'm probably wrong, I can't help but think that merging the functionalities of the monetdbd and monetdb binaries would streamline the experience for newcomers. Please don't interpret these as unkind criticisms of (or unhappiness with) MonetDB. Again, overall, very happy. [View Less]

2 1

Creation of a remote table overhead
by Ioannis Foufoulas 28 Jul '20

28 Jul '20

Hi, I am trying to develop a Python client which sends queries to different Monetdb servers and transfers the results between them using the remote tables functionalities. I’ve seen than my main overhead is execution of CREATE REMOTE TABLE statement. It requires 70-90msec so in cases with many transfers and fast and small queries this makes a difference. After looking at some older versions I’ve seen that the creation of a remote table was very fast before August 2018 (this is when … [View More]

4 7

MonetDB on GitHub
by Roberto Cornacchia 27 Jul '20

27 Jul '20

Hi, I was wondering whether the MonetDB repositories on GitHub (or any git-based platform) are, in your intentions, there to stay. That's because I'm planning to move our own fork from Mercurial to git. This would come very easy by using the GitHub repositories as upstreams. My second question though is: the git repositories are at this moment about 10 days behind. Is there a reason? Will that be improved? Thanks! Roberto

2 2

Announcement: New Jun2020-SP1 Bugfix release of MonetDB suite
by Sjoerd Mullender 27 Jul '20

27 Jul '20

The MonetDB team at MonetDB BV is pleased to announce the Jun2020-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/>. Jun 2020-SP1 bugfix release (11.37.11) MonetDB Common * Hash buckets come … [View More]in variable widths. But if a BAT grows long enough so that the BAT indexes that are stored in the buckets don't fit anymore, the buckets need to be widened. This is now fixed. Bug Fixes * 6844: sys.getUser('https://me:pw@www.monetdb.org/Doc') does not return the user: me * 6845: the url sys.get...(url) functions do not allow null as a parameter * 6858: json.keyarray(json '{ "":0 }') fails with error: Could not allocate space * 6859: only first character of the separator string in json.text(js json, sep string) is used * 6873: sys.hot_snapshot() creates incomplete snapshots if the write-ahead log is very large * 6876: tar files created by sys.hot_snapshot() produce warnings on some implementations of tar * 6877: MonetDB produces malformed LZ4 files * 6880: Left fuzzy queries are much slower than other fuzzy queries. * 6882: cgroups limits no longer respected? * 6883: SQLancer crash on delete query * 6884: SQLancer generates query with unclear error message * 6885: SQLancer causes assertion error on UTF8_strlen * 6886: SQLancer alter table add unique gives strange error message * 6887: SQLancer crash on complex query * 6888: SQLancer crash on cross join on view * 6889: SQLancer crash on long query * 6892: SQLancer crash on query with HAVING * 6893: SQLancer inner join reporting GDK error * 6894: SQLancer crash on rtrim function * 6895: SQLancer causing 'algebra.select' undefined error * 6896: SQLancer algebra.select' undefined 2 * 6897: SQLancer distinct aggregate with error on group by constant * 6898: SQLancer crash on join query * 6899: SQLancer TLP query with wrong results * 6900: SQLancer generated SIGFPE * 6901: SQLancer TLP query with wrong results 2 * 6902: SQLancer query: batcalc.between undefined * 6903: SQLancer calc.abs undefined * 6904: SQLancer aggr.subavg undefined * 6905: SQLancer TLP query with wrong results 3 * 6906: SQLancer crash on complex join * 6907: SQLancer algebra.select undefined * 6908: SQLancer inputs not the same size * 6909: SQLancer query with wrong results * 6911: SQLancer query: 'calc.bit' undefined * 6917: Decimal parsing fails * 6918: SQLancer query compilation error * 6919: SQLancer insert function doesn't handle utf-8 strings * 6920: SQLancer project_bte: does not match always * 6922: Timestamp columns not migrated to new format * 6923: Imprints data files for timestamp BAT not migrated to the new format * 6924: SQLancer query copy on unique pair of columns fails and complex query with GDK error * 6925: Count string rows in union of string tables leaks (RSS) memory * 6926: SQLancer query with wrong results * 6927: SQLancer inputs not the same size * 6928: SQLancer crash on coalesce * 6929: SQLancer calc.date undefined * 6932: Syntax error while parsing JSON numbers with exponent * 6934: sys.isauuid() returns wrong answer for some invalid uuid strings [View Less]

1 0

enhancements question
by ALEX OSSIPOV 25 Jul '20

25 Jul '20

Hi MonetDB Team I am very interested in pushing bug 6702 which is in fact an enhancement (was enhancement request) but seems to be more of a miss these days since all other competing products have it already implemented. What is decision process on prioritizing enhancements and how can a specific request be expedited/elevated? Love this product but can't survive without recursive support in modern analytics world. Regards Alex

2 1

MonetDb crashes on a join using date between from and until date
by Groot, Frank (Sociale Verzekeringsbank) 22 Jul '20

22 Jul '20

Hi all, We are using the June 2020 release, trying to query a table with 24 mio rows and join each row from this 'left' table with one row from a right table according to a specific join clause. This clause does not result in a carthesian product. The query structure is as follows: select left.* from myschema.mytable left inner join otherschema.yourtable right on left.somedatefield >= right.fromdate and left.somedatefield <= right.untildate where left.otherdatefield is null ; … [View More]

2 1

Partition pruning for merge tables
by Daniel Glöckner 22 Jul '20

22 Jul '20

Hi, looking at merge tables and the related query plans I was expecting the planner to skip tables depending on partition information and query predicates. I'm using the official example for merge tables: https://www.monetdb.org/blog/updatable-merge-tables CREATE MERGE TABLE splitted (stamp TIMESTAMP, val INT) PARTITION BY RANGE ON (stamp); CREATE TABLE first_decade (stamp TIMESTAMP, val INT); CREATE TABLE second_decade (stamp TIMESTAMP, val INT); CREATE TABLE third_decade (stamp TIMESTAMP, … [View More]val INT); ALTER TABLE splitted ADD TABLE first_decade AS PARTITION FROM TIMESTAMP '2000-01-01 00:00:00' TO TIMESTAMP '2010-01-01 00:00:00'; ALTER TABLE splitted ADD TABLE second_decade AS PARTITION FROM TIMESTAMP '2010-01-01 00:00:00' TO TIMESTAMP '2020-01-01 00:00:00'; ALTER TABLE splitted ADD TABLE third_decade AS PARTITION FROM TIMESTAMP '2020-01-01 00:00:00' TO RANGE MAXVALUE WITH NULL VALUES; INSERT INTO splitted VALUES (TIMESTAMP '2000-01-01 00:00:00', 1), (TIMESTAMP '2002-12-03 20:00:00', 2), (TIMESTAMP '2012-05-12 21:01:00', 3), (TIMESTAMP '2019-12-12 23:59:59', 4); INSERT INTO splitted VALUES (TIMESTAMP '2020-01-01 00:00:00', 5), (NULL, 6); When I trigger the following query I was expecting that only table second_decade would be used as Monet would be smart enough to check the partition information for each table. Kind regards, Daniel sql>plan select * from splitted where stamp = TIMESTAMP '2020-01-01 00:00:00'; +--------------------------------------------------------------------------------------------------------------------------------------+ | rel | +======================================================================================================================================+ | union ( | | | union ( | | | | project ( | | | | | select ( | | | | | | table(sys.first_decade) [ "first_decade"."stamp" as "splitted"."stamp", "first_decade"."val" as "splitted"."val" ] COUNT | | | | | ) [ "splitted"."stamp" = timestamp(7) "2020-01-01 00:00:00.000000" ] | | | | ) [ "splitted"."stamp", "splitted"."val" ], | | | | project ( | | | | | select ( | | | | | | table(sys.second_decade) [ "second_decade"."stamp" as "splitted"."stamp", "second_decade"."val" as "splitted"."val" ] COUNT | | | | | ) [ "splitted"."stamp" = timestamp(7) "2020-01-01 00:00:00.000000" ] | | | | ) [ "splitted"."stamp", "splitted"."val" ] | | | ) [ "splitted"."stamp", "splitted"."val" ], | | | project ( | | | | select ( | | | | | table(sys.third_decade) [ "third_decade"."stamp" as "splitted"."stamp", "third_decade"."val" as "splitted"."val" ] COUNT | | | | ) [ "splitted"."stamp" = timestamp(7) "2020-01-01 00:00:00.000000" ] | | | ) [ "splitted"."stamp", "splitted"."val" ] | | ) [ "splitted"."stamp", "splitted"."val" ] | +--------------------------------------------------------------------------------------------------------------------------------------+ 19 tuples clk: 2.428 ms [View Less]

2 4

Re: Re: Implementing bulk export to Parquet
by Daniel Glöckner 20 Jul '20

20 Jul '20

Hi, thanks for the implementation hint with Arrow C++, Anton. I’ve tried a similar approach using Pyarrow () and initial tests look promising. NumPy arrays can be written to Parquet quite easily: https://www.mail-archive.com/dev@parquet.apache.org/msg04506.html <https://www.mail-archive.com/dev@parquet.apache.org/msg04506.html> Kind regards, Daniel

1 0

BUG on last version?
by Ariel Abadi 20 Jul '20

20 Jul '20

Hi! Maybe somebody can help me to understand if there is a bug on the latest version or if it is a better way to solve this issue. Linux Centos 7 Monetdb version 11.37.7 (Jun2020) I have created a new fresh database to avoid any issue on the upgrade, and imported all the data. The DB seems to be working fine. We are using creating some dynamic queries, so the final query we need to run is the following: select sum(nrm_realmin) as nrm_realmin from sb_traf.nrm_20200716 as t0 where (… [View More]

2 1

Issues with None values handling in Python UDFs returning TABLE
by Daniel Glöckner 20 Jul '20

20 Jul '20

Hi, when testing TABLE-returning UDFs, I noticed that there are some issues with handling of None values from Python. Is there any magic approach on how to return NULLS / None values from such a UDF? Please see my examples below which are all not working ;) Kind regards, Daniel # 1 Does not work - Henk is just repeated in the second row drop function if exists python_table; CREATE FUNCTION python_table() RETURNS TABLE(name STRING, country STRING, age INTEGER) LANGUAGE PYTHON { result = … [View More]

1 0

Implementing bulk export to Parquet
by Daniel Glöckner 19 Jul '20

19 Jul '20

Hi, the project which I'm involved in would require us to integrate MonetDB with "big data technologies" so exporting data from MonetDB to Parquet for further processing in the big data tools would be an obvious choice. Can anyone guide me what it would mean to extend MonetDB with a writer for Parquet? It would be awesome if COPY INTO would be able to produce Parquet efficiently, e.g. using Arrow library: https://arrow.apache.org/docs/cpp/parquet.html Kind regards, Daniel

3 2

MonetDB/e and R
by Mark Clements 17 Jul '20

17 Jul '20

It is exciting to see the release of MonetDB/e - congratulations. I have two questions to offer. First, has anyone begun work on an R package? As a follow-up question if not, which of MonetDB.R, MonetDBLite or DuckDB packages for R would be a better starting point? Second, could someone kindly explain the potential advantages and disadvantages of using either MonetDB/e or DuckDB, please? They both seem to come from CWI, so this is a little confusing. Sincerely, Mark. När du skickar e-post … [View More]

3 2

PHP insert performance
by - - 16 Jul '20

16 Jul '20

I have run the series of INSERT tests in PHP for monetdb and SAP SQLAnywhere. The tests show: performance of the monetdb on INSERT operations is almost twice slower against SQLA with the equal conditions (DDL, index, data, autocommit, 10K records), monetdb is in in-memory mode . What can be a reason? p.s. It is not benchmark, I just used the SQLA test server already running. -- - -

4 12

News on MonetDB
by Martin Kersten 14 Jul '20

14 Jul '20

Hi, In recent weeks we have issued a few blog posts on the MonetDB site and announced them on Twitter. The latest one is a demonstration of MonetDB as a drop in library in Python. see https://monetdb.org/blog/taking-MonetDBe-for-a-taxi-ride Feedback on the embedded version of MonetDB is always welcome. regards, Martin Kersten

1 0

Error with concurrent inserts via PymonetDB mapi
by Ioannis Foufoulas 13 Jul '20

13 Jul '20

Hi, I have a weird error when I am sending the following queries in parallel from 2 different python clients with MAPI: insert into table1 select numpy_count(c1) as c1 from view; insert into table2 select numpy_count(c1) as c1 from view2; where numpy_count is: CREATE or replace AGGREGATE numpy_count(val INTEGER) RETURNS INTEGER LANGUAGE PYTHON { import time time.sleep(3) return val.size }; The error is: pymonetdb.exceptions.OperationalError: GDK reported error: GDKreleasesem:… [View More]

2 2

mserver5 options
by - - 12 Jul '20

12 Jul '20

Hi, How to pass/set mserver5 options via monetdb(d) ? I’m trying to get started monetdb in in-memory mode. mserver5 has option --in-memory Run database in-memory only however all attempts to pass it were unsuccessful. -- - -

2 4

Many aggregated columns / using custom aggregation function for pivot
by Daniel Glöckner 10 Jul '20

10 Jul '20

Hi, today I checked out how to implement custom aggregation functions in Python. Works pretty neat and scales well when you have few columns which you want to aggregate, however I have many :) Imagine that the following aggregate functions has variants which perform a similar iteration but call a different function (not sum). The call to numpy.unique() and the iteration would have to be performed for each aggregated column which is bad in terms of performance. Background: I have records in a … [View More]

1 0

Killing long running SQL queries
by Daniel Glöckner 09 Jul '20

09 Jul '20

Hi, sometimes things just go wrong ;) Is there a way to 1) list (long) running queries and 2) kill them? Kind regards, Daniel

2 1

Re: Re: Bit of documentation lacking (indexes, performance)
by gloeckner.daniel＠gmail.com 09 Jul '20

09 Jul '20

Hi, Thanks Martin Kersten, Alex Ossipov and Martin van Dinther for the valuable advice! It’s actually quite impressive to see how well MonetDB being a “knobless” system performs without any performance tuning. That’s what you do most of your day when using “big data” technologies from my experience 😉 but it’s of course not what you’re ultimately aiming to do… I think it could be considered as a unique selling point for MonetDB. Maybe the website should highlight this more and improve … [View More]

2 1

Bit of documentation lacking (indexes, performance)
by Daniel Glöckner 08 Jul '20

08 Jul '20

Hi, I'm currently in the process of evaluating MonetDB. Hats off for this great product! Very impressed by ease-of-use and performance so far. Looking for information what indexes are used by MonetDB I found a pretty empty page only: https://www.monetdb.org/Documentation/SQLReference/Indexes During our performance evaluation I was searching for common recipes to achieve good performance. Following page is unfortunately also under construction. https://www.monetdb.org/Documentation/… [View More]

4 3

Huge merovingian.log after update
by Lynn Carol Johnson 07 Jul '20

07 Jul '20

HI all – A week or so ago we ran an upgrade to the lastest monetdb June-2020 patch. Our db was 2 patches old. While the log showed no specific problems, the upgrade effected our databases in that 2 of them would crash when they were accessed, and the third one (the largest one) I could access but could not see any tables. I ended up “destroying” all the dbs and recreating them fomr the saved binary files. Now, we are getting disk full messages (the db is only read – no one is adding to it)… [View More]

3 5

inadvertantly last schema
by Lynn Carol Johnson 29 Jun '20

29 Jun '20

Hi all – I have a monetdb instance with a lot of tables and a lot of data. This data is organized into schemas. While logging on today as the admistrator, I inadvertently typed: sql>schema maizeFullGenome; syntax error, unexpected SCHEMA in: "schema" sql> Instead of “set schema maizeFullGenome;” This has apparently overwritten the data I had in my maizeFullGenome Schema. Is there anyway to get this back besides finding an old copy of the db? The following shows the schema as … [View More]

2 5

Grant access to sql system catalog
by Suresh Devarakonda 29 Jun '20

29 Jun '20

Hi, I just wanted to check if there is a way to grant access to system tables and views such as sys.tables and sys.schemas to the users other than granting "sysadmin" role. I am not sure what kind of privileges the sysadmin role possess so would like to find if there are other roles or privileges available to access system tables and views. [cid:image001.jpg@01D64952.B2EE5CC0] Suresh Devarakonda 84.51<http://www.8451.com/>° TDO - Database Support Team D: 513.632.3692 M: 859.512.… [View More]

2 1

Predicates in UDFs
by Oxana Dolmatova 25 Jun '20

25 Jun '20

Hello, Could you please explain why predicates with subqueries in UDFs do not work? For example, I have the following statements: create table itab (x int, y int); insert into itab values (1, 0); insert into itab values (2, 1); create function test1(n int) returns int begin while (n > 9) do set n = n -1; end while; return n; end; create function test2(n int) returns int begin while (n > (select 9 from itab) ) do set n = n -1; end while; return n; end; create function test3(n … [View More]

2 3

Re: MonetDB Table Append
by Niels Nes 22 Jun '20

22 Jun '20

On Mon, Jun 22, 2020 at 08:11:26PM +0400, Miro Mannino wrote: > Dear Niels Nes, > > We would like to insert data column by column, for various reasons. > > The problem is that if we create a larger table with column T1 and > column T2, and insert 1000 rows on column T1, then the next 1000 insert > on T2 are going to be appended, resulting in 1000 rows of (val, NULL) > followed by another 1000 rows of (NULL, val). We could do that if there > is an option to&… [View More]nbsp;INSERT INTO from the first row as well (ignoring > non-null values). > > In general, we are trying to use MonetDB taking advantage of a column > store DB, but we can't really insert a batch of values for one column > after another column due to the usual semantic of INSERT INTO that > works really in rows. > > Looking forward to hearing from you, Column by column inserts is indeed a problem with the sql language being row oriented. We do have some solution, ie binary copy into, but that maybe a bit too much for you. See https://www.monetdb.org/Documentation/Cookbooks/SQLrecipes/BinaryBulkLoad Niels > > Miro > > > > On Mon, Jun 22, 2020 at 8:02 PM Niels Nes <Niels.Nes(a)cwi.nl> wrote: > > Min > > Why don't you just create one larger table? > > Niels > > On 22 June 2020 14:59:44 CEST, Min Kyu Jung <mkj280(a)nyu.edu> wrote: > > To whom this may concern, > > I am Min, and I am currently utilizing MonetDB for a project > and I was wondering if there are any optimizations made in > MonetDB such that two tables with the same number of rows can > be joined together? > For example, consider the following two table: > CREATE TABLE t1(rowNumber, val); > WITH SERIES AS( SELECT * FROM generate_series(0, 10000)) > INSERT INTO t1 SELECT ROW_NUMBER() over (), rand() FROM series; > CREATE TABLE t2(rowNumber, val); > WITH SERIES AS( SELECT * FROM generate_series(0, 10000)) > INSERT INTO t2 SELECT ROW_NUMBER() over (), rand() FROM series; > > In this situation, I currently join the table as follows: > CREATE TABLE t3(row#, val1, val2); > INSERT INTO t3 SELECT ROW_NUMBER(), t1.val, t2.val FROM t1 > INNER JOIN t2 on t1.rowNumber = t2.rowNumber; > > Given that MonetDB is column-stored, I was wondering if there > is a simpler/faster/more optimized way of stitching the two > tables into one table. > > To be clearer, as of right now, I make sure all tables have the > rowNumber column. However, is there a way where I can join > multiple tables (all with the same number of rows) without > pre-generating rowNumber column for each table? > An example is this: > INSERT INTO t3 SELECT t1.val, t2.val FROM t1 INNER JOIN t2 on > row_number(t1) = row_number(t2); > > Sincerely, > Min > -- Niels Nes, CTO, MonetDB Solutions url: https://www.monetdbsolutions.com e-mail: Niels.Nes(a)monetdbsolutions.com [View Less]

2 1

MonetDB Table Append
by Min Kyu Jung 22 Jun '20

22 Jun '20

To whom this may concern, I am Min, and I am currently utilizing MonetDB for a project and I was wondering if there are any optimizations made in MonetDB such that two tables with the same number of rows can be joined together? For example, consider the following two table: CREATE TABLE t1(rowNumber, val); WITH SERIES AS( SELECT * FROM generate_series(0, 10000)) INSERT INTO t1 SELECT ROW_NUMBER() over (), rand() FROM series; CREATE TABLE t2(rowNumber, val); WITH SERIES AS( SELECT * FROM … [View More]

2 1

Announcement: New Jun2020 Feature release of MonetDB suite
by Sjoerd Mullender 03 Jun '20

03 Jun '20

The MonetDB team at MonetDB BV is pleased to announce the Jun2020 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/>. Jun 2020 feature release (11.37.7) MonetDB5 Server * The mserver5 option --… [View More]verbose (-v) was removed. A similar effect can be had by issuing the query CALL logging.setcomplevel('SQL_TRANS', 'INFO'); as the monetdb user. * The functions algebra.intersect, algebra.semijoin, and algebra.crossproduct have an extra argument, bool max_one, which indicates that there must be no more than one match in the join. * The example module opt_sql_append is not installed in the binary packages anymore. * Added mserver5 option (--dbtrace=<path>) in order to be able to specify the output file any produced traces. * Removed function bat.setKey(). * algebra.rangejoin now has two extra arguments: anti:bit and symmetric:bit. * Added session identifier, number of workers and memory claim to the sysmon queue. * The worker (number of threads), memory (in MB) and optimizer pipeline limits can now be set per user session basis. The query and session timeouts are now set in seconds. * With required privileges an user can set resource limits for a session. * There are now versions of group.(sub)group(done) that produce a single output containing just the groups. * algebra.join and algebra.leftjoin now have forms which return a single column. The column that is returned is the left column of the two column version. * The MAL profiler now assigns the SQL TRACE output to the client record thereby avoiding the interaction with other queries, but loosing insight of competing queries. The stethoscope should be used for that. SELinux Support * There was a problem with the MonetDB SELinux support on Fedora 32. That is fixed in this release. In order to do a proper upgrade of the package if you have already installed MonetDB-selinux on Fedora 32, you may need to uninstall (dnf remove) the old package and then install the new. Whole System * A new system to deal with debug output has been implemented. There is now an option --dbtrace to mserver5 that takes a file argument to which debug output is written. The default value is the file mdbtrace.log inside the database directory. This option can also be set through the monetdb program. * The home directory of the automatically created monetdb user was changed from /var/MonetDB to /var/lib/monetdb (RPM based systems only). This home directory is (currently) not used for anything, though. * Python 2 support has been removed. There is now only support for using Python 3. * Removed support for bam and sam files. * Added mserver5 option (--set raw_strings=true|false) and monetdb database property (raw_strings=yes|no) to control interpretation of strings. Merovingian * On Fedora and RHEL systems (not RHEL 6), if monetdbd runs under systemd, when the package is updated, monetdbd (and hence any mserver5 process it runs) is restarted. * Added dbtrace mserver5 option to the daemon in order to set mserver5's output directory for the produced traces. Client Package * The monetdb-client-tools (Debian/Ubuntu) and MonetDB-client-tools (Fedora/RH) containing the stethoscope, tachograph, and tomograph has been removed. A completely new version of stethoscope will be released to replace the old version. * Removed the possibility of using the MD5 checksum for authentication purposes. It was never actively used but was there as an option. Now the option has been removed. * Add port and host as fields in the .monetdb file. * Added 'sessionid' column to system function sys.queue(), so each query gets tagged with the current session identifier * Allow monetdb user to control session and query time out and selectively stopping a client sessions with a soft termination request. ODBC Driver * The NUMERIC and FLOAT types are now handled fully. Before only DECIMAL, FLOAT, and DOUBLE were handled fully. * Some bugs were fixed in the passing back and forth between application and server of values of type GUID (UUID). MonetDB Common * The functions BATintersect, BATsemijoin, and BATsubcross have an extra argument, bool max_one, which indicates that there must be no more than one match in the join. * The "unique" property on BATs was removed. The property indicated that all values in a BAT *had* to be distinct, but this was not actually used. * A new type of candidate list has been introduced. Candidate lists are used internally to specify which rows of a column participate in an operation. Before, candidate lists always contained a list of candidate row IDs. The new candidate list type specifies a list of row IDs that should NOT be considered (negative candidates). * The maximum number of BATs in the system has been increased for 64 bit architectures. * The hash tables used internally by the system now uses a technique based on Linear Hashing which allows them to grow gracefully. This means that hash tables aren't removed and recreated nearly as often anymore. This also meant that the hash table had to be split into two files, which means that after an upgrade the hash tables have to be recreated. * Implemented a version of BATproject, called BATproject2, with two "right" arguments which conceptually follow each other. * Removed MT_mmap and MT_munmap from the list of exported functions. Use GDKmmap and GDKmunmap with the same parameters instead. * Changed the interface of the atom "fix" and "unfix" functions. They now return a value of type gdk_return to indicate success/failure. * Removed the tunique property. The tunique property indicated that all values in the column had to be distinct. It was removed because it wasn't used. * BATrangeselect now has two extra arguments: anti and symmetric (both bool). SQL Frontend * Updating the value of a sequence now requires privilege on its own schema. * The sys.querylog_enable(threshold integer) now actually enables the querylog and uses a threshold in milliseconds. * Removed UNION JOIN statements. They were dropped by the SQL:2003 standard, plus MonetDB implementation was not fully compliant. * The OFFSET value in the COPY INTO query now counts uninterpreted newlines. Before it counted "unquoted record separators" which meant that if you had a single quote on a line that you want to skip, you could not use the feature. * Added support for FROM RANGE MINVALUE TO RANGE MAXVALUE and FROM RANGE MINVALUE TO RANGE MAXVALUE WITH NULL VALUES cases in partitioned tables by range (before they weren't). * Removed support for Python 2. Python 2 itself is no longer supported. Use Python 3 instead. Functions that were declared as LANGUAGE PYTHON2 or LANGUAGE PYTHON2_MAP are changed to LANGUAGE PYTHON and LANGUAGE PYTHON_MAP respectively (without changing the Python code). * Implemented 'covar_pop' and 'covar_samp' aggregate functions, as well as their window function counterparts. Implemented 'stddev_samp', 'stddev_pop', 'var_samp', 'var_pop', 'corr' and 'group_concat' window function correspondents. * Extended SQL catalog with CREATE WINDOW syntax for user-defined SQL:2003 window functions. At the moment, window functions must be defined on the backend engine, i.e. on this case MAL. In the current implementation, the backend code generation creates two additional columns of type lng with the start and end offsets for each row. * Added prepared_statements_args view, which details the arguments for the prepared statements created in the current session. * Added sys.prepared_statements view, which lists the available prepared statements in the current session. * Added deallocate statements with the syntax 'DEALLOCATE [PREPARE] { number | ALL }', to close an existing prepared statement or all, through the SQL layer. Previously this feature was available via MAPI exclusively with the "release" command. * Added support for raw strings using the syntax r'' or R''. This means that C-like escapes will remain uninterpreted within those strings. For instance SELECT r'\"' returns a string of length two. The user needs to escape single quotes by doubling them: SELECT r''''. * Implemented ROLLUP, CUBE and GROUPING SETS from SQL:1999. They define grouping subsets used with the GROUP BY clause in order to compute partial groupings. Also, the GROUPING aggregate was added. This aggregate is a bitmask identifying the grouping columns not present in the generated grouping row when used with the operators described above. * Updated user session procedures by adding the possibility to set properties based on a session identifier. Optimizer pipeline: sys.setoptimizer(int, string) Number of worker threads: sys.setworkerlimit(int, int) Memory limits (in MB): sys.setmemorylimit(int, int) Query timeout (in ms): sys.setquerytimeout(int, int) Session timeout (in ms): sys.setsessiontimeout(int, int) The first argument corresponds to the id of the session to modify, and these procedures are bound to the monetdb user exclusively. The versions of the mentioned procedures with just the second argument were added as well, where the changes are reflected in the current user session, and therefore every user can call them. * The procedures sys.settimeout(bigint), sys.settimeout(bigint,bigint) and sys.session(bigint) are now deprecated. Instead use sys.setquerytimeout and sys.setsessiontimeout mentioned above. * Added SQL procedure sys.hot_snapshot() which can be used to write a snapshot of the database to a tar file. For example, sys.hot_snapshot('/tmp/snapshot.tar'). If compression support is compiled in, snapshots can also be compressed ('/tmp/snapshot.tar.gz'). The tar file expands to a single directory with the same name as the database that was snapshotted. This directory can be passed directly as the --dbpath argument of mserver5 or it can be copied into an existing dbfarm and started from monetdbd. Bug Fixes * 6298: unexpectedly slow execution of SELECT length(fieldname) FROM tablename LIMIT 1 queries * 6401: Suspected memory leak in mserver5 when creating/dropping tables * 6687: Count distinct very slow and use too much the hard drive * 6723: columns aliases duplicates should not be allowed. automatic aliasing required. * 6731: Add system view to allow querying of available prepared statements and their parameters * 6732: Add SQL command to close a specific prepared statement * 6750: Executing a query on a non-existing column on a remote table crashes the remote server * 6785: function sys.isaURL(url) should have been declared as sys.isaURL(string) * 6808: reveal the alarm.sleep procedure in SQL * 6813: function not_uniques(bigint) returns error when called * 6818: usage of multiple column expressions in where-clause (f(a), f(b)) in (select a, b) causes assertion failure on mserver5 * 6821: Failed to start monetdb with embedded python * 6828: Server crashes when executing a window query with ordering by EXTRACT date * 6846: Global temporary table not accessible in other connections / sessions * 6847: A simple way of speeding up impscheck for dense canditers * 6850: Idle timestamp not set * 6851: json parser doesn't parse integers correctly * 6863: thash files not released upon drop table * 6864: (I)LIKE with multiple % doen't find matches [View Less]

1 0

Crashed Database
by Ariel Abadi 20 May '20

20 May '20

Hi! I have deployed several MonetDB databases on different customers, the database is excellent haven't had that much problems, but I'm starting feeling that the database is becoming "fragile" Yesterday I have 2 crashes... Firstly, a database of 2.4TB of data... Monet crashed... and the only information I have received was: ERR cli_mx[28693]: #main thread:!ERROR: BBPcheckbats: file /opt/monetdb/cli_mx/cli_mx/bat/52/5236.tail too small (expected 137803304, actual 137166848) 2020-05-19 11:10:… [View More]00 MSG cli_mx[28693]: !ERROR: BBPcheckbats: file /opt/monetdb/cli_mx/cli_mx/bat/52/5236.tail too small (expected 137803304, actual 137166848) 2020-05-19 11:08:11 ERR control[28629]: (local): failed to fork mserver: database 'cli_mx' has crashed after starting, manual intervention needed, check monetdbd's logfile (merovingian.log) for details Obviously that info Ive got it from merovingian.log.... so, which is the manual intervention needed... dont know! We run a backup all the nights (we rsync the database farm against backup server). Dont know the reason, but it seems that at moment of the backup, eventhought the database was working fine... The backup was done. So when I received the "crashed" notice.. I tried to recover from the backup.... but it seems the copy was already failing. So I had to start from zero... uploading all the information again. it was a very tought job, once I completed (at 1am in the morning), I stopped the db to do backup.... Again... the database has crashed!!!! never again started!!!! In this case the error was the following: 2020-05-19 23:57:52 MSG merovingian[2379]: sending process 2389 (database 'cli_mx') the TERM signal 2020-05-19 23:57:53 MSG merovingian[2379]: database 'cli_mx' has shut down 2020-05-19 23:57:53 MSG control[2379]: (local): stopped database 'cli_mx' 2020-05-19 23:57:54 MSG merovingian[2379]: database 'cli_mx' (2389) has exited with exit status 0 So the 3rd time, needed to upload the information again.. I have just finished!... Now, obviously I am scared to stop and start the db... and till this moment i dont have a backup of the farm directory. Can someone please help me to find the problem why the database has crashed? The only thing that I found on the /var/log/messages was the following (may be this may help to find the issue) May 19 23:03:49 mx-pve kernel: [4716718.867312] mserver5[19453]: segfault at 138 ip 00007fad7b66b1e9 sp 00007ffe648e5600 error 6 in lib_sql.so[7fad7b532000+1bc000] May 19 23:10:03 mx-monet kernel: [4717092.595561] mserver5[22348]: segfault at 138 ip 00007f07572d41e9 sp 00007ffd9f5aa950 error 6 in lib_sql.so[7f075719b000+1bc000] May 19 23:15:03 mx-monet kernel: [4717392.674941] mserver5[24044]: segfault at 138 ip 00007f4e7c0041e9 sp 00007ffeab6e8e90 error 6 in lib_sql.so[7f4e7becb000+1bc000] May 19 23:16:57 mx-monet kernel: [4717506.863046] mserver5[24675]: segfault at 138 ip 00007f8710d891e9 sp 00007ffc71a0e4a0 error 6 in lib_sql.so[7f8710c50000+1bc000] Do you have an idea what can I do ???! The version Im using is: v11.35.19 (Nov2019-SP3) on a Linux Centos 7. Ariel [View Less]

1 0

ILIKE Operator. Bad function?
by Ariel Abadi 20 May '20

20 May '20

Hi! May be some can help me. We are using the ILIKE operator to filter data. When we use a couple of "%" at a certain point the db stops filtering correctly. We started with *ILIKE '%guate%' *it found 7 records, then we changed to *ILIKE '%guate%**com% *it found 1 record (which is ok)... finally we changed to *ILIKE '%guate%mo%**com%**' *and now it didn't find anything :'( Please see the attached examples... *A*) sql>SELECT DISTINCT nts_area_name FROM sb_rmsv.nts_nt_sum_report WHERE … [View More]

4 6

Auto-scaling MonetDB cluster on AWS?
by Pascal Heus 18 May '20

18 May '20

Has anyone configured an scalable MonetDB using Docker cluster on Amazon Web Services or other cloud environment? I'm looking into setting this up for one of our project around COBID-19 and essentially need to: - have my number of MonetDB instances to go up and down with user demand - use a load balancer to spread user queries across multiple instances I had in mind that all the instances would just point to a single dbfarm directory (all the user queries are read only), but is this an … [View More]

2 1

MonetDB Cluster size
by 逄振洲 11 May '20

11 May '20

i am very interested in using MonetDB as OLAP solution，But now I have a few questions。 1. MonetDB cluster the largest scale ? 2. any customer case study ?

1 0

Integer divided by integer never produces a real number
by Groot, Frank (Sociale Verzekeringsbank) 23 Apr '20

23 Apr '20

Hi, Can you tell me which of the following division outcomes is expected behaviour? --Division -- outcome select 10/3, -- 3 10/3.0, -- 3.333 10.0/3, -- 3.333 cast(10 as decimal(18,2))/3, -- 3.333 cast(10 as decimal(18,0))/3, -- 3 cast(10 as decimal(18,0))/3.0 -- 3.333 ; Personally, I would have expected all of the outcomes to be real numbers and not integers. Can you tell me if that is a realistic … [View More]

3 4

conditional DDL statements
by Roberto Cornacchia 22 Apr '20

22 Apr '20

Hi, I am afraid I know the answer to this already ("not supported"), but I wanted to check with you guys. Perhaps someone has smart workaround? Essentially what I would like to do is something like: IF condition THEN CREATE FUNCTION ....; As far as I know, flow control statements are only allowed inside functions/procedures. However, CREATE statements are not allowed inside functions/procedure. So I don't see any way to do what I wrote above. Notice, I am aware of CREATE OR REPLACE. What I'… [View More]

4 6

Integer divided by integer never produces a real number
by Groot, Frank (Sociale Verzekeringsbank) 22 Apr '20

22 Apr '20

Hi, Can you tell me which of the following division outcomes is expected behaviour? --Division -- outcome select 10/3, -- 3 10/3.0, -- 3.333 10.0/3, -- 3.333 cast(10 as decimal(18,2))/3, -- 3.333 cast(10 as decimal(18,0))/3, -- 3 cast(10 as decimal(18,0))/3.0 -- 3.333 ; Personally, I would have expected all of the outcomes to be real numbers and not integers. Can you tell me if that is a realistic … [View More]

1 0

Compilation error macOS Catalina
by Ying Zhang 16 Apr '20

16 Apr '20

Hai all, Compiling MonetDB Mercurial source on macOS Catalina (10.15.4) results in the following error: /Users/jennie/monet/Nov2019/common/utils/mcrypt.c:476:3: error: 'CC_MD5_Final' is deprecated: first deprecated in macOS 10.15 - This function is cryptographically broken and should not be used in security contexts. Clients should migrate to SHA256 (or stronger). [-Werror,-Wdeprecated-declarations] MD5_Final(md, &c); ^ /Applications/… [View More]

2 1

sql.init() is gone?
by Torsten Grust 14 Apr '20

14 Apr '20

Dear MonetDB friends, I am about to start the next semester of my DB implementation course here at U Tübingen. The course peeks at the internals of a variety of DBMSs, PostgreSQL and MonetDB5 in particular. The discussion in that course relies on being able to use the functions in the MAL 'sql' module directly such that students can understand how SQL queries are compiled into sequences of MAL statements. MAL scripts that have worked perfectly for this in the past now already stop at the … [View More]

2 2

SQL script autoload
by Roberto Cornacchia 14 Apr '20

14 Apr '20

Hi, Is there something similar to the lib/autoload folder, but for SQL scripts? My use case is: I have a bunch of UDFs. A SQL script defines their SQL interfaces The script is in lib/createdb. Sometimes I make changes to those UDFs, and their interfaces need to be updated. But my the script is only run on DB creation, so I have to manually go thorough all existing databases and run the script. The script is in a way idempotent, because it uses CREATE OR REPLACE, so I don't mind running it … [View More]

2 1

New client library for PHP
by Tamas Bolner 10 Apr '20

10 Apr '20

Hi, I spent the past nights creating a client library for PHP, because I found too many problems with the official one. Just for the heads up: https://github.com/bolner/MonetDB-PHP-Deux Happy Easter! Tamas

1 0

RE: System Catalog - Objects creation date and time.
by Suresh Devarakonda 08 Apr '20

08 Apr '20

Hi, I just wanted to see when the objects such as tables created in MonetDB. I have looked at below note, but couldn't find the catalog tables that provides the table creation time so wondering if MonetDB has that capability. Can someone let me know at the earliest. Your early response is very much appreciated. https://www.monetdb.org/Documentation/SystemCatalog [cid:image002.jpg@01D60C19.28554180] Suresh Devarakonda 84.51<http://www.8451.com/>° TDO - Database Support Team D: … [View More]

2 1

Running two databases with forward set to redirect (monetdbd)
by stephenb 08 Apr '20

08 Apr '20

We have an environment that does not support Unix domain sockets well. We thus configured monetdbd with forward=redirect, as we note from the monetdbd man page that "for local databases, the proxy method uses a UNIX domain socket feature" We can create two database, but trying to connect (on the default 50000 port) to them only the first-started database is available. If we try to connect to the second we get the error "request for database 'dev_sb2', but this is database 'dev_sb', did you … [View More]

2 2

Fwd: [Help] create a new db user but need to add prefix 'sys.' in order to execute timestamp_to_str() function
by Kevin Chen 07 Apr '20

07 Apr '20

Hi, I have a new db user created by following scripts: CREATE USER "imdb" WITH PASSWORD 'imdb' NAME 'IMDB Explorer' SCHEMA "sys"; CREATE SCHEMA "imdb" AUTHORIZATION "imdb"; ALTER USER "imdb" SET SCHEMA "imdb"; When I tried to execute the function "timestamp_to_str", I have to add "sys." prefix to make it effective. "date_trunc" also needed to do so. The default user "monetdb" can run the function directly without the prefix. What should I do to perform the same way as user "monetdb" ? sql>… [View More]

2 1

Fwd: BULK UPLOAD very poor performance
by Ariel Abadi 01 Apr '20

01 Apr '20

Hi! After a big battle against the DB, I found 2 issues. 1) Running the COPY RECORDS FROM *STDIN *and from *FILE*. Is totally different in terms of performance. While the first one last 24 minutes, the second one last only *90 secs.* 2) As I had generated all those files thru msqldump (which it states the "CREATE TABLE" instruction and then the COPY RECORDS)... I try ro run the COPY *XXXX OFFSET *RECORDS (in order to avoid the create table statement)... and the query, because of the word "… [View More]STDIN" in the file. It was not OFFSETTING all the rows I was asking for. I hope I've been clear... if not please let me know! Ariel On Tue, Mar 24, 2020 at 11:33 PM Martin Kersten <martin.kersten(a)cwi.nl> wrote: > Hi > > I am not sure what issue you are now dealing with, but since you are a > company > that seems to use (or considering) MonetDB in your commercial offerings, > I gladly refer you to MonetDBSolutions(*), where we can give you the > commercial > support needed to diagnose your issues. > > regards Martin > > (*) https://www.monetdbsolutions.com/ > > On 24/03/2020 23:55, Ariel Abadi wrote: > > Thanks Martin for your prompt response > > But I did and msqldump from other database, and now the upload is being > done thru the BULK LOAD. > > > > /COPY 14173375 RECORDS INTO "sb_traf"."nrm_20180818" FROM stdin USING > DELIMITERS '\t','\n','"';/ > > > > > > Any other idea ? :'( > > > > > > > > > > On Tue, Mar 24, 2020 at 7:37 PM Martin Kersten <martin.kersten(a)cwi.nl > <mailto:martin.kersten@cwi.nl>> wrote: > > > > Hi, > > > > given the numbers I suspect you are loading them as SQL insert > statements under autocommit mode, > > Please read the documentation on Bulk loading. > > > > regards,Martin > > Sent from my iPad > > > >> On 24 Mar 2020, at 23:12, Ariel Abadi <aabadi(a)starbi.com <mailto: > aabadi(a)starbi.com>> wrote: > >> > >> > >> Hi! > >> Maybe somebody can help me, please! > >> > >> I'm trying to upload into Monet a file with 14MM records. Is taking > more than *24 minutes.* > >> It is a fresh new database. > >> > >> Enclosed you will find the server configuration. > >> > >> Monetdb Version Nov2019-SP3 > >> > >> > >> *[root@mn tmp]$ lscpu* > >> Architecture: x86_64 > >> CPU op-mode(s): 32-bit, 64-bit > >> Byte Order: Little Endian > >> CPU(s): 40 > >> On-line CPU(s) list: 0-39 > >> Thread(s) per core: 2 > >> Core(s) per socket: 10 > >> Socket(s): 2 > >> NUMA node(s): 2 > >> Vendor ID: GenuineIntel > >> CPU family: 6 > >> Model: 85 > >> Model name: Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz > >> Stepping: 4 > >> CPU MHz: 800.479 > >> BogoMIPS: 4400.00 > >> Virtualization: VT-x > >> L1d cache: 32K > >> L1i cache: 32K > >> L2 cache: 1024K > >> L3 cache: 14080K > >> NUMA node0 CPU(s): > 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38 > >> NUMA node1 CPU(s): > 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39 > >> Flags: fpu vme de pse tsc msr pae mce cx8 apic sep > mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe > syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts > rep_good nopl xtopology nonstop_tsc > >> cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est > tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe > popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm > 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 > >> invpcid_single pti intel_ppin ssbd mba ibrs ibpb stibp tpr_shadow > vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep > bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx smap > clflushopt clwb intel_pt avx512cd avx512bw > >> avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc > cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts pku ospke md_clear > flush_l1d > >> > >> > >> *[root@mn tmp]$ cat /proc/meminfo* > >> > >> MemTotal: 83886080 kB > >> MemFree: 10535812 kB > >> MemAvailable: 80159744 kB > >> Buffers: 0 kB > >> Cached: 69623932 kB > >> SwapCached: 0 kB > >> Active: 6625436 kB > >> Inactive: 63737872 kB > >> Active(anon): 324456 kB > >> Inactive(anon): 417184 kB > >> Active(file): 6300980 kB > >> Inactive(file): 63320688 kB > >> Unevictable: 0 kB > >> Mlocked: 5320 kB > >> SwapTotal: 8388604 kB > >> SwapFree: 8381988 kB > >> Dirty: 220 kB > >> Writeback: 0 kB > >> AnonPages: 13626052 kB > >> Mapped: 186368 kB > >> Shmem: 1800 kB > >> KReclaimable: 4134960 kB > >> Slab: 0 kB > >> SReclaimable: 0 kB > >> SUnreclaim: 0 kB > >> KernelStack: 16720 kB > >> PageTables: 56500 kB > >> NFS_Unstable: 0 kB > >> Bounce: 0 kB > >> WritebackTmp: 0 kB > >> CommitLimit: 74123472 kB > >> Committed_AS: 18337812 kB > >> VmallocTotal: 34359738367 kB > >> VmallocUsed: 415836 kB > >> VmallocChunk: 0 kB > >> Percpu: 39552 kB > >> HardwareCorrupted: 0 kB > >> AnonHugePages: 0 kB > >> ShmemHugePages: 0 kB > >> ShmemPmdMapped: 0 kB > >> CmaTotal: 0 kB > >> CmaFree: 0 kB > >> HugePages_Total: 0 > >> HugePages_Free: 0 > >> HugePages_Rsvd: 0 > >> HugePages_Surp: 0 > >> Hugepagesize: 2048 kB > >> Hugetlb: 0 kB > >> DirectMap4k: 816396 kB > >> DirectMap2M: 82513920 kB > >> DirectMap1G: 52428800 kB > >> > >> > >> > >> > >> _______________________________________________ > >> users-list mailing list > >> users-list(a)monetdb.org <mailto:users-list@monetdb.org> > >> https://www.monetdb.org/mailman/listinfo/users-list > > _______________________________________________ > > users-list mailing list > > users-list(a)monetdb.org <mailto:users-list@monetdb.org> > > https://www.monetdb.org/mailman/listinfo/users-list > > > > > > _______________________________________________ > > users-list mailing list > > users-list(a)monetdb.org > > https://www.monetdb.org/mailman/listinfo/users-list > > > [View Less]

5 11

BULK UPLOAD very poor performance
by Ariel Abadi 24 Mar '20

24 Mar '20

Hi! Maybe somebody can help me, please! I'm trying to upload into Monet a file with 14MM records. Is taking more than *24 minutes.* It is a fresh new database. Enclosed you will find the server configuration. Monetdb Version Nov2019-SP3 *[root@mn tmp]$ lscpu* Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 40 On-line CPU(s) list: 0-39 Thread(s) per core: 2 Core(s) per socket: 10 Socket(s): 2 … [View More]NUMA node(s): 2 Vendor ID: GenuineIntel CPU family: 6 Model: 85 Model name: Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz Stepping: 4 CPU MHz: 800.479 BogoMIPS: 4400.00 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 1024K L3 cache: 14080K NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single pti intel_ppin ssbd mba ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts pku ospke md_clear flush_l1d *[root@mn tmp]$ cat /proc/meminfo* MemTotal: 83886080 kB MemFree: 10535812 kB MemAvailable: 80159744 kB Buffers: 0 kB Cached: 69623932 kB SwapCached: 0 kB Active: 6625436 kB Inactive: 63737872 kB Active(anon): 324456 kB Inactive(anon): 417184 kB Active(file): 6300980 kB Inactive(file): 63320688 kB Unevictable: 0 kB Mlocked: 5320 kB SwapTotal: 8388604 kB SwapFree: 8381988 kB Dirty: 220 kB Writeback: 0 kB AnonPages: 13626052 kB Mapped: 186368 kB Shmem: 1800 kB KReclaimable: 4134960 kB Slab: 0 kB SReclaimable: 0 kB SUnreclaim: 0 kB KernelStack: 16720 kB PageTables: 56500 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 74123472 kB Committed_AS: 18337812 kB VmallocTotal: 34359738367 kB VmallocUsed: 415836 kB VmallocChunk: 0 kB Percpu: 39552 kB HardwareCorrupted: 0 kB AnonHugePages: 0 kB ShmemHugePages: 0 kB ShmemPmdMapped: 0 kB CmaTotal: 0 kB CmaFree: 0 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB Hugetlb: 0 kB DirectMap4k: 816396 kB DirectMap2M: 82513920 kB DirectMap1G: 52428800 kB [View Less]

2 2

Slowdown behaviour after loading large amounts of data
by stephenb 23 Mar '20

23 Mar '20

We believe we might be observing the behaviour described here: https://www.monetdb.org/blog/monetdb-sql-transaction-management-scheme Specifically “At certain intervals, if the database is idle, the store manager will merge the updates from the WAL into the primary storage” We perform some heavy updates to the database (we have experimented with putting these in a single transaction or having separate transactions for each, but the behaviour is the same). The updates are basically … [View More]

1 0

stethoscope tool
by Suresh Devarakonda 12 Mar '20

12 Mar '20

Thank you Sjoerd Mullender. I am able to install it. ====== Doing sudo yum install /usr/bin/stethoscope should do it. That will install the package MonetDB-client-tools. On 09/03/2020 16.11, Suresh Devarakonda wrote: > Hi, > > > > I would like to use the stethoscope tool to monitor the performance of > queries. But, I do not find the tool in the MonetDB software that I > installed on my server. Can you help me to get the stethoscope tool. > > … [View More]

1 0

stethoscope tool
by Suresh Devarakonda 09 Mar '20

09 Mar '20

Hi, I would like to use the stethoscope tool to monitor the performance of queries. But, I do not find the tool in the MonetDB software that I installed on my server. Can you help me to get the stethoscope tool. [root@xxxxxx ~]# yum list installed |grep -i monet MonetDB.x86_64 11.35.9-20191218.el7 @monetdb MonetDB-SQL-server5.x86_64 11.35.9-20191218.el7 @monetdb MonetDB-client.x86_64 11.35.9-20191218.el7 @monetdb MonetDB-client-odbc.… [View More]

2 1

SP2 R integration
by ALEX OSSIPOV 22 Feb '20

22 Feb '20

I am not able to get R part working in latest SP2 and getting this error: LoaderException:loadLibrary:Loading error failed to open lib rary rapi (from within file '/usr/lib64/monetdb5/lib_rapi.so'): libR.so: cannot open shared object file: No such file or directory I use Centos 7 package MonetDB-R.x86_64_11.35.15-20200217.el7 and wonder if it was build with --enable-R-shlib option. SP1 did not have this problem Thanks Alex

2 2

Announcement: New Nov2019-SP2 Bugfix release of MonetDB suite
by Sjoerd Mullender 21 Feb '20

21 Feb '20

The MonetDB team at MonetDB BV is pleased to announce the Nov2019-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/>. Nov 2019-SP2 bugfix release (11.35.15) Bug Fixes * 6805: Using the cascade … [View More]

1 0

dropped functions
by ALEX OSSIPOV 18 Feb '20

18 Feb '20

I noticed every time Monetdb service is bounced all created functions disappear from database. Is it a bug or a way functions are handled in MonetDB? Thanks Alex.

2 1

search links are broken
by ALEX OSSIPOV 17 Feb '20

17 Feb '20

All links in Search results point to localhost:8080 instead of site. Can it be fixed? Thanks Alex

2 1

Include additional libraries
by Oxana Dolmatova 13 Feb '20

13 Feb '20

Hello, Could you tell what would be the easiest way to include additional libraries into the compilation process of MonetDB? More specifically I'm interested in calling MKL operations inside BAT Algebra operations. For example, mkl standalone operation of QR decomposition (in file mkl_qr.c all the additional headers are included) is compiled as follows: gcc -c mkl_qr.c gcc -o mkl_qr mkl_qr.o -L${MKLROOT}/lib/intel64 -Wl,--no-as-needed -lmkl_intel_ilp64 -lmkl_gnu_thread -lmkl_core -lgomp -… [View More]

1 0

How can i change plan choice according new constraint
by DEMBELE Simon Pierre 10 Feb '20

10 Feb '20

hello, I want to know if it is possible to change how monetdb choose a plan by adding new contraints. -- Simon

2 2

A bug occurs when query logging is enabled
by Hanfeng Chen 09 Feb '20

09 Feb '20

Hello, The bug can be reproduced on a standard TPC-H database with scale factor 1. A query returns NULL after query logging is enabled. The computer we use has Intel i7-8700K (12 cores) and 32GB RAM. Please see the details below. >> mclient -d tpch1 -t performance Welcome to mclient, the MonetDB/SQL interactive terminal (Nov2019-SP1) Database: MonetDB v11.35.9 (Nov2019-SP1), 'mapi:monetdb://tigger:50000/tpch1' FOLLOW US on https://twitter.com/MonetDB or https://github.com/MonetDB/… [View More]

2 1

Re: pymonetdb issue
by alexo15＠comcast.net 04 Feb '20

04 Feb '20

That would be great Thank you Pedro Sent from Xfinity Connect App ------ Original Message ------ From: ferreira To: ALEX OSSIPOV, Communication channel for MonetDB users Sent: February 4, 2020 at 1:42 AM Subject: Re: pymonetdb issue Hello Alex, The pymonetdb developer merged a patch with IPv6 support, which will be available at pymonetdb's next release. As for the R client, it is maintained by a volunteer that has not been active in the MonetDB community lately. I can ask him for it. Beset … [View More]

1 0

pymonetdb issue
by ALEX OSSIPOV 04 Feb '20

04 Feb '20

Hi All I installed pymonetdb v 1.2.1 and trying to connect to remote server MonetDB v11.35.3 (Nov2019) listening on IPV6 only. I have got next error in python client: >>> mapi_connection.connect(hostname="<server_name>", port=xxxxx, username="monetdb", password="monetdb", database="demo", language="sql", unix_socket=None, connect_timeout=-1) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/local/lib/python3.7/site-packages/pymonetdb/… [View More]

2 3

Python3 packages for epel
by ALEX OSSIPOV 31 Jan '20

31 Jan '20

I cannot seem find MonetDB-python packages in MonetDB EPEL 7/8 directories. Does it mean it is still work in progress ? Thanks Alex

2 2

Logs on Windows
by Илья Хайбуллин 27 Jan '20

27 Jan '20

Sometimes the MonetDB server just shuts down. I want to find at least some information about what happens before the shutdown. Please tell me how you can turn on logs on Windows or in some other way see what happens before shutting down. MonetDB 5 server 11.35.9 (Nov2019-SP1) (64-bit) Copyright (c) 1993 - July 2008 CWI Copyright (c) August 2008 - 2019 MonetDB B.V., all rights reserved Visit https://www.monetdb.org/ for further information Found 32.0GiB available memory, 8 available cpu cores … [View More]

1 0

MonetDB crashing due to out of memory - monetdbd[2247] 1.7 (Aug2018-SP2)
by Suresh Devarakonda 22 Jan '20

22 Jan '20

Thank you Ying and Jenin. I am going to upgrade the MonetDB as you suggested and then go from there. Can you please let me know where can I find the upgrade procedure. Thank you for your help in advance. Suresh Devarakonda 84.51° TDO - Database Support Team D: 513.632.3692 M: 859.512.1839 A: 100 W. 5th Street, … [View More]Cincinnati, Ohio 45202 Cincinnati | Chicago | New York | Portland Facebook LinkedIn Instagram Twitter Please consider the environment before printing this email. -----Original Message----- From: users-list <users-list-bounces+suresh.devarakonda=8451.com(a)monetdb.org> On Behalf Of users-list-request(a)monetdb.org Sent: Friday, January 17, 2020 6:00 AM To: users-list(a)monetdb.org Subject: users-list Digest, Vol 89, Issue 6 Send users-list mailing list submissions to users-list(a)monetdb.org To subscribe or unsubscribe via the World Wide Web, visit https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.monet… or, via email, send a message with subject or body 'help' to users-list-request(a)monetdb.org You can reach the person managing the list at users-list-owner(a)monetdb.org When replying, please edit your Subject line so it is more specific than "Re: Contents of users-list digest..." Today's Topics: 1. Re: MonetDB crashing due to out of memory - monetdbd[2247] 1.7 (Aug2018-SP2) (Ying Zhang) ---------------------------------------------------------------------- Message: 1 Date: Thu, 16 Jan 2020 12:01:27 +0100 From: Ying Zhang <Y.Zhang(a)cwi.nl> To: Communication channel for MonetDB users <users-list(a)monetdb.org> Subject: Re: MonetDB crashing due to out of memory - monetdbd[2247] 1.7 (Aug2018-SP2) Message-ID: <E6A3FCCA-8023-4EBD-AF7A-CF89F615B2D8(a)cwi.nl> Content-Type: text/plain; charset=utf-8 Hai Suresh, First of all, I?d recommend you to upgrade your MonetDB installation to the most recent one, i.e. Nov2019-SP1. There are many improvements related to your problem since Aug2018-SP2. Also, the version you?re using is no longer supported by the open-source team. Please let us know if upgrade helps. But below, a bit more info. inlined. > On 15 Jan 2020, at 23:44, Suresh Devarakonda <Suresh.Devarakonda(a)8451.com> wrote: > > Hi, > > The Moentdb is crashing every couple of weeks due to out of memory in our environment. Did it really crash, or did MonetDB give error messages and stop executing the query? Crash always indicates a problem in MonetDB, but if it?s the second case, it?s expected. > What I have noticed that MonetDB is eating memory and not releasing it at all once we brought up the MonetDB server. I am not sure if this is how MonetDB works or is it a bug. MonetDB is supposed to free up the memory when it no longer use it, which often happens towards the end of a query execution. For further investigation, we need more information after you have upgraded to Nov2019-SP1. In general, we?ll need information with which we can reproduce the problem, e.g. data + queries. > This is running on monetdbd[2247] 1.7 (Aug2018-SP2) version. Also wondering is there way to limit the memory usage of MonetDB. Please beware that depending on your data sizes and (concurrent) queries, MonetDB might run faster into out-of-memory problem, if you limit the amount of memory it may use, How about putting MonetDB in a VM? There are also some undocumented kernel configurations for this, which we don?t recommend to our users lightly? > > Can you guys help me to resolve this issue. If you need professional support, please contact the supporting company MonetDB Solutions. Regards, Jennie > > [root@xxx ~]# monetdb status > name state health remarks > INVPRDB R 6h 67% 3d mapi:monetdb://xxxxx:50000/INVPRDB > FSPPRDB R 6h 50% 6w mapi:monetdb://xxxxx:50000/FSPPRDB > [root@xxxxx ~]# free -g --- Current utilization > total used free shared buff/cache available > Mem: 31 0 22 0 7 30 > Swap: 3 0 3 > > > <image003.png> > > > > > > <image002.jpg> > Suresh Devarakonda > 84.51? > TDO - Database Support Team > D: 513.632.3692 > M: 859.512.1839 > A: 100 W. 5th Street, Cincinnati, Ohio 45202 > > Cincinnati | Chicago | New York | Portland > Facebook LinkedIn Instagram Twitter > Please consider the environment before printing this email. > > > _______________________________________________ > users-list mailing list > users-list(a)monetdb.org > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. > monetdb.org%2Fmailman%2Flistinfo%2Fusers-list&data=02%7C01%7Csures > h.devarakonda%408451.com%7Cae946815e409491cb83d08d79b3c9c2c%7C5f9dc6bd > f38a454a864cc803691193c5%7C0%7C0%7C637148556952386018&sdata=3JmWyH > MNaeMNrBp8vX%2FAYES%2By%2FDqNHqGmE%2FKX%2F%2F4m%2Bs%3D&reserved=0 ------------------------------ Subject: Digest Footer _______________________________________________ users-list mailing list users-list(a)monetdb.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.monet… ------------------------------ End of users-list Digest, Vol 89, Issue 6 ***************************************** [View Less]

2 2

Re: embedded python in latest release
by alexo15＠comcast.net 21 Jan '20

21 Jan '20

That was it. I was missing python packages Thank you Panos ------ Original Message ------ From: Panagiotis Koutsourakis To: users-list(a)monetdb.org Sent: January 21, 2020 at 7:54 AM Subject: Re: embedded python in latest release Hello Alex, make sure that you have the MonetDB-python or MonetDB-python3 packages installed: dnf install MonetDB-python or dnf install MonetDB-python3 Also you will need to notify the MonetDB server that you want to start with embedded python support. If you are … [View More]starting the server using the MonetDB daemon, you need to set the relevant property for your database: monetdb set embedpy=true <database> or monetdb set embedpy3=true <database> If you are starting the server by hand, then mserver5 --dbpath=/path/to/database --set embedded_py=2 or mserver5 --dbpath=/path/to/database --set embedded_py=3 Best regards, Panos. On 1/21/20 5:11 AM, ALEX OSSIPOV wrote: Roberto I have all mentioned packages installed. I do not have any issues with R though. Centos based instance also works fine. Thanks Alex On January 20, 2020 at 3:49 AM Roberto Cornacchia <roberto.cornacchia(a)gmail.com> wrote: Alex, Do you have packages python3-devel python3-numpy (python2-devel python2-numpy for python 2) installed in your Fedora system? Yes, you can import what you like in the body of your function, as long as the package is installed in your system. Roberto On Sun, 19 Jan 2020 at 00:12, ALEX OSSIPOV < alexo15(a)comcast.net mailto:alexo15@comcast.net > wrote: I am having problem enabling embedded python in latest realease, MonetDB 5 server v11.35.9 (Nov2019-SP1) My 64bit Fedora environment has multiple versions of both python 2 and 3 wih 32 and 64 bit libs. MonetDB was installed following https://www.monetdb.org/downloads/Fedora/ with additional SELinux. I tried random_integers function from documentation with both embedpy=true and embedpy3=true separately but getting the same type of error: SQL Error [22000]: TypeException:user.s10_0[9]:'pyapi3.eval' undefined in: X_10:bat[:int] := pyapi3.eval(0x559cb0440270:ptr, "{ \n return numpy.random.randint(low, high, size=(amount,))\n}\n;":str, X_7:int, X_8:int, X_9:int); Both py2 and py3 versions work fine on my computer. How do I properly point to a specific python version to be used by MonetDB? Are there any specific env variables that should be set prior to installation/db creation? I tried to define PYTHONPATH but it did not help. Aside question: Can additional modules be imported in function body for PYTHON type functions or does it only work with numpy? Thanks Alex _______________________________________________ users-list mailing list users-list(a)monetdb.org mailto:users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list _______________________________________________ users-list mailing list users-list(a)monetdb.org https://www.monetdb.org/mailman/listinfo/users-list _______________________________________________ users-list mailing list users-list(a)monetdb.org https://www.monetdb.org/mailman/listinfo/users-list [View Less]

1 0

embedded python in latest release
by ALEX OSSIPOV 21 Jan '20

21 Jan '20

I am having problem enabling embedded python in latest realease, MonetDB 5 server v11.35.9 (Nov2019-SP1) My 64bit Fedora environment has multiple versions of both python 2 and 3 wih 32 and 64 bit libs. MonetDB was installed following https://www.monetdb.org/downloads/Fedora/ with additional SELinux. I tried random_integers function from documentation with both embedpy=true and embedpy3=true separately but getting the same type of error: SQL Error [22000]: TypeException:user.s10_0[9]:'pyapi3.… [View More]

3 3

MonetDB crashing due to out of memory - monetdbd[2247] 1.7 (Aug2018-SP2)
by Suresh Devarakonda 16 Jan '20

16 Jan '20

Hi, The Moentdb is crashing every couple of weeks due to out of memory in our environment. What I have noticed that MonetDB is eating memory and not releasing it at all once we brought up the MonetDB server. I am not sure if this is how MonetDB works or is it a bug. This is running on monetdbd[2247] 1.7 (Aug2018-SP2) version. Also wondering is there way to limit the memory usage of MonetDB. Can you guys help me to resolve this issue. [root@xxx ~]# monetdb status name state health … [View More]

2 1

Monetdb crashed issue
by Kalaiarasi Gowtham 14 Jan '20

14 Jan '20

Hi, Currently, we are trying to start the database created in monetdb using the following command monetdb start <dbname> starting database 'dbname'... FAILED start: starting '<dbname>' failed: database '<dbname>' has crashed after starting, manual intervention needed, check monetdbd's logfile (merovingian.log) for details Getting logs as follows [root@localhost mydbfarm]# tail -f merovingian.log 2020-01-14 14:56:20 MSG merovingian[19527]: database '<dbname>' (19757) … [View More]

2 1