Skip to Main Content

Infrastructure Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Monitoring Oracle Linux Virtualization Manager with Oracle Enterprise Manager

SHayler-OracleApr 1 2020 — edited Jun 5 2020

Comments

BluShadow

Why do you want a trigger for this?

If you're using apex, then you just need to create another process to happen after the insertion(s) have taken place, and then apply whatever insert code you want in that.

BluShadow

p.s. there's also an space where you can get help if you are unsure how to achieve it in Apex.

Marco Foxx

Thanks for feed back. Please consider DML process as which APEX provides which is inbuilt process where by i don't have to code manually which is better that way only.

Billy Verreynne

On insert/update/delete trigger on table temp_detail, adjust that row's ID totals in table temp_head.

But the solution you are describing here sounds flawed. Why temp tables? Why duplicate rows from the data table into the detail table? What is the use case for the header table?

Marco Foxx

Billy~Verreynne wrote:

On insert/update/delete trigger on table temp_detail, adjust that row's ID totals in table temp_head.

But the solution you are describing here sounds flawed. Why temp tables? Why duplicate rows from the data table into the detail table? What is the use case for the header table?

- temp tables are just naming convection so can create a show case to put here.

- header table will further be processed for other operations as well as detail table.

- its not duplicate data every table will be used for different purposes.

Thank you

BluShadow

Marco Foxx wrote:

Thanks for feed back. Please consider DML process as which APEX provides which is inbuilt process where by i don't have to code manually which is better that way only.

Sorry, that doesn't make sense.  Apex is meant to be coded just as much as we write code on the database.

If you must, then write a procedure on the database and have a post insertion process in Apex that calls that.

Triggers are not the correct place to be analysing and doing DML that isn't solely related to the table that the trigger is on.

1 - 6

Post Details