 9 | Welcome to ObjectDB for Java/JPA Developer's Guide. Here you can learn how to develop database applications using ObjectDB and JPA (Java Persistence API). The main purpose of this guide is to make you productive with ObjectDB and JPA in a short time. Guide Structure This manual is divided into |
9 | 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 |
9 | the database file in ObjectDB Explorer: This is the end of the tutorial. Learn more about ObjectDB and JPA by reading the Manual. |
9 | to do so but do so at their own discretion. Some subscriptions may be manually processed through prior written agreement |
9 | The way a field of a persistable class is managed by JPA can be set by the following annotations: Additional annotations (and enum) are designated for enum fields: Other additional annotations (and enum) are designated for date and calendar fields: Chapter 2 of the ObjectDB manual explains how to use all the above annotations. |
9 | Persistence fields can either be accessed by JPA directly (as fields) or indirectly (as properties and get/set methods). JPA 2 provides an annotation and an enum for setting the access mode: More details are provided in chapter 2 of the ObjectDB manual. |
9 | objects and flat database table rows. Object Relational Mapping (ORM) tools can reduce some manual work |
9 | , this alternative is not covered in this manual. Using Named Queries at Runtime Named queries are represented |
9 | (ORM) tools can reduce some manual work but cannot eliminate the extra processing time, and even add |
9 | order to learn how to use JPA and ObjectDB please read the ObjectDB manual. |
