For ages. There are far too many websites still using mysql to drop it at the moment. I suspect it will be an option to either use 5.6 or switch to 7 via the control panel and thats the way it will stay for the forseeable future.
Any host not supporting mysql will lose custom, something they probably don't want to do.
I dont expect any sensible web developer to use that as an excuse to keep on using mysql as a way of communicating with a database.
This brings up another issue which is how to protect yourself from these inevitable advances in languages, etc. I certainly have no clause in my contracts stating, "Website guaranteed to function perfectly despite advancements in programming languages which may make previous versions obsolete."
This brings up another issue which is how to protect yourself from these inevitable advances in languages, etc. I certainly have no clause in my contracts stating, "Website guaranteed to function perfectly despite advancements in programming languages which may make previous versions obsolete."
It will all depend on what is considered a resonable time period for a web site to work correctly, and as a web developer you are the one that should know what is happening, and what the best practices and recommendations are for what you are using.
The dropping of the database connection for MySQL was publicised on the php org site 10 years ago, and the recommendation not to use for new sites about 8 years ago, plus if i remember correctly the short tag being made obsolete and do not use, was a few years before that.
If you have used anything after that, even if it was in a cms, it would be seen as your responsibility to have known about the recommendations and not to have used them.
You would not expect a mechanic to service your car/auto and not know the latest recommendations would you.
The PHP community was eager to adopt PHP7, which has now been out for more than a year. WordPress, Joomla and Drupal have all migrated to PHP7.
Strangely, Zend Server did not support PHP7 until I think around May of 2016. I believe CPanel was packaging PHP7 in the Spring of last year. . .as an option.
At this point, it's a PHP7 world. There may be government and educational servers out there that still can't support it. Any commercial webhost that can't support PHP7 by now is not a webhost you want to use.
Migrating to PHP7 involves more than just changing the database connection. There are some functions and syntax that have been dropped. If you ever start a PHP script with just <? instead of <?php it will break on PHP7. Zend Studio had a nice inspector routine that can check a whole site for PHP7 readiness.
Migrating to PHP7 involves more than just changing the database connection. There are some functions and syntax that have been dropped. If you ever start a PHP script with just <? instead of <?php it will break on PHP7. Zend Studio had a nice inspector routine that can check a whole site for PHP7 readiness.
Fortunately I got into the habit of using <?php
Where does one look for a simple list of php changes that are commonly likely to be used?
The short tag (<?) issue did catch me. Out of thousands of lines of PHP, there was one place where I used the short code, and it broke a script but did not throw an error!
Also, any classes you use written by others may not be PHP7 compatible. I found this true for the export to excel class I use.
For ages. There are far too many websites still using mysql to drop it at the moment. I suspect it will be an option to either use 5.6 or switch to 7 via the control panel and thats the way it will stay for the forseeable future.
Any host not supporting mysql will lose custom, something they probably don't want to do.
I dont expect any sensible web developer to use that as an excuse to keep on using mysql as a way of communicating with a database.