0
Improve Foreign Key Constraint Error UX in Table Editor
Source: supabase/supabase#44742 · opened by @21lakshh
Summary When attempting to delete a row in the Supabase Table Editor that is referenced by foreign key constraints, the current experience surfaces a generic error message. This makes it difficult for developers to understand *why* the deletion failed and *what actions are required* to resolve it. This feature request proposes enhancing the error UI to: • Clearly list all referencing tables and affected rows • Provide actionable insights • Generate a ready-to-run SQL query to resolve the constraint issue --- Problem Currently, when a user tries to delete a row that is referenced by a foreign key: Issues with current UX: • ❌ Does not show all dependent tables (only one constraint at a time) • ❌ No visibility into how many rows are affected • ❌ Requires manual investigation across tables • ❌ Slows down debugging and development workflows --- Proposed Solution Enhance the Table Editor delete flow to surfa…
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
Would be nice to CRUD table level constraints via the GUI
2 votes · 0 comments
Default schema for Foreign Keys
1 vote · 0 comments
Improved type inference for JSONB columns with check constraints in supabase typescript client
3 votes · 0 comments
Foreign key relations page
1 vote · 0 comments
No comments yet.