| From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
| Cc: | "Henshall, Stuart - WCP" <SHenshall(at)westcountrypublications(dot)co(dot)uk>, "'Jean-Michel POURE'" <jm(dot)poure(at)freesurf(dot)fr>, "'pgsql-odbc(at)postgresql(dot)org'" <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | Re: Access '97 {oj ...} Left Join |
| Date: | 2001-04-12 00:33:38 |
| Message-ID: | 3AD4F7E2.8D53D6AB@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
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.
regards,
Hiroshi Inoue
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shawn Bisgrove | 2001-04-12 11:50:39 | iODBC |
| Previous Message | Dave Page | 2001-04-11 18:44:39 | RE: Access '97 {oj ...} Left Join |