Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-4122

Validate database and collection names on the server before creating them

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • Labels:
      None
    • ALL

      This is a call to prevent the creation of databases or collections with illegal names.

      During a recent training, some of the trainees ran into a problem when we were doing backups using mongodump. mongodump stopped, giving an error message because it couldn't dump a database named "*". "show dbs" in the shell confirmed that there was indeed a database named "*". (But attempting to use it failed because that led to a "..." continuation prompt.) But only a few people were affected, so this doesn't appear to be systemic. It seems likely that this was created accidentally as a result of some earlier mistyped command, possibly an attempt to use a wild card incorrectly.

      In some contexts, this name worked, and in others it didn't, leading me to believe we're not validating these on the server, but are instead relying on client parsers to keep them out, but apparently not always successfully.

            Assignee:
            randolph@mongodb.com Randolph Tan
            Reporter:
            cwestin Chris Westin
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: