ORACLE opdaterer poster med 1 til mange tabelrelationer i en trigger

Følgende VIEW vil hente person_id'er fra HISTORY_TRANSACTION-tabellerne, tilføje og 'X' til hver enkelt af dem, og også samle alle personer, der er "associeret" med (eller:kortlagt til) disse id'er fra CONSOLIDATED_NUMBERS, og tilføjer også en 'X' til deres id'er. (Sidebemærkning:det ser ud til, at din PERSON-tabel indeholder et rekursivt forhold, så man kunne skrive en rekursiv forespørgsel. Du vil dog have en grund til at modellere CONSOLIDATED_NUMBERS-tabellen, så vi vil bruge en JOIN her.)

SE

create or replace view personx
as
with PID as (
  select distinct person_id
  from history_transaction
)
select person_id, 'X' as woman_act  -- [Q1] all person_ids from history_transaction
from PID
union
select P.id, 'X' as woman_act       -- [Q2] all person_ids associated with ids from Q1
from person P
  join consolidated_numbers C
    on P.registration_number = C.secondary_number
    and C.person_id in (
      select person_id from PID
    )
;

-- with your initial test data, we get:
select * from personx ;
+---------+---------+
|PERSON_ID|WOMAN_ACT|
+---------+---------+
|132      |X        |
|151      |X        |
+---------+---------+
 

Lad os nu fjerne/tilføje nogle data og køre et par tests (se også:> ):

Hvis du - som angivet i din kommentar - skal gemme en værdi i WOMAN_ACT-kolonnen (selvom det tilsyneladende er en "afledt værdi"), kan du skrive en pakke, der indeholder procedurer for alle nødvendige DML-operationer - stadig uden at bruge en trigger. Men uden at kende hele historien er det svært at afgøre, om dette ville være den bedste vej frem. Følgende eksempel bruger en lille pakke, der indeholder procedurer til indstilling af WOMAN_ACT-værdier i PERSON-tabellen og en trigger, der udløses efter INSERTs/UPDATEs (tabel:HISTORY_TRANSACTIONS). DBfiddle her .

PERSON-tabel

create table person (
  id number primary key
, registration_number varchar2(9) unique
, primary_number varchar2(9)
, woman_act varchar2(1) check ( woman_act in ( null, 'X' ) )
);
-- all other tables: same as before
 

PAKKE

create or replace package pxpkg
is
  -- find out whether a certain id (table: PERSON) is a "parent" or a "child"
  function isparent( id_ number ) return boolean ;
  -- set 'X' values: id_ is a "parent"
  procedure setx_parentchildren( id_ number ) ;
  -- set 'X' values: id_ is a "child" 
  procedure setx_childsiblings( id_ number ) ;
end pxpkg ;
/
 

PAKKEBOD

create or replace package body pxpkg
is
  function isparent( id_ number )
  return boolean
  is
    secondarynumbers pls_integer := 0 ;
  begin
    select count(*) into secondarynumbers
    from consolidated_numbers
    where person_id = id_ ;
    if secondarynumbers = 0 then
      return false ;
    else
      return true ;
    end if ;
  end isparent ;
--
  procedure setx_parentchildren ( id_ number )
  is
  begin
    update person
    set woman_act = 'X'
    where id in ( 
      select id from person where id = id_ -- parent id
      union
      select id from person 
      where primary_number = ( 
        select registration_number from person where id = id_ -- parent id
      )
    ) ;
  end setx_parentchildren ;
--
  procedure setx_childsiblings ( id_ number )
  is
  begin
    update person
    set woman_act = 'X'
    where id in ( 
      with PID as (
        select id, primary_number from person
        where id = id_                    -- current id
          and primary_number is not null  -- child ids only
      )
      select id from PID
      union
      select id 
      from person 
      where registration_number in ( select primary_number from PID )
         or primary_number in ( select primary_number from PID )
    ) ;
  end setx_childsiblings ;
end pxpkg ;
/
 

TRIGGER

create or replace trigger pxtrigger
after insert or update on history_transaction
for each row
begin
  if pxpkg.isparent( :new.person_id ) then
    pxpkg.setx_parentchildren( :new.person_id )  ;
  else
    pxpkg.setx_childsiblings( :new.person_id )  ;
  end if ;
end pxtrigger ;
/
 

TEST:se DBfiddle