Hi Denis, "FOR UPDATE" is not supported at the moment. We will add it's support for transactional case [1]. In non-transactional case it would behave in the same way as normal SELECT.
[1] https://issues.apache.org/jira/browse/IGNITE-6937 On Thu, Oct 19, 2017 at 3:21 AM, Denis Magda <dma...@apache.org> wrote: > Vladimir, Alex P., > > In addition to that please review INSERT, UPDATE, DELETE, MERGE commands > syntax. Are all the parameters (DIRECT, SORTED, etc.) supported by Ignite > and if, yes, then how? I’m doubt that Ignite fully supports H2 syntax: > https://apacheignite-sql.readme.io/v2.1/docs/dml > > — > Denis > > > On Oct 18, 2017, at 2:02 PM, Denis Magda <dma...@apache.org> wrote: > > > > Vladimir, Igniters, > > > > I’m editing the new version of our SELECT page [1] that initially > consisted of the content fully copied from H2. > > > > For instance, there we had the following statement that’s not true for > Ignite: "If FOR UPDATE is specified, the tables are locked for writing. > When using MVCC, only the selected rows are locked as in an UPDATE > statement. In this case, aggregate, GROUP BY, DISTINCTqueries or joins are > not allowed in this case." > > > > How do we process FOR UPDATE parameter in Ignite right now? Please do a > proof-read of the page at all confirming the rest data applies for Ignite. > > > > [1] https://apacheignite-sql.readme.io/v2.1/docs/select > > > > — > > Denis > >
