Bug #54783 optimize table crashes with invalid timestamp default value and NO_ZERO_DATE
Submitted: 24 Jun 2010 15:33 Modified: 30 Jul 2010 2:46
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: DDL Severity:S1 (Critical)
Version:5.5.5 OS:Any
Assigned to: Davi Arnaut CPU Architecture:Any
Tags: NO_ZERO_DATE, regression, SQL_MODE, valgrind

Contributions can be accepted to Open bugs only.