About managed

release

2.4.2

... of primitive types. Fixed a bug of returning managed hollow objects in query results. Fixed an error message ... execution. Fixed a bug in using non managed non enhanced entity objects as parameters or in criteria queries ( ...

 
release

2.5.3

... AS 7.1.1. Improved performance of merging managed entities. Fixed a deadlock . Changed ... of primitive types. Fixed a bug of returning managed hollow objects in query results. Fixed an error message ...

 
release

2.5.4

... AS 7.1.1. Improved performance of merging managed entities. Fixed a deadlock . Changed ... of primitive types. Fixed a bug of returning managed hollow objects in query results. Fixed an error message ...

 
release

2.5.2

... AS 7.1.1. Improved performance of merging managed entities. Fixed a deadlock . Changed ... of primitive types. Fixed a bug of returning managed hollow objects in query results. Fixed an error message ...

 
manual

[ODB1] Chapter 6 - Persistent Objects

Shows how to store, retrieve, update and delete database objects. ... A persistent object that becomes transient is not managed by JDO anymore, and it is immediately removed form the persistent ...

 
forum_thread

LDAP and ObjectDB

Hello, Is there any advantage in using LDAP with ObjectDB? I notice that I would still have to query the config for the credential, as well as query LDAP, a doubling of the work.   Thanks #1 2011-11-14 18:43 Hello, Is there any advantage in using LDAP with ObjectDB? I notice that I would still have ...

 
faq

What is ObjectDB?

ObjectDB is an object oriented database management system (ODBMS). It provides all the standard database management services (storage and retrieval, transactions, lock management, query processing, etc.), but it uses an object oriented model to store an ...

 
api-jdo

javax.jdo.InstanceCallbacks

A PersistenceCapable class that provides callback methods for life cycle events implements this interface.(Interface of JDO)

 
forum_thread

in-memory and on-disk support?

I've had a quick read through the features/FAQ and haven't been able to find a clear answer. I'm looking at replacing a setup of H2 where I have 40GB in-memory backed by 800GB on-disk, the 40GB in memory represents the first 40GB of the 800GB on-disk for super-fast recent entry searching, the records at the end continuously purge as the new ones come in(duplicate write, one to in-memory and one to on-disk). ... The large database (800GB) will be managed on an ordinary disk. The small database (40GB) will be managed on a RAM disk / RAM drive . Both databases can be managed in embedded (in process) mode with no TCP/IP. Alternatively you ...

 
manual

Setting and Tuning of JPA Queries

Explains various JPA query settings - result range, flush and lock.... method Create a new application-managed EntityManager with the specified Map of properties. See JavaDoc ... method Create a new application-managed EntityManager with the specified Map of properties. See JavaDoc ...