Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Duplicate
-
3.0.3, 3.0.6
-
None
-
None
-
Seen on CentOS 7.1, both in 3.0.3 and 3.0.6. Not tested on anything else.
-
Fully Compatible
-
Linux
-
Description
If you store the value 0 as a double in a field, you can't change the value 0 to a 32 bit integer without switching the value to something else in between.
It appears MongoDB on update considers 0 (the double) to be equal to the new value 0 (32-bit integer) and does not do any update.
Attachments
Issue Links
- duplicates
-
SERVER-16801 update considers a change in numerical type to be a noop
-
- Closed
-