-
|
The managed DB team at work seems very unlikely to support us using Hasura if we need the meta-data table/tables stored in a different schema that is not |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
@botwhytho |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I've seen these docs before, whether specifying the same or a
different database server, there seems to be no settings for specifying a
different schema than 'hdb_catalog' where the metadata tables will live.
Can someone confirm if this is an impossibility at the moment? Per
description above I may not have the flexibility to create that schema or
tables in any other schema other than 'public'. Unfortunate but actual
situation at work and can't imagine I've been the only person to bump into
this
…On Wed, May 24, 2023, 19:49 Ashok Das ***@***.***> wrote:
@botwhytho <https://github.com/botwhytho>
You can have a separate metadata (postgres) database (distinct from your
data).
Here is the doc
<https://hasura.io/docs/latest/deployment/graphql-engine-flags/config-examples/#add-metadata-database>
—
Reply to this email directly, view it on GitHub
<#9668 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFB43JNLLLHCG7DU4LBJKEDXH2NB3ANCNFSM6AAAAAAYN5GWFI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
@botwhytho
So, it won't be possible to use a custom schema name for metadata catalog. |
Beta Was this translation helpful? Give feedback.
@botwhytho
As per our docs
The Hasura GraphQL Engine when initialized, creates a schema called hdb_catalog in the Postgres database and initializes a few tables under it. This schema and the internal tables are generally termed as the metadata catalogue and is responsible to manage the internal state of the Hasura GraphQL Engine.So, it won't be possible to use a custom schema name for metadata catalog.