April 2022 - users-list

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

24 Feb '24

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

2 2

DELETE INTO?
by Marc Lowenthal 25 Apr '22

25 Apr '22

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

2 1

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

21 Apr '22

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

2 4

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

08 Apr '22

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

1 0