Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

fix: check rows.Err() after iteration in Each to surface mid-stream errors

Unlike OneFromRows and AllFromRows, Each never consulted rows.Err()
after its for rows.Next() loop exited. If Next() returns false due to
a database error (network disconnect, context deadline, SQL error from
a function mid-result-set), the error was silently dropped and the
caller's range loop completed as if everything was fine.

pgx's own ForEachRow, CollectRows, AppendRows, and the database/sql
docs all follow the same pattern: check Err() after the loop. This
fix brings Each in line.