-
-
Notifications
You must be signed in to change notification settings - Fork 2
refactor(db): add transaction argument #245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
to: - check - get_data - o_get_data
Reviewer's GuideThis PR refactors key database helper functions in db.py to support optional transactions, simplifies the stored‐procedure flag check and output-parameter retrieval logic, and updates project URLs and changelog version formatting. Sequence diagram for refactored
|
| Change | Details | Files |
|---|---|---|
| Add optional transaction support to stored procedure wrapper functions |
|
src/incendium/db.py |
| Refactor check and get_output_params implementations |
|
src/incendium/db.py |
| Update project metadata and changelog formatting |
|
CHANGELOG.mdsrc/incendium/__about__.pysrc/incendium/__init__.py |
Tips and commands
Interacting with Sourcery
- Trigger a new review: Comment
@sourcery-ai reviewon the pull request. - Continue discussions: Reply directly to Sourcery's review comments.
- Generate a GitHub issue from a review comment: Ask Sourcery to create an
issue from a review comment by replying to it. You can also reply to a
review comment with@sourcery-ai issueto create an issue from it. - Generate a pull request title: Write
@sourcery-aianywhere in the pull
request title to generate a title at any time. You can also comment
@sourcery-ai titleon the pull request to (re-)generate the title at any time. - Generate a pull request summary: Write
@sourcery-ai summaryanywhere in
the pull request body to generate a PR summary at any time exactly where you
want it. You can also comment@sourcery-ai summaryon the pull request to
(re-)generate the summary at any time. - Generate reviewer's guide: Comment
@sourcery-ai guideon the pull
request to (re-)generate the reviewer's guide at any time. - Resolve all Sourcery comments: Comment
@sourcery-ai resolveon the
pull request to resolve all Sourcery comments. Useful if you've already
addressed all the comments and don't want to see them anymore. - Dismiss all Sourcery reviews: Comment
@sourcery-ai dismisson the pull
request to dismiss all existing Sourcery reviews. Especially useful if you
want to start fresh with a new review - don't forget to comment
@sourcery-ai reviewto trigger a new review!
Customizing Your Experience
Access your dashboard to:
- Enable or disable review features such as the Sourcery-generated pull request
summary, the reviewer's guide, and others. - Change the review language.
- Add, remove or edit custom review instructions.
- Adjust other review settings.
Getting Help
- Contact our support team for questions or feedback.
- Visit our documentation for detailed guides and information.
- Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @cesarcoatl - I've reviewed your changes - here's some feedback:
- Replace usage of iterkeys() in check() with standard dict membership (e.g.,
if 'flag' in result['output_params']) for Python 3 compatibility. - Consider having check() call get_output_params() internally instead of duplicating the _execute_sp invocation to reduce code duplication and keep output-param handling consistent.
Here's what I looked at during the review
- 🟡 General issues: 1 issue found
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
| stored_procedure, output=[output], database=database, params=params | ||
| return ( | ||
| result["output_params"]["flag"] | ||
| if "flag" in result["output_params"].iterkeys() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
issue: Avoid using iterkeys(), use direct membership or keys()
In Python 3, use '"flag" in result["output_params"]' or 'result["output_params"].keys()' for compatibility and clarity.
to:
Summary by Sourcery
Introduce transaction support across database utility functions, streamline output parameter handling, and update project metadata and CHANGELOG formatting.
Enhancements:
Documentation:
Chores: