| From: | "Yonatan Ben-Nes" <yonatan(at)epoch(dot)co(dot)il> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | PDOStatement:closeCursor |
| Date: | 2006-12-17 09:36:04 |
| Message-ID: | 2d0127b80612170136t6538d58fv906dedac7309b56e@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi all,
I know that it's also related to PHP but sadly no one knew anything there so
I try here... :)
At the PHP manual of
PDOStatement::closeCursor<http://il.php.net/manual/en/function.pdostatement-closecursor.php>it's
written that "This method is useful for database drivers that do not
support executing a PDOStatement object when a previously executed
PDOStatement object still has unfetched rows. If your database driver
suffers from this limitation, the problem may manifest itself in an
out-of-sequence error.".
Anyone know if the PostgreSQL driver suffer from this problem or not?
Thanks a lot in advance,
Ben-Nes Yonatan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrus | 2006-12-17 12:04:31 | How non-superuser can restore database containing procedures |
| Previous Message | Steve Castellotti | 2006-12-17 07:14:43 | determining which table to lookup depending on data values |