ObjectDB Database Search
101-150 of 200 resultsEmbedded 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 EKK | |
Speeding up the creation of Log entity objects related to other objectsSpeeding up the creation of Log entity objects related to other objects | |
JPA Annotations engine manages objects and their database mappings. These annotations configure entity behavior ... specifically for Object -Relational Mapping (ORM) and native SQL execution; ObjectDB ignores these relational annotations: Annotations for mapping objects to relational tables, columns, and foreign keys | |
Chapter 1 - Quick Tour is represented by an object with two int fields, x and y , that store the point's x and y ... Point objects . This chapter contains the following sections: To run the sample program from ... instructions on how to start using JPA in your IDE with the ObjectDB object database. Because ObjectDB | |
About Us ObjectDB Software develops, markets and supports the ObjectDB Object -Oriented Database Management ... persistence solution for Java, based on the Java Persistence API (JPA) and the Java Data Objects (JDO) standards, since ObjectDB is the first object oriented database with built in support of JPA and JDO | |
jakarta.persistence.Query. Since: Jakarta Persistence (JPA) 3.2 int getFirstResult () The position of the first result the query object was set to retrieve. Returns 0 if setFirstResult was not applied to the query object . Returns ... for the query execution. If a flush mode has not been set for the query object , returns the flush mode in | |
jakarta.persistence.TypedQuery result the query object was set to retrieve. Returns 0 if setFirstResult was not applied to the query object . Inherited from Query Returns: position of the first result. Since: Jakarta Persistence (JPA ... for the query object , returns the flush mode in effect for the entity manager. Inherited from Query Returns | |
JPA Entity Fields declared type, including a generic java.lang. Object , as long as the actual runtime value ... is populated with a mapping of employee names to their corresponding Employee objects . Single-value | |
JPA Persistable Types can be stored in the database only as embedded objects , that is, as part of a containing entity. A class ... in the debugger view and when invoking the getClass method on an object of a proxy class. Enum Types | |
Index Definition this full iteration, allowing complex queries over millions of objects to execute quickly ... embeddable classes, because the fields of an embedded object are stored as part of the containing entity | |
JPA Extended API Reference Guide for representing the persistent object model. Use these interfaces to inspect entity structures ... configuration options for common JPA operations. Details the annotations used to define the persistent object | |
JPA Metamodel API The JPA Metamodel API enables you to examine the persistent object model and retrieve details about managed classes, persistent fields, and properties, similar to how Java reflection provides ... -defined persistable types (also known as managed types) in the persistent object model. Three methods | |
JPA ORM Mapping Annotations Jakarta Persistence (JPA) provides a comprehensive set of annotations and enums for mapping object models to relational database schemas. These metadata elements define how entities, attributes ... that a persistent property or field should be persisted as a large object (BLOB or CLOB). Specifies | |
Updating JPA Entities detect changes to managed entities. One detection method is to save a snapshot of each managed object when it is retrieved from the database and then compare that snapshot to the object's current state | |
JPA Criteria API Queries Java objects that represent query elements. A major advantage of the Criteria API is that it enables ... expression. After building the CriteriaQuery , you use it to create a TypedQuery object | |
ORDER BY clause (JPQL / Criteria API) produces objects for examination, and the WHERE clause filters them. Then, the SELECT clause builds ... objects ordered by currency as the primary sort key and by name as the secondary sort key: SELECT c | |
Chapter 4 - JPA Queries (JPQL / Criteria) The Jakarta Persistence Query Language (JPQL) is an object -oriented version of SQL. Users familiar with SQL should find JPQL easy to learn and use. This chapter explains how to use JPQL ... the expressions used to build JPQL and criteria query clauses: ObjectDB also supports the Java Data Objects | |
jakarta.persistence.criteria.Subquery as ( Class type ) Perform a typecast upon the expression, returning a new expression object . Unlike ... a new expression object . Unlike Expression.as , this method does result in a runtime type ... parentJoin ) Create a subquery join object correlated to a join object of the enclosing query | |
jakarta.persistence.criteria.ListJoin a typecast upon the expression, returning a new expression object . Unlike Expression.cast , this method does ... ( Class type ) Cast this expression to the specified type, returning a new expression object . Unlike ... equalTo ( Object value ) Create a predicate to test whether the expression is equal to the argument | |
jakarta.persistence.criteria.Join as ( Class type ) Perform a typecast upon the expression, returning a new expression object . Unlike ... , returning a new expression object . Unlike Expression.as , this method does result in a runtime type ... . Since: Jakarta Persistence (JPA) 3.2 Predicate equalTo ( Object value ) Create a predicate to test | |
jakarta.persistence.PersistenceUnitUtil: IllegalArgumentException - if the given object is not an instance of an entity class belonging to the persistence unit ... cannot be loaded from the database. Since: Jakarta Persistence (JPA) 3.2 Object getIdentifier ( Object ... - entity instance Returns: id of the entity. Throws: IllegalArgumentException - if the object | |
jakarta.persistence.criteria.PluralJoin a typecast upon the expression, returning a new expression object . Unlike Expression.cast , this method ... ( Class type ) Cast this expression to the specified type, returning a new expression object . Unlike ... Predicate equalTo ( Object value ) Create a predicate to test whether the expression is equal | |
jakarta.persistence.criteria.MapJoin ( Class type ) Perform a typecast upon the expression, returning a new expression object . Unlike ... expression object . Unlike Expression.as , this method does result in a runtime type conversion ... ( Object value ) Create a predicate to test whether the expression is equal to the argument | |
jakarta.persistence.criteria.SetJoin upon the expression, returning a new expression object . Unlike Expression.cast , this method does not ... ( Class type ) Cast this expression to the specified type, returning a new expression object . Unlike ... equalTo ( Object value ) Create a predicate to test whether the expression is equal to the argument | |
jakarta.persistence.criteria.CollectionJoin type ) Perform a typecast upon the expression, returning a new expression object . Unlike Expression ... expression object . Unlike Expression.as , this method does result in a runtime type conversion ... Persistence (JPA) 3.2 Predicate equalTo ( Object value ) Create a predicate to test whether the expression | |
jakarta.persistence.criteria.CriteriaQuery is Tuple . Otherwise, the result type is Object . Inherited from AbstractQuery Returns: result type ... on the specification of the type of the criteria query object created as well as the arguments to the multiselect ... (i.e., a criteria query object created by either the createTupleQuery method or by passing a Tuple | |
jakarta.persistence.criteria.From upon the expression, returning a new expression object . Unlike Expression.cast , this method does not cause type ... ) Cast this expression to the specified type, returning a new expression object . Unlike Expression.as ... ( Object value ) Create a predicate to test whether the expression is equal to the argument. Inherited from | |
ObjectDB License Agreement [ver. 2.0.4] and objects in a database file. The full edition of the Software (without the restrictions | |
Strings in JPQL and Criteria Queries demonstrates, most methods are overloaded to support optional arguments and to accept both simple Java objects and criteria expressions. | |
JPA Attributes Annotations property as an attribute containing a collection of embedded objects . This is used for "one-to-many | |
JPA Metamodel Attributes, wrappers, Strings), embedded objects , and associations (reference fields and properties | |
Auto Generated Values. This generator creates automatic object IDs for entities that do not have defined primary key | |
JPA Fetch Plan Graphs attribute loading within the object hierarchy. The common super-interface for both entity and subgraphs | |
Numbers in JPQL and Criteria Queries expression or a simple Java numeric object . // Create path and parameter expressions: Expression path | |
JPA Class Enhancer. Without enhancement, only persistent collection and map fields can be loaded lazily (by using proxy objects | |
Step 2: Entity Class and Persistence Unit To store objects in an ObjectDB database using JPA we need to define an entity class: Open the [New Java Class] dialog box, e.g. by right clicking the project node (in the [Package Explorer] window ... objects in the database was created in the project (under Java Resources: src guest). Use copy | |
Step 4: Add a Controller Class. The JSP uses the GuestDao component to display the existing Guest objects . The returned ModelAndView object defines a target JSP ( "guest.jsp" ) and passes the GuestDao component to the JSP as a request | |
Step 2: Define a JPA Entity Class To store objects in an ObjectDB database using JPA we need to define an entity class: Right click on the project in the [Package Explorer] window and select New Class . Enter tutorial as the package ... should represent Point objects in the database. Apart from the @Entity annotation and the id field | |
Step 2: Define a JPA Entity Class To store objects in an ObjectDB database using JPA we need to define an entity class: Open the [New Java Class] dialog box, e.g. by right clicking the tutorial package node (in the [Projects] window ... objects in the database. Besides the @Entity annotation and the id field (and its annotations | |
Step 2: Entity Class and Persistence Unit To store objects in an ObjectDB database using JPA we need to define an entity class: Open the [New Entity Class] dialog box, e.g. by right clicking the project node (in the [Projects] window ... objects in the database was created in the project (under Source Packages guest). Use copy and paste | |
Step 3: Define a Spring DAO Component Operations on the database will be performed by an instance of a Data Access Object (DAO) that we will define in this step as a Spring MVC component: Open the [New Java Class] dialog box by right ... ; Guest objects from the database. By using Spring components we can move some work from | |
Step 2: Entity Class and Persistence Unit To store objects in an ObjectDB database using JPA we need to define an entity class: Right click the project node (in the [Package Explorer] window), select New Source Folder ... Finish to create the new entity class. A new class that should represent Guest objects in | |
Step 3: Add a Main Class In this step we will add a main class to the project to store and retrieve Point objects from the database: Right click the tutorial package in the [Package Explorer] window and select New Class ... = emf.createEntityManager(); // Store 1000 Point objects in the database: em.getTransaction().begin(); for (int i = 0; i | |
Step 3: Add a Main Class In this step we will add code to the Main class (that was generated with the project) in order to store Point objects in the database and then retrieve them from the database. Use copy and paste ... .createEntityManager(); // Store 1000 Point objects in the database: em.getTransaction().begin(); for (int i = 0; i | |
Step 4: Add a Controller Class to display the existing Guest objects . The returned ModelAndView object defines a target JSP ( "guest | |
Step 2: Entity Class and Persistence Unit To store objects in an ObjectDB database using JPA we need to define an entity class: Open the [New Entity Class] dialog box, e.g. by right clicking the project node (in the [Projects] window ... objects in the database was created in the project (under Source Packages guest). Use copy and paste | |
Step 3: Define a Spring DAO Component Operations on the database will be performed by an instance of a Data Access Object (DAO) that we will define in this step as a Spring MVC component: Open the [New Java Class] dialog box by right ... ; Guest objects from the database. By using Spring components we can move some work from | |
Step 2: Define a JPA Entity Class To store objects in an ObjectDB database using JPA we need to define an entity class: Open the [New Java Class] dialog box, e.g. by right clicking the project node (in the [Projects] window ... on " + signingDate + ")"; } } The new class should represent Guest objects in the database | |
Step 4: Run the Application 1,000 objects . You can view the content of the database file by opening it in the ObjectDB Explorer | |
JPA Tutorials The following tutorials demonstrate how to develop database driven applications using JPA and the ObjectDB ODBMS ( Object Oriented Database Management System). Console JPA Tutorial The Quick Start tutorial demonstrates how to use ObjectDB and JPA in a console application: Quick Start with JPA |