Frank,
With a lot of things Oracle the real answer is: it depends.
For a simple "select * from <table_name>" even with a where
clause you may simply get the results one row at a time as they are
extracted & deemed appropriate for the result set. But if you've
included a group by or order by clause, or a union/intersect/minus
clause then yes, the database will assemble results before sending them
to the client.
Also Oracle supports cursors which allow you to pop one or more
rows off of the result set at a time. The way Postgresql returns data
all at once is different.
Dick Goulet
Senior Oracle DBA
Oracle Certified DBA
-----Original Message-----
From: pgsql-interfaces-owner@postgresql.org
[mailto:pgsql-interfaces-owner@postgresql.org] On Behalf Of Frank van
Vugt
Sent: Thursday, November 10, 2005 3:33 PM
To: Greg Stark
Cc: pgsql-interfaces@postgresql.org
Subject: Re: [INTERFACES] Incremental results from libpq
> > If I'm informed correctly then Oracle and others are generating
> > the complete static result set on the server-side, which will then
> > stay cached until all rows/chunks are fetched.
> That's obviously not true. Try doing "select * from huge_table" on
Oracle
> and you'll see records start appearing immediately.
Then it seems I haven't (been informed correctly) :)
Now, given that OCI is offering some kind of asynchronous interface as
well,
how are they handling an error occuring after a partial result-set has
been
retrieved by the client?
--
Best,
Frank.
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to
majordomo@postgresql.orgso that your message can get through to the mailing list cleanly