In a recent release we added an all_results column to models which contains all the elements from the manifest for each model.
This caused issues with some DWHs because the records started to exceed limits.
As a workaround we have introduced batching of records in some previous PRs.
However, I think the raw sql is a big part of what is making the records large in the first place and doesn't need to be stored.
In a future commit it might be worth revoking more elements of this field / the field entirely and moving back to parsing out elements and adding new columns.
Overview
all_resultscolumn to models which contains all the elements from the manifest for each model.Update type - breaking / non-breaking
What does this solve?
Outstanding questions
What databases have you tested with?