Ido, you can also have a look into our Spring-Data-Graph project that comes with a (very early) implementation of a cross-store approach that allows you to have annotated JPA Entities of which certain parts (e.g. a social graph) are stored in the graph database.
You can check out the project here: http://www.springsource.com/spring-data there also the github repositories are listed and the reference docs. currently version 1.0.0.M2 is deployed to spring-maven repo with the M3 we will tackle transaction handler issues for multiple datasources (1PC best effort) and adding full XA support If you would like to look into it, feel free to contact me. Cheers Michael Am 09.02.2011 um 11:46 schrieb Craig Taverner: > Hi Ido, > > Do you mean you want a central place to store the names of all the > properties used on some types of object? Kind-of like a schema, so your > application code knows what properties are available before starting a > traversal? > > If that is the case, we have a similar requirement, and we solved it in the > following way. Most of our graphs are collected into 'datasets', which means > a collection of data that we expect to analyse as a whole, and therefor we > like to keep some metadata about the dataset. So we root the graph in a node > called the dataset node, and the graph of data is built as a tree structure > beneath that node. Then we connect a properties node to the dataset node, > and this is the root of another small graph, basically just a depth-1 tree > of nodes, each representing properties of a particular type. Each property > node has a key with the name of the property, and the value is the number of > occurences in the dataset. This allows us to show the list of properties in > the GUI when a user is preparing an analysis. > > An example line through the properties metadata graph might look like: > dataset--PROPERTIES-->properties--PROPERTY(float)-->property(x:10,y:20,z:7) > > Is this the kind of think you are looking for? > > Regards, Craig > > On Wed, Feb 9, 2011 at 10:36 AM, Ido Ran <[email protected]> wrote: > >> Hi, >> I have a question about how to design a database that has graph data >> structure in it's core yet have other data which is not graph in nature >> connected to it. >> In our model we have graph of objects that are connect with links - which >> is >> a prefect match for neo4j. >> Then on each object and and link we store properties of various types so we >> need to store list of all the property types we store. >> We can represent them as graph as well but that fells unnatural. The other >> way is to combine RDBMS with neo4j but then we run into sync. and >> deployment >> problems. >> >> Any help will be great. >> Thank you, >> Ido >> _______________________________________________ >> Neo4j mailing list >> [email protected] >> https://lists.neo4j.org/mailman/listinfo/user >> > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
