Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


On Wed, Sep 17, 2014 at 12:27:49AM +0200, Robert Antoni Buj i Gelonch wrote:

Within the ANNOUNCEMENT file of MySQL Connector/C++ 1.1.4 says that the
connector now is compiled and linked with Connector/C 6.1.4 rather than
with libmysql. For that reason, I wonder if we can add MySQL Connector/C
6.1.5 in the external libraries as a MySQL Connector/C++ 1.1.4 dependency.

We've been - on and off - trying to use the MariaDB native (that is,
C) client instead, which is supposed to be compatible and which we do
have as an external. The inclusion of it as an external was seen as a
first step towards getting progressively rid of MySQL Connector/C++.

However, twice I switched back to using libmysqlclient (which is AFAIK
another name for "MySQL Connector/C") because of bugs or
incompatibility in the MariaDB native client; however, the MariaDB
native client developer is *very* responsive in dealing with issues I
throw at him :) He already dealt with the latest one (from 9
September).

So, we could:

1) Have another try with MariaDB native client right now by including
   the patch for CONC-104
   http://bazaar.launchpad.net/~maria-captains/mariadb-native-client/trunk/revision/149

2) Have another try with MariaDB native client right now by updating
   our external to the "full" trunk revision 149.

3) Include libmysqlclient as an external.

-- 
Lionel

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.