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

Custom validation of database and collection names

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Usability
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: