Bug #38418 Old information on the DELETE documentation page
Submitted: 28 Jul 2008 23:52 Modified: 29 Jul 2008 0:11
Reporter: Federico Razzoli
Status: Verified
Category:Server: Docs Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Paul DuBois Target Version:
Triage: Needs Triage: D4 (Minor)

[28 Jul 2008 23:52] Federico Razzoli
Description:
Copied from http://dev.mysql.com/doc/refman/5.0/en/delete.html

---------------

 If you delete the row containing the maximum value for an AUTO_INCREMENT column, the
value is reused later for a BDB table, but not for a MyISAM or InnoDB table. If you
delete all rows in the table with DELETE FROM tbl_name (without a WHERE clause) in
AUTOCOMMIT  mode, the sequence starts over for all storage engines except InnoDB and
MyISAM. There are some exceptions to this behavior for InnoDB  tables, as discussed in
Section 13.2.6.3, “How AUTO_INCREMENT Handling Works in InnoDB”.

For MyISAM and BDB tables, you can specify an AUTO_INCREMENT secondary column in a
multiple-column key. In this case, reuse of values deleted from the top of the sequence
occurs even for MyISAM tables. See Section 3.6.9, “Using AUTO_INCREMENT”.

---------------

1) BDB is no more supported
2) Now there are new storage engines; what about ARCHIVE, CVS, etc?

How to repeat:
.
[29 Jul 2008 0:11] Miguel Solorzano
Thank you for the bug report.