Am 18.02.2013 10:57, schrieb Sebastien FLAESCH: > Hi all, > > What is the compatibility policy regarding the MySQL C API library? > > I could not find the rules in the documentation. > > I have several versions of MySQL installed on my Linux, and it appears > that the libmysqlclient versions have changed in the 5.x version line: > > /opt3/dbs/mys/4.1.24/lib/libmysqlclient.so.14 > /opt3/dbs/mys/5.0.90/lib/libmysqlclient.so.15 > /opt3/dbs/mys/5.1.35/lib/libmysqlclient.so.16 > /opt3/dbs/mys/5.1.51/lib/libmysqlclient.so.16 > /opt3/dbs/mys/5.4.0/lib/libmysqlclient.so.16 > /opt3/dbs/mys/5.5.1/lib/libmysqlclient.so.16 > /opt3/dbs/mys/5.5.19/lib/libmysqlclient.so.18 > /opt3/dbs/mys/5.6.10/lib/libmysqlclient.so.18 > > What's the rule? Is a 5.6 compatible to 5.5 because they have the same > library version number (.18)?
i bet we will see the same with MySQL 5.5.10 http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-10.html Incompatible Change: The shared library version of the client library was increased to 18 to reflect ABI changes, and avoid compatibility problems with the client library in MySQL 5.1. Note that this is an incompatible change between 5.5.10 and earlier 5.5 versions, so client programs that use the 5.5 client library should be recompiled against the 5.5.10 client library. (Bug #60061, Bug #11827366)
signature.asc
Description: OpenPGP digital signature
