So there are no settings for PG to can give me this same (fast) capability
just by issuing a SQL statement thru the ODBC driver?
The reason I can't go the route of a DECLARE CURSOR is because my
application runs on multiple databases, so I have stay clear of certain
routines that may are may not b
On Tue, Aug 26, 2003 at 02:18:23AM -0700, Bupp Phillips wrote:
> It there a way to get server side cursors with Postgresql like SQLServer has
> or is this a limitation that it has?
http://www.postgresql.org/docs/7.3/static/sql-declare.html
http://www.postgresql.org/docs/7.3/static/sql-fetch.html
Is this something that can be done thru a SQL statement, or are you saying
that I need to develop logic to handle this because the database won't hold
the resultset on the server, but instead sends it all to the client?
It there a way to get server side cursors with Postgresql like SQLServer has
o
Bupp Phillips <[EMAIL PROTECTED]> wrote:
> I'm very new to Postgresql, so don't beat me up to bad if you see a
> problem, just inform me what I've done wrong.
>
> I'm use Postgresql 7.2 (PeerDirect's Windows port) on Win2000 384MB
> RAM 10GB of Free space 800 Mhz, using the ODBC driver 7.03.01.00.
On Mon, 25 Aug 2003, Bupp Phillips wrote:
>
> I have a table that has 103,000 records in it (record size is about 953
> bytes) and when I do a select all (select * from ) it takes a
> whopping 30 secs for the data to return!!
>
> SQLServer on the other hand takes 6 secs, but you can also use what
I'm very new to Postgresql, so don't beat me up to bad if you see a problem,
just inform me what I've done wrong.
I'm use Postgresql 7.2 (PeerDirect's Windows port) on Win2000 384MB RAM 10GB
of Free space 800 Mhz, using the ODBC driver 7.03.01.00.
I have a table that has 103,000 records in it (re