Skip to content

Fix DB privilege check for database names containing _ or %#5522

Closed
leeclemens wants to merge 1 commit into
Icinga:mainfrom
leeclemens:fix/db-privilege-check-underscore-dbname-5521
Closed

Fix DB privilege check for database names containing _ or %#5522
leeclemens wants to merge 1 commit into
Icinga:mainfrom
leeclemens:fix/db-privilege-check-underscore-dbname-5521

Conversation

@leeclemens

Copy link
Copy Markdown
Contributor

Fixes the DB privilege check failing for database names with _ or %. The schema_privileges queries escaped the db name (_ → _) before an = comparison — escaping only works with LIKE, so it
never matched. Bind the raw name instead, consistent with the table_privileges query right below.

refs #5521

@cla-bot

cla-bot Bot commented Jun 14, 2026

Copy link
Copy Markdown

Thank you for your pull request. Before we can look at it, you'll need to sign a Contributor License Agreement (CLA).

Please follow instructions at https://icinga.com/company/contributor-agreement to sign the CLA.

After that, please reply here with a comment and we'll verify.

Contributors that have not signed yet: @leeclemens

Details
  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Please contact us if you think this is the case.

  • If you signed the CLA as a corporation, your GitHub username may not have been submitted to us. Please reach out to the responsible person in your organization.

@leeclemens

Copy link
Copy Markdown
Contributor Author

Signed, not sure which option to click on the generic Contact Us page.

@leeclemens leeclemens closed this Jun 15, 2026
@leeclemens leeclemens deleted the fix/db-privilege-check-underscore-dbname-5521 branch June 15, 2026 17:22
@bobapple

Copy link
Copy Markdown
Member

@cla-bot check

@cla-bot cla-bot Bot added the cla/signed label Jun 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants