Skip to content

Publications are not dropped when resetting remote database #2640

Closed

Description

@sweatybridge

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

To Reproduce
Steps to reproduce the behavior:

  1. create a publication in migration file
  2. run migration up --linked
  3. run db reset --linked
  4. 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]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions