After which ctrl+f " in" takes you to the correct chapters. I do agree that a direct link would be more helpful.
And for learning postgresql I agree it isn't very helpful - using their tutorial links, w3schools or something like udemy if you prefer video format is the way to go in that use case.
I remember back when you were told to learn to work with the documentation, not memorize it, because you will always have access to it as a reference. Maybe bookmarking reference books/documentation will make a come back as the search engines degrade.
Surely the word 'in' would appear countless times out of context on the table of contents.
You can press alt-w though to only show full word matches
" in" appears 25 times on the page to be exact, with 16 of those being in the table of contents and 9 being in the text afterwards.
"in" appears 54 times, as you know end up hitting "string" and so on.
Had I known that the functions table of contents was as short as it is I would probably have just scrolled.
This is partly why I prefer Firefox's implementation of the find feature - it allows case-sensitive search while Chrome does not support it.
After which ctrl+f " in" takes you to the correct chapters. I do agree that a direct link would be more helpful.
And for learning postgresql I agree it isn't very helpful - using their tutorial links, w3schools or something like udemy if you prefer video format is the way to go in that use case.
I remember back when you were told to learn to work with the documentation, not memorize it, because you will always have access to it as a reference. Maybe bookmarking reference books/documentation will make a come back as the search engines degrade.
Surely the word 'in' would appear countless times out of context on the table of contents.
You can press alt-w though to only show full word matches
" in" appears 25 times on the page to be exact, with 16 of those being in the table of contents and 9 being in the text afterwards.
"in" appears 54 times, as you know end up hitting "string" and so on.
Had I known that the functions table of contents was as short as it is I would probably have just scrolled.
This is partly why I prefer Firefox's implementation of the find feature - it allows case-sensitive search while Chrome does not support it.