Bug #18074 SHOW CREATE EVENTS fails for dates far away
Submitted: 8 Mar 2006 15:24 Modified: 8 Mar 2006 15:26
Reporter: Chad MILLER Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Stored Routines Severity:S3 (Non-critical)
Version:5.1.7 OS:MacOS (OSX)
Assigned to: CPU Architecture:Any

[8 Mar 2006 15:24] Chad MILLER 
Description:
In writing the tests for dumping and restoring events via mysqldump+mysql client, I wanted descriptions that were deterministic, so I had to choose a date far in the future (since past events are invalid), so that the test wouldn't start failing within my lifetime.

I checked the manual, which says that it requires a timestamp, which is defined elsewhere so that any year from 1000CE to 9999CE is valid.  

But, it seems the events are constrained to Unix-epoch 32-bit second-count numbers, as dates outside that range seem to come out as 1 Jan 1970.

How to repeat:
create event ee on schedule at '9999-01-01 01:23:45' do set @a=5;
show create event ee;
[8 Mar 2006 15:26] Chad MILLER 
Nevermind.  Dup of #16396.