I'm using the current CVS (4.0.8-dev)- It's spectacular. Lower memory
usage, more descriptive debug, better control over it. Tons more options,
smaller code, much much faster.
Can you trust it- sure. It isn't a release candidate. It is the
current development version. As they find problems, they get fixed. As
long as you keep a bit on top you are fine. If anything it is _MORE_ secure
than the current version, as any security problems were fixed earlier as
soon as they get found, and new bugs aren't known yet. I'm seriously
impressed with it and feel like I will be using the CVS code quite a bit
more. Any bugs Zend memory manager cleans up anyway.
Note: if you are not having the problem of 0 rows or buffer overruns,
don't bother upgrading as it will not benefit you. Clearly I was and the
new code fixed the flaws in the existing code for my usage.
--
Mike
----- Original Message -----
From: "Martín Marqués" <martin@bugs.unl.edu.ar>
To: "Mike Rogers" <temp6453@hotmail.com>
Cc: <pgsql-hackers@postgresql.org>; <pgsql-php@postgresql.org>
Sent: Thursday, September 27, 2001 5:55 PM
Subject: Re: [PHP] [HACKERS] [BUGS] PostgreSQL / PHP Overrun Error
> On Mié 26 Sep 2001 22:51, Mike Rogers wrote:
> > There is a problem in PHP-4.0.6. Please use PHP4.0.7 or 4.0.8 and the
> > problem will be solved. This can be obtained from CVS
>
> Sorry, but 4.0.6 is the last version out (there may be some RC of 4.0.7),
but
> how can we get those, and how much can we trust a RC version?
>
> Saludos... :-)
>
> --
> Porqué usar una base de datos relacional cualquiera,
> si podés usar PostgreSQL?
> -----------------------------------------------------------------
> Martín Marqués | mmarques@unl.edu.ar
> Programador, Administrador, DBA | Centro de Telematica
> Universidad Nacional
> del Litoral
> -----------------------------------------------------------------
>
