[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: |
|
||||||||
| Issue Links: |
|
||||||||
| 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. |
| Comment by Eric Sedor [ 11/Nov/19 ] |
|
Thanks urfx@yahoo.com, I am passing this ticket on to an appropriate team for consideration. Eric |