MongoDB Extended扩展的 JSON (v2)

MongoDB Extended JSON v2 UsageMongoDB扩展JSON v2使用

EJSON.serialize( db.<collection>.findOne() )

EJSON.deserialize( <serialized object> )

EJSON.stringify( <deserialized object> )

EJSON.parse( <string> )

BSON Data Types and Associated RepresentationsBSON数据类型和相关表示

The following presents some common BSON data types and the associated representations in Canonical and Relaxed.下面介绍了一些常见的BSON数据类型以及Canonical和Relaxed中的相关表示。

The complete list is here.完整的名单在这里。

Array

[ <elements> ]

<Same as Canonical>

Where the array elements are as follows:其中数组元素如下：

• <elements>

  • Array elements use Extended JSON.数组元素使用扩展JSON。
  • To specify an empty array, omit the content [ ].要指定空数组，请省略内容[ ]。

Binary

{ "$binary":
   {
      "base64": "<payload>",
      "subType": "<t>"
   }
}

<Same as Canonical>

Where the values are as follows:其中值如下：

• "<payload>"

  • Base64 encoded (with padding as "=") payload string.Base64编码（填充为“=”）有效载荷字符串。

• "<t>"

  • A one- or two-character hex string that corresponds to a BSON binary subtype. See the extended bson documentation http://bsonspec.org/spec.html for subtypes available.与BSON二进制子类型对应的一个或两个字符的十六进制字符串。请参阅扩展的bson文档http://bsonspec.org/spec.html以了解于可用的亚型。

Date

For dates between years 1970 and 9999, inclusive:对于1970年至9999年（含）之间的日期：

{"$date": {"$numberLong": "<millis>"}}

{"$date": "<ISO-8601 Date/Time Format>"}

For dates before year 1970 or after year 9999:对于1970年之前或9999年之后的日期：

{"$date": {"$numberLong": "<millis>"}}

<Same as Canonical>

Where the values are as follows:其中值如下：

• "<millis>"

  • A 64-bit signed integer as string. The value represents milliseconds relative to the epoch.一个64位带符号整数，作为字符串。该值表示相对于纪元的毫秒数。

• "<ISO-8601 Date/Time Format>"

  • A date in ISO-8601 Internet Date/Time Format as string.ISO-8601互联网日期/时间格式的日期字符串。

  • The date/time has a maximum time precision of milliseconds:日期/时间的最大时间精度为毫秒：

    • Fractional seconds have exactly 3 decimal places if the fractional part is non-zero.如果分数部分为非零，则分数秒精确到小数点后3位。
    • Otherwise, fractional seconds SHOULD be omitted if zero.否则，如果为零，则应省略小数秒。

Decimal128

{ "$numberDecimal": "<number>" }

<Same as Canonical>

Where the values are as follows:其中值如下：

• "<number>"

  • A high-precision decimal as a string.字符串形式的高精度十进制数。

Document

{ <content> }

<Same as Canonical>

Where the document contents are as follows:文件内容如下：

• <content>

  • Name:value pairs that use Extended JSON.名称：使用扩展JSON的值对。
  • To specify an empty document, omit the content { }.若要指定空文档，请省略内容{ }。

Double

For finite numbers:对于有限数：

{"$numberDouble": "<decimal string>" }

<non-integer number>

For infinite numbers or NAN:对于无限数或NAN：

{"$numberDouble": <"Infinity"|"-Infinity"|"NaN"> }

<Same as Canonical>

Where the values are as follows:其中值如下：

• "<decimal string>"

  • A 64-bit signed floating point as a string.字符串形式的64位有符号浮点。

• <non-integer number>

  • A non-integer number. Integer numbers are parsed as an integer instead of a double.非整数。整数被解析为整数而不是双精度数。

Int64

{ "$numberLong": "<number>" }

<integer>

Where the values are as follows:其中值如下：

• "<number>"

  • A 64-bit signed integer as string.作为字符串的64位带符号整数。

• <integer>

  • A 64-bit signed integer.一个64位带符号整数。

Int32

{ "$numberInt": "<number>" }

<integer>

Where the values are as follows:其中值如下：

• "<number>"

  • A 32-bit signed integer as a string.字符串形式的32位带符号整数。

• <integer>

  • A 32-bit signed integer.一个32位带符号整数。

MaxKey

{ "$maxKey": 1 }

<Same as Canonical>

The MaxKey BSON data type compares higher than all other types. See Comparison/Sort Order for more information on comparison order for BSON types.MaxKey BSON数据类型比其他所有类型都高。有关BSON类型的比较顺序的更多信息，请参阅比较/排序顺序。

MinKey

{ "$minKey": 1 }

<Same as Canonical>

The MinKey BSON data type compares lower than all other types. See Comparison/Sort Order for more information on comparison order for BSON types.MinKey BSON数据类型比其他所有类型都低。有关BSON类型的比较顺序的更多信息，请参阅比较/排序顺序。

ObjectId

{ "$oid": "<ObjectId bytes>" }

<Same as Canonical>

Where the values are as follows:其中值如下：

• "<ObjectId bytes>"

  • A 24-character, big-endian hexadecimal string that represents the ObjectId bytes.一个24个字符的大端十六进制字符串，表示ObjectId字节。

Regular Expression

{ "$regularExpression":
   {
      "pattern": "<regexPattern>",
      "options": "<options>"
  }
}

<Same as Canonical>

Where the values are as follows:其中值如下：

• "<regexPattern>"

  • A string that corresponds to the regular expression pattern. The string can contain valid JSON characters and unescaped double quote (") characters, but may not contain unescaped forward slash (/) characters.与正则表达式模式对应的字符串。字符串可以包含有效的JSON字符和未转义的双引号（"）字符，但不能包含未转义的正斜杠（/）字符。

• "<options>"

  • A string that specifies BSON regular expression options. You must specify the options in alphabetical order. For information on the supported options, see $options.指定BSON正则表达式选项的字符串。您必须按字母顺序指定选项。有关支持的选项的信息，请参阅$options。

Timestamp

{"$timestamp": {"t": <t>, "i": <i>}}

<Same as Canonical>

Where the values are as follows:其中值如下：

• <t>

  • A positive integer for the seconds since epoch.自纪元以来的秒数的正整数。

• <i>

  • A positive integer for the increment.增量为正整数。

Examples示例

The following examples illustrate Extended JSON usage.以下示例说明了扩展JSON的使用。

db.conversions.insertOne( { insertDate: new Date() } )

{
  acknowledged: true,
  insertedId: ObjectId("61fbaf25671c45f3f5f4074a")
}

serialized = EJSON.serialize( db.conversions.findOne() )

{
  _id: { '$oid': '61fbaf25671c45f3f5f4074a' },
  insertDate: { '$date': '2022-02-03T10:32:05.230Z' }
}

EJSON.deserialize( serialized )

{
  _id: new ObjectId( "61fbaf25671c45f3f5f4074a" ),
  insertDate: ISODate( "2022-02-03T10:32:05.230Z" )
}

stringified = EJSON.stringify( db.conversions.findOne() )

{
   "_id": {"$oid":"61fbaf25671c45f3f5f4074a"},
   "insertDate":{"$date":"2022-02-03T10:32:05.230Z"}
}

EJSON.parse( stringified )

{
  _id: new ObjectId("61fbaf25671c45f3f5f4074a"),
  insertDate: ISODate("2022-02-03T10:32:05.230Z")
}