Skip to content

fix(db): correct inverted return value in putsetting#530

Closed
somethingwithproof wants to merge 1 commit intoCacti:developfrom
somethingwithproof:fix/putsetting-return
Closed

fix(db): correct inverted return value in putsetting#530
somethingwithproof wants to merge 1 commit intoCacti:developfrom
somethingwithproof:fix/putsetting-return

Conversation

@somethingwithproof
Copy link
Copy Markdown
Contributor

db_insert returns TRUE on success and FALSE on failure. putsetting checked 'result == 0' and returned TRUE, inverting the semantics. Callers received success on insert failure.

Signed-off-by: Thomas Vincent <thomasvincent@gmail.com>
Copilot AI review requested due to automatic review settings April 8, 2026 19:31
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Fixes putsetting() to propagate db_insert()’s boolean return value correctly so callers no longer receive a success result when the insert fails.

Changes:

  • Remove inverted result == 0 check in putsetting().
  • Return db_insert()’s TRUE/FALSE result directly from putsetting().

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@somethingwithproof
Copy link
Copy Markdown
Contributor Author

Code-reviewed as part of a batch with #525-#531. These 7 atomic bug fixes are independent of each other and can be merged in any order; recommend bundling into a single dated release. The Windows/CMake work in #523/#524 should follow this batch, and #512 (production CI pipeline) should be split into smaller PRs before review.

@somethingwithproof
Copy link
Copy Markdown
Contributor Author

Superseded by #523 after consolidation to reduce overlap and merge conflicts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants