The system I'm working on uses CMP entity beans on a WebLogic platform. Most access is controlled through the use of EJB Select/Finder methods.
Technically, this architecture performs correctly.
However, to increase performance, I'm looking for more control over how often Weblogic flushes data to the database.
During a managed transaction, various inserts and updates will be performed. In order for EJB-QL statements to run correctly against any uncommited data, the changes must be flushed to the database prior to running the EJB-QL statement.
Is it possible for CocoBase to query against an in-memory database (that contains un-committed data)? Ideally I'd like to pre-query the data that may be affected, perform all changes in memory, and then flush the data at the end of the transaction one time.
|