When C3P0 attempts to create a new connection pool, it first tries to set the isolation level for each transaction through the connection provided by the JDBC driver. At this point, when the method getTransactionIsolation() is called on the Connection, the Ignite driver throws the SQLFeatureNotSupportedException, as it should.
Thanks for opening the ticket! In the meantime, maybe I'll just see if we can substitute our queries with the Ignite API On Wed, Nov 9, 2016 at 6:42 PM, Denis Magda <dma...@gridgain.com> wrote: > There is a ticket to introduce the transactional support for the JDBC > driver. > https://issues.apache.org/jira/browse/IGNITE-4191 > > Hope this will be implemented in the beginning of the next year. > > — > Denis > > On Nov 9, 2016, at 2:01 PM, vkulichenko <valentin.kuliche...@gmail.com> > wrote: > > Transactions are not supported because updates are not supported. However, > I'm not sure I understand why transactions are required by C3PO in > read-only > scenarios. Do you have any idea how it tries to use transactions in this > case? > > -Val > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Ignite-JDBC-Driver-JDBC-Connection- > Pool-tp8846p8849.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > > >
