elasticsearch/docs/reference/sql
Marios Trivyzas 8810ed03a2
SQL: Fix DATETIME_PARSE behaviour regarding timezones (#56158)
Previously, when the timezone was missing from the datetime string
and the pattern, UTC was used, instead of the session defined timezone.
Moreover, if a timezone was included in the datetime string and the
pattern then this timezone was used. To have a consistent behaviour
the resulting datetime will always be converted to the session defined
timezone, e.g.:
```
SELECT DATETIME_PARSE('2020-05-04 10:20:30.123 +02:00', 'HH:mm:ss dd/MM/uuuu VV') AS datetime;
```
with `time_zone` set to `-03:00` will result in
```
2020-05-04T05:20:40.123-03:00
```

Follows: #54960
2020-05-05 11:13:47 +02:00
..
appendix
endpoints SQL: Fix DATETIME_PARSE behaviour regarding timezones (#56158) 2020-05-05 11:13:47 +02:00
functions SQL: Fix DATETIME_PARSE behaviour regarding timezones (#56158) 2020-05-05 11:13:47 +02:00
language QL: constant_keyword support (#53241) 2020-03-16 15:22:42 +02:00
concepts.asciidoc
getting-started.asciidoc
index.asciidoc
limitations.asciidoc SQL: Implement scripting inside aggs (#55241) 2020-04-17 11:22:06 +02:00
overview.asciidoc
security.asciidoc