About class

61-70 of 200Refresh
Manual
30

JPA Lifecycle Events

methods are methods that are defined within an entity class. For example, the following entity class defines all the supported callback methods with empty implementations: @Entity public static class ... class may include callback methods for any subset or combination of lifecycle events
Manual
29

Schema Update

The configuration element supports renaming packages, classes and fields in ObjectDB ... is required when persistable classes are renamed or moved to another package. Running the application with persistable classes that have been renamed or moved in the IDE, with no matching schema configuration
Manual
28

JPA Entity Fields

Fields of persistable user defined classes (entity classes, embeddable classes and mapped ... and inverse fields) can be used in both entity classes and embeddable classes. However, the last two groups (primary key and version fields) can only be used in entity classes. Primary key fields
Manual
26

SELECT clause (JPQL / Criteria API)

query = em.createQuery("SELECT c FROM Country c", Country.class); List query = em.createQuery( "SELECT c.name FROM Country AS c", String.class); Listclass); List results = query.getResultList(); for (Object[] result : results
Manual
26

JPA Primary Key

and its primary key. Primary key values are unique per entity class. Instances of different entity classes, however, may share the same primary key value. Only entity objects have primary keys. Instances ... key field: @Entity public class Project { @Id @GeneratedValue long id; // still set
Manual
25

JPA Metamodel API

details on managed classes and persistent fields and properties, similarly to the ability that Java ... to retrieve sets of types: // Get all the managed classes: // (entity classes, embeddable classes, mapped super classes) Set allManagedTypes = metamodel.getManagedTypes
Manual
22

Shared (L2) Entity Cache

. Per persistence unit in the persistence.xml file. Per entity class - using annotations. ObjectDB ... : NONE - cache is disabled. ENABLE_SELECTIVE - cache is disabled except for selected entity classes (see below). DISABLE_SELECTIVE - cache is enabled except for selected entity classes
Issue
21

Schema-Update: Deactivation of automatic entity class removing and introduction of a new class remove in the schema config

works correctly we add ALL entity classes to this product. Because we will prevent a data loss of entites which are not found in the class path. With this background it would be very helpful for us if we could ignore in the ProfileMigration the classes we had not changed. And we were able
Manual
20

FROM clause (JPQL / Criteria API)

identification variables that iterate over all the database objects of a specific entity class hierarchy (i.e. an entity class and all its descendant entity classes). Identification variables are always polymorphic. JPQL does not provide a way to exclude descendant classes from iteration
Manual
20

Paths and Types in JPQL and Criteria API

Instances of user defined persistable classes (entity classes, mapped super classes and embeddable classes) are represented in JPQL by the following types of expressions: Variables - FROM identification variables and SELECT result variables. Parameters - when instances of these classes are assigned