RE: uses of autonomous transactions

As I mentioned in my original reply, AT's can be a great tool or they can kill your performance and data integrity. I primarily use them for logging and have never needed them to avoid a mutating table error. But knowing that the tool exists is worthwhile even if it is band-aid unless I am the only one that has been called in to an environment with a bad database design (sarcasm intended).  

Ken

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Jared Still
Sent: Thursday, May 29, 2008 3:50 PM
To: jonathan_at_jlcomp.demon.co.uk
Cc: oracle-l_at_freelists.org
Subject: Re: uses of autonomous transactions  

n Sat, May 24, 2008 at 2:26 AM, Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk> wrote:  

                    For example you can avoid mutating table

With a high probability that most people don't realised what the side-effects of read-consistency are going to do, and end up with incorrect data.

I didn't see that one.

Use of triggers to avoid mutating tables is generally a band-aid approach to dealing
with sub-optimal database design.

-- 
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist



--
http://www.freelists.org/webpage/oracle-l