 |
From: Michael Hunger <michael.hun...@neotechnology.com>
Date: Wed, 12 Sep 2012 10:32:18 +0300
Local: Wed, Sep 12 2012 3:32 am
Subject: Re: [Neo4j] Re: NEO4J: love the idea/concept, wondering if it is what I need...
You can have a look at this: http://docs.neo4j.org/chunked/snapshot/cypher-cookbook-path-tree.html
Another option is to create a secondary index that links your nodes in the order of your time series:
Graphity is an example on how to take this to the extreme: http://www.rene-pickhardt.de/graphity-an-efficient-graph-model-for-re...
Michael
Am 12.09.2012 um 04:28 schrieb Bogus Exception:
> OK... Perhaps my last post was a lot to take in... :)
> How about this:
> How should time-series/time-domain data be integrated into a graph?
> TIA!
> pat
> On Saturday, September 8, 2012 6:52:08 PM UTC-4, Bogus Exception wrote:
> The things I need to persist do not fit an RDBMS model well, and I am searching to find a model/system that will. The data has many hierarchies, I guess is the easiest way to sum it up. I prefer to think of it as aspects, but interpretations differ.
> Consider a container in a container ship. It:
> Is a container
> In other words, I never will know what aspect/point of view/top or bottom of any hierarchy the sole container will be referenced from. Has that same container been on board more than one time with this particular captain? Has this container been on any ships that were taken over by pirates? Has either the sender/receiver ever been charged with trying to convey bad things? > A room full of people, some who know each other, some who don't... Some are left -handed, some wear size 10 shoes... his kind of scenario, although illustrative, is actually far too simple for me, as we are always talking about a person object, and the relationships between them.
> I hope I'm explaining this correctly. So basically in our (seemingly) simple example, there are many attributes/aspects of investigating relationships. In fact, I'm looking for a solution that will make discovering relationships easier. By that, of course, I mean a persistence layer/engine that will easily allow me to programmatically discover relationships where none are known to exist.
> A graph seems to be the thing I would need. There are stubs possible, but in my need, there is always some kind of relationship with another something. So it isn't like the Matrix example where you want to know friends of friends... It's more like 'what commonalities, traits & patterns in data and relationships exist in the Matrix people?'...
> TIA!
> :)
> -- You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| |||||||||||||