Invalidating query cache entries key mysql

How do you guys plan on achieving such a (laudable) goal without bringing about the kind of baggage that stereotypically has come with it?

FWIW, I suspect the strictness changes you mentioned will go a long way towards addressing that, but I'm curious if there's more you have in mind. Apologies if I've set up a bit of a straw man in my last paragraph.

Having said that, I think expectations on what is the minimal functionality have evolved, and we have responded by adding functionality like JSON in My SQL 5.7, and CTEs and Window Functions in 8.0.

In terms of the specific issues you raise:* utf8 vs utf8mb4 is "problem #1"

Then, since slave contained more data, we started backing up the slave.

This model pulls people toward alternative databases such as Cassandra, Mongo DB, etc.

I'm trying to predict what your answer to the prior paragraph might be and pose additional questions based on that answer to avoid an extra round-trip.

I want to start by saying that gripes/land mines don't help anyone.

The CRUD API has overlap with Document Stores like Mongo DB, but the X Protocol really goes beyond that.

There are plans to continue developing the X Protocol. I'm thrilled to hear that My SQL is taking strictness much more seriously with the above-mentioned strategies.