It worth noting that users should be cautious with SQL transactions. As fair SQL transactions are supported only for TRANSACTIONAL_SNAPSHOT mode which are still kind of experimental feature [1].
[1] https://apacheignite.readme.io/docs/multiversion-concurrency-control пт, 6 дек. 2019 г. в 15:12, Ilya Kasnacheev <ilya.kasnach...@gmail.com>: > > Hello! > > As we have discussed privately, ODBC is actually the C++ thin SQL client, and > it supports transactions since 2.7. > > C++ code should look forward to using ODBC to communicate with Ignite. > > Regards, > -- > Ilya Kasnacheev > > > пн, 2 дек. 2019 г. в 16:26, Igor Sapego <isap...@apache.org>: >> >> Ivan, >> >> You are right. Though now we have transactions support in thin client >> protocol, >> It is only now implemented for Java. Also, C++ thin client yet to support >> SQL. >> >> Best Regards, >> Igor >> >> >> On Sat, Nov 30, 2019 at 9:35 AM Ivan Pavlukhin <vololo...@gmail.com> wrote: >>> >>> Igor, >>> >>> Could you please elaborate whether C++ thin client is going to have >>> transactions support in 2.8? AFAIR, it was implemented only for Java >>> thin client. >>> >>> пт, 29 нояб. 2019 г. в 18:29, Stephen Darlington >>> <stephen.darling...@gridgain.com>: >>> >>> > >>> > The ticket says “Fix version: 2.8” so I would assume it would be >>> > available then. Currently planned for late January. >>> > >>> > > On 29 Nov 2019, at 13:58, dkurzaj <dori...@hotmail.fr> wrote: >>> > > >>> > > Hello, >>> > > >>> > > Since this improvement : >>> > > https://issues.apache.org/jira/browse/IGNITE-9410 >>> > > is resolved, I'd assume that it is now possible to do SQL transactions >>> > > using >>> > > the C++ thin client, though I'm not sure it is yet since I did not find >>> > > documentation about that. Would someone happen to know more about this >>> > > subject? >>> > > >>> > > Thank you! >>> > > >>> > > Dorian >>> > > >>> > > >>> > > >>> > > -- >>> > > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >>> > >>> > >>> >>> >>> -- >>> Best regards, >>> Ivan Pavlukhin -- Best regards, Ivan Pavlukhin
