Handle unknown mapping strategies in newer imodels #977
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.
WIP
If we have a newer iModel which has a class with a mapping strategy unknown to the current ECDb runtime, the class will be loaded but, however, if we try to query it, we will end up with an "...unsupported map strategy...class wasn't loaded..." error.
Unlike the class modifier or relationship strength fields, a class's mapping strategy does not get checked when the class gets loaded.
This PR adds a new value to the MapStrategy Enum to handle an unknown strategy.
If we try to query this class, we should get a null view even if we are successful in loading the property map (due to the general uncertainty with an unknown mapping strat).
To-Do: