As I'm thinking a Db design through I'm realizing how much my brain is accustomed to tabular SQL-Type organization. Getting used to thinking i terms of Graphs is taking a little time. l'd like to get a little feedback on a couple design issues to see if I'm on the right track.
I want to design a Node space with a specific content and relationship structure. Alongside the content is a typical unix like "User/Group" system. my initial thought was to create a property for each node for a UserId and GroupId as a key value. But then I thought why not simply create a relationship between the user/group node to each of his/her content nodes. This would make querying much easier. In general it seems that the data saved with specific nodes should be limited to data which specific to that node like name, title, article text etc. Other information which deals with classification, categorization and organization like types, users, groups, tagging etc. should be represented with relationships. I'm wondering if this is a reasonable way of learning to think in terms of Graphical-DBs? It would be nice if something like this were in the Wiki, where users could share their design experiences. It might fit here: http://wiki.neo4j.org/content/Guidelines_for_Building_a_Neo_App or here: http://wiki.neo4j.org/content/Domain_Modeling_Gallery But I don't yet have any Neo Design experience so I cannot speak with much authority. However, if desired I could start a page in the Wiki. Thanks Andy Potter _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
