Updating objects with Date fields converts Date to Double about mongohub-mac HOT 6 CLOSED

Please, keep in mind that I'm using strict json to parse and show documents : http://www.mongodb.org/display/DOCS/Mongo+Extended+JSON

So according to this web page a timestamp is represented by : { "$timestamp" : [ 1, 2 ] }

Anyway, I didn't find some bugs to display documents that come from mongodb. Those bugs are with regex and timestamp values. So I just fixed those bugs and added more tests to make sure this will never happens again.

I'm very sorry about those bugs I already did a software update.

from mongohub-mac.

please, close this bug as soon as you verify this issue. Fixed in 2.4.7 or higher.

from mongohub-mac.

Thanks for the quick response! :)
Unfortunately, the bug persist... Date fields still get converted to Double fields when I edit and save an object.
According to the link you posted, I would expect a Date to be shown as
"created_at": { "$date" : 132006661200 }
instead of just
"created_at": 1320066612000

Similar to the $oid Mongo-ObjectIDs, so that the data type doesn't change.
Timestamps would be similar:
"created_at": { "$timestamp" : { 1320066612000, 000000 } }

Would that be possible? =)

from mongohub-mac.

Sorry about that… I don't know why but when I read "date", I understood "timestamp"… Well, that was not bad since I found bugs around timestamp too. Anyway, now that I can understand "date", I just fixed the bug you describe.

So the date should be display as : "created_at": { $"date" : 1320066612000.00000 }

This should be fixed with 2.4.8, I let you close this issue

from mongohub-mac.

Perfect! Works flawlessly.
Thanks again, is there some way we could donate some money for the awesome support? :D

from mongohub-mac.

Well, I can't accept crasher and data lost… So that's obvious for me to fix those bugs as fast as I can. Plus, you already paid by hitting this bug (and having data lost) instead of me… :-)

from mongohub-mac.