114 | Cache configuration of database file pages, query programs, query resultsAre there some possibilities to configure following caches in order to keep cache data for only some important entity types and for the entire life cycle of the EntityManagerFactory. Cache of database file pages. Cache of query programs. Cache of query execution results. btc_es BTC EmbeddedSystems |
114 | Caching/Paging Questions... size of ObjectDB L2 cache or EntityManager context ? Q4: Would paging result sets |
109 | Suggest link to Maven example from Enhancer tool pageSuggest link to Maven example from Enhancer tool page |
109 | Page dividing support in ObjectdbPage dividing support in Objectdb |
22 | Minor typo on web page...On Page: http://www.objectdb.com/java/jpa/entity/types Under: Serializable Types "The internal Java serialization format will be inaccessible to future versions of ObjectDB on other platform." ...should be platforms (plural). rwehrli Rob Wehrli Thanks. Following your report the text was fixed. support Support |
21 | Page cache File handling produced an java.io.IOException: Negative seek offsetPage cache File handling produced an java.io.IOException: Negative seek offset |
21 | Setting and Tuning of JPA Queries. These methods support the implementation of efficient result paging. For example, if each result page should show exactly pageSize results, and pageId represents the result page number (0 for the first page), the following expression retrieves the results for a specified page: List<Country |
3 | Step 4: Add a Servlet Class "guest" attribute. Then the processing is forwarded to the JSP page (which is presented in the next tutorial step). The JSP uses the "guest" attribute to generate the page output. Finally, the database connection (including the transaction if still active) is closed. The next step is adding a JSP page that will produce the guestbook page output. |
3 | Step 4: Add a Servlet Class is forwarded to the JSP page (which is presented in the next tutorial step). The JSP uses the "guest" attribute to generate the page output. Finally, the database connection (including the transaction if still active) is closed. The next step is adding a JSP page that will produce the guestbook page output. |
1 | [ODB1] Chapter 6 - Persistent Objects that is required by JDO, ObjectDB manages another cache containing database pages, in order to improve efficiency. Unlike the object cache, which is always on the client side, the page cache is located ... applications, in which passing string values between web pages is easier than passing real object ID |
