You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug The Supabase GraphQL documentation mentions the possibility to enable aggregate fields using table comments (see: https://supabase.com/docs/guides/graphql/configuration#aggregate). However, when attempting to enable it on a Supabase Cloud project, the feature does not appear in the schema. This looks like either:
the feature is not yet released despite being documented, or
there is a bug in the extension where the configuration is silently ignored.
To Reproduce Steps to reproduce the behavior:
On Supabase Cloud, with pg_graphql v1.5.11 (Postgres 17.4.1.074), open the SQL Editor.
Run:
comment on table "TableName" is e'@graphql({"aggregate": {"enabled": true}})';
Go to the GraphQL schema explorer in Supabase Studio or introspect the schema via GraphQL.
Notice that the aggregate field is not exposed on the type.
Expected behavior The GraphQL schema should expose an aggregate field on the BlogPost type when aggregate.enabled = true, as described in the documentation.
Screenshots No SQL error is returned when applying the comment, but the field is missing from the schema. Example from the GraphQL Explorer:
# Expected to see something like:aggregate {
count...
}
# But aggregate is not present.
Describe the bug The Supabase GraphQL documentation mentions the possibility to enable
aggregatefields using table comments (see: https://supabase.com/docs/guides/graphql/configuration#aggregate). However, when attempting to enable it on a Supabase Cloud project, the feature does not appear in the schema. This looks like either:To Reproduce Steps to reproduce the behavior:
aggregatefield is not exposed on the type.Expected behavior The GraphQL schema should expose an
aggregatefield on theBlogPosttype whenaggregate.enabled = true, as described in the documentation.Screenshots No SQL error is returned when applying the comment, but the field is missing from the schema. Example from the GraphQL Explorer:
Versions:
Additional context
aggregateas available, which creates confusion.Security This is not a security issue.