Home » Search

About entities

61-70 of 200Refresh
Manual
27

Chapter 3 - Using JPA

Explains how to store, retrieve, update and delete entity objects using JPA.
Manual
27

Schema Update

Explains how to handle JPA/JDO database schema evolution in ObjectDB.
Manual
24

Database Explorer

general information about the database and the bottom sub window displays a list of bookmarked entity objects. The [Schema] window shows the user defined persistable types (entity and embeddable classes ... an element for viewing (an entity class in the [Schema] tabbed window, a bookmark in the [Database
Manual
23

Index Definition

Querying without indexes requires iteration over entity objects in the database one by one. This may take a significant amount of time if many entity objects have to be examined. Using proper indexes ... a standard method for declaring indexes, but JDO does. The following entity definition uses JDO’s
Manual
23

SELECT clause (JPQL / Criteria API)

The ability to retrieve managed entity objects is a major advantage of JPQL. For example ... > results = query.getResultList(); Because the results are managed entity objects they have all the support that JPA provides for managed entity objects, including transparent navigation to other database
Manual
22

CRUD Database Operations with JPA

it to store, retrieve, update and delete database objects. Storing New Entity Objects The following ... a managed entity) by the persist method. The new Point objects are physically stored in the database only when the transaction is committed. The Storing Entities section in chapter 3 discusses
JPA Doc
21

javax.persistence.EntityManager

of entity instances in which for any persistent entity identity there is a unique entity instance. Within the persistence context, the entity instances and their lifecycle are managed. The EntityManager API is used to create and remove persistent entity instances, to find entities by their primary
Forum
18

JPQL query to get entities that does not have a child entity in their child entities

' and not '%Canceled' and not 'Finished'. I have entities for Job and Status with NamedQueries on Job entity and using TomEE for deployment. I am using following queries. FINISHED Jobs between a time
Manual
18

Database Schema Evolution

Modifications to entity classes that do not change their persistent field definitions (their schema ... of an entity class are detected by ObjectDB. New entity objects have to be stored in the new class schema, and old entity objects, which were stored previously in the old class schema
Manual
18

Locking in JPA

, are detected earlier. Optimistic Locking ObjectDB maintains a version number for every entity object. The initial version of a new entity object (when it is stored in the database for the first time) is 1. In every transaction in which an entity object is modified its version number