Replacing Len function with DATALENGTH function #5025
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
"CONSTRAINT CHK_TokenSearchParam_CodeOverflow CHECK (LEN(Code) = 256 OR CodeOverflow IS NULL)" is failing while inserting data.
Code value that is greater than 256 characters and has empty spaces at the end when we split it into Code and CodeOverFlow causes the issue.
CHECK (LEN(Code) = 256 - SQL LEN function returns length of the value removing trailing blanks.
This PR has changes to replace LEN function with DATALENGH to get correct bytes stored.
Related issues
Addresses [issue #158203].
Testing
Manually verified the scenario by testing with same data that is breaking before the change
Existing unit and E2E tests
FHIR Team Checklist
Semver Change (docs)
Patch|Skip|Feature|Breaking (reason)