« Show Previous 30 Entries | Showing 31-37 of 37 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
93286 | 2018-11-22 6:43 | 2018-11-22 7:20 | MySQL Server: Command-line Clients | Verified (1981 days) | S2 | 8.0.13 | CentOS (7) | x86 | mysqldump uses deprecated option "NO_KEY_OPTIONS" in 8.0.13 with --skip-opt |
93566 | 2018-12-11 22:53 | 2018-12-12 6:52 | MySQL Server: mysqldump Command-line Client | Verified (1961 days) | S2 | 5.6.42, 5.7.24 | Debian (http://repo.mysql.com/apt/debian stretch/mysql-5.6) | x86 | mysqldump --compact omits NO_AUTO_VALUE_ON_ZERO option |
74899 | 2014-11-17 11:18 | 2020-01-18 18:30 | MySQL Server: mysqldump Command-line Client | Verified (3447 days) | S3 | all versions up to 5.7.5 | Any | Any | mysqldump should ignore prompt setting in ~/.my.cnf |
81926 | 2016-06-20 8:50 | 2020-07-27 12:17 | MySQL Server: mysqldump Command-line Client | Verified (2866 days) | S1 | 5.7.11, 5.7.13 | CentOS (6.5) | Any | mysqldump produce wrong sql on table with virtual json column as primary key |
54371 | 2010-06-09 15:32 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (5068 days) | S3 | 5.1.44, 5.1.49-bzr | Linux | Any | Privileges required to use --events option for mysqldump |
111793 | 2023-07-18 15:06 | 2023-07-19 15:45 | MySQL Server: mysqldump Command-line Client | Verified (281 days) | S2 | 8.1 | Any | Any | mysqldump memory leaks |
113400 | 2023-12-12 14:12 | 2023-12-15 13:44 | MySQL Server: mysqldump Command-line Client | Verified (132 days) | S2 | 8.0 | Any | Any | mysqldump generates incorrect sql when skipping generated invisible pk |
« Show Previous 30 Entries | Showing 31-37 of 37 (Edit, Save, CSV, Feed) |