Bug #22117 Extra Slave Col: CURRENT_TIMESTAMP not allowed for a DEFAULT value
Submitted: 8 Sep 2006 12:42 Modified: 8 Sep 2006 16:55
Reporter: Jonathan Miller Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server: Row Based Replication ( RBR ) Severity:S3 (Non-critical)
Version:5.1.12-new-rpl OS:Linux (Linux 32 Bit OS)
Assigned to: Mats Kindahl CPU Architecture:Any

[8 Sep 2006 12:42] Jonathan Miller
I have been trying to use CURRENT_TIMESTAMP for a DEFAULT value on a slave table and keep getting:

060907 23:32:56 [ERROR] Slave: Field `d` of table `test`.`t1` has no default value and cannot be NULL, Error_code: 1364
060907 23:32:56 [ERROR] Slave: Error in Write_rows event: error during transaction exec ution on table test.t1, Error_code: 1364

but our manual states:

For one TIMESTAMP column in a table, you can assign the current timestamp as the default value and the auto-update value. It is possible to have the current timestamp be the default value for initializing the column, for the auto-update value


How to repeat:
See Above

Suggested fix:
[8 Sep 2006 16:55] Jonathan Miller
Was adding it back into the test today so Mats would have it, but I can not get it to fail again. Closing out the bug for now.