Thread

  1. TRUNCATE violates Referential Integrity

    Oliver Elphick <olly@lfix.co.uk> — 2000-06-25T22:26:16Z

    This is a problem in release 7.0.2.
    
    I had never heard of the truncate command!  It seems that it ought to be
    disallowed on a table that is a target for RI checks, since checking that
    deletions are OK would frustrate the whole purpose of truncate as opposed
    to delete.
    
    ------- Forwarded Message
    
    Date:    25 Jun 2000 13:49:14 +0000
    From:    Grzegorz Stelmaszek <greg@tenet.pl>
    To:      submit@bugs.debian.org
    Subject: Bug#66232: postgresql: TRUNCATE doesn't check REFERENCE clause
    
    Package: postgresql
    Version: 7.0-release-1
    Severity: normal
    
    TRUNCATE'ing the table allows rows to be deleted in spite of the REFERENCES
    clause pointing to that table. These may bring the db to an inconsistent
    state.
    
    ...
    ------- End of Forwarded Message
    
    
    -- 
    Oliver Elphick                                Oliver.Elphick@lfix.co.uk
    Isle of Wight                              http://www.lfix.co.uk/oliver
    PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47  6B 7E 39 CC 56 E4 C1 47
    GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839  932A 614D 4C34 3E1D 0C1C
                     ========================================
         "Honour thy father and mother; which is the first  
          commandment with promise; That it may be well with 
          thee, and thou mayest live long on the earth."        
                              Ephesians 6:2,3