CLIENT_LONG_PASSWORDUse the improved version of Old Password Authentication.
Note
Assumed to be set since 4.1.1.
Value0x00000001CLIENT_FOUND_ROWSSend found rows instead of affected rows in EOF_Packet.
Value0x00000002CLIENT_LONG_FLAGValue0x00000004ServerSupports longer flags.ClientExpects longer flags.CLIENT_CONNECT_WITH_DBDatabase (schema) name can be specified on connect in Handshake Response Packet.
Value0x00000008ServerClientCLIENT_NO_SCHEMAValue0x00000010ServerDo not permit database.table.column.CLIENT_COMPRESSCompression protocol supported.
Value0x00000020ServerSupports compression.ClientSwitches to Compression compressed protocol after successful authentication.CLIENT_ODBCValue0x00000040
Special handling of ODBC behavior.
Note
No special behavior since 3.22.CLIENT_LOCAL_FILESCan use LOAD DATA LOCAL.
Value0x00000080ServerEnables the LOCAL INFILE request of LOAD DATA|XML.ClientCLIENT_IGNORE_SPACEValue0x00000100ServerParser can ignore spaces before '('.ClientLet the parser ignore spaces before '('.CLIENT_PROTOCOL_41Value0x00000200ServerSupports the 4.1 protocol.ClientUses the 4.1 protocol.
Note
this value was CLIENT_CHANGE_USER in 3.22, unused in 4.0CLIENT_INTERACTIVEwait_timeout versus wait_interactive_timeout.
Value0x00000400ServerSupports interactive and noninteractive clients.ClientClient is interactive.SeeCLIENT_SSLValue0x00000800ServerSupports SSL.ClientSwitch to SSL after sending the capability-flags.CLIENT_IGNORE_SIGPIPEValue0x00001000ClientDo not issue SIGPIPE if network failures occur (libmysqlclient only).SeeCLIENT_TRANSACTIONSValue0x00002000ServerCan send status flags in EOF_Packet.ClientExpects status flags in EOF_Packet.
Note
This flag is optional in 3.23, but always set by the server since 4.0.CLIENT_RESERVEDUnused.
Value0x00004000
Note
Was named CLIENT_PROTOCOL_41 in 4.1.0.CLIENT_SECURE_CONNECTIONCLIENT_MULTI_STATEMENTSValue0x00010000ServerCan handle multiple statements per COM_QUERY and COM_STMT_PREPARE.ClientMay send multiple statements per COM_QUERY and COM_STMT_PREPARE.
Note
Was named CLIENT_MULTI_QUERIES in 4.1.0, renamed later.CLIENT_MULTI_RESULTSValue0x00020000ServerCan send multiple resultsets for COM_QUERY.ClientCan handle multiple resultsets for COM_QUERY.RequiresCLIENT_PS_MULTI_RESULTSServerCan send multiple resultsets for COM_STMT_EXECUTE.ClientCan handle multiple resultsets for COM_STMT_EXECUTE.Value0x00040000RequiresCLIENT_PLUGIN_AUTHValue0x00080000ServerSends extra data in Initial Handshake Packet and supports the pluggable authentication protocol.ClientSupports authentication plugins.RequiresCLIENT_CONNECT_ATTRSValue0x00100000ServerPermits connection attributes in Protocol::HandshakeResponse41.ClientSends connection attributes in Protocol::HandshakeResponse41.CLIENT_PLUGIN_AUTH_LENENC_CLIENT_DATAValue0x00200000ServerUnderstands length-encoded integer for auth response data in Protocol::HandshakeResponse41.ClientLength of auth response data in Protocol::HandshakeResponse41 is a length-encoded integer.
Note
The flag was introduced in 5.6.6, but had the wrong value.CLIENT_CAN_HANDLE_EXPIRED_PASSWORDSValue0x00400000ServerClientCLIENT_SESSION_TRACKValue0x00800000ServerClientExpects the server to send sesson-state changes after a OK packet.CLIENT_DEPRECATE_EOFValue0x01000000ServerCan send OK after a Text Resultset.ClientExpects an OK (instead of EOF) after the resultset rows of a Text Resultset.BackgroundTo 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.