I don't know if it's necessary separate "likes" which points to a statement
from those pointing to something concrete (e.g. a movie).
Anyway you could always keep statements in a separate subclass (Statement)
and "real objects" in another one (Concrete).
I'm thinking of something like:
SELECT in("subject").out("object")
FROM #1:1
WHERE in("subject").out("object") INSTANCEOF "Concrete"
I know it's a bit complicated, but it seems to me the simplest way to model
it.
If you want to follow a chain of statements, without knowing a priori the
depth level, you could also use a TRAVERSE.
Cheers,
Riccardo
2015-08-24 8:08 GMT+02:00 scott molinari <[email protected]>:
> And in this scenario, S1 has a label called likes? So with S1, we are
> basically creating a vertex what connects two other vertices through the
> edges subject and object. I think I get it.
>
> I can imagine that abstract data model makes querying a bit more
> complicated, doesn't it? How would one query for exactly what it is that
> Joe is liking?
>
> Scott
>
> --
>
> ---
> 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.
>
--
---
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.
