db4o Developer Community

Actually I think the decision is quite easy and it has been taken a long time ago for db4o. The Java Language Specification is explicit what the *same* object is:object1 == object2 We never store *the same* object twice in a database. What you are asking for is special treatment for objects that are *equivalent*.object1.equals(object2) The ...

This is a repost from the user forum: When you store a graph of objects to db4o and retrieve it afterwards, db4o assembles the graph in exactly the same way as it was stored. In doing so db4o makes sure that every object is instantiated only once, no matter which access path you choose. You can run hundreds of queries, navigate through hundreds ...

WolfBenz: What could be greater and more natural, for an Object Database, than that Objects themselves could define their equality? Well, that's exactly what equals() does. :-) Hi Wolf, we have had many discussions about this theme in the past. Let me explain why db4o behaves as it does. When you store a graph of objects to db4o and ...