> -----Original Message----- > From: Nick Arnett [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 25, 2003 8:48 AM
... > Just noticed something odd, though, with the MySQLdb SSCursor. > When close() > is called, it does a fetchall(), getting any records that you hadn't > retrieved, trying to load all of them into memory. It's actually calling > nextset(), even though MySQL doesn't support multiple result sets. This is because MySQL requires all rows to be read from a server-side connection before issuing another query on that connection, Andy Dustman tells me. It doesn't seem to be a problem as long as you do, in fact, read all the rows, so this is more an issue of the way I was testing than the real world. Nick -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
