Although current behavior is ISO 8601 standards compliant and specified in the
docs, it would be nice if more precision were supported in datetimes.
datetime("2001-01-01T01:01:01.123")
Works fine, no errors
datetime("2001-01-01T01:01:01.1234")
Error: This can not be an instance of datetime [AlgebricksException]
datetime("2001-01-01T01:01:01.1230")
Error: This can not be an instance of datetime [AlgebricksException]
Note that the last example ends in 0.
(AsterixDB 0.8.5)
It is not uncommon to have datetimes with > millisecond precision. For example,
.NET (when generating an ISO 8601 compliant datetime string with
.ToString("o")) by default has 7 digits of fractional seconds.
If this can't be supported, a more descriptive error message would also be
helpful.
Original issue reported on code.google.com by euf...@gmail.com on 26 May 2014 at 6:24
Original issue reported on code.google.com by
euf...@gmail.com
on 26 May 2014 at 6:24