Showing all 21 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
29797 | 2007-07-13 20:45 | 2007-07-14 2:56 | Connector / J | Won't fix (6102 days) | S3 | 5.1 | Linux | Any | Statement objects not being closed when garbage collected / memory leak |
39968 | 2008-10-10 3:03 | 2008-10-31 9:09 | MySQL Server: Replication | Can't repeat (5627 days) | S2 | 5.1.28-rc | FreeBSD (7.1) | Any | Single chars get corrupted in SQL queries during replication to slave |
48815 | 2009-11-16 19:54 | 2010-01-14 13:11 | MySQL Server: Row Based Replication ( RBR ) | Not a Bug (5187 days) | S2 | 5.1-rep+3 | Any | Any | Slave stops with error code 1644 but row event executed by SQL thread |
42851 | 2009-02-13 22:27 | 2017-05-21 20:45 | MySQL Server: Replication | Duplicate (5229 days) | S3 | 5.1.31 | Linux (Fedora Core 9) | Any | Spurious "Statement is not safe to log in statement format." warnings |
48635 | 2009-11-09 11:53 | 2009-11-09 18:28 | MySQL Server: Replication | Not a Bug (5253 days) | S2 | mysql-5.0.70-r1 | Linux (Gentoo) | Any | Replication doesn't divide accurate when using "Replicate_Do_DB" |
53560 | 2010-05-11 11:52 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (4914 days) | S3 | 5.1.44 | Any | Any | CREATE TEMP./DROP TEMP. are not binlogged correctly after a failed statement |
53721 | 2010-05-17 23:54 | 2012-01-18 1:00 | MySQL Server: Prepared statements | No Feedback (4454 days) | S1 | 5.1.45-Community | Windows | Any | Server crash |
51426 | 2010-02-23 15:57 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (4985 days) | S3 | 5.1.44,5.5.99-m3 | Any | Any | User var unsigned_flag value not preserved until binlog time |
54527 | 2010-06-15 19:40 | 2011-02-16 23:44 | MySQL Workbench | Duplicate (5035 days) | S1 | 5.2.22 | MacOS | Any | Workbench Crashes Everytime a SQL statement is executed |
61898 | 2011-07-18 15:30 | 2011-12-30 7:00 | MySQL Server: Replication | No Feedback (4473 days) | S2 | 5.1.57 | Linux | Any | Error 1535 after on online schema change with switch to 'statement' repl.on runt |
80432 | 2016-02-18 15:58 | 2016-03-16 6:15 | MySQL Server: FULLTEXT search | Won't fix (2934 days) | S1 | 5.7.10 | Windows (InnoDB, utf8mb4_unicode_ci) | Any | No results in fulltext search for top level domain in domain part of email |
81316 | 2016-05-04 20:39 | 2016-05-05 7:24 | MySQL Server: Optimizer | Closed (2884 days) | S1 | 5.7.10,5.7.12 | CentOS (CentOS release 6.7 (Final)) | Any | Optimizer broke for large in clauses |
84185 | 2016-12-13 14:07 | 2016-12-14 7:20 | MySQL Server: Replication | Verified (2661 days) | S3 | 5.6, 5.7.17, 8.0.0, 5.6.35 | Any | Any | Not all "Statements writing to a table with an auto-increment..." are unsafe |
86897 | 2017-07-02 13:15 | 2017-07-02 18:26 | MySQL Workbench: SQL Editor | Duplicate (2461 days) | S3 | 6.3.6 | Windows (Microsoft Windows 10 Home) | Any | invalid literal for int() with base 10 |
87250 | 2017-07-30 9:43 | 2017-07-31 10:20 | MySQL Workbench | Verified (2432 days) | S3 | 6.3.9 | Windows (Microsoft Windows 10 Home) | Any | Client Connections: SQL is being truncated when clicking on "Show in Editor" |
87624 | 2017-08-31 11:04 | 2017-09-01 12:08 | MySQL Server: Replication | Verified (2400 days) | S2 | 5.6, 8.0.2, any?, 5.6.37 | Any | Any | Wrong statement-based binary logging for CONCAT() in stored procedure |
73056 | 2014-06-19 21:34 | 2018-03-15 14:17 | MySQL Server: Prepared statements | Closed (2939 days) | S5 | 5.7, 5.7.8 | Any | Any | Prepared Statements ABSURDLY SLOW due to inefficient query creation for logging |
91299 | 2018-06-18 12:09 | 2018-06-18 16:56 | Connector / J | Can't repeat (2110 days) | S3 | Windows | x86 | createStatement() method gaves me a NullPointerException | |
85155 | 2017-02-23 16:25 | 2021-01-20 18:14 | MySQL Server: Command-line Clients | Closed (2078 days) | S5 | 5.7.17 | CentOS | Any | Importing huge statement seems to cause memory problems |
96774 | 2019-09-06 7:42 | 2019-09-06 13:28 | MySQL Server: Performance Schema | Can't repeat (1665 days) | S3 | 5.6.23,5.7.21 | CentOS | Any | The timer_start in performance_schema is much smaller than mysql' uptime |
101127 | 2020-10-12 9:59 | 2020-10-13 8:38 | MySQL Server: Documentation | Not a Bug (1262 days) | S3 | 5.7/8.0 | Any (n.a.) | Any (n.a.) | Docu bug in CASE Statement |
Showing all 21 (Edit, Save, CSV, Feed) |