Re: the changeover to mysqli [message #182936 is a reply to message #182930] |
Wed, 25 September 2013 21:46 |
Lew Pitcher
Messages: 60 Registered: April 2013
Karma:
|
Member |
|
|
On Wednesday 25 September 2013 16:21, in comp.lang.php, richard
(noreply(at)example(dot)com) wrote:
> On Wed, 25 Sep 2013 19:28:38 +0000 (UTC), Adam Harvey wrote:
>
>> On Wed, 25 Sep 2013 15:01:28 -0400, richard wrote:
>>> Hell, if that theory held true, we'd still be using tables.
>>> So why don't they just make the change, be done with it and let the
>>> people have the option of using either.
>>
>> The change you refer to happened nine years ago, when PDO and mysqli were
>> bundled into the release of PHP 5.0.0. You've had the option of using
>> either since then.
>>
>> Make no mistake: ext/mysql will be removed at a future date. The manual
>> text isn't hyperbole. All I'm saying is that it almost certainly won't be
>> next year, but that it will be soon enough that writing new code to use
>> ext/mysql is unwise.
>>
>> Adam
>
> then why hasn't the horses mouth followed their own demands?
> Of all the reference material I've seen on their site, all examples refer
> to mysql, NOT mysqli.
Richard, forget that we even suggested that you be proactive about your
site. You don't need to take any action now; you can wait until your
provider switches to whatever PHP release that removes the mysql_
interface, and then make your changes.
Of course, your site will be unavailable for the duration of your
changeover, and you won't be able to easily regression test the code
changes, but those are trivialities. I'm sure that you won't be off the air
for more than a few weeks.
As for the examples in the PHP documentation, I notice that most of them
are "contributed" by outsiders, as comments. I'm not certain that I'd trust
most of those examples to be representative of how the PHP maintainers
recommend that you do things.
HTH
--
Lew Pitcher
"In Skills, We Trust"
PGP public key available upon request
|
|
|