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

Dave Page wrote:
>
> > -----Original Message-----
> > From: Hiroshi Inoue [mailto:Inoue(at)tpf(dot)co(dot)jp]
> > Sent: 12 April 2001 01:34
> > To: Dave Page
> > Cc: Henshall, Stuart - WCP; 'Jean-Michel POURE';
> > 'pgsql-odbc(at)postgresql(dot)org'
> > Subject: Re: [ODBC] Access '97 {oj ...} Left Join
> >
> >
> > Dave Page wrote:
> >
> > [snip]
> >
> > >
> > > 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.
> >
> > As Henshall pointed out, {oj ...} style syntax seems a
> > ODBC thing and the driver has to map the syntax to
> > DBMS-specific syntax. In fact psqlodbc driver already
> > supports {fn ..}, {dt ..} syntax etc ...
> > In my simple test case, mapping the escape part as-is
> > seems to work.
>
> So the ODBC driver has to support syntax that isn't supported by the
> backend? Hmm, I wasn't aware of that (not that that's unusual :-)).
>

I don't know any DBMS which supports {oj syntax directly.
What I meant is to pass the outer join syntax inside the
{oj .. } as-is to 7.1 PostgreSQL servers.

regards,
Hiroshi Inoue