Legacy Connection String Info passing into MySQLdb

Bug #290097 reported by Nick Verbeck on 2008-10-27
Affects Status Importance Assigned to Milestone
Status tracked in Pre-1.0
Fix Released
Nick Verbeck

Bug Description


Ive downloaded the new v0.3B and it appears the connection parameters have changed and am not sure how I should be using the new library.
when connecting:
 con = PySQLPool.getNewConnection(host = 'host', username='user', password='pwd', schema='test', commitOnEnd =False)
I get a string and int concatenation error. I believe that this might be a bug (but am not sure am using it correctly) I changed the source on PySQLConnection line 52 to hashStr += str(self.info[key]) which was a simple fix.After that it got a bit more complicated. I then started getting another error
TypeError: 'username' is an invalid keyword argument for this function. Debugging through it it appears that this error has something to do with unknown para being passed to MySQLdb.connect() method.


Nick Verbeck (nerdynick) on 2008-10-27
Changed in pysqlpool:
assignee: nobody → nerdynick
importance: Undecided → Critical
milestone: none → 0.3
status: New → Confirmed
Nick Verbeck (nerdynick) wrote :

Fix Commited into SVN

Changed in pysqlpool:
status: Confirmed → Fix Committed
Nick Verbeck (nerdynick) wrote :

Release with 0.3

Changed in pysqlpool:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers