Readonly views work in database tab. #734
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before the database tab would not display anything if the database had readonly views. This was due to 2 reasons:
collStats
command could not be executed against thesystem.views
namespace when readonly views exist, because it is a system namespace.collStats
command failed when executing against a readonly view directly.The mongodb-data-service 2.4.0 release filters these out instead of erroring, which is updated in this pull request. We also now format the readonly views in the table to display
-
instead of all zeros for values.This also now indicates in the collection view if the collection is a readonly view with a lock next to the name: