That looks correct to me :) Maybe as a step 0, if you wish to maximize your use of MetaModel, you can also use JdbcDataContext to populate (with executeUpdate) the H2 or Derby database.
2016-08-30 2:20 GMT-07:00 tesm...@gmail.com <tesm...@gmail.com>: > Dear Kasper, > > Tying to understanding the flow for H2 or Derby. I'll do the following > steps in the listed order: > > 1) Load data from a data source to H2/Derby for temporarily storing it in > the memory > 2) Use H2/Derby as data source for Apache MetaModel > 3) Connect to H2/Derby data via jbdcDataContect > 4) Query data using Apache MetaMoodel > > Is the above sequence correct or am I missing any step? > > > > Regards, > > > On Wed, Aug 24, 2016 at 8:42 PM, Kasper Sørensen < > i.am.kasper.soren...@gmail.com> wrote: > >> Do you want to offer the users to run any type of query (as in - a >> MetaModel Query) or is it specific things like "lookup by some attribute". >> In the first case, you could put it into e.g. a PojoDataContext and just >> serve that as a in-memory datastore. Or you could use something like H2 or >> Derby and offer that via a JdbcDataContext. In the latter case I would >> suggest simply to load it into a HashMap or something like that. >> >> 2016-08-24 11:15 GMT-07:00 tesm...@gmail.com <tesm...@gmail.com>: >> >>> Hi, >>> >>> New to the list and beginner with Apache Metamodel. >>> >>> I need to load data from multiple data sources using Apache Metamodel. >>> The application will allow user to query the the data loaded from the >>> sources. >>> >>> What is the best option to retain the loaded data in memory while user >>> is processing queries on the data ( We don't want to re-load the data over >>> and over again)? >>> >>> >>> Regards, >>> >> >> >
