On 05/17/2013 03:07 PM, Reindl Harald wrote:
Am 17.05.2013 14:53, schrieb Sebastien FLAESCH:
On 05/17/2013 12:29 PM, Reindl Harald wrote:
Am 17.05.2013 12:05, schrieb Sebastien FLAESCH:
Beside the Oracle skills debate and the stupid mistakes with soname
changes between 5.5.8 and 5.5.10 or
Am 17.05.2013 14:53, schrieb Sebastien FLAESCH:
> On 05/17/2013 12:29 PM, Reindl Harald wrote:
>>
>>
>> Am 17.05.2013 12:05, schrieb Sebastien FLAESCH:
>>> Beside the Oracle skills debate and the stupid mistakes with soname
>>> changes between 5.5.8 and 5.5.10 or 5.6.x, (imagine all of this did
>
On 05/17/2013 12:29 PM, Reindl Harald wrote:
Am 17.05.2013 12:05, schrieb Sebastien FLAESCH:
Beside the Oracle skills debate and the stupid mistakes with soname
changes between 5.5.8 and 5.5.10 or 5.6.x, (imagine all of this did
not happen):
I have a VERY simple question that needs a VERY CLE
Am 17.05.2013 12:05, schrieb Sebastien FLAESCH:
> Beside the Oracle skills debate and the stupid mistakes with soname
> changes between 5.5.8 and 5.5.10 or 5.6.x, (imagine all of this did
> not happen):
>
> I have a VERY simple question that needs a VERY CLEAR answer:
>
> In our distribution pa
Beside the Oracle skills debate and the stupid mistakes with soname
changes between 5.5.8 and 5.5.10 or 5.6.x, (imagine all of this did
not happen):
I have a VERY simple question that needs a VERY CLEAR answer:
In our distribution packages (for different platforms! not only Linux),
I need to pro
Oracle fails the context by make incompatible ABI changes
which are *expected* by raise the minor release number
but claim they are compatible until it is clear that
random things are broken and the soname needs to be
changed what leaves the question: was the QA at holiday
due the whole development
Hi all,
Could someone from the libmysqlclient contributors comment on this, and
could someone complete the documentation regarding client compatiblity?
Thanks!
Seb
On 02/20/2013 09:31 AM, Sebastien FLAESCH wrote:
Hello,
FYI, I found this statement in the doc, at the end of the C API main page
Hello,
FYI, I found this statement in the doc, at the end of the C API main page:
http://dev.mysql.com/doc/refman/5.6/en/c.html
If, after an upgrade, you experience problems with compiled client programs, such as Commands out of sync or unexpected core dumps, you probably have
used old header
On 02/18/2013 12:14 PM, Noel Butler wrote:
On Mon, 2013-02-18 at 10:57 +0100, Sebastien FLAESCH wrote:
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
/op
On Mon, 2013-02-18 at 10:57 +0100, Sebastien FLAESCH wrote:
> 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/libmysqlclien
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 h
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/li
12 matches
Mail list logo
