pyr0ball
db359d35b2
Both log_fts and log_entries have timestamp_iso, severity, source_id, and matched_patterns columns. After the JOIN, unqualified references to any of these caused SQLite to raise 'ambiguous column name', silently falling back to the non-FTS scan path on every time-filtered or severity-filtered query. Prefix all filter conditions that touch FTS-mirror columns with f. to resolve the ambiguity. The e. prefix on tenant_id was already correct since tenant_id is not present in the FTS virtual table. |
||
|---|---|---|
| .. | ||
| api | ||
| context | ||
| db | ||
| glean | ||
| services | ||
| tasks | ||
| watch | ||
| __init__.py | ||
| mcp_server.py | ||
| rest.py | ||