Today I was chatting with a technical friend, and she mentioned that she has a "todo" of writing a decent node.js driver for MySQL. A bit more chatting back and forth, and http://nodejsdb.org/db-drizzle/ was discovered. It was written to use libdrizzle and drizzled, but since libdrizzle can talk to MySQL, it should work for her needs as well.

I would love to see some work done on how well libmysql+mysqld, libdrizzle+mysqld, and libdrizzle+drizzled handle highly concurrent asynchronous event-oriented workloads such as those generated by all these new node.js applications.

I suspect that all sorts of surprising bugs will be discovered.

Please help us discover those bugs.

Quick post here for a problem that other people might run into and wonder how to fix. Let’s say you have the following error:

install_driver(mysql) failed: Can't load '/usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi/auto/DBD/mysql/mysql.so' for module DBD::mysql: libmysqlclient.so.14: cannot open shared object file: No such file or directory at /usr/lib64/perl5/5.8.5/x86_64-linux-thread-multi/DynaLoader.pm line 230.
at line 3
Compilation failed in require at line 3.
Perhaps a required shared library or dll isn't installed where expected
at ./kontroll-client-5.0.x_linux-x86-2.0.1.pl line 193


Well, you probably need to symlink “libmysqlclient.so.14″ to the existing one that is most likely of a newer version.

> find / -name "libmysqlclient*"
/usr/lib64/libmysqlclient.so.15
/usr/lib64/libmysqlclient_r.so
…

was it really almost a year ago that i mentioned that my focus would be shifting from connector/odbc to libmysql? time certainly flies.

after what now seems much too long, i can say that we have carved out libmysql from the server source code, rebuilt its build system (using cmake), and are gearing up for an alpha release. the code is on launchpad, and it builds on all the platforms that the mysql server does. we have a build system set up that runs what scant tests we have on all of the platforms, and the big thing to work one before release is making more tests.

because this source is derived from the 6.0 server code, it has at least one big flaw that needs to get addressed — if you try to use utf-8, it uses the new 4-byte utf-8 supported in …

while we start to wind up development of connector/odbc 5.1, i will also be taking on responsibility for libmysql, the c library that defines the client interface to mysql, and the mysql command-line utilities. there are about 120 active bugs in those areas right now, so the first task will be getting that down to a more manageable number.

after that, the field will open up for new development. i know that an asynchronous interface to libmysql is on some people’s wishlist, and there are other areas where i think that libmysql could be cleaned up in general.

but the idea that i think is the most exciting is to build a scripting …