Note that there are some explanatory texts on larger screens.

plurals
  1. POGraph databases and RDF triplestores: storage of graph data in python
    text
    copied!<p>I need to develop a graph database in python (I would enjoy if anybody can join me in the development. I already have a bit of code, but I would gladly discuss about it).</p> <p>I did my research on the internet. in Java, <a href="http://neo4j.org/" rel="noreferrer">neo4j</a> is a candidate, but I was not able to find anything about actual disk storage. In python, there are many <a href="http://wiki.python.org/moin/PythonGraphApi" rel="noreferrer">graph data models</a> (see this pre-PEP proposal, but none of them satisfy my need to store and retrieve from disk.</p> <p>I do know about triplestores, however. triplestores are basically RDF databases, so a graph data model could be mapped in RDF and stored, but I am generally uneasy (mainly due to lack of experience) about this solution. One example is <a href="http://www.openrdf.org/" rel="noreferrer">Sesame</a>. Fact is that, in any case, you have to convert from in-memory graph representation to RDF representation and viceversa in any case, unless the client code wants to hack on the RDF document directly, which is mostly unlikely. It would be like handling DB tuples directly, instead of creating an object. </p> <p>What is the state-of-the-art for storage and retrieval (<em>a la</em> DBMS) of graph data in python, at the moment? Would it make sense to start developing an implementation, hopefully with the help of someone interested in it, and in collaboration with the proposers for the Graph API PEP ? Please note that this is going to be part of my job for the next months, so my contribution to this eventual project is pretty damn serious ;)</p> <p><strong>Edit</strong>: Found also <a href="http://blog.directededge.com/2009/02/27/on-building-a-stupidly-fast-graph-database/" rel="noreferrer">directededge</a>, but it appears to be a commercial product</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload