Bug #24443 | second timestamp column has an invalid default value | ||
---|---|---|---|
Submitted: | 20 Nov 2006 18:07 | Modified: | 4 Feb 2008 14:40 |
Reporter: | Brian Duggan | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: DDL | Severity: | S3 (Non-critical) |
Version: | 5.0.54, 5.0.32-BK, 5.0.26 | OS: | Linux (linux) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[20 Nov 2006 18:07]
Brian Duggan
[21 Nov 2006 17:28]
Valeriy Kravchuk
Thank you for a bug report. Verified just as described with 5.0.32-BK on Linux: mysql> set sql_mode='STRICT_TRANS_TABLES,STRICT_ALL_TABLES,NO_ZERO_IN_DATE,NO_Z ERO_DATE'; Query OK, 0 rows affected (0.01 sec) mysql> drop table foo2; Query OK, 0 rows affected (0.01 sec) mysql> create table foo2 (aaa timestamp, bbb timestamp, ccc int); Query OK, 0 rows affected (0.01 sec) mysql> alter table foo2 modify ccc int(12); ERROR 1067 (42000): Invalid default value for 'bbb' NO_ZERO_DATE mode leads to this result.
[4 Feb 2008 14:40]
Alexander Nozdrin
This is a duplicate of Bug#18834.