Fixed handling of BigDecimal data type#710
Merged
Merged
Conversation
dstenger
added
bug
dstenger
added a commit
to lat-lon/deegree3
that referenced
this pull request
Aug 25, 2025
dstenger
added a commit
that referenced
this pull request
Aug 25, 2025
dstenger
added a commit
to lat-lon/deegree3
that referenced
this pull request
Aug 26, 2025
dstenger
added a commit
to lat-lon/deegree3
that referenced
this pull request
Aug 26, 2025
latlon-team
pushed a commit
to lat-lon/deegree3
that referenced
this pull request
Sep 4, 2025
latlon-team
pushed a commit
to lat-lon/deegree3
that referenced
this pull request
Sep 4, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Previously, the handling of BigDecimal data type was not correct in deegree as exponents could be returned in a GML response. For example, following property value is possible in a GetFeature response: "5.4578635E+10".
This pull request fixes that BigDecimal are always exported as plain text (without exponent).