server: mutation fails when we pass non-default value for ENUM where ENUM and table are defined in non-public schema about graphql-engine

[plcplc]

Unfortunately, the graphql-engine does not track the schema that types are defined in.
This is an inherent shortcoming of how user-defined types are managed in Hasura v2. We are however going to improve this for Hasura V3, which is currently available in an alpha version: https://hasura.io/docs/3.0/local-dev/.

This issue will now be reviewed and tracked as part of the Hasura V3 roadmap.

In as much as this is practical in your specific case, a workaround is to set the search_path config option to include the schema where the type is defined. Use e.g. the sql command ALTER ROLE <your-pg-user-name> SET search_path TO public, user. (where user is the schema the enum type lives in).