So I had a breakthrough that gives me exactly what I'm looking for:
select *, out('identified') as identities from user fetchplan identities:1
Is there any reason why this type of query is a *bad idea*?
Geoff
On Wednesday, January 21, 2015 at 1:53:47 PM UTC-5, Geoff Goodman wrote:
>
> Hi Marcel,
>
> Thanks for the suggestion.
>
> I tried:
>
> SELECT user.username, out('identified').include('identity.*', null) as
> identities FROM #13:1
>
> but the result of that query is:
>
> [{"@type":"d","@version":0},{"@type":"d","@version":0},{"@type":"d",
> "@version":0},{"@type":"d","@version":0}]
>
> What I discovered that pretty much gives me exactly what I need (except
> that the edge records are included) is the FETCHPLAN directive:
>
> SELECT from user fetchplan out_identified:2
>
> My mind is blown.
>
> Geoff
>
>
> On Wednesday, January 21, 2015 at 3:55:10 AM UTC-5, Marcel Pitch wrote:
>>
>> Hi Geoff,
>>
>> Did you try this ?
>>
>> SELECT <USER.prop>, out('IDENTIFIED').include('<IDENTITY.prop1>',
>> '<IDENTITY.prop2>') FROM <USER.@rid>
>>
>>
>>
--
---
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.
