I get the same. With MonetDB v11.41.14: sql>COPY SELECT * FROM tst INTO '/tmp/cars_out.csv' USING DELIMITERS ',' , '\n' , '"'; 1 affected row sql> With MonetDB v11.43.9 (Jan2022-SP1): sql>COPY SELECT * FROM tbl INTO '/tmp/cars_out.csv' USING DELIMITERS ',' , '\n' , '"'; sql> The resulting CSV file is correct. I don't if the lacking of "1 affected row" with Jan2022-SP1 is expected. I'll ask the colleagues. - Jennie

On 14 Feb 2022, at 13:47, Ariel Abadi wrote:

Hi All! I'm resending to the new user list.

BR Ariel

---------- Forwarded message --------- From: Ariel Abadi mailto:aabadi@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 mailto:users-list@monetdb.org>

Hi All! We found a problem on the new version 11.43.5 (Jan2022).

We have some processes that run the COPY SELECT INTO to "move" data from monetdb to other different databases. We are expecting to receive an "answer" from monetdb affected, when the export finishes, like in the example below that informes "3 affected rows" sql>COPY SELECT * FROM cars INTO '/tmp/cars_out.csv' USING DELIMITERS ',' , '\n' , '"'; 3 affected rows While we run the same query on the new server, mclient/monetdb is not returning anything like the image below. sql>COPY SELECT * FROM cars INTO '/tmp/cars_out.csv' USING DELIMITERS ',' , '\n' , '"'; sql> Does anybody have the same issue? Am i doing something wrong? Thks a lot in advance! Ariel _______________________________________________ users-list mailing list -- users-list@monetdb.org To unsubscribe send an email to users-list-leave@monetdb.org