From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | Ragnar Hafstað <gnari(at)simnet(dot)is> |
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:30:01 |
Message-ID: | 1107210601.16640.154.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 2005-01-31 at 16:08, Ragnar Hafstað wrote:
> 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.
Correct. However, that isn't a limitation in PHP so much as in the
stateless nature of http. But PHP can certainly instantiate and use a
cursor within a single page quite well. Based on what little was in the
message I replied to, that seemed to be the only point made. I'm sure
there was more to the question than what was left in the post I
answered.
From | Date | Subject | |
---|---|---|---|
Next Message | phil campaigne | 2005-02-01 01:53:15 | Error Message |
Previous Message | Ragnar Hafstað | 2005-01-31 22:08:45 | Re: postgres session termination |