如何使用其他連接表中的記錄對記錄進行歸檔？

Question

我有8個表：

users: 
    uid 
users_removed: 
    uid 
messages: 
    mid 
    uid FK users (uid) 
messages_removed: 
    mid 
    uid 
comments: 
    cid 
    mid FK messages (mid) 
comments_removed: 
    cid 
    mid 
files: 
    fid 
    mid FK messages (mid) 
files_removed: 
    fid 
    mid 

當我從表中刪除記錄「用戶」我想（從用戶在刪除之前）將其移動到users_removed表。我還希望將所有相應的消息（以及文件和註釋）移至* _removed表。

我使用觸發器：

CREATE TRIGGER delete_user BEFORE DELETE ON users 
    FOR EACH ROW BEGIN 
     INSERT IGNORE INTO users_removed 
      SELECT * FROM users WHERE uid = OLD.uid; 
     DELETE FROM messages WHERE OLD.uid in (owner_id, author_id); 
    END 
| 

CREATE TRIGGER delete_message BEFORE DELETE ON messages 
    FOR EACH ROW BEGIN 
     INSERT IGNORE INTO messages_removed 
      SELECT * FROM messages WHERE mid = OLD.mid; 
     DELETE FROM comments WHERE mid = OLD.mid; 
     DELETE FROM files WHERE mid = OLD.mid; 
    END 
| 

CREATE TRIGGER delete_comment BEFORE DELETE ON comments 
    FOR EACH ROW BEGIN 
     INSERT IGNORE INTO comments_removed 
      SELECT * FROM comments WHERE cid = OLD.cid; 
    END 
| 

CREATE TRIGGER delete_file BEFORE DELETE ON files 
    FOR EACH ROW BEGIN 
     INSERT IGNORE INTO files_removed 
      SELECT * FROM files WHERE fid = OLD.fid; 
    END 
| 

但它與> 5萬個用戶的速度很慢，> 1M消息，評論和文件。

有沒有快速的方法來做到這一點？

Answer 1

1. 有沒有快速的方法來做到這一點。假設你使用的是InnoDB，你必須編寫一個表條目，刪除一個表條目引用，然後InnoDB做第二次清理運行以實際擺脫它（刪除代價昂貴）。然後，隨着您隨着時間的推移刪除更多用戶，數據庫中的這些漏洞幾乎肯定會最終損害性能。

2. 如果您要保存用戶信息，爲什麼不直接在enum（true，false）的用戶表中添加一個名爲「active」的用戶表？