Showing all 147 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
118987 | 2025-09-10 14:53 | 2025-09-11 13:01 | MySQL Server: General | Verified (3 days) | S3 | Any | Any | Contribution: docs: typo unrwapped -> unwrapped | |
118984 | 2025-09-10 7:05 | 2025-09-12 14:13 | MySQL Server: InnoDB storage engine | Verified (2 days) | S3 | 9.4.0 | Any | Any | fts_optimize_read_deleted_doc_id_snapshot reads BEING_DELETED table twice |
118983 | 2025-09-10 6:59 | 2025-09-11 13:03 | MySQL Server: InnoDB storage engine | Verified (3 days) | S3 | 8.0.43 | Any | Any | PCursor::move_to_next_block is not functioning as expected |
118982 | 2025-09-10 6:55 | 2025-09-11 12:57 | MySQL Server: Optimizer | Analyzing (3 days) | S1 | 9.4.0 | Linux | Any | Unexpected result of IN operator |
118981 | 2025-09-10 3:41 | 2025-09-11 12:57 | MySQL Server: DML | Analyzing (3 days) | S3 | 8.0.41 | Any | Any | adding DEFAULT FUNCTION in the where clause, the query returns a wrong result caused by the cached value. |
118980 | 2025-09-10 2:52 | 2025-09-11 13:04 | MySQL Server: Optimizer | Verified (3 days) | S2 | MySQL8.0.41 | Any | Any | queries have different results using and without index |
118976 | 2025-09-09 12:43 | 2025-09-11 13:07 | MySQL Server: Performance Schema | Not a Bug (3 days) | S3 | 8.0.41 | Any | Any | Executing "show full columns from table" under high concurrency results in poor performance. |
118961 | 2025-09-09 3:43 | 2025-09-10 6:45 | MySQL Server: Optimizer | Not a Bug (4 days) | S3 | 8.0.41 | Any | Any | float in large value query no result |
118960 | 2025-09-09 2:57 | 2025-09-09 7:12 | MySQL Server: Optimizer | Verified (5 days) | S5 | 9.2, 8.0, 8.4 | Any | Any | Sort optimization fails as primary key info in secondary index is not considered after hint-enforced secondary index |
118957 | 2025-09-08 12:24 | 2025-09-08 15:18 | MySQL Server: Documentation | Not a Bug (6 days) | S3 | 8.0.35 | Any | Any | Documentation says you can use a HEX value for ALTER user passwords, but you can't. |
118949 | 2025-09-05 13:57 | 2025-09-10 0:42 | MySQL Server: Optimizer | Verified (6 days) | S2 | 9.2.0 | Linux (ubuntu 20.04) | Any | MySQL 9.2.0: Complex CASE in JOIN makes INNER vs INTERSECT yield different rows |
118941 | 2025-09-05 8:19 | 2025-09-10 14:45 | MySQL Server: Optimizer | Verified (4 days) | S2 | 8.0.x, 8.4.x | Any | Any | Bug Report: DECIMAL(22,2) Column Comparison with -0.001 Excludes 0.00 Row |
118937 | 2025-09-04 4:36 | 2025-09-10 0:43 | MySQL Server: Optimizer | Verified (5 days) | S2 | 9.4.0 | Any | Any | LEFT JOIN with constant functions returns incorrect results when condition is ON FALSE |
118927 | 2025-09-02 21:41 | 2025-09-03 10:12 | MySQL Server: Parser | Need Feedback (11 days) | S3 | 9.4 | Any | ARM (arm64) | Incorrect Binary Library Hex Representation Due to Sign Extension in SHOW CREATE LIBRARY |
118923 | 2025-09-02 7:49 | 2025-09-04 11:46 | MySQL Server: InnoDB storage engine | Verified (11 days) | S2 | 8.4, 8.0.22, 9.4.0 | Any | Any | Abnormal read phenomena are observed under MySQL's Read Committed isolation level |
118918 | 2025-09-01 7:30 | 2025-09-04 11:47 | MySQL Server: Optimizer | Verified (11 days) | S2 | 9.4.0 | Any | Any | Inconsistent NULL handling in CTE LEFT JOIN results |
118916 | 2025-08-31 18:26 | 2025-09-05 8:21 | MySQL Server: Optimizer | Duplicate (9 days) | S2 | 9.4.0 | Any | Any | Incorrect result set when querying view with LEFT JOIN, COALESCE and EXISTS subquery |
118913 | 2025-08-29 3:40 | 2025-09-01 10:19 | MySQL Server: Optimizer | Verified (13 days) | S2 | 8.0.41, 9.4.0 | Any | Any | queries have different results for non primary key table and table with primary key |
118912 | 2025-08-28 16:24 | 2025-09-04 11:48 | MySQL Server: Optimizer | Verified (13 days) | S1 | 8 and above, 8.0.42, 8.4.5, 9.3.0 | Any | Any | Mismatch in Column values with SUM of IFNULL vs IFNULL of SUM |
118909 | 2025-08-28 11:04 | 2025-09-04 11:49 | MySQL Server: Optimizer | Verified (11 days) | S3 | 8.0.41, 9.4.0 | Linux | x86 | Inconsistent evaluation of WHERE predicate between table-scan and covering-index paths; result set changes with projecti |
118905 | 2025-08-28 6:47 | 2025-08-28 10:44 | MySQL Server: Optimizer | Not a Bug (17 days) | S3 | 8.0.41 | Linux | x86 | Inconsistent evaluation of WHERE predicate between table-scan and covering-index paths; result set changes with projecti |
118904 | 2025-08-28 3:20 | 2025-09-04 11:46 | MySQL Server: Optimizer | Verified (13 days) | S2 | 8.0.41+ | Any | Any | Incorrect results could be returned when using index condition pushdown and Range checked for each record |
118903 | 2025-08-28 2:20 | 2025-09-01 9:10 | MySQL Server: Optimizer | Need Feedback (13 days) | S3 | Any | Any | Incorrect results could be returned when using index condition pushdown | |
118902 | 2025-08-27 14:16 | 2025-08-28 2:25 | MySQL Server: InnoDB storage engine | Closed (17 days) | S5 | 8.0.42 | Any | Any | no need to set rec_new_set_instant in row_upd_rec_in_place |
118893 | 2025-08-26 8:31 | 2025-09-04 11:53 | MySQL Server: Optimizer | Verified (13 days) | S3 | 9.4.0-1.el9 | Linux | Any | "SELECT AUTO_INCREMENT FROM information_schema.TABLES" reports a value that is reduced by one |
118890 | 2025-08-25 12:32 | 2025-09-04 11:52 | MySQL Server: Documentation | Verified (13 days) | S3 | 8.0, 8.4, 9.2 | Any | Any | wrong supported ranges in the manual |
118888 | 2025-08-25 7:19 | 2025-08-29 11:13 | MySQL Server: DDL | Verified (20 days) | S2 | 8.0.43/8.4.6 | Any | Any | DDL operation fills the entire disk space and eventually fails |
118887 | 2025-08-25 2:49 | 2025-08-29 11:06 | MySQL Server: Optimizer | Verified (20 days) | S3 | 9.4.0 | CentOS | Any | Zero '0000-00-00 00:00:00' datetime returned when SQL_BUFFER_RESULT is used |
118876 | 2025-08-21 13:22 | 2025-08-25 12:00 | MySQL Server: Documentation | Verified (24 days) | S3 | 9.4 | Any | Any | Contribution: docs: update protocol description |
118875 | 2025-08-21 12:42 | 2025-08-21 13:16 | MySQL Server: DML | Verified (24 days) | S3 | 8.0.41, 8.0.43 | Any | Any | set optimizer_switch='block_nested_loop=off/on', result is different. |
118872 | 2025-08-21 5:01 | 2025-08-21 6:31 | MySQL Server: InnoDB storage engine | Verified (24 days) | S3 | 8.0.40 | Any | Any | Innodb_data_written lacks statistics for double-write files |
118871 | 2025-08-21 2:37 | 2025-08-29 11:12 | MySQL Server: Optimizer | Verified (20 days) | S3 | 8.0.43 MySQL Community Server - GPL | Linux (Linux (Rocky Linux release 8.8 (Green Obsidian))) | Any | Constant conditions in SQL with derived views are not passed.new |
118870 | 2025-08-21 2:22 | 2025-08-21 2:33 | MySQL Server: Optimizer | Closed (24 days) | S3 | 8.0.43 MySQL Community Server - GPL | Linux (Rocky Linux release 8.8 (Green Obsidian)) | Any | Constant conditions in SQL with derived views are not passed. |
118867 | 2025-08-20 18:35 | 2025-09-01 11:12 | MySQL Server: InnoDB storage engine | Verified (24 days) | S3 | 9.4 | Any | Any | Contribution: Optimize NUMA Scheduling |
118866 | 2025-08-20 18:17 | 2025-08-21 6:22 | MySQL Server: InnoDB storage engine | Verified (24 days) | S3 | 9.4 | Any | Any | Contribution: Optimize hash_table_locks |
118865 | 2025-08-20 18:17 | 2025-08-21 6:21 | MySQL Server: Performance Schema | Verified (24 days) | S3 | 9.4 | Any | Any | Contribution: Optimize process of thread counter |
118864 | 2025-08-20 18:17 | 2025-08-21 6:20 | MySQL Server: InnoDB storage engine | Verified (24 days) | S3 | 9.4 | Any | Any | Contribution: Optimize undo spaces lock |
118863 | 2025-08-20 14:23 | 2025-08-21 6:30 | MySQL Server: Optimizer | Verified (24 days) | S2 | 8.4.x, 8.4.6 | Any | Any | Complex collection query incorrectly missing '0' |
118862 | 2025-08-20 14:05 | 2025-08-21 6:28 | MySQL Server: Optimizer | Verified (24 days) | S3 | 8.0.x, 8.4.x, 8.0.43 | Any | Any | MySQL Returns Incorrect Results for Complex Query with Set Operations |
118858 | 2025-08-20 8:51 | 2025-08-20 10:19 | MySQL Server: Optimizer | Verified (25 days) | S3 | 9.2.0 | Linux | Any | Inconsistency between the results returned by MySQL and other vendors' database systems was found during differentiation |
118857 | 2025-08-20 8:39 | 2025-08-20 10:19 | MySQL Server: Optimizer | Verified (25 days) | S2 | 9.2.0 | Linux | Any | Bug Summary: MySQL Returns Incorrect Results for Complex Query with Set Operations |
118853 | 2025-08-19 9:58 | 2025-08-19 11:32 | MySQL Server: Documentation | Closed (26 days) | S3 | 8.0.43, 8.4.5, 9.4.0 | Any | Any | Wrong description for TEXT datatype (and its variants) maximum length in the refman. |
118849 | 2025-08-18 12:14 | 2025-08-18 23:50 | MySQL Server: Optimizer | Verified (27 days) | S3 | 8.0.41 | Any | Any | after add HINT:JOIN_ORDER, the result is wrong. |
118848 | 2025-08-15 21:07 | 2025-08-18 8:55 | MySQL Server: Errors | Need Feedback (27 days) | S3 | 8.0.43 | Windows (Microsoft Windows 11 Home) | Any | My screen is black when i try to open an EER diagram |
118846 | 2025-08-15 8:50 | 2025-08-19 7:34 | MySQL Server: Optimizer | Verified (26 days) | S3 | 9.3.0 | Ubuntu | Any | column name change cased by where |
118845 | 2025-08-15 7:32 | 2025-08-18 9:41 | MySQL Server: DML | Not a Bug (27 days) | S3 | 8.0.41 | Any | Any | After a prepare stmt is declared, switch to a new database and run the stmt,the result is still result in the last DB. |
118844 | 2025-08-14 23:06 | 2025-08-16 5:57 | MySQL Server: Information schema | Verified (29 days) | S3 | 9.4.0 | Any | Any | In MySQL 9.4.0, Reserved is set 0 in information schema for one of the new keyword out of 2 |
118842 | 2025-08-14 8:50 | 2025-09-11 2:28 | MySQL Server: InnoDB storage engine | Verified (3 days) | S1 | 8.4.6 | Red Hat (9.4) | x86 | Transactions get stuck in stage/sql/waiting for handler commit until mysqld restart (MySQL 8.4.3), heavy concurrent DML |
118840 | 2025-08-14 3:33 | 2025-08-19 7:49 | MySQL Server: DML | Not a Bug (26 days) | S3 | 8.0.41 | Any | Any | a query including where (NOT XX NOT IN ()) returns a wrong nonempty result while (NOT XX NOT IN ()) returns 0. |
118839 | 2025-08-14 3:13 | 2025-08-18 23:50 | MySQL Server: DML | Verified (27 days) | S3 | 8.0.41 | Any | Any | a query including the having subclause that returns NULL, return a wrong nonempty result. |
118838 | 2025-08-14 3:10 | 2025-08-18 15:21 | MySQL Server: DML | Closed (27 days) | S3 | 8.0.41 | Any | Any | A query containing a where subclause returnning true, the query result is empty. |
118837 | 2025-08-14 3:05 | 2025-08-18 23:51 | MySQL Server: Optimizer | Verified (27 days) | S3 | 8.0.41 | Any | Any | After having(col) in the query statement is changed to having min(col), the returned result is incorrect. |
118836 | 2025-08-14 3:01 | 2025-08-18 23:56 | MySQL Server: Optimizer | Verified (27 days) | S3 | 8.0.41 | Any | Any | adding a having clause that return 1/TRUE, the query returns a different and wrong empty result. |
118835 | 2025-08-14 2:56 | 2025-08-19 0:17 | MySQL Server: Optimizer | Verified (26 days) | S3 | 8.0.41 | Any | Any | A query statement that returns 0/FALSE in the having clause, the returned result is not null. |
118834 | 2025-08-14 2:54 | 2025-08-19 0:16 | MySQL Server: DML | Closed (26 days) | S3 | 8.0.41 | Any | Any | Change a number in the query statement to -(-NUMBER), the query return different results. |
118833 | 2025-08-14 2:43 | 2025-08-19 0:36 | MySQL Server: Optimizer | Verified (26 days) | S3 | 8.0.41 | Any | Any | Two queries that use the where clause with opposite semantics return the same result. |
118832 | 2025-08-14 2:39 | 2025-08-19 7:34 | MySQL Server: Optimizer | Verified (26 days) | S3 | 8.0.41, 9.4.0 | Any | Any | using the return value replacing the IFNUILL function , the query returns different value; |
118831 | 2025-08-14 2:33 | 2025-08-19 10:51 | MySQL Server: Optimizer | Verified (26 days) | S3 | 8.0.41, 9.4.0 | Any | Any | !(expression1 or expression2) return a different result from !(expression1), while expression2 is 0. |
118830 | 2025-08-14 2:26 | 2025-08-19 10:51 | MySQL Server: DML | Verified (26 days) | S3 | 8.0.41, 9.4.0 | Any | Any | After a constant value is replaced by a LEAST function returnning the same value, the sql returns different result; |
118820 | 2025-08-13 7:39 | 2025-08-20 6:01 | MySQL Server: InnoDB storage engine | Verified (26 days) | S2 | 8.0.41 | Any | Any | AHI results the mysqld hung and assertion failure: btr0sea.cc:295:sleep_counter < 60000 |
118819 | 2025-08-13 5:53 | 2025-08-13 21:29 | MySQL Server: Command-line Clients | Verified (32 days) | S2 | 9.4.0 | Any | Any | Vertical (\G) doesn't work in MySQL 9.4.0 |
118818 | 2025-08-13 3:44 | 2025-08-18 12:16 | MySQL Server: InnoDB storage engine | Verified (27 days) | S2 | 8.0.41, 8.0.43 | Any | Any | Assertion failure row0pread.h:306:active >= n_threads happens when create thread fail for parallel scan |
118817 | 2025-08-12 11:35 | 2025-08-13 7:23 | MySQL Server: DDL | Verified (32 days) | S3 | 8.0 | Any | Any | Code Comment Error for row_import::m_n_instant_cols in storage/innobase/row/row0import.cc |
118814 | 2025-08-12 3:47 | 2025-09-11 13:08 | MySQL Server: Windows | Not a Bug (3 days) | S2 | 8.0.39 | Windows | Any | I/O error while writing to file: .\#ib_16384_0.dblwr |
118813 | 2025-08-12 3:20 | 2025-08-21 12:49 | MySQL Server: DML | Not a Bug (24 days) | S3 | 8.0.41, 8.0.43, 8.4.6 | Any | Any | utf8mb4_0900_ai_ci check different string mark as duplicate |
118811 | 2025-08-11 3:31 | 2025-08-11 12:02 | MySQL Server: Optimizer | Verified (34 days) | S3 | 8.0.43 | Linux | x86 | When hints are added, different execution plans are used for query. The query result are different. |
118810 | 2025-08-11 3:19 | 2025-08-11 10:35 | MySQL Server: Optimizer | Verified (34 days) | S3 | 8.0.41, 8.0.43, 8.4.6 | Linux | x86 | he query result are inconsistent,when select difference indexes |
118808 | 2025-08-10 11:26 | 2025-08-11 7:00 | MySQL Server: Optimizer | Verified (34 days) | S2 | 9.4.0, 8.4.3, 8.4.6 | Any | Any | Different result with range scan and table scan in sql with subquery |
118806 | 2025-08-09 13:00 | 2025-08-11 5:39 | MySQL Server: Optimizer | Verified (34 days) | S3 | 8.0,9.0, 8.0.43, 8.4.6, 9.4.0 | Ubuntu | x86 | NULLIF with VARCHAR omits rows unexpectedly |
118798 | 2025-08-07 9:22 | 2025-08-08 7:36 | MySQL Server: Replication | Verified (37 days) | S1 | 8.0.40 | Ubuntu | Any | Replication Break in 8.0.40 salve when from 8.0.33 Master |
118797 | 2025-08-07 2:08 | 2025-08-07 9:17 | MySQL Server: Replication | Verified (38 days) | S2 | 8.4, 8.4.6, 9.4.0 | Any | Any | Contribution by Tencent: previous gtids may loss xa commit/rollback gtids |
118788 | 2025-08-06 9:33 | 2025-08-21 8:59 | MySQL Server: Optimizer | Verified (39 days) | S3 | 8.0.41, 8.0.43 | Linux | x86 | When two tables are joined, the execution results are different in different join order. |
118785 | 2025-08-06 5:55 | 2025-08-06 14:31 | MySQL Server: Documentation | Closed (39 days) | S3 | 8.4 | Any | Any | Did 8.4.6 and 8.4.7 get released simultaneously on 2025.7.22? |
118766 | 2025-08-01 9:11 | 2025-08-18 14:18 | MySQL Server: Documentation | Closed (27 days) | S3 | 8.0 | Any | Any | default row_format should be DYNAMIC |
118765 | 2025-08-01 2:56 | 2025-08-01 5:26 | MySQL Server: DML | Verified (44 days) | S3 | 8.0, 9.0, 8.4.6, 8.0.43 | Any | Any | Substring_index with negative index returns inconsistent results across different character sets |
118755 | 2025-07-31 2:04 | 2025-08-21 12:32 | MySQL Server: DML | Not a Bug (24 days) | S3 | 8.0.36, 8.0.43, 8.4.6 | Windows | Any | Incorrect lowercasing of word-final Greek capital Sigma (Σ) |
118750 | 2025-07-30 3:33 | 2025-07-30 5:51 | MySQL Server: Prepared statements | Analyzing (46 days) | S3 | 9.3.0 | Any | Any | binary comparison has different results in prepared statement and normal SELECT query |
118749 | 2025-07-30 2:41 | 2025-07-30 11:57 | MySQL Server: Optimizer | Duplicate (46 days) | S3 | 9.3.0 | Any | Any | internal_tmp_mem_storage_engine=memory make the query generate different result on -0 and 0 |
118729 | 2025-07-28 13:17 | 2025-07-29 6:37 | MySQL Server: Optimizer | Verified (47 days) | S3 | 8.4.4 (Any), 8.0.43, 8.4.6, 9.4.0 | Any | Any | Select Query is showing wrong column name alias from sub-query |
118724 | 2025-07-26 12:08 | 2025-08-11 12:06 | MySQL Server: Performance Schema | Verified (34 days) | S5 | 8.0.42 | Any | Any | optimzie for performance_schema |
118723 | 2025-07-26 11:54 | 2025-07-28 4:29 | MySQL Server: InnoDB storage engine | Verified (48 days) | S5 | 8.0.42 | Any | Any | optimize for innodb insert |
118721 | 2025-07-26 9:40 | 2025-07-27 10:44 | MySQL Server: Documentation | Not a Bug (49 days) | S3 | 8.0, 8.4, 9.x | Any | Any | Improve documentation for CREATE / ALTER USER syntax related to comments and user_attributes |
118710 | 2025-07-23 12:08 | 2025-07-23 12:42 | MySQL Server: Optimizer | Verified (53 days) | S1 | 8.0.36, 8.0.42, 8.0.43, 8.4.6 | Windows | Any | Optimizer incorrectly simplifies negative float/decimal comparison in JOIN condition, leading to wrong results |
118705 | 2025-07-23 8:06 | 2025-08-13 11:06 | MySQL Server: InnoDB storage engine | Verified (51 days) | S2 | 8.0 | Any | Any | when call que_eval_sql, may crash. |
118700 | 2025-07-22 12:55 | 2025-08-25 1:00 | MySQL Server: Replication | No Feedback (21 days) | S2 | 8.0.40 | Any | Any | Due to the master enabling the NO_BACKSLASH_ESCAPES sql_mode, an error occurs during replay on the slave. |
118695 | 2025-07-22 7:11 | 2025-07-23 7:33 | MySQL Server: InnoDB storage engine | Verified (53 days) | S3 | 8.0 | Any | Any | This if condition seems to be useless in btr0cur.cc:1398 |
118694 | 2025-07-22 7:03 | 2025-07-22 11:45 | MySQL Server: DML | Verified (54 days) | S3 | 8.0.41 5.7, 8.0.42 | Any | Any | Item_func_between deal with decimel different from other methods |
118693 | 2025-07-22 5:52 | 2025-07-22 6:34 | MySQL Server: InnoDB storage engine | Verified (54 days) | S3 | 8.0.42 | Any | Any | Increasing length of varchar field should be inplace. |
118689 | 2025-07-21 11:33 | 2025-08-04 9:43 | MySQL Server: Optimizer | Not a Bug (41 days) | S2 | 9.2.0, 8.0.42, 8.4.5, 9.3.0 | Linux | Any | Inconsistent data returns when using INTERESECT operator |
118684 | 2025-07-18 14:54 | 2025-07-21 6:07 | MySQL Server: Optimizer | Verified (55 days) | S2 | 9.2.0, 8.0.42, 8.4.5 | Linux | Any | Inconsistent rows are returned |
118682 | 2025-07-18 3:52 | 2025-07-24 6:33 | MySQL Server: Options | Verified (52 days) | S2 | 8.0, 8.0.42 | Any | Any | connection_memory_limit and global_connection_memory_limit don't work |
118681 | 2025-07-18 2:54 | 2025-07-18 5:22 | MySQL Server: InnoDB storage engine | Verified (58 days) | S5 | 8.0.42 | Any | Any | Reduce the locking scope of dict_sys_mutex in dict_stats_drop_table |
118672 | 2025-07-16 9:31 | 2025-08-22 1:00 | MySQL Server: DML | No Feedback (24 days) | S3 | 8.0.41 | Any | Any | do dml sql crash |
118670 | 2025-07-16 9:23 | 2025-08-22 1:00 | MySQL Server: DDL | No Feedback (24 days) | S3 | 8.0.41 | Any | Any | add partition crash |
118669 | 2025-07-16 5:22 | 2025-07-16 6:46 | MySQL Server: Optimizer | Verified (60 days) | S1 | 8 and above, 8.0.42, 8.4.5, 9.3.0 | Any | Any | Issue in applying limit on aggregated data |
118659 | 2025-07-15 7:31 | 2025-08-22 1:00 | MySQL Server: DDL | No Feedback (24 days) | S3 | 8.0.41 | Linux | Any | doing optimize table crash |
118658 | 2025-07-15 6:11 | 2025-07-15 6:16 | MySQL Server: Data Types | Verified (61 days) | S3 | 9.2.0, 8.0, 8.0.42 | Any | Any | Issue with NULL Detection for DATE-Type Columns in Derived Tables After Derived Merge |
118630 | 2025-07-10 9:05 | 2025-07-23 1:36 | MySQL Server: DML | Not a Bug (53 days) | S3 | 9.3.0 | Any | Any | INSERT IGNORE failed but insert a different value |
118627 | 2025-07-10 7:26 | 2025-07-23 13:04 | MySQL Server: DML | Not a Bug (53 days) | S3 | 8.0.41 | Any | Any | while exexuting prepare statement including 'order by ?', the sort of result set is not right |
118625 | 2025-07-10 3:04 | 2025-08-06 12:47 | MySQL Server: DDL | Duplicate (39 days) | S3 | 9.3.0 | Any | Any | index makes query generate incorrect result |
118624 | 2025-07-10 2:47 | 2025-07-10 8:15 | MySQL Server: InnoDB storage engine | Verified (66 days) | S1 | 8.3.0, 8.0.42, 8.3.0, 8.4.5, 9.3.0 | Any | Any | Wrong result when icp(push a 'like condition' into engine) |
118621 | 2025-07-09 12:39 | 2025-07-09 14:19 | MySQL Server: Optimizer | Verified (67 days) | S3 | 9.3.0, 8.0.42 | Any | Any | subquery_to_derived optimizer makes query produce incorrect result |
118611 | 2025-07-09 4:40 | 2025-07-09 8:27 | MySQL Server: DDL | Verified (67 days) | S3 | 8.4, 8.0.42 | Linux | Any | Creating an InnoDB table with a CONNECTION clause should not be allowed |
118602 | 2025-07-08 10:26 | 2025-08-19 0:07 | MySQL Server: Replication | Can't repeat (26 days) | S2 | 8.0.42 | Ubuntu (8.0.42-0ubuntu0.24.04.1) | x86 | SQL Thread cannot be stopped when last error was 1755 |
118601 | 2025-07-08 9:30 | 2025-07-09 8:47 | MySQL Server: Prepared statements | Not a Bug (67 days) | S3 | 8.0.42, 8.4.5 | Any | Any | Inconstant type between constants in prepare statement and SELECT statement |
118595 | 2025-07-07 15:16 | 2025-07-10 7:19 | MySQL Server: Prepared statements | Not a Bug (66 days) | S1 | 9.3.0 | Any | Any | NULL are transformed to false in certain expression in prepared statement |
118594 | 2025-07-07 14:16 | 2025-07-07 14:58 | MySQL Server: InnoDB storage engine | Verified (69 days) | S2 | 8.0.42 | Any | Any | In-place ALTER TABLE ... ADD FOREIGN KEY can sometimes fails with unwarranted error or even crashes |
118592 | 2025-07-07 12:12 | 2025-07-10 6:53 | MySQL Server: Prepared statements | Duplicate (66 days) | S1 | 9.3.0 | Any | Any | Unexpected result of prepared statement |
118591 | 2025-07-07 11:28 | 2025-07-10 7:11 | MySQL Server: Data Types | Duplicate (66 days) | S1 | 9.3.0 | Any | Any | empty string parse to 0 in SET statement, which is different from that in the SELECT query |
118585 | 2025-07-03 16:35 | 2025-07-04 6:42 | MySQL Server: Optimizer | Verified (72 days) | S5 | 8.0.39, 8.0.42, 8.4.5, 9.3.0 | Ubuntu (Ubuntu 20.04.2) | Any | system variable "range_alloc_block_size" arouse different execution plan |
118575 | 2025-07-02 11:06 | 2025-07-02 14:38 | MySQL Server: DML | Not a Bug (74 days) | S3 | 8.0.42 | Any | Any | Unexpected NULL Match in <=> Comparison When Subquery Returns No Rows |
118571 | 2025-07-02 7:27 | 2025-08-06 12:50 | MySQL Server: DML | Duplicate (39 days) | S3 | 8.0.41 | Any | Any | using index lookup, the query return a wrong result; |
118570 | 2025-07-02 2:29 | 2025-07-03 9:32 | MySQL Server: DML | Verified (74 days) | S5 | 8.0.42 | Linux (22.04) | x86 | Performance regression occurs with INSERT statements after c17d86b |
118560 | 2025-06-30 11:58 | 2025-06-30 13:01 | MySQL Server: DDL | Verified (76 days) | S3 | 8.0, 8.4 | Any | Any | drop full text can not instant |
118556 | 2025-06-29 19:07 | 2025-06-30 8:14 | MySQL Server: DML | Verified (76 days) | S3 | 9.3.0 | Ubuntu | x86 | Queries on tables with same data return different results |
118555 | 2025-06-29 18:55 | 2025-06-30 8:09 | MySQL Server: DML | Verified (76 days) | S3 | 9.3.0 | Ubuntu | x86 | Inconsistant results in tables containing NULL values |
118554 | 2025-06-29 18:42 | 2025-06-30 8:05 | MySQL Server: DML | Verified (76 days) | S3 | 9.3.0 | Ubuntu | x86 | Inconsistent results on same tables with different PRIMARY KEY constraint |
118553 | 2025-06-29 18:26 | 2025-06-30 8:03 | MySQL Server: DML | Verified (76 days) | S3 | 9.3.0 | Ubuntu | x86 | SELECT returns different results on tables with same data |
118552 | 2025-06-29 18:14 | 2025-06-30 8:00 | MySQL Server: DML | Verified (76 days) | S3 | 9.3.0 | Ubuntu | x86 | Inconsistant result on tables with same data but different constraints |
118551 | 2025-06-29 17:59 | 2025-06-30 7:42 | MySQL Server: DML | Verified (76 days) | S3 | 9.3.0 | Ubuntu | x86 | Inconsistant result after removing constraints on table |
118548 | 2025-06-28 7:56 | 2025-06-30 6:45 | MySQL Server: Optimizer | Verified (76 days) | S3 | 9.2.0, 9.3.0 | Linux | x86 | A potential bugs in Mysql Server |
118547 | 2025-06-27 17:26 | 2025-06-30 6:36 | MySQL Server: Information schema | Verified (76 days) | S3 | 8.0, 8.4, 8.0.42 | Any | Any | SET DEFAULT (expr) on PK column requires issuing command twice |
118544 | 2025-06-27 14:18 | 2025-06-30 6:43 | MySQL Server: Optimizer | Verified (76 days) | S3 | 9.2.0 , 9.3.0 | Linux | Any | A potential join operator bug |
118542 | 2025-06-27 8:35 | 2025-08-18 16:11 | MySQL Server: Documentation | Closed (27 days) | S3 | 8.0, 8.4 | Any | Any | The table reference in the performance_schema is incomplete |
118541 | 2025-06-27 8:31 | 2025-06-27 13:37 | MySQL Server: Optimizer | Verified (79 days) | S3 | 9.2.0 , 8.0.42 | Linux | Any | Inconsistent Results Between NATURAL JOIN and its Equivalent Form Using EXCEPT ALL with Implicit Type Casting |
118540 | 2025-06-27 7:27 | 2025-06-27 13:36 | MySQL Server: Optimizer | Verified (79 days) | S3 | 9.2.0 , 8.0.42 | Linux | Any | Inconsistent results between NATURAL JOIN and INNER JOIN simulated via LEFT JOIN, RIGHT JOIN, and EXCEPT ALL with NULL v |
118536 | 2025-06-26 17:55 | 2025-06-27 7:24 | MySQL Server: Optimizer | Analyzing (79 days) | S2 | 8.0.40, 9.3.0 | Linux (RDS, Docker) | Any (Tested on x86_64 and aarch64) | Concurrent CTE queries cause erroneous missing temporary table errors |
118535 | 2025-06-26 17:43 | 2025-06-27 19:27 | MySQL Server: FULLTEXT search | Verified (79 days) | S3 | 9.3.0, 8.4.5, 8.0.42 | Ubuntu (25.04 Server) | x86 | Arithmetic operations fail on fulltext-indexed fields inserted with DISABLE KEYS |
118529 | 2025-06-26 9:50 | 2025-06-26 12:18 | MySQL Server: Options | Verified (80 days) | S3 | 8,9 | Any | Any | 'init_connect' not re-executed after 'COM_RESET_CONNECTION' or 'COM_CHANGE_USER' |
118516 | 2025-06-24 10:42 | 2025-07-03 18:36 | MySQL Server: InnoDB storage engine | Verified (73 days) | S3 | 8.0.39 | Any | Any | Unexpected blocked statement when different select statements are executed |
118515 | 2025-06-24 9:08 | 2025-07-01 4:35 | MySQL Server: InnoDB storage engine | Verified (76 days) | S2 | 8.4, 8.4.5 | Any | Any | Contribution by Tencent: trx_cleanup_at_db_startup did not clean up trx_sys->shards |
118512 | 2025-06-24 7:52 | 2025-06-25 8:13 | MySQL Server: Optimizer | Verified (82 days) | S2 | 8.0.42, 8.4.5, 9.3.0 | Any | Any | The missing semi join condition causes incorrect result |
118510 | 2025-06-23 20:09 | 2025-07-01 12:50 | MySQL Server: FULLTEXT search | Verified (75 days) | S2 | 8.0.39 | Any | Any | InnoDB Match Against does not work properly with utf8mb4_0900_as_ci |
118499 | 2025-06-23 9:20 | 2025-06-26 1:47 | MySQL Server: Command-line Clients | Analyzing (80 days) | S2 | mysql-8.0.32 | Linux (centos7.9) | Any | .mylogin.cnf covered the command line |
118497 | 2025-06-23 1:11 | 2025-06-23 4:20 | MySQL Server: DML | Duplicate (83 days) | S3 | 8.0.41 | Any | Any | When inserting floating-point data into JSON type, the query result precision is incorrect. |
118495 | 2025-06-20 7:40 | 2025-06-20 10:32 | MySQL Server: DML | Verified (86 days) | S3 | 8.0.41 | Linux | x86 | The query returned wrong result with l"imit offset" |
118493 | 2025-06-20 6:54 | 2025-06-20 10:38 | MySQL Server: Partitions | Verified (86 days) | S3 | 8.0, 8.0.42 | Any | Any | Subpartitions can not be pruned by conditions derived from equal propagation |
118492 | 2025-06-20 3:07 | 2025-07-01 12:40 | MySQL Server: DML | Can't repeat (75 days) | S3 | 8.0.41, 8.0.42 | Linux | x86 | The result returned by the DIAMETER_TZ function is incorrect. The time after conversion is expected. |
118490 | 2025-06-19 13:00 | 2025-06-20 5:21 | MySQL Server: Optimizer | Verified (86 days) | S3 | master, 8.4 | Any | Any | hypergraph optimizer const folding caused inequivalent for join_cond_optim in Table_ref |
118486 | 2025-06-19 10:07 | 2025-07-14 12:17 | MySQL Server: Optimizer | Duplicate (62 days) | S5 | 8.4.3, 8.4.5, 9.3.0 | Any (AWS RDS) | Any | Index is ignored in case of multiple values in "select" and the length of any one value is more than column length |
118481 | 2025-06-18 20:04 | 2025-08-04 6:05 | MySQL Server: Optimizer | No Feedback (42 days) | S3 | Mysql 8.4.5 | Linux (Amazon Linux (AWS RDS managed)) | Any | MySQL 8.4.5 chooses suboptimal index for UPDATE query, leading to deadlocks and performance degradation |
118476 | 2025-06-18 8:45 | 2025-07-02 14:47 | MySQL Server: DDL | Verified (88 days) | S2 | 8.0, 8.4 | Red Hat | x86 | Unable to create partition with name '1e3fRQM2GhI' |
118475 | 2025-06-18 7:58 | 2025-06-18 8:40 | MySQL Server: DML | Verified (88 days) | S3 | 8.0.41, 8.4.5 | Any | Any | When the IF function is invoked to replace the specified column name, the returned results are inconsistent. |
118469 | 2025-06-17 9:38 | 2025-06-17 10:33 | MySQL Server: Documentation | Verified (89 days) | S3 | 9.3 | Any | Any | Connection attributes for Connector/NET are incomplete/incorrect |
118465 | 2025-06-17 7:42 | 2025-06-17 9:02 | MySQL Server: DML | Duplicate (89 days) | S3 | 8.0.41 | Any | Any | Inserting into a float value exceeding the precision, using IF function and using the column return different result. |
118464 | 2025-06-17 7:24 | 2025-06-17 9:29 | MySQL Server: DML | Analyzing (89 days) | S3 | 8.0.41 | Any | Any | Inserting into a float value exceeding the precision, using IF function and using the column return different result. |
118462 | 2025-06-17 2:56 | 2025-07-01 14:09 | MySQL Server: Replication | Can't repeat (75 days) | S3 | 8.0.39 | Red Hat (Rocky Linux 8.10) | x86 (AMD EPYC 7R32) | Executed SQL on replica is different from source |
Showing all 147 (Edit, Save, CSV, Feed) |