Re: [Solved] Slow performance on Windows .NET and OleDb

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Magnus Hagander" <mha(at)sollentuna(dot)net>
Cc: Antoine <melser(dot)anton(at)gmail(dot)com>, "Dave Dutcher" <dave(at)tridecap(dot)com>, "Greg Quinn" <greg(at)officium(dot)co(dot)za>, pgsql-performance(at)postgresql(dot)org
Subject: Re: [Solved] Slow performance on Windows .NET and OleDb
Date: 2006-04-01 19:23:20
Message-ID: b42b73150604011123u5e179cfeo3eec7db6f8f33ae@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 3/31/06, Magnus Hagander <mha(at)sollentuna(dot)net> wrote:
> > This is a blatant thread steal... but here we go...
> > Do people have any opinions on the pgsql driver?

> I beleive so. I've been using it for a long time with zero problems.
> While I don't use many of the exotic features in it, I doubt most people
> do ;-) Don't get scared by the claim it's in beta - IIRC there's an RC
> out any day now, and it's been stable long before 1.0. But it's always a
> good idea to browse through the list of known bugs and see if one will
> likely hit you...

Up until a few months ago the npgsql driver was missing a few features
that made it easier to work with typed datasets in the IDE...I would
use the odbc driver to create the dataset at design time and work with
it at run time with the npgsql driver.

Lately though, it seems there is no reason not use the npgsql driver.

Merlin

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message chris smith 2006-04-02 00:50:44 Re: Query using SeqScan instead of IndexScan
Previous Message Brendan Duddridge 2006-04-01 17:51:12 Re: Query using SeqScan instead of IndexScan