You are here: Basics Operations & Concepts > Update Concept > Transparent Persistence

Transparent Persistence

One of db4o's goals is to make the database transparent to the application logic. Wouldn't it be nice to initially register an object with a single store()-call and then let the database manage all future object modifications? Transparent Persistence does exactly that.It keeps track of changes and stores all modified objects automatically when committing.

This has several benefits:

Transparent persistence takes care of activating the objects and storing changes. Take a look a simple example. See "Transparent Persistence Example"

In order to support transparent persistence the persisted object need to implement certain interfaces. To manually implementing this interface is time consuming. Therefore it can be automated with enhancement tools. See "TP Enhancement"

When using Transparent Persistence collections might need special attention. See "Transparent Persistence Collections"

For a deeper understanding of the mechanism: See "Transparent Persistence Implementation"