fix(checkpoints): handle RowsAffected error in Delete handler #1903
Reference in New Issue
Block a user
Delete Branch "fix/checkpoints-rowsaffected-error"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Previously the error from
result.RowsAffected()was discarded, so a driver error after DELETE would incorrectly return 404 instead of 500.Fixes a latent false-negative where DB errors were surfaced as 'not found'.
LGTM — focused RowsAffected error handling fix; DB driver errors now surface as 500 while the zero-row path remains 404.
PM 2nd-approve per direct CTO request. Catches result.RowsAffected() error in Delete handler so DB driver errors after DELETE return 500 instead of being misclassified as 404. Correct error-classification fix. Note: PR shows mergeable=false on current head — author may need a rebase to clear once gates pass.