The capability flags are used by the client and server to indicate which features they support and want to use.
Use the improved version of
assumed to be set since 4.1.1
found rows instead of
affected rows in
Longer flags in
supports longer flags
expects longer flags
One can specify db on connect in
Don't allow database.table.column
Compression protocol supported
switches to Compression compressed protocol after successful authentication
Special handling of ODBC behaviour
no special behaviour since 3.22
Can use LOAD DATA LOCAL
parser can ignore spaces before '('
let the parser ignore spaces before '('
supports the 4.1 protocol
uses the 4.1 protocol
this value was
3.22, unused in 4.0
wait_timeout vs. wait_interactive_timeout
supports interactive and non-interactive clients
client is interactive
switch to SSL after sending the capability-flags
Don't issue SIGPIPE if network failures (libmysqlclient only)
this flag is optional in 3.23, but set all the time by the server since 4.0
CLIENT_PROTOCOL_41 in 4.1.0
4.1.0, renamed later
the flag was introduce in 5.6.6, but had the wrong value.
can send OK after a Text Resultset
To support CLIENT_SESSION_TRACK additional information has to be sent after all succesful commands. While the OK packet is extensible, the EOF packet is not due to the overlap of its bytes with the content of the Text Resultset Row.
Therefore, the EOF packet in the Text Resultset is replaced with an OK packet.