ObjectDB Database Search
51-100 of 200 resultsIssue deploying J6EE/Eclipse/Glassfish example to TomEE 1.5.1Issue deploying J6EE/Eclipse/Glassfish example to TomEE 1.5.1 | |
Number of current connections Is there any way to find out the number of current connections to the DB server? natmaclin Natalia Levine Currently not. You may subscribe to this feature request and update it according to your needs. support Support | |
Is there an API to get the current version of ObjectDB that's being used? 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 | |
JBoss 7.1 and EAP 6 support I understand that keeping up with a new version can be difficult. Having said that, JBoss 7. 1 . 1 ... version by RedHat which is based on 7. 1 , has been released recently. I would really like to use ... with JBoss 7. 1 . 1 but was unable to get it to deploy. I also tried the recent releases of ObjectDB | |
Upgrade to 2.4.1_01 Hi, We tried to upgrade from 2.3.7_18 to 2.4. 1 _01 to pickup some fixes. We discovered that our code no longer works when using 2.4. 1 _01. We did some probing and found one thing. I have attached ... with 2.4. 1 _01, with each giving a different error. @Embedded gives: [ObjectDB 2.4. 1 _01] javax | |
Upgrade to 2.4.1_03 Right, that fix to 2.4. 1 _02 got us past the previous issue. Now I'm not sure ... is: [ObjectDB 2.4. 1 _03] javax.persistence.PersistenceException Failed to clear field property com ... .FrameworkMethod$ 1 .runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model | |
Unable to convert 1.x odb file to 2.x Hi, my company is just about to switch from ObjectDB 1 .04.2487 (SE) to ObjectDB 2. So I ... well, but then on converting 1 of the DB files I got this error: java -jar converter.jar ../old.odb ../new.odb ObjectDB 1 .0 ... . Output of conversion: ObjectDB 1 .0 - 2.0 file conversion | |
Upgrade to 2.4.1_02 Hi there, The upgrade to 2.4. 1 _02 fixed the initial problem ... Sorry forgot the stack trace: [ObjectDB 2.4. 1 _02] javax.persistence.PersistenceException Failed ... ) at org.junit.runners.model.FrameworkMethod$ 1 .runReflectiveCall(FrameworkMethod.java:44) at org.junit | |
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 | |
javax.transaction-api-1.3.jar and javax.persistence-api.2.2.jar Hi, I notice that objectdb zip file has: javax.transaction-api- 1 .3.jar However that library 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 | |
objectdb explorer in ver 2.2 and 1.0 You are right - some important features of ObjectDB 1 .0 Explorer are not implemented yet in ObjectDB 2.2 ... to the Explorer in future versions. Support of ObjectDB 1 .x is now limited, so new application should only use ObjectDB 2.x. Notice that ObjectDB 2.x also supports JDO better (JDO 2 instead of JDO 1 ). support Support | |
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 ... application failed: C:\Users\Mircea\Documents\NetBeansProjects\natural7\target\natural7- 1 .0-SNAPSHOT | |
ObjectDB version 2.1 has been released ObjectDB 2. 1 has been released and it includes important additions and fixes: Added Online Backup utility ( issue #16 ). Added Master-Slave Replication / Clustering (issue #17 ). Added a PDF version of the ObjectDB manual (included in the download). Added sample (tutorials) Maven projects | |
Verify Error with Java 1.7 ObjectDB enhanced classes fail when compiled to Java 1 .7 [ObjectDB 2.2.9_08 Enhancer] 28 persistable types have been enhanced: ... com.vaisala.jx.db.gdm.model.SourceType stack trace from jUnit test com.vaisala.jx.db.gdm.facade.BaseFacadeTest Time elapsed: 0 sec | |
javax.transaction.Synchronization with Java SE 10.0.1 (using Java SE 10.0. 1 ). So I tried to track down why it is not found via runtime and discovered | |
ObjectDB Unable to process 1.6 L records. Hi I have a db of around 1 .6 lakh records. But now am getting some unexpected error when accessing some of the entities. And when am fetching all the records using objectdb explorer its showing exception. I have diagnosis the db with objectdb doctor but not find any error. Please check | |
ObjectDB 2.1.1ObjectDB 2.1.1 | |
jakarta.persistence.EntityTransaction (JPA) 1 .0 void commit () Commit the current resource transaction, writing any unflushed changes ... the EntityTransaction interface. Since: Jakarta Persistence (JPA) 1 .0 The JPA Connections ... - if the commit fails. Since: Jakarta Persistence (JPA) 1 .0 boolean getRollbackOnly () Determine | |
jakarta.persistence.criteria.MapJoin Selection Parameters: name - alias Returns: selection item. Since: Jakarta Persistence (JPA) 1 .0 ... Persistence (JPA) 1 .0 Expression cast ( Class type ) Cast this expression to the specified type ... Persistence (JPA) 1 .0 Predicate equalTo ( Expression value ) Create a predicate to test | |
jakarta.persistence.criteria.ListJoin - alias Returns: selection item. Since: Jakarta Persistence (JPA) 1 .0 Expression as ( Class type ) Perform ... : new expression of the given type. See Also: .cast(Class) Since: Jakarta Persistence (JPA) 1 .0 ... . Since: Jakarta Persistence (JPA) 1 .0 Fetch fetch ( SingularAttribute attribute , JoinType jt ) Create | |
jakarta.persistence.OptimisticLockException may be thrown as part of an API call, a flush or at commit time. The current transaction, if one is active ... .lock(Object, LockModeType, java.util.Map) Since: Jakarta Persistence (JPA) 1 .0 Public Constructors ... its detail message. Since: Jakarta Persistence (JPA) 1 .0 OptimisticLockException ( String message | |
jakarta.persistence.PersistenceContext EntityManager and its associated persistence context. Since: Jakarta Persistence (JPA) 1 .0 Annotation ... Persistence (JPA) 1 .0 String unitName (Optional) The name of the persistence unit as defined in ... that is accessible in JNDI must have the same name. Default: "" Since: Jakarta Persistence (JPA) 1 .0 | |
jakarta.persistence.criteria.PluralJoin Returns: selection item. Since: Jakarta Persistence (JPA) 1 .0 Expression as ( Class type ) Perform ... expression of the given type. See Also: .cast(Class) Since: Jakarta Persistence (JPA) 1 .0 Expression cast ... Persistence (JPA) 1 .0 Fetch fetch ( SingularAttribute attribute , JoinType jt ) Create a fetch join | |
jakarta.persistence.criteria.SetJoin Returns: selection item. Since: Jakarta Persistence (JPA) 1 .0 Expression as ( Class type ) Perform ... expression of the given type. See Also: .cast(Class) Since: Jakarta Persistence (JPA) 1 .0 Expression ... . Since: Jakarta Persistence (JPA) 1 .0 Fetch fetch ( SingularAttribute attribute , JoinType jt ) Create a fetch | |
jakarta.persistence.criteria.CollectionJoin Parameters: name - alias Returns: selection item. Since: Jakarta Persistence (JPA) 1 .0 Expression ... Persistence (JPA) 1 .0 Expression cast ( Class type ) Cast this expression to the specified type, returning ... : the resulting fetch join. Since: Jakarta Persistence (JPA) 1 .0 Fetch fetch ( SingularAttribute attribute | |
jakarta.persistence.criteria.Join Selection Parameters: name - alias Returns: selection item. Since: Jakarta Persistence (JPA) 1 .0 Expression ... Persistence (JPA) 1 .0 Expression cast ( Class type ) Cast this expression to the specified type ... : the resulting fetch join. Since: Jakarta Persistence (JPA) 1 .0 Fetch fetch ( SingularAttribute attribute | |
jakarta.persistence.PessimisticLockException may be thrown as part of an API call, a flush or at commit time. The current transaction, if one is active ... . Since: Jakarta Persistence (JPA) 1 .0 PessimisticLockException ( String message ) Constructs a new ... . Since: Jakarta Persistence (JPA) 1 .0 PessimisticLockException ( String message , Throwable cause | |
jakarta.persistence.LockTimeoutException. The current transaction, if one is active, will be not be marked for rollback. Since: Jakarta Persistence ... exception with null as its detail message. Since: Jakarta Persistence (JPA) 1 .0 LockTimeoutException ... . Parameters: message - the detail message. Since: Jakarta Persistence (JPA) 1 .0 LockTimeoutException | |
jakarta.persistence.QueryTimeoutException the persistence provider when a query times out and only the statement is rolled back. The current ... with null as its detail message. Since: Jakarta Persistence (JPA) 1 .0 QueryTimeoutException ( String ... . Parameters: message - the detail message. Since: Jakarta Persistence (JPA) 1 .0 QueryTimeoutException | |
jakarta.persistence.SynchronizationType joined to the current transaction Since: Jakarta Persistence (JPA) 1 .0 Synthetic Public Static Methods ... with the current transaction or whether the persistence context must be explicitly joined to the current transaction by means of the EntityManager.joinTransaction method. Since: Jakarta Persistence (JPA) 2. 1 | |
jakarta.persistence.EntityExistsException. The current transaction, if one is active, will be marked for rollback. If the entity already exists ... the EntityExistsException or another PersistenceException may be thrown at flush or commit time. The current transaction ... . See Also: EntityManager.persist(Object) Since: Jakarta Persistence (JPA) 1 .0 Public Constructors | |
jakarta.persistence.criteria.Root Selection Parameters: name - alias Returns: selection item. Since: Jakarta Persistence (JPA) 1 .0 ... Persistence (JPA) 1 .0 Expression cast ( Class type ) Cast this expression to the specified type ... : the resulting fetch join. Since: Jakarta Persistence (JPA) 1 .0 Fetch fetch ( SingularAttribute | |
jakarta.persistence.criteria.From. Since: Jakarta Persistence (JPA) 1 .0 Expression as ( Class type ) Perform a typecast ... type. See Also: .cast(Class) Since: Jakarta Persistence (JPA) 1 .0 Expression cast ( Class type ... ) 1 .0 Fetch fetch ( SingularAttribute attribute , JoinType jt ) Create a fetch join to the specified | |
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 ... .linkedObjects.objectNameUpper = "ORG" and o.linkedObjects.type = 1 and o.linkedObjects.state = 0 | |
[ObjectDB 2.4.1] Unexpected exception (Error 990) Hi, getting this unexpected exception, would welcome advice: [ObjectDB 2.4. 1 ] Unexpected exception (Error 990) Generated by Java HotSpot(TM) Client VM 1 .6.0_29 (on Windows 7 6. 1 ... .runners.model.FrameworkMethod$ 1 .runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners | |
ArrayIndexOutOfBoundsException: -1 I've attached a test which fails with the error "ArrayIndexOutOfBoundsException: - 1 ". It runs 10 ... . I'm running with 64bit JVM 1 .6.0_30 on windows 7 The first thread to fail output the following stacktrace: java.lang.ArrayIndexOutOfBoundsException: - 1 at com.objectdb.o.HTB.t(HTB.java:448) at com | |
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 ... . (PersistenceUnitLoader.java:120) at org.glassfish.persistence.jpa.JPADeployer$ 1 .visitPUD(JPADeployer.java:224 | |
[ObjectDB 2.5.1_05] Unexpected exception (Error 990) I have this error in log. The query can't return result. Thanks for help. LOG: [ObjectDB 2.5. 1 _05] Unexpected exception (Error 990) Generated by Java HotSpot(TM) Server VM 1 .7.0_55 (on Windows Server 2008 R2 6. 1 ). Please report this error on http://www.objectdb.com/database/issue/new com.objectdb | |
[ObjectDB 2.8.1] Unexpected exception (Error 990) [ObjectDB 2.8. 1 ] Unexpected exception (Error 990) Generated by OpenJDK 64-Bit Server VM 1 .8.0_212 (on Linux 5.0.0-27-generic). Please report this error on http://www.objectdb.com/issue/new com ... .persist(EMImpl.java:415) at javax.persistence.EntityManager$persist$ 1 .call(Unknown Source) at org | |
[ObjectDB 2.4.1] Unexpected exception (Error 990) on getObjectById In this code: String id = "my key"; ABC itemDb = pm.getObjectById(ABC.class, id); I get this: [ObjectDB 2.4. 1 ] Unexpected exception (Error 990) Generated by Java HotSpot(TM) Client VM 1 .6.0_29 (on Windows 7 6. 1 ). Please report this error on http://www.objectdb.com/database/issue/new com.objectdb.o | |
JDOQL Subqueries (JDO 2.1) Subqueries (nested queries) have been added to JDOQL (JDO Query Language) in JDO 2. 1 . This is the main feature of JDO 2.0-2. 1 -2.2 that is not implemented yet in ObjectDB 2. support Support | |
query only reports 1 result 2.7.2_01 suddenly some queries do only have 1 result even there are more results (you can use the database that you have from #308): this query gives 1 result even there are a lot more: select o from ObjectNode o where o.classIdentifier = '(OP)' and o.state = 98 and o.type = 0 and o | |
ObjectDB 2.2.1 Added support for using ObjectDB with JBoss AS 6.0 / 6. 1 . Fixed several bugs in handling eager fetch. Fixed a pessimistic locking bug . Fixed a bug in using primary key fields in queries. Fixed a bug in queries on deleted objects before commit / flush. | |
Typo in ObjectDB 1.0 Manual Support Knowledge Base ObjectDB 1 .0 Manual Chapter 7 "JDOQL Queries" Section 7.2 "Query Filter Syntax" Subsection "Fields" Second to last sentence Remove "not" from that sentence. "An attempt to access a field or invoke a method using a null reference results in a false evaluation | |
ObjectDB 2.5.1ObjectDB 2.5.1 | |
ObjectDB 2.9.1ObjectDB 2.9.1 | |
ObjectDB 2.6.1ObjectDB 2.6.1 | |
ObjectDB 2.3.1ObjectDB 2.3.1 | |
[ODB1] Chapter 8 - ObjectDB Server mode are discussed in Section 1 .2 . Because the JDO API and the format of the database file ... the connection URL string. 8. 1 Running an ObjectDB Server The ObjectDB server is a pure Java ... in the url connection string (as explained in section 5. 1 ) when connecting to the database | |
[ODB1] Chapter 3 - Persistent Classes . The JDO specification refers to persistent classes as persistence capable classes . 3. 1   ... of any of the persistent types defined above in the database (as demonstrated in section 2. 1 ... ObjectDB JDO Enhancer - Version 1 .00 Copyright (C) ObjectDB Software 2003. All rights reserved. Usage |