Yes, the version of Spidermonkey included in Riak is somewhere around the
1.8.1 release. This means that it doesn't include the ISO8601 format
automatically.
On Mon, Jul 23, 2012 at 10:27 AM, lazukars wrote:
> Thanks for the response Sean! Making the timestamp RFC 822 compliant did
> indeed wor
Thanks for the response Sean! Making the timestamp RFC 822 compliant did
indeed work. However, playing devils advocate, MDN documentaion states this
"Alternatively, the date/time string may be in ISO 8601 format. Starting
with JavaScript 1.8.5 / Firefox 4, a subset of ISO 8601 is supported. For
Note that JavaScript's Date.parse() expects timestamps to be formatted in a
style similar to RFC 822, which is not the format shown in your data. You
might want to add the functions from this file to your Riak installation:
https://github.com/seancribbs/ripple/blob/master/lib/rails/generators/rippl
@siculars The funny thing is that I used your blog for an inspiration for my
code ( The code that was originally posted in this thread. ) I'm not doing
things exactly the same way you did in your post. I just can't figure out
why the code from your blog post works and mine does not. Mine just re
, "Marcel Meyer" wrote:
> I was struggling with this as well. I would get proper dates in a JS test
> console, but the exact same function under Riak would yield null dates.
>
>
> On Fri, Jul 20, 2012 at 6:48 PM, Ryan Lazuka wrote:
>
>> Data.parse() does not
I was struggling with this as well. I would get proper dates in a JS test
console, but the exact same function under Riak would yield null dates.
On Fri, Jul 20, 2012 at 6:48 PM, Ryan Lazuka wrote:
> Data.parse() does not seem to be working in a MapReduce phase.
> http://codepad.org/sT
Data.parse() does not seem to be working in a MapReduce phase.
http://codepad.org/sT0E5ch5 Here is the resulting array:
[{"description":"","signed-in_date":"07-20-2012","signed-in_time":"9:43
pm","date-time":null},{"des
