Re: PDO proposal: add PDOStatement::nextResult() method to support stored procedures
| From: | Dan Scott | Date: | Sat, 09 Apr 2005 16:07:34 +0000 |
| Subject: | Re: PDO proposal: add PDOStatement::nextResult() method to support stored procedures | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-15933@lists.php.net to get a copy of this message | ||
On Apr 9, 2005 11:48 AM, Christopher Kings-Lynne
<chriskl@familyhealth.com.au> 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