Loading...

XML

Word

Printable

JSON

Documentation Changes:
Needed
Documentation Changes Summary:

Hide

From this version we require NumberLong and NumberDecimal to be constructed from a string. This is a breaking change from the old shell behavior.

Now: NumberLong("123") and NumberDecimal("123.1") would work, whereas: NumberLong(123) and NumberDecimal(123.1) would throw an exception.

Show
From this version we require NumberLong and NumberDecimal to be constructed from a string. This is a breaking change from the old shell behavior. Now: NumberLong("123") and NumberDecimal("123.1") would work, whereas: NumberLong(123) and NumberDecimal(123.1) would throw an exception.
Sprint:
Iteration Lime

`NumberLong` is created incorrectly with unsafe integers (> Number.MAX_SAFE_INTEGER)

The same happens when retrieving a NumberLong which is an unsafe integer, even if was correctly inserted in the database.

The old shell correctly handles it:

New shell:

> db.coll3.insertOne({x: NumberLong("345678654321234561")})

{ acknowledged: 1, insertedId: ObjectId("5f564a3c4f53d376a739e656") }

> db.coll3.find()

    _id: ObjectId("5f564a3c4f53d376a739e656"),

    x: NumberLong(345678654321234560)

Old shell:

> db.coll5.insertOne({int64: NumberLong("345678654321234561")})

        "acknowledged" : true,

        "insertedId" : ObjectId("5f564a9284f79fe8de9e7e40")

> db.coll5.find()

{ "_id" : ObjectId("5f564a9284f79fe8de9e7e40"), "int64" : NumberLong("345678654321234561") }

related to

COMPASS-4355 $match stage in Aggregation Pipeline builder does not find int64 fields