Currently, any datatypes that are not in the allow list
https://supabase.github.io/pg_graphql/reflection/#type-conve...
are cast as strings, but prioritizing a JSON conversion if one is available is a great idea that we'll look into
https://supabase.github.io/pg_graphql/reflection/#type-conve...
are cast as strings, but prioritizing a JSON conversion if one is available is a great idea that we'll look into
https://www.postgresql.org/docs/current/sql-createcast.html
There are some weird permissions issues to work out IIRC, but this allows the user to specify how the json should be marshalled, and then can be implicitly or explicitly used by any sql statements. This is how PostgREST solves this problem, and I currently have a few custom casts created for range and multirange datatypes through my PostgREST server.