You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading the self hosted version of supabase to the latest: supabase/studio:20240422-5cf8f30 when an existing foreign key is updated, the FK name is updated with a prefix of schema name, or in some cases it does even duplicate the key.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Go to an existing table in supabase studio
Create a FK on a column by giving it a custom name and save
Edit the existing FK by updating it's cascading logics
Et voilà your FK name has been change from custom_fkey to schema_custom_fkey
Expected behavior
The studio must just update the existing FK values without changing it's name or duplicating it.
Screenshots
System information
OS: Ubuntu 20.04.6
Browser: Chrome
Version of supabase-js: 2.39.7
Version of Node.js: 20.10.0
The text was updated successfully, but these errors were encountered:
Bug report
Describe the bug
After upgrading the self hosted version of supabase to the latest:
supabase/studio:20240422-5cf8f30
when an existing foreign key is updated, the FK name is updated with a prefix of schema name, or in some cases it does even duplicate the key.To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
custom_fkey
toschema_custom_fkey
Expected behavior
The studio must just update the existing FK values without changing it's name or duplicating it.
Screenshots
System information
The text was updated successfully, but these errors were encountered: