[ENH]: add method to delete database (single-node)

[codetheweb]

Description of changes

Adds a method to delete a database.

Test plan

How are these changes tested?

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

Yes.

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[codetheweb]

• [ENH] add distributed implementation for database deletion #3460
• [ENH]: add method to delete database (single-node) #3457 👈 (View in Graphite)
• [ENH]: add API to list all databases for tenant #3432 : 1 other dependent PR (#3440 )
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[atroyn]

I think we can make the tests a little more robust.

What happens if a user has a handle on a Collection, and then delete_database gets called underneath? Maybe we need a friendly error to let them know what happened.

[codetheweb]

What happens if a user has a handle on a Collection, and then delete_database gets called underneath? Maybe we need a friendly error to let them know what happened.

InvalidCollectionException will be thrown. Updated the test to assert this.

[atroyn]

LGTM, optional test improvement.

[codetheweb]

Merge activity

• Jan 13, 7:00 PM EST: A user started a stack merge that includes this pull request via Graphite.
• Jan 13, 7:06 PM EST: Graphite couldn't merge this PR because it failed for an unknown reason.
• Jan 13, 7:43 PM EST: A user started a stack merge that includes this pull request via Graphite.
• Jan 13, 7:44 PM EST: Graphite rebased this pull request as part of a merge.
• Jan 13, 7:44 PM EST: A user merged this pull request with Graphite.