Hi.
Sorry, very late reaction...
Um, I tried it on ACCESS2000.(08.02.0402)
This is the table which stretched the link.
http://www.skcapi.co.jp/~saito/psqlODBC_TEST/psqlODBC_link1.PNG
Query which you say was imitated.?
http://www.skcapi.co.jp/~saito/psqlODBC_TEST/psqlODBC_link2.PNG
It is tested.
http://www.skcapi.co.jp/~saito/psqlODBC_TEST/psqlODBC_link3.PNG
Your problem is not reproduced....I may have missed something.
If possible, please let me know reproducible environment.
Thanks!
Regards,
Hiroshi Saito
From: "Paul Lambert"
> Tom Lane wrote:
>> Paul Lambert <paul.lambert@autoledgers.com.au> writes:
>>> My initial assumption was that the ODBC driver makes an assumption that
>>> standard_conforming_strings will not be on and adjusts the table names
>>> accordingly.
>>
>> Which ODBC driver version are you using? I'd quite expect a pre-8.2
>> release to not be prepared to deal with this. If the 8.2 version still
>> can't hack it then you've got a legitimate beef ...
>>
>> regards, tom lane
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 5: don't forget to increase your free space map settings
>>
>>
>
> I'm using version 8.2.4 of Postgres, and 8.02.04 of the ODBC driver -
> first had the problem using 8.02.03 ODBC, but upgraded with no change.
>
> P
>
> --
> Paul Lambert
> Database Administrator
> AutoLedgers
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
