mgo

Encoding json.Number as a number (int64 or float64)

Bug #1342207 reported by Min-Young Wu on 2014-07-15
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mgo
Undecided
Unassigned

Bug Description

As json.Number is part of the standard library and is excessively common, it kind of makes sense to handle it as part of bson encoding? Since it's supposed to be a number, let's encode it as a number (int64 or float64).

Revision history for this message
Min-Young Wu (min-young-wu) wrote :
Revision history for this message
Gustavo Niemeyer (niemeyer) wrote :

This has been committed to tip, including a few changes so that decoding happens properly too (important for backwards compatibility).

Please note that the commit happened at the new location that will be announced tomorrow with the release (https://gopkg.in/mgo.v2).

Changed in mgo:
status: New → Fix Committed
Changed in mgo:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers