On Wed, Nov 26, 2008 at 1:45 PM, Chris <[EMAIL PROTECTED]> wrote:
>> It's bad if you ever want to use something other than mysqli! Imagine
>> your company switching to another database server. You'd have to
>> rewrite code in hundreds of functions!
[...]
> You're going to have a lot more problems
Fergus Gibson wrote:
-- Forwarded message --
From: Fergus Gibson <[EMAIL PROTECTED]>
Date: Wed, Nov 26, 2008 at 11:55 AM
Subject: Re: Fwd: [PHP-DB] MySQLi connections
To: "J. Hill" <[EMAIL PROTECTED]>
On Tue, Nov 25, 2008 at 3:12 PM, J. Hill <[EMAIL
-- Forwarded message --
From: Fergus Gibson <[EMAIL PROTECTED]>
Date: Wed, Nov 26, 2008 at 11:55 AM
Subject: Re: Fwd: [PHP-DB] MySQLi connections
To: "J. Hill" <[EMAIL PROTECTED]>
On Tue, Nov 25, 2008 at 3:12 PM, J. Hill <[EMAIL PROTECTED]> wrote:
>
Thank you for your response.
I am glad to hear that the structure is not a problem, but I suspect he
new about singletons (I forgot that term) as he was an old C/C++
progammer (now retired), although I gather he was not a PHP guy.
In all other respects, his code and documentation seem very go
J. Hill wrote:
Reading the thread on mysqli connection issues, I am curious if anyone
knows of a downside to creating a connection from a configuration page
and using it as a global in all functions?
Good way to do it. You create the connection at the start and use the
same thing throughout t
Reading the thread on mysqli connection issues, I am curious if anyone
knows of a downside to creating a connection from a configuration page
and using it as a global in all functions?
I am used to creating a class and a database handle for functions to
use, but I inherited an intranet that ju
