Hi Pablo,
CONTAINS is like the '//' operator in Xpath - it's matches the thing on
the right hand side, anywhere under the object on the left hand side.
So doing COMPOSITION CONTAINS OBSERVATION and similar things is normal.
The AQL documentation may need to be fixed.
- thomas
On 01/10/2017 16:11, Pablo Pazos wrote:
Hi all,
I'm reading through the AQL specs, on this section
http://openehr.org/releases/QUERY/latest/docs/AQL/AQL.html#_containment
it is mentioned that CONTAINS is from parent to child.
Most examples there show COMPOSITION CONTAINS ENTRY. In a case that
there is a SECTION in the middle, should AQL be always COMPOSITION
CONTAINS SECTION CONTAINS ENTRY?
Before reading this specific point I was thinking that CONTAINS
allowed to look anywhere on the COMPOSITION tree, semantically looking
for "child or descendant", instead of just "child".
If we have only direct "child" references, having a small tree of
SECTIONs can make queries more complex, like COMPOSITION CONTAINS
SECTION CONTAINS SECTION CONTAINS SECTION CONTAINS ENTRY ...
Would it be useful to have that kind of "child or descendant"
containment operator added to AQL?
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
