Re: [INTERFACES] ODBC is slow with M$-Access Report - Mailing list pgsql-hackers

From Jose' Soares Da Silva
Subject Re: [INTERFACES] ODBC is slow with M$-Access Report
Date
Msg-id Pine.LNX.3.96.980603104111.745A-100000@proxy.bazzanese.com
Whole thread Raw
In response to Re: [INTERFACES] ODBC is slow with M$-Access Report  (David Hartwig <daveh@insightdist.com>)
List pgsql-hackers
On Tue, 2 Jun 1998, David Hartwig wrote:

<DELETED>
> > Nikolaidis and David Hartwig of insightdist.com that are doing a
> > really great job with ODBC driver), but with the obvious consequences.
>
>  I am currently working on a solution as time will allow.   Hopefully part of 6.4
> > 2.  As PostgreSQL doesn't allow an "ORDER BY" on columns not
> > included in the target list of the "SELECT", (I know that it is
> > SQL/92 standard, but IMO it's a fool thing), therefore, is not possible
> > to  have the "dynaset "sorted for any field that is different from
> > the key (in our case the useless OIDs).
>
> This fix is in alpha and will be in the 6.4 release.  I do not know when 6.4 is slated
> for release, but I am willing to send you a patch if it is critical for you to proceed.
>
> > 3. The times required to run complex reports (for example those that
> > include LEFT JOINS) is very long (about 15 minutes to retrieve
> > 2850 rows).
> >
> The solution to your first item will resolve this also.
>
This is a great new David, Thank you very much for your work, this allow us
to go on with this important project.
For us, is enough to know that it will be available *maybe* on next release.
                                               Thanks a lot, Jose'


pgsql-hackers by date:

Previous
From: Michael Meskes
Date:
Subject: Re: [HACKERS] mpsql
Next
From: Brett McCormick
Date:
Subject: Re: [HACKERS] keeping track of connections