Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MySQL++ - Programming with the C++ API to MySQL
MaxDB - Everything about MaxDB, formerly known as SAP DB
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
• Subject: mysql openssl Question
• ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
• Update one field with more fields from another table
• Subject: Getting Identity after INSERT
• ERROR 2002: Can 't connect to local MySQL server through socket
• mysql test 4 1 fails with the gis test
• Subject: MySQL Cluster Software
• Downgrade Mysql from 4 to 3 23
• Mysql 4 0 Oracle Stored Procedure Trigger Conversion
• Can 't access mysql after kernel upgrade
• Executing MySQL Commands From Within C Program
• Comparing and writing out BLOBS
• Subject: Re: Preventing Duplicate Entries
• FULLTEXT query format question
• Strange behavior, Table Level Permission
• Does the binary log enabling affect the MySQL performances?
• mysql:it 's a db not a dbms how it 's possible?!
• mysql have same function mthod as Oracle decode()
 
Subject: Unconverted SQLError in Python sdb.dbapi

Subject: Unconverted SQLError in Python sdb.dbapi

2007-08-16       - By Christian Ullrich

 Back
Hello all,

the Python DB-API describes a set of exceptions that must be used by
implementing modules. There is a bug in the current Python API
(7.6.0.37), in which a native exception (sdb.sql.SQLError) is seen in
code that uses the sdb.dbapi interface.

If the database connection times out, the next query will fail with an
SQLError code 700 (session reconnected, work rolled back). This
exception is caught in dbapi.py and converted to a DB-API compliant
ProgrammingError exception. This works fine for simple statements.

If the query had parameters, however, the original exception is not
handled and passes up to the caller. The following patch fixes this:

--- sdb/dbapi.py.orig   2007-08-16 11:24:58.915828800 +0200
+++ sdb/dbapi.py   2007-08-16 11:25:15.880053000 +0200
@@ -240,7 +240,7 @@
        if parameters == None:
            result = wrapCall (self.__executeDirect, operation)
        else:
-            parsed = self.__getParsed, operation
+            parsed = wrapCall (self.__getParsed, operation)
            result = wrapCall (self.__executeParsed, parsed,
parameters)
        return result

Preparing a (parameterized) statement for execution apparently involves
communication with the server, so the __getParsed() call can fail for a
lost connection.

--
Christian Ullrich

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=mysql@(protected)