1
Default schema for Foreign Keys
Source: supabase/supabase#38828 · opened by @tamaro-skaljic
Current behavior
Currently the public schema is always selected
<img width="452" height="369" alt="{6F844F61-883E-44D0-9AEA-9C9C8FAD6A79}" src=" />
Because I've enabled the api schema in the project settings, I always need to change the schema if I want to use it.
Proposed behavior
Instead the schema should be selected, which is the schema of the table in which a foreign key is created. So:
Default Schema::
• Foreign key for table in public schema: public.
• Foreign key for table in api schema: api.
Currently the public schema is always selected
<img width="452" height="369" alt="{6F844F61-883E-44D0-9AEA-9C9C8FAD6A79}" src=" />
Because I've enabled the api schema in the project settings, I always need to change the schema if I want to use it.
Proposed behavior
Instead the schema should be selected, which is the schema of the table in which a foreign key is created. So:
Default Schema::
• Foreign key for table in public schema: public.
• Foreign key for table in api schema: api.
No pledges yet. Be the first to back this.
Comments
Similar requests
Improve table editor UI for arrays of foreign keys (they aren't supported)
2 votes · 0 comments
Shortcut for foreign keys to `auth.users.id`
1 vote · 0 comments
Add a display_name to improve foreign key visualization
8 votes · 0 comments
Disallow Foreign Key Arrays in the UI
1 vote · 0 comments
Foreign key relations page
1 vote · 0 comments
No comments yet.