Getting the wrong column about mysql HOT 8 CLOSED

What does the table schema look like and at any point are any of the values in any of the columns null, empty, or anything special like that?

from mysql.

Give me a few hours to reproduce that ;)

from mysql.

http://gist.github.com/552473

This is the schema. And no, all of the columns have normal values, no NULL or empty strings or something like that

from mysql.

Can you quantify "sometimes"? Is it happening in regular intervals, if so how big are they? This sounds like it could get fairly tricky to reproduce on my end without further information, but I'll have a look.

from mysql.

I ran into this too. It occurs rarely but that makes me sweat even more.

Testcase at http://gist.github.com/583048

from mysql.

I think it happens when the end of a string value aligns exactly to the end of a buffer, then the entire buffer is used but the parser state doesn't advance to COLUMN_VALUE_LENGTH. This causes the parser to assign an empty string to the next field and assign subsequent values to the wrong column.

We don't see it that often because generally an entire row is received in one buffer, so only the end of the last column's value aligns to the end of the buffer, but then there are no 'next' columns to f*ck up.

Very simple patch: http://gist.github.com/583103

from mysql.

Excellent test case, analysis and patch! Thank you so much. I just incorporated your changes and pushed out v0.5.0 to npm! Let me know if this works for you.

from mysql.

Yup it does. Thanks

from mysql.