[SERVER-6813] Shell support for Extended JSON Created: 21/Aug/12  Updated: 18/May/22  Resolved: 25/Oct/21

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

Type: Improvement Priority: Minor - P4
Reporter: Richard Kreuter (Inactive) Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Won't Do Votes: 8
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-20129 $oid does not work with $ne Closed
Related
related to SERVER-16618 Log file should print extended json c... Backlog
is related to SERVER-5675 mongoimport should support all (exten... Closed
is related to SERVER-13209 Ensure extended shell JSON ouput form... Closed
Participants:
Case:

 Description   

AFAICT, the shell has never supported Extended JSON syntax. Example:

> db.foo.insert({ "_id" : { "$oid" : "5033c7decf61e919ab517ea4" } })
Tue Aug 21 14:09:22 uncaught exception: field names cannot start with $ [$oid]

This is of low importance, but would arguably be convenient for cutting and pasting from mongoexport output, for example.

For extra credit, the shell might have a mode in which it printed BSON objects in Extended JSON.

(As a design note, in order for this to work over time, it'd be important to ensure that the set of field names used for Extended JSON, queries, updates, etc. never collide, or else bad badness would ensue.)



 Comments   
Comment by Richard Kreuter (Inactive) [ 21/Aug/12 ]

This is the converse of SERVER-5675. Can't all our programs just get along?

Generated at Thu Feb 08 03:12:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.