Skip to content

Commit

Permalink
Try 8MB large data (innodb redo log file size dependent).
Browse files Browse the repository at this point in the history
  • Loading branch information
gitlost committed Oct 13, 2017
1 parent 98fd965 commit 44b9d79
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions features/db-search.feature
Original file line number Diff line number Diff line change
Expand Up @@ -974,8 +974,8 @@ Feature: Search through the database
Scenario: Search with large data
Given a WP install
# Note "_utf8 X'CC88'" is combining umlaut. Doing it this way as non-ASCII stuff gets stripped due to (eventually) been put thru `escapeshellarg()` with a default C locale.
# Also restricted by MySQL's default `max_allowed_packet` size to 16 MB - 1 (0xFFFFFF).
And I run `wp db query "INSERT INTO wp_options (option_name, option_value) VALUES ('opt_large', CONCAT(REPEAT('a', 1024 * 1024 * 16 - 9), 'o', _utf8 X'CC88', 'XYXYX'));"`
# Also restricted by default MySQL values for the version-dependent size of the innodb redo log file (max 10% one transaction) and `max_allowed_packet` size (16MB).
And I run `wp db query "INSERT INTO wp_options (option_name, option_value) VALUES ('opt_large', CONCAT(REPEAT('a', 1024 * 1024 * 8 - 9), 'o', _utf8 X'CC88', 'XYXYX'));"`

When I run `wp db search XYXYX --before_context=1 --stats`
Then STDOUT should contain:
Expand Down

0 comments on commit 44b9d79

Please sign in to comment.