[SERVER-44504] Treat linefeeds (\n, etc.) as invalid for collection (and database?) names Created: 08/Nov/19  Updated: 10/May/22

Status: Backlog
Project: Core Server
Component/s: Shell
Affects Version/s: 4.2.1
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: ur fx Assignee: Massimiliano Marcon
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2019-11-08 at 15.40.28.png     PNG File Screenshot 2019-11-08 at 15.41.27.png    
Issue Links:
Related
is related to SERVER-5002 Change prohibited character sets in d... Closed
Participants:

 Description   

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. 




 Comments   
Comment by Steven Vannelli [ 10/May/22 ]

Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions.

Comment by Connie Chen [ 20/Jul/20 ]

This should be fixed in the shell by escaping control characters.
massimiliano.marcon passing this to you to evaluate whether this should be done for the test shell.

Comment by Eric Sedor [ 11/Nov/19 ]

Thanks urfx@yahoo.com,

I am passing this ticket on to an appropriate team for consideration.

Eric

Generated at Thu Feb 08 05:06:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.