Brad Bell

Was this working before an update and broke after or has it never worked for you? If the prior, do you recall the version you were on before?

@GaryReckard any chance you're getting these results on AWS RDS?

@GaryReckard Trying to narrow some things down. Is this MySQL Aurora, or native MySQL? Serverless or "traditional"? Do you have a cluster setup at all?

Hrm... can you run a `SHOW VARIABLES;` SQL query and share the results over at [email protected] and reference this ticket?

> It's curious to me that two different search approaches are used: WHERE ((keywords LIKE '% law%')) and WHERE (MATCH(keywords) AGAINST('+laws*' IN BOOLEAN MODE)), and the former is SO much...

So the takeaway from your benchmarks is: * `LIKE` queries are consistently fast across all environments * Full-text queries can vary anywhere from 50ms to 21 seconds across environments I...

@GaryReckard Solution 1: I completely forgot we added that property! You'll obviously lose any of the full-text search benefits. Solution 2: Interesting - I wonder if you'd get the same...

@mdoorschodt Sounds like a PHP session issue... is this in a load-balanced web server setup?

@iliaivanov you can also make sure that InnoDB is using the Barracuda file format and turn ROW_FORMAT=COMPRESSED on. More reading here: https://dba.stackexchange.com/questions/6598/innodb-create-table-error-row-size-too-large/6599#6599 and https://dba.stackexchange.com/questions/22441/error-1118-row-size-too-large-utf8-innodb/22463#22463

@brandonkelly "row" is confusing in the error message, since it's referring to row length of a database page (which is used in calculating the maximum length of an index), not...