We've discovered some issues due to joins which don't scale well with large numbers of records.

The one which we discovered this with is assign and it's because the query planner in some engines doesn't deal well with joins where the filter is only in the WHERE (when it should be on the JOIN).

Thankfully this only effects providers, and only those which do complex joins, and thankfully these are mostly extremely well unit tested now.