Is it possible to get posts with custom taxonomy, targeting a specific tax meta value... in one wp_query?

The meta_query par targets the CPT's meta values, not the tax meta...

So essentially, what I want is the option to target meta values within the tax_query par.

@ChristineCooper I don't think so, unless you set pass the result of get_terms() to the tax_query while setting the fields argument to ids.

  $args = [
    'post_type' => 'post',
    'tax_query' => [
      [
        'taxonomy' => 'my_tax',
        'field'    => 'term_id',
        'terms'    => get_terms(
          [
            'taxonomy'   => 'my_tax',
            'fields'     => 'ids',
            'meta_query' => [
              [
                'key'     => 'some_key',
                'value'   => 'some_value',
                'compare' => '='
              ]
            ]
          ]
        ),
      ],
    ],
  ];

Something like this, which I'm sure you thought of it. But can't imagine the low performance of nested meta queries.

are you sure that's even possible?

keep in mind that if it is, then it's a truly earth shatteringly expensive query

the correct approach would be to do an expensive tax query first separately

Why not possible?

I've never seen it to be possible via WP_Query

but even if it's possible, it's highly undesirable

this suggests that the problem is data storage design

That's probably why no one uses it

if you ever need to get all posts X which have a term Z where Z has term meta Y, something has gone terrible wrong somewhere

But the syntax should be correct.

I never knew that syntax was possible

a post meta query is super expensive, as is a term meta query

to then compound it with another layer makes it orders of magnitude more expensive

I would not expect a shared server to be able to handle that query with 1 active user on 1 page load

assuming 100 posts

Haha

I'd expect either mysql server has gone away, or time execution limit

Well that's OP's problem, I just wrote it to work in 1 query.

but those kinds of queries are hard on the DB server

order it by rand, and throw a not__in whose value comes from a HTTP request and you've got the absolute worst case scenario

You're about to trigger WWIII if you keep adding stuff to the query.

eitherway, if you need to find posts in a term that has X, then X should have been a term in a taxonomy, not term meta

and don't forget, for those 1 in a million rare circumstances, you can have term taxonomies

where the objects being taxonomised are terms rather than posts

but i have literally never come across a situation that required it

@ChristineCooper Well she mentioned that she wants to target the terms meta

Assuming that she didn't mean taxonomy's meta itself ( do they even have meta by default? )

no

Thanks Jack! I meant the term's meta value. This is way to mental and not at all appropriate for a high trafficked platform. :D

I wonder if that query even works though.

I ended up by storing post ids in custom post meta. Far from ideal structure, but considerably more ideal when considering performance.

End of the day brainscramble: