Skip to content

Avoid error logging on bad SQL parameter values#7233

Merged
labkey-jeckels merged 1 commit intorelease25.11-SNAPSHOTfrom
25.11_fb_sqlParameterLogging
Dec 4, 2025
Merged

Avoid error logging on bad SQL parameter values#7233
labkey-jeckels merged 1 commit intorelease25.11-SNAPSHOTfrom
25.11_fb_sqlParameterLogging

Conversation

@labkey-jeckels
Copy link
Contributor

@labkey-jeckels labkey-jeckels commented Dec 1, 2025

Rationale

We don't want to spam the log or mothership with exceptions caused by bad SQL parameter values.

Changes

  • Throw a specific subclass
  • Propagate exception decorations through SQL exception translation
  • Minor cleanup

Tasks 📍

@labkey-jeckels
Copy link
Contributor Author

@labkey-matthewb see what you think. I'm open to other approaches.

Copy link
Contributor

@labkey-matthewb labkey-matthewb left a comment

Choose a reason for hiding this comment

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

Seem generally fine. My only observation is that the name of the class SQLGenerationException() sounds more like a LabKey problem than a user/caller problem. Then again the specific class SQLParameterException make sense.

Copy link
Member

@labkey-tchad labkey-tchad left a comment

Choose a reason for hiding this comment

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

Manual testing complete: ✅

@labkey-jeckels labkey-jeckels merged commit 1f7f37b into release25.11-SNAPSHOT Dec 4, 2025
11 of 12 checks passed
@labkey-jeckels labkey-jeckels deleted the 25.11_fb_sqlParameterLogging branch December 4, 2025 21:27
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.

3 participants