Got it, thanks!
On Sat, Apr 30, 2016 at 11:49 AM, Igor Sapego wrote:
> Dmitriy,
>
> Physically user code is an executable and driver is the dynamic library
> which is dynamically loaded by the client. So it's on the same machine and
> even in the same address space.
>
> Best Regards,
> Igor
>
>
Dmitriy,
Physically user code is an executable and driver is the dynamic library
which is dynamically loaded by the client. So it's on the same machine and
even in the same address space.
Best Regards,
Igor
On Sat, Apr 30, 2016 at 7:16 PM, Dmitriy Setrakyan
wrote:
> On Sat, Apr 30, 2016 at 6:3
On Sat, Apr 30, 2016 at 6:37 AM, Igor Sapego wrote:
> The only difference would be that the buffers-filling loop had been moved
> from user
> code to the driver code.
>
>
Thanks Igor. Can you explain this sentence. Where are the user code and the
driver code physically located? Are they on the sa
Dmitriy,
Sure it may have some impact on the performance as user would need
to make more several calls instead of one to fetch several rows. Though
I'm pretty sure that this impact is not going to be very big because of the
current approach.
Currently ODBC Driver retrieves several rows of the res
