-
Notifications
You must be signed in to change notification settings - Fork 335
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
Handle max_allowed_packet client-side #40
Comments
For efficiency in the typical use case, perhaps we could only |
What about cases where the client has upped it's
Maybe a better approach is to record number of bytes sent in the packet, and throw an Outer Exception if packet size was > 4MB with "Exception after submitting XXMB Packet, ensure |
MySQL Server does send a final packet with the contents
|
Fixed in 0.16.1. |
If a packet that is larger than
max_allowed_packet
(a server-defined variable) is sent, the server will reset the connection and send an error packet with the responseGot a packet bigger than 'max_allowed_packet' bytes
. However, once this happens the connection is destroyed and the client can't recover.Additionally, it's a waste of time to send the query to the server when we know it'll be rejected. By running
SHOW VARIABLES
when the connection is established, we could get the value ofmax_allowed_packet
, and check packets to ensure they don't exceed that length before sending them.The text was updated successfully, but these errors were encountered: