Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The studio rename or even duplicate the FK when it is updated #25985

Open
2 tasks done
nicetomytyuk opened this issue May 10, 2024 · 0 comments
Open
2 tasks done

The studio rename or even duplicate the FK when it is updated #25985

nicetomytyuk opened this issue May 10, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@nicetomytyuk
Copy link
Contributor

nicetomytyuk commented May 10, 2024

Bug report

  • I confirm this is a bug with Supabase, not with my own application.
  • I confirm I have searched the Docs, GitHub Discussions, and Discord.

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:

  1. Go to an existing table in supabase studio
  2. Create a FK on a column by giving it a custom name and save
  3. Edit the existing FK by updating it's cascading logics
  4. 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

image
image
image

System information

  • OS: Ubuntu 20.04.6
  • Browser: Chrome
  • Version of supabase-js: 2.39.7
  • Version of Node.js: 20.10.0
@nicetomytyuk nicetomytyuk added the bug Something isn't working label May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant