fix: if field contains space in constraint expression, checks will fail #3374
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
When adding a constraint to a table, the expression is formatted as:
<FIELD> <CONDITION> <VALUE>
. If - god forbid - a space occurs in a field name, the condition will not evaluate due to the field name not being escaped. During theenforce_check
we are unable to get the field name, and to avoid breaking backward, I am suggesting adding some logic to add backticks to conditions.I am not fan of this solution myself, but I do not have a better solution at the moment.