ObjectDB Database Search

I executed the following example with ObjectDB 2 .8.7 a few years ago, it worked. But with ObjectDB 2 .9.5_01 it does not work anymore. It works only, if I uncomment the commit() and begin() in ... outerEntity = new MyEntity(); outerEntity.strValue = " outer entity"; outerEm.persist(outerEntity

Hello I get an error when executing the following JPQL query: select doi from Doi doi left join 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

DISTINCT m FROM Person m LEFT OUTER JOIN m.answers answers LEFT OUTER JOIN answers.persons likedPersons ... Following your request we added support for casting boolean to int in build 2 .5. 2 _03 ... version 2 .5. 2 _04. but in the Explorer queries SELECT approveEmail FROM Person ORDER BY (int

Hi,   AFter the upgrade from 2 . 2 .8_02 (not sure if it was build 03/04 as I skipped 03 ... =false) OR ($1.conditionThree=false)))) Exception in thread "main" [ObjectDB 2 . 2 .8_04] Unexpected ... The criteria query AND/OR fix in 2 . 2 .8_04 caused this new problem. Please try build  2 . 2 .8_05

inner join e.person person inner join person.address address left join address.place addressPlace left join address.city addressCity left join address.county addressCounty left join person.birthPlace birthPlace left join person.birthCounty birthCounty left join person.citizenship citizenship left

)" + " from Account acct" + " left outer join AccountTransaction att on acct.id = att.accountId" + " left outer join Transaction trans on att.transactionId = trans.id" + " left outer join AccountGroup ag on acct.accountGroupId = ag.id" + " left outer join AccountType at on at.id = ag.accountType" + " group

the WHERE clause. Try LEFT OUTER JOIN : SELECT a FROM A a LEFT JOIN a.another b WHERE a.another IS NULL OR b ... Hello, I'm struggeling to get a query run right. I have 2 entities (simplified) class A {   ... A other; } so entity B is the owner. Now I persisted 2 entities of type A. In the first one, the member

- The requested resource () is not available. I tried it on Glassfish server 3.1. 2 and 3.1. 2 . 2 . Sometimes I ... INFO: Running GlassFish Version: GlassFish Server Open Source Edition 3.1. 2 (build 23) INFO: Grizzly ... : Created HTTP listener [http-listener- 2 ] on host/port [0.0.0.0:8181] INFO: WEB0169: Created HTTP

that object explorer has lower functionality than in ver 2 . 2 eg garbarage collector or xml import ... You are right - some important features of ObjectDB 1.0 Explorer are not implemented yet in ObjectDB 2 . 2 . This is because ObjectDB 2 was written almost from scratch and the old Explorer does not match

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.persistence-api. 2 . 2 .jar ships with the zip file, but this has also moved to jakarta, and is now

We are decided to move our products from 2 .6.1.b06 to 2 .8.4, could you confirm that new objectDb 2 .8.4 is fully compatible with many already created databases based on 2 .6.1? So, it means that we need to be sure that new objectDb 2 .8.4 could read/write to databases created by 2 .6.1. Please confirm

ObjectDB 2 . 2 has been released and it includes important additions and fixes: Added full support of JPA 2 Criteria Queries API ( issue #10 ) Added full support of JPA 2 Metamodel API ( issue #9 ... the ObjectDB Doctor of version 2 . 2 in repair mode on existing database files, and to switch to the new

Hi , in my database i want to fetch resultlist as big chunks.JPA 2 . 2 has new feature named Stream ... objectdb for JPA 2 . 2 ?  eix128 Kadir BAŞOL We hope to support this feature soon ... , similarly to the way that JPA 2 . 2 streams work. To free memory, however you will have to clear

.objectdb.com/forum/2845 for queries we are using hgzpincher Hans-Georg Zwicker Version 2 .8.9_01 ... in version 2 .8.9_02 but maybe there is another relevant query performance regression that has not been fixed. Changes in versions 2 .8.9_03 - 2 .8.9_06 are not expected to affect queries. An attempt

updated ObjectDB from 2 .5.6.x to 2 .5.7_03. Maybe this will save someone a bit of time and effort. - Ron AlphaOne Ron Brennan Actually build 2 .5.6 should also support Java 8 ... . But maybe build  2 .5.7_03 is somehow better for Java 8. Thanks for the report. support Support

In earlier versions this query worked fine. In version 2 .5. 2 _05 does not work .orderBy(cb.desc(cb.greatest(root.get("createDate").as(Date.class)))).distinct(true) Thank you for your help. galandor Orlov Sergey Please try build 2 .5. 2 _06 that should fix this regression (of casting to Date ). support Support

Jakarta Persistence (JPA) Enum Constant in jakarta.persistence.criteria.JoinType RIGHT Right outer join. Since: Jakarta Persistence (JPA) 1.0

line: ObjectDB Enhancer [version 2 .9.4] Copyright (c) 2025, ObjectDB Software. All rights reserved ... lists the classes that have been enhanced: [ObjectDB 2 .9.4] 3 persistable types have been enhanced: test.MyEntity1 test.MyEntity2 test.MyEmbeddable 2 NON persistable types have been enhanced: Main test

. "Recipient" means anyone who receives the Program under this Agreement, including all Contributors. 2 ... such Recipient's patent(s), then such Recipient's rights granted under Section 2 (b) shall terminate as ... its Contributions) under the new version. Except as expressly stated in Sections 2 (a) and 2 (b

Exception thrown by ConnectionFunction.apply , if any. Since: Jakarta Persistence (JPA) 3. 2 void ... of entity graph Returns: entity graph. Since: Jakarta Persistence (JPA) 2 .1 EntityGraph ... graph. Since: Jakarta Persistence (JPA) 2 .1 Query createNamedQuery ( String name ) Create an instance

Added support of editing enum values in the Explorer. Added logging of type registration . Added error message when using mapped by (inverse) collections and maps of invalid types. Changed JOIN FETCH to act as LEFT JOIN in path expressions. Updated the PDF manual. Fixed a possible deadlock

, -127L, 0L, 07777L float : 3.14F, 0f, 1e2f, - 2 .f, 5.04e+17f double : 3.14, 0d, 1e2D, - 2 ., 5.04e+17 ... . literal (1); Expression i2 = cb. literal (Integer.ValueOf( 2 )); Expression d = cb. literal (3.4

All latest versions later 2 .4.5+ even 2 .4.5_05 doesn't work, it deployed but errors when running. But 2 .4.4 worked javax.ejb.EJBException at com.sun.ejb.containers.BaseContainer ... Luc Have you tried 2 .4.5 or 2 .4.5_03? Because 2 .4.5_03 fixes a GlassFish integration issue . support

that will be in effect during query execution. Since: Jakarta Persistence (JPA) 3. 2 CacheStoreMode ... . Since: Jakarta Persistence (JPA) 3. 2 int getFirstResult () The position of the first result the query object ... : position of the first result. Since: Jakarta Persistence (JPA) 2 .0 The Running JPA Queries article

#23 server] [ObjectDB 2 . 2 .8] Unexpected exception (Error 990) Generated by Java HotSpot(TM) 64-Bit Server VM 1.5.0_21 (on Windows 2003 5. 2 ). Please report this error on http://www.objectdb.com/database ... : Java heap space The server manages 2 "queue" databases used for communication between processes

. See Also: Query Parameter Since: Jakarta Persistence (JPA) 2 .0 Chapter 4 - JPA Queries (JPQL / Criteria ... effect during query execution. Inherited from Query Since: Jakarta Persistence (JPA) 3. 2 CacheStoreMode ... . Inherited from Query Since: Jakarta Persistence (JPA) 3. 2 int getFirstResult () The position of the first

Since: Jakarta Persistence (JPA) 2 .1 Public Instance Methods boolean execute () Return true if the first ... . 2 CacheStoreMode getCacheStoreMode () The cache storage mode that will be in effect during query execution. Inherited from Query Since: Jakarta Persistence (JPA) 3. 2 int getFirstResult () The position

attribute specifies the size of the shared level- 2 cache that is managed by the EntityManagerFactory and shared by all its EntityManager instances. To disable the level- 2 cache, specify 0 or 0mb

order. The left -to-right sequence of the ordering expressions determines the precedence

ObjectDB 2.2.2

through null in one of the OR components. Navigation should be compiled as LEFT OUTER JOIN to avoid losing ... ] Evaluate fields in IndividualContact ($1) instances. Step 2 : Process OrganisationContact (v$1 ... ) instances. Step 2 : Process OrganisationContact (v$1) instances   (for every result of step 1

.individual.IndividualContact $1 LEFT JOIN $1.profile $ 2 WHERE ((TYPE($1)=class com.quasado.foundation ... DISTINCT $1 FROM com.quasado.foundation.contact.individual.IndividualContact $1 LEFT JOIN $1.profile $ 2 ... : SELECT DISTINCT $1 FROM IndividualContact $1 LEFT JOIN $1.profile $ 2 ORDER BY UPPER($ 2 .lastName) By

graph entityGraph - entity graph Since: Jakarta Persistence (JPA) 2 .1 void addNamedQuery ( String ... (JPA) 2 .1 R callInTransaction ( Function work ) Create a new application-managed EntityManager ... . 2 void close () Close the factory, releasing any resources that it holds. After a factory instance

we update to the latest version from 2 .7.6. Now we have the problem that we have numerous logs ... since version 2 .7.6 that could possibly effect query execution. Could you please explain or post some of these logs that show deep query plan checks (and are new in 2 .7.6_04)? In addition

Take a .odb created with ObjectDB 2 .7. 2 or later OR EARLIER.  Run ObjectDB 2 .7. 2 Doctor on it.  See indexing errors reported. Run ObjectDB 2 .7.1 on same .odb and you will not see indexing errors. Run ObjectDB 2 .7. 2 (or later or earlier) Doctor with repair and create repaired.odb. 

Hi, We are preparing to upgrade our database servers and application dependencies from 2 .6.9_04 to 2 .7.6.  The desired path was to upgrade the database servers to 2 .7.6 first, followed by ... path? Thanks,  Clinton CAPdev CAP Dev the desired path was to upgrade the database servers to 2 .7

- we restarted to try to use 2 .8.1 instead of 2 .7.6 - we did a doctor on the database ... in 2 .7.6 around 5-10 seconds takes in 2 .8.1 around 150-200 seconds: SELECT DISTINCT o.parentNode ... . It seems that running your query on your sample database with version 2 .8.1 is slower

Hello, we have an issue with following query which needs with objectdb- 2 .7.6_07 only 15 - 30 milli seconds, but since objectdb- 2 .7.6_08 the query needs round about 3000 ms. I added a database example in a ticket. SELECT a FROM ArtifactImpl a LEFT OUTER JOIN a.tcSignal s WHERE a.endStep.stepNumber = 2000 AND a.startStep.stepNumber

Can't deploy objectDB ver 2 .4.5 or later using GlassFish 3.1. 2 , NetBeans 7. 2 .1 Win 7 & 8. ObjectDB Version 2 .4.4 is working good. [#|2012-12-18T05:26:53.167-0800|SEVERE|glassfish3.1. 2 |javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=44;_ThreadName=Thread- 2 ;|java.lang

reporting issue as requested  [ObjectDB 2 . 2 .5_02] Unexpected exception (Error 990) Generated ... you for your report. Build 2 . 2 .5_09 should fix this NullPointerException . support Support Thank you for a quick turnaround. I can confirm it fixed using Build 2 . 2 .5_10 longpat Brian O'Hare

I was experiencing an exception so I did a test to reproduce it.   here it is. [ObjectDB 2 . 2 .6_02] Unexpected exception (Error 990) Generated by Java HotSpot(TM) Client VM 1.6.0_17 (on Windows ... O'Hare Thank you for your report and for the test. Please try build 2 . 2 .6_03 that should fix this exception. support Support

= x :     (0, 0), (1, 1), ( 2 , 2 ), ..., (999, 999) The BIRT report

: ObjectDB 2 .3.7_04 or later is required if Glassfish 3.1. 2 (or later) is used. The Tutorial Steps This tutorial consists of the following steps:

and menus might look slightly different but the code would be the same). Note: ObjectDB 2 .3.7_04 or later is required if Glassfish 3.1. 2 (or later) is used. The Tutorial Steps This tutorial consists of the following steps:

of persistent types is available at section 3. 2 ). ObjectDB provides an additional storing method ... (an embedded object can only be retrieved using a reference from its containing object). 6. 2   ... of the first object in the database is always 1, the ID of the second object is 2

mode are discussed in Section 1. 2 . Because the JDO API and the format of the database file ... is listening for new connections is specified in the configuration file (as explained in section 8. 2 ... to manage the server (stop, restart and start), and to exit the application. 8. 2   Single User

). 3. 2   Persistent Fields and Types Storing a persistent object in the database does not ... of any of the persistent types defined above in the database (as demonstrated in section 2 .1 ... /*.class [ObjectDB Enhancer] 2 new persistence capable classes have been enhanced. [ObjectDB Enhancer] 1

. 2   javax.jdo.PersistenceManager The javax.jdo.PersistenceManager interface represents ... retries (about 2 seconds) a JDOUserException (a subclass of JDOException ) is thrown. These constants

. Therefore, only the first metadata for a class in the search order specified above has effect. 4. 2    ... for determining if a field is persistent are explained in section 3. 2 . The persistence-modifier

. It has a small footprint, high performance, and a flexible architecture (1-Tier, 2 -Tier or N-Tier). 1 ... developing software without a debugger. 1. 2   ObjectDB Operating Modes ObjectDB for Java/JDO