Re: Compression on ODBC? - Mailing list pgsql-general

From David C. Hartwig Jr
Subject Re: Compression on ODBC?
Date
Msg-id 394635DE.C2718E61@home.com
Whole thread Raw
In response to Compression on ODBC?  ("Mark Alliban" <MarkA@idnltd.com>)
List pgsql-general
Mark Alliban wrote:

> Hi,
>
> I have an application which dials a modem, and connects to Postgres using
> ODBC. When I call the SQLExecDirect function to get the (quite large: 10000
> rows) result set, it takes a long time to execute. The query itself is
> indexed and runs very quickly from psql. I presume the delay is because the
> ODBC is downloading all the rows. Is there any way to either:
>
> 1) Use compression on the recordset to make the call faster?
> 2) Download each row one at a time, when SQLFetch is called?
>
> Also I don't seem to be able to find an ODBC function to return the number
> of records in a results set. Is there one?
>
> TIA,
> Mark.

Its been a while since I have used the ODBC driver, but I believe if you set
the Declare/Fetch driver option you will get a better response time.  This
option uses a cursor to bring in the rows in set.   I believe the default is
to cache 100 rows at a time  - on demand.   Kind of a lazy retrieval thing.
The side effect of using this option is that as long as that  record set is in
use, you must open another separate connection to perform other database
operations.    Hope this helps.


pgsql-general by date:

Previous
From: Thomas Lockhart
Date:
Subject: Re: Compression on ODBC?
Next
From: "David C. Hartwig Jr"
Date:
Subject: Re: Compression on ODBC?