-- Fixed 1⃣
* Search with Special Characters - Fixed search failure when querying for commands containing special characters
* IP addresses (e.g., 10.104.113.39) now work correctly
* URLs (e.g., https://api.github.com) are fully supported
* File paths with dots (e.g., ./config/settings.yaml) search successfully
* Email addresses and other special character combinations work properly
* Added automatic FTS5 query sanitization by wrapping queries in quotes
* Implemented fallback to SQL LIKE search for edge cases where FTS5 still fails
* Error: "fts5: syntax error near "."" is now resolved
-- Added 2⃣
* sanitize_fts5_query() helper function for safe FTS5 queries
search_with_like() fallback method for robustness
* 7 new test cases for special character searches (98 total tests)
* Architecture Decision Record: ADR-001: FTS5 Query Sanitization
-- Changed 3⃣
All search queries now use exact phrase matching for better accuracy
Search is now more robust with multi-layered fallback mechanisms
This is my own personal daily driver and the aim is to keep it minimal, open and secure. It's not trying to compete, it's only trying to defeat - my own brain fog :)
danebalia•4w ago
-- Added 2⃣ * sanitize_fts5_query() helper function for safe FTS5 queries search_with_like() fallback method for robustness * 7 new test cases for special character searches (98 total tests) * Architecture Decision Record: ADR-001: FTS5 Query Sanitization
-- Changed 3⃣ All search queries now use exact phrase matching for better accuracy Search is now more robust with multi-layered fallback mechanisms
This is my own personal daily driver and the aim is to keep it minimal, open and secure. It's not trying to compete, it's only trying to defeat - my own brain fog :)