ObjectDB Database Search

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

/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

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

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

metadata files:                       ... try I changed only the metadata to this:               ... :82)   I thought that simply changing JDO metadata is not sufficient. Should it be sufficient

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

(JpaQuery.java:719) - locked (a com.objectdb.jdo.PMImpl) at com.agile.hummingbird. API .handleQuery( API .java:3020) at com.agile.hummingbird. API .directRequest( API .java:852) at com.agile.hummingbird. API .handleWebSocketRequest( API .java:614) at com.agile.hummingbird.WebSocketServerListener.onWebSocketText

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

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

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

Jakarta Persistence (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 Path.get operation in order

Jakarta Persistence (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

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

Jakarta Persistence (JPA) Method in jakarta.persistence.EntityManager Query createNativeQuery (    String sqlString ,    Class resultClass ) Create an instance of Query for executing a native SQL query. In the next release of this API , the return type of this method will change

Issue with TYPE expression in Criteria API

;      at org.hibernate.validator. metadata .MetaConstraint. (MetaConstraint.java:75)         at org.hibernate.validator. metadata ... ; at org.hibernate.validator. metadata .BeanMetaDataImpl.initMethodConstraints(BeanMetaDataImpl.java:376

.endAction(AC_Action.java:878) at com.agile.hummingbird. API .executeEndAction( API .java:1874) at com.agile.hummingbird. API .handleAction( API .java:1614) at com.agile.hummingbird. API .directRequest( API .java:1089) at com.agile.hummingbird. API .handleWebSocketRequest( API .java:890) at com.agile.hummingbird

is actually 2 databases to seperate metadata used for searching and the data itself. So in total ... is reperesented by 2 databases under the covers - one for small metadata objects which are used ... which can be anything from 1k to 10mb. We've proved the benefits of keeping the metadata & data separate in past

.vereinsverwaltung.abrechnung. api .model.mitglied.MitgliedDebitorenKontoFragment) $1.qubletFRAGMENTMAP.get('com.lexware.vereinsverwaltung.abrechnung. api .model.mitglied.MitgliedDebitorenKontoFragment')).debitor=true)) AND ((((com.lexware.vereinsverwaltung.abrechnung. api .model.mitglied

.hummingbird. API .executeEndAction( API .java:1718) at com.agile.hummingbird. API .handleAction( API .java:1480) at com.agile.hummingbird. API .directRequest( API .java:1001) at com.agile.hummingbird. API .handleWebSocketRequest( API .java:836) at com.agile.hummingbird.WebSocketServerListener.onWebSocketText

.hummingbird. API .handleGetContainer( API .java:2745) at com.agile.hummingbird. API .directRequest( API .java:802) at com.agile.hummingbird. API .handleWebSocketRequest( API .java:630) at com.agile.hummingbird ... .java:163) at com.agile.hummingbird. API .handleGetContainer( API .java:2745) at com.agile.hummingbird. API

output here.  I confirmed that the directory C:\Users\kwhittin\new_workspace_birt\. metadata ... _birt\. metadata \.plugins\org.eclipse.birt.report.data.oda.jdbc.dbprofile.sampledb\db\META-INF ... \new_workspace_birt\. metadata \.plugins\org.eclipse.birt.report.data.oda.jdbc.dbprofile.sampledb\db