Imagine we had this in ores_model
and we have two scores for each model for every revision:
In this case we would have two rows in user contribs or changes list query because we do LEFT JOIN on ores_model (using other types will lead to omitting cases when we don't have score which not desirable).
So I solved it by explicitly adding a where condition that oresm_is_current != 0.
It will all cases except when the oresc_model id doesn't exist in ores_model (which can happen due to T144195: Check model version replaces every time it runs.) but hopefully we won't see it again since the patch got merged.