docs: clarify quoted date-keyword phrases and dropped *_id field aliases

Add a sentence to the "Supported date keywords" advanced-search section
noting that multi-word date keywords must be quoted (e.g.
added:"previous month") -- whoosh-compat requires quoting where the
unquoted form used to work. Also document that the old undocumented
*_id field aliases (tag_id, owner_id, viewer_id, correspondent_id,
document_type_id, storage_path_id, type_id, path_id) are no longer
recognized: a query using one now silently folds to a literal-text
search instead of matching the intended structured field.
This commit is contained in:
Trenton Holmes committed 2026-08-18 11:05:04 -07:00
1 parent b48b1a7d08
commit a66237f614
1 file changed
+11
+11
View File
@@ -915,6 +915,14 @@ original_filename:invoice.pdf
- `original_filename` matches the filename of the document as originally
consumed.
Older, undocumented `*_id` field prefixes (`tag_id`, `owner_id`, `viewer_id`,
`correspondent_id`, `document_type_id`, `storage_path_id`, `type_id`, and
`path_id`) are no longer recognized advanced-search fields. A query using one
of them (e.g. `tag_id:5`) does not error; it silently falls back to a literal
text search for that string, which will almost never match real document
content. Use the corresponding named field (`tag`, `correspondent`,
`document_type`, etc.) instead.
Matching inexact words:
```
@@ -923,6 +931,9 @@ produ*name
Matching natural date keywords:
Multi-word date keywords must be quoted (e.g. `added:"previous month"`); an
unquoted multi-word keyword is not recognized as a date keyword.
```
added:today
modified:yesterday