From: | Mike Mascari <mascarm(at)mascari(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | markw(at)mohawksoft(dot)com, slutz(at)alacritude(dot)com, pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: FUD!! ODBC will not be supported by Microsoft in the future |
Date: | 2003-10-01 12:39:31 |
Message-ID: | 3F7ACB03.3090200@mascari.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Stephen Frost wrote:
> * markw(at)mohawksoft(dot)com (markw(at)mohawksoft(dot)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(at)mascari(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2003-10-01 12:41:46 | Re: FUD!! ODBC will not be supported by Microsoft in the future |
Previous Message | Stephen Frost | 2003-10-01 11:58:22 | Re: FUD!! ODBC will not be supported by Microsoft in the future |