Very slight errors on the
search syntax page:
In the paragraph text for sections Searching Through Other Fields and Numeric Range Queries, the links go to invalid searches that have an asterisk instead of a colon in the query. In addition to the aforementioned typo, “score.gte:100” links to a search for “gt” not “gte”. (The links within the table of Numeric Range Queries are all fine.)
[Update: fixed]
Within the table of
Date/Time Range Queries, the example query “created_at:2015-04-03:00” fails with the error “Oops, there was an error evaluating your query: expected a RFC3339 datetime fragment, like `2019-01-01’, or relative date, like `3 days ago’, starting at: -04-03:00”
I would guess the last dash needs to be a plus.
[Update: still in error 2021 Oct 05]
In the section
Escaping Special Characters, the example for escaping is “\-_-” but no images actually have that tag; perhaps it would be better to use “\- -” or “\-.-”
1
[Update: unchanged thru 2021 Oct 05]
The example
Approximate (Fuzzy) String Matching text is
fluttersho~0.8
but links to a search for
fluttersho~1.0
[Update: still in error 2021 Oct 05 plus more]
In the section
Boosting Terms, the example searches have the parameter
&sf=relevance
in their URLs, but this does not lead to a search sorted by relevance because the actual parameter string the site uses for a sort-by-relevance is
&sf=_score
[Update: still in error 2021 Oct 05]
———————
1 An oddity here is that when visiting
the tag page for one of these escaping-needed tags, the search field is auto-populated with a query beginning with a double-escape (eg. “\\- -”) but if you
attempt to perform that search, it does not return any results, whereas
a query with one escape (eg. “\- -”) succeeds.
[Update: still in error 2021 Oct 05]