| Method Summary |
|
| public void | cascadeOnActivate(boolean flag)
sets cascaded activation behaviour.
Setting cascadeOnActivate to true will result in the activation
of the object attribute stored in this field if the parent object
is activated.
The default setting is false.
In client-server environment this setting should be used on both
client and server. |
| public void | cascadeOnDelete(boolean flag)
sets cascaded delete behaviour.
Setting cascadeOnDelete to true will result in the deletion of
the object attribute stored in this field on the parent object
if the parent object is passed to
com.db4o.ObjectContainer.delete .
Caution !
This setting will also trigger deletion of the old member object, on
calls to
com.db4o.ObjectContainer.set .
An example of the behaviour can be found in
ObjectClass.cascadeOnDelete
The default setting is false.
In client-server environment this setting should be used on both
client and server. |
| public void | cascadeOnUpdate(boolean flag)
sets cascaded update behaviour.
Setting cascadeOnUpdate to true will result in the update
of the object attribute stored in this field if the parent object
is passed to
com.db4o.ObjectContainer.set .
The default setting is false.
In client-server environment this setting should be used on both
client and server. |
| public void | indexed(boolean flag)
turns indexing on or off.
Field indices dramatically improve query performance but they may
considerably reduce storage and update performance.
The best benchmark whether
or not an index on a field achieves the desired result is the completed application
- with a data load that is typical for it's use.
This configuration setting
is only checked when the
com.db4o.ObjectContainer is opened. |
| public void | queryEvaluation(boolean flag)
toggles query evaluation.
All fields are evaluated by default. |
| public void | rename(String newName)
renames a field of a stored class.
Use this method to refactor classes.
In client-server environment this setting should be used on both
client and server. |