About API

release

2.6.9

... conflict (missing synchronization) in the JPA metamodel API. Fixed implementation of casting ( as ) in criteria ... in listing inherited persistent fields (in the Metamodel API and in the Explorer). Fixed a bug in merging complex object ...

 
release

2.5.0

... in listing inherited persistent fields (in the Metamodel API and in the Explorer). Fixed a bug in merging complex object ... JOIN FETCH with DISTINCT. Fixed Metamodel API's getTypeId  method to support single ID field . ...

 
release

2.3.6

... JOIN FETCH with DISTINCT. Fixed Metamodel API's getTypeId  method to support single ID field . ... Added full support of JPA 2 Criteria Queries API ( issue #9 ) Added full support of JPA 2 Metamodel ...

 
issue

ObjectDB 2 JDO Manual

The new ObjectDB Manual describes how to use ObjectDB 2 with JPA. An additional manual that focuses on using ObjectDB 2 with JDO can help JDO users. But since writing a new manual and then maintaining two similar manuals, one for JPA and the other for JDO requires sufficient effort, this will be done only if there is sufficient demand.  ... so there is no particular advantage in moving from db4o API to JDO rather than to JPA. JPA is much more popular than JDO these ... all seen on the Web concluding that JDO is a superior API for object databases. I am not however, married to JDO, although I ...

 
release

2.6.8

... conflict (missing synchronization) in the JPA metamodel API. Fixed implementation of casting ( as ) in criteria ... in listing inherited persistent fields (in the Metamodel API and in the Explorer). Fixed a bug in merging complex object ...

 
release

2.3.5

... JOIN FETCH with DISTINCT. Fixed Metamodel API's getTypeId  method to support single ID field . ... Added full support of JPA 2 Criteria Queries API ( issue #9 ) Added full support of JPA 2 Metamodel ...

 
release

2.4.7

... in listing inherited persistent fields (in the Metamodel API and in the Explorer). Fixed a bug in merging complex object ... JOIN FETCH with DISTINCT. Fixed Metamodel API's getTypeId  method to support single ID field . ...

 
release

2.6.7

... conflict (missing synchronization) in the JPA metamodel API. Fixed implementation of casting ( as ) in criteria ... in listing inherited persistent fields (in the Metamodel API and in the Explorer). Fixed a bug in merging complex object ...

 
forum_thread

Updating existing persistence entries

I have stored some instances of MyObject via em.persist(myObjectInstance); I can fetch them and bind them to a kind of property editor in my app (it simply calls the setters to reflect gui editing actions). When I try to persist a object later on, I get an error like com.objectdb.o.UserException: Attempt to reuse an existing primary key value which makes sense to me but I'm missing a em.update() method. ... you mentioned (from the knowledge base) describes the JDO API. It is still supported but only when using JDO rather than JPA. You ... and ObjectDB. Both Hibernate and ObjectDB have an old API ( Session in Hibernate, JDO PersistenceManager in ObjectDB) and a ...

 
forum_thread

Request clarification of changes to accessor enhancement policy (non-getter prefix instead of getter suffix) AND annotations

In response to the forum posting http://www.objectdb.com/database/forum/994 changes were made to the way enhancement treats getters and setters (property accessors), namely there are no longer enhanced additional getters/setters, because the additional methods now use (since about version 2-6-5) this pattern: __odbHidden_[accessor_name] Instead of this pattern with a suffix (preserving the method as a setter or getter), prior to version 2-6-5: ... which "moved" the annotations, essentially broke the JPA API, one reason I prefer the new non-accessor hidden method approach). ... posting is to emphasise that annotations are part of the API, and may include custom annotations. The original strategy of "moving" the ...