Fix queries on JSON fields #1987
Merged
Conversation
This file contains 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
DavideD
force-pushed
the
1984-BigDecimal
branch
2 times, most recently
from
4cd00b7 to
4c1c1f6
Compare
DavideD
changed the title
DavideD
force-pushed
the
1984-BigDecimal
branch
2 times, most recently
from
c27aa38 to
c505102
Compare
This information is now available and it's required when working with JSON.
It confirms that queries on entities with regular BigDecimal fields are working.
DavideD
force-pushed
the
1984-BigDecimal
branch
3 times, most recently
from
d7ec199 to
c67f2aa
Compare
DavideD
force-pushed
the
1984-BigDecimal
branch
from
c67f2aa to
8616020
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix #1984