headers
markw | 1 Oct 2003 13:53

Re: FUD!! ODBC will not be supported by Microsoft in the future

> * Steve Lutz (slutz <at> alacritude.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.

On a side not, you will be hard pressed to find a commercial ODBC
application, i.e. Access, that can handle large tables.

For what its worth, I use the PGODBC driver to create an index of tables
with Millions of rows.

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo <at> postgresql.org
Permalink | Reply | 5 comments |
headers
Stephen Frost | 1 Oct 2003 13:58

Re: FUD!! ODBC will not be supported by Microsoft in the future

* markw <at> mohawksoft.com (markw <at> mohawksoft.com) wrote:
> > * Steve Lutz (slutz <at> alacritude.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
(Continue reading)

Permalink | Reply | 4 comments |
headers
Mike Mascari | 1 Oct 2003 14:39

Re: FUD!! ODBC will not be supported by Microsoft in the future

Stephen Frost wrote:

> * markw <at> mohawksoft.com (markw <at> 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
(Continue reading)

Permalink | Reply | 2 comments |
headers
Richard Huxton | 1 Oct 2003 14:41
Favicon

Re: FUD!! ODBC will not be supported by Microsoft in the future

On Wednesday 01 October 2003 12:58, Stephen Frost wrote:
> * markw <at> mohawksoft.com (markw <at> mohawksoft.com) wrote:
>
> 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.

This is probably less to do with ODBC and more with PG's approach to result 
sets. With PG, if you ask for 10 million rows it will pass all of them to the 
client in one go. Other systems tend to act as though you asked for a cursor 
and return rows as you fetch them. In PG, if you want a cursor, you ask for a 
cursor.

--

-- 
  Richard Huxton
  Archonet Ltd

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
Permalink | Reply | 0 comments |
headers
Michael Calabrese | 1 Oct 2003 14:53
Picon
Favicon

Re: FUD!! ODBC will not be supported by Microsoft in the future

Stephen can you please be more specific.  How big of a table? What type 
of problem did you have opening a big table.  I use Postgres in a 
production enivornment with about 2 to 3 million row (for all tables).  
This is big to some and small to others.  I have had no problems 
"opening" tables in psql, php, MSAcess, with a row count well over 
100,000 rows.  If you have had a problem that is reproducible, then you 
should let the list know so the problem can be fixed.

For the others on the list, I have not moved from Oracle to Postgres but 
from Access to Postgres.  Most of the problems with that transition deal 
with name issues (Access allows many things in the naming of tables and 
fields) and Access thinking it is smarter than me when I give it a query 
to run.  (I still use Access as a front end, and am slowly porting it to 
php.)

I hope this helps others on the list,
Michael Calabrese
Bike Friday

Stephen Frost wrote:

>* Steve Lutz (slutz <at> alacritude.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?
>>    
>>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ben Trewern | 1 Oct 2003 15:01
Picon
Favicon

Re: FUD!! ODBC will not be supported by Microsoft in the future

All

I've been using (or trying to use) the pgODBC driver with 'Use 
Declare/Fetch' set to true and all goes well till you try to go to the end 
of a large recordset.  The driver seems to load all the records instead of 
just the last 50 (or whatever).  I'm using Delphi 7, BDE and psqlODBC 
version 7.03.01.08 to connect to Postgres 7.3.1.

Any ideas?  Could this be a BDE problem?  Any one else out there using this 
configuration?

Regards,

Ben

>From: Mike Mascari <mascarm <at> mascari.com>
>To: Stephen Frost <sfrost <at> snowman.net>
>CC: markw <at> mohawksoft.com, slutz <at> alacritude.com,pgsql-odbc <at> postgresql.org
>Subject: Re: [ODBC] FUD!! ODBC will not be supported by Microsoft in the 
>future
>Date: Wed, 01 Oct 2003 08:39:31 -0400
>
>Stephen Frost wrote:
>
> > * markw <at> mohawksoft.com (markw <at> 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
(Continue reading)

Permalink | Reply | 1 comment |
headers
Steve Lutz | 1 Oct 2003 15:02

Re: FUD!! ODBC will not be supported by Microsoft in the future

Hi Again Stephen,

I've also had similar issues with Oracle and SQL Server. I don't use
access as part of the system, but use it to link to tables for quick
data checks, or quick data entry, especially during development. It's
also great for import/export and initial data setup. I think that the
problem may be more with the server and not especially with the ODBC
driver, and possibly a little bit to do with access. I know that access
simplifies things, and it doesn't alway do what I expected (especially
queries with joined linked tables). 

One workaround I've found is that instead of opening the table directly,
create an updatable query that includes the entire source table, (Select
* from source_table) then use that query instead of the linked table
directly. I think that the query will do a cursor, but opening a linked
table doesn't. 

I'm posting this to the list in case other people have had similar
issues.

Steve

-----Original Message-----
From: Stephen Frost [mailto:sfrost <at> snowman.net]
Sent: Wednesday, October 01, 2003 8:18 AM
To: Steve Lutz
Subject: Re: [ODBC] FUD!! ODBC will not be supported by Microsoft in the
future

* Steve Lutz (slutz <at> alacritude.com) wrote:
(Continue reading)

Permalink | Reply | 2 comments |
headers
Stephen Frost | 1 Oct 2003 15:09

Re: FUD!! ODBC will not be supported by Microsoft in the future

* Mike Mascari (mascarm <at> mascari.com) wrote:
> http://gborg.postgresql.org/project/psqlodbc/genpage.php?doc-config

I saw that, and it said it was on by default so I figured it must be
something else.  Apparently it's *not* actually on by default.  I
turned it on and I'll play around with that and see if it helps.

	Stephen
Permalink | Reply | 1 comment |
headers
Jeff Eckermann | 1 Oct 2003 16:18
Picon
Favicon

Re: FUD!! ODBC will not be supported by Microsoft in the future

Client-server brings up a bunch of issues that don't
apply when using local data storage for applications
such as MS Access: server load/performance, network
performance, lack of support for certain application
features etc.  These issues require a higher level of
awareness by the user/developer of what is going on.

Some products are easy to use because they silently
handle things that you would otherwise have to handle
yourself.  MS Access itself is a prime example of
this.  PostgreSQL requires more of the user, because
you have to do more of the driving yourself.  It's the
old control vs. complexity tradeoff.

The silently-manage-things-for-you approach is
attractive, until you find that the behaviour you are
getting is not what you want.  Then it can be hard to
change.

Even people who work a lot with MS Access end up
having to know a lot about how Access does things
behind the scenes, because inevitably they run into
cases where Access just doesn't do what they want.

I am using Access as the example, but this refers just
as much to the Oracle & SQL Server ODBC setups
referred to in earlier posts.

--- Steve Lutz <slutz <at> alacritude.com> wrote:
> Hi Again Stephen,
(Continue reading)

Permalink | Reply | 1 comment |
headers
Nowland, Belinda (London | 1 Oct 2003 16:21
Picon
Favicon

How do I unsubscribe?


thanks

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

               http://archives.postgresql.org
Permalink | Reply | 0 comments |

Gmane