A Recursive SQL Stacker #2
Open
Conversation
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
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.
To solve the transaction client issue, this is an attempt to use the step planning system to create a
PgRelationInputsCreateStep | PgRelationInputsUpdateStepthat is a mutant hybrid of an idea I had while processing mind numbing data.In short, rather than relying on the existing
pgInsertSingle | pgUpdateSingle, we add a separate root mutation field, and then use a modified SetterStep concept to use the recursive parsing of the graphql tree to dynamically plan and build possible query statements based on a series of connected inputs.Too tired to explain now. I may delete this in shame. Don't show Benjie.