fix: adding missing whitespaces in SQL queries#4147
Open
fix: adding missing whitespaces in SQL queries#4147
Conversation
There are missing whitespaces in some of the queries which make triggers errors when running against a PostgreSQL 17 database. Apparently due to a more stringent SQL parsing in that version. The following error in the DB logs was corrected by the changes at the time of associating a user to an organization: ```console ERROR: trailing junk after parameter at or near "$3WHERE" at character 62 STATEMENT: UPDATE groups SET last_updated_by= $1, updated_at= $2, name= $3WHERE| id= ``` Signed-off-by: Mauro Oddi <mauro.oddi@progress.com>
👷 Deploy Preview for chef-server processing.
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
There are missing whitespaces in some of the queries which make Chef Server trigger errors when running against a PostgreSQL 17 database. Apparently due to a more stringent SQL parsing in that version.
Issues Resolved
The following error in the DB logs was corrected by the changes at the time of associating a user to an organization:
Check List