LIBBSON_LEGACY_EXTENDED_JSON(3)

📦
version 2.5.6 · 11 versions
, in epel 10

okay so this is the libbson_legacy_extended_json(3) manual page, and it's literally about how libbson can produce a non-portable Legacy Extended JSON format ✨

⚠️ WARNING ⚠️

🚨 Use of the Legacy Extended JSON format is discouraged. Prefer Canonical Extended JSON or Relaxed Extended JSON for portability. no cap, this is the important bit 💅

MongoDB Extended JSON (v2) describes the preferred Relaxed Extended JSON format and Canonical Extended Formats.

libbson's Legacy Extended JSON format matches Relaxed Extended JSON with the following exceptions. Notation is borrowed from MongoDB Extended JSON (v2):

  • Binary — { "$binary": "<payload>", "$type": "<t>" }
  • Date — { "$date" : "<millis>" }
  • Regular Expression — { "$regex" : "<regexPattern>", "$options" : "<options>" }
  • DBPointer (deprecated) — { "$ref" : "<collection namespace>", "$id" : "<ObjectId bytes>" }
  • Symbol (deprecated) — "<string>"
  • Double infinity — infinity or inf without quotes. Implementation defined. Produces invalid JSON. 😭
  • Double NaN — nan or nan(n-char-sequence). Implementation defined. Produces invalid JSON. 💀

👑 AUTHOR 👑

MongoDB, Inc

2009-present, MongoDB, Inc.

that's the whole page, bestie! 🫶 source/version: 2.5.6, date: Oct 09, 2026 — mwah, bye 💖

📦 where this page comes from