-
I have protocol.v1.alternate-header-name=Presto would be great to have a table like this (but I'm not sure the right version values...):
I vaguely recall timestamp types were changing to have a zone or not and also timestamp precision changing but not sure if the clients had backwards compatibility |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Currently, every Trino server supports all JDBC drivers >= 352 Also, the current JDBC driver supports Trino servers 15 releases back (eg for current release 395, the oldest Trino server supported is 380). You can derive the information you need from the information above. This project runs releases off of master, with no maintenance branches and has no capacity to maintain/document information about old releases. |
Beta Was this translation helpful? Give feedback.
Currently, every Trino server supports all JDBC drivers >= 352
trino/testing/trino-test-jdbc-compatibility-old-driver/bin/run_tests.sh
Line 13 in 029d9c0
Also, the current JDBC driver supports Trino servers 15 releases back
trino/testing/trino-test-jdbc-compatibility-old-server/src/test/java/io/trino/TestJdbcResultSetCompatibilityOldServer.java
Lines 72 to 79 in c637346