2018-09-11 14:11:24 +03:00
|
|
|
Schema
|
|
|
|
|
======
|
|
|
|
|
|
|
|
|
|
Hasura GraphQL engine automatically generates your GraphQL schema and resolvers based on your tables/views
|
2018-10-10 09:32:03 +03:00
|
|
|
in Postgres. **You don't need to write a GraphQL schema or resolvers.**
|
2018-09-11 14:11:24 +03:00
|
|
|
|
2018-10-16 09:32:29 +03:00
|
|
|
The Hasura console gives you UI tools that speed up your data-modeling process, or working with your existing database.
|
2018-09-11 14:11:24 +03:00
|
|
|
The console also automatically generates migrations or metadata files that you can edit directly and check into your
|
|
|
|
|
version control.
|
|
|
|
|
|
|
|
|
|
Hasura GraphQL engine lets you do anything you would usually do with Postgres by giving you GraphQL over native
|
|
|
|
|
Postgres constructs.
|
|
|
|
|
|
|
|
|
|
See:
|
|
|
|
|
^^^^
|
|
|
|
|
|
|
|
|
|
.. toctree::
|
|
|
|
|
:maxdepth: 1
|
|
|
|
|
|
|
|
|
|
Basics <basics>
|
|
|
|
|
Relationships <relationships/index>
|
|
|
|
|
Customise with views <views>
|
2018-11-06 11:37:17 +03:00
|
|
|
Default field values <default-values/index>
|
2018-09-11 14:11:24 +03:00
|
|
|
Enum type fields <enums>
|
|
|
|
|
Using an existing database <using-existing-database>
|
|
|
|
|
Export GraphQL schema <export-graphql-schema>
|
|
|
|
|
How schema generation works <how-it-works>
|
