-
Notifications
You must be signed in to change notification settings - Fork 159
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
Opening and saving documents with $date zeroes out millis for all $dates in the document #102
Comments
Thanks for the fast response! 👍 |
Btw, is there a dev/test (.app) build available for download, that reflects whatevers currently in |
Not yet... |
I did a test to make sure mongohub doesn't modify a document if you open it, and save it without changing anything. This test failed on this bug. I would like to fix that bug before doing the next build. I should be able to do that over the week-end. But meanwhile, I can send you a build by email, if you want. |
That would be great! |
Fixed in 2.5.14, I let you close this issue after testing this new release. |
Looks good to me! |
It seems MongoHub does not take milliseconds of a date into account, hence, opening and saving a document, without modifying it, will clear out the millis of a date.
Steps to reproduce:
Save a document with some
$date
field"someDate": { "$date": 1384297199999.00000 }
Read it back out, it shows as
"someDate": { "$date": 1384297199000.00000 }
Save it, and milliseconds are lost. The date is now in fact
1384297199000.00000
i mongodb.The text was updated successfully, but these errors were encountered: