Skip to Main Content

Breadcrumb

Question and Answer

Chris Saxon

Thanks for the question, Mauricio.

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

Last updated: September 05, 2024 - 1:06 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

  (1 rating)

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.

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