Regardless of whether it's a good idea or not, you should not just go
ahead and commit such a big behaviour change to the stable branch
during the release process.
Please revert your commit.
--Wez.
On 3/27/06, Yasuo Ohgaki <[EMAIL PROTECTED]> wrote:
> Lukas Smith wrote:
> > So why dont you just do @pg_execute() and in your error handler you can do:
> >
> > function ErrorHandler($errno, $errstr, $errfile, $errline)
> > {
> > // ignore silenced function calls
> > if (!error_reporting()) {
> > return;
> > }
> > ..
> >
> > If you want a "beautiful" solution you will have to manage your prepared
> > statements in some persistant layer.
>
> This is one option.
>
> @ operator is ok, but usually @ operator is not recommenned.
> Don't you think so? I try not to use @ as much as possible.
>
> pg_execute() does not have to raise error just like file_exists().
> It may be good idea to raise error when connection is bad, etc.
>
> --
> Yasuo Ohgaki
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
