Search Results
                    
                    
            https://dev.mysql.com/doc/connector-python/en/connector-python-cext.html
                                It is also possible to use the C Extension directly, by importing the _mysql_connector module rather than the mysql.connector module.  Connector/Python supports a C extension that interfaces with the MySQL C client library. For queries that return ...
                                            
                https://dev.mysql.com/doc/internals/en/binary-log-overview.html
                                The binary log has two important purposes: For replication, the binary log is used on master replication servers as a record of the statements to be sent to slave servers.  [Some information in this section is derived from Chapter 20, The Binary ...
                                            
                https://dev.mysql.com/doc/internals/en/binary-log-versions.html
                                Important constants: START_EVENT_V3 = 1 FORMAT_DESCRIPTION_EVENT = 15 EVENT_TYPE_OFFSET = 4 EVENT_LEN_OFFSET = 9 ST_SERVER_VER_LEN = 50 A binary log file begins with a 4-byte magic number followed by an initial descriptor event that identifies the ... 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/class-procedure-send-row.html
                                Whatever you do here is up to you, it is important to note though that to pass on the result row to the client you have to call result->send_data() yourself.  Prototype: virtual int send_row(List<Item> &fields); This member is called for every ...
                                            
                https://dev.mysql.com/doc/internals/en/client-directory.html
                                The client library includes mysql.cc (the source of the mysql executable) and other utilities. Most of the utilities are mentioned in the MySQL Reference Manual. Generally these are standalone C programs which one runs in "client mode", that is, ...
                                            
                https://dev.mysql.com/doc/internals/en/client-server-protocol.html
                                For current information, please refer to the Client/Server Protocol section of the MySQL Server Doxygen documentation, available at https://dev.mysql.com/doc/index-other.html. 
                                            
                https://dev.mysql.com/doc/internals/en/determining-binary-log-version.html
                                Some important points about descriptor event formats: The v1 header fields are common to all formats.  Given any binary log file, the information in this section describes how to determine the format in which it is written. (v3 and v4 headers begin ...
                                            
                https://dev.mysql.com/doc/internals/en/event-data-for-specific-event-types.html
                                This should does not cause inconsistencies in replication because the only important property of transaction numbers is that different transactions have different numbers (relative order does not matter).  The following sections provide details ...
                                            
                https://dev.mysql.com/doc/internals/en/extending-this-page.html
                                 For each new data structure, please make sure you add: the important trade-offs, such as speed vs. 
                                            
                https://dev.mysql.com/doc/internals/en/guided-tour-flow.html
                                The flow works like this: First, the client routines get an SQL statement from a user, allowing edit, performing initial checks, and so on. Then, via the vio routines, the somewhat-massaged statement goes off to the server. Next, the sql routines ...