linux-traipu team mailing list archive
-
linux-traipu team
-
Mailing list archive
-
Message #01812
[Bug 528410] Re: drizzle_state_packet_read:bad packet number
I have provided a fix for libdrizzle for this and proposed it for
merging. This adds the function drizzle_column_skip_all and makes it so
that you cannot retrieve rows until all columns have been pulled out of
the network buffer.
In Mike's case this also requires bug #843782 to be fixed for gearman.
--
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Drizzle.
https://bugs.launchpad.net/bugs/528410
Title:
drizzle_state_packet_read:bad packet number
Status in A Lightweight SQL Database for Cloud Infrastructure and Web Applications:
Fix Committed
Status in Drizzle Client & Protocol Library:
Fix Released
Bug description:
I am getting the following error when using libdrizzle 0.7 together
with MySQL Ver 14.14 Distrib 5.1.38. The error occurs when using
“drizzle_result_buffer”:
drizzle_state_packet_read:bad packet number:213:223
The error is reproduceable; it always occurs on the same query. This
query works just fine when running it with the “mysql” commandline
client.
To manage notifications about this bug go to:
https://bugs.launchpad.net/drizzle/+bug/528410/+subscriptions