> Heath, > > Good clear answer. Thanks. > > You enable me to take us back to where this conversation started. I can now > make a possibly uneducated guess how the Ocean querying works: You > parse AQL queries into two distinct parts, (1) for the relational DB and its > paths and (2) for the "object layer." The first part narrows down the range > of blobs you must look at as far as possible, and the second part penetrates > into specific values in the blobs themselves. If you end up with 10,000 > blobs resulting from part 1, you must parse and instantiate each one into > the memory of your object server and then step through each one to find > which of them satisfies the query.
Without going into the details of te exact architecture (its not interesting), ou are missing one important factor: we can know in advance a lot about what is in the blobs due to having the archetype 'path-map' for each blob. For example, if teh query concerns HbA1C levels, we know that only the HbA1C archetype is implicated. There is no need to even bother instantiating any blob not containing the HbA1C archetype paths. The archetype path maps give yo an x-ray view of the data. - thomas beale
