oracle - Should procedures and/or functions of the DBMS_STANDARD package be used in PL/SQL code? -

recently, encountered before insert or update trigger on table. in trigger, author relies on inserting , updating functions (both return boolean) of dbms_standard package determine if trigger fired before insert or before update.

for example:

create or replace trigger customer_trigger   before insert or update on customer   each row begin   if inserting     /* code */   end if;    if updating     /* other code */   end if; end; 

yes, know two, individual triggers have been written handle 2 events separately. that's not point of question.

after troubleshooting error being received these functions, received word (from oracle support) "dbms_standard routines not meant called user programs". true?

i find little strange, considering other procedures (such raise_application_error , commit) commonly used in pl/sql code.

the functions inserting, updating , deleting expressly provided use in writing trigger code (see trigger documentation), there absolutely no proscription against using those. similarly, raise_application_error documented intended use developers.

having described dbms_standard there functions in there don't know , perhaps shouldn't used in own code (for know) such grantee.

generally, if can find oracle official documentation telling how use something, ok use it.