Re: [BUGS] BUG #6534: Passing numeric Bind variables to ODBC driver convers to "Double precision"

Does it happen only for function call or otherwise for Insert statement also? What is your function declaration. How have you verified that in postgres it is double precision. -Original Message- From: Barry Bell [mailto:barry_b...@harte-hanks.com] Sent: Tuesday, April 10, 2012 6:00 PM To:

Re: [BUGS] BUG #6534: Passing numeric Bind variables to ODBC driver convers to "Double precision"

Yes, this is happening when variables are passed to a function The call below does work: Nvar Select * from mytable where id=?nvar Select function call below will work if they function is defined as "Double precision" (that and the error I am getting from Postgres says it is be passed "Double

[BUGS] BUG #6581: pg_dumpall --no-tablespaces option still sets default tablespace

The following bug has been logged on the website: Bug reference: 6581 Logged by: Keith Fiske Email address: ke...@omniti.com PostgreSQL version: 9.1.3 Operating system: Any Description: Using the --no-tablespaces option for pg_dumpall correctly stops tablespace creati

Re: [BUGS] BUG #6581: pg_dumpall --no-tablespaces option still sets default tablespace

ke...@omniti.com writes: > Using the --no-tablespaces option for pg_dumpall correctly stops tablespace > creation and each individual object from having its tablespace set. But if > the original database had its default tablespace changed, this is still > added at the beginning of the dump file: >

Re: [BUGS] BUG #6581: pg_dumpall --no-tablespaces option still sets default tablespace

On Wed, Apr 11, 2012 at 2:21 PM, Tom Lane wrote: > ke...@omniti.com writes: >> Using the --no-tablespaces option for pg_dumpall correctly stops tablespace >> creation and each individual object from having its tablespace set. But if >> the original database had its default tablespace changed, this

[BUGS] ERROR: operator does not exist: integer = integer[]

I have the following select * from employee AS e where (e.id) IN (ARRAY[3,1]); I have the following mistake ERROR: operator does not exist: integer = integer[] LINE 3: where (e.id) IN (ARRAY[3,1]); ^ HINT: No operator matches the given name and argument type(s). You

Re: [BUGS] ERROR: operator does not exist: integer = integer[]

On Thu, Apr 12, 2012 at 2:47 AM, cesar_cast wrote: > I have the following > > select * > from employee AS e > where (e.id) IN (ARRAY[3,1]); > Use: SELECT * FROM employee AS e WHERE e.id = ANY(ARRAY[3,1]); -- Thanks & Regards, Ashesh Vashi EnterpriseDB INDIA: Enterprise PostgreSQL Company

Re: [BUGS] BUG #6534: Passing numeric Bind variables to ODBC driver convers to "Double precision"

>> Is there an ODBC setting for incoming numeric bind variables? I don't think there is any such kind of setting, atleast I am not aware. I am guessing mostly it’s the Postgres behavior or some problem in the way the application is using ODBC. >> Select function call below will work if they fu