| Showing 1-50 of 1454 (Edit, Save, CSV, Feed) | Show Next 50 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 119270 | 2025-10-30 9:12 | 2026-04-14 8:43 | MySQL Server: Replication | Open | S3 | MySQL8.0,5.7 | Any | Any | Single-statement transactions can cause latency spikes on the replica |
| 119271 | 2025-10-30 11:14 | 2026-01-21 11:37 | Connector / J | Closed (288 days) | S3 | All | Any | Any | Connector/J fails to accept legacy value zeroDateTimeBehavior=convertToNull on multi-host URLs (failover), but works on |
| 119273 | 2025-10-30 14:14 | 2026-01-15 10:29 | MySQL Server: InnoDB storage engine | Open (364 days) | S2 | 8.4.6 | Red Hat (5.14.0-570.25.1.el9_6.x86_64) | x86 | disk-based Temptable gives "Table './tmp/#sql2730_2b2_4' doesn't exist" |
| 119275 | 2025-10-30 17:57 | 2025-10-30 17:57 | MySQL Cluster: NDB API | Open | S3 | Any | Any | Drop TCKEY_FAILCONF lead to crash | |
| 119276 | 2025-10-31 6:05 | 2026-10-01 14:48 | MySQL Server: InnoDB storage engine | Documenting (85 days) | S3 | 8.0.44 | Any | Any | ALTER TABLE ANALYZE PARTITION statement causes incorrect results in the mysql.table_table_stats |
| 119279 | 2025-10-31 10:48 | 2025-10-31 10:48 | MySQL Server: Tests | Open | S3 | 8.4.6 | Any | Any | The default value of innodb_read_io_threads uses too many system resources with mysql-test.run.pl |
| 119280 | 2025-10-31 11:55 | 2026-06-20 21:50 | MySQL Server: InnoDB storage engine | Open (153 days) | S2 | 9.5.0 | Any | Any | INSTANT ADD succeeds even when the size of a row crosses row_size_limit |
| 119281 | 2025-10-31 14:10 | 2025-12-02 1:00 | MySQL Server: Optimizer | No Feedback (332 days) | S3 | mysql:8.0.41 | Any | Any | The crash occured |
| 119284 | 2025-10-31 17:43 | 2025-10-31 20:16 | Connector / ODBC | Open (363 days) | S3 | 9.0 | Windows | Any | Unicode characters encoding problem on Connector/ODBC >= 9.0 |
| 119285 | 2025-11-01 6:16 | 2026-01-29 6:39 | MySQL Server: InnoDB storage engine | Open (273 days) | S5 | 8.0.44 | Any | Any | resue read-view for read_only mode |
| 119286 | 2025-11-01 9:57 | 2025-11-06 9:40 | MySQL Server: DML | Duplicate (359 days) | S3 | 8.0.41 | Any | Any | Query Results Incorrect Due to Indexed String Field |
| 119287 | 2025-11-01 10:08 | 2025-11-04 21:01 | MySQL Server: Optimizer | Verified (359 days) | S3 | 8.0.41 | Any | Any | Decimal Precision Mismatch in UNION Query with CONCAT Function |
| 119289 | 2025-11-02 10:48 | 2025-11-02 20:07 | MySQL Server | Not a Bug (361 days) | S3 | 8.0.41 | Any | Any | Same predicate condition, but SELECT affects different records than UPDATE and DELETE. |
| 119290 | 2025-11-02 15:06 | 2025-11-07 7:43 | MySQL Server: InnoDB storage engine | Open (356 days) | S2 | 9.3.0, 9.5.0 | Any | Any | SELECT statement is affected by concurrent transaction under Read Uncommitted |
| 119292 | 2025-11-03 6:07 | 2025-11-04 20:41 | MySQL Server | Not a Bug (359 days) | S3 | 9.4.0 | Any | Any | SIN result is not the same with SIN(x+2*PI()) |
| 119300 | 2025-11-04 10:46 | 2025-11-04 10:56 | MySQL Server: InnoDB storage engine | Open (359 days) | S3 | 8.0.44 | Any | Any | Debug assertion failure: field.field_no < dict_index_get_n_fields(index) |
| 119303 | 2025-11-05 1:49 | 2025-11-05 5:00 | MySQL Server: DML | Verified (358 days) | S3 | 8.0.41 | Any | Any | The query is normal without using the histogram, but an error occurs when using the histogram |
| 119304 | 2025-11-05 2:08 | 2026-01-15 10:31 | MySQL Server: Replication | Open (358 days) | S3 | 5.7，8.0 | Any | Any | SQL_LOAD-xxxx file exists when the SQL thread checks permissions, causing the SQL thread fail to start |
| 119305 | 2025-11-05 4:02 | 2025-12-16 13:55 | MySQL Server: Optimizer | Verified (317 days) | S3 | 8.0.41 | Linux | x86 | The query results of enabling and disabling materialization are inconsistent. |
| 119306 | 2025-11-05 7:02 | 2025-11-06 5:34 | MySQL Server: Optimizer | Verified (357 days) | S3 | 8.0, 9.5 | Any | Any | The EXPLAIN plan may be inconsistent with the actual execution. |
| 119309 | 2025-11-05 13:37 | 2026-06-03 12:37 | MySQL Server: Partitions | Verified (282 days) | S3 | 8.0.42 | Any | Any | An insert prepared statement fails to write across partitions |
| 119310 | 2025-11-05 14:54 | 2025-11-05 14:54 | MySQL Package Repos | Open | S1 | 8.4 | Ubuntu (24.04 LTS) | x86 | Version regression in repository, not newest packages in repository |
| 119311 | 2025-11-05 16:33 | 2026-09-14 18:06 | MySQL Workbench | Won't Fix | S3 | Any | Any | Contribution: remove: gnome-keyring from dependencies in .spec file | |
| 119312 | 2025-11-05 17:30 | 2026-01-13 11:33 | MySQL Server: Replication | Open | S3 | 8.4.x | Any | Any | `start replica` command adds an invalid record to mysql.slave_master_info |
| 119313 | 2025-11-06 3:03 | 2025-12-06 21:22 | MySQL Server: Optimizer | Verified (327 days) | S3 | 8.0.41 | Any | Any | BETWEEN clause returns incorrect results when comparing numeric literal with DATETIME columns |
| 119315 | 2025-11-06 8:04 | 2026-10-02 23:21 | Connector / Python | Verified (27 days) | S3 | 9.0.0~9.5.0 | Any | Any | mysql.connector.aio TypeError when connecting to MySQL without explicit SSL config (even if server requires SSL) |
| 119316 | 2025-11-06 8:51 | 2025-11-06 8:51 | Shell Dump & Load | Open | S3 | 9.5.0 | Any | x86 | mysql shell dumpInstance to s3, support use_dualstack_endpoint from config profile |
| 119318 | 2025-11-06 11:28 | 2026-09-01 23:15 | MySQL Server: Data Dictionary | Verified (128 days) | S3 | 8.4.10 | CentOS (CentOS Linux release 7.7.1908 (Core)) | x86 (x86_64) | When modifying the system time to a date beyond 2038, MySQL installation reports an error |
| 119321 | 2025-11-07 4:35 | 2026-07-10 7:51 | MySQL Server: Optimizer | Duplicate (111 days) | S3 | 9.4.0 | Any | Any | Unexpected None after changing SUM to SUM (x*2) |
| 119322 | 2025-11-07 4:58 | 2026-07-10 7:52 | MySQL Server: Optimizer | Duplicate (111 days) | S3 | 9.4.0 | Any | Any | Unexpected None after adding a window column |
| 119323 | 2025-11-07 5:59 | 2026-09-18 8:15 | MySQL Server: Optimizer | Closed (41 days) | S3 | 9.4.0 | Any | Any | row number become less after changing COUNT(DISTINCT) to COUNT |
| 119324 | 2025-11-07 6:19 | 2025-11-07 8:52 | MySQL Server | Not a Bug (356 days) | S3 | 9.4.0 | Any | Any | Inconsistent Data Type Inference in Aggregate Functions with CTE |
| 119325 | 2025-11-07 7:33 | 2025-11-07 7:33 | MySQL Server: InnoDB storage engine | Open | S2 | 9.5.0 | Any | Any | SELECT does not create a snapshot when the WHERE condition evaluates to false |
| 119326 | 2025-11-07 7:40 | 2025-11-07 9:07 | MySQL Server: Optimizer | Verified (356 days) | S3 | 8.0.41 | Any | Any | Using the COALESCE function, two opposite conditions return the same result. |
| 119327 | 2025-11-07 7:52 | 2026-07-10 7:51 | MySQL Server: Optimizer | Duplicate (111 days) | S3 | 8.0.45 | Any | Any | after adding an index ,the result return different |
| 119329 | 2025-11-07 8:13 | 2025-11-11 14:02 | MySQL Server: Optimizer | Verified (356 days) | S3 | 8.0.44 | Any | Any | Column name unexpectedly change after changing COUNT to COUNT(DISTINCT) |
| 119331 | 2025-11-07 9:44 | 2026-09-14 18:06 | MySQL Workbench: Modeling | Won't Fix | S3 | 8.0.44 | Any (MS Windows 10 Enterprise & macOS 15.6.1) | Any | Forward engineering process: Selecting Table objects to not be exported, does not work |
| 119334 | 2025-11-07 13:52 | 2026-09-14 18:06 | MySQL Workbench | Won't Fix | S3 | 8.0.43 | Windows (Microsoft Windows 10 Pro for Workstations) | Any | Query with DROP TABLE statement removes the table name from schemas, but CREATE TABLE don't restore it |
| 119335 | 2025-11-07 17:54 | 2026-09-14 18:06 | MySQL Workbench | Won't Fix | S3 | 8.0.42 | Windows (Microsoft Windows 11 Pro) | x86 (workstation) | Opened MySQL Workbench -> BugReport Suggested |
| 119336 | 2025-11-07 18:21 | 2025-11-07 18:49 | MySQL Server: Command-line Clients | Open (356 days) | S3 | 5.7 8.0 8.4 | Any | Any | extra whitespace in grant statement results in syntax error |
| 119337 | 2025-11-07 18:24 | 2026-01-21 10:13 | MySQL Package Repos | Open (316 days) | S2 | Ubuntu (25.10) | x86 (amd64) | No apt repo for Ubuntu 25.10 (code name questing) | |
| 119338 | 2025-11-08 2:34 | 2026-04-22 10:14 | Connector / NET | Closed (190 days) | S3 | Any | Any | Contribution: Apply type mapping to arguments in `StartsWith/EndsWith` tran ... | |
| 119339 | 2025-11-08 17:27 | 2025-11-11 7:31 | MySQL Server: Optimizer | Verified (352 days) | S3 | 8.0.41 | Any | Any | The results are different after extracting the value of the COALESCE function |
| 119340 | 2025-11-10 7:58 | 2026-06-08 11:35 | MySQL Server: Optimizer | Verified (143 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect result for RLIKE when INSERT() uses CURRENT_USER() as an argument. |
| 119341 | 2025-11-10 8:24 | 2025-11-11 7:56 | MySQL Server: Optimizer | Verified (352 days) | S3 | 9.4.0 | Any | Any | ALL subquery evaluates incorrectly in SELECT list when comparing against a BIT column |
| 119342 | 2025-11-10 8:26 | 2025-11-11 8:10 | MySQL Server: Optimizer | Verified (352 days) | S3 | 9.4.0 | Any | Any | Bits value change after changing UNION to UNION ALL |
| 119343 | 2025-11-10 8:40 | 2026-05-28 1:13 | MySQL Server: Optimizer | Documenting (343 days) | S3 | 8.0 | Any | Any | NOT BETWEEN evaluates incorrectlywhen FROM_UNIXTIME operates on a FLOAT column |
| 119344 | 2025-11-10 8:47 | 2025-11-12 3:04 | MySQL Server: Optimizer | Verified (351 days) | S3 | 9.4.0 | Any | Any | Floating-point precision loss happen after changing UNION to UNION ALL |
| 119345 | 2025-11-10 9:21 | 2025-11-20 11:33 | MySQL Server: Optimizer | Verified (343 days) | S3 | 8.0 | Any | Any | Presence of UNIQUE index on INT column causes inconsistent results for IF with ANY subquery |
| 119346 | 2025-11-10 9:43 | 2025-11-20 12:40 | MySQL Server: Optimizer | Verified (343 days) | S3 | 8.0 | Any | Any | CASE expression evaluates incorrectly |
| Showing 1-50 of 1454 (Edit, Save, CSV, Feed) | Show Next 50 Entries » |
