Bug #56628 ALTER TABLE .. KEY_BLOCK_SIZE=0 produces untrue warning or unnecessary error
Submitted: 7 Sep 2010 19:46 Modified: 14 Dec 2010 22:43
Reporter: Elena Stepanova Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.1.51, 5.5.6-m3, 5.6.0-m4 OS:Any
Assigned to: Kevin Lewis CPU Architecture:Any

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:

[21 Oct 2010 19:25] Kevin Lewis
A patch for mysql-5.5-innodb with comprehensive fixes for Bug56632 and Bug#56628

Attachment: Bug56632andBug56628.patch (application/octet-stream, text), 112.94 KiB.

[2 Nov 2010 3:45] Kevin Lewis
patch for mysql-5.5-innodb with better comments and replaced tests are removed.

Attachment: Bug56628and56632.patch (application/octet-stream, text), 105.09 KiB.

[2 Nov 2010 23:44] Kevin Lewis
Patch pushed to mysql-5.1-innodb

Attachment: Bug56628and56632.5.1.patch (application/octet-stream, text), 110.66 KiB.

[2 Nov 2010 23:49] Kevin Lewis
Patch pushed to mysql-5.5-innodb

Attachment: Bug56628and56632.5.5.patch (application/octet-stream, text), 110.45 KiB.

[3 Nov 2010 20:01] Kevin Lewis
patch for the mysql-next-mr branch

Attachment: Bug56628and55632.next.mr.patch (application/octet-stream, text), 2.12 KiB.