Bug #506 | MySQL 4.0.13 files to access the table MySQL 4.0.12, 3.23.57 opens file | ||
---|---|---|---|
Submitted: | 26 May 2003 8:55 | Modified: | 16 Jun 2003 10:07 |
Reporter: | Peter Zaitsev (Basic Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: MyISAM storage engine | Severity: | S3 (Non-critical) |
Version: | 4.0.13 | OS: | Any (all) |
Assigned to: | Sergei Golubchik | CPU Architecture: | Any |
[26 May 2003 8:55]
Peter Zaitsev
[28 May 2003 5:02]
Ramil Kalimullin
I spent some time digging the problem. What I found is: 1. it seems to me that problem is in FULLTEXT-related code something strange happens in myisam/mi_open.c (lines 332 - 368 in the latest 4.1 tree) 2. This code was added by serg: ChangeSet 1.1396 03/01/21 19:24:34 serg@serg.mysql.com +25 -0 Two-level index structure for FULLTEXT indexes .......... myisam/mi_open.c 1.55 03/01/02 21:00:16 serg@sergbook.mysql.com +16 -7 preserve 4.0 compatibility for FULLTEXT indexes .......... myisam/mi_open.c 1.56 03/01/06 12:37:40 serg@sergbook.mysql.com +17 -7 creating two-level ft tree in mi_repair_by_sort, cleanups
[16 Jun 2003 10:07]
Sergei Golubchik
fixed in 4.0.14.