[SERVER-19044] use same database name validation rules on all platforms Created: 18/Jun/15 Updated: 06/Dec/22 Resolved: 15/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.0.4, 3.1.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Adam Midvidy | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
NamespaceString::validDBName checks different characters on Windows. It seems like this could cause issues with mixed OS replica sets, for example. This also can break mongodump/restore on mixed OS clusters. We should use the same database name validation rules on Linux as we do on Windows. |
| Comments |
| Comment by Sara Williamson [ 15/Apr/19 ] |
|
Please see |