odd error message when dropping database #23661
Labels
S-3-ux-surprise
Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.
Milestone
I ran the following commands:
The drop ran successfully, but I'm not sure why I get an error message afterwards?
Running show databases confirms that the database is gone.
The text was updated successfully, but these errors were encountered: