Objectives:	Understand the functionality provided by autonomous transactions Understand limitations, dangers, and side-effects of autonomous transactions Learn how autonomous transactions can be used to solve real problems
Abstract:	Effective usage of transaction control provides many interesting development options. Synchronizing the rules repository with the database objects in a rules-based environment is always a challenge. Defining INSTEAD-OF triggers as autonomous transactions solves this problem, making it possible to fire DDL immediately when the view receives an update of the core repository data. Autonomous transactions allow developers to get around the restriction of “no DML/DDL in functions that can be used in SQL. This can be very handy for functions that return collections or even function-based views. This presentation discusses when, why, and how to use autonomous transactions in conjunction with other features, such as object collections, Dynamic SQL, INSTEAD OF triggers, etc. Additional focus will be placed on critical issues such as resolving self-mutating tables, preventing deadlocks, and understanding read/write-consistency and its corresponding side-effects.
Audiernce Focus:	Developers
Expertise:	Intermediate
Track:	Development
Date:	Monday, April 14, 2008
Time:	3:30 PM - 4:30 PM