| From: | "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp> |
|---|---|
| To: | "Vilches, Alejandro" <alejandro(dot)vilches(at)intel(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | Re: Problem calling a function from ODBC application |
| Date: | 2017-02-07 11:54:54 |
| Message-ID: | 5d8022f4-9984-2991-e050-7cf82f7c15e1@dream.email.ne.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Hi Alejandro,
On 2017/02/07 9:24, Vilches, Alejandro wrote:
> Hi Hiroshi,
>
> Thanks for your suggestion! That actually worked! It works two ways: "?::timestamp" or "cast(? as timestamp)".
>
> After running further tests, I'm seeing the issue occurs when the function has a parameter of type timestamp. Furthermore, it throws off other parameters after that (e.g. the varchar parameters show up as unknown in the error message). Anyway, I thought I would just mention that in case it helps anything.
>
> I wish there was a way to specify the timestamp type better when binding the parameter in ODBC (or that PostgreSQL wouldn't get confused between timestamp with or without time zone) so that I didn't need to cast it on top of that (as this seems a bit redundant).
I'd like to improve the behavior in the next release.
regards,
Hiroshi Inoue
>
> Anyway, thanks so much for your help, I really appreciate it!
>
> Alejandro
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2017-02-07 15:52:26 | Re: [HY000] no error information; Error while preparing parameters |
| Previous Message | Vilches, Alejandro | 2017-02-07 00:24:46 | Re: Problem calling a function from ODBC application |