supabase / supabase-flutter / 39595018290

92%

push

github

feat(typegen)!: read int2vector and oidvector columns as integer lists (#1996)

## Summary

`int2vector` and `oidvector` columns generated `Object?`. PostgREST
sends them as JSON arrays: numbers for `int2vector` (`[1,2]`) and
strings for `oidvector` (`["1","2"]`). They now generate `List<int>`.

They cannot be written or filtered as an ordinary list column, as
checked on the local stack:

- In a filter, every operator (`eq`, `cs`, `ov`, `in`, `gt`) only
accepts the space-separated literal these types read, `1 2`. The array
literal `{1,2}` that a list column sends fails with 22P02.
- A JSON array write is accepted, but it stores a vector that then fails
equality with the same value. Writes have to send the `1 2` text too.

So, like the pgvector columns, they get column classes of their own:
`PostgrestIntegerVectorColumn` and
`PostgrestNullableIntegerVectorColumn`. Any list operand on them,
including each member of an `inFilter`, is sent as the space-separated
literal. Generated setters write `values.join(' ')`. Getters read the
array, parsing string elements for `oidvector`.

Arrays of these types (`int2vector[]`) arrive as nested JSON arrays, so
their elements stay `Object`.

## Breaking change

Regenerated getters for these columns change from `Object?` to
`List<int>`.

## Tests

- The parser test now expects the new kind for both types.
- Fixture columns, regenerated goldens, and a behavior test covering
read, write, `eq` and `contains`.
- `catalog_values` gains `int2vector` and `oidvector` columns. A
postgrest integration test writes them and then reads them back through
`eq`, `contains` and `inFilter` against the local stack.
- The SDK compliance symbol, drift and schema checks pass locally.

## Also in this PR

- Typed streams now send a vector or integer vector operand, and each
`inFilter` member, as its literal, to both the initial PostgREST query
and the realtime filter. Before, the raw list reached both. This covers
pgvector columns too.
- A ... (continued)

40 of 48 new or added lines in 5 files covered. (83.33%)

10305 of 11207 relevant lines covered (91.95%)

5.47 hits per line