There is a bug here: MySQLProtocolParser::parser_error_packet() doesn't understand non-SQL errors, i.e. errors that do not have this format:
# Error packet structure: # Offset Bytes Field # ====== ================= ==================================== # 00 00 00 01 MySQL proto header (already removed) # ff Error (already removed) # 0 00 00 Error number # 4 23 SQL state marker, always '#' # 6 00 00 00 00 00 SQL state # 16 00 ... Error message
Connection errors, for example, don't have a SQL state, they have only FF, error number, then error message.
There is a bug here: MySQLProtocolPa rser::parser_ error_packet( ) doesn't understand non-SQL errors, i.e. errors that do not have this format:
# Error packet structure: ======= ======= ======= ======= =
# Offset Bytes Field
# ====== ================= =======
# 00 00 00 01 MySQL proto header (already removed)
# ff Error (already removed)
# 0 00 00 Error number
# 4 23 SQL state marker, always '#'
# 6 00 00 00 00 00 SQL state
# 16 00 ... Error message
Connection errors, for example, don't have a SQL state, they have only FF, error number, then error message.