Bug #26642 create index corrupts table definition in .frm
Submitted: 26 Feb 2007 17:55 Modified: 3 Jul 2007 18:40
Reporter: Martin Friebe (Gold Quality Contributor) (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.38 4.1.23 OS:Any (*)
Assigned to: Georgi Kodinov CPU Architecture:Any
Tags: corrupt table, INDEX, qc

File: Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

[26 Feb 2007 17:56] Martin Friebe
test case

Attachment: index_create.test (application/octet-stream, text), 12.74 KiB.

[26 Feb 2007 17:57] Martin Friebe
expected test result

Attachment: index_create.result (application/octet-stream, text), 34.48 KiB.

[26 Feb 2007 17:57] Martin Friebe
expected test result

Attachment: index_create.result (application/octet-stream, text), 34.48 KiB.

[26 Feb 2007 17:58] Martin Friebe
patch to fix the issue

Attachment: index_len_in_frm.patch (text/x-patch), 2.14 KiB.

[29 Mar 2007 21:52] Martin Friebe
enables the server to read a "broken" frm file

Attachment: read_invalid_frm.patch (text/x-patch), 2.70 KiB.

[2 Apr 2007 11:50] Martin Friebe
downport to 4.1, includes all patches. 4.1 needed additional fixes in unireq.cc. Test can be taken from previous post

Attachment: index_len_41.patch (text/x-patch), 6.14 KiB.