Alessandro, the query does return results - but if you look at them
carefully, you'll see that they're incorrect.
Try putting completely different dates, and you'll see that the results
don't change :(
On Fri, Sep 4, 2015 at 12:54 PM, wrote:
> Hi Lior,
> this query seems to work
> select expa
It should work - but it doesn't. There's an open issue about it,
apparently...
https://github.com/orientechnologies/orientdb/issues/4697
:(
Thanks again for the help.
On Fri, Sep 4, 2015 at 12:34 PM, wrote:
> Hi Lior,
> try this query
>
> select expand(distinct(rid)) from index:aggregatedphone
That would work, Alessandro, but it means traversing and expanding all
call_times without using the index.
Giulia - I've made some progress: this query shows that the index *does*
index the fields:
select from index:aggregatedphonecall_call_times
I get a table of *individual* keys and rids! That'
It's a bit weird, because the created index *does* include all values in an
array.
So if I have an index with all the values from within the lists, it would
make sense that I could issue an indexed based range query...
On Sep 4, 2015 10:14, "Giulia Brignoli" wrote:
> Hi Lior,
>
> probably your pr
Hi,
I have a DB with vertices called Person, and edges called
AggregatedPhoneCall.
Each edge keeps an *indexed* embedded list "call_times", which keeps all
the times in which a phone call was made between these 2 Persons.
I want to write a query which will return all AggregatedPhoneCall edges
on you can use the DISTINCT clause,
> for example : SELECT distinct(outV()) FROM Called WHERE start_time>X AND
> end_time
> Bye, Alessandro
>
> Il giorno lunedì 1 giugno 2015 20:36:59 UTC+2, Lior Neudorfer ha scritto:
>>
>> Hi,
>>
>> two small questions
Hi,
two small questions from an OrientDB beginner...
I have a graph with one type of Vertices - "Person" - and one type of Edges
- "Called".
The graph describes phone conversations between people, with each edge
having a "start_time" and "end_time" properties which describe the call's
start a
