Jens Peter Secher a écrit :
2009/9/1 Palotai Robin <[email protected]>:
Is there a known bug why mysql5.ndll should not work where mysql.ndll works?
I also had some problems with mysql5.ndll in the Debian package [1].
In the end I found out that not building mysql5.ndll and simply
building mysql.ndll against the most recent version of
libmysqlclient-dev and linking with -lmysqlclient solved all problems,
in the sense that I can now connect to and query any mysql version
present in current Debian.
Nicolas, what is purpose of mysql5.ndll? Does it provide something
that mysql.ndll does not?
mysql5.ndll was at first the Mysql5 client library (whereas mysql.ndll
was MySQL4). But since we were experimenting some issues with native
mysql client (a lot of crashes if the version of the compiled headers
does not match the runtime library) I did a rewrite-from-scratch of the
mysql client library.
It should work pretty well (we're using it in production on our
websites) but does not support all native MySQL client library features
(in particular, no Unix socket connection and not MySQL4 identification
mode).
I would be happy if someone could provide tested patches for these,
based on protocol documentation here :
http://forge.mysql.com/wiki/MySQL_Internals_ClientServer_Protocol
Best,
Nicolas
--
Neko : One VM to run them all
(http://nekovm.org)
