ObjectDB Database Search

Hi, I am using JDO access to the database with the persistence defined in package.jdo XML metadata files. In those metadata files I have few persistence-capable classes which had extents in ObjectDB ... and own OID) in those few peristence-capable ones. Example of JDO metadata :        

Hi, I notice that objectdb zip file has: javax.transaction- api -1.3.jar However that library has moved to jakarta.transaction- api and is now on version 2.0.1 Questions: a) Do I need this library at all? b) If I do need it, do I use jakarta.transaction- api 1.3 or 2.0.1? Similarly java

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

list links to detailed explanations of how to build clauses for Criteria API queries: Criteria SELECT

is developed for an existing old relational database). By using the Java Persistence API (JPA

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

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 Demonstrates basic database

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 methods for performing database operations. Many applications require multiple database connections

The JPA Criteria API provides type-safe interfaces for defining query result expressions and ordering, mirroring the SELECT and ORDER BY clauses in JPQL or SQL. These interfaces allow you to specify exactly what data is returned and how it is sorted within the result set. SELECT clause elements

the attributes of the corresponding entity, typically for use with the Criteria API .

HAVING COUNT(c) 1 can be built using the criteria query API as follows: CriteriaQuery q = cb

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

runtime exception for the JPA API . All other JPA exceptions inherit from this class, enabling

JDO 3 introduces the ability to specify and query metadata of persistable types dynamically. ObjectDB 2 supports specifying metadata by: JPA XML Mapping Metadata JPA Annotations JDO XML Metadata (e.g. package.jdo) JDO Annotations All these methods are static, i.e. the metadata has to be provided

Jakarta Persistence (JPA) Field in jakarta.persistence.PersistenceConfiguration SCHEMAGEN_CREATE_SOURCE The source of artifacts to be created. Standard sources are: metadata , script , metadata -then-script , script-then- metadata . The location of the script source is specified by "jakarta

Jakarta Persistence (JPA) Field in jakarta.persistence.PersistenceConfiguration SCHEMAGEN_DROP_SOURCE The source of artifacts to be dropped. Standard sources are: metadata , script , metadata -then-script , script-then- metadata . The location of the script source is specified by "jakarta

can be included in the query result by specifying this annotation in the metadata . Example: Query q = em

metadata . Default: {} Since: Jakarta Persistence (JPA) 1.0 QueryHint[] hints Query properties

of a SqlResultSetMapping , as defined in metadata . The named result set mapping is used to interpret the result set

. 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

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

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

API . Criteria API bulk update operations map directly to database update operations, bypassing any

. Since: Jakarta Persistence (JPA) 2.0 The JPA Criteria API Queries article explains how to use ... : Applications using the string-based API may need to specify the type of the select item when it results

API Criteria API bulk delete operations map directly to database delete operations. The persistence

Persistence (JPA) 2.0 The FROM clause (JPQL / Criteria API ) article explains how to use Join . Public ... attribute. Note: Applications using the string-based API may need to specify the type resulting from

parameterName - name of the parameter as registered or specified in metadata type - type of the parameter

of the parameter as registered or specified in metadata Returns: the result that is passed

metadata Returns: the new stored procedure query instance. Throws: IllegalArgumentException

- a reference to the query defined in metadata Returns: the new query instance. Throws

metadata Returns: the new query instance. Throws: IllegalArgumentException - if a query has not

. Parameters: name - the name of a query defined in metadata resultClass - the type of the query result

Jakarta Persistence (JPA) Method in jakarta.persistence.NamedNativeQuery String resultSetMapping The name of a SqlResultSetMapping , as defined in metadata . The named result set mapping is used to interpret the result set of the native SQL query. Alternatively, the elements NamedNativeQuery

Jakarta Persistence (JPA) Method in jakarta.persistence.NamedStoredProcedureQuery String[] resultSetMappings The names of one or more result set mappings, as defined in metadata . Default: {} Since: Jakarta Persistence (JPA) 1.0

may be thrown as part of an API call, a flush or at commit time. The current transaction, if one is active

transaction rollback. This exception may be thrown as part of an API call, at, flush or at commit time

the string-based API may need to specify the type resulting from the Path.get operation in order

. Since: Jakarta Persistence (JPA) 2.0 The Logical Operators in JPQL and Criteria API article explains

the string-based API may need to specify the type resulting from the Path.get operation in 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

/ Criteria API ) article explains how to use Selection . Public Instance Methods Selection alias

the string-based API may need to specify the type resulting from the Path.get operation in order

API . If the provider implementation of Query does not support the given type

attribute. Note: Applications using the string-based API may need to specify the type resulting from

using the string-based API may need to specify the type resulting from the Path.get operation in

) Create a path corresponding to the referenced attribute. Note: Applications using the string-based API

cls ) Return an object of the specified type to allow access to the provider-specific API

access to a provider-specific API . If the provider implementation of Query does not support the given

mapping, and used to refer to it in the methods of the Query and StoredProcedureQuery APIs

mode are discussed in Section 1.2 . Because the JDO API and the format of the database file