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.
Database (schema) name can be specified on connect in
Do not permit
Compression protocol supported.
Switches to Compression compressed protocol after successful authentication.
Special handling of ODBC behavior.
No special behavior since 3.22.
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
Supports interactive and noninteractive clients.
Client is interactive.
Switch to SSL after sending the capability-flags.
Do not issue
SIGPIPE if network
failures occur (libmysqlclient only).
This flag is optional in 3.23, but always set by the server since 4.0.
4.1.0, renamed later.
The flag was introduced in 5.6.6, but had the wrong value.
Can send OK after a Text Resultset.
To support CLIENT_SESSION_TRACK, additional information must be sent after all successful commands. Although 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. EOF packets are deprecated as of MySQL 5.7.5.