• gkodinov/kgeorge@macbook.gmz's avatar
    Bug#23556: TRUNCATE TABLE still maps to DELETE · 5e0f4e53
    gkodinov/kgeorge@macbook.gmz authored
     This is the 5.0 part of the fix.
     Currently TRUNCATE command will not call
     delete_all_rows() in the handler (that implements
     the "fast" TRUNCATE for InnoDB) when there are
     triggers on the table.
     As decided by the architecture team TRUNCATE must
     use "fast" TRUNCATE even when there are triggers.
     Thus it must ignore the triggers. 
     Made TRUNCATE to ignore the triggers and call
     delete_all_rows() for all storage engines
     to maintain engine consistency.
    5e0f4e53
trigger.result 38.8 KB