Thanks, I think this is the best thing to do. On Mon, Aug 20, 2012 at 1:17 PM, Thomas Beale < thomas.beale at oceaninformatics.com> wrote:
> On 20/08/2012 05:47, Seref Arikan wrote: > >> Hi Tom, >> Your comments are quite helpful, but they do not belong to the context >> I'm asking about. I'm asking the default behaviour for returning results >> when no constraints are there. >> It may not be a meaningful use case for using AQL, but it is a >> technically valid one. My question is: how should the implementation behave >> when it faces this technically valid AQL, on this EHR? >> >> > in that case, whatever is matched is matched, which will include all your > combinations ;-) > > - thomas > > > ______________________________**_________________ > openEHR-technical mailing list > openEHR-technical at lists.**openehr.org<openEHR-technical at > lists.openehr.org> > http://lists.openehr.org/**mailman/listinfo/openehr-** > technical_lists.openehr.org<http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120820/b00bbd90/attachment.html>
