From: | Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: SQLExecute returns 0 rows with BoolsAsChar=1 |
Date: | 2013-03-26 15:02:53 |
Message-ID: | 5151B89D.8060902@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
(2013/03/25 20:44), Heikki Linnakangas wrote:
> On 24.03.2013 12:07, Hiroshi Inoue wrote:
>> I can reproduce it now when I turn off the *Server side prepare* option
>> or turn on the *Use Declare/Fetch* option.
>
> Ah yeah, UseServerSidePrepare hides it. I'm also seeing the problem
> without UseDeclareFetch, though.
>
>> Attached is a patch to fix the bug.
>
> Thanks. I must admit I don't understand how this works. Also, the 2nd
> test case in attached file now fails. It does a DELETE ... RETURNING,
> binding a parameter array with a VARCHAR(5) column, and fetches the
> results. With the patch, it can't fetch the result sets.
Thanks for the test case.
The attached patch instead of the previous one would fix the problem
but still has a problem when the server side prepare option is turned
on.
regards,
Hiroshi Inoue
Attachment | Content-Type | Size |
---|---|---|
statement.c.patch | text/x-patch | 1020 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2013-03-29 13:51:39 | Re: SQLExecute returns 0 rows with BoolsAsChar=1 |
Previous Message | Heikki Linnakangas | 2013-03-25 11:44:05 | Re: SQLExecute returns 0 rows with BoolsAsChar=1 |