You are here: Usage Pitfalls

Usage Pitfalls

The db4o team tries hard to make the db4o as easy to use as possible. However there are still some pitfalls.

When objects are only partially loaded and you run into null pointer exceptions, then you ran into not activated objects. This is a common issue. See "The Activation Pitfall"

When updates are not stored then you have issues with the update-depth.See "Update Depth Pitfall"

db4o tries hard to store every object without any mapping. However in practice the mapping is not perfect. .For example remoting objects shouldn't be stored in db4o. See "Storing MarshalByRef Objects"

db4o includes the assembly-name in the type names. This also means that you need to be careful when accessing the same database from different applications. See "Accessing Persistent Classes From Different .NET Applications"

There are a few dangerous practices which you really should avoid. See "Dangerous Practices"

db4o has database size limit, which is by default 2 GByte. See how you can increase it. See "Working With Large Amounts Of Data"