You are here: Basics Operations & Concepts > Transparent Activation/Persistence

Transparent Activation/Persistence

One of the challenges of db4o is to manage the activation of objects. Also updating the changed objects can be a challenge. The transparent activation/persistence framework solves these issues.

Transparent activation manages the activation of objects. It activates objects as soon as you access them. That means that you don't have to worry about the activation-depth or cascaded activation.

Transparent persistence builds on top of transparent activation and also manages updating objects. It monitors stored objects and memorizes changed objects. When you commit it automatically stores all updated objects.

Transparent activation and persistence are very similar to implement. Therefore the same steps need to be taken to enable them.

To get started take a look at an example.See "Transparent Persistence Enhancement Example"

For the learning the implementation details take a look at a manual implementation. See "Implementation"

Collections need special attention in transparent activation / persistence. See "Collections"

Also take a look at rollback strategies, which allows db4o to rollback in memory objects. See "Automatic Rollback"

And finally take a look some well known pitfalls: See "Transparent Activation Pitfalls"