[Twisted-Python] Case for an Async MySQL Driver?

orbitz orbitz at ezabel.com
Tue Oct 26 18:27:22 EDT 2004

For starters, MySQL is a really poor DBM, I suggest switching, if you 
don't believe me:

Secondly, adbapi is made in such a way that it doesn't care which module 
you use as long as it is DB-API 2.0 compliant (2.0 right?).  There is a 
postgresql module which provides async access to a postgresql db, 
however it is not DB-API compliant so twisted cannot use it.  If you can 
fit an async MySQL API into DB-API compliance, kick ass, but otherwise 
having a twisted specific module for MySQL kind of defeats the purpose 
of having DB-API.  Finally, will the MySQL lib even allow you to do non 
blocking calls to the database? If not then that sounds like a major 
pitfall there.

Seun Osewa wrote:

>I'm new to Twisted, and I was just thinking about how, while
>'twisted.enterprise.adbapi' is is a really neat idea, it's sort of a
>stop-gap solution pending the time async database drivers can be
>integrated into Twisted.  It's not 'right' to have 1 python thread and
>1 mysql server thread/process for each connection.
>How about an event-driven MySQL protocol implementation that fits into
>the Twisted Framework? (I came accross a MySQL protocol specification
>online once but I think I've lost it). If this sounds sensible, I'll
>be interested with helping out with implementation but I won't be able
>to do actual coding for some time.
>Twisted-Python mailing list
>Twisted-Python at twistedmatrix.com

More information about the Twisted-Python mailing list