Transparent activation and activation statements about DB4O

Transparent activation and activation statements about DB4O

There is an introduction to transparent activation, which you can see here: http://www.cnblogs.com/redmoon/archive/2008/02/23/1078619.html

It is pointed out that through the transparent activation feature, db4o can help us automatically deal with the activation level problem, so that the object's properties are non-basic types can also be automatically loaded on demand.

I don't understand how it works, but I use it very frankly until I see a child with a collection property loaded is always empty, no solution to the flex wall ~

It was once suspected that db4o support for class inheritance exists bug~

It was later discovered that all levels of the declaration were activated (Db4ofactory.configure (). ObjectClass (typeof (MyClass1)). Cascadeonactivate (True), the property can be successfully obtained, and the problem is still derived from transparent activation-it's not smart enough

The property that raises the question is a List<> collection property, and the other properties are no problem with the underlying type or the custom type, so the guess might be that transparent activation has not yet been supported for the collection.

There is also a bit to note about the activation statement, such as the following activation level description:

Db4ofactory.configure (). ObjectClass (typeof (MyClass1)). Cascadeonupdate (TRUE);
Db4ofactory.configure (). ObjectClass (typeof (MyClass1)). Cascadeonactivate (TRUE);

It should be noted that the type of the highlighted part should not be an abstract class or interface, it should be a definite absolute type (that is, if you want a class and its parent class to be assigned such a declaration, you need to declare them separately, not just the parent class), otherwise it will not work.

Reprint: http://www.cnblogs.com/SkyD/archive/2010/10/03/1841729.html

Transparent activation and activation statements about DB4O