| Re: the changeover to mysqli [message #182955 is a reply to message #182937] |
Thu, 26 September 2013 23:09   |
Thomas 'PointedEars'
Messages: 701
Registered: October 2010
Karma:
|
Senior Member |
|
|
Christoph Michael Becker wrote:
> Tim Streater wrote:
>> In article <1cun3xxz7nbpj(dot)zop5ye5ou0f7$(dot)dlg(at)40tude(dot)net>,
>> richard <noreply(at)example(dot)com> wrote:
>>> Let's face it, html has deprecated a ton of things which are still in
>>> use. Why? because a hoard of people refuse to upgrade their systems.
>>
>> You mean, update their web pages. Fat chance of that happening. And
>> because browsers still support almost everything that was ever
>> introduced, bar a couple of minor things, I see no reason, by and large,
>> to do so either. I just use the HTML5 doctype to ensure standards mode.
>
> And that is exactly the reason, why those deprecated features won't be
> removed--because it would break too many existing sites. If there were
> less websites relying on obsolete features, the browser's could be
> purged, which would be beneficial to ease further development.
>
> The situation is similar with regard to the original MySQL extension.
> Cf. <https://wiki.php.net/rfc/mysql_deprecation>.
The most important issue with the mysql extension that appears to be
overlooked by all discussing so far is not that the extension will be
removed later. It is the fact that it is patently inefficient and insecure
by comparison *right now*. It has no native support for
- reading a result into an array *without* a loop (there is no
mysql_fetchall)
- transactions
- Prepared Statements
and so on.
It is no longer officially supported by the MySQL vendor, Oracle. As a
result, it does not support natively (if at all; I have not tried) features
introduced in MySQL 5.1 and above. The current MySQL stable version is 5.6.
The latest bugfix of php_mysql.c was in 2011:
<http://git.php.net/?p=php-src.git ;a=history;f=ext/mysql/php_mysql.c;h=88bb9ab21ef9fb15a147fc776569e8548e0be8 3b;hb=HEAD >
That was 2 years ago. An eternity in computer technology, considering that
updates and especially security updated for maintained software are released
on a daily (e.g., security.debian.org) to at most bimonthly (e.g., Firefox)
basis.
See also <http://php.net/manual/en/mysqlinfo.api.choosing.php>
Deprecation is not merely a documentation status with PHP; it has
consequences for running PHP code:
<http://git.php.net/?p=php-src.git;a=commitdiff;h=b7091aaf0137d97cf4aa4a402ec50b3946d369c0>
IOW, E_DEPRECATED warnings may pile up in your log and make the application
and the server run slower than it could be.
Insofar your well-intentioned comparison with deprecated HTML features is
missing the point.
Anyhow, I am afraid that none of our arguments will be convincing enough for
*seemingly* natural-born ignorants like “richard”. So why not save free-
time and just stop feeding the likely troll – both of them?
PointedEars
--
Prototype.js was written by people who don't know javascript for people
who don't know javascript. People who don't know javascript are not
the best source of advice on designing systems that use javascript.
-- Richard Cornford, cljs, <f806at$ail$1$8300dec7(at)news(dot)demon(dot)co(dot)uk>
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]