Dapper Backports

Requesting python-mysqldb 1.2.1-p2-4ubuntu2

Bug #64270 reported by John Millikin
6
Affects Status Importance Assigned to Milestone
Dapper Backports
Invalid
Undecided
Unassigned
python-mysqldb (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

The version of python-mysqldb in Edgy has a patch to work around another change in MySQL (02_reconnect.dpatch). Specifically, it adds a 'reconnect' parameter to the _mysql.connection() initialization function, which is now needed since MySQL disabled reconnects by default.

By the way, it seems the package was renamed. In Dapper the real package is python2.4-mysqldb.

Revision history for this message
John Millikin (jmillikin) wrote :

I've also created a quick patch for the Dapper version (python-mysqldb_1.2.1c3-4ubuntu4), which adds this feature.

Revision history for this message
John Millikin (jmillikin) wrote :

Forgot to mention, that patch is from the Edgy version, so it should work.

Revision history for this message
John Dong (jdong) wrote :

If you got the patch isolated to Dapper, you should target dapper-updates :)

Changed in dapper-backports:
status: Unconfirmed → Rejected
Revision history for this message
Gustavo Niemeyer (niemeyer) wrote :

Please don't apply this patch.

First, the description is incorrect. It doesn't offer a "reconnect" parameter. It
turns on reconnection by default.

Second, the patch should actually be *removed* from any versions that currently
have it applied. Check bug #163184 for more information.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package python-mysqldb - 1.2.2-5ubuntu1

---------------
python-mysqldb (1.2.2-5ubuntu1) hardy; urgency=low

  * Disable the 02_reconnect patch. LP: #64270, #163184.

    Comment in Storm which explains the problem:

        # Here is another sad story about bad transactional behavior. MySQL
        # offers a feature to automatically reconnect dropped connections.
        # What sounds like a dream, is actually a nightmare for anyone who
        # is dealing with transactions. When a reconnection happens, the
        # currently running transaction is transparently rolled back, and
        # everything that was being done is lost, without notice. Not only
        # that, but the connection may be put back in AUTOCOMMIT mode, even
        # when that's not the default MySQLdb behavior. The MySQL developers
        # quickly understood that this is a terrible idea, and removed the
        # behavior in MySQL 5.0.3. Unfortunately, Debian and Ubuntu still
        # have a patch right now which *reenables* that behavior by default
        # even past version 5.0.3.

 -- Matthias Klose <email address hidden> Wed, 09 Apr 2008 19:19:42 +0000

Changed in python-mysqldb:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.