Paul,
----- Original Message ----- From: "Paul Mallach" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Monday, December 06, 2004 4:26 PM
Subject: innodb: TRUNCATE vs. DELETE FROM
Hi!
Is TRUNCATE optimized for innodb tables in MySQL 4.1.7?
http://dev.mysql.com/doc/mysql/en/TRUNCATE.html says:
"For InnoDB, TRUNCATE TABLE is mapped to DELETE, so there is no difference.".
But http://dev.mysql.com/doc/mysql/en/InnoDB_tuning.html claims:
"Beware also of other big disk-bound operations. Use DROP TABLE or TRUNCATE
TABLE (from MySQL 4.0 up) to empty a table, not DELETE FROM tbl_name."
thank you for pointing out this error. TRUNCATE is still mapped to DELETE FROM ... in 5.0. I have now corrected the online manual.
bye, Paul.
-- Paul Mallach ARIVA.DE AG Ostseekai 2 D - 24103 Kiel
Tel: +49 (0)431/97108-24 E-Mail: [EMAIL PROTECTED] Fax: +49 (0)431/97108-29 Internet: http://www.ariva.de
Best regards,
Heikki Tuuri
Innobase Oy
Foreign keys, transactions, and row level locking for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables
http://www.innodb.com/order.php
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
