listDatabases command reports existence of databases that have never been written to.

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Usability
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If a client accesses a non-existent database by reading it, a side-effect of that action is to cause listDatabases to believe in its existence. Further, listDatabases reports its sizeOnDisk as 1 byte, but sets the "empty" flag to true. This is confusing. Non-existent databases should not appear in listDatabases, even if someone attempted to read from it. Should they appear, they certainly shouldn't be reported as having a size on disk, when they have no associated files.

              Assignee:
              Unassigned
              Reporter:
              Andy Schwerin
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: