There is a support requested for “LIKE”-like operator for partial text matching. This should support conditions like:
WHERE path/value LIKE "some%"`
See https://www.techonthenet.com/sql/like.php for the level of support of LIKE operator in various SQL implementation.
We need to establish to which types this LIKE operator can be applied. For instance, if it should only be applied to the assumed type String, or if it could be applied to openEHR DVs and the AQL processor is the one that internally knows to which single attribute apply the operator. I guess the only difference of these two options is the DV option would have a shorter path, while the String option should have a path to a single String attribute.
/a/b/value/value <String> LIKE “%…”
/a/b/value <DV_TEXT> LIKE “%…”
Another option would be to allow both.
Some DVs that contain Strings, so LIKE could be applied:
+ DV_DATE, DV_TIME, DV_DATE_TIME
To avoid any misconceptions or implementation particularities, I would keep LIKE only on attributes of DV types or others, so only on primitive types like String, etc
I agree with : only on "primitive" values that get treated as strings for purposes of LIKE.
I agree with others - let's stick to LIKE for primitive Strings for now. Anything else I think is hard to understand and query authors are never going to know what queries with LIKE <some DV_TEXT> really mean...
+1 on using LIKE only for primitive Strings