Transparent Persistence

One of db4o goals is to make database transparent to the application logic. Would not it be nice after an initial registering of an object with a database with a single store() method to leave the database to manage all the future object modification? This idea went a long way from initial vague thoughts to a final implementation in db4o version 7.1 and was named Transparent Persistence. Let's look at the implementation in a more detail.