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


From: Sbragion Denis <infotecn(at)tin(dot)it>
To: Bruce Tong <zztong(at)laxmi(dot)ev(dot)net>
Cc: pgsql-interfaces(at)postgreSQL(dot)org
Subject: Re: [INTERFACES] ODBC Driver
Date: 1998-07-23 06:39:47
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-interfaces

At 13.11 22/07/98 -0400, you wrote:
>Since I hadn't specified any sorting, the "order by" part of the message
>had me confused. I decided to have MS Access show me the SQL it had
>SELECT contact.contact_lname, contact.contact_fname, school.school_name
>FROM contact INNER JOIN school ON contact.contact_school =
>If I remember correctly, INNER JOIN is not yet supported in PostgreSQL,
>which would explain the failure. Sorry to have accused the failure on the
>ODBC driver. While some people's ignorance is bliss, mine thrashes. At
>least now I know what a $#(at)!% INNER JOIN is. ;)

Are you sure this is the cause of the problem? I have been able to perform
INNER JOIN queries (and even outer joins) using Visual Basic 5.0 without
problems even if pgsql doesn't support them. The undelrying Jet database
engine performs the join using simpler queries. Things are pretty slow, but
it works. As far as I know Access should use the same Jet database engine
so things should be the same. 

Any hint here? 


	Dr. Sbragion Denis
	Tel, Fax: +39 39 2324054

In response to


pgsql-interfaces by date

Next:From: Pap TiborDate: 1998-07-23 07:10:09
Subject: JDBC compile error
Previous:From: Byron NikolaidisDate: 1998-07-22 22:42:46
Subject: Re: [INTERFACES] ODBC Driver

pgsql-general by date

Next:From: Maarten BoekholdDate: 1998-07-23 09:01:55
Subject: Re: [GENERAL] Re: [HACKERS] [Fwd: SGVLLUG Oracle and Informix on Linux]
Previous:From: Gene Selkov, Jr.Date: 1998-07-23 05:18:50
Subject: Re: [NOVICE] Re: [GENERAL] Postgres superuser priviledges

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