Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:15933 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91461 invoked by uid 1010); 9 Apr 2005 16:07:38 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 91446 invoked from network); 9 Apr 2005 16:07:38 -0000 Received: from unknown (HELO yahoo.com) (127.0.0.1) by localhost with SMTP; 9 Apr 2005 16:07:38 -0000 X-Host-Fingerprint: 64.233.170.206 rproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.170.206:23419] helo=rproxy.gmail.com) by pb1.pair.com (ecelerity HEAD r(5268)) with SMTP id 73/38-19272-9CDF7524 for ; Sat, 09 Apr 2005 12:07:38 -0400 Received: by rproxy.gmail.com with SMTP id i8so838314rne for ; Sat, 09 Apr 2005 09:07:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=DQaNNvnbOantXC3907TO2TcAHzWi/36KiF2gsxttbehCDXPcAdUGAsru/pDefQo/c/KuVyDS1/732sH7O8kbcqR+7E0B7siOYI6dRFsIUX0RW2LB9ALqnGFEZ+DEM/qvZywAwa70/2eTfCfgatPHlI6Y4H/kQq6ku5EHP98w9Ng= Received: by 10.38.82.21 with SMTP id f21mr2661242rnb; Sat, 09 Apr 2005 09:07:34 -0700 (PDT) Received: by 10.38.65.30 with HTTP; Sat, 9 Apr 2005 09:07:34 -0700 (PDT) Message-ID: Date: Sat, 9 Apr 2005 12:07:34 -0400 Reply-To: Dan Scott To: internals@lists.php.net In-Reply-To: <4257F933.5000301@familyhealth.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <4257F933.5000301@familyhealth.com.au> Subject: Re: [PHP-DEV] PDO proposal: add PDOStatement::nextResult() method to support stored procedures From: denials@gmail.com (Dan Scott) On Apr 9, 2005 11:48 AM, Christopher Kings-Lynne wrote: > > PDO API. Many databases (Apache Derby, DB2, Microsoft SQL Server, > > MySQL 5, and PostgreSQL to a certain extent) support stored procedures > > PostgreSQL to a certain extent, what the...? > > Anyway, why do stored procs need to be treated differently to normal > results? In PostgreSQL they just return results like normal SELECTs... > > Chris > Sorry Chris, no slight against PostgreSQL intended. I guess when I think of "normal" SELECT statements, they return a single result set. But then I'm coming at this from a different set of databases that use CREATE PROCEDURE / CALL to deal with stored procedures, instead of CREATE FUNCTION / SELECT in PostgreSQL's case. I do enjoy the learning curve associated with database abstractions :) I was reading through the PostgreSQL 8.0 docs and saw how functions returned multiple result sets, but didn't see the corresponding client-side API for calling it. Looking deeper at the docs, in pgsql would it be pg_get_result()? BTW, I have now added PDOStatement::nextRowset() documentation to the manual. That's what I get for reading my own (incomplete) documentation. Dan