-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] validate driver and server constraints on connect #1210
Labels
Comments
rosswbrown
changed the title
[FEATURE]
[FEATURE] validate driver and server constraints on connect
Dec 20, 2023
Tracked with: W-14701240 |
Very useful feature. Another use case: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
One JDBC driver can be used to connect to different versions of the same database, or even different database kinds (e.g. Postgres wire protocol is used by different database venders). And different versions of JDBC might be used as well.
I my case, I want to validate the database product name and version in my Tableau connector.
Describe the solution you'd like
I would like to access and validate some attributes via JDBC DatabaseMetaData interface, e.g.
getDatabaseProductName()
,getDatabaseProductVersion()
,getDriverName()
andgetDriverVersion()
. If the validation fails, error it out and close connecting.Regarding to the validation rules, I would like to be able to define a callback function somewhere so Tableau connector SDK can call it after connection is made.
Describe alternatives you've considered
No workaround exist for this problem.
About You
Name: Song Gao
Company: Starburst Data
The text was updated successfully, but these errors were encountered: