hasura / hasura/graphql-engine

impossible to autogenerate relations between tables in different schemas

Open
#9,644 2 comments 0 reactions 0 assignees View on GitHub
k/enhancement t/native-dbs
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Is your proposal related to a problem?
YES

The "track all" relations funcitonality (in the data section) is not able to automatically generate relations from tables in different db schema.
it whouldn't be a problem (it is possible to generate them manually) but the procedure doesn't continue to generate those relation it can generate correctly. it abort the creation and show the error message.
Should be usefull to have a "skip error" option during this phase.
Optionally should be useful to extend the "Untracked foreingn-key relation" list, to the tracked ones as well, to better identify some relations that need to be manually modified!

thanks

Contributor guide

Open the contributing guide

Research direction

Start in the Data section's “track all” relations flow and reproduce the failure with tables in different database schemas. Trace how automatic relation generation handles an error and compare it with the manually generated relations path. Done means the process can continue past an unsupported relation and clearly identifies relations that require manual changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgres
Domain
database
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.