Showing all 22 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
80723 | 2016-03-14 8:40 | 2022-11-03 12:29 | MySQL Server: FULLTEXT search | Verified (3131 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 |
82330 | 2016-07-25 5:55 | 2024-10-25 21:15 | MySQL Server: FULLTEXT search | Verified (210 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 |
107364 | 2022-05-22 15:32 | 2022-05-23 14:02 | MySQL Server: DML | Verified (894 days) | S2 | 8.0.29 | Any (Docker(mysql:latest)) | Any | using "OR EXISTS" and "SELECT...MATCH" shows less records than expected |
95006 | 2019-04-12 10:37 | 2019-04-12 12:26 | MySQL Server: InnoDB storage engine | Verified (2031 days) | S3 | 5.7.24, 5.7.25 | Linux | Any | Multiple FULLTEXT indexes become broken after mysql_upgrade (5.7.21 -> 5.7.24) |
86036 | 2017-04-21 10:08 | 2018-11-13 7:55 | MySQL Server: InnoDB storage engine | Verified (2750 days) | S3 | 5.7/8.0 | Any | Any | InnoDB FULLTEXT index has too strict innodb_ft_result_cache_limit max limit |
92230 | 2018-08-29 14:42 | 2018-10-09 14:18 | MySQL Server: FULLTEXT search | Verified (2216 days) | S3 | 5.7/8.0 | Any (RDS Aurora) | Any | Fulltext search returns unexpected results |
87182 | 2017-07-25 8:27 | 2017-07-31 12:44 | MySQL Server: FULLTEXT search | Verified (2651 days) | S3 | 5.6.35 | Any | Any | Sporadic MATCH AGAINST results with unique index |
86460 | 2017-05-25 14:19 | 2017-06-14 3:38 | MySQL Server: InnoDB storage engine | Verified (2712 days) | S3 | 5.6 5.7 | Any | Any | Deleted DOCID are not maintained during OPTIMIZE of InnoDB FULLTEXT tables |
83776 | 2016-11-10 20:42 | 2016-11-11 18:51 | MySQL Server: FULLTEXT search | Verified (2913 days) | S3 | 5.6/5.7/8.0 | Any | Any | InnoDB FULLTEXT search returns incorrect result for operators on ignored words |
84158 | 2016-12-11 12:15 | 2017-09-26 12:28 | MySQL Server: mysqldump Command-line Client | Verified (2882 days) | S3 | 8.0.0, 5.7.16 | Any | Any | Loading table with fulltext from mysqldump fails |
83397 | 2016-10-16 10:58 | 2016-10-17 6:58 | MySQL Server: FULLTEXT search | Verified (2938 days) | S3 | 5.7.15, 5.7.16 | Any | Any | INSERT INTO ... SELECT FROM ... fails if source has > 65535 rows on FTS |
35933 | 2008-04-09 11:03 | 2018-09-09 20:45 | MySQL Server: FULLTEXT search | Verified (6050 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 |
76210 | 2015-03-07 21:58 | 2015-03-09 9:07 | MySQL Server: FULLTEXT search | Verified (3526 days) | S2 | 5.6.22, 5.6.25, 5.7.7 | Any | Any | InnoDB FULLTEXT index returns wrong results for key/value pair documents |
79953 | 2016-01-13 13:31 | 2016-01-14 6:52 | MySQL Server: FULLTEXT search | Verified (3215 days) | S3 | 5.7.10 | Windows (Win 2012R2) | Any | Fulltext-index not found in MySQL 5.7.10 when use GROUP_CONCAT |
76121 | 2015-03-03 10:47 | 2015-03-03 12:50 | MySQL Server: InnoDB storage engine | Verified (3532 days) | S3 | 5.6.23, 5.6.24 | Linux (CentOS 6.5) | Any | Warning 1235, "FTS auxiliary tables will not be flushed" is printed twice. |
78485 | 2015-09-19 10:12 | 2019-10-30 17:31 | MySQL Server: FULLTEXT search | Verified (3332 days) | S3 | 5.6/5.7 | Ubuntu | Any | Fulltext search with char * produces a syntax error with InnoDB |
75451 | 2015-01-08 17:58 | 2015-02-18 11:11 | MySQL Server: InnoDB storage engine | Verified (3585 days) | S3 | 5.6, 5.6.24, 5.7.6 | Any | Any | Cannot use a table containing special chars for InnoDB stopwords |
75763 | 2015-02-04 13:29 | 2015-02-05 8:19 | MySQL Server: FULLTEXT search | Verified (3558 days) | S2 | 5.6.21, 5.6.24 | Any | Any | InnoDB FULLTEXT index reduces insert performance by up to 6x on JSON docs |
72532 | 2014-05-04 19:26 | 2014-05-05 8:42 | MySQL Server: Optimizer | Verified (3834 days) | S3 | 5.6.12, 5.6.19 | Any | Any | DESCRIBE with FULLTEXT does Key=MUL incorrectly |
69491 | 2013-06-17 12:16 | 2013-06-18 7:01 | MySQL Server: Replication | Verified (4155 days) | S2 | 5.1 and 5.5 | Linux (debian) | Any | Breaking replication with update on fulltext |
63718 | 2011-12-11 18:45 | 2011-12-14 10:30 | MySQL Server: Options | Verified (4709 days) | S3 | 5.1.41, 5.1.61 | Any | Any | Unable to increase ft_max_word_len variable |
44397 | 2009-04-22 2:46 | 2012-05-18 20:19 | MySQL Server: FULLTEXT search | Verified (5673 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 |
Showing all 22 (Edit, Save, CSV, Feed) |