[DB-SIG] MySQLdb module 0.3.1
Andy Dustman
andy@dustman.net
Mon, 22 Jan 2001 14:46:08 -0500 (EST)
An interface to MySQL
Stability: Perfect in every way
Released: 2001-01-22 00:00 UTC
Notes
This release fixes two minor issues with 0.3.0. If they don't otherwise
affect you, you don't need to upgrade. This is a release candidate for
version 1.0.0. The plan is that 1.0.x will be the last version to support
Python-1.5.2 and MySQL-3.22. Version 1.1.x will target MySQL-3.23, the
upcoming MySQL-4.0, and Python-2.x.
MySQL INTEGER columns have a FIELD_TYPE of LONG, which is a C long and
therefore a Python integer. However, INTEGER UNSIGNED may overflow when
converted to a Python integer. Therefore, FIELD_TYPE.LONG is now converted
to a Python long integer. To revert to the old behavior:
import MySQLdb
MySQLdb.type_conv[MySQLdb.FIELD_TYPE.LONG]=int
MySQL-3.23.29a broke the version parsing. Don't use 3.23.29a. At the time
of writing, 3.23.32 (stable) is the current version.
MySQLdb now looks for the server variable have_bdb (YES) to determine
whether or not transactions can be performed. You need at least
MySQL-3.23.30 for this.
Documentation has been brought up-to-date.
Note that all Linux binaries here are compiled with Python-1.5.2,
MySQL-3.23.32, Red Hat 6.2, and RPM 4.0 (where applicable).
Windows binaries may show up at http://highqualdev.com
http://dustman.net/andy/python/MySQLdb/0.3.1
--
Andy Dustman PGP: 0xC72F3F1D
@ .net http://dustman.net/andy
"Normally with carbonara you use eggs, but I used lobster brains instead."
-- Masahiko Kobe (Iron Chef Italian): 30-year-old Giant Lobster Battle