# Make mysqlnd default over libmysql in 5.4

- Thread: https://externals.io/message/55084
- Original archive: https://news-web.php.net/php.internals/55084
- Started by johannes.schlueter@oracle.com on 2011-09-02T12:27:04+00:00
- Messages: 67
- Page 1 of 3: messages 1 to 25 (25 per page, add `?page=N` to the URL)
- Next page: https://externals.io/message/55084.md?page=2
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · RFCs at https://externals.io/rfc.md · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #55084 — johannes.schlueter@oracle.com — 2011-09-02T12:27:04+00:00

URL: https://externals.io/message/55084#55084

Hi,

when building PHP using
  (I) ./configure --with-mysql --with-mysqli --with-pdo-mysql
you currently get a build using the system default libmysql, usually
in /us or
such. Alternatively PHP can be built using
 (II) ./configure --with-mysqli=mysqlnd [...]
to build the MySQL extensions using the mysqlnd library.

I would like to change mysqlnd's config9.m4 file to build PHP using
mysqlnd when being called in form (I). Users would still be able to
enforce libmysql by passing a path, like /usr.

There are two main reasons I see for this:
  a) Different libmysql versions have slightly different behavior,
     which shows in our tests. We can't have both, a good test coverage
     and cover all these differences. By using mysqlnd we have a clear
     behavior every PHP developer can rely on.
  b) We provide different extensions (pecl/mysqlnd_*) which
     improve/extend mysqlnd functionality. By having mysqlnd as default
     these are better usable by users.

Opinions?

johannes
-- 
Johannes Schlüter, Oracle
MySQL Engineering - MySQL Connectors and Client Connectivity

---

## #55085 — Reindl Harald — 2011-09-02T12:56:46+00:00

URL: https://externals.io/message/55084#55085 · In reply to: #55084

please do it

we are using mysqlnd on some hundret domains with all sort of php-software
since PHP 5.3.3 (the first 5.3 version we used) and thinking back how
hard it was to get the fedora-srpm chnaged to build with mysqlnd
my opinion is drop the libmysql-support completly

you named the main-reason for that: auto-tests

supporting both without a real good reason will have permanently
side-effects covered in bugreports and instead maintain two code-paths
from the view of quality it would be better to optimize mysqlnd
if there is something missing what i do not know now

Am 02.09.2011 14:27, schrieb Johannes Schlüter:
> Hi,
> 
> when building PHP using
>   (I) ./configure --with-mysql --with-mysqli --with-pdo-mysql
> you currently get a build using the system default libmysql, usually
> in /us or
> such. Alternatively PHP can be built using
>  (II) ./configure --with-mysqli=mysqlnd [...]
> to build the MySQL extensions using the mysqlnd library.
> 
> I would like to change mysqlnd's config9.m4 file to build PHP using
> mysqlnd when being called in form (I). Users would still be able to
> enforce libmysql by passing a path, like /usr.
> 
> There are two main reasons I see for this:
>   a) Different libmysql versions have slightly different behavior,
>      which shows in our tests. We can't have both, a good test coverage
>      and cover all these differences. By using mysqlnd we have a clear
>      behavior every PHP developer can rely on.
>   b) We provide different extensions (pecl/mysqlnd_*) which
>      improve/extend mysqlnd functionality. By having mysqlnd as default
>      these are better usable by users.
> 
> Opinions?
> 
> johannes

---

## #55087 — Sebastian Bergmann — 2011-09-02T13:58:29+00:00

URL: https://externals.io/message/55084#55087 · In reply to: #55084

Am 02.09.2011 14:27, schrieb Johannes Schlüter:
> I would like to change mysqlnd's config9.m4 file to build PHP using
> mysqlnd when being called in form (I). Users would still be able to
> enforce libmysql by passing a path, like /usr.

 PLEASE do it :-)

-- 
Sebastian Bergmann                    Co-Founder and Principal Consultant
http://sebastian-bergmann.de/                           http://thePHP.cc/

---

## #55088 — Rasmus Lerdorf — 2011-09-02T15:32:34+00:00

URL: https://externals.io/message/55084#55088 · In reply to: #55084

> Hi,
> 
> when building PHP using
>   (I) ./configure --with-mysql --with-mysqli --with-pdo-mysql
> you currently get a build using the system default libmysql, usually
> in /us or
> such. Alternatively PHP can be built using
>  (II) ./configure --with-mysqli=mysqlnd [...]
> to build the MySQL extensions using the mysqlnd library.
> 
> I would like to change mysqlnd's config9.m4 file to build PHP using
> mysqlnd when being called in form (I). Users would still be able to
> enforce libmysql by passing a path, like /usr.
> 
> There are two main reasons I see for this:
>   a) Different libmysql versions have slightly different behavior,
>      which shows in our tests. We can't have both, a good test coverage
>      and cover all these differences. By using mysqlnd we have a clear
>      behavior every PHP developer can rely on.
>   b) We provide different extensions (pecl/mysqlnd_*) which
>      improve/extend mysqlnd functionality. By having mysqlnd as default
>      these are better usable by users.
> 
> Opinions?

I was actually going to suggest doing this in 5.4 and trunk but didn't
get around to writing the email yet.

-Rasmus

---

## #55090 — Mike Willbanks — 2011-09-02T17:19:00+00:00

URL: https://externals.io/message/55084#55090

forgot to include everyone on this response - sorry.

when building PHP using
> > […]
>
> Also; while we're talking about it; can we do something about the default
> socket location OR change configuring it in 3 places for pdo_mysql; mysqli;
> mysql?!   Maybe a mysqlnd_default_socket - or autoconf magic (for instance
> RedHat/CentOS MySQL provided RPM's default to: /var/lib/mysql/mysql.sock;
> Ubuntu/Debian default is: /var/run/mysqld/mysqld.sock, lastly is the current
> php default and mysql source default of /tmp/mysql.sock).  It seems like it
> could do a quick check either by platform or check to see if it is already
> there to change the default on build.  Only reason for bringing this up is
> that I've been burned a few times on this one (for instance pdo_mysql is
> configured but mysqli was not for the default socket locations).
>
> Regards,
>
> Mike

---

## #55097 — Christopher Jones — 2011-09-02T19:17:14+00:00

URL: https://externals.io/message/55084#55097 · In reply to: #55088

> 
> > […]
>
> I was actually going to suggest doing this in 5.4 and trunk but didn't
> get around to writing the email yet.
>
> -Rasmus
>

I'm +1 for this.  I think the decision & implementation needs to be done
before Beta or deferred to trunk.

Chris

-- 
Email: christopher.jones@oracle.com
Tel:  +1 650 506 8630
Blog:  http://blogs.oracle.com/opal/

---

## #55098 — Stas Malyshev — 2011-09-02T19:24:32+00:00

URL: https://externals.io/message/55084#55098 · In reply to: #55097

Hi!


> I'm +1 for this.  I think the decision&  implementation needs to be done
> before Beta or deferred to trunk.

Frankly, I'd be more comfortable with trunk. We have enough trouble with 
unit tests etc. before the beta, and introducing profound change in 
default without enough time for discussion and gathering feedback from 
packagers, etc. doesn't look a smart thing to do.

-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227

---

## #55099 — Christopher Jones — 2011-09-02T19:39:41+00:00

URL: https://externals.io/message/55084#55099 · In reply to: #55098

> Hi!
>
> 
> > […]
>
> Frankly, I'd be more comfortable with trunk. We have enough trouble with unit tests etc. before the beta, and introducing profound change in default without enough time for discussion and gathering feedback from packagers, etc. doesn't look a smart thing
> to do.
>

Let's see what other comments come in.

Doing it in 5.4 will make it easier to stabilize the tests and allow
trunk & 5.4 build & tests to be in sync.  The user benefits include
more predictable behavior on edge cases, and presumably better
features & quality that core developers could fill their time working
on.

Chris

-- 
Email: christopher.jones@oracle.com
Tel:  +1 650 506 8630
Blog:  http://blogs.oracle.com/opal/

---

## #55100 — Ulf Wendel — 2011-09-02T19:58:57+00:00

URL: https://externals.io/message/55084#55100 · In reply to: #55098

Am 02.09.2011 21:24, schrieb Stas Malyshev:
> Hi!
>
> 
> > […]
>
> Frankly, I'd be more comfortable with trunk. We have enough trouble with
> unit tests etc. before the beta, and introducing profound change in
> default without enough time for discussion and gathering feedback from
> packagers, etc. doesn't look a smart thing to do.

Hmm, I do not understand the unit test argument. Non-portable tests 
exist regardless of what the config.m4 default is.

We are talking about making mysqlnd as a compile default, if not 
explicitly choosing libmysql to compile against. This is no attempt to 
remove libmysql support. I somewhat assume most packagers do explicitly 
set libmysql path already and do not rely on any magic, because they 
don't use MySQL's default source layout. However, argument taken, let's 
do some checks who (Debian, Ubuntu, OpenSuse, RH, ...) does not set 
libmysql path during compile.

mysqlnd was introduced with PHP 5.3. IMHO, it has matured quite well. 
Mysqlnd reduces the PHP projects dependency on anybody controlling the 
library. This has been a major pain in the past. Think of builds made 
against outdated versions of libmysql, think of waiting for new libmysql 
releases, think of compilers not supported by libmysql, think of license 
discussion, think of accepting code contributions and so forth.

 From a user perspective mysqlnd removes the need to install libmyql 
prior to building and a has a couple of neat features not available with 
libmysql, for example, the plugins.

Ulf

---

## #55102 — Michael Stowe — 2011-09-02T20:04:02+00:00

URL: https://externals.io/message/55084#55102 · In reply to: #55100

+1 and agree that it should be implemented before the beta.






> Am 02.09.2011 21:24, schrieb Stas Malyshev:
>
>  Hi!
> > […]
>
> Hmm, I do not understand the unit test argument. Non-portable tests exist
> regardless of what the config.m4 default is.
>
> We are talking about making mysqlnd as a compile default, if not explicitly
> choosing libmysql to compile against. This is no attempt to remove libmysql
> support. I somewhat assume most packagers do explicitly set libmysql path
> already and do not rely on any magic, because they don't use MySQL's default
> source layout. However, argument taken, let's do some checks who (Debian,
> Ubuntu, OpenSuse, RH, ...) does not set libmysql path during compile.
>
> mysqlnd was introduced with PHP 5.3. IMHO, it has matured quite well.
> Mysqlnd reduces the PHP projects dependency on anybody controlling the
> library. This has been a major pain in the past. Think of builds made
> against outdated versions of libmysql, think of waiting for new libmysql
> releases, think of compilers not supported by libmysql, think of license
> discussion, think of accepting code contributions and so forth.
>
> From a user perspective mysqlnd removes the need to install libmyql prior
> to building and a has a couple of neat features not available with libmysql,
> for example, the plugins.
>
> Ulf
>
>
> --
> 
> 
>
>


-- 
-----------------------

"My command is this: Love each other as I
have loved you."                         John 15:12

---

## #55105 — johannes.schlueter@oracle.com — 2011-09-02T20:14:43+00:00

URL: https://externals.io/message/55084#55105 · In reply to: #55098

> Hi!
> 
> 
> > […]
> 
> Frankly, I'd be more comfortable with trunk. We have enough trouble with 
> unit tests etc. before the beta, and introducing profound change in 
> default without enough time for discussion and gathering feedback from 
> packagers, etc. doesn't look a smart thing to do.

Actually the testing point was the trigger for me to write this mail.
I/We should have done it earlier but for me it's too normal to build
using mysqlnd.

Looking at the tests we have: Most tests are written with mysqlnd in
focus. mysqlnd is what we (Oracle/MySQL) test the most in PHP
perspective for quite some time already. By making mysqlnd the default
we remove one moving piece out of the test equation which simplifies
tests[1]. (we still have multiple server versions to keep in mind ...)
Looking at the last test results Rasmus' sent (using my own would be a
lame cheat ;-) ) he had 6 mysqlnd test failures of which we fixed most
(we also fixed others) whereas libmysql builds have more (depending on
versions). Yes we could spend a few more days and do massive builds of
different combinations (and make the tests more complex to cover
multiple cases) or focus on having a good and stable default which
behaves the same on all platforms.

Looking at distributions: On Windows (which probably is the single most
used build of PHP at all) we're using mysqlnd by default since 5.3.0.
This had some pain in the beginning but went, aside from the recent
OpenSSL issue, quite soomthly. Some other packagers we could meanwhile
convince to use mysqlnd others told me things which boil down to "if PHP
makes it default we use it". So I see little risk there.

johannes

[1] Yes, we will still allow building with libmysql and we will fix bugs
reported there and we will verify it works but focus on mysqlnd, as
we're actually handling it already

-- 
Johannes Schlüter, Oracle
MySQL Engineering - connectors and Client Connectivity

---

## #55104 — Lester Caine — 2011-09-02T20:17:14+00:00

URL: https://externals.io/message/55084#55104 · In reply to: #55088

Rasmus Lerdorf wrote:
> I was actually going to suggest doing this in 5.4 and trunk but didn't
> get around to writing the email yet.

It would still be nice to be able to simply switch off MySQL for those of us who 
do not have it installed ...
It gets annoying when PHP forces the installation of MySQL in a distribution and 
then prevents disabling it. It is another example of why a more modular approach 
does make sense!

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php

---

## #55106 — Stas Malyshev — 2011-09-02T20:38:36+00:00

URL: https://externals.io/message/55084#55106 · In reply to: #55105

Hi!


> Looking at the tests we have: Most tests are written with mysqlnd in
> focus. mysqlnd is what we (Oracle/MySQL) test the most in PHP
> perspective for quite some time already. By making mysqlnd the default
> we remove one moving piece out of the test equation which simplifies
> tests[1]. (we still have multiple server versions to keep in mind ...)

Are you implying you would no longer fix failures on libmysql? If so, we 
should announce libmysql is unsupported and I definitely am against 
doing anything like this in 5.4. If you are not meaning this, then 
absolutely nothing changes with regard to unit tests - they still must 
pass on both modes.

> different combinations (and make the tests more complex to cover
> multiple cases) or focus on having a good and stable default which
> behaves the same on all platforms.

We should focus on having unit tests passing, otherwise there's no point 
in having them. If we do not drop libmysql support, we should have 
exactly the same results in libmysql as we have in mysqlnd. Otherwise it 
is called "unsupported configuration". If the plan is to keep pretense 
of supporting libmysql while actually neglecting to do fixes and fix 
tests for it in hope that people would eventually switch - this is not 
the right way to do it.
-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227

---

## #55108 — Ferenc Kovacs — 2011-09-02T20:41:09+00:00

URL: https://externals.io/message/55084#55108 · In reply to: #55106

2011/9/2 Stas Malyshev <smalyshev@sugarcrm.com>:
> Hi!
>
> 
> > […]
>
> Are you implying you would no longer fix failures on libmysql? If so, we
> should announce libmysql is unsupported and I definitely am against doing
> anything like this in 5.4. If you are not meaning this, then absolutely
> nothing changes with regard to unit tests - they still must pass on both
> modes.
>

I think you missed the referenced [1]:

[1] Yes, we will still allow building with libmysql and we will fix bugs
reported there and we will verify it works but focus on mysqlnd, as
we're actually handling it already

-- 
Ferenc Kovács
@Tyr43l - http://tyrael.hu

---

## #55109 — Stas Malyshev — 2011-09-02T20:44:12+00:00

URL: https://externals.io/message/55084#55109 · In reply to: #55108

Hi!


> I think you missed the referenced [1]:
>
> [1] Yes, we will still allow building with libmysql and we will fix bugs
> reported there and we will verify it works but focus on mysqlnd, as
> we're actually handling it already

I did not miss it - I do not see what it means. Either we support both - 
and then for the matter of development and testing nothing changes - or 
something changes, namely "we remove one moving piece out of the test 
equation", the moving piece being libmysql - and "remove" means 
"remove". I just don't see how you can have both of these things at the 
same time.
-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227

---

## #55110 — Ulf Wendel — 2011-09-02T20:48:26+00:00

URL: https://externals.io/message/55084#55110 · In reply to: #55104

Am 02.09.2011 22:17, schrieb Lester Caine:
> Rasmus Lerdorf wrote:
> > […]
>
> It would still be nice to be able to simply switch off MySQL for those
> of us who do not have it installed ...
> It gets annoying when PHP forces the installation of MySQL in a
> distribution and then prevents disabling it. It is another example of
> why a more modular approach does make sense!

Lester,

do I understand that you are afraid of a PHP which comes with MySQL 
support that cannot be disabled?

I don't think the proposal goes like that. The proposal is to change the 
default library, if not set during compile, used by the MySQL 
extensions, if enabled, from libmysql to mysqlnd. This is independent of 
the questions:

  - if any MySQL extension shall be enabled by default
  - if PHP can be built without MySQL support

And, I said it in the other email, this is no attempt to remove libmysql 
support.

I may be wrong but your concern - as valid as it is - seems a bit off 
topic, no?

Ulf

---

## #55111 — Ferenc Kovacs — 2011-09-02T20:48:33+00:00

URL: https://externals.io/message/55084#55111 · In reply to: #55109

> Hi!
>
> 
> > […]
>
> I did not miss it - I do not see what it means. Either we support both - and
> then for the matter of development and testing nothing changes - or
> something changes, namely "we remove one moving piece out of the test
> equation", the moving piece being libmysql - and "remove" means "remove". I
> just don't see how you can have both of these things at the same time.

I think that Johannes means that mysqld would be the preferred or
baseline for the mysql tests.
maybe supporting IE6 would be a good metaphor: you could say that you
support every browser equally, or you could say that you write your
stuff for the modern browsers and tests it against IE6 and fix where
necessary.
Johannes, is this what you had in mind?


-- 
Ferenc Kovács
@Tyr43l - http://tyrael.hu

---

## #55112 — johannes.schlueter@oracle.com — 2011-09-02T20:57:20+00:00

URL: https://externals.io/message/55084#55112 · In reply to: #55111

> 
> > […]
> 
> I think that Johannes means that mysqld would be the preferred or
> baseline for the mysql tests.
> maybe supporting IE6 would be a good metaphor: you could say that you
> support every browser equally, or you could say that you write your
> stuff for the modern browsers and tests it against IE6 and fix where
> necessary.
> Johannes, is this what you had in mind?

Thanks, I like your analogy and don't have a better one.

johannes

> 
> -- 
> Ferenc Kovács
> @Tyr43l - http://tyrael.hu

---

## #55113 — Ulf Wendel — 2011-09-02T21:12:57+00:00

URL: https://externals.io/message/55084#55113 · In reply to: #55112

Am 02.09.2011 22:57, schrieb Johannes Schlüter:
> 
> > […]
>
> Thanks, I like your analogy and don't have a better one.


Let's see if I get it right.

Johannes and I say:

  - libmysql support is there and it will stay there
  - libmysql shall continue to be supported
  - tests shall be written in a portable way, whenever possible

We furthermore said, let me put it straigt:

  - we failed to catch some libmysql/MySQL/test version combination 
portability issues - shit happens, sorry for that
  - testing any extension that has external dependencies is a pain

I think, such a statement is quite a big step towards your test 
concerns, Stas. Ultimately, I still don't get what you (Stas) are after 
with the test discussion. Have I missed any of your worries?

Ulf

---

## #55114 — Stas Malyshev — 2011-09-02T21:20:52+00:00

URL: https://externals.io/message/55084#55114 · In reply to: #55112

Hi!


> > […]
>
> Thanks, I like your analogy and don't have a better one.

That is exactly the problem - *nobody* says "we support every browser 
equally" and most sites/applications explicitly say "we do not support 
IE6" and every bug on IE6 is rejected unless it happens in some other 
place. If you plan to give libmysql the same treatment it means removing 
support for it, plain and simple. If you mean something else, please 
explain.

-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227

---

## #55115 — Ulf Wendel — 2011-09-02T21:29:35+00:00

URL: https://externals.io/message/55084#55115 · In reply to: #55114

Am 02.09.2011 23:20, schrieb Stas Malyshev:
> Hi!
>
> 
> > […]
>
> That is exactly the problem - *nobody* says "we support every browser
> equally" and most sites/applications explicitly say "we do not support
> IE6" and every bug on IE6 is rejected unless it happens in some other
> place. If you plan to give libmysql the same treatment it means removing
> support for it, plain and simple. If you mean something else, please
> explain.

Stas,

what is not clear from my last mail?

Ulf

---

## #55116 — Stas Malyshev — 2011-09-02T21:30:40+00:00

URL: https://externals.io/message/55084#55116 · In reply to: #55113

Hi!


> I think, such a statement is quite a big step towards your test
> concerns, Stas. Ultimately, I still don't get what you (Stas) are after
> with the test discussion. Have I missed any of your worries?

My concerns is first and foremost to have unit tests passing and 
compatibility API issues sorted out - such as same functions producing 
different semantics on libmysql and mysqlnd. This is my primary concern, 
especially if we want to have beta anytime soon :)

That said, talk about "removing one moving piece out of the test
equation" and comparing libmysql support to universally unsupported and 
officially considered dead IE6 makes me worried, when it comes from 
mysql extension maintainers. Your clarification about it in this letter 
makes clear my concerns are unfounded, which is good. Let's now get back 
to the first part - the failing tests.
-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227

---

## #55117 — Lester Caine — 2011-09-02T21:33:10+00:00

URL: https://externals.io/message/55084#55117 · In reply to: #55110

Ulf Wendel wrote:
> Am 02.09.2011 22:17, schrieb Lester Caine:
> > […]
>
> Lester,
>
> do I understand that you are afraid of a PHP which comes with MySQL support that
> cannot be disabled?
>
> I don't think the proposal goes like that. The proposal is to change the default
> library, if not set during compile, used by the MySQL extensions, if enabled,
> from libmysql to mysqlnd. This is independent of the questions:
>
>   - if any MySQL extension shall be enabled by default
>   - if PHP can be built without MySQL support
>
> And, I said it in the other email, this is no attempt to remove libmysql support.
>
> I may be wrong but your concern - as valid as it is - seems a bit off topic, no?

If the MySQL support was loaded as an extension rather than being forced on 
everybody, then you could provide either version of library just by selecting 
the right extension? Just as we provide special builds of other extensions to 
allow backwards compatibility ... we HAD dropped MySQL dependence at one point, 
but it seems to have crept back in without any particular agreement?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php

---

## #55118 — Ulf Wendel — 2011-09-02T21:51:51+00:00

URL: https://externals.io/message/55084#55118 · In reply to: #55116

Am 02.09.2011 23:30, schrieb Stas Malyshev:
> Hi!
>
> 
> > […]
>
> My concerns is first and foremost to have unit tests passing and
> compatibility API issues sorted out - such as same functions producing
> different semantics on libmysql and mysqlnd. This is my primary concern,
> especially if we want to have beta anytime soon :)

Stas,

if you are really concerned about tests, aren't you a bit late, are all 
the 5.3 releases to be considered instable. I mean, they use the same 
tests. Andrey may know better, but I even assume mysqlnd to be very, 
very similar in 5.3 and 5.4. How strong is your argument, how many 
critical differences are you aware of that prevent a config.m4 change? 
If there are criticial differences of much practical relevance, how 
could we miss them, why are we not seeing more bug reports?

With all given respect, I think you are going a bit far here. You seem 
to be extrapolating from "test x does not work in configuration y" to "z 
is instable/incompatible with y".

You have one argument against the config.m4 change that I get - the 
packaging/distribution one. But the test does not pass with X/Y/Z_old 
seems a bit weak to me.

I hope, nobody is angry if I call it a day.

Enjoy the weekend,
Ulf

---

## #55120 — Pierre Joye — 2011-09-02T22:00:08+00:00

URL: https://externals.io/message/55084#55120 · In reply to: #55106

2011/9/2 Stas Malyshev <smalyshev@sugarcrm.com>:
> Hi!
>
> 
> > […]
>
> Are you implying you would no longer fix failures on libmysql?

The problem is the exact opposite, the fact that mysqlnd is not
default makes the bugs hunting harder for this backend. Most bad bugs
(thread safe related for example) come from the windows where mysqlnd
is already the only and default option. So having more users now in
5.4-beta will only help to make it even more stable.

While limysql is still a good alternative (slightly faster in some
cases) and does not have some of the TS issues we meet with mysqlnd,
but both are certainly temporary states.

Cheers,
-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org

---

Next page: https://externals.io/message/55084.md?page=2
