Bug #30757 | "range checked for each record" is not well-documented | ||
---|---|---|---|
Submitted: | 1 Sep 2007 14:09 | Modified: | 22 Feb 2008 15:23 |
Reporter: | Baron Schwartz (Basic Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | OS: | Any | |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
Tags: | qc |
[1 Sep 2007 14:09]
Baron Schwartz
[1 Sep 2007 20:09]
Valeriy Kravchuk
Thank you for a reasonable documentation request.
[22 Feb 2008 15:23]
Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products. Added to explanation of "Range checked for ...": "Indexes are numbered beginning with 1, in the same order as shown by SHOW INDEX for the table. The index map value N is a bitmask value that indicates which indexes are candidates. For example, a value of 0x19 (binary 11001) means that indexes 1, 4, and 5 will be considered." Also updated examples to use "index map" rather than "key map" and hex values of N. (The change to "index map" occurred in ancient history, in MySQL 3.22.5.)