Pain point · API & developer experience · Blocks work
NOT NULL columns are not marked required in the generated schema
2 source threads · first seen 2019-01 · last seen 2019-04
Summary
Non-nullable database columns are not exposed as required fields in the GraphQL schema, which the user finds surprising.
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“Every field of a schema generated from SQL View is nullable/optional even though the underlying table might have NOT NULL fields”
“Not nullable fields in the database are not exposed through the graphql schema as required”