| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | Brigitte und Wolfgang Pasche <pasche(dot)wolfgang(at)kabelmail(dot)de> |
| Cc: | pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: Problem with psqlODBC and "call" (of Stored Procedures) |
| Date: | 2009-10-19 00:21:59 |
| Message-ID: | 4ADBB127.6020008@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2009-10-19 03:37:28 | Re: Problem with psqlODBC and "call" (of Stored Procedures) |
| Previous Message | kishoramballi | 2009-10-14 18:31:35 | Postgres inserts null value for parameterized statement |