Skip site navigation (1) Skip section navigation (2)

Re: Passing numeric Bind variables to ODBC driver convers to "Double precision"

From: Barry Bell <Barry_Bell(at)harte-hanks(dot)com>
To: Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>
Cc: "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Passing numeric Bind variables to ODBC driver convers to "Double precision"
Date: 2012-04-12 17:12:19
Message-ID: 542B943ED5D72E408BF9CBBD61ABC94D52D11039@VA3DIAXVSC31.RED001.local (view raw or flat)
Thread:
Lists: pgsql-odbc
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?
 
Thanks
Barry Bell, IT Department 
Office: 954-429-3771 x267 Fax: 954-281-1464 email Barry_Bell(at)harte-hanks(dot)com


-----Original Message-----
From: Hiroshi Inoue [mailto:inoue(at)tpf(dot)co(dot)jp] 
Sent: Thursday, April 12, 2012 9:24 AM
To: Barry Bell
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: [ODBC] Passing numeric Bind variables to ODBC driver convers to "Double precision"

Hi Barry,

(2012/04/09 23:35), Barry Bell wrote:
>
>   Using the lastest of ODBC ANSI driver for windows 32bit ver 9.00.03  Calling from MS VFP 9.0
>
>   public nvar as interger
>   nvar=1
>   running the following sql:
>   "( select function_pkg(?nvar) "
>
>   The bind variable nvar will show in postgres as "Double Precision"  format instead of integer(or numeric)
>
>   Is there a setting on the ODBC driver for incoming vairables?

Are you turning on the Server side prepare option?

regards,
Hiroshi Inoue



In response to

Responses

pgsql-odbc by date

Next:From: Hiroshi InoueDate: 2012-04-13 13:27:05
Subject: Re: Passing numeric Bind variables to ODBC driver convers to "Double precision"
Previous:From: Hiroshi InoueDate: 2012-04-12 13:24:09
Subject: Re: Passing numeric Bind variables to ODBC driver convers to "Double precision"

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group