About relation

manual

Locking in JPA

Explains how to use optimistic locking and pessimistic locking in JPA. JPA 2 supports both optimistic locking and pessimistic locking . Locking is essential to avoid update collisions resulting from simultaneous updates to the same data by two concurrent users. Locking in ObjectDB (and in JPA) is always at the da ...

 
manual

[ODB1] Chapter 3 - Persistent Classes

Explains what a persistence capable class is and which types are supported by JDO. Persistent Classes are user defined classes whose instances can be stored in a database using JDO. Instances of these classes that represent objects in the database are called persistent objects or persistent instances . Objects that do not repre ...

 
issue

Internal Exception and Index Problems

Dear Support Team, we have an urgent issue in a productive database. The objectdb doctor finds no error but one string field of one database item is not editable (even not using the objectdb explorer). The corrupt entry is in entity "UserModelData" with id="7d29d5eb-69a6-4d46-9bf1-802cbb6e439b". Try to change the userName attribute of this entry then the following error occurs: Bug Version: 2.5.3 Priority: High Status: Active Replies: 8 Type:  Bug ...

 
issue

InternalException - error reading field from "queue" database

I trying to use an objectdb database as a persitent queue but have started getting the following error on the receiver side: Bug Version: 2.2.8 Priority: Normal Status: Closed Replies: 6 Type:  Bug ...

 
forum_thread

Upgrade to Java 8 won't run

I've been using ObjectDB with Groovy 2.1 and Java 7 for nearly a year.  Today, I updated everything to the latest revs (Groovy 2.3.6, Java 1.8.0_25, and ObjectDB 2.5.7_05), and now my application fails when opening the database. It's dying on one of these lines:   emf = Persistence.createEntityManagerFactory (dbName)   em = emf.createEntityManager()   em.setFlushMode(FlushModeType.AUTO)   ObjectDB.em = em   #1 2014-11-16 20:44 I've been using ObjectDB with Groovy 2.1 and Java 7 for nearly a year.  Today, I updated everything to t ...

 
manual

FROM clause (JPQL / Criteria API)

Explains how to use the FROM clause and JOIN expressions in a JPA/JPQL query. The FROM clause declares query identification variables that represent iteration over objects in the database. A query identification variable is similar to a variable of a Java enhanced for loop in a program, since both are used for iteration over o ...

 
issue

Error in production. Failed to commit transaction: Unexpected database state: BTree -152 is not found

2014-06-16 11:52:26,684 ERROR cl.intelidata.servlet.Fact .respondeRut (122 ): Unexpected internal exception [ObjectDB 2.5.5] Unexpected exception (Error 990) Generated by OpenJDK 64-Bit Server VM 1.7.0_25 (on Linux 3.11.0-12-generic). Please report this error on http://www.objectdb.com/database/issue/new com.objectdb.o.InternalException: java.lang.NullPointerException: null java.lang.NullPointerException Bug Version: 2.5.5 Priority: Normal Status: Active Replies: 1 Type:  Bug ...

 
manual

JPA Entity Fields

Explains how to define and use primary keys in JPA, including composite and embedded primary keys. Fields of persistable user defined classes (entity classes, embeddable classes and mapped superclasses) can be classified into the following five groups: Transient fields Persistent fields Inverse (Mapped By ...

 
forum_thread

ObjectDB within a resource adapter module and Java EE Connector Architecture

Has anybody managed to use ObjectDB in a resource adapter module in accordance with the Java EE Connector Architecture so that it may be packaged separately from (but used by components of) an EJB Module after the pattern of the classic EAR File structure as illustrated in the Java EE 7 tutorial in Figure 5-1 EAR File Structure ? #1 2016-11-19 11:19 Has anybody managed to use ObjectDB in a resource adapter module in accordance with the Java EE Connector Ar ...

 
issue

NullpointerException at a normal select

When I run the following code: EntityManager em = getEm(); Customer result = null; try {     logger.debug("Ident: "+ident);     result = em.createQuery("Select c from Customer c where c.identifier=:id", Customer.class).setParameter("id", ident).getSingleResult(); } catch (javax.persistence.NoResultException nre) { } finally {      em.close(); } I get the following error (you can also see the log message containing the String parameter at the top): Bug Version: 2.5.6 Priority: Normal Status: Active Replies: 1 Type:  Bug ...