ObjectDB Database Search

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

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 .  

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

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

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

maybe recover back with api ? It wont be hard to implement these to objectdb core! best regards kadirbasol Kadir BASOL

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? 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

Hi, I am about to update the JDO metadata in the package.jdo files after moving from ObjectDB 1 to 2. However I found that there is no complete description or guide how the XML metadata should look ... description of XML metadata for ObjectDB ver2 using JDO which I did not find? 2. Is the combined

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

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

) 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

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

the sorted results. However, running this with the criteria API produces this error: Caused by: com