Hello, At this moment Ignite support only SELECT* SQL query.
You can use cache API directly for update or insert data. Ignite implements JCache API for access to data, you can look article about this[1]. [1]: http://apacheignite.gridgain.org/docs/jcache On Fri, Aug 26, 2016 at 9:32 AM, san <[email protected]> wrote: > Hi, > > please let know, If JDBC driver is read only then what is the advantage we > are getting. > our scenario is > 1. Populate cache using 'Automatic Persistence' in server. > 2. client will connect to server using JDBC Driver and access the cache > using standard sql queries. > 3. And we are expecting if value is not there in server cache, then server > should fetch from the db (ReadThrough) > 4. as well as update the cache using standard sql query and server shall > update the DB (WriteThrough) > > Advantage we are expecting from this is, we can access ignite server cache > using sql query to do CRUD operation. server shall take care of DB reads > and > writes. > > In this model without change in existing DAO(JDBC code) layer we can > introduce ignite cache in-between application and DB. > > please let know how to solve this issue. is there any way to do it. > > Thanks, > San > > > > > > > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Spring-application-context-resource- > is-not-injected-exception-while-starting-ignite-in-jdbc- > driver-me-tp7299p7332.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Vladislav Pyatkov
