-
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The table editor shows an incorrect foreign key relation with composite foreign keys #3583
Comments
Hey there! Sorry it took us so long to get to your issue - we're just looking into this right now As at the current state of the dashboard the relation descriptions under but the relation descriptions under |
How is this topic going? |
Hey folks - me and the team here are looking at a visual solution for composite foreign keys today and I'll post an update shortly on what we might propose. This will be so we officially support composite foreign keys in the dashboard, and issues like this won't be an issue anymore. We would also like to solve the issue of creating composite foreign keys in the dashboard which will probably mean having some 'mapping UI' so you can easily associate the right columns together to a target table. will update shortly. |
We'll probably look at implementing this soon, we are just prioritizing some other areas right now. Feel free for anyone else to take this though and implement it themselves, if you don't want to wait on the supabase team to implement it. |
Related to #2481 perhaps, as we can maybe handle naming of FK constraints as well |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Bug report
Describe the bug
The table editor shows an incorrect foreign key relation when a table has a composite foreign key.
To Reproduce
Screenshots
System information
The text was updated successfully, but these errors were encountered: