Literal search
Syntax description
Literal search is case-insensitive and partial, meaning that search for ‘abc’ brings also XABCD.
Operators
Operators |
Description |
Examples |
---|---|---|
AND aliases:
|
The logical AND operator allows you to find timelines that contain all search query words. Format: <query text> AND <query text> |
test1 AND test2
test1 test2 AND (test3 & test4)
|
OR aliases:
|
The logical OR operator allows you to find timelines that contain at least one of the search words. Format: <query text> OR <query text> |
test1 OR test2 test1, test2 test1, test2 OR (test3 | test4)
|
NOT aliases:
|
The logical NOT operator allows you to exclude a timeline containing a specified word from search results. In this case, the NOT operator should come before the word to be excluded. Format: NOT <query text>тест1 NOT тест2 |
test1 -test2
* -test
q -(b, x, z)
|
"" aliases:
|
The strict match operator "" (double quotes) is used to search for exact matches. It allows you to find a timeline that contains an entire query text. That is, routes that contain part of the query text will not be included in the search results. Format: "<query text>" |
"test", "test1"
"test", "some" AND 'query'
|
Clarifying flags
Operators |
Description |
Examples |
---|---|---|
<entry>:id aliases:
|
Looking up in timeline’s ID. |
(1 2 3):id
|
<entry>:activity aliases:
|
Looking up in timeline’s activity names. |
test:activity
|
<entry>:attrs aliases:
|
Looking up in timeline’s attributes. |
test:id -test:attrs
(12, 14, 18):attr1
|
<entry>:1-N aliases:
|
Looking up in timeline’s attributes (N – is an attribute number). |
test:1-10
|
<entry>{id, activity, 1, 2, N} |
Looking up in timeline’s id and activity and attributes (1, 2, N). |
113{id, events, 1}
|