Bernandas Savarimuthu

SQL & PL/SQL Colletions

Wednesday, September 10, 2008

Mutating table error

This happens with triggers. It occurs because the trigger is trying to update a row it is currently using. The usual fix involves either use of views or temporary tables so the database is selecting from one while updating the other.
Posted by Bernandas at 1:11 AM

No comments:

Post a Comment

Newer Post Older Post Home
Subscribe to: Post Comments (Atom)
free counters

Subscribe To

Posts
Atom
Posts
Comments
Atom
Comments

Total Pageviews

HitCount

hit counter
hit counter
Nothing comes easy...

Blog Archive

  • ►  2014 (1)
    • ►  November (1)
  • ►  2012 (3)
    • ►  September (1)
    • ►  August (2)
  • ►  2011 (4)
    • ►  April (1)
    • ►  January (3)
  • ►  2010 (12)
    • ►  December (1)
    • ►  September (1)
    • ►  July (2)
    • ►  June (5)
    • ►  May (1)
    • ►  March (2)
  • ►  2009 (10)
    • ►  September (1)
    • ►  February (5)
    • ►  January (4)
  • ▼  2008 (68)
    • ►  October (37)
    • ▼  September (31)
      • Cache and NoCache
      • Nowait
      • ORA-01000 - Maximun open cursors exceeded
      • init.ora
      • Query Collections
      • Sequence of trigger when form is opened & closed
      • The TRUNC() function
      • VARRAYS
      • ROWID
      • View
      • Pseudo column
      • Joins
      • CO-RELATED SUBQUERY
      • SQLCODE and SQLERRM
      • %ROWTYPE and %TYPE
      • Mutating table error
      • Anonymous block
      • TNSNAMES.ORA
      • IN vs Exists
      • When a procedure or package gets invalidated?
      • ACID
      • Automomus transaction
      • Cartesian join
      • Coalesce
      • Nvl
      • Nvl2
      • Decode
      • Nullif
      • DNS
      • Varchar vs Varchar2
      • Dual table

About Me

My photo
Bernandas
View my complete profile
Picture Window theme. Theme images by Airyelf. Powered by Blogger.