>
> I'll try to explain my situation a little better with a different use-case.
>
I have data that is represented in a time-flow manner; i.e. EventC occurs
after EventB which occurs after EventA, etc. This data is coming from
multiple sources, so it is not completely linear. It needs to be
congregated together, which is where I'm having the issue.
Currently the data looks something like this:
# | event | next
--------------------------
12:0 | EventA | 12:1
12:1 | EventB | 12:2
12:2 | EventC |
12:3 | EventA | 12:4
12:4 | EventD |
Where "next" is the out() edge to the event that comes next in the
time-flow. On a graph this comes out to look like:
EventA-->EventB-->EventC
EventA-->EventD
Since this data needs to be congregated together, **I need to merge
duplicate events but preserve their edges**. In other words, I need a
select query that will result in:
-->EventB-->EventC
EventA |
-->EventD
In this example, since EventB and EventD both occurred after EventA (just
at different times), the select query will show two branches off EventA as
opposed to two separate time-flows.
I am using the most recent stable version of OrientDB (2.0.6?) through the
Docker image.
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
