Opened 11 years ago

Closed 7 years ago

#9274 closed New feature (invalid)

Support MySQLdb >= 1.3.0

Reported by: Dave St.Germain <…> Owned by: nobody
Component: Database layer (models, ORM) Version: 1.0
Severity: Normal Keywords: mysqldb
Cc: Triage Stage: Someday/Maybe
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


MySQL-python version 1.3.0 and greater has moved two functions. This patch enables support for the latest MySQLdb module.

Attachments (1)

mysqldb_changes.diff (709 bytes) - added by Dave St.Germain <…> 11 years ago.

Download all attachments as: .zip

Change History (4)

Changed 11 years ago by Dave St.Germain <…>

Attachment: mysqldb_changes.diff added

comment:1 Changed 11 years ago by Malcolm Tredinnick

Triage Stage: UnreviewedSomeday/Maybe

As far as I can tell from the sourceforge page, there is no release called 1.3.0 yet. Our policy is not to worry about chasing unreleased versions, at least until the get to release-candidate mode, since plenty of things could change between now and release time (and have done in the past, both with MySQLdb and other modules we rely upon).

For example, the fact that those particular functions have been moved inside an underscore-prefixed attribute means they probably aren't intended to be used by public code any longer. That may be a bug in MySQLdb, since presumably one is meant to be able to get the server version and check connection liveness or it may be that Andy is intended to provide a different way to do it or it may be that the recommended way is to refer to _db. So let's wait and see how it pans out (you may wish to follow up with the MySQLdb project and see if users of that module are meant to be using _db to get that information).

Let's put this on hold until there's a release. We don't want to inadvertently look like we're supporting something that isn't released yet.

comment:2 Changed 8 years ago by Luke Plant

Severity: Normal
Type: New feature

comment:3 Changed 7 years ago by Adam Nelson

Easy pickings: unset
Resolution: invalid
Status: newclosed
UI/UX: unset

There still is not a version 1.3.x - 3 years later :-(

Note: See TracTickets for help on using tickets.
Back to Top