ObjectDB Database Search

in criteria queries The criteria query API provides several ways to set the SELECT clause. Single ... it as the SELECT clause content, overriding any previously set SELECT content. Many valid criteria API expressions can be used as a selection because criteria API expressions are represented by Expression

Explains how to use the FROM clause and JOIN expressions in a JPA/JPQL query.

Explains how to use AND, OR and NOT in JPQL queries.

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 :        

, that is scheduled for removal from the database upon transaction commit. The EntityManager API is used ... . Parameters: name - the name of a query defined in metadata Returns: the new query instance. Throws ... . Parameters: name - the name of a query defined in metadata resultClass - the type of the query

: ObjectDB is unique in supporting the standard APIs . It is the only object database with built in support for the Java Persistence API (JPA). It also supports a more recent and advanced version of the Java Data Objects (JDO) API than competing object databases. By using a standard API such as JPA

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

via the PersistenceConfiguration API . Every persistence unit has a transaction type , either JTA , or RESOURCE_LOCAL . Resource ... other useful APIs : an instance of Metamodel exposing a model of the managed types associated ... , information that can be set by means of the query APIs can be overridden. Information

Criteria API expressions. Atomic expressions The atomic query expressions are: JPQL / Criteria Variables ... with operators and functions. Operators and functions JPQL and the Criteria API support the following ... the following pages: Detailed explanations of how to build Criteria API expressions are provided

Jakarta Persistence (JPA) Criteria API uses a hierarchy of interfaces to model query conditions and selections, enabling the construction of dynamic, type-safe queries. These interfaces represent the building blocks for defining query logic programmatically. The hierarchy of the expression

The Jakarta Persistence (JPA) Metamodel API defines a structured hierarchy of interfaces and enumerations to represent the attributes of managed persistent types (entities, embeddable and superclasses). Metamodel Attributes Hierarchy in Jakarta Persistence (JPA) 3. Base attribute definitions

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

/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

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

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

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

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

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

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

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

.transaction jta 1.1 javax.servlet servlet- api 2.5 provided javax.servlet.jsp jsp- api 2.1 provided org

;      javax.servlet    servlet- api    2.5    provided        javax.servlet.jsp    jsp- api    2.1    provided

-servlet- api _3.0_spec-1.0.0.Final.jar:1.0.0.Final] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet- api _3.0_spec-1.0.0.Final.jar:1.0.0.Final] at org.apache.catalina.core ... (HttpServlet.java:754) [jboss-servlet- api _3.0_spec-1.0.0.Final.jar:1.0.0.Final] at javax.servlet.http

.UIData.getValue(UIData.java:736) at org.primefaces.component. api .UIData.getDataModel(UIData.java:628) at javax.faces.component.UIData.getRowCount(UIData.java:347) at org.primefaces.component. api ... . api .UIData.getDataModel(UIData.java:628) at javax.faces.component.UIData.getRowCount(UIData.java:347

;are clear selling points. (JPA and JDO APIs versus an elegant proprietary API  is a negative ... , but expectations should remain realistic. Supporting the JPA and JDO APIs is an important selling ... investment that you make in a software that uses ObjectDB is secured by the standard API

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

. This technique is currently in use internally by ObjectDB tests. Not ideal (and obviously dedicated API ... ; may we hope for an Api in some future release ? best regards Arne Arne Arne Stocker An API may be added. There is a plan to support running the Doctor online (against an open database) using an API

.testng.TestNG.run(TestNG.java:1017) at org.gradle. api .internal.tasks.testing.testng.TestNGTestClassProcessor.runTests(TestNGTestClassProcessor.java:140) at org.gradle. api .internal.tasks.testing.testng.TestNGTestClassProcessor.stop(TestNGTestClassProcessor.java:89) at org.gradle. api .internal.tasks

queries for entities with complex relationships, because the metadata  model (MMM) object 

Hello, I got an unpleasant bug which turned into a serious issue. Using ObjectDB 2.6.9.b08 on Linux. Here is the structure (JDO metadata ) of 3 classes which I am storing as values in a HashMap of another entity in the DB.                  

but they are already used through the JDO Metadata file. For instance I use this class: public class MessageImpl

Font size on new site is huge! This is especially a problem when browsing the api .   dmoshal David Moshal Difficult to find info on ODB1, including api javadocs. dmoshal David Moshal Thank ... to browse the API - notice that a version is specified for each interface, method

I was wondering if there is any way to get a list of the entity names in the database? dmoshal David Moshal You can use the Metamodel API as explained by the JPA Metamodel API  page in ... (PersistenceManager.class)); This method remained from ObjectDB 1.x, but in JPA 2 applications the JPA Metamodel API

datasource it requires a SQL driver (confusing a bit!). Anyhow solved this without referring to the API ? I don't want to use the API as I much rather declarative-ly set it up. Thanks Willks William

, but we prefer to avoid introducing our own API , so possibly this can be achieved if a future version of JPA will define a standard API for OSGi integration.   support Support Hello, OK, sounds like a plan. Regards, Alex alexweirig Alex Weirig

on: http://www.objectdb.com/ api /java/jpa/UniqueConstraint Until JPA defines Java object model level ... / @Unique annotations: http://www.objectdb.com/ api /java/jdo/annotations/indexes http://www.objectdb.com

.service(HttpServlet.java:754) [jboss-servlet- api _3.0_spec-1.0.0.Final.jar:1.0.0.Final] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet- api _3.0_spec-1.0.0.Final.jar:1.0.0

parse the data? ezazop Akis Zazopoulos Using Java Reflection API . The JPA Metamodel API may also help. support Support

until the next API change. Other solutions (like adding a special prefix for absolute paths) are not ... , etc.) seems unjustified in this case. That said, there are future plans to extend the backup API and then this issue should be addressed. support Support

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

.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

.agile.hummingbirdcore. API .executeErrorAction( API .java:2940)     at com.agile.hummingbirdcore. API .handleAction( API .java:2418)     at com.agile.hummingbirdcore. API .directRequest( API .java:1621)     at com.agile.hummingbirdcore. API .handleWebSocketRequest( API

.gridservice. api ._WorkflowAdminClientAPIDisp.___query(Unknown Source) at rbccm.felix.gridservice. api ... .gridservice.admin.server.WorkflowAdminClientImpl.query(Unknown Source) at rbccm.felix.gridservice. api ._WorkflowAdminClientAPIDisp.___query(Unknown Source) at rbccm.felix.gridservice. api

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

, cascade=CascadeType.ALL, fetch=FetchType.EAGER) private Map metadata ; ... In this case the "payload

similarly to the XML metadata . Therefore, the name of a sequence that is defined by an annotation