You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Case: When a user creates a Manager configuration and specifies a database name that does not exist, the database is created automatically.
Expected:
User should be aware, that provided DB does not exist
Handled by some configuration, like when DB does not exist, decide if it has to be created automatically, or skip the creation and handle correctly the user notification.
The text was updated successfully, but these errors were encountered:
This is fully expected behavior of MongoDB. If a database does not exist, MongoDB creates it the first time you store data for that database, so I believe restricting this with additional configuration is unnecessary, as it will never cause an error. Nevertheless, in the linked merge request, I added a log warning to highlight when a given database does not exist.
Case: When a user creates a Manager configuration and specifies a database name that does not exist, the database is created automatically.
Expected:
The text was updated successfully, but these errors were encountered: