MySQL Connector/Python

Removing overhead and better exception handling in connection

Bug #584518 reported by Geert JM Vanderkelen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Connector/Python
Fix Released
Low
Geert JM Vanderkelen

Bug Description

We could do without the MySQLBaseConnection._next_buffer() method. Also, need raise a useful exception when no buffer is available.

This report is made from fixes found in following branch:
 https://code.launchpad.net/~bsdemon/myconnpy/fixes

Related branches

lp:~geertjmvdk/myconnpy/main
Revision history for this message
Geert JM Vanderkelen (geertjmvdk) wrote :

revno: 246
committer: Geert Vanderkelen <email address hidden>
branch nick: myconnpy-dev
timestamp: Sun 2010-05-23 13:39:37 +0200
message:
  Remove some overhead while reading packets from MySQL

  o The call to _next_buffer()-method was really not need.
  o We raise an InterfaceError when no buffer can be read when we got everything
  received.
  o Adding entry to ChangeLog

Changed in myconnpy:
status: In Progress → Fix Committed
Geert JM Vanderkelen (geertjmvdk)
Changed in myconnpy:
status: Fix Committed → 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.