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

fetch doi. metadata metadata left join fetch metadata .titles titles left join fetch metadata .creators creators left join fetch metadata .descriptions descriptions left join fetch metadata .publishers publishers left join fetch metadata .contributors contributors left join fetch metadata .dates dates left

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 .  

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

using the criteria query API as follows: CriteriaQuery q = cb. createQuery (Country.class); Root c = q

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

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

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 to avoid

of the specified type to allow access to a provider-specific API . If the provider implementation

: Applications using the string-based API may need to specify the type resulting from the Path

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

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

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

an object of the specified type to allow access to a provider-specific API . If the provider

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

a Jakarta EE container environment as well; however, support for the Java SE bootstrapping APIs is not

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

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

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

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

One of the new features of JDO 3 is a standard API for enhancement. Currently ObjectDB implements its own enhancement API . support Support