| ... | ... | @@ -167,18 +167,25 @@ will be translated to |
|
|
|
|
|
|
|
If a column on a big table is not indexed correctly, this search option will not be allowed.
|
|
|
|
|
|
|
|
# JSONB contains (@>)
|
|
|
|
## JSONB contains (@>)
|
|
|
|
|
|
|
|
This is an extension for IronAPI. Does the left JSONB value contain the right JSONB path/value entries at the top level?
|
|
|
|
|
|
|
|
`POST /data/extensions/client_meta_data/query`
|
|
|
|
|
|
|
|
```json
|
|
|
|
#/data/core/customer/query
|
|
|
|
{
|
|
|
|
"conds" : {"me.phonenumbers" : {"@>" : {"mobile": "+4354359"} } }
|
|
|
|
"conds": {
|
|
|
|
"me.settings": {
|
|
|
|
"@>": {
|
|
|
|
"login_name": "test"
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
# Subtree
|
|
|
|
## -subtree
|
|
|
|
|
|
|
|
This is an extension for IronAPI.
|
|
|
|
|
| ... | ... | @@ -192,7 +199,6 @@ For entities which represent a tree structure ("isTree": true in the universe), |
|
|
|
|
|
|
|
The search may be limited to a certain depth, in this example it's "2", so only the main entry (with id "1") and it's direct children will be returned:
|
|
|
|
|
|
|
|
|
|
|
|
```json
|
|
|
|
{
|
|
|
|
"conds": {"me.id": {"-subtree": [1, 2] }
|
| ... | ... | @@ -222,7 +228,7 @@ with "and": |
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
# Parents
|
|
|
|
## -parents
|
|
|
|
|
|
|
|
This is an extension for IronAPI.
|
|
|
|
|
| ... | ... | |