« Show Previous 30 Entries | Showing 31-60 of 64 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
44397 | 2009-04-22 2:46 | 2012-05-18 20:19 | MySQL Server: FULLTEXT search | Verified (5476 days) | S2 | 5.0.79, 5.1.33, 5.1.34, 6.0.9 | Any | Any | Negative relevancy value for boolean fulltext query using a left join |
50969 | 2010-02-07 10:09 | 2013-03-03 20:45 | MySQL Server: FULLTEXT search | Verified (5185 days) | S3 | Any | Any | FT min/max has to be overridable per-use (current impl. assumes text is western) | |
57354 | 2010-10-10 19:52 | 2013-03-03 20:45 | MySQL Server: FULLTEXT search | Verified (4863 days) | S5 | 5.1.41, 5.1.55 | Any (CentOS and Win7 tested) | Any | Using "=" operator with FULL-TEXT search decrease the speed |
60904 | 2011-04-18 8:10 | 2011-07-17 13:14 | MySQL Server: FULLTEXT search | Verified (4660 days) | S1 | 5.1.49, 5.1.59 | Any | Any | plugin of full text index has a string address error |
75763 | 2015-02-04 13:29 | 2015-02-05 8:19 | MySQL Server: FULLTEXT search | Verified (3361 days) | S2 | 5.6.21, 5.6.24 | Any | Any | InnoDB FULLTEXT index reduces insert performance by up to 6x on JSON docs |
76210 | 2015-03-07 21:58 | 2015-03-09 9:07 | MySQL Server: FULLTEXT search | Verified (3329 days) | S2 | 5.6.22, 5.6.25, 5.7.7 | Any | Any | InnoDB FULLTEXT index returns wrong results for key/value pair documents |
77054 | 2015-05-16 3:23 | 2016-03-14 4:19 | MySQL Server: FULLTEXT search | Verified (3060 days) | S3 | 5.6.24, 5.6.29, 5.7.11 | Any | Any | Fulltext search with wildcard and words with apostrophe (‘) works incorrectly |
78092 | 2015-08-16 14:07 | 2015-08-16 14:09 | MySQL Server: FULLTEXT search | Verified | S3 | 5.6.26 | Any | Any | fts lexer spams error log with " and % characters |
80723 | 2016-03-14 8:40 | 2022-11-03 12:29 | MySQL Server: FULLTEXT search | Verified (2934 days) | S3 | 5.6.23, 5.6.29, 5.7.11 | Any | Any | @ Distance operator does not bring expected results when used in with wildcards |
81930 | 2016-06-20 10:54 | 2016-06-20 11:35 | MySQL Server: FULLTEXT search | Verified (2860 days) | S3 | 5.6, 5.7, 5.6.31 | Any | Any | incorrect result with InnoDB FTS and subquery |
79639 | 2015-12-14 17:06 | 2015-12-15 8:19 | MySQL Server: FULLTEXT search | Verified (3048 days) | S3 | Any | Any | Add parser which indexes words in Unicode NFC normalized form. (contribution) | |
80347 | 2016-02-12 5:02 | 2016-11-08 13:39 | MySQL Server: FULLTEXT search | Verified (2719 days) | S2 | 5.7.9, 5.7.11 | Any | Any | mysqldump backup restore fails due to invalid FTS_DOC_ID (Error 182 and 1030) |
107329 | 2022-05-18 11:59 | 2022-05-20 6:15 | MySQL Server: FULLTEXT search | Verified (702 days) | S3 | 8.0.29 | Linux | Any | Fulltext search returns different results based on execution plan |
35933 | 2008-04-09 11:03 | 2018-09-09 20:45 | MySQL Server: FULLTEXT search | Verified (5853 days) | S3 | 5.0.51a, 5.0 BK | Linux (debian, x86, 32bit) | Any | spurious select ERROR 1191 when insert into ... select * is done on fulltext tab |
67991 | 2012-12-29 22:10 | 2012-12-30 6:34 | MySQL Server: FULLTEXT search | Verified (4128 days) | S2 | 5.5 | Linux (Ubuntu) | Any | Server crash due to bad "ft_stopword_file" |
70240 | 2013-09-04 11:37 | 2014-03-13 9:00 | MySQL Server: FULLTEXT search | Verified (3698 days) | S3 | 5.5.37 | Linux (redhat 7.8) | Any | match against search in hindi |
109885 | 2023-02-01 21:19 | 2023-02-02 8:02 | MySQL Server: FULLTEXT search | Verified (442 days) | S3 | 8.0.23, 8.0.32 | Linux (Docker mysql:8.0.23) | x86 | ALTER TABLE doesn't update use_stopword when dropping & recreating |
110557 | 2023-03-30 3:20 | 2023-11-07 9:03 | MySQL Server: FULLTEXT search | Verified (386 days) | S3 | 8.0.28, 8.0.32 | Linux | Any | When innodb_disable_sort_file_cache=ON, create a full-text index will fail |
36384 | 2008-04-28 20:15 | 2018-09-09 20:45 | MySQL Server: FULLTEXT search | Verified (5834 days) | S1 | 5.0.44-r1, 5.0.58 | Linux (5.0.44-log Gentoo Linux mysql-5.0.44-r1) | Any | Full-Text required (+) operator bug |
75538 | 2015-01-17 19:54 | 2015-01-21 7:27 | MySQL Server: FULLTEXT search | Verified (3376 days) | S2 | 5.7, 5.7.6 | Windows (Windows 8) | Any | Multiple / Single phrase serach using Full Text In InnoDB is not working |
71551 | 2014-02-01 16:02 | 2021-05-25 13:04 | MySQL Server: FULLTEXT search | Verified (3557 days) | S2 | 5.6.15, 5.6.21, 8.0.24 | Windows | Any | ft_boolean_syntax has no impact on InnoDB FTS |
79953 | 2016-01-13 13:31 | 2016-01-14 6:52 | MySQL Server: FULLTEXT search | Verified (3018 days) | S3 | 5.7.10 | Windows (Win 2012R2) | Any | Fulltext-index not found in MySQL 5.7.10 when use GROUP_CONCAT |
84036 | 2016-12-02 6:34 | 2016-12-02 6:57 | MySQL Server: FULLTEXT search | Verified (2695 days) | S3 | 5.7.13, 5.7.16 | Windows | Any | Incorrect result for MyISAM boolean mode fulltext query with negated phrase |
82330 | 2016-07-25 5:55 | 2024-04-06 9:15 | MySQL Server: FULLTEXT search | Verified (13 days) | S1 | 5.7.13, 5.7.22, 8.0.16, 8.3.0 | CentOS (6.6) | Any | Don't recursively-evaluate stopword after tokenize |
103920 | 2021-06-06 9:52 | 2021-06-07 14:51 | MySQL Server: FULLTEXT search | Verified (1047 days) | S3 | 8.0, 8.0.25, 5.7.34 | CentOS | Any | memory recycle improve in fts query |
80579 | 2016-03-02 5:58 | 2016-03-02 6:33 | MySQL Server: FULLTEXT search | Verified (2970 days) | S3 | 5.6.29, 5.7.11 | CentOS | Any | Failing assertion: result != FTS_INVALID in file fts0fts.cc line 2209 |
78643 | 2015-09-30 10:44 | 2015-09-30 11:05 | MySQL Server: FULLTEXT search | Verified (3124 days) | S3 | 5.6.26, 5.6.28, 5.7.10 | CentOS (CentOS 7) | Any | InnoDB: Failing assertion: val <= 4294967295u in fts0vlc.ic line 96 |
92240 | 2018-08-30 4:01 | 2018-08-30 6:43 | MySQL Server: FULLTEXT search | Verified (2059 days) | S2 | 5.7, 5.7.23, 8.0.12, 5.6.41 | Fedora | x86 | when i recreate full text composite index , i could not less result. |
107201 | 2022-05-03 18:13 | 2022-05-04 5:52 | MySQL Server: FULLTEXT search | Verified (716 days) | S2 | 8.0.29 | Ubuntu | x86 | Result of fulltext match is on the wrong row with GROUP BY (reproducible) |
102833 | 2021-03-05 18:04 | 2021-03-05 20:25 | MySQL Server: FULLTEXT search | Verified (1141 days) | S1 | 5.7.33 | Ubuntu | x86 | Fulltext index error [ERROR] InnoDB: Duplicate FTS_DOC_ID value on table |
« Show Previous 30 Entries | Showing 31-60 of 64 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |