 12 | ) is automatically enabled without specifying a Java agent. This is the end of the tutorial. Learn more about ObjectDB and JPA by reading the Manual. |
12 | , this alternative is not covered in this manual. Using Named Queries at Runtime Named queries are represented |
12 | (ORM) tools can reduce some manual work but cannot eliminate the extra processing time, and even add |
12 | Queries are represented in JPA by the Query and TypedQuery interfaces: The JPA Query API section (in chapter 4 of the ObjectDB manual) provides detailed explanation of how exactly to use these interfaces to build and run JPQL queries. The TypedQuery interface (or alternatively the older Query |
12 | can be found in the Quick Tour chapter of the ObjectDB Manual. The next (and last) step in this tutorial is running the project. |
5 | . Feedback We would appreciate any comment or suggestion regarding this manual. Please send your comments or questions to support@objectdb.com. |
5 | Chapter 4 of the ObjectDB/JPA manual. int executeUpdate() Execute an update or delete statement ... manual. FlushModeType getFlushMode() Get the flush mode in effect for the query execution. Get the flush |
3 | Method javax.persistence.Query int getFirstResult() The position of the first result the query object was set to retrieve. Returns 0 if setFirstResult was not applied to the query object. Returns: position of the first result Since: JPA 2.0 Learn how to define and use JPA/JPQL queries in Chapter 4 of the ObjectDB/JPA manual. |
3 | javax.persistence Interface Cache Interface used to interact with the second-level cache. If a cache is not in use, the methods of this interface have no effect, except for contains, which returns false. Since: JPA 2.0 Learn how to use Cache in Chapter 3 of the ObjectDB/JPA manual. boolean contains |
3 | Chapter 3 of the ObjectDB/JPA manual. boolean value (Optional) Whether or not the entity should be cached |