We recognize certain specific patterns involving array parameters and translate these (see docs); but the list is limited.

For any other pattern involving an array of scalars, we can simply translate that to a pseudo-table using unnest. At that point, the regular EF query pipeline should kick in and allow us to translate anything EF supports, as if it were just another table.

Note that this should only be a fallback; the specialized translations should take precedence as they're better and probably more efficient.

PS Pay special attention to the ordering guarantees of the rowset coming out of unnest; we probably need to add an ORDER BY to preserve it.