Graphql error: enum type does not exist because case sensitivity was not recognized

I have an existing postgres DB with an enum (native Postgres enum type) named “enum_Motivations_desired_solution” on a table named “Motivations”. When I try to insert into the table, Hasura throws an error indicating it is looking for an enum of the same name but in lower case. If I re-name the enum in Postgres to be lower case, it solves the problem. The error: { “errors”: [ { “extensions”: { “path”: “$.selectionSet.insert_Interactions.args.objects[0].Motivations.data”, “code”: “constraint-error” }, “message”: “type "enum_motivations_desired_solution" does not exist” } ] }

The query:

mutation InteractionTest {
  insert_Interactions(objects: [
    {
      OwnerId: 5,
      forUserId: 1,
      initiatedByUserId: 1,
      Motivations: {
      data: [
        {
          desired_solution: "solution A",
          MotivatingFactors: {
            data: [{
              isCurrentFactor: true,
              commonFactor: "A"
            },
            {
              isCurrentFactor: true,
              commonFactor: "B"
            }]
          }
        }
      ]
    }
    }
  ]) {
    affected_rows
    returning {
      Motivations {
        desired_solution
        MotivatingFactors {
          commonFactor
          isCurrentFactor
        }
      }
    }
  }
}

[rakeshkky]

Hi @gentleShark , thank you for the detailed bug report, and for your patience whilst we fix it. I’m happy to say this has been fixed at https://github.com/hasura/graphql-engine/commit/d5610242542eb10c8d3ba825f2bd34fb23fb4faf, and will be available in the next stable release within two weeks.

[rakeshkky]

Additional context: We don’t generate GraphQL enum types out of Postgres enums instead we generate simple custom scalar type. We treat them as Unknown type and insert data with String literals ('').