> I have not much to add to your analysis, and I agree in that we can't
> and shouldn't change the structure of the packages in existing stable
> releases. However we can take this issue as a good warning on the fact
> that compatibility between the two DBs can't be assumed, and the
> packages in
Hi Otto,
Otto Kekäläinen wrote on 28/05/2020:
> A future version of MariaDB might have the charsets in its own
> directory, but we can't start changing paths of stuff in existing
> stable releases, such as MariaDB 10.3 in Ubuntu 20.04 or Debian
> Buster. If MySQL introduces a backwards
A future version of MariaDB might have the charsets in its own
directory, but we can't start changing paths of stuff in existing
stable releases, such as MariaDB 10.3 in Ubuntu 20.04 or Debian
Buster. If MySQL introduces a backwards incompatible change, the new
uploads should test for them and
Hello!
> /usr/share/mysql/charsets
..
> The location of these files causes the libmysqlclient20 client library
> to consider them charset files from mysql, and it tries to use them.
>
> I think this behavior is wrong, as the charset files do not belong to
> mysql, however it is not immediately
4 matches
Mail list logo
