perf: avoid per-row snapshot hash tuple copy

[TonisOrmisson]

Summary

• Use SQLAlchemy Row slicing directly in the normative relation-snapshot hash loop.
• Remove one redundant tuple(row) allocation per streamed case row.
• Preserve all snapshot hash calls, typed binary64/NULL/string encoding, execution atomicity, and public outputs.

Evidence

Fresh disposable SQLite execution workload, Python 3.13.2 / SQLite 3.47.1, five repetitions per size:

parent/output rows	baseline median	candidate median	change
50,000	1.707318 s	1.588952 s	-6.9% / 1.07x
100,000	3.465342 s	3.118572 s	-10.0% / 1.11x

Relation-hash call count stayed at 3. A 10,000-row fidelity comparison produced identical content_hash and input_hash values.

Checks

• 414 passed, 9 skipped, 53 deselected
• git diff --check
• Local read-only review: no findings

No public API, dependency, dataset identity, or persistence model changes.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[coderabbitai]

Warning

Review limit reached

Next included review available in 4 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 864f09f7-1699-418a-8b74-2bfbcb43564c

📥 Commits

Reviewing files that changed from the base of the PR and between abdbd91 and 0d14767.

📒 Files selected for processing (1)

• src/openstatspec/sql/workflow.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}