Showing all 15 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
21677 | 2006-08-16 18:48 | 2014-02-06 14:01 | MySQL Server: Data Types | Verified (3704 days) | S3 | 4.1.21, 5.0.23 | Linux (Linux) | Any | Change in results with "now() BETWEEN date_field1 AND date_field2" |
30933 | 2007-09-10 14:26 | 2014-06-29 20:45 | Connector / ODBC | Verified (3892 days) | S2 | 3.51.18 and higher | Windows (MyODBC 3.51.18) | Any | Timestamp field in View is not updated after changing data in the view. |
38457 | 2008-07-30 12:38 | 2018-09-09 20:45 | MySQL Server: Data Types | Verified | S3 | 4.1, 5.0, 5.1, etc | Any | Any | NOW() loses time information when writing to TIMESTAMP field |
41157 | 2008-12-01 19:38 | 2011-02-16 23:43 | MySQL Server: General | Verified (5596 days) | S3 | 5.1 | Any | Any | Modify PreparedStatement to include timestamp column in RETURN_GENERATED_KEYS |
41311 | 2008-12-08 21:39 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (5589 days) | S3 | 5.0.67, 5.0.72, 5.1.30 | Any | Any | set timestamp allows unprivileged users to change per-session clock |
44763 | 2009-05-09 20:07 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Patch pending (5135 days) | S3 | mysql-5.1-telco-6.3 | Any | Any | ndb_restore - timestamp data is printed in wrong format when using --print-data |
46392 | 2009-07-27 4:13 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (5359 days) | S3 | 5.0, 5.1 bzr | Any (MS Windows NT 6, Mac) | Any | mysqldump.exe drops character on its timestamp |
71035 | 2013-11-28 15:53 | 2014-10-30 8:47 | MySQL Server: Row Based Replication ( RBR ) | Verified (3772 days) | S2 | mysqlbinlog Ver 3.4, 5.1.74, 5.5.35, 5.6.16 | Linux (CentOS release 6.4 2.6.32-358.23.2.el6.x86_64) | Any | mysqlbinlog dumps out improperly-formatted TIMESTAMP values |
84704 | 2017-01-29 11:02 | 2017-01-30 8:12 | MySQL Server: Document Store: MySQL Shell | Verified (2615 days) | S2 | 1.0.5 | Any | Any | The month in the output of a timestamp in MySQL shell is offset by 1. |
88465 | 2017-11-13 16:34 | 2017-11-21 4:34 | MySQL Server: DML | Verified (2322 days) | S2 | 5.7.20 | Any | Any | JOIN is performed incorrectly on TIMESTAMP |
94550 | 2019-03-04 16:18 | 2019-03-04 18:47 | MySQL Server: DML | Verified (1852 days) | S3 | 8.0.15 | Oracle Linux (OL7) | x86 | generated columns referring to current_timestamp fail |
95797 | 2019-06-13 22:10 | 2021-03-01 7:01 | MySQL Server: DML | Verified (1747 days) | S2 | 5.7, 8, 8.0.16, 5.7.26 | Any | Any | Erratic lossy roundtrip conversion of timestamps when copying columns |
96608 | 2019-08-21 18:53 | 2020-02-06 13:38 | MySQL Server: Data Types | Verified (1514 days) | S3 | 5.7.23, 5.7.27 | Debian | Any | Mishandled timezone conversions on timestamps |
96609 | 2019-08-21 19:14 | 2020-02-06 13:36 | MySQL Server: Data Types | Verified (1681 days) | S2 | 5.7.23, 5.7.27 | Debian | Any | Corrupted timestamp data on alter |
112220 | 2023-08-30 10:27 | 2023-08-31 4:21 | Connector / J | Analyzing (211 days) | S3 | 8.0.33 | Any | Any | Create TimeStamp instance from DateTime in db for specific datetime |
Showing all 15 (Edit, Save, CSV, Feed) |