On Thursday, June 11, 2015 at 3:32:35 PM UTC+2, [email protected] wrote:
>
>
> In the field category 2 the are only the contracts from OpenInterest where
> the fetch_date is 2015-06-02.
>
> Let me know if that is what you wanted.
>
>
>
> Hi,
interesting: you came to the same solution, I figured out a few days ago.
Problem is: After carefully crosschecking I found, that just the content
of the Object Industries.categories is returned.
In a database with joins, you alway got "has many" and "belongs to". The
one-way-graph defines only »has many«.
Lesson learned:
if you start at the top, you only get the »precision« of the TOP-Level. –
unless you narrow your query by defining subqueries as demonstrated in the
time-series-workout.
So you need to reference the (sub-)results of the sub-queries, which
provide a better precision.
To be specific: the query you (and I) build, queries only
select name, categories.name, categories.subcategories.contracts.symbol
from Industries where categories = {specific category)
The contents of subcategories and contracts are uniform and not dependent
on the set of contents used in the most inner subquery.
Which is consistent with the OO-architecture of the document-db.
I learned a lot about the database – about its document-part, its
OO-behavior and structural limits.
If the documentation would be complete, one might figure out, how the
results of the sub-queries can be linked together. UnionAll might already
be the solution. But its behavior, its syntax are not documented at all.
--
---
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.
