Skip to content

Commit 5826dcc

Browse files
authored
Hasura custom metadata docs (#599)
1 parent 9f7d21f commit 5826dcc

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

docs/graphql/hasura.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -71,3 +71,11 @@ Remember that "camelcasing" is a separate stage performed after all tables are r
7171
* {{ #summary config/hasura.md }}
7272
* {{ #summary cli-reference.md#hasura-configure }}
7373
```
74+
75+
## Custom Hasura Metadata
76+
77+
There are some cases where you have to make a custom modifications to the Hasura metadata. For example, assume that your database schema has a view that contains data from the main table, in which case you cannot set a foreign key between them. Then you can place files with a `.json` extension in the `hasura` directory of your project with the content in Hasura query format, and DipDup will execute them in alphabetical order of file names when the indexing is complete.
78+
79+
The format of the queries can be found in the [Schema Metadata API](https://hasura.io/docs/latest/api-reference/schema-metadata-api/index/) documentation.
80+
81+
Feature flag `allow_inconsistent_metadata` set in `hasura` configuration section allow users to modify the behavior of the requests error handling. By default this value is False.

0 commit comments

Comments
 (0)