GH-44273: [C++][Decimal] Use 0E+1 not 0.E+1 for broader compatibility #44275
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.
Rationale for this change
Most environments such as Python, Node.js, PostgreSQL and MySQL accepts
0.E+1
but some environments such as Ruby don't accept0.E+1
. More environments accept0.0E+1
or0E+1
than0.E+1
.What changes are included in this PR?
Use
0E+1
not0.E+1
for broader compatibility.Are these changes tested?
Yes.
Are there any user-facing changes?
Yes.
0E+1
not0.E+1
for broader compatibility #44273