[SERVER-7645] Remove system. from collection namespace Created: 13/Nov/12 Updated: 06/Dec/22 Resolved: 19/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Per Lindberg | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
The .system.* collection namespace is reserved, but should not be. It's counter-intuitive and pollutes the namespace. I suggest that all such system stuff should be moved to a separate table named 'system' or 'mongodb' (like in MySQL). + Safer See e.g. http://stackoverflow.com/questions/4665244/system-in-a-collection-name-in-mongodb?rq=1 |
| Comments |
| Comment by Eric Milkie [ 19/Feb/19 ] |
|
We believe that changing this now will break too many applications that assume the existence of system-type namespaces. For the next release of MongoDB, we have removed some system-type namespace names to reduce clutter, and we aspire to continue to clean up more of them in the future. |
| Comment by Per Lindberg [ 13/Nov/12 ] |
|
Oops, I mean "...moved to to a separate DATABASE", of course. |