Bug #42268 | MYSQL::server_capabilities is 16-bit in the protocol, but 32-bit in the library | ||
---|---|---|---|
Submitted: | 22 Jan 2009 13:15 | Modified: | 27 Feb 2013 13:19 |
Reporter: | Alexander Nozdrin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: C API (client library) | Severity: | S2 (Serious) |
Version: | 5.0+ | OS: | Any |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[22 Jan 2009 13:15]
Alexander Nozdrin
[4 May 2009 18:25]
Jim Winstead
This is not actually a problem for clients, but some comments need to be added to the code to clarify what CLIENT_* flags are used by the server to signal what it is capable of, and what are only meant to tell the server what the client wants to do. In the case of CLIENT_MULTI_*, they are purely used for signaling from the client to server. We are out of bits to indicate to the client that the server is capable of something. Rectifying this is going to require a protocol change, and it makes sense to do this as a real protocol upgrade instead of trying to just jam more into the existing one.
[27 Feb 2013 13:19]
Erlend Dahl
This was fixed in 5.5.7. Current protocol supports 32 capability flags - see http://dev.mysql.com/doc/internals/en/connection-phase.html#packet-Protocol::Handshake