# Enable mysqlnd as default backend (not about enabling mysql by default) - Thread: https://externals.io/message/43835 - Original archive: https://news-web.php.net/php.internals/43835 - Started by Pierre Joye on 2009-05-04T18:31:01+00:00 - Messages: 8 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #43835 — Pierre Joye — 2009-05-04T18:31:01+00:00 URL: https://externals.io/message/43835#43835 Hi, Would it not easier and better to have mysqlnd as default backend for the mysql extensions (pdo, mysqli and mysql) when the configure option are used without value? I can already imagine the maintenance pains and the debugging nightmare for our users while working with a buggy libmysql instead of mysqlnd. Please note that it is only about using myslqnd by default, not about enabling mysqlnd by default (a vote has been done already on that and rejected). Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org | http://windows.php.net --- ## #43838 — Jani Taskinen — 2009-05-04T19:07:12+00:00 URL: https://externals.io/message/43835#43838 · In reply to: #43835 Pierre Joye kirjoitti: > Hi, > > Would it not easier and better to have mysqlnd as default backend for > the mysql extensions (pdo, mysqli and mysql) when the configure option > are used without value? I can already imagine the maintenance pains > and the debugging nightmare for our users while working with a buggy > libmysql instead of mysqlnd. Current status of mysqlnd does not warrant it being default. Just check the bug database.. --Jani --- ## #43840 — Lukas Kahwe Smith — 2009-05-04T19:35:42+00:00 URL: https://externals.io/message/43835#43840 · In reply to: #43835 > Hi, > > Would it not easier and better to have mysqlnd as default backend for > the mysql extensions (pdo, mysqli and mysql) when the configure option > are used without value? I can already imagine the maintenance pains > and the debugging nightmare for our users while working with a buggy > libmysql instead of mysqlnd. > > Please note that it is only about using myslqnd by default, not about > enabling mysqlnd by default (a vote has been done already on that and > rejected). Well atm I would prefer to stick with our current "plan". That being said I think in the end it will be the distro vendors that decide what will happen anyways. Bringing us back to the entire topic of the need for us to build better communication channels to them, so that we are in the loop about their needs and decisions and a way to better help them make the right decisions. regards, Lukas Kahwe Smith mls@pooteeweet.org --- ## #43857 — Pierre Joye — 2009-05-06T11:29:38+00:00 URL: https://externals.io/message/43835#43857 > Jani Taskinen schrieb: > > […] > > I would appreciate if the bug database could distinguish between feature > requests and bugs. it can, but then it gets even worst as you lost the category... a feature request being a category. -- Pierre http://blog.thepimp.net | http://www.libgd.org --- ## #43858 — Hannes Magnusson — 2009-05-06T11:37:26+00:00 URL: https://externals.io/message/43835#43858 · In reply to: #43857 > > > […] > > it can, but then it gets even worst as you lost the category... a > feature request being a category. We could apply the same workaround as we did for docs, use a status.. -Hannes --- ## #43859 — Pierre Joye — 2009-05-06T12:00:35+00:00 URL: https://externals.io/message/43835#43859 · In reply to: #43858 On Wed, May 6, 2009 at 1:37 PM, Hannes Magnusson wrote: > > > […] > > We could apply the same workaround as we did for docs, use a status.. I think it is a bug type (bug, feature request) not a status (closed, open, feedback, to be doc'ed, etc.) Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org --- ## #43860 — Johannes.Schlueter@Sun.COM — 2009-05-06T12:11:32+00:00 URL: https://externals.io/message/43835#43860 · In reply to: #43859 > On Wed, May 6, 2009 at 1:37 PM, Hannes Magnusson > wrote: > > […] > > I think it is a bug type (bug, feature request) not a status (closed, > open, feedback, to be doc'ed, etc.) Actually it is a flag as it is an "open" "feature request" in the "foobar category". So this might be a checkbox in the GUI ... (just my opinion) Maybe Philip and felipe2 can add that during the GSoC work johannes > > Cheers, -- Johannes Schlüter - MySQL Engineering, Connectors and Client Connectivity Sun Microsystems GmbH, Sonnenallee 1, 85551 Kirchheim-Heimstetten Amtsgericht München: HRB161028 Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Wolf Frenkel Vorsitzender des Aufsichtsrates: Martin Haering --- ## #43861 — Pierre Joye — 2009-05-06T12:47:35+00:00 URL: https://externals.io/message/43835#43861 · In reply to: #43860 2009/5/6 Johannes Schlüter : > > > […] > > Actually it is a flag as it is an "open" "feature request" in the > "foobar category". So this might be a checkbox in the GUI ... (just my > opinion) Call it JohnDoe, if you prefer, as long as it allows us to have all info (category, status, bug or FR :) -- Pierre http://blog.thepimp.net | http://www.libgd.org