ObjectDB Database Search

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 .  

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

/slf4j- api -1.6.4.jar, URLEntry : file:/usr/local/glassfish/glassfish/domains/dex/applications ... .0-SNAPSHOT/lib/javaee- api -6.0.jar, URLEntry : file:/usr/local/glassfish/glassfish/domains/dex ... - org.glassfish.internal. api .DelegatingClassLoader@43de6a4f AT Thu Jun 02 14:19:14 CEST 2016 BY :java

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

with the Persistence api : EntityManagerFactory emf = Persistence.createEntitManagerFactory("project.odb"); //this set ... -classes to false. The Metamodel API still returns the empty set when 'getEntities()' is invoked ... the Metamodel API (storing objects, etc)? Does it work? support Support So I changed the persistence

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

have long been a fan of JDO as it's a hugely easer API and gets work done with a lot less metadata .  ... and a test will be needed. Regarding JPA/JDO, when using ObjectDB no need to use much metadata in either of them, so you can stay with JPA and just remove the ORM metadata when switching to ObjectDB

Mahmoud Defining default listeners is one of the few things that currently require XML metadata ... Is there a way using em.getDelegate() and then using objectdb api ? I would like to do specifics actions ... chapter 3 of the manual. You may also register listener using the JDO API , which is not documented but supported by ObjectDB. support Support

In a class how do I define which are the fields to be stored? (using JDO API ) It's using persistence-modifier="persistent" ? If I have a class with 40 fields and I only want to store ... @NonPersistent  (starting JDO 2.1 you can use annotations instead of XML metadata ). support Support

JPA Static 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 {@value #SCHEMAGEN_CREATE_SCRIPT_SOURCE}. Since: JPA 3.2

: info - metadata for use by the persistence provider map - a Map of integration-level properties ... the metadata Since: JPA 1.0 EntityManagerFactory createEntityManagerFactory ( PersistenceConfiguration   ... . Parameters: info - metadata for use by the persistence provider map - properties for schema generation

) Called by the container when an EntityManagerFactory is to be created. Parameters: info - metadata ... "} . Return: {@link EntityManagerFactory} for the persistence unit specified by the metadata Since: JPA 1.0

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

JPA Annotation Attribute in jakarta.persistence.NamedStoredProcedureQuery String[] resultSetMappings default {} The names of one or more result set mappings, as defined in metadata . Since: JPA 2.1

. Since: JPA 2.1 String[] resultSetMappings default {} The names of one or more result set mappings, as defined in metadata . Since: JPA 2.1

of the parameter as registered or specified in metadata type - type of the parameter mode - parameter mode Return: the same query instance Since: JPA 2.1

JPA Annotation Attribute in jakarta.persistence.NamedNativeQuery String resultSetMapping default "" 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 entities , classes

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

this annotation in the metadata . Example: {@snippet : Query q = em.createNativeQuery( "SELECT o.id AS

of the parameter as registered or specified in metadata type - type of the parameter mode - parameter mode Return: the same query instance Since: JPA 2.1

registered or specified in metadata Return: the result that is passed back through the parameter

to the query defined in metadata Return: the new query instance Throws: IllegalArgumentException - if a query

. Parameters: info - metadata for use by the persistence provider map - properties for schema generation

of type Object[] . Parameters: name - name assigned to the stored procedure query in metadata Return

JPA Method in jakarta.persistence.EntityManager Query createNamedQuery (   String name ) Create an instance of Query for executing a named query written in the Jakarta Persistence query language or in native SQL. Parameters: name - the name of a query defined in metadata Return

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

Issue with TYPE expression in Criteria API

criteria api / embedded objects / where order

JPA Interface CriteriaDelete Type Parameters: - the entity type that is the target of the DELETE Super Interfaces: CommonAbstractCriteria The CriteriaDelete interface defines functionality for performing bulk delete operations using the Criteria API Criteria API bulk delete operations map directly

JPA Interface CriteriaBuilder Used to construct criteria queries, compound selections, expressions, predicates, orderings. Note that Predicate is used instead of Expression in this API in order ... Criteria API Queries article explains how to use CriteriaBuilder . Public Methods Expression abs

" expression. Since: JPA 2.0 The Paths and Types in JPQL and Criteria API article explains ... corresponding to the referenced attribute. Note: Applications using the string-based API may need to specify

JPA Interface CriteriaUpdate Type Parameters: - the entity type that is the target of the update Super Interfaces: CommonAbstractCriteria The CriteriaUpdate interface defines functionality for performing bulk update operations using the Criteria API . Criteria API bulk update operations map

functionality that is specific to top-level queries. Since: JPA 2.0 The JPA Criteria API Queries article ... : Applications using the string-based API may need to specify the type of the select item when it results

.hummingbird.CT_Container.computeContainer(CT_Container.java:214) com.agile.hummingbird. API .handleGetContainer( API .java:3130) com.agile.hummingbird. API .directRequest( API .java:965) com.agile.hummingbird. API .handleWebSocketRequest( API .java:808) com.agile.hummingbird.WebSocketServerListener

JPA Interface Selection Type Parameters: - the type of the selection item Super Interfaces: TupleElement The Selection interface defines an item that is to be returned in a query result. Since: JPA 2.0 The SELECT clause (JPQL / Criteria API ) article explains how to use Selection . Public Methods

JPA Interface Root Type Parameters: - the entity type referenced by the root Super Interfaces: FetchParent , From A root type in the from clause. Query roots always reference entities. Since: JPA 2.0 The FROM clause (JPQL / Criteria API ) article explains how to use Root . Public Methods EntityType

part of an API call, at, flush or at commit time. The current transaction, if one is active

JPA Method in jakarta.persistence.EntityManagerFactory T unwrap (   Class  cls ) Return an object of the specified type to allow access to a provider-specific API . If the provider implementation of EntityManagerFactory does not support the given type, the PersistenceException

when a pessimistic locking conflict occurs. This exception may be thrown as part of an API call, a flush or

and Criteria API article explains how to use Predicate . Public Methods List getExpressions () Return

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 get operation in order to avoid the use of Path