Build: #561 was successful Changes by Marc

Stages & jobs

  1. Default Stage

Build result summary

Details

Completed
Duration
27 minutes
Labels
None
Revision
5526ddeeaf858fef9447f47eb86b8e991b4ecb81 5526ddeeaf858fef9447f47eb86b8e991b4ecb81
Total tests
7151
Successful since
#528 ()

Tests

Code commits

Author Commit Message Commit date
Marc Marc 5526ddeeaf858fef9447f47eb86b8e991b4ecb81 5526ddeeaf858fef9447f47eb86b8e991b4ecb81 Merge branch '3.3.x'
Marc Marc 31192fc08e2cc12efa0a59a2edb9128ed806d3db m 31192fc08e2cc12efa0a59a2edb9128ed806d3db Merge branch '3.2.x' into 3.3.x
Marc Marc 79bcb20ac53ab76e6a3590651a6598e95b64e25f m 79bcb20ac53ab76e6a3590651a6598e95b64e25f Merge pull request #5626 from cpeel/ticket/16096
[ticket/16096] Use InnoDB fulltext limits for InnoDB tables
Casey Peel <cpeel@users.noreply.github.com> Casey Peel <cpeel@users.noreply.github.com> e33e5727413543c74b3ede43ad437bb261c72839 m e33e5727413543c74b3ede43ad437bb261c72839 [ticket/16096] Use InnoDB fulltext limits for InnoDB tables
The max and min search length for the MySQL database vary based on the
engine for the underlying table. For MyISAM tables, the variables are
ft_max_word_len and ft_min_word_len, but for InnoDB tables the
variables are innodb_ft_max_token_size and innodb_ft_min_token_size.

Take the posts table type into account when setting the max and min
search length.

PHPBB3-16096

Jira issues

IssueDescriptionStatus
Unknown Issue TypePHPBB3-16096Could not obtain issue details from Jira