Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id DB26E632933 for ; Wed, 19 Aug 2009 19:36:35 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 95129-06 for ; Wed, 19 Aug 2009 22:36:25 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smtp-gw51.mailanyone.net (smtp-gw51.mailanyone.net [208.70.128.77]) by mail.postgresql.org (Postfix) with ESMTP id F06BE63286E for ; Wed, 19 Aug 2009 19:36:25 -0300 (ADT) Received: from mailanyone.net by smtp-gw51.mailanyone.net with esmtpa (MailAnyone extSMTP andy@networkmail.eu) id 1MdtlU-0003wQ-Pb; Wed, 19 Aug 2009 17:36:24 -0500 Message-ID: <4A8C7E77.4030902@networkmail.eu> Date: Wed, 19 Aug 2009 23:36:39 +0100 From: Andy Shellam User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: Eric Chamberlain CC: "pgsql-php@postgresql.org" Subject: Re: Stored procedures, PDO, and PHP issue References: <4A8C6432.2050500@networkmail.eu> <2AE0AB18-0F9D-4A32-92D3-4D86F176D432@zonarsystems.com> <4A8C6B7D.7020806@networkmail.eu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 200908/16 X-Sequence-Number: 4057 Hi Eric, Ah cool well I guess we all learnt something now then huh!? Cheers for letting us know the solution. Strange that PDO won't let you use the "?" syntax as well as named data types in the query. > > Here is what is in the Apache log: > > [Wed Aug 19 15:07:02 2009] [notice] child pid 31897 exit signal > Segmentation fault (11) > [Wed Aug 19 15:07:03 2009] [notice] child pid 4163 exit signal > Segmentation fault (11) > [Wed Aug 19 15:07:05 2009] [notice] child pid 4122 exit signal > Segmentation fault (11) > [Wed Aug 19 15:07:07 2009] [notice] child pid 4209 exit signal > Segmentation fault (11) Yeah that's PHP crashing (explaining why you only get the blank screen.) If you have the time, maybe report it to the PHP guys (http://bugs.php.net.) I can't see why you cannot use "?::BIGINT" but you can use ":name::BIGINT." As far as we as developers are concerned, the two should be interchangeable (and the documentation certainly suggests that.) At any rate even if you couldn't use that syntax, PHP shouldn't segfault. > > This was after 5 successive hits using the ?::BIGINT, ?::VARCHAR syntax. > Regards, Andy