| Bug #16434 | Events: Illegal dates don't cause errors | ||
|---|---|---|---|
| Submitted: | 12 Jan 2006 4:33 | Modified: | 2 Feb 2006 5:07 |
| 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:33]
Peter Gulutzan
[18 Jan 2006 18:46]
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/1285
[23 Jan 2006 11:26]
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/1489
[23 Jan 2006 11:31]
Andrey Hristov
Go back to patch pending because the new patch is a bit changed
[26 Jan 2006 21:03]
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/1694
[27 Jan 2006 0:20]
Andrey Hristov
The date for STARTS/ENDS wasn't handled correctly - not converted internaly to datetime but to int. Fixed in 5.1.6 .
[2 Feb 2006 5:07]
Mike Hillyer
Documented in 5.1.6 changelog.
