API/Queries.md

@@ -89,11 +89,12 @@ The main logic is that the search parameters are presented in a data structure a
 
 Keys are restricted, as they are not bound, as values are.
 
-The must either be a reference to a [column](/API/Queries/Attributes#permitted-column-names) or a call
-to on of the [permitted functions](/API/Queries/Attributes#permitted-functions).
+They must either be a reference to a [column](/API/Queries/Attributes#permitted-column-names) or a call
+to one of the [permitted functions](/API/Queries/Attributes#permitted-functions).
 
 ### Examples:
 
+#### and
 ```json
 {
     "conds" : {
@@ -115,6 +116,9 @@ WHERE ( ( me.id = ? AND me.name = ? ) )
 ```
 ```sql
 WHERE ( ( me.id < ? AND me.name = ? ) )
+
+#### or
+
 ```
 ```json
 {
@@ -130,6 +134,20 @@ WHERE ( ( me.id < ? AND me.name = ? ) )
 WHERE ( me.id < ? OR me.name = ? ) )
 ```
 
+#### json(b)
+
+#### functions
+
+`POST /data/system/entity/query`
+
+```json
+{
+  "conds": {
+    "coalesce(me.id,1)": 1
+  }
+}
+```
+
 For more examples of search options see [Query-Search-Options](/API/Queries/Query-Search-Options) and [Query-Examples](/API/Queries/Query-Examples).
 
 ## [Attributes](/API/Queries/Attributes)