ObjectDB Database Search

101-150 of 200 results

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 ... query.execute(param1, param2); This takes 1 second to execute using objectdb1.x, but the same takes ... objectdb explorer binitbhaskar Binit Bhaskar ObjectDB 2.x is usually faster than ObjectDB 1 .x

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

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

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

Is persistence version 2.1 supported?

.sax.SAXParseException; lineNumber: 10; columnNumber: 135; cvc-elt. 1 : Cannot find the declaration ... .createEntityManagerFactory(Persistence.java:54) but reverting to version 1 .0 makes the error go away.     freddieFishCake Jonathan Lister Thank you for this report. Support of JPA 2. 1 format

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

JVM crash when using IBM JDK 1.6.0

The FAQ states in the system requirements only that a JDK/JRE 1 .5 or 1 .6(prefered) is required. When I try to use the IBM JDK 1 .6.0 I get a GPF exception while creating the entity manager. Looks like a call to putInt on sun.misc.Unsafe object Does this mean there is a BUG in the IBM JDK or are not

JPA 2.1 and AttributeConverter

Hello :-). Are there any plans to support JPA 2. 1 ? I would wish to have a support for @AttributeConverter. Bot01 Frantisek Novak The general plan is to support future versions of JPA so probably JPA 2. 1 features will also be supported. support Support Thanks for the answer. And is there current

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

License Key on macOS Sequoia 15.6.1

Regarding the  OEM license I've another issue: I've updated my macbook to the latest version of macos Sequioa 15.6. 1 (24G90). Unfortunately since then the mac-id behavior drives me crazy (*). If I create a new activation code for my objectdb.conf it will be valid sometimes for 2 hours

jakarta.persistence.MapKeyJoinColumn.name

upon the context . If the join is for a map key for an element collection, the foreign key column is in ... of the referencing relationship property or field of the referencing entity or embeddable class; " _ "; " KEY ". Since: Jakarta Persistence (JPA) 1 .0

jakarta.persistence.EntityManager.remove(Object)

the database when the persistence context is synchronized with the database. This operation cascades ... - if invoked on a container-managed entity manager of type PersistenceContextType.TRANSACTION and there is no transaction. Since: Jakarta Persistence (JPA) 1 .0

jakarta.persistence.EntityManager.find(Class,Object)

of the specified class and primary key. If the entity instance is contained in the persistence context ... for that entity's primary key or is null. Since: Jakarta Persistence (JPA) 1 .0

jakarta.persistence.EntityManager.flush()

Jakarta Persistence (JPA) Method in jakarta.persistence.EntityManager void flush() Synchronize changes held in the persistence context to the underlying database. Throws: PersistenceException ... has not been joined to the current transaction. Since: Jakarta Persistence (JPA) 1 .0

jakarta.persistence.Query.executeUpdate()

context has not been joined to the transaction. QueryTimeoutException - if the statement execution exceeds the query timeout value set and only the statement is rolled back. Since: Jakarta Persistence (JPA) 1 .0

jakarta.persistence.Query.getResultList()

other than NONE has been set and there is no transaction or the persistence context has not been joined ... and only the statement is rolled back. Since: Jakarta Persistence (JPA) 1 .0

jakarta.persistence.Query.getSingleResult()

and there is no transaction or the persistence context has not been joined to the transaction. Since: Jakarta Persistence (JPA) 1 .0

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

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 ... % and around 200 threads hgzwicker Hans-Georg Zwicker According to the subject of this thread it happens every 1 -2 ... = 1 and c1.state = 0) or (c1.classIdentifier = '(TC)' and c1.objectNameUpper = 'CAM-ELECTRODES' and c1

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

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

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

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

New Java 8 (JDK 1.8) Collection Methods

ObjectDB version 2.5.5 (and above) supports Java 8 (JDK 1 .8). Tracking changes to collections and maps using some new Java 8 methods is currently not fully supported. The main known issue is that orphan removal does not happen as a result of removing a reference to an object

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

ObjectDB 2.5.1

JPQL Subqueries (JPA 1.0)

JPQL Subqueries (JPA 1.0)

ObjectDB 2.9.1

ObjectDB 2.9.1

ObjectDB 2.6.1

ObjectDB 2.6.1

ObjectDB 2.3.1

ObjectDB 2.3.1