Skip to Main Content

Breadcrumb

Connor and Chris will both be at AI World from October 12 to October 17 , the premier Oracle conference of 2025. If you're in Vegas, please come say Hi or pop into our sessions

Question and Answer

Chris Saxon

Thanks for the question, Mauricio.

Asked: September 04, 2024 - 1:23 pm UTC

Last updated: January 21, 2025 - 1:27 pm UTC

Version: 19c

Viewed 1000+ times

You Asked

It took me a while pick database development over dabase administration, concerning a editions.

My questions is simple, if I've decided to create an editioning view over a table with N triggres, what would I do about this??

some people says all triggers must be moved to the editioning view. Other says if there are trigger oriented to update auditing column (created by, date of creation, updated, etc) or update surrogated key columns (pre-insert), this kind of triggers must remain in the table.

Kind regards

Mauricio

and Connor said...

if I've decided to create an editioning view over a table with N triggres, what would I do about this??


All triggers should be moved to the editioned view. Triggers are code, and code is subject to change.

(I would love to have a dollar for every time someone said to me: "This code will NEVER change, so we don't need to version it" :-) )

If you're new to EBR, good friend has an excellent intro series on it

https://db-oriented.com/my-ebr-blog-post-series/

Rating

  (2 ratings)

Is this answer out of date? If it is, please let us know via a Comment

Comments

Mauricio Fernández, September 05, 2024 - 10:58 am UTC

Thaks Connor for thr answer. Last question, the triggers are always editionables? (PL/Saql) even there belong to the table and not an editioning view?

Kind regards

Mauricio
Chris Saxon
September 05, 2024 - 1:06 pm UTC

By default, yes. You can declare them to be NONEDITIONABLE though.

One exception to the rule

Oren Nakdimon, January 21, 2025 - 5:48 am UTC

Thanks for the shout-out, Connor!
I totally agree with the general rule: All triggers should be moved to the editioned view. However, I can think of one edge-case exception, when the trigger is on the child side of a foreign key constraint with the ON DELETE clause.
Encouraged by this thread, I've recently added a new post to my EBR series: https://db-oriented.com/2025/01/08/ebr-part-13-the-trouble-with-foreign-keys-with-on-delete-clause-and-related-triggers/
Thanks,
Oren.
Chris Saxon
January 21, 2025 - 1:27 pm UTC

Thanks for sharing Oren.
more

Connor and Chris don't just spend all day on AskTOM. You can also catch regular content via Connor's blog and Chris's blog. Or if video is more your thing, check out Connor's channel and Chris's channel from their Youtube channels. And of course, keep up to date with AskTOM via the official twitter account.

More to Explore

PL/SQL demos

Check out more PL/SQL tutorials on our LiveSQL tool.

PL/SQL docs

PL/SQL reference manual from the Oracle documentation library