mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-10-26 10:20:54 +03:00
docs: fix typo in config examples page
GITHUB_PR_NUMBER: 7634 GITHUB_PR_URL: https://github.com/hasura/graphql-engine/pull/7634 PR-URL: https://github.com/hasura/graphql-engine-mono/pull/2489 Co-authored-by: thephenix4 <69722745+thephenix4@users.noreply.github.com> Co-authored-by: Rikin Kachhia <54616969+rikinsk@users.noreply.github.com> GitOrigin-RevId: 246da4575afa583ce44fc858ac1a1053a730cf26
This commit is contained in:
parent
4f827429d3
commit
169902f88a
@ -229,7 +229,7 @@ and initializes a few tables under it. This schema and the internal tables are g
|
||||
By default, the ``metadata_catalogue`` is created inside the primary database provided by the user.
|
||||
But sometimes it might be more advantageous to segregate the primary database and the metadata database.
|
||||
|
||||
Hasura GraphQL engine provides a way to the users to provide an entirely seperate Database to store the
|
||||
Hasura GraphQL engine provides a way to the users to provide an entirely separate database to store the
|
||||
``metadata catalogue``.
|
||||
|
||||
To add a metadata database, set the following environment variable or add the flag to the server executable
|
||||
|
Loading…
Reference in New Issue
Block a user