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?
Hi
Dne Thu, 12 Dec 2013 06:25:35 -0500 Marc Delisle marc@infomarc.info napsal(a):
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?
Sounds good.
Le 2013-12-12 09:03, Michal Čihař a écrit :
Hi
Dne Thu, 12 Dec 2013 06:25:35 -0500 Marc Delisle marc@infomarc.info napsal(a):
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?
Sounds good.
Done.
-
Marc Delisle -
Michal Čihař