| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | markw(at)mohawksoft(dot)com |
| Cc: | 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 11:58:22 |
| Message-ID: | 20031001115822.GR3749@ns.snowman.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
* markw(at)mohawksoft(dot)com (markw(at)mohawksoft(dot)com) wrote:
> > * Steve Lutz (slutz(at)alacritude(dot)com) wrote:
> >> Yes, can you please be more specific, what problems have you had with
> >> it? We are in the process of moving from Oracle on Sun to Postgres on
> >> Linux with front end windows machines. What problems have you had with
> >> the Postgres ODBC drivers on Windows?
> >
> > Try opening a big table.
>
> 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?
> 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.
> 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.
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Mascari | 2003-10-01 12:39:31 | Re: FUD!! ODBC will not be supported by Microsoft in the future |
| Previous Message | markw | 2003-10-01 11:53:13 | Re: FUD!! ODBC will not be supported by Microsoft in the future |