Support SQL Select and Explain actions for Postgres JSON fields. #1229
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
tim-schilling
force-pushed
the
postgres-json-explain
branch
from
431b795
to
4aa0300
Compare
Codecov Report
@@ Coverage Diff @@
## master #1229 +/- ##
==========================================
+ Coverage 86.41% 86.47% +0.05%
==========================================
Files 25 25
Lines 1428 1434 +6
Branches 204 205 +1
==========================================
+ Hits 1234 1240 +6
Misses 141 141
Partials 53 53
Continue to review full report at Codecov.
|
tim-schilling
force-pushed
the
postgres-json-explain
branch
from
4aa0300
to
ab5c53e
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.
Closes #1133
I'm not sure of a good way to dynamically import the postgres members. I'm definitely open to other methods.