MySQL Connector/Python Release Notes
Incompatible Change: Python 2 code was changed to use new features introduced in Python 2.6 and 2.7. Some examples:
print()
is used as a function, not a
statement.
Exceptions are handled using the as
keyword.
The in
keyword is used instead of the
has_key()
dictionary method.
This change means that MySQL Connector/Python 1.1 does not work with versions of Python older than 2.6.
Connector/Python was updated with error information from MySQL 5.7.1. (Bug #16896702)
mysql.connector.__version__
and
mysql.connector.__version_info__
now are
available to provide MySQL Connector/Python version information
in a more standard, Pythonic manner.
MySQLConnection
objects now support an
in_transaction
property that returns
True
or False
to indicate
whether a transaction is active for the connection.
MySQLConnection
objects now support a
start_transaction()
method to begin a
transaction. This method accepts arguments indicating whether to
use a consistent snapshot and which transaction isolation level
to use:
cnx.start_transaction(consistent_snapshot=bool
, isolation_level=level
)
The default consistent_snapshot
value is
False
. The default
isolation_level
value is
None
, and permitted values are 'READ
UNCOMMITTED'
, 'READ COMMITTED'
,
'REPEATABLE READ'
, and
'SERIALIZABLE'
.
Connector/Python supports a new
MySQLCursorPrepared
class that enables
execution of prepared SQL statements using the binary
client/server protocol. For details, see
cursor.MySQLCursorPrepared Class.