Re: Problem with psqlODBC and "call" (of Stored Procedures) - Mailing list pgsql-odbc

From Craig Ringer
Subject Re: Problem with psqlODBC and "call" (of Stored Procedures)
Date
Msg-id 4ADBB127.6020008@postnewspapers.com.au
Whole thread Raw
In response to Problem with psqlODBC and "call" (of Stored Procedures)  (Brigitte und Wolfgang Pasche <pasche.wolfgang@kabelmail.de>)
List pgsql-odbc
Brigitte und Wolfgang Pasche wrote:

> In this case, since PostgreSQL don't
> know a call statement, the ODBC driver correctly transform it into a
> SELECT statement. Unfortunately, the procedure parameter (datatype date)
> in the escaped form is transformed removing only the curly braces and
> leaving the rest untouched instead of transforming it (in a second
> step??) to the correct form. This of course leads to nonsense and
> results in an error message.
>
> My personal impression is, that this is a bug in the ODBC driver

Yep, sounds like an ODBC driver bug for sure.

It might even be worth grabbing the ODBC driver sources to see if you
can spot the issue.

As it happens, the statement could be transformed correctly by
substituting 'DATE' for 'd'.

--
Craig Ringer

pgsql-odbc by date:

Previous
From: kishoramballi
Date:
Subject: Postgres inserts null value for parameterized statement
Next
From: Hiroshi Inoue
Date:
Subject: Re: Problem with psqlODBC and "call" (of Stored Procedures)