Jon Ribbens wrote:
On Tue, May 15, 2007 at 04:13:33PM -0500, Kenneth Loafman wrote:
Can't tell. The docs are somewhat lacking in detail, however, if I do a
db.autocommit(True) it works as it should.
Will have to dig into the API code and see if that is where the semantic
discontinuity lies.
The MySQL-python-1.2.2/doc/FAQ.txt says:
| Starting with 1.2.0, MySQLdb disables autocommit by default, as
| required by the DB-API standard (PEP-249). If you are using InnoDB
| tables or some other type of transactional table type, you'll need
| to do connection.commit() before closing the connection, or else
| none of your changes will be written to the database.
Interesting... guess the intent was a disconnect that would break code
trying to work on MySQL, regardless of engine selected. That decision
makes it two products, MySQL/MyISAM and MySQL/InnoDB with different
semantics. Yes, you can work around it, but its not transparent.
...Ken
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
