Treat linefeeds (\n, etc.) as invalid for collection (and database?) names

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 4.2.1
    • Component/s: Shell
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      I was using node client

      insertOne()

      I accidentally called my collection "\n\ngamestatequests" 

      a new collection as born which created me hrs of voodoo bug and undermined my confidence in the product...

      I reported that the atlas site correctly listed my collection and the documents in it... 

      but the mongo shell did not. 

      had to go to a lot of extremes to figure this out... because even the sell don't render line feed characters in a database name. 


              Assignee:
              Massimiliano Marcon
              Reporter:
              ur fx
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated: