Custom validation of database and collection names

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Usability
    • None
    • Storage Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Often, developers / DBAs accidentally create databases with names that are nonsensical. This could be for a number of reasons, such as:

      • the database name chosen is not sufficiently descriptive and thus hard to identify by other teams
      • typos
      • running a bogus command such as the following in the shell (this is a real example)
      mongos> use *
      mongos> 
      

      It would be good to be able to specify a regex that a database name must match before creation can occur, so that sensible naming conventions could be enforced. This should also be made user-specific in some way.

      e.g. In a large organization, provide the ability to enforce some kind of naming conventions for certain groups to only be able to create databases named 'groupname_foo'.

      The above description equally applies to validation of collection names.

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Jon Rangel (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: