Re: Re: pg_execute error

Yasuo Ohgaki wrote: > @ 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. the problem is a limitation in pgsql and hiding this fact imho causes more problems than it solves, especially since pgsql will eventually solve this limitation (i hear 8.2 will solve this). another solution that does of course add a fixed amount of overhead is to simply prepare the statement again before you enter the loop. you will then only have to supress a single call to pg_prepare(). regards, Lukas