| Re: the changeover to mysqli [message #182918 is a reply to message #182914] |
Wed, 25 September 2013 04:20  |
David Robley
Messages: 23
Registered: March 2013
Karma:
|
Junior Member |
|
|
richard wrote:
> The big push is on for scripters to change to to i.
> But nobody knows when that's going to happen.
_Providing your host supports it_, it happens when _you_ change your code.
The mysqli API has been available for some years now. I think it was
established in another thread that your hosting does support mysqli?
> As far as I can see, the "horses mouth" has not changed.
> the online resource manual STILL and totally, discusses mysql.
Well, yes, they would keep the information on how to use it as long as the
mysql API exists. How would you feel, as a user of it, if the mysql API docs
were removed? How would you know how to use it? Note that the mysql
extension docs do emphasise that it is deprecated as of ver 5.5 .
> They need to be making new pages that discuss what the changes are and how
> one is to make the changes properly.
That is pretty well covered in the mysqli documentation -
http://php.net/manual/en/book.mysqli.php
> Mr. Yates pointed out that changing over hundreds of pages can be a
> tedious task. They need to literally rewrite the book.
> NOW!
> And define when the changeover is to happen.
As said, the changeover can be done now - it depends on the programmer
writing the code as to which API is used.
>
> For now anyway, my little site only requires a few short pages and that
> can easily be changed.
So, why not do it now?
--
Cheers
David Robley
Insert inevitable trivial witticism of your choice.
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]