FeatureFuel
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.

Make a pledge

Pledge your monetary support if this feature is added.

$

Comments

No comments yet.

Replying to

Add a comment

What do you think about this feature request?


Similar requests