stephenafamo / scan

90%

main: 91%

LAST BUILD ON BRANCH fix/each-rows-err-check

branch: fix/each-rows-err-check

CHANGE BRANCH

x

Reset

• fix/each-rows-err-check
• fix/close-rows-in-fromrows
• main
• perf/reuse-row-scan-buffers
• perf/schedule-scan-by-index
• refs/tags/v0.1.0
• refs/tags/v0.1.1
• refs/tags/v0.2.0
• refs/tags/v0.3.0
• refs/tags/v0.4.0
• refs/tags/v0.4.1
• refs/tags/v0.4.2
• refs/tags/v0.5.0
• refs/tags/v0.6.0
• refs/tags/v0.6.1
• refs/tags/v0.6.2
• refs/tags/v0.7.0
• refs/tags/v0.8.0
• refs/tags/v0.9.0
• revert-3-named-args-v2
• scan-plan-once
• scan-rowskip

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.