9.2.2 Functionality provided by Cosminexus JPA Provider

Updating a database using entities

Updates the data in the database using the entities generated from the user applications.

Standard

9.3,

9.4

Defining the mapping information between the database and Java objects

The mapping information between the database and Java objects can be defined with annotations or the O/R mapping file.

Standard

9.5

Entity relationship settings

Sets up the relationship between the database tables by using entities.

Standard

9.6

Entity object cache

This functionality stores the content of the entity object of EntityManager in the memory. When an entity object with the same content is invoked, the entity object in the memory is used.

Extended

9.7

Auto-numbering of primary key

Cosminexus JPA Provider automatically stores the primary key when the entity object is used to insert the data in the database. Even if the user does not specify the primary key, a unique value is stored.

Standard

9.8

Database operations based on the query language

The database can be operated using the query language. With Cosminexus JPA Provider, you can use JPQL or SQL as the query language.

Standard

9.9

Optimistic lock

This is one of the database locking methods. The data is updated after confirming that the data in the database is not being updated by another transaction. An optimistic lock does not lock the data, so a deadlock does not occur.

Standard

9.10

Pessimistic lock in JPQL

This is one of the database locking methods. A dedicated lock is set for the record so that the record is not updated by another transaction. A pessimistic lock is executed only when JPQL is used.

Extended

9.11