Plagiarizing the now defunct American anti-drug campaign, "Just say no...to object features." The memory management and schema processing of objects would decrease the speed (and arguably the elegance) of the graph.
On Sun, Nov 22, 2009 at 1:26 PM, Emil Eifrem <e...@neotechnology.com> wrote: > On Sun, Nov 22, 2009 at 18:34, Robert Lockhart <bobby...@gmail.com> wrote: >> it's super-lame that you only allow a basic set of objects to be the values >> of properties. Any plans to open it up to arbitrary objects? > > No. We're not an object database. I think going down that path opens > up a whole can of worms that I'd rather not get us into. For example, > class/object versioning and activation depth. > > On the contrary, I've always agreed with the relational gurus that > separating data and logic is a good thing. I.e., a programming > language paradigm is not necessarily the most robust and effective > data model. I disagree with the RDBMS guys, however, that tables is > that data model. At least not for the majority of the applications in > 2009. > > Anyway, it seems to be easy enough to map any object down to the > property data types Neo4j provides. If you think about it, you can > recursively decompose most Java object's state to Strings + the JVM > primitive types. What we need to add is more powerful wiring so you > won't have to do as much of the get/setProperty that you need to do > today. > > Cheers, > > -- > Emil Eifrém, CEO [e...@neotechnology.com] > Neo Technology, www.neotechnology.com > Cell: +46 733 462 271 | US: 206 403 8808 > http://blogs.neotechnology.com/emil > http://twitter.com/emileifrem > _______________________________________________ > Neo mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
