Douglas Wilson

Hi @avnersorek ! It would be really neat if someone could put together a flamegraph of what Node.js is spending it's time doing during your query, however 115k rows is...

Thank you so much, @avnersorek ! So according to the flamegraph, most of the time is taking up by v8 setting properties on object (i.e. within v8 itself from us...

Unless you're talking about a different issue in this thread from the OP, I think the provided flame graphs are pretty straight forward for where the bottleneck is, so I...

Nice! It would be very interesting to know if this impacts the wall clock of large query results, but fixing scheduling lock ups is more important than raw throughput for...

My understanding is that workers threads are not made for parsing, either. This is because they run in a separate v8 isolate, so all the parsing work done there would...

I am working through this module prs and issues this week.

Hi @AgnisLV in the MySQL protocol, the `insertId` is always returned as a BIGINT no matter the query. The `bigNumberStrings` is specifically around the typecasting of columns, not of the...

AFAIK there is no loss in the value. Can you provide a reproduction for the precision loss you are seeing so we can take a look?

The hard part about this is that all this module does right now is implement the MySQL protocol, and supporting `DELIMITER` means that the module would have to implement and...

Hi @kpetrow , the code above has a lot of issues, the easiest to see are the following: 1. The occurrence of `ADELIMITER $$` will incorrectly change the delimiter to...