About object

31-40 of 200Refresh
Manual
15

Running JPA Queries [2011-09-21]

when exactly one result object is expected. Query.getResultList - for general use in any other case ... - for use when exactly one result object is expected. TypedQuery.getResultList - for general use in any ... (with getResultList) The following query retrieves all the Country objects in the database. Because multiple
Manual
15

Running JPA Queries

when exactly one result object is expected. Query.getResultList - for general use in any other case ... - for use when exactly one result object is expected. TypedQuery.getResultList - for general use in any ... (with getResultList) The following query retrieves all the Country objects in the database. Because multiple
JDO Doc
15

javax.jdo.PersistenceManager

. This exception contains a nested JDOOptimisticVerificationException for each object that failed ... 1.0 void deletePersistent(Object pc) Delete the persistent instance from the data store. Delete ... . The data store object will be removed at commit. Unlike makePersistent, which makes the closure
Forum
14

Embedded Object inside another embedded object - is that possible?

I have an entity with an embedded object - it works fine. Now I am trying to add an embedded object inside the first level embedded object - but it does not seem to store it and does not throw either... I was wondering if it was a limitation or not? has anyone tried this before? Thanks
Manual
14

DELETE Queries in JPA/JPQL

As explained in chapter 2, entity objects can be deleted from the database by: Retrieving the entity objects into an EntityManager. Removing these objects from the EntityManager within an active ... an alternative way for deleting entity objects. Unlike SELECT queries, which are used to retrieve data from
Manual
14

JPA Entity Fields

otherwise (e.g. by using the @Transient annotation). Storing an entity object in the database does not store methods or code. Only the persistent state of the entity object, as reflected by its persistent ... . When an entity object is stored in the database every persistent field must contain either null or a value
Manual
14

Defining a JPA Entity Class [2011-02-11]

To be able to store Point objects in the database using JPA we need to define an entity class. A JPA entity class is a POJO (Plain Old Java Object) class, i.e. an ordinary Java class that is marked (annotated) as having the ability to represent objects in the database. Conceptually this is similar
Manual
14

Defining a JPA Entity Class

To be able to store Point objects in the database using JPA we need to define an entity class. A JPA entity class is a POJO (Plain Old Java Object) class, i.e. an ordinary Java class that is marked (annotated) as having the ability to represent objects in the database. Conceptually this is similar
Manual
13

Database Schema Evolution

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 ... that enables transparent use of old entity objects after schema change. When an entity object
Manual
12

UPDATE SET Queries in JPA/JPQL

Existing entity objects can be updated, as explained in chapter 2, by: Retrieving the entity objects into an EntityManager. Updating the relevant entity object fields within an active transaction ... an alternative way for updating entity objects. Unlike SELECT queries, which are used to retrieve data from