MySQL 8.3.0 increments libmysqlclient.so lib version from 22 to 23

[Sebastien FLAESCH]

Hello,

Just installed MySQL 8.3.0 on my Linux Debian 11, and I can see that the shared lib version number of libmysqlclient.so has been incremented from 22 to 23:

libmysqlclient.so.23

I just want to get a confirmation that this is expected.

I assume it's because the API/ABI of the library has changed and is no longer compatible with libmysqlclient.so.23 - is this the case?

In fact, we deliver our C binary linked with libmysqlclient, which results in a dependency to the shared lib with version number (this is normal on Linux):

$ ldd -r $FGLDIR/dbdrivers/dbmmys_8_2.so
...
libmysqlclient.so.22 => /opt3/dbs/mys/8.2/lib/libmysqlclient.so.22 (0x00007f6bca430000)
...


If we want to support MySQL 8.3.x, we will have to build a specific binary linked with libmysqlclient.so.23

We have our own installer and do not use Linux packaging systems.

Since we want to support various versions of MySQL, we must deliver a binary for each of the existing libmysqlclient.so.xxx versions.
So far we have binaries for:
libmysqlclient.so.20 ( MySQL 5.7 )
libmysqlclient.so.21 ( MySQL 8.0 )
libmysqlclient.so.22 ( MySQL 8.2 )

I would expect NO VERSION NUMBER increment, if the libmysqlclient shared libs of 8.3.x is compatible with 8.2.x

What are the libmysqlclient API changes in 8.3.0 ?

Seb