| From: | Alex Pilosov <alex(at)pilosoft(dot)com> |
|---|---|
| To: | "Command Prompt, Inc(dot)" <pgsql-general(at)commandprompt(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Practical Cursors |
| Date: | 2001-09-18 03:01:24 |
| Message-ID: | Pine.BSO.4.10.10109172300040.31711-100000@spider.pilosoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 17 Sep 2001, Command Prompt, Inc. wrote:
> However, using something like PHP will not allow this because HTTP is
> stateless and PostgreSQL will not know from one transaction to the next
> that the results of the connection are related.
>
> Is this truly the case, or is there a way for PostgreSQL to remember the
> connection identifier so that the next time a PHP connection is made with
> the same identifier a transaction can be completed?
Not currently. Cursor right now is a per-backend thing. A lot of changes
are needed to make cursors global. (particularly transaction-awareness)
-alex
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sam Tregar | 2001-09-18 05:44:14 | Re: Practical Cursors |
| Previous Message | Cosmos Tong | 2001-09-17 23:48:11 | Re: Error in compiling PHP with PostgreSQL support |