From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au> |
Cc: | Chris Bitmead <chris(at)bitmead(dot)com>, "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgresql(dot)org>, pgsql-hackers-oo(at)postgresql(dot)org |
Subject: | Re: [HACKERS-OO] Re: Proposed new libpq API |
Date: | 2000-07-06 12:10:05 |
Message-ID: | Pine.BSF.4.21.0007060909080.33627-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 6 Jul 2000, Chris Bitmead wrote:
> The Hermit Hacker wrote:
>
> > One last comment .. when you say 'random access', are you saying that I
> > can't do a 'PQexec()' to get the results for a SELECT, use a for loop to
> > go through those results, and then start from i=0 to go through that loop
> > again without having to do a new SELECT on it?
>
> Random access means that the whole query result is in memory. If you
> choose to use PQflush then you will no longer be able to go back to 0
> and re-iterate. If you don't use PQflush then you can do what you do now
> which is go back and iterate through. If you use PQflush it means that
> you don't need to do that.
Okay, that sounds cool ... since nobody does the PQflush() during a
for() iteration now (I dont' believe), then old apps are fine, and this
does add a nice level of functionality as far as memory usage is concerned
...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Warner | 2000-07-06 12:17:31 | Re: fcntl(F_SETLK) |
Previous Message | Jan Wieck | 2000-07-06 12:04:14 | Re: 2nd update on TOAST |