[
https://issues.apache.org/jira/browse/IGNITE-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410532#comment-15410532
]
Alexander Paschenko edited comment on IGNITE-2294 at 8/6/16 7:53 AM:
---------------------------------------------------------------------
1. You're not quite right. {{addBatch}} method of *{{PreparedStatement}}* (not
{{Statement}}!) does not assign params by itself (and does not take any args at
all), but rather tells driver that a new row has to be added to the batch, and
for it the current set of values is copied. You set params by calling series
of, say, {{setInt(column, value)}} (or whatever the type of param is), then
call {{addBatch}}, and so forth, for each of the rows.
2. Could you please elaborate on difference in semantics?
We could of course turn data streamer on by setting connection string param,
but still there's the question: how and when do we flush then? By forcing the
user to set auto flush timeout? (Sounds like an option to me.) I don't think
that it would be a good idea to introduce our "own" SQL statements for data
streamer flush, and can't come up with how we could let the driver and cache
know about the flush otherwise.
was (Author: al.psc):
1. You're not quite right. {{addBatch}} does not assign params by itself (and
does not take any args at all), but rather tells driver that a new row has to
be added to the batch, and for it the current set of values is copied. You set
params by calling series of, say, {{setInt(column, value)}} (or whatever the
type of param is), then call {{addBatch}}, and so forth, for each of the rows.
2. Could you please elaborate on difference in semantics?
We could of course turn data streamer on by setting connection string param,
but still there's the question: how and when do we flush then? By forcing the
user to set auto flush timeout? (Sounds like an option to me.) I don't think
that it would be a good idea to introduce our "own" SQL statements for data
streamer flush, and can't come up with how we could let the driver and cache
know about the flush otherwise.
> Implement SQL DML (insert, update, delete) clauses.
> ---------------------------------------------------
>
> Key: IGNITE-2294
> URL: https://issues.apache.org/jira/browse/IGNITE-2294
> Project: Ignite
> Issue Type: Wish
> Reporter: Sergi Vladykin
> Assignee: Alexander Paschenko
> Fix For: 1.7
>
>
> We need to add parsing for all the listed SQL commands and translate them
> into respective cache operations (putIfAbstent, put, remove).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
