Stephen Frost wrote:
> * markw@mohawksoft.com (markw@mohawksoft.com) wrote:
>>That is not a PostgreSQL ODBC issue. There is a setting, I forget the
>>name, that enables a cursor in the query.
>
> It should be on by default then, and I didn't see that option when I was
> looking, can you tell me where it is?
Nothin' like RTFM:
http://gborg.postgresql.org/project/psqlodbc/genpage.php?doc-config
>>On a side not, you will be hard pressed to find a commercial ODBC
>>application, i.e. Access, that can handle large tables.
>
> Uh, Access and Oracle ODBC works just fine on the same table that
> Postgres ODBC grinds the machine to a halt on.
Use Declare/Fetch
>>For what its worth, I use the PGODBC driver to create an index of tables
>>with Millions of rows.
>
> I tried using the postgres ODBC driver to open a table with a couple
> million rows. It ran the client machine out of memory. Same table w/
> the Oracle ODBC driver worked just fine.
Use Declare/Fetch
HTH,
Mike Mascari
mascarm@mascari.com
