db4o Developer Community

As the popular saying  tell us, there's no such thing as free lunch. It is no different for work related subjects. When we introduced Transparent Activation (TA) concept we knew that it could make developer's life easier (by presenting a simpler model for object life cycle): developers would not be required to think about activation depths ...

Hello, I'm not sure how much this applies to Java (I'm a bit rusty there), but .NET has some really really easy, intuitive and useful transaction management options built in and I would love to see db4o implement these. I have implemented a Transaction Resource Manager for an ORM I was working on before, and really it's not very difficult, but ...

In this post Rodrigo introduced the concept of Transparent Persistence that makes developers life even easier as, once configured, db4o will take care of changed objects and make sure they are updated in the database (when the transaction gets committed) without developer assistance.This level of transparency is, of course, a welcome addition but ...

Activation has been discussed in depth (no pun intended) before. Transparent Activation is db4o's ability to defer loading an object's state until just before it's accessed for the first time. Transparent Activation relieves programmers from keeping track of which objects must be completely available before an operation can be executed. ...