supabase / supabase / 42192289172

87%

push

github

Joshenlim/fe 4721 cmd k support searching for triggers (#52755)

## Context

Building off from
[here](https://github.com/supabase/supabase/pull/52751) to make Cmd+K
resource-aware so finding and inspecting anything in a project doesn't
depend on knowing where it lives in the dashboard.

Specifically looking into database entities for now - end state would be
that you could search for a table name for example, and Cmd K will pull
up everything related to that table for you to skim (e.g Policies,
Functions, Triggers, etc). Changes in this PR sets up searching for
**database triggers**, and will probably be the last database entity
that we'll add into context aware cmd K for now given that we'll have
tables, policies, functions and triggers which are the primary building
blocks for a project.

<img width="500" alt="image"
src="https://github.com/user-attachments/assets/242ec517-88cd-4f3d-96ce-741edaa8560d"
/>

Triggers will also match if it's function matches the search input, and
its description will tweak slightly as well
<img width="500" alt="image"
src="https://github.com/user-attachments/assets/65f515df-b875-4b92-95b7-00389d8a070b"
/>

## Performance

Had Claude do some benchmarking against `getSearchEntitiesSql` (`EXPLAIN
ANALYZE`, median of 5 runs, local Postgres, warm cache) on one synthetic
catalog:
- 12,000 tables (36,651 `pg_class`), 6,001 policies, 27,261 `pg_proc`
(12,000 user + 12,000 extension-owned functions), 56,304 `pg_trigger`
- 3,500 user triggers, 500 of which run one shared function; the rest
are internal FK triggers
  - 297,921 `pg_depend`.

Compared against master (tables + policies) and the functions PR (before
triggers).

| Search | What it exercises | master | functions PR | this PR | Δ this
PR |
|---|---|---|---|---|---|
| `t_1` | broad table match | 12ms | 26ms | 30ms | +4ms |
| `p_1` | broad policy-name match | 15ms | 27ms | 35ms | +8ms |
| `fn_1` | broad function match | 10ms | 26ms | 33ms | +7ms |
| `trg_1` | broad trigger... (continued)

2048 of 2417 branches covered (84.73%)

Branch coverage included in aggregate %.

2845 of 3205 relevant lines covered (88.77%)

201.2 hits per line