On 05/11/2019 02:45, Alexander Korotkov wrote:
> 3) Do we like to change behavior to_date()/to_timestamp()? Or just
> jsonpath .datetime() and future CAST(... AS ... FORMAT ...) defined in
> SQL 2016?
I don't want to hijack this thread, but I would like the CAST feature to
call to_timestamp()
Hi!
Thread [1] about support for .datetime() jsonpath method raises a
question about standard-conforming parising for Y, YY, YYY and RR
datetime template patterns.
According to standard YYY, YY and Y should get higher digits from
current year. Our current implementation gets higher digits so
