| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | "Inoue, Hiroshi" <inoue(at)tpf(dot)co(dot)jp> |
| Cc: | "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | Re: UseServerSidePrepare and data-at-execution |
| Date: | 2013-08-22 06:50:04 |
| Message-ID: | 5215B49C.7000605@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
On 22.08.2013 02:50, Inoue, Hiroshi wrote:
> (2013/08/15 22:43), Heikki Linnakangas wrote:
>> The test case executes a SELECT statement twice, using data-at-execution
>> parameters (ie. SQLParamData and SQLPutData) and array binding together.
>> In that combination, the server logs confirm that the query is executed
>> twice with different parameters, but only the first result is returned
>> to the client.
>>
>> After some debugging, I came up with the attached patch. It clears the
>> curr_param_result flag from the statement object, in SQLParamData, after
>> executing the statement with the current set of parameters.
>
> Oops I overlooked this case.
> Yes the curr_param_result flag must be cleared before excecuting
> the subsequent set of parameters.
Ok then, I committed the patch. Thanks!
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2013-08-22 07:06:05 | Re: UseServerSidePrepare default |
| Previous Message | Inoue, Hiroshi | 2013-08-22 03:54:19 | Re: Removing support for < 7.4 servers |