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

Schema-specific DB reset #2626

Open
foxted opened this issue Aug 22, 2024 · 0 comments
Open

Schema-specific DB reset #2626

foxted opened this issue Aug 22, 2024 · 0 comments

Comments

@foxted
Copy link

foxted commented Aug 22, 2024

Is your feature request related to a problem? Please describe.
When running supabase db reset, the entire database is dropped. This can be an issue when working with other applications leveraging the same database but not leveraging the Supabase migrations (for example, PayloadCMS).

Describe the solution you'd like
Allow a "soft reset", where only the specified schemas should be reset, leaving any other schemas in the database intact.

Something like supabase db reset --schema public,some_other_schema

This would be similar to supabase db diff, supabase db dump or supabase db lint, which all accept a --schema flag.

Describe alternatives you've considered
Currently using a manual script to achieve this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant