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

Re: PostgreSQL/ODBC/WinNT

From: David Hartwig <daveh(at)insightdist(dot)com>
To: Jeffrey Lyon <lyonj(at)em-systems(dot)com>
Cc: byronn(at)insightdist(dot)com, pgsql-interfaces <pgsql-interfaces(at)postgreSQL(dot)org>
Subject: Re: PostgreSQL/ODBC/WinNT
Date: 1998-06-15 19:49:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
There is a patch in due for release with 6.4 that removes the restriction
that requires all  ORDER BY columns be present in the  target list.

It does not make sense that a query from the ODBC driver produces an error
in the backend while the same query from the psql does not.  The queries
must be different in some way.   Is this a passthru query on the ODBC side,
or is it a query generated by a query builder.   MS Access for example, will
not necessary show the user the actual query that is rendered to the
backend.   To get the actual queries you may need to examine  the
psqlodbc.log file.

Jeffrey Lyon wrote:

> Guys,
> Thanks for the help, a combination of setting the authentication type to
> ident, telling the ODBC driver to use the 6.2 protocol and some Windows
> registry stuff made the connection work.
> But now I'm having another problem - A simple "SELECT * FROM table ORDER
> BY tableid" on the ODBC connection gives me a "The field being ordered
> by must appear in the target list (#1)" error.  I've tried creating an
> index on the sorted field with no success.  The only way I can run the
> query is unordered.  The query, however, runs perfectly under psql!
> Any suggestions?

pgsql-interfaces by date

Next:From: Byron NikolaidisDate: 1998-06-15 21:38:12
Subject: Re: [HACKERS] User authentification failed
Previous:From: Constantin TeodorescuDate: 1998-06-15 18:14:18
Subject: HOWTO make PgAccess work under Irix - available

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