DMLs are not returning an output while iterating the result using the conn.queryStream() iterator

[ghost]

Hi all,

if I run an "UPDATE ..." query and I run it using the .queryStream method and I try to iterate the returned rows, the iterator doesn't return the result.

I'm using the for await (const elm of conn.queryStream()) { ... } syntax for this. Apparently, the code never enters the cycle and the execution goes ahead, meaning that the AsyncGenerator's Promise is indeed resolved as the query's execution ends.

While it does if the query is a DDL. I'm using .queryStream() over a connection borrowed from the connection pool, as the documentation suggests.

Instead, when I was using mysql2 in the past, I could get the same output that I can get using the mysql cli. Something like this:

Query OK, 0 rows affected (0.00 sec)
Rows matched: 1  Changed: 0  Warnings: 0

Can you help me to obtain the same behaviour on this connector?

Thank you

[rusher]

There is indeed a difference in behavior compared to mysql2.
Just a question: why using streaming on a command that will have only one result ? streaming is to avoid loading lots of data into memory for big query.
anyway, I'll add that for compatibility.

[ghost]

Your suggestion makes definitely sense and I've already provided to implement it while we wait for this improvement to ship!

Thank you @rusher