Search Results
https://dev.mysql.com/doc/connectors/en/connector-python-api-mysqlconnection-start-transaction.html
If the value is True, Connector/Python sends WITH CONSISTENT SNAPSHOT with the statement. For details about transaction access mode, see the description for the START TRANSACTION statement at START TRANSACTION, COMMIT, and ROLLBACK Statements. This ...It accepts arguments indicating whether to use a consistent snapshot, which transaction isolation level to use, and the transaction access mode: cnx.start_transaction(consistent_snapshot=bool, isolation_level=level, readonly=access_mode) The default consistent_snapshot value is ...
https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-usagenotes-functionality-last-insert-id.html
Obtaining the value of column that uses AUTO_INCREMENT after an INSERT statement can be achieved in a number of different ways. For example, using Connector/ODBC you would execute two separate statements, the INSERT statement and the SELECT query ...To obtain the value immediately after an INSERT, use a SELECT query with the LAST_INSERT_ID() ...
https://dev.mysql.com/doc/connector-python/en/connector-python-api-mysqlconnection-cmd-query.html
Syntax: cnx.cmd_query(statement) This method sends the given statement to the MySQL server and returns a result. If the query is a SELECT statement, the result contains information about columns. Other statements return a dictionary containing OK ...The returned dictionary contains information depending on what kind of query was ...
https://dev.mysql.com/doc/connector-python/en/connector-python-api-mysqlconnection-start-transaction.html
If the value is True, Connector/Python sends WITH CONSISTENT SNAPSHOT with the statement. For details about transaction access mode, see the description for the START TRANSACTION statement at START TRANSACTION, COMMIT, and ROLLBACK Statements. This ...It accepts arguments indicating whether to use a consistent snapshot, which transaction isolation level to use, and the transaction access mode: cnx.start_transaction(consistent_snapshot=bool, isolation_level=level, readonly=access_mode) The default consistent_snapshot value is ...
https://dev.mysql.com/doc/internals/en/binlog-event.html
START_EVENT_V3 FORMAT_DESCRIPTION_EVENT STOP_EVENT ROTATE_EVENT SLAVE_EVENT INCIDENT_EVENT HEARTBEAT_EVENT Statement Based Replication Events Statement Based Replication or SBR sends the SQL queries a client sent to the master AS IS to the slave.
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 ...
https://dev.mysql.com/doc/internals/en/replication-source-code-files.html
sql_binlog.cc Contains code to execute BINLOG statements (that is, the base64-encoded things that mysqlbinlog prints when it sees row events). sql_base.cc Prior to Bug#39934, the function decide_logging_format() that determines if statements should ... Status of this section: up to date 2009-12-16 Files in the sql directory: File Description slave.h/.cc Contains the slave IO and SQL ...
https://dev.mysql.com/doc/internals/en/row-based-binary-logging.html
Similar remarks apply to the terms "statement-based logging" (SBL) versus "statement-based replication" (SBR). Logging in this format can be done independent of whether the log is used for replication. That is, replication need not figure into the ...
https://dev.mysql.com/doc/internals/en/tuning-trace-purging.html
The SET statement has the following effects: All remembered traces are cleared A later SELECT on the OPTIMIZER_TRACE table returns the first LIMIT traces of the OFFSET oldest remembered traces (if OFFSET ≥ 0), or the first LIMIT traces of the ...
https://dev.mysql.com/doc/relnotes/connector-cpp/en/news-8-0-24.html
Bugs Fixed Upon connecting to the server, Connector/C++ executed a number of SHOW [SESSION] VARIABLES statements to retrieve system variable values. Such statements involve locking in the server, so they are now avoided in favor of SELECT @@var_name ...Typically, the client would see Lost connection to MySQL server during query (CR_SERVER_LOST) or MySQL server has gone away ...