> In addition, the query plan always contains FirstMatch regardless of whether the firstmatch switch is on or off.
This is expected, When LooseScan strategy is taking care of removing duplicates produced by a multi-table subquery, one can see EXPLAIN outputs like this:
> In addition, the query plan always contains FirstMatch regardless of whether the firstmatch switch is on or off.
This is expected, When LooseScan strategy is taking care of removing duplicates produced by a multi-table subquery, one can see EXPLAIN outputs like this:
table_x LooseScan
...
table_y FirstMatch(table_x)