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
Include support for Client Application Identification [CORE5979] #6231
Comments
Commented by: @aafemt Already implemented. Look at MON$ATTACHEMENT.MON$REMOTE_PROCESS and content variable CLIENT_PROCESS. |
Commented by: Dyorgio Nascimento (dyorgio) Sorry for duplicate it Dimitry, is it already implemented on JDBC driver? I couldn't find it on documented properties. |
Commented by: Sean Leyne (seanleyne) Dyorgio, The implementation requires that SQL be executed against the MON$ATTACHMENT table, it is not a property that is "exposed" by any client/driver software. |
Modified by: Sean Leyne (seanleyne)status: Open [ 1 ] => Resolved [ 5 ] resolution: Duplicate [ 3 ] |
Commented by: Dyorgio Nascimento (dyorgio) Thank you Sean, My real issue is get it implemented on JDBC Client as connection extend property. I would like to help database managers to identify my application, not only an application that use JDBC driver (current implementation). Should I create another ticket or edit this? |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Commented by: @mrotteveel Jaybird has supported this since 2008 in version Jaybird 2.1.6 (see JDBC118). You can specify a system property org.firebirdsql.jdbc.processName with the desired name. But you are right, the existence of this is poorly documented. |
Modified by: @mrotteveel |
Commented by: @mrotteveel Added it to the (snapshot) documentation: https://firebirdsql.github.io/jaybird-manual/jaybird_manual.html#ref-processinfo |
Submitted by: Dyorgio Nascimento (dyorgio)
Duplicates JDBC334
Votes: 1
Include on connection/transaction control/table one more property/column: Client Application Identification.
Adjust client drivers to support specify the name of client app (by default driver put his own identification with version).
This is analogous to User-Agent HTTP header. Many databases support it.
It can be used to better analyze/monitor an application database access behaviour and other cool stuffs.
The text was updated successfully, but these errors were encountered: