RE: Access '97 {oj ...} Left Join

> -----Original Message-----
> From: Hiroshi Inoue [mailto:Inoue(at)tpf(dot)co(dot)jp]
> Sent: 11 April 2001 11:42
> To: Henshall, Stuart - WCP
> Cc: 'Jean-Michel POURE'; 'pgsql-odbc(at)postgresql(dot)org'
> Subject: Re: [ODBC] Access '97 {oj ...} Left Join
>
>
> "Henshall, Stuart - WCP" wrote:
> >
> > Oh, that explains it :)
> > As a quick query why does the ODBC driver report them as
> available? As this
> > information is normally used by programs to determine if
> outer joins can be
> > used then surely they should be reported as not working,
> IMHO (I'm guessing
> > that humans read the docs to find a db's features). If this
> where the case
> > then IIRC Access '97 would use its own method of performing
> the join (which
> > is inefficient, but works).
>
> It seems you are right.
> I would change the driver report after the release of
> 7.1. Or hopefully I may be able to implement the {oj
> functionality.

The driver reports that it is OJ capable if it is connected to 7.1 or
higher. When I made the mods to the driver I tested successfully the OJs did
work (this *may* not be the case if the Parse Statements option is
selected).

What doesn't work is the {oj...} style syntax as Stuart reported (which
would have made my life easier when re-coding the SQL Wizard in pgAdmin!),
but this is because PostgreSQL doesn't support it, not the driver. The
following style syntax works a treat via ODBC:

SELECT * FROM foo
LEFT OUTER JOIN bar ON foo.col1 = bar.col1

Regards, Dave.