Max Castagno
Member²
Hi,
I've just a problem with AfterConnect.sql script.
I need to change the informations in V$Session table pertinent to MODULE, ACTION and CLIENT_INFO fields whenever a connection is made using PL/SQL Dev.
Now I've introduced this in AfterConnect.sql nd Login.sql scripts:
BEGIN
DBMS_APPLICATION_INFO.SET_MODULE('Module', 'Action');
DBMS_APPLICATION_INFO.SET_CLIENT_INFO('Client Info');
END;
/
For the main connection (browser) and the Command Windos, this works fine. But when I open a SQL Window the script is still executed, so I saw the CLIENT_INFO information changed, but the MODULE and ACTION fields are overwritten by PL/SQL Dev itself with "PL/SQL Developer" and "SQL Window - New" strings.
The workaround is, immediatiatly after a new SQL window session is started, to execute the same block contained in AfterConnect.Sql script, but this is not so friendly....
Is it possible to had a configuration option that permits to disable the "SQL Window" override?
Thanks in advance
Max
I've just a problem with AfterConnect.sql script.
I need to change the informations in V$Session table pertinent to MODULE, ACTION and CLIENT_INFO fields whenever a connection is made using PL/SQL Dev.
Now I've introduced this in AfterConnect.sql nd Login.sql scripts:
BEGIN
DBMS_APPLICATION_INFO.SET_MODULE('Module', 'Action');
DBMS_APPLICATION_INFO.SET_CLIENT_INFO('Client Info');
END;
/
For the main connection (browser) and the Command Windos, this works fine. But when I open a SQL Window the script is still executed, so I saw the CLIENT_INFO information changed, but the MODULE and ACTION fields are overwritten by PL/SQL Dev itself with "PL/SQL Developer" and "SQL Window - New" strings.
The workaround is, immediatiatly after a new SQL window session is started, to execute the same block contained in AfterConnect.Sql script, but this is not so friendly....
Is it possible to had a configuration option that permits to disable the "SQL Window" override?
Thanks in advance
Max