diff options
| author | svoj@mysql.com/june.mysql.com <> | 2007-03-30 13:00:21 +0500 |
|---|---|---|
| committer | svoj@mysql.com/june.mysql.com <> | 2007-03-30 13:00:21 +0500 |
| commit | 556de62f8da2c1cf6c1656efd2f903f01250e01d (patch) | |
| tree | 5b389c352c3cde60ec4de181522882af5dd2b654 /mysys | |
| parent | 75f0416532c431f094b191dba637612c80bf651d (diff) | |
| download | mariadb-git-556de62f8da2c1cf6c1656efd2f903f01250e01d.tar.gz | |
BUG#26138 - REPAIR TABLE with option USE_FRM erases all records in
ARCHIVE table
ARCHIVE table was truncated by REPAIR TABLE ... USE_FRM statement.
The table handler returned its file name extensions in a wrong order.
REPAIR TABLE believed it has to use the meta file to create a new table
from it.
With the fixed order, REPAIR TABLE does now use the data file to create
a new table. So REPAIR TABLE ... USE_FRM works well with ARCHIVE engine
now.
This issue affects 5.0 only, since in 5.1 ARCHIVE engine stores meta
information and data in the same file.
Diffstat (limited to 'mysys')
0 files changed, 0 insertions, 0 deletions