Support for LIKE operator
Description
CR fixes the problem in
Activity
Sebastian Iancu January 11, 2021 at 8:30 PM
The first version was using %, but actually this feature was already implemented with * by a couple of AQL implementations, so we just formalize what it is being used out there. For details check discourse links to see what was discussed.
Pieter Bos January 11, 2021 at 1:31 PM
I spoke to the one implementing AQL, and he said just the wildcards is good to be able to optimize queries, much easier than regexps, so I guess this is good to have.
Diego Bosca January 11, 2021 at 1:18 PM
I assume using % is because “select *”, but we don’t have that problem.
Like has limited expression power, surely not at the level of a regex
Pieter Bos January 11, 2021 at 1:03 PM
I’m a bit surprised by the choice of wildcard character. In SQL, this is usually ‘%', not ‘*’, but I guess it does not matter much. do we have a reason to use '*'?
Also do we have a reason to support both Like and matches {/regexp/}? Is like easier to optimize? case sensitivity?
Sebastian Iancu December 30, 2020 at 1:24 PM
I’ll change it
See https://discourse.openehr.org/t/can-we-talk-next-week-about-some-of-the-open-questions-for-the-aql-spec/249
and https://discourse.openehr.org/t/aql-issue-5-correct-spec-for-the-matches-operator-with-regexes/307