Query for retrieving managed metadata column where the column values are a subset of a list of values

Question

In CAML, if I have a managed metadata column with multiple values, you can determine if one of a list of values is in the column using the following query (where the order of the Values/FieldRef elements does not matter):

<Where>
    <In>
          <Values><Value Type="Integer">2</Value><Value Type="Integer">8</Value></Values>
          <FieldRef LookupId="True" Name="Managed" />          
    </In>
</Where>

This will return true for a document which has terms 2 and 7 contained within it, because one of the values (2) is in the managed metadata column.

Is there a way to flip that around and say that all of the field values from the Managed Metadata column must be in the given list of values? i.e. if the Managed Metadata column has terms 2 and 7, something similar to the above would return false, because the list of values does not contain 2 AND 7. If the values were 2, 7, 10, that would return true, because the list of values does contain all of the terms in the column.

Answer 1

Not at a box but I think it is since what you are asking for is multiple subqueries, I would write it in SQL or LINQ and get the CAML that way. At a guess it will look something similar too:

<Where>
    <And>
      <In>
         ... Value 1 lookup
      </In>
      <In>
         ... Value 2 lookup
      </In>
    </And>
 </Where>

Answer 2

I have come up with one way to do what I want. If the managed terms have ids 1 through 5, and my list of values is 2, 3, then I can construct a query like:

<Where>
    <And>
        <Neq><FieldRef LookupId="True" Name="Managed"/><Value Type="Integer">1</Value></Neq>
        <And>
           <Neq><FieldRef LookupId="True" Name="Managed"/><Value Type="Integer">4</Value></Neq>
           <Neq><FieldRef LookupId="True" Name="Managed"/><Value Type="Integer">5</Value></Neq>
        </And>
    </And>
</Where>

This will get cumbersome when there's 50 terms and I want to query on 2 of them, so I'm still interested if there's a better way, although it does look like you can get into several hundred conditions before CAML starts having issues.