How to have ID type in schema for primary keys?

Hi,

it seems that Hasura doesn’t generate the graphql type ID (https://graphql.github.io/graphql-spec/June2018/#sec-ID) for primary keys. Instead it generates a scalar type matching the type of the primary key in the database.

So, in case my primary key is a bigint then in the schema I will have

scalar bigint

type todo {
  id: bigint!
  ...
}

The problem is that other tools (eg. https://github.com/mobxjs/mst-gql) depend on the existence of a unique identifier for types and expects it to be the one field with type ID.

Would it be possible to have a Hasura server setting / environment variable, which enables generation of ID types for primary fields instead of the default mechanism?

[philschonholzer]

The new Remote Relationships with v1.3 do not work with Sanity.io because their id’s are of type ID! which Hasura does not support. Using another type like uuid! gets you an exception when trying to create a new remote relationships:

[
    {
        "definition": {
            "remote_field": {
                "allPackages": {
                    "arguments": {
                        "where": {
                            "_id": {
                                "eq": "$package_id"
                            }
                        }
                    }
                }
            },
            "name": "Package_ID",
            "hasura_fields": [
                "package_id"
            ],
            "remote_schema": "Sanity",
            "table": {
                "schema": "public",
                "name": "Orders"
            }
        },
        "reason": "in table \"Orders\": in remote relationship\"Package_ID\": cannot validate remote relationship because expected type \"ID\" but got \"uuid\"",
        "type": "remote_relationship"
    }
]

A possible solution would be to define the type that is needed by a remote schema (like ID!)

[adrien-mg]

Do we have any update on this? This is a blocker for us too trying to integrate with Strapi which uses ID as a type for its collections 😞

in table "origin_table": in remote relationship "remote_table": cannot validate remote relationship because expected type "ID" but got "Int"