From 1282d3a2709064cb847b8757409a7153449faa9d Mon Sep 17 00:00:00 2001 From: Alexandre Alapetite Date: Wed, 22 Oct 2025 21:21:17 +0200 Subject: PostgreSQL: compatibility with PCRE word boundary (#8141) Allow the use of regex `\b` for word boundary (and `\B` for the opposite) even when using PostgreSQL. Follow up of: * https://github.com/FreshRSS/FreshRSS/pull/6706 For instance, `intitle:/\bnew\B/` will find *newest* but not *new* nor *renewal*. Useful in particular to minimise the differences between PHP and database in: * https://github.com/FreshRSS/FreshRSS/pull/7959 --- docs/en/users/10_filter.md | 2 ++ 1 file changed, 2 insertions(+) (limited to 'docs/en') diff --git a/docs/en/users/10_filter.md b/docs/en/users/10_filter.md index 742a22413..bb90f9925 100644 --- a/docs/en/users/10_filter.md +++ b/docs/en/users/10_filter.md @@ -155,6 +155,8 @@ As opposed to normal searches, special XML characters `<&">` are not escaped in * [For MariaDB](https://mariadb.com/kb/en/pcre/); * [For MySQL](https://dev.mysql.com/doc/refman/9.0/en/regexp.html#function_regexp-like). +> ℹ️ Even with PostgreSQL, you are welcome to use `\b` for word boundary (and `\B` for the opposite), as there is an automatic translation to `\y` and `\Y`. + ## By sorting by date You can change the sort order by clicking the toggle button available in the header. -- cgit v1.2.3