-
Type:
Task
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: BSON
-
None
-
Environment:go version go1.11 linux/amd64
-
None
-
None
-
None
-
None
-
None
-
None
-
None
What's the reason of choosing int64 over time.Time?
Migration from mgo to official driver caused this unexpected behaviour.