On 31.03.2017 14:35, jerome brauge
wrote:
Vladislav,
It’s weird to implement setClientInfo
without provide a way to see values (MySql Connector J
only put values in a hashtable, I do not know what it is
for !)
On Oracle, Sybase, SQLServer and DB2, these
values are pushed in processes system view.
https://dev.mysql.com/doc/refman/5.6/en/session-connect-attrs-table.html
is actually something like that, and both MySQL and
MariaDB drivers support connectionAttributes in the
connection URL, so maybe it is something that you can use.
It is weird that these client connection attributes are
tied to performance schema, that can be switched off
during runtime, or during compilation. I'd rather have it
in the information schema, that cannot be switched off.
Maybe it is something that we need to fix.
As
much as possible, we want avoid to use one solution per
database vendor or a feature with a performance cost.
But
I agree, it's boring if it’s implementation can change in
future.
Thanks.
Regards
Jérôme.
On 3/31/2017 12:16 PM, jerome brauge
wrote:
Hi Vladislav,
As I understand is that this plugin allow
user to see their own session variables.
Here, we can see these information for
each session (for monitoring purpose, licensing
control, …)
Is it correct ?
Yes, I think you're correct and I'm not .
I was chatting to Diego, our JDBC expert, he does not
seem to recall the reason session variables were used. I
assume the implementation can change without any
notification.
MySQL Connector/J does not issue SET as I understand at
the moment, does not talk to DB at all.
But for monitoring purposes, there is something in
performance schema you might find useful
https://dev.mysql.com/doc/refman/5.6/en/session-connect-attrs-table.html
, most current drivers populate this table with
similar information to Appname, client user, client
hostname
Regards,
Jérôme.