From 7561bb0c392b71316b81ebc14af227c64967e331 Mon Sep 17 00:00:00 2001 From: dc Date: Wed, 16 Sep 2026 23:42:45 +0000 Subject: [PATCH] feed: correct the case sensitivity example in the full table search post The post claimed `smith` finds `Smithson`, which only holds for a case insensitive match. The comparison is case sensitive, so the search term has to match the case as stored: `Smith` finds `Smithson`, and `smith` finds `Goldsmith`, but `smith` will not find `Smithson`. --- content/feed/full-table-search/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/feed/full-table-search/index.md b/content/feed/full-table-search/index.md index dedf1a4..da5088d 100644 --- a/content/feed/full-table-search/index.md +++ b/content/feed/full-table-search/index.md @@ -17,7 +17,7 @@ Finding a value in a large table usually means writing a query first: guess whic The search box sits in the Viewer toolbar, next to a **Numeric** checkbox: -- **Text search** matches part of a value, so `smith` finds `Smithson` and `Goldsmith`. The comparison is case sensitive, using the SASĀ® `CONTAINS` operator. +- **Text search** matches part of a value, so `Smith` finds `Smithson` and `smith` finds `Goldsmith`. The comparison is case sensitive, using the SASĀ® `CONTAINS` operator, so `smith` will not find `Smithson`. - **Numeric search** (tick the box) matches the number exactly against every numeric column in the table. Whichever you use, the results are ordinary rows in the Viewer, with the rest of the screen behaving exactly as it does for a normal view.