Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-5496

Collection name check does not match actual requirements

    • 2
    • 2
    • Not Needed
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      The checkCollectionName method in the driver does not match the actual restrictions on collection names.

      For example, one can use the Node.js driver to create a collection ending in a dot character, but cannot use it to access that collection afterwards.

      The method should be adjusted to actually match naming restrictions.

       

      AC

      • Remove validation on naming restrictions on collection and database names when creating the resource; delete any associated unneeded methods like checkCollectionName
        • Special Case: In the case of '.' in database names, we want to continue to validate client-side
      • Update existing tests or create new ones to check that the method is able to fail because of a server name validation error and not a driver error
      • Delete any unneeded tests

            Assignee:
            aditi.khare@mongodb.com Aditi Khare
            Reporter:
            anna.henningsen@mongodb.com Anna Henningsen
            Neal Beeken
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: