Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:22601 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 98729 invoked by uid 1010); 27 Mar 2006 16:51:21 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 98713 invoked from network); 27 Mar 2006 16:51:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Mar 2006 16:51:21 -0000 X-Host-Fingerprint: 212.112.227.169 ipx11223.ipxserver.de Linux 2.5 (sometimes 2.4) (4) Received: from ([212.112.227.169:40154] helo=ipx11223.ipxserver.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 98/D6-37235-80818244 for ; Mon, 27 Mar 2006 11:51:21 -0500 Received: from localhost (localhost [127.0.0.1]) by ipx11223.ipxserver.de (Postfix) with ESMTP id 3B843DF0099; Mon, 27 Mar 2006 18:51:11 +0200 (CEST) Received: from ipx11223.ipxserver.de ([127.0.0.1]) by localhost (ipx11223 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03158-07; Mon, 27 Mar 2006 18:51:00 +0200 (CEST) Received: from [127.0.0.1] (i577B5B91.versanet.de [87.123.91.145]) by ipx11223.ipxserver.de (Postfix) with ESMTP id 821B3DF0043; Mon, 27 Mar 2006 18:51:00 +0200 (CEST) Message-ID: <442817F7.1080409@php.net> Date: Mon, 27 Mar 2006 18:51:03 +0200 User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Yasuo Ohgaki Cc: internals@lists.php.net References: <4425040E.60402@ohgaki.net> <44250532.7070509@php.net> <44275330.7050508@ohgaki.net> <44279BCB.1090105@php.net> <44280F96.3090600@ohgaki.net> <44281210.3000103@php.net> <442816CF.6040305@ohgaki.net> In-Reply-To: <442816CF.6040305@ohgaki.net> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: by somedaemon at backendmedia.com Subject: Re: [PHP-DEV] Re: pg_execute error From: lsmith@php.net (Lukas Smith) 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