From: Josh Berkus <josh@agliodbs.com>
To: Charles Hauser <chauser@acpub.duke.edu>
Cc: pgsql-sql@postgresql.org
Subject: Re: psql: question
Date: Wed, 08 May 2002 08:23:32 -0700
Message-ID: <web-1453665@davinci.ethosmedia.com> (raw)
In-Reply-To: <a05010401b8feed0b22fc@[152.3.11.193]>
Chuck,
Please cc: one of the Postgres lists when you query me. If you're
getting Q&A support just from me, I'll have to start charging you!
> Trying to work out details of how to let users page back and forth
> among a multi-page list of results.
>
> Problem: I need to know the total number of tuples the query would
> return in order to decide if there are more to display.
>
> 1) Use CURSOR and FETCH
>
> $res= $con->exec(
> "BEGIN WORK;
> DECLARE gene_result CURSOR FOR
> SELECT blah blah
> ORDER BY blah;
> FETCH $offset IN gene_result
> ");
>
> $result->ntuple: returns only the number set by $offset, not TOTAL
> for query.
>
> 2) use LIMIT OFFSET
>
> same problem,
> $result->ntuple: returns only the number set by LIMIT, OFFSET, not
> TOTAL for query.
>
> So there has to be a way to glean both the TOTAL and the SUBSET
> returned?
>
> Searching the postgresql archives obviously can deal with this
> http://archives.postgresql.org/pgsql-sql/
> 'Displaying documents 11-20 of total 243 found.'
Personally, I don't know any way to do this without running the query
twice.
Least inefficient approach: If your interface allows seperating the
SELECT clause from the rest of the query, then run first:
SELECT COUNT(*)
FROM rest-of-query ...
Check that value. If it's 0, then return a "no records found" message
to the user. Otherwise, run the query broken into LIMIT and OFFSET
blocks.
More inefficient approach: if the way the query is being generated
does not allow you to break off the SELECT clause, then you need to
subselect a count:
SELECT COUNT(*) FROM (
SELECT blah FROM rest_of_query) query_count;
This will also give you a count, buut be slightly slower than the
above.
If anybody knows a way to get a count *without* running the query
twice, I'd be glad to hear it!
-Josh Berkus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com, chauser@acpub.duke.edu
Subject: Re: psql: question
In-Reply-To: <web-1453665@davinci.ethosmedia.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox