Walkthrough

A new internal method ensure_connection_open() was added to the Blob struct to centralize connection open state validation. All Blob operations (read, write, tell, seek, enter, exit, subscript, and ass_subscript) now invoke this check, ensuring consistent ProgrammingError propagation when operating on closed connections.

Changes

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

• Verify that ensure_connection_open() is called in all relevant Blob methods
• Confirm that no Blob operations bypass the connection state check
• Validate error handling and ProgrammingError propagation behavior

Possibly related PRs

• fix(sqlite): raise ProgrammingError when operating on a blob with a… #6286: Adds Connection::is_closed() method and applies the check to Blob::read(), forming the foundation this PR builds upon
• Fix sqlite connection reinitialization #6288: Modifies Connection.initialized and reinitialization behavior, affecting the connection state used by blob operations
• stdlib(sqlite): Raise ProgrammingError in closed Blob context manager #6041: Updates Blob.__enter__() and __exit__() to be VM-aware, overlapping with methods now gated by ensure_connection_open()

Suggested reviewers

• youknowone
• ShaharNaveh

Poem

🐰 A blob without a home so bright,
Now checks if doors are locked up tight!
With one small guard to seal the gate,
All operations validate.
No sneaking past a closed connection's might! 🔒

Pre-merge checks and finishing touches

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.

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