Author: toad
Date: 2008-10-07 23:50:11 +0000 (Tue, 07 Oct 2008)
New Revision: 22963
Modified:
branches/db4o/freenet/src/freenet/node/Node.java
Log:
Don't need cascade for HashMap
Modified: branches/db4o/freenet/src/freenet/node/Node.java
===================================================================
--- branches/db4o/freenet/src/freenet/node/Node.java 2008-10-07 16:07:31 UTC
(rev 22962)
+++ branches/db4o/freenet/src/freenet/node/Node.java 2008-10-07 23:50:11 UTC
(rev 22963)
@@ -834,9 +834,10 @@
dbConfig.objectClass(freenet.client.async.InsertCompressor.class).objectField("nodeDBHandle").indexed(true);
dbConfig.objectClass(freenet.node.fcp.FCPClient.class).objectField("name").indexed(true);
dbConfig.objectClass(freenet.client.async.DatastoreCheckerItem.class).objectField("prio").indexed(true);
-
dbConfig.objectClass(java.util.HashMap.class).cascadeOnUpdate(true);
-
dbConfig.objectClass(java.util.HashMap.class).cascadeOnDelete(true);
-
dbConfig.objectClass(java.util.HashMap.class).cascadeOnActivate(true);
+ /*
+ * HashMap: don't enable cascade on update/delete/activate,
db4o handles this
+ * internally through the TMap translator.
+ */
/** Maybe we want a different query evaluation mode?
* At the moment, a big splitfile insert will result in one
SingleBlockInserter
* for every key, which means one RegisterMe for each ... this
results in a long pause
