Consequences of using DBMS_APPLICATION_INFO.SET_CLIENT

From: April <PrivateBenjamin_at_hushmail.com>
Date: 15 Oct 2002 11:32:27 -0700
Message-ID: <54df0379.0210151032.238d6530@posting.google.com>

Are there any multiuser issues regarding creating dynamic views using DBMS_APPLICATION_INFO.SET_CLIENT_INFO in the manner as below

CREATE OR REPLACE VIEW VW_MYINVESTMENTS ( DRIVER, INV#, DESCRIPTION, USERID ) AS SELECT

  vw_TBLINVESTMENTS.INV_DRIVER# AS Driver,
  vw_TBLINVESTMENTS.INVESTMENT# AS "Inv#",
  vw_TBLINVESTMENTS.INVESTMENT_DESCRIPTION AS Description,
  VW_TBLEMPLOYEE.USERID

FROM
  VW_TBLINVESTMENTS,
  VW_TBLEMPLOYEE
WHERE
  VW_TBLINVESTMENTS.Employee# = vw_TBLEmployee.Employee# and   VW_TBLEMPLOYEE.userid = userenv('client_info')

then -------

"BEGIN DBMS_APPLICATION_INFO.SET_CLIENT_INFO ( & '" & param & "')" &
"; END;"
For example, when multiple users are setting the environment variable will that affect the other users?

Thanks
April Received on Tue Oct 15 2002 - 13:32:27 CDT

Consequences of using DBMS_APPLICATION_INFO.SET_CLIENT_INFO ???