Oracle trigger updating predicate multiple columns Chat iranian people
regards & thanks pjp June 29, 2005 - am UTC select as many old columns as you want and as many new columns as you want??? But when i did the same with the syntax given i got this error ora-01779 cannot modify a column which maps to a non key preserved value. I tried doing the same through this update ( select old. WORKEXTENSION from TBL_VOTERS old, VOTERSWITHNUMBERS new where old. While a trigger is , which determines whether the trigger fires before or after the triggering statement runs and whether it fires for each row that the triggering statement affects. If the trigger is created on a schema or the database, then the triggering event is composed of either DDL or database operation statements, and the trigger is called a )".By default, a trigger is created in the enabled state. When a trigger fires, tables that the trigger references might be undergoing changes made by SQL statements in other users' transactions. I want to write SQL ( not PL/SQL ) to update transaction table from mapping table at one stroke. regards & thanks pjp update ( select old.old_account_number, new.new_account_number from old_table old, mapping_table new where old.old_account_number = new.new_account_number ) set old_account_number = new_account_number; disabling foreign keys during the operation and enabling them afterward. update ( select old.old_account_number, new.new_account_number from old_table old, mapping_table new where old.old_account_number = new.old_account_number ) set old_account_number = new_account_number; (ie in the subquery, match the old account numbers not try matching the old in the old table to the new in the mapping table) Of course if the original posting had the CREATEs/INSERTS etc, it would have a quick and east test. I have to update a transaction table where mapping is existing with old account no and new account number.
However, triggers can enforce some complex business rules that constraints cannot. A trigger can have the same name as another kind of object in the schema (for example, a table); however, Oracle recommends using a naming convention that avoids confusion. By default, a trigger is created in the enabled state.You can disable an enabled trigger, and enable a disabled trigger.A procedure is explicitly run by a user, application, or trigger.Triggers are implicitly fired by Oracle when a triggering event occurs, no matter which user is connected or which application is being used.