[Sqlalchemy-tickets] [sqlalchemy] #2928: yield_per working with oursql but not with mysqldb

[sqlalchemy <mi...@zz...>]

#2928: yield_per working with oursql but not with mysqldb
----------------------+-----------------------------------------
 Reporter:  postpawl  |           Owner:
     Type:  defect    |          Status:  new
 Priority:  medium    |       Milestone:
Component:  mysql     |        Severity:  no triage selected yet
 Keywords:            |  Progress State:  awaiting triage
----------------------+-----------------------------------------
 I have a large query which uses all of my system's memory unless I use
 yield_per.

 While using the mysqldb library in the sqlalchemy connection string and
 watching TOP, the query will eat up all the systems memory (and get
 killed) with or without yield_per. However, when I use oursql - the memory
 usage will stay steady while I use yield_per (as expected).

 You can simulate this by using the mysqldb library + a query using
 query(table).yield_per(5) on an extremely large dataset on a server with a
 small amount of RAM.

--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2928>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python