public inbox for [email protected]
help / color / mirror / Atom feedOnline Documentation Search Issue
3+ messages / 3 participants
[nested] [flat]
* Online Documentation Search Issue
@ 2021-05-17 15:43 PG Doc comments form <[email protected]>
2021-05-17 16:14 ` Re: Online Documentation Search Issue Karoline Pauls <[email protected]>
0 siblings, 1 reply; 3+ messages in thread
From: PG Doc comments form @ 2021-05-17 15:43 UTC (permalink / raw)
To: [email protected]; +Cc: [email protected]
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/functions-comparison.html
Description:
Hi,
Just an FYI, but I'm running into a somewhat annoying issue with the
documentation search that I'm not sure you're aware of.
Namely, searching for "BETWEEN" (upper or lowercase) yields zero results.
Trying a few different search queries right now, it appears I might be just
running into an issue where my query is a stopword, but in this case it's
particularly frustrating because (even once I realize that) there is no
obvious alternative search query. (I wouldn't have thought to search for
"Comparison Functions", the page where it's actually explained.)
Is there any way your search platform can be set to index all text that
appears in the documentation inside 'code' tags? Or could some sort of
suggestion bar be added to the results page so that if a query contains a
keyword (especially if it consists entirely of the keyword), a link is
presented to go to it's page?
Barring that, could searching a stopword trigger a message (and perhaps a
link to search it on Google) other than just "no results found"?
Thanks,
Mike
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Online Documentation Search Issue
2021-05-17 15:43 Online Documentation Search Issue PG Doc comments form <[email protected]>
@ 2021-05-17 16:14 ` Karoline Pauls <[email protected]>
2021-05-18 06:56 ` Re: Online Documentation Search Issue Laurenz Albe <[email protected]>
0 siblings, 1 reply; 3+ messages in thread
From: Karoline Pauls @ 2021-05-17 16:14 UTC (permalink / raw)
To: [email protected]; [email protected]
HAVING is another stop-word.
-------- Original Message --------
On 17 May 2021, 16:43, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/13/functions-comparison.html
> Description:
>
> Hi,
> Just an FYI, but I'm running into a somewhat annoying issue with the
> documentation search that I'm not sure you're aware of.
> Namely, searching for "BETWEEN" (upper or lowercase) yields zero results.
>
> Trying a few different search queries right now, it appears I might be just
> running into an issue where my query is a stopword, but in this case it's
> particularly frustrating because (even once I realize that) there is no
> obvious alternative search query. (I wouldn't have thought to search for
> "Comparison Functions", the page where it's actually explained.)
>
> Is there any way your search platform can be set to index all text that
> appears in the documentation inside 'code' tags? Or could some sort of
> suggestion bar be added to the results page so that if a query contains a
> keyword (especially if it consists entirely of the keyword), a link is
> presented to go to it's page?
>
> Barring that, could searching a stopword trigger a message (and perhaps a
> link to search it on Google) other than just "no results found"?
>
> Thanks,
> Mike
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Online Documentation Search Issue
2021-05-17 15:43 Online Documentation Search Issue PG Doc comments form <[email protected]>
2021-05-17 16:14 ` Re: Online Documentation Search Issue Karoline Pauls <[email protected]>
@ 2021-05-18 06:56 ` Laurenz Albe <[email protected]>
0 siblings, 0 replies; 3+ messages in thread
From: Laurenz Albe @ 2021-05-18 06:56 UTC (permalink / raw)
To: Karoline Pauls <[email protected]>; [email protected]; [email protected]
On Mon, 2021-05-17 at 16:14 +0000, Karoline Pauls wrote:
>
> On 17 May 2021, 16:43, PG Doc comments form < [email protected]> wrote:
> > Just an FYI, but I'm running into a somewhat annoying issue with the
> > documentation search that I'm not sure you're aware of.
> > Namely, searching for "BETWEEN" (upper or lowercase) yields zero results.
> >
> > Trying a few different search queries right now, it appears I might be just
> > running into an issue where my query is a stopword, but in this case it's
> > particularly frustrating because (even once I realize that) there is no
> > obvious alternative search query. (I wouldn't have thought to search for
> > "Comparison Functions", the page where it's actually explained.)
> >
> > Is there any way your search platform can be set to index all text that
> > appears in the documentation inside 'code' tags? Or could some sort of
> > suggestion bar be added to the results page so that if a query contains a
> > keyword (especially if it consists entirely of the keyword), a link is
> > presented to go to it's page?
> >
> > Barring that, could searching a stopword trigger a message (and perhaps a
> > link to search it on Google) other than just "no results found"?
>
> HAVING is another stop-word.
I find 518 lines with "between" in the documentation, so I am not sure if
removing that stopword would be beneficial.
But there is an index for the documentation:
https://www.postgresql.org/docs/current/bookindex.html#indexdiv-B
"BETWEEN" is in the index.
So is "HAVING". Removing "HAVING" as a stopword would mean indexing
"have", and that is obviously not going to help anybody.
Yours,
Laurenz Albe
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2021-05-18 06:56 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2021-05-17 15:43 Online Documentation Search Issue PG Doc comments form <[email protected]>
2021-05-17 16:14 ` Karoline Pauls <[email protected]>
2021-05-18 06:56 ` Laurenz Albe <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox