The following table describes the Cosminexus JPA Provider functionality. Select the functionality according to the purpose of a system. For details about the functionality, see the reference location.
Table 1-6 Correspondence between the Cosminexus JPA Provider functionality and the purpose of a system
Functionality name | Purpose of a system | Compliance with Java EE standards | Reference location | |||||
---|---|---|---|---|---|---|---|---|
Reliability | Performance | Operation and maintenance | Expansion | Others | Standard | Expanded | ||
Updating the database using entities | Y | Y | N | N | N | Y | Y | 6.3 |
Entity operations by EntityManager | N | N | N | N | Y | Y | Y | 6.4 |
Defining the mapping information between a database and Java objects | N | N | N | N | Y | Y | Y | 6.5 |
Entity relationship | N | Y | N | N | N | Y | Y | 6.6 |
Functionality for caching entity objects | N | Y | N | N | N | N | Y | 6.7 |
Auto-numbering of primary key values | N | N | N | N | Y | Y | Y | 6.8 |
Database operations based on query language | N | N | Y | N | N | Y | Y | 6.9 |
Optimistic lock | Y | N | N | N | N | Y | Y | 6.10 |
Pessimistic lock in the JPQL | Y | N | N | N | N | N | Y | 6.11 |
Note: The functionality for which Y is specified in both Standard and Expanded columns of the Compliance with Java EE standards column indicates that the Application Server-specific functionality has been expanded to the Java EE standard functionality. The functionality for which Y is specified only in the Expanded column indicates the Application Server-specific functionality.