mirror of
https://github.com/ClickHouse/ClickHouse.git
synced 2024-11-19 14:11:58 +00:00
e8a5804e76
* update presentations * CLICKHOUSE-2936: redirect from clickhouse.yandex.ru and clickhouse.yandex.com * update submodule * lost files * CLICKHOUSE-2981: prefer sphinx docs over original reference * CLICKHOUSE-2981: docs styles more similar to main website + add flags to switch language links * update presentations * Less confusing directory structure (docs -> doc/reference/) * Minify sphinx docs too * Website release script: fail fast + pass docker hash on deploy * Do not underline links in docs * shorter * cleanup docker images * tune nginx config * CLICKHOUSE-3043: get rid of habrastorage links * Lost translation * CLICKHOUSE-2936: temporary client-side redirect * behaves weird in test * put redirect back * CLICKHOUSE-3047: copy docs txts to public too * move to proper file * remove old pages to avoid confusion * Remove reference redirect warning for now * Refresh README.md * Yellow buttons in docs * Use svg flags instead of unicode ones in docs * fix test website instance * Put flags to separate files * wrong flag * Copy Yandex.Metrica introduction from main page to docs * Yet another home page structure change, couple new blocks (CLICKHOUSE-3045) * Update Contacts section * CLICKHOUSE-2849: more detailed legal information * CLICKHOUSE-2978 preparation - split by files * More changes in Contacts block * Tune texts on index page * update presentations * One more benchmark * Add usage sections to index page, adapted from slides * Get the roadmap started, based on slides from last ClickHouse Meetup * CLICKHOUSE-2977: some rendering tuning * Get rid of excessive section in the end of getting started * Make headers linkable * CLICKHOUSE-2981: links to editing reference - https://github.com/yandex/ClickHouse/issues/849 * CLICKHOUSE-2981: fix mobile styles in docs * Ban crawling of duplicating docs * Open some external links in new tab * Ban old docs too * Lots of trivial fixes in english docs * Lots of trivial fixes in russian docs * Remove getting started copies in markdown * Add Yandex.Webmaster * Fix some sphinx warnings * More warnings fixed in english docs * More sphinx warnings fixed * Add code-block:: text * More code-block:: text * These headers look not that well * Better switch between documentation languages * merge use_case.rst into ya_metrika_task.rst * Edit the agg_functions.rst texts * Add lost empty lines
53 lines
3.1 KiB
ReStructuredText
53 lines
3.1 KiB
ReStructuredText
Functions for searching strings
|
|
-------------------------------
|
|
The search is case-sensitive in all these functions.
|
|
The search substring or regular expression must be a constant in all these functions.
|
|
|
|
position(haystack, needle)
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
Searches for the 'needle' substring in the 'haystack' string.
|
|
Returns the position (in bytes) of the found substring, starting from 1, or returns 0 if the substring was not found.
|
|
There's also positionCaseInsensitive function.
|
|
|
|
positionUTF8(haystack, needle)
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
The same as 'position', but the position is returned in Unicode code points. Works under the assumption that the string contains a set of bytes representing a UTF-8 encoded text. If this assumption is not met, it returns some result (it doesn't throw an exception).
|
|
There's also positionCaseInsensitiveUTF8 function.
|
|
|
|
match(haystack, pattern)
|
|
~~~~~~~~~~~~~~~~~~~~~~~~
|
|
Checks whether the string matches the 'pattern' regular expression.
|
|
The regular expression is re2.
|
|
Returns 0 if it doesn't match, or 1 if it matches.
|
|
|
|
Note that the backslash symbol (``\``) is used for escaping in the regular expression. The same symbol is used for escaping in string literals.
|
|
So in order to escape the symbol in a regular expression, you must write two backslashes (``\\``) in a string literal.
|
|
|
|
The regular expression works with the string as if it is a set of bytes.
|
|
The regular expression can't contain null bytes.
|
|
For patterns to search for substrings in a string, it is better to use LIKE or 'position', since they work much faster.
|
|
|
|
extract(haystack, pattern)
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
Extracts a fragment of a string using a regular expression. If 'haystack' doesn't match the 'pattern' regex, an empty string is returned. If the regex doesn't contain subpatterns, it takes the fragment that matches the entire regex. Otherwise, it takes the fragment that matches the first subpattern.
|
|
|
|
extractAll(haystack, pattern)
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
Extracts all the fragments of a string using a regular expression. If 'haystack' doesn't match the 'pattern' regex, an empty string is returned. Returns an array of strings consisting of all matches to the regex. In general, the behavior is the same as the 'extract' function (it takes the first subpattern, or the entire expression if there isn't a subpattern).
|
|
|
|
like(haystack, pattern), оператор haystack LIKE pattern
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
Checks whether a string matches a simple regular expression. The regular expression can contain the metasymbols ``%`` and ``_``.
|
|
|
|
``%`` indicates any quantity of any bytes (including zero characters).
|
|
|
|
``_`` indicates any one byte.
|
|
|
|
Use the backslash (``\``) for escaping metasymbols. See the note on escaping in the description of the 'match' function.
|
|
|
|
For regular expressions like%needle%, the code is more optimal and works as fast as the 'position' function. For other regular expressions, the code is the same as for the 'match' function.
|
|
|
|
notLike(haystack, pattern), оператор haystack NOT LIKE pattern
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
The same thing as 'like', but negative.
|