Re: Passing numeric Bind variables to ODBC driver convers to "Double precision" - Mailing list pgsql-odbc

From Barry Bell
Subject Re: Passing numeric Bind variables to ODBC driver convers to "Double precision"
Date
Msg-id 542B943ED5D72E408BF9CBBD61ABC94D52D11168@VA3DIAXVSC31.RED001.local
Whole thread Raw
In response to Re: Passing numeric Bind variables to ODBC driver convers to "Double precision"  (Hiroshi Inoue <inoue@tpf.co.jp>)
Responses Re: Passing numeric Bind variables to ODBC driver convers to "Double precision"  (Hiroshi Inoue <inoue@tpf.co.jp>)
List pgsql-odbc
Note: The UseServerSidePrepare=1; only works with the PostgresSQL 9.01 driver (It will not work with the 9.00 driver)

Setting TextAsLongVarchar=0 has no effect on the blanks("") comes back as longvarchar.

UnknownsAsLongVarchar=0 or UnknownsAsLongVarchar=1 has no effect on this either.


Thanks
Barry Bell, IT Department 
Office: 954-429-3771 x267 Fax: 954-281-1464 email Barry_Bell@harte-hanks.com


-----Original Message-----
From: Hiroshi Inoue [mailto:inoue@tpf.co.jp] 
Sent: Friday, April 13, 2012 9:27 AM
To: Barry Bell
Cc: pgsql-odbc@postgresql.org
Subject: Re: [ODBC] Passing numeric Bind variables to ODBC driver convers to "Double precision"

(2012/04/13 2:12), Barry Bell wrote:
> Thanks, "UseServerSidePrepare=1;  does appear to fix this. (working for both numeric and integer)
>
> Next issue,
> When calling a function in postgres, the postgres is returning a blank string ('').
> This is showing as a blank longvarchar(memo,clob) instead of a varchar.
>
> Any ideas?

Please try to turn off the Text as LongVarChar option.

regards,
Hiroshi Inoue


pgsql-odbc by date:

Previous
From: Richard Broersma
Date:
Subject: Re: UPDATE table via ODBC fails.
Next
From: Hiroshi Inoue
Date:
Subject: Re: Passing numeric Bind variables to ODBC driver convers to "Double precision"