This repository has been archived by the owner on Jul 5, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 163
ISODate bug #130
Comments
bobthecow
added a commit
that referenced
this issue
Aug 11, 2013
Thirteen years past y2k, and JavaScript is still dumb about years less than 100 :-/ See #130
Arrgh. JavaScript. I bet you thought weren't going to get bitten by a y2k bug in 2013, right? The branch Funny story: the |
This has been released in v2.3.8. Thanks for reporting it! |
Hi, sorry I have not had the time to reply earlier. Works great with the new release, thanks for the quick fix! |
No worries. Thanks for taking a look! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, been using Genghisapp for a while now it's really nice I must say!
I have one problem though, ISODate does not really work as expected when I try to edit or create entries. I'm not completely sure if it's only me, but I don't think so.
To recreate, add a document like this:
{
uptime: ISODate("0001-01-01T01:00:00+01:00")
}
And if the bug is not only me, the saved value will become something like this:
{
uptime: ISODate("1901-01-01T01:00:00+01:00")
}
It can fetch and present ISODate("0001-01-01T01:00:00+01:00") just fine if it's already in the database, but it can't add it manually from the interface or edit a document manually.
The text was updated successfully, but these errors were encountered: