[EHRbase] Storing and querying data without an standalone archetype

[damoca (David Moner)]

I think it is important to distinguish between functionality and performance of AQL. It is reasonable to expect that in AQL you can query at least for any LOCATABLE children because, well, they are locatable. Then, if they are archetyped, then they can be indexed more easily and then the query performance is better… that’s fair but just complementary.

BTW, this is a good example of what @pablo mentioned some weeks ago about the need to improve the AQL specifications. What can be queried in the FROM clause? Now it is a quite informal definition:

Does that include other non-LOCATABLE classes?

AQL to Database SQL convertor

It’s long/complex to explain, you’ll need to study the whole AQL and we’ll need to do a workshop or two to go through all the issues in the spec. Though I did study the specs and tried to improve what I could while working for HiGHmed, but don’t trust me, you can check the spec yourself. One small example, consider the WHERE clause definition: Archetype Query Language (AQL) [Screenshot_2024-02-28_14-52-17] Then think about how that should be evaluated and executed and how that affects the re…