Search Results
https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-configuration-connection-without-dsn.html
You can connect to the MySQL server using SQLDriverConnect, by specifying the DRIVER name field. Here are the connection strings for Connector/ODBC using DSN-less connections: For Connector/ODBC 9.6: ConnectionString = "DRIVER={MySQL ODBC 9.6 ...If ...
https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-usagenotes-functionality-catalog-schema.html
This would suggest that CATALOG equals a SCHEMA, which is incorrect, but in the MySQL Server context they would be the same thing. However, some software such as MS SQL Server might try do so through the linked server objects. Many relational ...
https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-versions.html
The latest version of Connector/ODBC supports all active MySQL Server versions, which today includes MySQL Server 8.0 and higher. As an example, use Connector/ODBC 9.6.0 with MySQL Server 8.0, 8.4, and 9.6. Information about each Connector/ODBC ...
https://dev.mysql.com/doc/connector-python/en/connector-python-connection-pooling.html
This enables applications to support pools of connections to different MySQL servers, for example. Applications that can benefit from connection-pooling capability include: Middleware that maintains multiple connections to multiple MySQL servers and ... Simple connection pooling is supported that has these characteristics: The mysql.connector.pooling module implements ...
https://dev.mysql.com/doc/connector-python/en/connector-python-introduction.html
MySQL Connector/Python includes support for: Almost all features provided by MySQL Server version 8.0 and higher. Protocol compression, which enables compressing the data stream between the client and server. Note Connector/Python does not support ... MySQL Connector/Python enables Python programs to access MySQL databases, using an API that is compliant with the Python Database API Specification v2.0 (PEP ...
https://dev.mysql.com/doc/internals/en/binary-log-versions.html
This section describes how the server distinguishes each format to identify which one a binary log file uses. Important constants: START_EVENT_V3 = 1 FORMAT_DESCRIPTION_EVENT = 15 EVENT_TYPE_OFFSET = 4 EVENT_LEN_OFFSET = 9 ST_SERVER_VER_LEN = 50 A ... There are several versions of the binary log file format: v1: Used in MySQL 3.23 v3: Used in MySQL 4.0.2 though 4.1 v4: Used in MySQL 5.0 and up A v2 format was used briefly (in early MySQL 4.0.x versions), but it is obsolete and no longer ...
https://dev.mysql.com/doc/internals/en/binlog-event-header.html
Binlog::EventHeader: Binlog header Payload 4 timestamp 1 event type 4 server-id 4 event-size if binlog-version > 1: 4 log pos 2 flags Fields timestamp (4) -- seconds since unix epoch event_type (1) -- see Binlog Event Type server_id (4) -- server-id ... The binlog event header starts each event and is either 13 or 19 bytes long, depending on the binlog ...
https://dev.mysql.com/doc/internals/en/com-binlog-dump-gtid.html
If the binlog-filename is empty, the server will send the binlog-stream of the first known binlog.
https://dev.mysql.com/doc/internals/en/com-query.html
COM_QUERY: A COM_QUERY is used to send the server a text-based query that is executed immediately. The server replies to a COM_QUERY packet with a COM_QUERY Response. The length of the query-string is a taken from the packet length - 1.
https://dev.mysql.com/doc/internals/en/com-stmt-execute.html
COM_STMT_EXECUTE asks the server to execute a prepared statement as identified by stmt-id. It sends the values for the placeholders of the prepared statement (if it contained any) in Binary Protocol Value form. The type of each parameter is made up ...