Internal Website Search
1-50 of 200 resultsJPA Criteria API Queries The JPA Criteria API provides an alternative way for defining JPA queries, which is mainly useful for building dynamic queries whose exact structure is only known at runtime. JPA Criteria API vs ... of using the criteria API is that errors can be detected earlier, during compilation | |
JPA Metamodel API The JPA Metamodel API , which is introduced in JPA 2.0, enables examining the classes, fields and properties of the persistent object model, similarly to the Java reflection API . The main interface of the JPA Metamodel API is: Types (mainly classes) and attributes (persistent field and properties | |
SELECT clause (JPQL / Criteria API) of the query result list and other factors. SELECT in Criteria Queries The criteria query API   ... ;(overriding previously set SELECT content if any). Every valid criteria API expression can be used as selection, because all the criteria API expressions are represented by a sub interface | |
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 Metamodel API The JPA Metamodel API provides the ability to examine the persistent object model and retrieve ... Metamodel API is Metamodel . It can be obtained either by the EntityManagerFactory 's getMetamodel ... the specified type to ObjectDB. Type Interface Hierarchy Types are represented in the Metamodel API by | |
JPA Query API variant is valid because it introduces the Country class to ObjectDB. Dynamic JPQL, Criteria API ... can be built dynamically at runtime. The JPA Criteria API provides an alternative way for building dynamic | |
JPA Metamodel API Attributes The following interfaces and enum types represent attributes (persistent fields and properties) in the JPA Metamodel API : See the Metamodel Attribute Interface Hierarchy section for more details and examples. | |
JPA Metamodel API Types The following interfaces and enum represent types in the JPA Metamodel API : See the Metamodel Type Interface Hierarchy section for more details and examples. | |
WHERE clause (JPQL / Criteria API) can be built by using the criteria query API as follows: CriteriaQuery q = cb. createQuery (Country.class | |
Paths and Types in JPQL and Criteria API and navigations are represented in the JPA Criteria API by the Path interface and by | |
ORDER BY clause (JPQL / Criteria API) can be built using the criteria query API as follows: CriteriaQuery q = cb. createQuery (Country.class | |
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. | |
Comparison in JPQL and Criteria APIExplains how comparison operators can be used in JPQL queries, including in comparing null values. | |
ObjectDB Object Database Features support of the JPA and JDO APIs . Fundamental features of relational databases (e.g. primary keys ... database files (the ObjectDB Doctor ). Standard Persistence APIs ObjectDB is the only Object-Oriented Database with built in support for JPA 2 . Java Persistence API (JPA) Most features of JPA 2 | |
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 identifier that serves as the parameter name. JPA does not provide an API for defining the parameters explicitly (except when using criteria API ), so query parameters are defined implicitly by ... that is built by using the JPA Criteria API - parameters (as other query elements) are represented by objects | |
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 Queries are represented in JPA by the Query and TypedQuery interfaces: The JPA Query API ... ;(e.g. "SELECT c FROM Country" ). Criteria Query API Building dynamic queries with a structure ... Query API , as a cleaner alternative that enables building a dynamic query by using instances | |
JPA 2.0 Criteria API: (When) Fully supported ? API . Tested JPA 2.0 providers * Hibernate 3.6.1 - PASS. Minimum version 3.6.1 - older versions have a bug in the Criteria API implementation which prevents correct negation ... ; * DataNucleus 2.2.2 - FAIL. Was not able to create even a simple query with Criteria API .   | |
Which API should I use - JPA or JDO? You can use ObjectDB with either the Java Persistence API (JPA) or the Java Data Objects (JDO) API ... the primary API , and if necessary, switch to JDO as a secondary API for special additional features that are supported only by JDO. Selecting the more popular API leads to more portable application | |
Enhancement API - NullPointerException Hi! I am trying to use the Enhancement API from within my application like this: com.objectdb.Enhancer.enhance("my.package.Foo"); However, I get the following NullPointerException: [ObjectDB 2.7.1 ... above). I'm not sure what is happening, the class exists and trying the API with a non-existent class | |
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 | |
JPA Reference (JavaDoc) This reference contains the API documentation (similar to JavaDoc) of the Java Persistence API (JPA) 2.0. The content is derived from the original JPA documentation (in the EclipseLink JPA 2 RI) with some additions and notes. The JPA types are organized into the following sections: The purpose | |
JPA Class Enhancer Similarly, enhancement can be also be integrated into an ANT build script, as so: Enhancement API ... .*,test.X", text.X.class.getClassLoader()); The enhancement API and invocation of the Enhancer from | |
Can I use ObjectDB to access a relational database? To access relational databases using the Java Persistence API (JPA) you will need an Object Relational Mapping (ORM) tool, such as Hibernate, TopLink, EclipseLink, Open JPA or DataNucleus. The DataNucleus ORM implementation supports also the Java Data Objects (JDO) API . ObjectDB is a full featured | |
ObjectDB Overview API - managed only by standard Java APIs (JPA 2 / JDO 2). Extremely fast - faster than any other JPA | |
Chapter 4 - JPA Queries (JPQL / Criteria) well as how to use the JPA Criteria API , which provides an alternative way for building queries in JPA, based on JPQL. The first section describes the API that JPA provides for using dynamic and static | |
Retrieving JPA Entity Objects The Java Persistence API (JPA) provides various ways to retrieve objects from the database. The retrieval of objects does not require an active transaction because it does not change the content of the database. The persistence context serves as a cache of retrieved entity objects. If a requested | |
Is ObjectDB better than Object Relational Mapping (ORM)? is developed for an existing old relational database). By using the Java Persistence API (JPA | |
Chapter 3 - Using JPA This chapter explains how to manage ObjectDB databases using the Java Persistence API (JPA). The first two pages introduce basic JPA interfaces and concepts: The next section explains how to use JPA for database CRUD operations: More advanced topics (e.g. locking and events) are discussed in the last section: | |
ObjectDB 2.9 Developer's Guide Welcome to ObjectDB for Java/JPA Developer's Guide. Here you can learn how to develop database applications using ObjectDB and JPA (Java Persistence API ). The main purpose of this guide is to make you productive with ObjectDB and JPA in a short time. Guide Structure This manual is divided into | |
Database Connection using JPA Working with the Java Persistence API (JPA) consists of using the following interfaces: Overview A connection to a database is represented by an EntityManager instance, which also provides functionality for performing operations on a database. Many applications require multiple database | |
Criteria Query Selection and Results The JPA Criteria API interfaces in this group are used for setting the SELECT and ORDER BY clauses and for representing query results as tuples. SELECT Clause Elements The content of the SELECT clause in a criteria query is represented by Selection : Because Selection is a super interface | |
GROUP BY and HAVING clauses using the criteria query API as follows: CriteriaQuery q = cb. createQuery (Country.class); Root c = q | |
About Us ObjectDB Software develops, markets and supports the ObjectDB Object-Oriented Database Management System (ODBMS). ObjectDB Software is the market leader in providing a very high performance persistence solution for Java, based on the Java Persistence API (JPA) and the Java Data Objects (JDO | |
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 | |
No Entity Class API and should not be bound to specific entity classes and persistent fields. Therefore, an API for accessing ... database with no original classes: Use the Metamodel API to find details on the entity classes in ... exists in the database and missing from the classpath. Use Java reflection API with information | |
JPA Query Criteria API (JPA 2.0) The JPA Criteria API supports dynamic definition of JPQL queries using CriteriaBuilder as ... Criteria API in expected in future versions. support Support Implementation of the JPA Criteria Query API was just added to ObjectDB in version 2.1.1_01. It will be officially supported | |
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 | |
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 | |
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. | |
[ODB1] Chapter 1 - About ObjectDB code. The JDO API is available today for most relational database systems (RDBMS), e.g. Oracle, IBM ... URL), because the JDO API is the same for both modes. 1.3 ObjectDB Editions ObjectDB | |
[ODB1] Chapter 8 - ObjectDB Server mode are discussed in Section 1.2 . Because the JDO API and the format of the database file | |
JDO Reference (JavaDoc) This reference contains the API documentation (similar to JavaDoc) of JDO 2.2. The content is derived from the original JDO documentation with some additions and notes. The most basic JDO types are: All the other JDO types are organized into the following sections: |