reactivemongo.play.json.compat
ValueConverters
Related Docs:
trait ValueConverters
| package compat
JSON representation for numbers
JSON representation for numbers
See syntax:
See syntax:
{ "$binary":
{
"base64": "<payload>",
"subType": "<t>"
}
}
See syntax:
See syntax:
{ "$date": { "$numberLong": "<millis>" } }
See syntax:
See syntax:
{ "$code": "<javascript>" }
See syntax:
See syntax:
{
"$code": "<javascript>",
"$scope": { }
}
See syntax:
See syntax:
See syntax:
See syntax:
{ "$oid": "<ObjectId bytes>" }
dsl.objectID
See syntax:
See syntax:
{ "$regularExpression":
{
"pattern": "<regexPattern>",
"options": "<options>"
}
}
See syntax:
See syntax:
{ "$symbol": "<name>" }
dsl.symbol
See syntax:
See syntax:
{ "$timestamp": {"t": <t>, "i": } }`
See syntax:
See compat$ and ValueConverters.
Note that as there is not a JSON equivalent for each BSON value (
BSONDateTime, or even distinction between BSON long/int).So for example, using the default JSON handlers, a same
Longproperty can be written in some documents as BSON long (NumberLong), and in some other as BSON integer (see ValueConverters.toNumber), which is ok to read all these documents, but can impact the MongoDB queries (same for date/time values that will be serialized as BSON string, rather than BSON date/time or timestamp).