ObjectDB Database Search
51-100 of 200 resultsobjectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check") vs. generic classes with interfaces: detailed investigation objectdb- 2 .6.9_02 (with "objectdb.temp.no-enhancement-crc-check" system property ... there are now obsolete): - Issue #1924 - ObjectDB- 2 .6.9: Failed to commit transaction: Failed ... the system, just for Expert System cases). To make things simpler, this posting will examine only these 2 cases | |
getting "Unexpected total page count" error when diagnosis mu db by ObjectDB doctor..Skill.Campaign.Id=: campid And agsk.Skill.Queue.Channel=:chan" for this query am getting empty result | |
Slave server not getting deletes I have a Master and Slave Server and the slave server is getting the persists, but when I do a delete query, the records don't get deleted "delete from TestTable t " When I insert a record, then delete it, then re-insert it again, the slave server will give this error because the record did not | |
Eclipse - Maven - Dependencies not getting automatically reflected are not getting displayed. Say if I input springframework, it only reflect the jars that installed | |
ID format in objectdb 2.x for JDOHelper.getObjectId for the same object in object db 2 .x, i am getting Object obj = JDOHelper.getObjectId(logTestRunImpl) obj ... Hi, I am trying to upgrade the objectdb from 1.x to 2 .x. I installed and configured as per object ... for a persistable object, i am getting an integer as a result e.g Object obj = JDOHelper.getObjectId | |
Puzzler: Not getting cascades on read from Spring contextPuzzler: Not getting cascades on read from Spring context | |
Low performance when getting grove rootsLow performance when getting grove roots | |
Getting Foreign KeyGetting Foreign Key | |
Query becomes slower on moving from ObjectDB 1.x to ObjectDB 2.x, with object 1.x, the same query was getting executed within an seconds and now the same is taking around 40 seconds in object db 2 .x I have build the query using the follwoing Query query = persistanceManager ... objectdb explorer binitbhaskar Binit Bhaskar ObjectDB 2 .x is usually faster than ObjectDB 1.x | |
after upgrade to 2.9.0 database destroys, urgent issue at our most important customer, production shutdown after upgrading to 2 .9.0 (because of the other problems in former versions), the database destroys ... (if you had schema changes in addition to upgrading to 2 .9.0) . If this is the only issue then running ... the engine that manages the database storage, at least in the last 2 years, so there is nothing in version 2 | |
OutofMemory error with Object DB 2.0 Hi, I am getting the below OutOfMemoryError after I have migrated from objectdb 1.0 to 2 .0 The application works fine with only 256MB heap size with objectdb 1.0 But on 2 .0 even with max heap ... PersistentManager is used to begin the transaction. With objectdb 2 .x do we need to close the  | |
Reading 1.x odb files in ObjectDB 2.x without upgrading db odb file from version 1.x to 2 .x, user is unable to open the odb files in the application which is having object db 1.x installed. Is there any way to read odb files from 1.x in object db 2 .x ... binitbhaskar Binit Bhaskar Old ObjectDB 1.x databases cannot be opened directly by ObjectDB 2 .x | |
Issue with merge in 2.4.3 Hi, we just tried to upgrade to 2 .4.3 from 2 .4. 2 . One of our regression tests is failing. Appears objects are getting created twice on merge. Please see attached unit test. Thanks Paul. pedwards Paul Edwards This regression bug was the result of a bad optimization that is now fixed in build 2 .4.3_01. support Support | |
Source not found error after downloading ObjectDB 2.3.7_04 = pmf.getPersistenceManager(); I am getting an error Source attachment does not contain source for File PMF.class. I had added the zip file jdo_ 2 . 2 .zip as source. Please help need to complete assg in 2 days Pallavi pallavi You have to provide more details. What kind of error is it? Compilation | |
ObjectDB 2.x is working without any activation code. Put the activation code in the objectdb.conf file and again put this conf file in the objectdb.jar 2 . Used other machine (other developers machine) 2 . Enhannced all the persistance class using this jar file 3. Trying to run the application whichi is using Tomcat 7.0 and getting the following exception | |
Apache Tomee 1.5.2: Failed to use JTA (TransactionManager is not found) Hello, ObjectDB team! I am struggling with getting ObjectDB 2 .5.0 to work with clean Apache Tomee 1.5. 2 with transaction-type="JTA". I don't have any configurations in Tomee (objectdb.jar is in Tomee's classpath) nor other parts, excepting the following persistence.xml: com.objectdb.jpa.Provider | |
Help: After upgrading from 2.2.8_02 to 2.2.8_04, can't perform LIKE query 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 | |
Glassfish 3.1.2.1 and ObjectDB 2.4.3 - 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 | |
objectdb explorer in ver 2.2 and 1.0 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 | |
javax.transaction-api-1.3.jar and javax.persistence-api.2.2.jar 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 | |
objectdb:2.8.4 & 2.6.1.b06 backward compatibility 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 version 2.2 has been released 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 | |
ObjectDB JPA 2.2 support ( java.util.stream.Stream | |
version 2.8.9_06 significantly slower for queries compared to 2.8.9.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 | |
each 1-2 days objects on some objectdb level lock/block each other each 1- 2 days we have the situation that our system changes to a completely underperforming mode ... is much more critical, today we switched back to 2 .7.5, but the same behaviour - nothing changed in ... % and around 200 threads hgzwicker Hans-Georg Zwicker According to the subject of this thread it happens every 1- 2 | |
JPA Class Enhancer 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 | |
Eclipse Public License - v 1.0. "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 | |
jakarta.persistence.EntityManager 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 | |
[ObjectDB 2.4.1] Unexpected exception (Error 990) Hi, getting this unexpected exception, would welcome advice: [ObjectDB 2 .4.1] Unexpected exception ... .ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$ 2 .evaluate(ParentRunner ... ; } } A better error message is produced by build 2 .4.1_01. support Support | |
Literals in JPQL and Criteria Queries, -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 | |
version 2.4.5+ with GlassFish 3.1.2, errors when runs application. Version 2.4.4 worked but not 2.4.5 or later 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 | |
jakarta.persistence.Query 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 | |
jakarta.persistence.TypedQuery. 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 | |
jakarta.persistence.StoredProcedureQuery 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 | |
Entity Management Settings 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 | |
jakarta.persistence.criteria.CriteriaBuilder compatible with varags. Since: Jakarta Persistence (JPA) 2 .0 The JPA Criteria API Queries article ... more restriction predicates Returns: and predicate. Since: Jakarta Persistence (JPA) 3. 2 Expression ... . Since: Jakarta Persistence (JPA) 3. 2 Order asc ( Expression expression ) Create an ordering by | |
ObjectDB 2.2.2ObjectDB 2.2.2 | |
queries under 2.7.6_4 significantly slower than under 2.7.6 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 | |
ObjectDB 2.7.2_x Doctor Yields "Index Requires Rebuild" Always 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.  | |
jakarta.persistence.EntityManagerFactory 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 | |
queries more than 10 times slower using 2.8.1 versus 2.7.6 - 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 | |
Regression bug in using version 2.4.5 with GlassFish 3.1.2 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 | |
[ObjectDB 2.2.5_02] Unexpected exception (Error 990) com.objectdb.o.InternalException: java.lang.NullPointerException: null 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 | |
Eclipse/JPA Java EE Tutorial: 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: | |
NetBeans/JPA Java EE Tutorial 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: | |
[ODB1] Chapter 6 - Persistent Objects 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 | |
[ODB1] Chapter 9 - ObjectDB Explorer version to the same installation directory. 9. 2 Browsing the Database The ability ... viewer window (Table or Browser), as discussed in Section 9. 2 . Whether or not to use different | |
[ODB1] Chapter 5 - JDO Connections. 2 javax.jdo.PersistenceManager The javax.jdo.PersistenceManager interface represents ... retries (about 2 seconds) a JDOUserException (a subclass of JDOException ) is thrown. These constants | |
[ODB1] Chapter 4 - JDO Metadata. 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 | |
[ODB1] Chapter 1 - About ObjectDB. 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 |