supabase / mcp / 41833926218

98%

push

github

fix(pg-meta): report partition FKs once and add partition_of to list_tables (#508)

Closes #507

## What kind of change does this PR introduce?

Bug fix, plus an optional `partition_of` output field.

## What is the current behavior?

`list_tables` reports the FK clones Postgres creates for partitions as
separate foreign keys, so one FK is listed once per partition. Nothing
in the output marks a partition's parent.

## What is the new behavior?

The relationships subquery filters `conparentid = 0`, the predicate
`pg_dump` uses, so each FK is reported once. FKs declared directly on a
partition are still reported.

Partitions carry `partition_of`, their immediate parent in the same
`schema.name` format as `name`, in both compact and verbose output:

```jsonc
{ "name": "public.events_2025", "rls_enabled": false, "rows": 0, "partition_of": "public.events" }
```

A sub-partition points to its own parent, not the root. Other tables
omit the field, including `INHERITS` children. A partition still names
its parent when the parent's schema isn't in `schemas`, as
`target_table` already does.

No change to tool names, descriptions or input schemas. `partition_of`
is optional in the output schema. Databases without partitioned tables
get identical output.

## How to Review

1. **Query**
   - `packages/mcp-server-supabase/src/pg-meta/tables.sql`
- One predicate in the relationships subquery. `conparentid` rather than
`relispartition`, which would also hide FKs declared on or pointing at a
partition.
- One scalar subquery for `partition_of`. It filters the parent on
`relkind = 'p'`, because `INHERITS` children also have `pg_inherits`
rows.

2. **Output**
- `packages/mcp-server-supabase/src/pg-meta/types.ts`,
`packages/mcp-server-supabase/src/tools/database-operation-tools.ts`
   - `partition_of` is omitted when null, like `comment`.

3. **Tests**
- `packages/mcp-server-supabase/src/server.database.test.ts`, next to
the composite-FK tests:
- Clones on both sides of ... (continued)

1099 of 1156 branches covered (95.07%)

Branch coverage included in aggregate %.

4 of 4 new or added lines in 2 files covered. (100.0%)

5809 of 5915 relevant lines covered (98.21%)

172.69 hits per line