I ran into an old MySQL limitation while experimenting with subqueries and wanted to document it because it can be confusing when you first hit it.
Using the sample world database, this kind of query worked:
| |
But when I tried to use that same pattern inside a DELETE ... WHERE Name IN (...) statement:
| |
MySQL responded with:
| |
At the time, the practical fallback was to resolve the values first and then run a query like:
| |
It was a small issue, but one worth remembering if you are working with older MySQL behavior or trying to understand why a query structure that seems reasonable still fails.