Oliver Jowett wrote:
> Oliver Jowett wrote:
>
>>Maik Wiege wrote:
>>
>>
>>>I didn't find a solution for this, but there must be, because the pgAdmin III - tool does this. After starting the
queryin the SQL-Dialog it asks wether to retrieve just the first 100 results or all results displaying the corect
amountof found rows. Or is this just not possible with jdbc.
>>
>>
>>I'd point out that this does not require knowing exactly how many rows
>>there are -- only that there are more than 100. You can do the
>>equivalent in JDBC easily by setting fetchsize to 100 or so and calling
>>next() 100 times.. if you haven't hit the end of the resultset by that
>>point, it has more than 100 rows.
>
>
> Oh, sorry, my mistake -- I misread your description. Perhaps they are
> using either COUNT(*) in the same query or MOVE to get the number of rows.
Ok, some digging in pgAdmin's svn web interface seems to indicate that
pgadmin is not actually doing anything special here -- it does the full
query via libpq's PQexec(), retrieving all the tuples (and hence can
count them) but only does the work to construct a user interface
displaying them all after that "lots of rows, retrieve anyway?" dialog
has been answered.
You could check this by looking at pgadmin's memory footprint while
retrieving a big resultset.
-O
