Skip site navigation (1) Skip section navigation (2)

Re: [INTERFACES] NEW ODBC DRIVER

From: Byron Nikolaidis <byronn(at)insightdist(dot)com>
To: Chris Osborn <fozztexx(at)talia(dot)hq(dot)vxn(dot)com>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: [INTERFACES] NEW ODBC DRIVER
Date: 1998-05-10 00:12:21
Message-ID: 3554F0E4.AB657CA1@insightdist.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-interfaces
Access insists on using order by clauses like that, even though the
driver returns information saying it can't support it!

Postgres simply can't handle order by clauses without the fields also
being in the target.

The error you see is a legitimate error coming from the backend.

When the backend can handle those kinds of order by clauses, the error
will stop happening.

Byron


Chris Osborn wrote:

> I just downloaded it, and I cannot get any queries that have an
> "ORDER BY" in them to work. Access '97 keeps returning an ODBC call
> failed error, and gives me the message:
>
>    ERROR: The field being ordered must appear in the target list (#1)
>
> If I cut and paste the SQL code directly into a psql session, it
> runs just fine.
>
> ---
> Chris Osborn, Network Administrator      T3West/WebCow!
> 707 255 9330 x225 - Voice                1804 Soscol Ave, #203
> 707 224 9916      - Fax                  Napa, CA 94559
> <fozztexx(at)t3west(dot)com>                   <http://t3west.com/>




In response to

Responses

pgsql-hackers by date

Next:From: Thomas G. LockhartDate: 1998-05-10 00:14:11
Subject: Automatic type conversion
Previous:From: Woohyun,TakDate: 1998-05-09 06:22:46
Subject: Help me!!! Pleass

pgsql-interfaces by date

Next:From: Byron NikolaidisDate: 1998-05-10 00:15:37
Subject: Re: [INTERFACES] NEW ODBC DRIVER
Previous:From: Anil AmarakoonDate: 1998-05-09 04:57:06
Subject: Re: [INTERFACES] jdbc can't getResult of "select nextval (seq_name)"

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group