2
Improve table editor UI for arrays of foreign keys (they aren't supported)
Source: supabase/supabase#11130 · opened by @CrowhopTech
Feature request
In the table editor UI, if I try to both mark a field as a foreign key and an array (not supported in Postgres), the UI will allow me to select both options but the create/edit request will fail as expected.
Is your feature request related to a problem? Please describe.
Not really; the request still fails as expected, this is more of a UI improvment to reduce questions/frustration.
Describe the solution you'd like
Ideally the UI should catch this case with a nice UI message like "arrays of foreign keys are not supported", or even better just not allow selecting both at the same time (hide the array option when a foreign key is selected, or hide the foreign key option when array is selected)
Describe alternatives you've considered
N/A
Additional context
UI with both foreign key and array selected
, the UI will allow me to select both options but the create/edit request will fail as expected.
Is your feature request related to a problem? Please describe.
Not really; the request still fails as expected, this is more of a UI improvment to reduce questions/frustration.
Describe the solution you'd like
Ideally the UI should catch this case with a nice UI message like "arrays of foreign keys are not supported", or even better just not allow selecting both at the same time (hide the array option when a foreign key is selected, or hide the foreign key option when array is selected)
Describe alternatives you've considered
N/A
Additional context
UI with both foreign key and array selected
![image](
Error returned when I attempt to create/edit a table with this field
![image](
No pledges yet. Be the first to back this.
Comments
Similar requests
Disallow Foreign Key Arrays in the UI
1 vote · 0 comments
Default schema for Foreign Keys
1 vote · 0 comments
Improve Foreign Key Constraint Error UX in Table Editor
0 votes · 0 comments
Retrieve list of users by ID
1 vote · 0 comments
Multiple foreign tables in a single "or" statement
14 votes · 0 comments
No comments yet.