On Monday, 28 November 2016 21:37:05 CET Robie Basak wrote:
> On Mon, Nov 28, 2016 at 10:12:14PM +0100, Stefan Fritsch wrote:
> > thank you both for the information, this sounds quite good. I will switch
> > to libmariadbclient for stretch. For stretch+1, we'll see how things
> > develop upstream.
On Mon, Nov 28, 2016 at 10:12:14PM +0100, Stefan Fritsch wrote:
> thank you both for the information, this sounds quite good. I will switch to
> libmariadbclient for stretch. For stretch+1, we'll see how things develop
> upstream.
Can you not use default-libmysqlclient-dev and maintain build-tim
Hi Robie, hi Kristian,
On Sunday, 27 November 2016 14:11:11 CET Kristian Nielsen wrote:
> Future compatibility between MariaDB client library and MySQL server, or
> wise versa, is rather more likely than other kinds of compatibility. This is
> because there is generally a strong desire to have the
Kristian Nielsen writes:
> that an old client can connect to a new server, _and_ that a new server can
> connect to an old client. This helps a lot to ensure that eg. new mariadb
Ehm. I mean "... and that a new client can connect to an old server", of
course.
- Kristian.
Robie Basak writes:
> On Sat, Nov 26, 2016 at 11:40:34PM +0100, Stefan Fritsch wrote:
>> Are the mariadb client libraries compatible with current mysql servers?
>
> I believe this is true at the moment, though as one might reasonably
> expect I believe this is "unsupported" by MySQL upstream. For
Hi Stefan,
On Sat, Nov 26, 2016 at 11:40:34PM +0100, Stefan Fritsch wrote:
> Are the mariadb client libraries compatible with current mysql servers?
I believe this is true at the moment, though as one might reasonably
expect I believe this is "unsupported" by MySQL upstream. For us, that
probably
6 matches
Mail list logo
