title: Parameterized trigger - concurrency concerns
body: <p>My question is quite similar to <a href="https://stackoverflow.com/questions/1880729/how-to-send-arbitrary-parameters-to-oracle-trigger">this one</a> but I need more guidance. I also read the <a href="http://docs.oracle.com/cd/B28359_01/network.111/b28531/app_context.htm#DBSEG011" rel="nofollow noreferrer">Oracle context</a> doc.</p>
  
  <p>The current (test) trigger is :</p>
  
  <pre><code>CREATE OR REPLACE TRIGGER CHASSIS_DT_EVNT_AIUR_TRG_OLD AFTER DELETE OR INSERT OR UPDATE
  OF ETA
  ON CHASSITRANSPORTS
  REFERENCING NEW AS New OLD AS Old
  FOR EACH ROW
  DECLARE
  BEGIN
     INSERT INTO TS_CHASSIS_DATE_EVENTS (CHASSISNUMBER,DATETYPE,TRANSPORTLEGSORTORDER,OLDDATE,CREATEDBY,CREATEDDATE,UPDATEDBY,UPDATEDDATE) VALUES (:old.chassino,'ETA',:old.sortorder,:old.eta,'xyz',sysdate,'xyz',sysdate);
  
     EXCEPTION
       WHEN OTHERS THEN
          NULL;
  END TS_CHASSIS_DT_EVNT_AIUR_TRG;
  </code></pre>
  
  <p>Now the 'CREATEDBY', 'UPDATEDBY' will be the web application users who have logged in and made the changes which caused the trigger execution, hence, these values need to be passed from the application.</p>
  
  <p>The web application :</p>
  
  <ol>
  <li>Is deployed in Websphere Application Server where the datasources are configured</li>
  <li>As expected, is using db connection pooling</li>
  </ol>
  
  <p>My question is which approach mentioned in the thread and the doc. should I take to avoid the 'concurrency' issues i.e the updates by the app. users in multiple sessions at the application level as well the db level should not interfere with each other.</p>