Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:22602 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 75759 invoked by uid 1010); 27 Mar 2006 21:11:46 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 75742 invoked from network); 27 Mar 2006 21:11:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Mar 2006 21:11:45 -0000 X-Host-Fingerprint: 64.233.166.177 pproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.166.177:63905] helo=pproxy.gmail.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 7E/25-37235-11558244 for ; Mon, 27 Mar 2006 16:11:45 -0500 Received: by pproxy.gmail.com with SMTP id e30so1495466pya for ; Mon, 27 Mar 2006 13:11:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=boz+W9uIS/8Sxaq94DCQv7/dfIgj2mDu3bJiNiUhqI0Dyyd9DXg6aIu08tSKdKlBNXZXS6QFfL+3AMh5g4SpDDTLLEpY/12SWiUMTH/H1pJFsmFHnPQWH/OggIqDTTlpV5RoEQLFCRUJvk7HqCrMuNydirPFnrKB7VXtDNSJzug= Received: by 10.35.97.17 with SMTP id z17mr1275929pyl; Mon, 27 Mar 2006 13:11:31 -0800 (PST) Received: by 10.35.41.17 with HTTP; Mon, 27 Mar 2006 13:11:31 -0800 (PST) Message-ID: <4e89b4260603271311m50dcbdbbw8b29b0ddf712baf6@mail.gmail.com> Date: Mon, 27 Mar 2006 16:11:31 -0500 To: "Yasuo Ohgaki" Cc: "Lukas Smith" , internals@lists.php.net In-Reply-To: <442816CF.6040305@ohgaki.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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> Subject: Re: [PHP-DEV] Re: pg_execute error From: kingwez@gmail.com ("Wez Furlong") 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 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 prepare= d > > 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 > >