hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-09-21 07:28:26 +03:00
Code Issues Projects Releases Wiki Activity

docs: fix column type in migrations setup example

Browse Source 
GITHUB_PR_NUMBER: 8312
GITHUB_PR_URL: https://github.com/hasura/graphql-engine/pull/8312

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/3966
Co-authored-by: #кодеротбога <1025241+comerc@users.noreply.github.com>
GitOrigin-RevId: 0b085bddc7ed097000594f7a17425951d73deff8
This commit is contained in:
hasura-bot 2022-03-16 07:37:23 -07:00
parent 7eb59330b1
commit 250a280132
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/graphql/core/migrations/migrations-setup.rst
View File

@ -198,7 +198,7 @@ As you use the Hasura console UI served by the CLI to make changes to your schem
files are automatically generated in the ``migrations/`` directory and the metadata is
exported in the ``metadata/`` directory of your project.
Let's create the following table ``address (id uuid, street text, zip text, city text, country text, author_id int)``
Let's create the following table ``address (id uuid, street text, zip text, city text, country text, author_id uuid)``
and then create a foreign-key to the ``author`` table via the ``author_id -> id`` columns.
In the ``migrations/<database-name>`` directory, we can find new directories called ``<timestamp>_create_table_public_address``