MySQL Connector/Python doesn’t buffer results by default. This means you have to fetch the rows when you issued a SELECT. This post describes how you can change this behavior. Why buffering result sets? Buffering or storing the result set on the client side is handy when you, for example, would like to use multiple cursors per connection and you’de like to traverse each one interleaved. Keep in mind that with bigger result sets, the client side will use more memory.

This post describes how to make a custom cursor returning rows as dictionaries using MySQL Connctor/Python v0.2 (or later).

Next development release v0.2.0 of MySQL Connector/Python is available for download and testing. We still don’t recommend to use it in production: it is not beta or GA yet, but we are getting there. Bug reports and feature requests are welcome through the Launchpad bug tracking tool. Highlights: .executemany() now optimizes INSERT statements using the MySQL multiple row syntax. Setting sql_mode and time_zone when connecting as well as collation. Raw Cursors can be used when you want to do the conversion yourself.

My blog (and website) is now running on self-hosted WordPress installation. Yeah, it’s a PHP-thing, but I couldn’t bother making my own with Django or similar using Python. No time for that and I’m not a programming-language-radical-idiot. RSS feeds have changed: you’ll find the link on my new website. Why I moved away from Blogger? It just plain sucked, and I have had my fill of it.. I needed to create some plugin for WordPress.

A few SQL queries are worth a thousands words: mysql> SELECT VERSION(); +----------------+ | VERSION() | +----------------+ | 5.5.6-rc-debug | +----------------+ mysql> SELECT @@global.storage_engine; +-------------------------+ | @@global.storage_engine | +-------------------------+ | InnoDB | +-------------------------+ (Note: the above is without using the default storage engine option) Scary! Excitement! MySQL!