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) ?

What about other platforms not using library version numbers?

Is there any lib client version compatibility checking when initializing
the client library? That would prevent from invalid combinations of there
is a compatibility issue.

Can a C program compiled/linked with the 5.6.* client be used with all
the older and future 5.* clients?
Or is 5.6 a major version compared to 5.5, that requires a recompilation
and re-link of the C client programs?

This is critical for software vendors that want to provide a database
client/driver for different versions of MySQL, using the native MySQL C
client API (without going through ODBC or other layers).

Thanks!
Seb

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql