About entity

81-90 of 200Refresh
Manual
14

JPA Named Queries

is attached to exactly one entity class or mapped superclass - usually to the most relevant entity ... carefully to avoid collision (e.g. by using the unique entity name as a prefix). It makes sense to add the above @NamedQuery to the Country entity class: @Entity @NamedQuery(name="Country.findAll
Manual
14

Auto Generated Values

for entity objects with no primary key fields defined (as explained in the previous section). The same ... @GeneratedValue with the AUTO strategy: @Entity public class EntityWithAutoId1 { @Id @GeneratedValue ... definition is equivalent: @Entity public class EntityWithAutoId2 { @Id @GeneratedValue long
Result
14

ObjectDB Object Database Features [2018-01-27]

entity classes per database file. Up to 2,147,483,648 indices per database file. Up to 9,223,372,036,854,775,808 entity objects per database file. Unlimited database connections (limited only by ... and timeout. Caching L1 entity object cache (per EntityManager). L2 shared entity data cache
Result
14

ObjectDB Object Database Features [2018-10-27]

entity classes per database file. Up to 2,147,483,648 indices per database file. Up to 9,223,372,036,854,775,808 entity objects per database file. Unlimited database connections (limited only by ... and timeout. Caching L1 entity object cache (per EntityManager). L2 shared entity data cache
Result
14

ObjectDB Object Database Features

file size up to 128 TB (= 131,072 GB = 134,217,728 MB). Up to 2,147,483,648 entity classes per database file. Up to 2,147,483,648 indices per database file. Up to 9,223,372,036,854,775,808 entity ... entity object cache (per EntityManager). L2 shared entity data cache (per EntityManagerFactory
Issue
13

Removing of an entity removes also another entity type

Hello, we have following case: All entities must be enhanced, because see Issue #303. ToleranceDefinition and ResolverMapping are entities and have not any relations each other. Before start transaction the ToleranceDefinition entities exist already in the database. The transaction starts
Forum
13

Update Entity references if we change the type of an entity

Hello, we must change (extend) our entity model and therefor we convert the type of some entities ... . But now we introduced as example a new Entity NewKindOfEntityB. And we have a defined logic how we detect the existing EntityB instances they must be converted to the new Entity. With the same ID
Manual
13

JPA Metamodel API

to retrieve sets of types: // Get all the managed classes: // (entity classes, embeddable classes ... (); // Get all the entity classes: Set allEntityTypes = metamodel.getEntities ... instance: // Get a managed type (entity, embeddable or mapped super classes): ManagedType
Issue
13

ODB-FileWriter holds unecessary entity reference after transaction and entity manager are closed

a transaction (including the entity manager) the ODB file writer still holds a reference to entities. Performing similar calls repeatedly hence increases the number of references to entities not longer needed in ... are enhanced. The screenshot indicates using some entity objects (MappingImpl?) in reflection mode. Reflection
Forum
13

Type ... is not defined as an entity (@Entity is missing) (error 302)

.epimss.lab.data.bacti.CultureRqst is not defined as an entity (@Entity is missing) (error 302) at com ... . The class definition looks fine (@PersistenceCapable and @Entity are equivalent - but you may try adding also @Entity). This might be a class loading issue - i.e. PersistenceCapable is available in