| Bug #96248 | unix_timestamp function | ||
|---|---|---|---|
| Submitted: | 18 Jul 2019 12:05 | Modified: | 22 Jul 2019 12:33 |
| Reporter: | NAGSEWARARAO CH | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server | Severity: | S7 (Test Cases) |
| Version: | 8.0.15 | OS: | Linux |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | timestamp conversion | ||
[22 Jul 2019 12:33]
MySQL Verification Team
Hi Mr. CCH, Thank you for your bug report. However, what you have hit upon is not MySQL bug. The date after which UNIX timestamp does not work is the last day for which this standard is valid. We are following the standard and as soon as the committee changes the standard, we shall implement it. Not a bug.
Description: select version(); +-----------+ | version() | +-----------+ | 8.0.15 | +-----------+ 1 row in set (0.00 sec) select unix_timestamp('2038-01-19'); +------------------------------+ | unix_timestamp('2038-01-19') | +------------------------------+ | 2147452200 | +------------------------------+ 1 row in set (0.00 sec) mysql> select unix_timestamp('2038-01-20'); +------------------------------+ | unix_timestamp('2038-01-20') | +------------------------------+ | 0 | +------------------------------+ 1 row in set (0.04 sec) we are unable to convert datetime to unixtimestamp after the above mentioned day How to repeat: we are unable to convert datetime to unixtimestamp after the above mentioned day mysql> select unix_timestamp('2038-01-20'); +------------------------------+ | unix_timestamp('2038-01-20') | +------------------------------+ | 0 | +------------------------------+ 1 row in set (0.04 sec)