[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] postgres session termination
From:       Scott Marlowe <smarlowe () g2switchworks ! com>
Date:       2005-01-31 22:30:01
Message-ID: 1107210601.16640.154.camel () state ! g2switchworks ! com
[Download RAW message or body]

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.

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

[prev in list] [next in list] [prev in thread] [next in thread]