Bug #22594 | Crash on select using timestamp and between | ||
---|---|---|---|
Submitted: | 22 Sep 2006 15:18 | Modified: | 22 Sep 2006 19:03 |
Reporter: | Ron Mercer | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 4.1.21 | OS: | Windows (Windows Server 2003) |
Assigned to: | CPU Architecture: | Any | |
Tags: | between, crash, SELECT, timestamp |
[22 Sep 2006 15:18]
Ron Mercer
[22 Sep 2006 19:03]
MySQL Verification Team
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at http://dev.mysql.com/doc/en/installing-source.html F:\mysql\bin>mysql -uroot test Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2 to server version: 4.1.22 Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> select * from crash_table where time_stamp+0 between date_sub(now()+0,interval 3 -> month) and now(); Empty set, 1 warning (0.00 sec) mysql> show warnings; +---------+------+-------------------------------------------------------------+ | Level | Code | Message | +---------+------+-------------------------------------------------------------+ | Warning | 1292 | Truncated incorrect datetime value: '20060922155510.000000' | +---------+------+-------------------------------------------------------------+ 1 row in set (0.00 sec) mysql>