[SERVER-75924] Un-deprecate BSON type Symbol (14) Created: 10/Apr/23 Updated: 08/Jun/23 Resolved: 08/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Johnny Shields | Assignee: | Backlog - Triage Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Triage
|
| Operating System: | ALL |
| Participants: |
| Description |
|
The BSON Symbol type has been "deprecated" for over 11 years https://github.com/mongodb/bsonspec.org/commit/b5b60d6eca910a139a91736922cc04dc30ccdb34 but yet there doesn't seem to be any plan to actually remove it. Removing it would break a lot of client apps esp. in languages like Ruby that support symbols/atoms. For these languages, its quite useful to be able to persist MongoDB data in a way that mirror the application's memory structure. Moreover it the deprecation "limbo" status seems to be perennial source of confusion/issues, e.g. Doesn't the MongoDB team think it might be better to undeprecate Symbol and instead make some guidelines about how it can be used in both languages like Ruby which have a symbol type, and languages like Javascript which do not? |
| Comments |
| Comment by Eric Sedor [ 08/Jun/23 ] |
|
I can see how this behavior would be valuable for reducing confusion, shields@tablecheck.com. You can help get this on the radar of our product teams by submitting a feature request to our MongoDB Feedback Engine. We use JIRA to track bug reports. Thank you! |