RE: Access '97 {oj ...} Left Join - Mailing list pgsql-odbc

From Dave Page
Subject RE: Access '97 {oj ...} Left Join
Date
Msg-id 8568FC767B4AD311AC33006097BCD3D61A2AAE@woody.vale-housing.co.uk
Whole thread Raw
In response to Access '97 {oj ...} Left Join  ("Henshall, Stuart - WCP" <SHenshall@westcountrypublications.co.uk>)
Responses Re: Access '97 {oj ...} Left Join  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-odbc

> -----Original Message-----
> From: Hiroshi Inoue [mailto:Inoue@tpf.co.jp]
> Sent: 12 April 2001 01:34
> To: Dave Page
> Cc: Henshall, Stuart - WCP; 'Jean-Michel POURE';
> 'pgsql-odbc@postgresql.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 :-)).


Regards, Dave.

pgsql-odbc by date:

Previous
From: Hiroshi Inoue
Date:
Subject: ODBCINI in iODBC
Next
From: Hiroshi Inoue
Date:
Subject: Re: Access '97 {oj ...} Left Join