child node, but *never* deletes it from the database. remove() actually deletes the node from the database and also releases it from its parent. This affects HopObject.remove() and HopObject.remove(HopObject), which use these methods. From now on, the only way to delete a HopObject from db is to use the remove() function without arguments. HopObject.remove(HopObject) should be used to - remove a child object from an embedded db collection without deleting it - removing a hopobject from a relational db collection with cachemode = aggressive if the collection does not belong to the child object's parent. - Do not return on-demand nodes (groupby, accessname) in getProperty(). - Avoid creating loops in parent chain when creating cyclic references on transient objects before committing them to db - Removed unused links vector and code - Rename Enumerations because enum is a reserved word in Java 1.5 |
||
---|---|---|
.. | ||
Acme | ||
helma |