createdAt and updatedAt are left in Parse::Object hash as Strings

[ericcj]

which means they're passed around as strings which will never match conditions if you do something like:

2.0.0-p0 :011 > Parse::Query.new('_User').greater_than('createdAt', Parse::Query.new('_User').get.first['createdAt']).get
2013-05-23 17:16:06 [INFO] Parse query for /1/users {"where"=>"{}"}
2013-05-23 17:16:07 [INFO] Parse query for /1/users {"where"=>"{"createdAt":{"$gt":"2013-05-02T15:25:43.714Z"}}"}

[xavdid]

@ericcj what's the correct object to store them as? Time objects?

[ericcj]

all other dates come back as Parse::Date

[rhymes]

@ericcj I think it has something to do with how Parse sends back the query results. Can you provide an example of what do you mean when you say

all other dates come back as Parse::Date

?

[syampsijk]

can i split the dates of updatedAt when i call in my javascript site