You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In your Docs about Teradata you mention that it only supports Databases of version 17.20 and 17.10.
And you have an example that references the old Teradata JDBC Driver:
However lately the teradata drivers are also available on maven central, as noted on the driver page, and there are also much newer versions of the driver that are also compatible with the supported database versions:
Using the newer Driver seems to work fine (so far).
So maybe it you could update the documentation to mention that also the newer drivers are supported and drop the sentence that says that there is no such driver in maven central:
If you use Maven, note that this database does not provide its driver JAR on a public Maven repository, so you must install a local copy and add it as a dependency to your pom.xml file.
Also if you have a decent test setup it would be nice to include tests against the new driver version if such tests exist.
Search first
Description
In your Docs about Teradata you mention that it only supports Databases of version 17.20 and 17.10.
And you have an example that references the old Teradata JDBC Driver:
However lately the teradata drivers are also available on maven central, as noted on the driver page, and there are also much newer versions of the driver that are also compatible with the supported database versions:
Using the newer Driver seems to work fine (so far).
So maybe it you could update the documentation to mention that also the newer drivers are supported and drop the sentence that says that there is no such driver in maven central:
Steps To Reproduce
Expected/Desired Behavior
Liquibase Version
4.27.0
Database Vendor & Version
Teradata 17.20.03.20
Liquibase Integration
maven
Liquibase Extensions
liquibase-teradata
OS and/or Infrastructure Type/Provider
MacOS
Additional Context
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: