In ODBC while binding variable using SQLBindParameter(..) API you might be using SQL_DOUBLE or SQL_Numeric or some similar datatype to send the variable, thats why in postgres it is showing as "Double precision"
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Robert Haas Sent: Monday, April 09, 2012 7:31 PM To: [email protected] Cc: [email protected] Subject: Re: [BUGS] BUG #6534: Passing numeric Bind variables to ODBC driver convers to "Double precision" On Thu, Mar 15, 2012 at 3:04 PM, <[email protected]> wrote: > The following bug has been logged on the website: > > Bug reference: 6534 > Logged by: Barry Bell > Email address: [email protected] > PostgreSQL version: 9.1.2 > Operating system: Windows Server 2003 > Description: > > 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. > > Is there a setting on the ODBC driver for incoming vairables? > If not it is a buf. Given the lack of any response here, I suggest reposting this to the pgsql-odbc mailing list. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs -- Sent via pgsql-bugs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
