From: David Hartwig <daveh@insightdist.com>
To: Taral <taral@mail.utexas.edu>
Cc: pgsql-sql@hub.org
Subject: Re: [SQL] MS Access via ODBC
Date: Mon, 10 Aug 1998 08:00:22 -0400
Message-ID: <35CEE0D5.BB8F0F8B@insightdist.com> (raw)
References: <000001bdc3c6$299f7960$3b291f0a@taral>
This is caused by the MS Jet Engine. It is using a record set strategy to
optimize navigation through potentially large numbers of rows. It is even
more interesting if you use a join condition. The Jet Engine will split the
single join into two (or more) queries. In any case PostgreSQL 6.3.2 cannot
handle an ORDER BY that is not in the projection/target_list. It will be
available in 6.4 In the mean time. I have posted the patch at our web sit
(see: http://insightdist.com/psqlodbc_faq.htm Why does MS Access sometimes
complain about a GROUP BY or ORDER BY not being in the target list?.)
There a two other pit falls. Multi-part keys may exhaust memory in the
backend. And large tables will be slow. This is being addressed for 6.4
Taral wrote:
> I noticed that when trying to get MS Access to do a query of "SELECT * FROM
> table ORDER BY somekey" as its data source for a form, it actually issues
> "SELECT primarykey FROM table ORDER BY somekey", which PostgreSQL rejects
> because "somekey" isn't being selected.
>
> Now, either PostgreSQL has put an (odd) restriction on SQL, or MS Access is
> issuing an invalid SQL query. Which one is it?
>
> Taral
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: daveh@insightdist.com, taral@mail.utexas.edu, pgsql-sql@hub.org
Subject: Re: [SQL] MS Access via ODBC
In-Reply-To: <35CEE0D5.BB8F0F8B@insightdist.com>
References: <000001bdc3c6$299f7960$3b291f0a@taral> <35CEE0D5.BB8F0F8B@insightdist.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox