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.

Sign up for GitHub

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

Jump to bottom

Publications are not dropped when resetting remote database #2640

Open

sweatybridge opened this issue Aug 28, 2024 · 0 comments

Labels

bug

Contributor

sweatybridge commented Aug 28, 2024 •

edited

Loading

Describe the bug
This leads to failure creating publication as there will be duplicate.

To Reproduce
Steps to reproduce the behavior:

create a publication in migration file
run migration up --linked
run db reset --linked
see error

Expected behavior
Publications are dropped with db reset.

Screenshots
If applicable, add screenshots to help explain your problem.

System information
Rerun the failing command with --create-ticket flag.

Ticket ID: [e.g. ab1ac733e31e4f928a4d7c8402543712]
Version of OS: [e.g. Ubuntu 22.04]
Version of CLI: [e.g. v1.60.0]
Version of Docker: [e.g. v25.0.3]
Versions of services: [output from supabase services command]

Additional context
If applicable, add any other context about the problem here.

Browser [e.g. chrome, safari]
Version of supabase-js [e.g. v2.22.0]
Version of Node.js [e.g. v16.20.0]

The text was updated successfully, but these errors were encountered:

sweatybridge added the bug label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment