mirror of
https://github.com/postgres/postgres.git
synced 2025-04-24 10:47:04 +03:00
Doc: improve documentation of websearch_to_tqsuery().
It wasn't totally clear about punctuation other than what's specified being ignored. Pavel Borisov and Tom Lane Discussion: https://postgr.es/m/CALT9ZEFsBdsogVjG40Z4KfM1Um=wj1FE9hJ00GK3oVfzz0sFNg@mail.gmail.com
This commit is contained in:
parent
f057980149
commit
459f4076c8
@ -11381,11 +11381,12 @@ CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow', 'green', 'blue', 'purple
|
||||
<replaceable>query</replaceable> <type>text</type> )
|
||||
<returnvalue>tsquery</returnvalue>
|
||||
<?br?>
|
||||
Converts text to a <type>tsquery</type>, normalizing words according to
|
||||
the specified or default configuration. Quoted word sequences are
|
||||
converted to phrase tests, and the word <quote>or</quote> is
|
||||
understood as producing an OR operator. This approximates the
|
||||
behavior of some common web search tools.
|
||||
Converts text to a <type>tsquery</type>, normalizing words according
|
||||
to the specified or default configuration. Quoted word sequences are
|
||||
converted to phrase tests. The word <quote>or</quote> is understood
|
||||
as producing an OR operator, and a dash produces a NOT operator;
|
||||
other punctuation is ignored.
|
||||
This approximates the behavior of some common web search tools.
|
||||
<?br?>
|
||||
<literal>websearch_to_tsquery('english', '"fat rat" or cat dog')</literal>
|
||||
<returnvalue>'fat' <-> 'rat' | 'cat' & 'dog'</returnvalue>
|
||||
|
@ -913,7 +913,7 @@ SELECT plainto_tsquery('english', 'The Fat & Rats:C');
|
||||
'fat' & 'rat' & 'c'
|
||||
</screen>
|
||||
|
||||
Here, all the input punctuation was discarded as being space symbols.
|
||||
Here, all the input punctuation was discarded.
|
||||
</para>
|
||||
|
||||
<indexterm>
|
||||
@ -969,16 +969,16 @@ websearch_to_tsquery(<optional> <replaceable class="parameter">config</replaceab
|
||||
syntax in which simple unformatted text is a valid query.
|
||||
Unlike <function>plainto_tsquery</function>
|
||||
and <function>phraseto_tsquery</function>, it also recognizes certain
|
||||
operators. Moreover, this function should never raise syntax errors,
|
||||
operators. Moreover, this function will never raise syntax errors,
|
||||
which makes it possible to use raw user-supplied input for search.
|
||||
The following syntax is supported:
|
||||
|
||||
<itemizedlist spacing="compact" mark="bullet">
|
||||
<listitem>
|
||||
<para>
|
||||
<literal>unquoted text</literal>: text not inside quote marks will be
|
||||
converted to terms separated by <literal>&</literal> operators, as
|
||||
if processed by
|
||||
<function>plainto_tsquery</function>.
|
||||
if processed by <function>plainto_tsquery</function>.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
@ -990,18 +990,26 @@ websearch_to_tsquery(<optional> <replaceable class="parameter">config</replaceab
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<literal>OR</literal>: logical or will be converted to
|
||||
<literal>OR</literal>: the word <quote>or</quote> will be converted to
|
||||
the <literal>|</literal> operator.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<literal>-</literal>: the logical not operator, converted to the
|
||||
<literal>-</literal>: a dash will be converted to
|
||||
the <literal>!</literal> operator.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
Other punctuation is ignored. So
|
||||
like <function>plainto_tsquery</function>
|
||||
and <function>phraseto_tsquery</function>,
|
||||
the <function>websearch_to_tsquery</function> function will not
|
||||
recognize <type>tsquery</type> operators, weight labels, or prefix-match
|
||||
labels in its input.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Examples:
|
||||
<screen>
|
||||
|
Loading…
x
Reference in New Issue
Block a user