Structure
MySQLProtocol.CapabilityFlags
The capability flags are used by the client and server to indicate which features they support and want to use.
struct CapabilityFlags
Overview
https://dev.mysql.com/doc/internals/en/capability-flags.html#packet-Protocol::CapabilityFlags
Topics
Initializers
init(rawValue: UInt64)Create a newMySQLCapabilityFlagsfrom the upper and lower values.
Instance Properties
var description: StringSeeCustomStringConvertible.var name: Stringvar rawValue: UInt64The raw capabilities value.
Type Properties
static var CLIENT_CAN_HANDLE_EXPIRED_PASSWORDS: MySQLProtocol.CapabilityFlagsServer: Announces support for expired password extension. Client: Can handle expired passwords. https://dev.mysql.com/doc/internals/en/cs-sect-expired-password.htmlstatic var CLIENT_COMPRESS: MySQLProtocol.CapabilityFlagsCompression protocol supported. Server: Supports compression. Client: Switches to compressed protocol after successful authentication.static var CLIENT_CONNECT_ATTRS: MySQLProtocol.CapabilityFlagsServer: Permits connection attributes inProtocol::HandshakeResponse41. Client: Sends connection attributes inProtocol::HandshakeResponse41.static var CLIENT_CONNECT_WITH_DB: MySQLProtocol.CapabilityFlagsDatabase (schema) name can be specified on connect in Handshake Response Packet. Server: Supports schema-name in Handshake Response Packet. Client: Handshake Response Packet contains a schema-name.static var CLIENT_DEPRECATE_EOF: MySQLProtocol.CapabilityFlagsServer: Can send OK after a Text Resultset. Client: Expects an OK (instead of EOF) after the resultset rows of a Text Resultset. To supportCLIENT_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.static var CLIENT_FOUND_ROWS: MySQLProtocol.CapabilityFlagsSend found rows instead of affected rows inEOF_Packet.static var CLIENT_IGNORE_SIGPIPE: MySQLProtocol.CapabilityFlagsClient: Do not issueSIGPIPEif network failures occur (libmysqlclientonly).static var CLIENT_IGNORE_SPACE: MySQLProtocol.CapabilityFlagsServer: Parser can ignore spaces before ‘(’. Client: Let the parser ignore spaces before ‘(’.static var CLIENT_INTERACTIVE: MySQLProtocol.CapabilityFlagswait_timeoutversuswait_interactive_timeout. Server: Supports interactive and noninteractive clients. Client: Client is interactive.static var CLIENT_LOCAL_FILES: MySQLProtocol.CapabilityFlagsCan useLOAD DATA LOCAL. Server: Enables theLOCAL INFILErequest ofLOAD DATA|XML. Client: Will handleLOCAL INFILErequest.static var CLIENT_LONG_FLAG: MySQLProtocol.CapabilityFlagsLonger flags inProtocol::ColumnDefinition320. Server: Supports longer flags. Client: Expects longer flags.static var CLIENT_LONG_PASSWORD: MySQLProtocol.CapabilityFlagsUse the improved version of Old Password Authentication.static var CLIENT_MULTI_RESULTS: MySQLProtocol.CapabilityFlagsServer: Can send multiple resultsets forCOM_QUERY. Client: Can handle multiple resultsets forCOM_QUERY.static var CLIENT_MULTI_STATEMENTS: MySQLProtocol.CapabilityFlagsServer: Can handle multiple statements perCOM_QUERYandCOM_STMT_PREPARE. Client: May send multiple statements perCOM_QUERYandCOM_STMT_PREPARE.static var CLIENT_NO_SCHEMA: MySQLProtocol.CapabilityFlagsServer: Do not permitdatabase.table.column.static var CLIENT_ODBC: MySQLProtocol.CapabilityFlagsSpecial handling of ODBC behavior.static var CLIENT_PLUGIN_AUTH: MySQLProtocol.CapabilityFlagsServer: Sends extra data in Initial Handshake Packet and supports the pluggable authentication protocol. Client: Supports authentication plugins.static var CLIENT_PLUGIN_AUTH_LENENC_CLIENT_DATA: MySQLProtocol.CapabilityFlagsServer: Understands length-encoded integer for auth response data inProtocol::HandshakeResponse41. Client: Length of auth response data inProtocol::HandshakeResponse41is a length-encoded integer.static var CLIENT_PROTOCOL_41: MySQLProtocol.CapabilityFlagsServer: Supports the 4.1 protocol. Client: Uses the 4.1 protocol.static var CLIENT_PS_MULTI_RESULTS: MySQLProtocol.CapabilityFlagsServer: Can send multiple resultsets forCOM_STMT_EXECUTE. Client: Can handle multiple resultsets forCOM_STMT_EXECUTE.static var CLIENT_RESERVED: MySQLProtocol.CapabilityFlagsUnused.static var CLIENT_SECURE_CONNECTION: MySQLProtocol.CapabilityFlagsServer: SupportsAuthentication::Native41. Client: SupportsAuthentication::Native41.static var CLIENT_SESSION_TRACK: MySQLProtocol.CapabilityFlagsServer: Can setSERVER_SESSION_STATE_CHANGEDin the Status Flags and send session state change data after a OK packet. Client: Expects the server to send sesson state changes after a OK packet.static var CLIENT_SSL: MySQLProtocol.CapabilityFlagsServer: Supports SSL. Client: Switch to SSL after sending the capability flags.static var CLIENT_TRANSACTIONS: MySQLProtocol.CapabilityFlagsServer: Can send status flags inEOF_Packet. Client: Expects status flags inEOF_Packet.static var MARIADB_CLIENT_COM_MULTI: MySQLProtocol.CapabilityFlagsPermitCOM_MULTIprotocol.static var MARIADB_CLIENT_PROGRESS: MySQLProtocol.CapabilityFlagsClient support progress indicator (since 10.2).static var MARIADB_CLIENT_STMT_BULK_OPERATIONS: MySQLProtocol.CapabilityFlagsPermit bulk insert.static var all: [MySQLProtocol.CapabilityFlags]All capabilities.static var clientDefault: MySQLProtocol.CapabilityFlagsDefault capabilities.
Relationships
Conforms To
Swift.CustomStringConvertibleSwift.EquatableSwift.ExpressibleByArrayLiteralSwift.OptionSetSwift.RawRepresentableSwift.SendableSwift.SendableMetatypeSwift.SetAlgebra