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

[Suggestion] It would be better pop up a notification and output a log after deleting a database for graph/sql/mongo account #1863

Closed
v-xinda opened this issue May 27, 2021 · 0 comments · Fixed by #2254
Assignees
Labels
AT-CTI Created by CTI team
Milestone

Comments

@v-xinda
Copy link

v-xinda commented May 27, 2021

OS: All
Build Version: 20210525.1

Repro Steps:

  1. Drill down a PostgreSQL server -> Right click a database (e.g. testdata) -> Click "Delete Database...".
  2. Pop up a notification and output a log to prompt the database is deleted successfully.
    image
  3. Drill down a graph/sql/mongo account -> Right click a database -> Click "Delete Database...".
  4. Check whether pop up a notification and output a log to prompt the database is deleted successfully.

Actual:
There is no any notification and log after deleting a database.

Suggestion:
It would be better pop up a notification and output a log after deleting a database for graph/sql/mongo account, like below.
image
image

More Info:
This issue also reproduces after deleting the collection/graph/document.

@v-xinda v-xinda added the AT-CTI Created by CTI team label May 27, 2021
@neelip neelip added this to the 0.19.0 milestone Jul 26, 2021
@JasonYeMSFT JasonYeMSFT modified the milestones: 0.19.0, 0.20.0 Sep 11, 2023
@JasonYeMSFT JasonYeMSFT self-assigned this Sep 20, 2023
@JasonYeMSFT JasonYeMSFT modified the milestones: 0.20.0, 0.21.0 Sep 20, 2023
@microsoft microsoft locked and limited conversation to collaborators Apr 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
AT-CTI Created by CTI team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants