Skip to content
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

CONNECTION_PROPERTY_PROXY_CLIENT_NAME not present in OracleR2dbcOptions #154

Closed
deb538 opened this issue Sep 18, 2024 · 3 comments · Fixed by #155
Closed

CONNECTION_PROPERTY_PROXY_CLIENT_NAME not present in OracleR2dbcOptions #154

deb538 opened this issue Sep 18, 2024 · 3 comments · Fixed by #155

Comments

@deb538
Copy link

deb538 commented Sep 18, 2024

OracleConnection class (https://docs.oracle.com/en/database/oracle/oracle-database/19/jajdb/oracle/jdbc/OracleConnection.html) has a field CONNECTION_PROPERTY_PROXY_CLIENT_NAME
image

We use this field in our application.

We are moving to R2DBC. Extended options supported by Oracle R2DBC in https://github.com/oracle/oracle-r2dbc/blob/main/src/main/java/oracle/r2dbc/OracleR2dbcOptions.java does not have field CONNECTION_PROPERTY_PROXY_CLIENT_NAME.
image

Please review and let me if there is any other way to pass proxy client name or it needs a fix.

@Michael-A-McMahon
Copy link
Member

We should add this into OracleR2dbcOptions. Let's leave this issue open as a reminder to do that.

Working with the current release of Oracle R2DBC, it should be possible to configure this as a system property "-Doracle.jdbc.proxyClientName=...", or you can configure this in a connection properties file.

@deb538
Copy link
Author

deb538 commented Sep 18, 2024

-Doracle.jdbc.proxyClientName=..." works. Thanks for your quick response.
May I know when the code fix can be available.

@Michael-A-McMahon
Copy link
Member

Sorry, but I can't commit to any timeline right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants