Hi,
while removing the "extension" directive, I noticed that there is an
undocumented possible value, "drizzle".
I guess it's undocumented because the corresponding library is marked as
being experimental and not to be used in production.
So what's the status about these experimentations? Should we keep this
directive in case someone wants to experiment?
Note that connection via mysqli works fine with a Drizzle server.
--
Marc Delisle
http://infomarc.info | http://phpmyadmin.net
Hi All,
I have tried to fix the bug #2760 . Here is the pull request I have
submitted https://github.com/phpmyadmin/phpmyadmin/pull/795 . Please review
and test if it's working fine.
Thanks and Regards
Smita Kumari
Hi,
Our GSoC round up post was published on the Google Open Source blog [0].
Thanks to all who contributed to write this text and to everyone
(mentors, students, ...) who contributed in making GSoC 2013 a succes
for phpMyAdmin.
[0] http://google-opensource.blogspot.be/2013/11/google-summer-of-code-veteran-…
--
Kind regards,
Dieter Adriaenssens
Hi,
yesterday at our team meeting, we decided that for the 4.2 version, we
would tell users that the mysql extension is deprecated, and we would
remove support for it in the 4.3 version.
I would like to go further (for 4.2), to better help our users:
- remove the $cfg['Servers'][$i]['extension'] directive
- always try to load mysqli
- if this fails, try to load mysql
-- if this fails, give up (like we currently do)
-- if this works, display a strong message explaining that this
extension is no longer recommended and will be deprecated in the next
version
Comments?
--
Marc Delisle
http://infomarc.info | http://phpmyadmin.net