Insert Records into another tables

Question

Hi guyz,
I have four tables as below
1) employee
empid (primary key)
deptid
emp_name
work_location
date_of_join
emp_status
date
2) Termination
empid reference employee
deptid
emp_name
work_location
terminate_date
3) Resignation
empid reference employee
deptid
emp_name
work_location
resign_date
4) Vacation
empid reference employee
deptid
emp_name
work_location
vac_date
i have list item on employee form --> emp_status is list item whic contain Termination, Resignation, Vacation
i want to update employee as well other tables if user select the respected field from the list item.
if the user select termination/resignation from the list item the date item will be enable and user should enter the date,otherwise give the error on commit please enter the date and when user commit the record on employee it should update the table employee and delete the record belongs to Termination/Reisgnation and the record will be insert into Termination/Resignation table as select by user from list item.i tried this before but im fail i write the below code on pre-update trigger as below
begin
insert into termination
(empid,deptid,emp_name,work_location,termination_date)select (empid,deptid,emp_name,work_location,date from employee where emp_status='Termination';
delete from employee where emp_status='Termination' ;
end;
same as on resignation
anybuddy help me how to do this task? to update the tables. im new in oracle.
Regards
Edited by: user10648713 on Dec 21, 2008 4:29 AM

Answer 1

You run into the classic Mutating table problem. You cannot issue DML-statement against the same table the trigger is based on in a FOR EACH ROW-trigger.
But even worse, you will cause any kind of client program to get in trouble if you implement such a logic. The client issues an update and as a result the record gets deleted. And, for you have a forms-module based i tell you that you will get problems with your forms-module.
I still can't see whats the sense behind it, putting records into different tables dependant on a status. Oracle is built to manage large data volumes, so even for a large number of records that doesn't make sense to me.
But anyway if you still want to deal with that multi-table-approach, go for the following:
You will need three triggers on your table: a before-statement, an after-statement and a for-each-row-trigger:
The before-statement will initialize a list of PK-Items
The for-each-row will add the id of the processed row to the list
The after-statement will loop over the list and process the rows.
Create a Package for handling the logic including three procedures
CREATE OR REPLACE PACKAGE PK_TRIGGER IS
  PROCEDURE PR_BS;
  PROCEDURE PR_ARIU(i_nEmpId IN NUMBER);
  PROCEDURE PR_AS;
END;
CREATE OR REPLACE PACKAGE BODY IS
  TYPE tData IS TABLE OF NUMBER INDEX BY BINARY_INTEGER;
  lData tData;
  PROCEDURE PR_BS IS
  BEGIN
    lData.DELETE;
  END;
  PROCEDURE PR_ARIU(i_nEmpId IN NUMBER) IS
    iPos PLS_INTEGER:=lData.COUNT+1;
  BEGIN
    lData(iPos):=i_nEmpId;
  END;
  PROCEDURE PR_AS IS
    CURSOR crEmp(i_nEmpId IN NUMBER) IS
      SELECT *
        FROM EMP
       WHERE EMP_ID=i_nEmpId;
    recEmp crEmp%ROWTYPE;
    iPos PLS_INTEGER;
  BEGIN
    iPos:=lData.FIRST;
    LOOP
      EXIT WHEN iPos IS NULL;
      -- Do whatever you want with the data in the record
      OPEN crEmp(lData(iPos));
      FETCH crEmp INTO recEmp;
      IF crEmp%FOUND THEN
        IF :NEW.EMP_STATUS='Termination' THEN
          DELETE FROM emp
           WHERE EMPID=lData(iPos);
          INSERT INTO TERMINATION (
            empid,
            deptid,
            emp_name,
            work_location,
            t_date
          ) VALUES (
            recEmp.empid,
            recEmp.deptid,
            recEmp.emp_name,
            recEmp.work_location,
            sysdate
        END IF;
      END IF; 
      CLOSE crEmp;
      -- Process next record
      iPos:=lIds.NEXT(iPos);
    END LOOP;
    lIds.DELETE;
  END;
END;Now create the three triggers calling the appropiate procedures.