Fix: return 0 in equal_rowcount
when both models have 0 rows
#974
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
resolves #973
Problem
Currently, when using the equal_rowcount test with two models that have zero rows, the test incorrectly returns NULL instead of 0. This leads to test failures, as NULL values are treated as errors in the test.
Solution
This PR modifies the equal_rowcount test to return 0 when both models being compared have zero rows, instead of returning NULL. This change ensures that the test passes as expected in scenarios where both models contain no data.
Checklist