| From: | Ragnar Hafstað <gnari(at)simnet(dot)is> |
|---|---|
| To: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
| Cc: | Alban Hertroys <alban(at)magproductions(dot)nl>, John DeSoi <desoi(at)pgedit(dot)com>, Rick Schumeyer <rschumeyer(at)ieee(dot)org>, 'PgSql General' <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: postgres session termination |
| Date: | 2005-01-31 22:08:45 |
| Message-ID: | 1107209325.27081.24.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 2005-01-31 at 15:38 -0600, Scott Marlowe wrote:
> On Mon, 2005-01-31 at 09:28, Alban Hertroys wrote:
> > John DeSoi wrote:
> > > I think there are much better ways to do this. If the result set is
> > > large, the user could be waiting a very long time. Two possibilities are
> > > (1) use a cursor or (2) use limit and offset in your select statement
> > > grab only the rows you need to display.
> >
> > Someone correct me if I'm wrong, but I don't think PHP supports cursors
> > (Maybe PHP 5?).
> >
> > Otherwise, that would have been a neat solution indeed.
>
> PHP supports postgresql cursors, and has since php was able to connect
> to postgresql.
well, my impression was that the OP wanted to divide result sets
between web pages, so cursors would not help anyways,as they do
not survive their session.
gnari
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2005-01-31 22:30:01 | Re: postgres session termination |
| Previous Message | Michael Fuhr | 2005-01-31 21:54:27 | Re: how to release a transaction lock on a table? |