On Wed 27 Feb 2002 (06:31 -0700), Zak Greant wrote:
> On Wed, 2002-02-27 at 05:40, [EMAIL PROTECTED] wrote:
> > Hello,
> >
> > I think it's a bad idea to patch extension for flaws not in PHP itself.
> > Furthermore, this adds a performance loss to every query. Did you do any
> > benchmarks with i
On Wed, 2002-02-27 at 05:40, [EMAIL PROTECTED] wrote:
> Hello,
>
> I think it's a bad idea to patch extension for flaws not in PHP itself.
> Furthermore, this adds a performance loss to every query. Did you do any
> benchmarks with it? Anyway... I still think it's a bad idea, and from what
> I've
Hello,
I think it's a bad idea to patch extension for flaws not in PHP itself.
Furthermore, this adds a performance loss to every query. Did you do any
benchmarks with it? Anyway... I still think it's a bad idea, and from what
I've heard Zak is talking with MySQL about this.
Derick
On Wed, 27 F
On Tue 26 Feb 2002 (21:58 +0100), Jim Segrave wrote:
>
> I was looking at the posting from "James E. Flemer" <[EMAIL PROTECTED]>
> and decided to try adding a bit more to it.
>
> ** This code is compiled, but not tested **
I now have a patch against
/* $Id: php_mysql.c,v 1.97.2.3 2001/12/09