Search Results
https://dev.mysql.com/doc/connector-python/en/connector-python-api-mysqlconnection-commit.html
>>> cursor.execute("INSERT INTO employees (first_name) VALUES (%s), (%s)", ('Jane', 'Mary')) >>> cnx.commit() To roll back instead and discard modifications, see the rollback() method. This method sends a COMMIT statement to the MySQL server, ...
https://dev.mysql.com/doc/connector-python/en/connector-python-api-mysqlconnection-rollback.html
>>> cursor.execute("INSERT INTO employees (first_name) VALUES (%s), (%s)", ('Jane', 'Mary')) >>> cnx.rollback() To commit modifications, see the commit() method. This method sends a ROLLBACK statement to the MySQL server, undoing all data changes ...
https://dev.mysql.com/doc/connector-python/en/connector-python-api-mysqlcursor-rowcount.html
Syntax: count = cursor.rowcount This read-only property returns the number of rows returned for SELECT statements, or the number of rows affected by DML statements such as INSERT or UPDATE. For nonbuffered cursors, the row count cannot be known ...
https://dev.mysql.com/doc/connector-python/en/connector-python-asyncio.html
Installing Connector/Python also installs the mysql.connector.aio package that integrates asyncio with the connector to allow integrating asynchronous MySQL interactions with an application. Functions included in the asyncio API must be used to ...
https://dev.mysql.com/doc/connector-python/en/connector-python-coding.html
You use the SQL INSERT, UPDATE, and DELETE statements to update different items concurrently, writing only the changed values to disk. The following guidelines cover aspects of developing MySQL applications that might not be immediately obvious to ...
https://dev.mysql.com/doc/internals/en/binary-log-overview.html
There are two types of binary logging: Statement-based logging: Events contain SQL statements that produce data changes (inserts, updates, deletes) Row-based logging: Events describe changes to individual rows Mixed logging uses statement-based ...
https://dev.mysql.com/doc/internals/en/creating-index-keys.html
As part of every table-write operation (INSERT, UPDATE, DELETE), the storage engine is required to update its internal index information. The method used to update indexes will vary from storage engine to storage engine, depending on the method ...
https://dev.mysql.com/doc/internals/en/custom-engine-overview.html
Custom storage engines can be built in a progressive manner: Developers can start with a read-only storage engine and later add support for INSERT, UPDATE, and DELETE operations, and even later add support for indexing, transactions, and other ...
https://dev.mysql.com/doc/internals/en/dbug-directory.html
How it works: One inserts a function call that begins with DBUG_* in one of the regular MYSQL programs. Rather, it's a set of public-domain routines which are useful for debugging MySQL programs. The MySQL Server and all .c and .cc programs support ...
https://dev.mysql.com/doc/internals/en/delete-row.html
In sql_select it is used for removing duplicates, while in insert it is used for REPLACE calls. Synopsis virtual int delete_row ( buf); const byte * buf ; Description This is the delete_row method. buf will contain a copy of the row to be deleted.