FUDforum
Fast Uncompromising Discussions. FUDforum will get your users talking.

Home » Imported messages » comp.lang.php » part 2 - file exists not working
Show: Today's Messages :: Polls :: Message Navigator
Return to the default flat view Create a new topic Submit Reply
Re: part 2 - file exists not working [message #182911 is a reply to message #182903] Wed, 25 September 2013 01:54 Go to previous messageGo to previous message
Scott Johnson is currently offline  Scott Johnson
Messages: 196
Registered: January 2012
Karma:
Senior Member
On 9/24/2013 4:08 PM, Twayne wrote:
> Finally, a voice of some reason instead of scare tactics even if still a
> little light in areas.
>
> On 2013-09-24 3:10 PM, Denis McMahon wrote:
>> On Tue, 24 Sep 2013 12:17:23 -0400, richard wrote:
>>
>>> I will change when my host changes.
>>> As the host is responsible for maintaining the server side, I can't do a
>>> damn thing until they do.
>
> And that's true.

Probably not in the context of using mysqli over mysql.
The host gives you both options (unless you have some budget host in
which case the jokes on him) UNTIL they switch to the version in which
the mysql_ is deprecated and your site breaks.

>
>>
>> Have you tested to see if mysqli is available on your host?
>
> I have, yes. I did it by contacting Support and they responded in the
> same day.
> And at least with MY host they have a "What's New" page to look for
> things like that, too. All version updates/upgrades/deletions are
> mentioned there.

I am pretty sure he was talking to Richard.


>>
>> If it is, why are you not using it? mysqli is not something that your
>> hosting server will expect to announce the roll out of, indeed it's quite
>> possible that it's been on the server for several years already.
>
> The poster already mentioned why he wasn't using it.
> Not necessarily in most cases IME at least. Although, if it's avaliable,
> it's a good move to be checking into what it takes to make the revision
> IFF it will benefit you.

The benefit would be your site does not break once the php version
deprecates the currently used functions.

There is a solid reason that the manual says you should NOT be using it
since it will not exist in the future.

> ...
>> It is quite possible for both these sets of interface functions to be
>> installed in the same php build. Certainly this is the case in eg PHP
>> Version 5.3.10-1ubuntu3.8 on my server.
>
> Exactly.

It exists not so you can build a new site upon it. It does so to allow
those who in the past had only that function and gives them reasonable
amount of time to switch to the new one.

>
> ...
>> If you check now and discover that yes, your server does in fact also
>> support mysqli_* functions already, then you can start migrating your
>> code from mysql_* functions to mysqli_* functions now so that you won't
>> get caught out in a future upgrade it
>
> Unless it's of no benefit; you already said they may both exist and if
> that's the case and one gains no benefit from changing, well, ... .

Again we are not talking about the benefit of memory or speed or ease of
programming, the benefit is that you site keeps working. A pretty solid
benefit if you ask me or you just end up having a hard drive full of
useless files.

>>
>> Note that checking doesn't mean you look to see if the database has
>> changed from mysql to mysqli, because that's not what happens. Checking
>> means creating a page called something like sysinfo.php that contains the
>> following code:
>>
>> <?php
>> phpinfo();
>>
>> and then putting that page in your website, and then going to the url:
>>
>> http://your_website_name_here/sysinfo.php
>>
>> Then scroll down the output until you come to the mysqli section. The
>> presence of this section means that the mysqli interface modules are
>> installed in the servers php code.
>
> Good advice. But if someone is so new that phpinfo.php & 'sysinfo' is
> news to them, well, they've a lot more than mysql to get up to date on.

This is the one statement that I agree on with a but. We have pointed
out the function that is going bye bye and gave links on how to use the
new one which does not differ all too much from the former in the
context of the OPs question. If that is too difficult then I do think
we (he) is going to and has had a long frustrating journey.

>>
>> Hostgator support PHP 5, so their PHP build includes mysqli_* functions.
>> The only thing stopping you using mysqli_* functions instead of mysql_*
>> functions is *YOU*!
>
> And a learning curve, and time (which is money), and ... etc. etc..
> Nothing is ever gained from advice like that.

In all professions you have to stay current with new way of doing things
and toss the old.

You have to learn how to keep up to date with the server needs, it is
part of the job. And by keeping up to date, your site is less likely to
break and cause even more money when you have a down site and still have
to find where it broke and also to learn the new functions anyhow.

Why not do it while the site is still functioning and no one public is
the wiser.
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [urgent] need solution of Questions, in context of PHP5
Next Topic: Host recommendations (slightly OT)
Goto Forum:
  

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Sat Nov 23 08:53:37 GMT 2024

Total time taken to generate the page: 0.04972 seconds