Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

uint32 and similar fields are always marshaled into BSON int64 #132

Closed
xen0n opened this issue Nov 24, 2020 · 5 comments
Closed

uint32 and similar fields are always marshaled into BSON int64 #132

xen0n opened this issue Nov 24, 2020 · 5 comments

Comments

@xen0n
Copy link
Contributor

xen0n commented Nov 24, 2020

@xen0n
Copy link
Contributor Author

xen0n commented Nov 24, 2020

N.B. These are actually mongo-driver bugs/features, but have caused actual pain in our transition away from mgo. I don't know if such shimming should be best done in qmgo proper.

@xen0n
Copy link
Contributor Author

xen0n commented Nov 24, 2020

First one is dup of #117, updated parent comment.

@xen0n xen0n changed the title BSON (de)serialization behavior is not equivalent to mgo uint32 and similar fields are always marshaled into BSON int64 Nov 24, 2020
@jiangz222
Copy link
Collaborator

Record here
Wait for official plan.

@xen0n
Copy link
Contributor Author

xen0n commented Nov 24, 2020

For the time being, you can mass-update (or insert) bson:"foo" tags to look like bson:"foo,minsize", for the affected fields, to maintain compatibility of stored data.

@lifegit
Copy link

lifegit commented Jun 7, 2021

excuse me, can you tell me how to use it?
#117

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants