Re: Development of touching tables in functions
I'd like to be able to maintain history tables via triggers. That is, when an insert or update is made to table foo, a copy of that row (more/less) is added to a table called foo_hist..
We currently enforce this via application level code that does and insert/select but havbing this done at the app level is not ideal.
Any idea if this is/will be supported in 5.0? Is there any mention of this issue with respect to the release roadmap?
Subject
Views
Written By
Posted
3740
April 07, 2005 02:02AM
2596
April 07, 2005 04:57AM
2244
April 08, 2005 12:24AM
2279
April 08, 2005 03:39AM
2395
April 08, 2005 05:56AM
2293
April 14, 2005 03:17AM
2312
April 19, 2005 01:11AM
2494
April 19, 2005 02:17AM
2366
April 19, 2005 04:03AM
2405
April 19, 2005 04:25AM
2289
April 19, 2005 04:38AM
2328
April 20, 2005 03:18AM
2483
April 19, 2005 04:49AM
2332
April 19, 2005 05:13AM
2355
April 20, 2005 06:02AM
Re: Development of touching tables in functions
2312
April 22, 2005 12:52AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.