hi! > Your best shot right now is to search the mailing list archives and > look at the code.
And here's the searchable mail archive: http://www.mail-archive.com/user@lists.neo4j.org/info.html /anders > If you are interested in how nodes and relationships > are stored on disk I would suggest take a look at > org.neo4j.impl.nioneo.store package. > > There is also a batch insert implementation (that will be available in > b9 release) that can be found int the org.neo4j.impl.batchinsert > package. The batch insert implementation works directly with the > nioneo.store package and drops support for transactions and the like > to achieve maximum insert speed. It may be easier to start looking > there since transactions tend to make things more complicated. > > Regards, > Johan > > On Tue, May 5, 2009 at 7:50 AM, Matthias Broecheler > <matth...@knowledgefrominformation.com> wrote: > >> Hello everybody, >> >> I just spend a good deal of time learning about Neo4j and got very >> interested in the database framework. It seems applicable to the kind of >> things I would like to do on graph datasets. However, I could not find any >> information on the underlying data model of neo4j. How are nodes/edges >> stored on disk? How do you optimize retrieval? What kind of index structures >> do you use? Do you have any information for contributing developers? >> >> Thank you very much and keep up the good work. >> Best, >> Matthias >> > _______________________________________________ > Neo mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > -- Anders Nawroth [and...@neotechnology.com] GTalk, Skype: anders.nawroth Phone: +46 737 894 163 http://twitter.com/nawroth http://blog.nawroth.com/ _______________________________________________ Neo mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
