From 42c566b19bb0b0335eb1fa83d34936742c65d57a Mon Sep 17 00:00:00 2001 From: Matt Westcott Date: Wed, 24 Jul 2024 17:04:12 +0100 Subject: [PATCH] Remove note about database search not ordering by relevance This text existed since Wagtail 1.x and is referring to the original database backend that just did substring matches (which is now the fallback backend), before we supported database-backed full-text search. --- docs/topics/search/searching.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/topics/search/searching.md b/docs/topics/search/searching.md index b551c47cc1..ccf1510b4e 100644 --- a/docs/topics/search/searching.md +++ b/docs/topics/search/searching.md @@ -128,7 +128,7 @@ The search operator specifies how the search should behave when the user has typ Both operators have benefits and drawbacks. The "or" operator will return many more results but will likely contain a lot of results that aren't relevant. The "and" operator only returns results that contain all search terms but requires the user to be more precise with their query. -We recommend using the "or" operator when ordering by relevance and the "and" operator when ordering by anything else (note: the database backend doesn't currently support ordering by relevance). +We recommend using the "or" operator when ordering by relevance and the "and" operator when ordering by anything else. Here's an example of using the `operator` keyword argument: