Showing 1-30 of 63 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
36384 | 2008-04-28 20:15 | 2018-09-09 20:45 | MySQL Server: FULLTEXT search | Verified (5840 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 |
60904 | 2011-04-18 8:10 | 2011-07-17 13:14 | MySQL Server: FULLTEXT search | Verified (4666 days) | S1 | 5.1.49, 5.1.59 | Any | Any | plugin of full text index has a string address error |
82330 | 2016-07-25 5:55 | 2024-04-06 9:15 | MySQL Server: FULLTEXT search | Verified (19 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 |
102833 | 2021-03-05 18:04 | 2021-03-05 20:25 | MySQL Server: FULLTEXT search | Verified (1147 days) | S1 | 5.7.33 | Ubuntu | x86 | Fulltext index error [ERROR] InnoDB: Duplicate FTS_DOC_ID value on table |
106569 | 2022-02-25 7:35 | 2022-02-25 10:25 | MySQL Server: FULLTEXT search | Verified (790 days) | S2 | 8.0.28, 5.7.37 | Any | Any | Full-text search get stuck at "FULLTEXT INITIALIZATION" stage for exact phrases |
88396 | 2017-11-08 4:01 | 2017-11-08 6:34 | MySQL Server: FULLTEXT search | Verified (2360 days) | S2 | 5.7, 5.7.20 | Any | Any | term search and phrase serch in boolean mode with mecab don't work as manual |
88395 | 2017-11-08 3:41 | 2017-11-08 6:23 | MySQL Server: FULLTEXT search | Verified (2360 days) | S2 | 5.7, 5.7.20 | Any | Any | fulltext boolean mode with mecab don't work as manual(builtin parser). |
92240 | 2018-08-30 4:01 | 2018-08-30 6:43 | MySQL Server: FULLTEXT search | Verified (2065 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. |
86164 | 2017-05-03 3:43 | 2017-05-08 11:49 | MySQL Server: FULLTEXT search | Verified (2548 days) | S2 | 5.7.17, 5.7.18 | Any | Any | Fulltext search can not find word which contains punctuation marks |
92705 | 2018-10-08 10:49 | 2018-10-08 17:17 | MySQL Server: FULLTEXT search | Verified (2026 days) | S2 | 5.7.22/8.0 | Ubuntu | x86 | ngram full text search - can't find words smaller than ngram_token_size |
80347 | 2016-02-12 5:02 | 2016-11-08 13:39 | MySQL Server: FULLTEXT search | Verified (2725 days) | S2 | 5.7.9, 5.7.11 | Any | Any | mysqldump backup restore fails due to invalid FTS_DOC_ID (Error 182 and 1030) |
79497 | 2015-12-02 16:41 | 2015-12-02 17:51 | MySQL Server: FULLTEXT search | Verified (3067 days) | S2 | 5.7, 5.6.29, 5.7.11, 5.7.9 | Ubuntu (14.04) | Any | Fulltext index on a given column causes empty set for 'distinct' query |
107201 | 2022-05-03 18:13 | 2022-05-04 5:52 | MySQL Server: FULLTEXT search | Verified (722 days) | S2 | 8.0.29 | Ubuntu | x86 | Result of fulltext match is on the wrong row with GROUP BY (reproducible) |
108509 | 2022-09-16 0:17 | 2022-09-16 5:25 | MySQL Server: FULLTEXT search | Verified (587 days) | S2 | 8.0.21 | Any | Any | Return value of rbt_search() not get checked |
76210 | 2015-03-07 21:58 | 2015-03-09 9:07 | MySQL Server: FULLTEXT search | Verified (3335 days) | S2 | 5.6.22, 5.6.25, 5.7.7 | Any | Any | InnoDB FULLTEXT index returns wrong results for key/value pair documents |
44397 | 2009-04-22 2:46 | 2012-05-18 20:19 | MySQL Server: FULLTEXT search | Verified (5482 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 |
67991 | 2012-12-29 22:10 | 2012-12-30 6:34 | MySQL Server: FULLTEXT search | Verified (4134 days) | S2 | 5.5 | Linux (Ubuntu) | Any | Server crash due to bad "ft_stopword_file" |
71551 | 2014-02-01 16:02 | 2021-05-25 13:04 | MySQL Server: FULLTEXT search | Verified (3563 days) | S2 | 5.6.15, 5.6.21, 8.0.24 | Windows | Any | ft_boolean_syntax has no impact on InnoDB FTS |
75763 | 2015-02-04 13:29 | 2015-02-05 8:19 | MySQL Server: FULLTEXT search | Verified (3367 days) | S2 | 5.6.21, 5.6.24 | Any | Any | InnoDB FULLTEXT index reduces insert performance by up to 6x on JSON docs |
108796 | 2022-10-17 7:42 | 2022-10-17 8:17 | MySQL Server: FULLTEXT search | Verified (556 days) | S2 | 8.0 | Any | Any | Contribution by Tencent: fts query may read unconsistent data |
75538 | 2015-01-17 19:54 | 2015-01-21 7:27 | MySQL Server: FULLTEXT search | Verified (3382 days) | S2 | 5.7, 5.7.6 | Windows (Windows 8) | Any | Multiple / Single phrase serach using Full Text In InnoDB is not working |
95434 | 2019-05-20 21:09 | 2019-05-21 7:53 | MySQL Server: FULLTEXT search | Verified (1801 days) | S3 | Aurora MySQL 5.7.12, 5.6.44, 5.7.26 | Any | Any | Order of terms in boolean mode fulltext search affects the result set |
92142 | 2018-08-23 7:30 | 2022-11-18 23:43 | MySQL Server: FULLTEXT search | Verified (2071 days) | S3 | 5.7.19 and 5.7.21 | Other (AWS RDS) | Other | Having different result set with a full text index on different MySQL versions. |
35933 | 2008-04-09 11:03 | 2018-09-09 20:45 | MySQL Server: FULLTEXT search | Verified (5859 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 |
110976 | 2023-05-10 13:09 | 2024-01-24 9:14 | MySQL Server: FULLTEXT search | Verified (350 days) | S3 | 8.0.33, 5.7.42 | Any | Any | full-text index does not change when ngram parser changed |
92230 | 2018-08-29 14:42 | 2018-10-09 14:18 | MySQL Server: FULLTEXT search | Verified (2025 days) | S3 | 5.7/8.0 | Any (RDS Aurora) | Any | Fulltext search returns unexpected results |
110565 | 2023-03-30 10:52 | 2023-04-17 18:28 | MySQL Server: FULLTEXT search | Verified (374 days) | S3 | 8.0.32 | Any | Any | Adding a fulltext index causes a "Duplicate entry '0'" for the primary key |
110448 | 2023-03-21 4:51 | 2023-03-22 3:14 | MySQL Server: FULLTEXT search | Verified (400 days) | S3 | 8.0.32 | Any | Any | Contribution by Tencent: incorrect result of fulltext search |
93924 | 2019-01-14 17:44 | 2019-01-14 21:53 | MySQL Server: FULLTEXT search | Verified (1928 days) | S3 | 5.6/5.7/8.0 | Any | Any | Fulltext search using words with apostrophe (') does not work on INNODB tables |
94709 | 2019-03-19 19:41 | 2019-03-20 8:01 | MySQL Server: FULLTEXT search | Verified (1863 days) | S3 | 5.7.21,5.7.25, 8.0.15, 5.6.43 | Any | Any | Regression behavior for full text index |
Showing 1-30 of 63 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |