Bug #16419 | Events: can't use timestamp in the schedule | ||
---|---|---|---|
Submitted: | 12 Jan 2006 4:11 | Modified: | 2 Feb 2006 4:41 |
Reporter: | Peter Gulutzan | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Stored Routines | Severity: | S3 (Non-critical) |
Version: | 5.1.6-alpha-debug | OS: | Linux (SUSE 10.0) |
Assigned to: | Andrey Hristov | CPU Architecture: | Any |
[12 Jan 2006 4:11]
Peter Gulutzan
[12 Jan 2006 7:55]
Aleksey Kishkin
mysql> create event e_31 on schedule at '10:55' do insert into t values (0); ERROR 1518 (HY000): Activation (AT) time is in the past mysql> select now(); +---------------------+ | now() | +---------------------+ | 2006-01-12 10:54:42 | +---------------------+ 1 row in set (0.00 sec)
[12 Jan 2006 7:59]
Aleksey Kishkin
sorry pls disregard my previuos post. (it was reply for anyther bug report :-( )
[12 Jan 2006 7:59]
Aleksey Kishkin
mysql> create event e_26 on schedule at '2007-01-01 00:00:00' do set @a = 5; ERROR 1518 (HY000): Activation (AT) time is in the past mysql> create event e_26 on schedule at '2008-01-01 00:00:00' do set @a = 5; ERROR 1518 (HY000): Activation (AT) time is in the past mysql> create event e_26 on schedule at '20070101000000' do set @a = 5; Query OK, 1 row affected (0.00 sec)
[23 Jan 2006 20:12]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/1521
[26 Jan 2006 20:23]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/1691
[26 Jan 2006 21:20]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/1696
[26 Jan 2006 21:52]
Andrey Hristov
Fixed in 5.1.6 The problem was in the interpretation of the value. Internally was casted to integer while had to be converted to internal datetime value.
[2 Feb 2006 4:41]
Mike Hillyer
Documented in 5.1.6 changelog: <listitem><para>Datatime values in timestamp format were misinterpreted in <literal>CREATE EVENT</literal> statement. (Bug #16419)</para></listitem>