> but BSON pidgenholes numeric values to either double, int32, int64, or
> a 12-byte MongoDB Object ID. Thus, for people who expect JSON to be
> able to hold arbitrary-precision numbers (which the JSON data type in
> my patch can), using BSON for transfer or storage will violate that
> expectation.
Good lord. I'd suggest that maybe we wait for BSON v. 2.0 instead.
Is BSON even any kind of a standard?
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com