From 638e30603c2b78affa2eb1f1cdc565b1f10cc027 Mon Sep 17 00:00:00 2001 From: mechatroner Date: Tue, 31 Mar 2020 23:56:09 -0400 Subject: [PATCH] readme --- README.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 39f89fd..9cafb29 100644 --- a/README.md +++ b/README.md @@ -204,7 +204,7 @@ There is a workaround for the limitation above for _ARRAY_AGG_ function which su Join table B can be referenced either by it's file path or by it's name - an arbitary string which user should provide before executing the JOIN query. RBQL supports _STRICT LEFT JOIN_ which is like _LEFT JOIN_, but generates an error if any key in left table "A" doesn't have exactly one matching key in the right table "B". -Limitation: _JOIN_ statements must have the following form: _ (/path/to/table.tsv | table_name ) ON ai == bj_ +Limitation: _JOIN_ statements can't contain Python/JS expressions and must have the following form: _ (/path/to/table.tsv | table_name ) ON a... == b... [AND a... == b... [AND ... ]]_ ### SELECT EXCEPT statement @@ -218,6 +218,11 @@ UNNEST(list) takes a list/array as an argument and repeats the output record mul Example: `SELECT a1, UNNEST(a2.split(';'))` +### LIKE() function +RBQL does not support LIKE operator, instead it provides "like()" function which can be used like this: +`SELECT * where like(a1, 'foo%bar')` + + ### User Defined Functions (UDF) RBQL supports User Defined Functions