ObjectDB Database Search
1-50 of 163 resultsSELECT clause (JPQL / Criteria API) in criteria queries The criteria query API provides several ways to set the SELECT clause. Single ... it as the SELECT clause content, overriding any previously set SELECT content. Many valid criteria API expressions can be used as a selection because criteria API expressions are represented by Expression | |
JPA Extended API Reference Guide Jakarta Persistence API (JPA) 3.2 documentation, generated from the official JavaDoc and enriched with practical notes. It groups the API types into logical sections to help you locate core concepts ... the fundamental classes and interfaces for entity management and persistence operations. Covers the query API | |
What is the Java Persistence API (JPA)? The Java Persistence API (JPA) is a standard API for accessing databases from within Java applications. The main advantage of JPA over JDBC (the older Java API for interacting with databases ... of the Java Persistence API (JPA). By interacting with ObjectDB using standard JPA | |
JPA Query API because it introduces the Country class to ObjectDB. Dynamic JPQL, Criteria API , and named queries In ... Criteria API provides an alternative way to build dynamic queries. It uses Java objects that represent | |
WHERE clause (JPQL / Criteria API) JPQL query: SELECT c FROM Country c WHERE c.population :p can be built using the criteria query API | |
FROM clause (JPQL / Criteria API)Explains how to use the FROM clause and JOIN expressions in a JPA/JPQL query. | |
Logical Operators in JPQL and Criteria APIExplains how to use AND, OR and NOT in JPQL queries. | |
ObjectDB API ReferenceAll about ObjectDB API Reference in Java/JPA database - explanations, examples, references, links and related information. | |
ObjectDB APIsAll about ObjectDB APIs in Java/JPA database - explanations, examples, references, links and related information. | |
ObjectDB - JPA Object Database for Java using the Java Persistence API (JPA). It is the first persistence solution that combined a powerful ... tutorial now... Protect your investment. Use a standard Java API . ObjectDB became the first Object Oriented Database with built in support for the two standard Java database APIs : Java | |
Query Parameters in JPA does not provide an API to define parameters explicitly (except when using the Criteria API ). Instead ... over ordinal parameters. Criteria Query Parameters In a JPA query built using the JPA Criteria API ... , parameters are more flexible and support elements that are unavailable as literals, such as entities. API | |
Is ObjectDB better than competing object databases?: ObjectDB is unique in supporting the standard APIs . It is the only object database with built in support for the Java Persistence API (JPA). It also supports a more recent and advanced version of the Java Data Objects (JDO) API than competing object databases. By using a standard API such as JPA | |
JPA Queries Jakarta Persistence provides powerful APIs for executing database queries using JPQL strings or the programmatic Criteria API . These interfaces support both static and dynamic query construction ... instructions, refer to the JPA Query API section in the ObjectDB manual. Criteria query API | |
JPA Metamodel and Graphs The Jakarta Persistence (JPA) Metamodel API provides a type-safe way to introspect the persistent ... to retrieve entity and attribute information by class or name, similar to the reflection API in Java ... and further explanation, refer to the JPA Metamodel API section in the ObjectDB manual. Criteria query | |
JPA Query Expressions (JPQL / Criteria) Criteria API expressions. Atomic expressions The atomic query expressions are: JPQL / Criteria Variables ... with operators and functions. Operators and functions JPQL and the Criteria API support the following ... the following pages: Detailed explanations of how to build Criteria API expressions are provided | |
JPA Class Enhancer into an ANT build script, as follows: Enhancement API The ObjectDB Enhancer can also be invoked from ... ()); The enhancement API and invocation of the Enhancer from Java code is useful, for instance, in | |
JPA Core Types your ObjectDB database. An alternative bootstrap class that offers a programmatic API for configuration ... attributes, and access entity content not yet fetched due to lazy loading. Provides an API for programmatic | |
Java 8 time API Hi. Is Java 8 new DateTime API supported natively or through Converters in the newest versions of objectdb? If not, can we expect this feature in the next releases? Best regards and congratulations on this awesome database. Amsterdam Amsterdam Luís de Lima Filho It is not | |
Softdelete api like hibernate maybe recover back with api ? It wont be hard to implement these to objectdb core! best regards kadirbasol Kadir BASOL | |
Separate ODB files API Customer asked during opened ObjectDb connection (ODB location A) to stop writing and continue to another ODB file (Location B). Does exist some API to achieve that? What is a possible solution? Harman Alexander Golyshkin You have to close the database in location A, copy it from location | |
Is there an API to get the current version of ObjectDB that's being used? Is there an API to get the current version of ObjectDB that's being used? This would be very handy to have, because it is somewhat difficult to know what version of the ObjectDB you are currently using since the objectdb.jar filename remains the same for all versions (which is not a bad thing by | |
JPA Criteria Query Expressions Jakarta Persistence (JPA) Criteria API uses a hierarchy of interfaces to model query conditions and selections, enabling the construction of dynamic, type-safe queries. These interfaces represent the building blocks for defining query logic programmatically. The hierarchy of the expression | |
JPA Metamodel Attributes The Jakarta Persistence (JPA) Metamodel API defines a structured hierarchy of interfaces and enumerations to represent the attributes of managed persistent types (entities, embeddable and superclasses). Metamodel Attributes Hierarchy in Jakarta Persistence (JPA) 3. Base attribute definitions | |
JPA Metamodel Types The Jakarta Persistence (JPA) Metamodel API defines a structured hierarchy of interfaces and enumerations to represent the persistent types within a domain model. Metamodel Types Hierarchy in Jakarta Persistence (JPA) 3.2 Base type definitions The core abstractions of model types | |
JPA Query Structure (JPQL / Criteria) list links to detailed explanations of how to build clauses for Criteria API queries: Criteria SELECT | |
Is ObjectDB better than Object Relational Mapping (ORM)? is developed for an existing old relational database). By using the Java Persistence API (JPA | |
JPA Criteria Queries The Jakarta Persistence (JPA) Criteria API provides a type-safe, programmatic alternative to string-based JPQL for constructing dynamic queries, ensuring compile-time safety and facilitating easier refactoring. It defines a structured hierarchy of interfaces for SELECT, UPDATE, and DELETE | |
jakarta.persistence.EntityManagerFactory via the PersistenceConfiguration API . Every persistence unit has a transaction type , either JTA , or RESOURCE_LOCAL . Resource ... other useful APIs : an instance of Metamodel exposing a model of the managed types associated ... , information that can be set by means of the query APIs can be overridden. Information | |
jakarta.persistence.EntityManager, that is scheduled for removal from the database upon transaction commit. The EntityManager API is used ... a native SQL query. In the next release of this API , the return type of this method will change | |
jakarta.persistence.criteria.Path. Since: Jakarta Persistence (JPA) 2.0 The Paths and Types in JPQL and Criteria API article explains ... the string-based API may need to specify the type resulting from the get operation in order to avoid | |
jakarta.persistence.criteria.Root Persistence (JPA) 2.0 The FROM clause (JPQL / Criteria API ) article explains how to use Root ... attribute. Note: Applications using the string-based API may need to specify the type resulting from | |
jakarta.persistence.criteria.CriteriaBuilder is used instead of Expression in this API in order to work around the fact that Java generics are not compatible with varags. Since: Jakarta Persistence (JPA) 2.0 The JPA Criteria API Queries article | |
jakarta.persistence.PessimisticLockException may be thrown as part of an API call, a flush or at commit time. The current transaction, if one is active | |
jakarta.persistence.LockTimeoutException transaction rollback. This exception may be thrown as part of an API call, at, flush or at commit time | |
jakarta.persistence.criteria.PluralJoin the string-based API may need to specify the type resulting from the Path.get operation in order | |
jakarta.persistence.criteria.Predicate. Since: Jakarta Persistence (JPA) 2.0 The Logical Operators in JPQL and Criteria API article explains | |
jakarta.persistence.criteria.MapJoin-based API may need to specify the type resulting from the Path.get operation in order to avoid the use | |
jakarta.persistence.criteria.Order Jakarta Persistence (JPA) Interface jakarta.persistence.criteria.Order An object that defines an ordering over the query results. Since: Jakarta Persistence (JPA) 2.0 The ORDER BY clause (JPQL / Criteria API ) article explains how to use Order . Public Instance Methods Expression getExpression | |
jakarta.persistence.criteria.Selection / Criteria API ) article explains how to use Selection . Public Instance Methods Selection alias | |
jakarta.persistence.criteria.SetJoin the string-based API may need to specify the type resulting from the Path.get operation in order to avoid | |
jakarta.persistence.TypedQuery of the specified type to allow access to a provider-specific API . If the provider implementation | |
jakarta.persistence.criteria.CollectionJoin: Applications using the string-based API may need to specify the type resulting from the Path | |
Step 1: Create a Maven Web Project.transaction jta 1.1 javax.servlet servlet- api 2.5 provided javax.servlet.jsp jsp- api 2.1 provided org | |
Step 1: Create a Maven Web Project; javax.servlet servlet- api 2.5 provided javax.servlet.jsp jsp- api 2.1 provided | |
Why does ObjectDB duplicate classes from javax.jdo:jdo-api? Hello, I'm using the Java Persistence API (JPA) in a library to not lock myself in to using ... . To use the @Index annotation, I had to add a dependency to the JDO API version 3.1 (old link: https://mvnrepository.com/artifact/javax.jdo/jdo- api /3.1). The code works just fine, but when I use | |
Enhancer API (JDO 3.0) One of the new features of JDO 3 is a standard API for enhancement. Currently ObjectDB implements its own enhancement API . support Support | |
ArrayIndexOutOfBounds with Critera API and function call Hello, This is getting really frustrating sorry but we're close before delivering our app to our customer and went against a show-stopper again. We're building a simple query with the criteria api ... ; } }; Create Selection Query (Critera- API ) from * TestEntity and add WHERE class | |
Strange Error with Criteria API and Sorting the sorted results. However, running this with the criteria API produces this error: Caused by: com | |
jakarta.persistence.criteria.Path.get(String) Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.Path Path get ( String attributeName ) Create a path corresponding to the referenced attribute. Note: Applications using the string-based API may need to specify the type resulting from the Path.get operation in order | |
What is the Java Data Objects (JDO)? The Java Data Objects (JDO) is another standard for accessing persistent data in databases, using plain old Java objects (POJO) to represent the object model. Unlike Java Persistence API (JPA ... , and it is probably the most popular Java API for object databases today. |