Optimization of stored query execution in EHRBase

As per my understanding AQL gets compiled into SQL for execution. In stored queries, are the AQLs being pre-compiled so that it does not have to be done every time it is used?

Hi Dileep,

no, there is no such optimization at the moment.

Have you done any analysis on the potential improvement this can give? Is this in your roadmap?

1 Like

I don’t think this would provide value. Queries are already cached. Are you facing any issues at the moment?

I have not faced any problem. Just a thought


That’s good to hear! We could actually think about providing a convenince feature that would allow you to provide a further parameter when creating a stored query to allow the creation of secondary indexes. Just an idea, there might be some practical issues to that.