Costin Leau b376edf269

SQL: Move internals from TimeZone to ZoneId (#36651) ...

As the internals have moved to java.time, the usage of TimeZone itself
 should be minimized as it creates issues when being converted to ZoneId
Protocol wise the two are mostly identical so consumer should not see
 any difference.
Note that terminology wise, inside the docs, the public API and inside
 the protocol timeZone will continue to be used as it's more widely
 understood as oppose to zoneId which is an implementation detail
 specific to the JVM

Fix #36535

2018-12-17 13:55:44 +02:00

..

licenses

CORE: Upgrade to Jackson 2.8.11 (#32670)

2018-08-08 12:04:25 +02:00

src

SQL: Move internals from TimeZone to ZoneId (#36651)

2018-12-17 13:55:44 +02:00

build.gradle

Run forbidden api checks with runtimeJavaVersion (#32947)

2018-08-22 09:05:22 +03:00