Got it, thanks! On Sat, Apr 30, 2016 at 11:49 AM, Igor Sapego <[email protected]> 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 > > On Sat, Apr 30, 2016 at 7:16 PM, Dmitriy Setrakyan <[email protected]> > wrote: > > > On Sat, Apr 30, 2016 at 6:37 AM, Igor Sapego <[email protected]> > 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 same server or is the > user > > code on the client side? > > > > > > > > > On Fri, Apr 29, 2016 at 11:37 PM, Dmitriy Setrakyan < > > [email protected] > > > > > > > wrote: > > > > > > > One of the users recently asked on the user list [1] whether our ODBC > > > > driver supports row-set binding and we gave him the following answer: > > > > > > > > —- > > > > ODBC driver supports rowset binding though currently only fetching > of a > > > > single row per call is supported, i.e. SQL_ATTR_ROW_ARRAY_SIZE > > attribute > > > > can only be set to 1 right now. > > > > —- > > > > > > > > I am curious as to what “single row per call” means. Will it have > > > negative > > > > performance implications? > > > > > > > > D. > > > > > > > > [1] - > > > > > http://apache-ignite-users.70518.x6.nabble.com/ODBC-Driver-td4557.html > > > > > > > > > >
