Re: Re: pg_execute error

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