OpenFileGDB writer: fix corrupted maximum blob size header field in some SetFeature() scenarios (fixes #9388) #9400
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.
When SetFeature() involves generating a row whose blob size is larger than the maximum one in the file, the file header was no properly refreshed. This didn't cause issues to the OpenFileGDB driver, which is robust to that, but ESRI based readers, like ArcMap or the FileGDB SDK, were unable to read such features.