Re: Autonomous Transactions - Good or Bad
- From: Adam Musch <ahmusch@xxxxxxxxx>
- To: JChirco@xxxxxxxxxx
- Date: Mon, 12 Mar 2012 13:21:45 -0500
If you're using it for anything other than specific logging or
auditing requirements that are impractical to implement any other way,
you are using it wrong.
Transactions should be properly scoped for all-or-nothing. If you
don't want or need ACID compliance at the data persistence layer, then
you shouldn't be paying Oracle the exorbitant price that comes with
it.
I'd be very curious if I were you to hear why they "need to run other
transactions over their current one." It sounds to me like they've
got asynchronicity requirements that would be better served with an
architectural change.
On Mon, Mar 12, 2012 at 9:19 AM, Jeff Chirco <JChirco@xxxxxxxxxx> wrote:
> I recently saw Tom Kyte and he mentioned how he doesn't like autonomous
> transactions and said you should never really use them except for when
> logging errors. I didn't understand what was so bad about them and didn't
> get a chance to ask him. So I was wondering if any of you agree with this
> statement and why? I personally try to avoid them but I have other
> developers that use them frequently because they need to run other
> transactions over their current one.
> Thanks for any info.
> Jeff
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
--
Adam Musch
ahmusch@xxxxxxxxx
--
//www.freelists.org/webpage/oracle-l
Other related posts:
