Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CALOGAow_9fwDvFcCaKK7rmOZCqMBb0a4=XjBrrQPVxQLPHBFRA@mail.gmail.com>
References: 
 <CA+0=VoU7eyM7XCT7KVDk9ypd-HphkPFKL3xDVhVmZ3D1tp5M-g@mail.gmail.com>
 <CALOGAow_9fwDvFcCaKK7rmOZCqMBb0a4=XjBrrQPVxQLPHBFRA@mail.gmail.com>
From: Dmitriy Setrakyan <dsetrakyan@apache.org>
Date: Sat, 30 Apr 2016 09:16:34 -0700
Message-ID: 
 <CA+0=VoURPi=eK2XpWn39h+0N7UKb1k4PLE9SC3GCh636TLf_LA@mail.gmail.com>
Subject: Re: ODBC question
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a11350dba9e1b190531b6177f

--001a11350dba9e1b190531b6177f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sat, Apr 30, 2016 at 6:37 AM, Igor Sapego <isapego@gridgain.com> 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 <dsetrakyan@apache.or=
g
> >
> 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:
> >
> > =E2=80=94-
> > ODBC driver supports rowset binding though currently only fetching of a
> > single row per call is supported, i.e. SQL_ATTR_ROW_ARRAY_SIZE attribut=
e
> > can only be set to 1 right now.
> > =E2=80=94-
> >
> > I am curious as to what =E2=80=9Csingle row per call=E2=80=9D means. Wi=
ll it have
> negative
> > performance implications?
> >
> > D.
> >
> > [1] -
> > http://apache-ignite-users.70518.x6.nabble.com/ODBC-Driver-td4557.html
> >
>

--001a11350dba9e1b190531b6177f--