-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
select varchar - thinks the package is incomplete while it's actually complete #18
Comments
I cannot test the case right now, but I noticed that a packet is not checked by calling |
I'm seeing this issue here too. Field is a varchar(256) in my case and if it's sufficiently long the query will just hang within the loop. Any fixes or ideas what to do to work around? |
fixed decoding LCB value for fields > 250 bytes. according to this doc: http://dev.mysql.com/doc/internals/en/event-content-writing-conventions.html Current implementation ignored this and was hanging waiting for more packets when VARCHAR was larger than 250 bytes. There is also parseLCB function that is doing this exactly, but it seems to be not used since commit 01b30f1 this probably fixes mysql-d#18
@simendsjo: Your sample code doesn't reproduce the issue for me even if I insert a row with the maximum length, 64 bytes. However, it does hang for me if I change it to varchar(256) and insert a row with at least 251 bytes. Is that perhaps what you meant? If so, then it should be fixed now, via #40. Can you verify? |
Pinging @simendsjo: Since I (still) can't reproduce the exact original problem with varchar(64), but can verify that #40 does fix it for varchar(256) and a row with >=251 bytes, I'm going to go ahead and assume this issue is fixed and close the ticket. Please re-open if the problem still occurs. |
EDIT: I wrote the wrong compiler version
I'm not really sure what is causing this as I no longer remember the protocol.
This is running on linux x64, mariadb 5.5.32, dmd 2.063.2.
Could anyone test this on mysql? It's up for grabs if anyone wants it :)
The text was updated successfully, but these errors were encountered: