hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-14 17:02:49 +03:00
Code Issues Projects Releases Wiki Activity

grammar corrections (#782)

Browse Source
This commit is contained in:
Mayank Raj 2018-10-20 08:52:13 +05:30 committed by Shahidh K Muhammed
parent c13f679766
commit d561ba2bd2
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/graphql/manual/auth/basics.rst
View File

@ -4,7 +4,7 @@ Access control basics
In this section, we're going to set up a simple access control rule for restricting querying on a table.
We're working with a simple ``author`` table where users have some information stored about themselves.
Create a author table
Create an author table
---------------------
Head to your console and create an ``author`` table with the following columns:

2
docs/graphql/manual/schema/relationships/index.rst
View File

@ -17,7 +17,7 @@ an ``author`` and "``author``" of an ``article``.
Creating relationships
----------------------
Typically relationships are defined using foreign-key constraints. But in some cases, it might not be possible to
Typically, relationships are defined using foreign-key constraints. But in some cases, it might not be possible to
use foreign-key constraints to create the relation. For example, while trying to create a relationship involving a view
as foreign-keys can't be created on views.

4
docs/graphql/manual/troubleshooting/index.rst
View File

@ -5,9 +5,9 @@ Hasura GraphQL engine may not work as expected and will throw unexpected errors
the GraphQL engine are altered using ``psql`` or any other PostgreSQL client.
Hasura GraphQL engine creates and maintains an **internal state** based on the database it is configured to use.
This internal state will comprise of information about the tables/views, relationships and access control rules
This internal state will comprise information about the tables/views, relationships and access control rules
defined on them using Hasura GraphQL engine. See :doc:`Hasura GraphQL engine internals <../engine-internals/index>`
for information on how this internal state is maintained. It is highly recommended to do any modifications to the
for information on how this internal state is maintained. It is highly recommended doing any modifications to the
database schema only through Hasura console to avoid corrupting the GraphQL engine's state.
Following are the list of error messages returned by the GraphQL Engine when it encounters an inconsistent state: