Hm, I quess you can't query metadata with gremlin, but you might be able to
get the classes programatically:
ODatabase.getMetadata().getSchema().getClass("A") ....
or by SQL:
select classes from metadata:schema
and pass them as parameter, not trivial however...
Dne úterý 26. ledna 2016 17:39:40 UTC+1 [email protected] napsal(a):
>
> Right, I realize that. The question is whether there's something in
> OrientDB's tinkerpop implementation to make this work. Maybe a @superclass
> property that matches any class in the inheritance tree
>
> Otherwise we are reduced to using mixed concepts of SELECT
> expand(gremlin("current.<blah>)) from A which is less than ideal.
>
>
> On Tuesday, January 26, 2016 at 10:46:42 AM UTC-5, Jan Plaček wrote:
>>
>> Tinkerpop 2 does not define something like classes, so only way to filter
>> verticies is by property or edge.
>>
>> Since Tinkerpop 3 (not implemented by OrientDB yet) verticies are allowed
>> to have a single immutable label accessible via "T.label" . But it's
>> basically used just as typed property name:
>>
>> g.V(T.label, "A")
>>
>> Now Tinkerpop implementors can define T.label as "@class" for example.
>>
>> Dne úterý 26. ledna 2016 15:42:25 UTC+1 [email protected] napsal(a):
>>>
>>> Right, so what's the gremlin alternative to
>>>
>>> select from A ?
>>>
>>> On Tuesday, January 26, 2016 at 4:32:06 AM UTC-5, [email protected]
>>> wrote:
>>>>
>>>> Hi,
>>>> I think that
>>>>
>>>> g.V("@class", "A")
>>>>
>>>> is equivalent to
>>>>
>>>> select from V where @class='A'
>>>>
>>>> and then it will return only the verteces of the class A..
>>>>
>>>> Kind regards,
>>>> Alessandro
>>>>
>>>
--
---
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.
