[release/8.0] Handle complex types in GetDatabaseValues #32894
Merged
Conversation
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
AndriySvyryd
approved these changes
Jan 23, 2024
|
Note that the branch is currently closed. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Port of #32813
Fixes #32701
Fixes #31353
Description
Code to refresh the database values was not updated to account for complex types.
Customer impact
Attempting to get database values for an entity with a complex type throws an exception.
How found
Customer reported on 8.
Regression
No. Complex types is a major new feature in 8.
Testing
Testing was missed because the tests for this API that access the database live in a different location than the other tests that were updated. Tests now added.
Risk
Low. Quirked.