About change

forum_thread

Beginners questions

Hello !! I am new in JPA / ObjectDB development and I have many questions: 1. If I understood correctly, ObjectDB is an implementation of JPA standard (currently 2.0)? 1.1. Is ObjectDB on the same level like Hibernate with only difference that Hibernate stores the data in a RDBMS and ObjectDB has its own format?   #1 2017-02-10 13:12 Hello !! I am new in JPA / ObjectDB development and I have many questions:   ...

 
release

2.4.0

... bug in using IS NULL in queries on new fields after schema change. Fixed an Explorer bug in using an entity class with ID ... criteria queries. Fixed a bug in collection change tracking in a new entity object. Fixed merging entity ...

 
release

2.3.7

... bug in using IS NULL in queries on new fields after schema change. Fixed an Explorer bug in using an entity class with ID ... criteria queries. Fixed a bug in collection change tracking in a new entity object. Fixed merging entity ...

 
manual

Setting and Tuning of JPA Queries

Explains various JPA query settings - result range, flush and lock. The  Query javax.persistence.Query JPA interface Interface used to control query execution. See JavaDoc Reference Page... and  TypedQuery javax.persistence.TypedQuery JPA interface Inter ...

 
release

2.4.1

... bug in using IS NULL in queries on new fields after schema change. Fixed an Explorer bug in using an entity class with ID ... criteria queries. Fixed a bug in collection change tracking in a new entity object. Fixed merging entity ...

 
manual

Retrieving JPA Entity Objects

Explains how to use JPA to retrieve entity objects from the database.... does not require an active transaction because it does not change the content of the database. The persistence context serves ...

 
release

2.2.6

... criteria queries. Fixed a bug in collection change tracking in a new entity object. Fixed merging entity ...

 
issue

JQL-Update Queries fails with activated L2-Cache

When using JQL-Update Queries it is basically not working without calling entityManager.clear() after a transaction commit. When the clear() method isn't called the entityManager will never return a container the updated Entities. Scenario 1: Disabled L2 Cache, updating elements using UPDATE-Query and fetching Entities afterwards from database. Expected result: Getting changed Entities from database - Actual result: No changes are visble. Bug Version: Priority: Critical Status: Closed Replies: 1 Type:  Bug ...

 
manual

Working with JPA Entity Objects

Explains the entity object lifecycle and the persistence context.... entity object is modified within an active transaction the change is detected by the owning EntityManager and the update is propagated ...

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