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

Unable to remove databases which can't be connected to #4149

Open
zackkrida opened this issue Jan 21, 2025 · 0 comments
Open

Unable to remove databases which can't be connected to #4149

zackkrida opened this issue Jan 21, 2025 · 0 comments
Labels
affects: ux Related to user experience needs: troubleshooting Issues that we can't reproduce or need to investigate further before picking a course of action
Milestone

Comments

@zackkrida
Copy link
Contributor

Description

If a user has deleted or otherwise lost access to one of their Postgres databases, it follows that they would want to remove the database from Mathesar.

Currently, it doesn't seem that Mathesar can remove databases which cannot be connected to:

Image

Expected behavior

Remove the DB from Mathesar but inform the user that Mathesar is unable to connect to the DB. Perhaps, if the user wishes to drop the DB and/or remove Mathesar's schema, we should not delete the Database from Mathesar. Rather, we should inform the user "The selected actions can't be completed because Mathesar is unable to connect to your database. Either repair the connection or uncheck 'Drop the database' or 'Remove Mathesars internal schema' features to continue removing the database from Mathesar"

To Reproduce

  1. Create a DB somewhere, add it to Mathesar.
  2. Delete or revoke access to the DB.
  3. Try to remove it in the Mathesar UI.
@zackkrida zackkrida added affects: ux Related to user experience needs: troubleshooting Issues that we can't reproduce or need to investigate further before picking a course of action labels Jan 21, 2025
@kgodey kgodey added this to the Backlog milestone Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects: ux Related to user experience needs: troubleshooting Issues that we can't reproduce or need to investigate further before picking a course of action
Projects
None yet
Development

No branches or pull requests

2 participants