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
Computed query doesn't appear in graphql schema, if it returns a setof a table that is annotated with @omit
Steps to reproduce
Create a table and annotate it with a plain @omit, and use this table as return type for a computed query function.
Expected results
The computed query to appear on the graphql schema.
Actual results
The computed query does not appear on the graphql schema
Possible solutions
Initially I thought it could be solved by "translating" @omit to @behavior -* +select +table but unfortunately the computed query also "inherits" the behavior of the returned type, including -* which implicates -queryField:resource:connection. But translating @omit to @behavior -* +select +table +queryField:resource:connection would also be incorrect, when the @omit was used for a function.
So, maybe adding context to the method processTags of what kind of entity (pgClass, pgAttr, etc.) to process the tags for, might be a solutions here.
The text was updated successfully, but these errors were encountered:
Summary
Computed query doesn't appear in graphql schema, if it returns a
setof
a table that is annotated with@omit
Steps to reproduce
Create a table and annotate it with a plain
@omit
, and use this table as return type for a computed query function.Expected results
The computed query to appear on the graphql schema.
Actual results
The computed query does not appear on the graphql schema
Possible solutions
Initially I thought it could be solved by "translating"
@omit
to@behavior -* +select +table
but unfortunately the computed query also "inherits" the behavior of the returned type, including-*
which implicates-queryField:resource:connection
. But translating@omit
to@behavior -* +select +table +queryField:resource:connection
would also be incorrect, when the@omit
was used for a function.So, maybe adding context to the method
processTags
of what kind of entity (pgClass
,pgAttr
, etc.) to process the tags for, might be a solutions here.The text was updated successfully, but these errors were encountered: