Stored procedures schema and introspection (Incremental PR - I) #142
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
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.
What
This PR adds introspection and schema support for stored procedures in MSSQL. This PR is the first incremental PR towards adding stored procedures support.
How
Introspection
A database query is made to get all the metadata about stored procedures present in the database. As it is a stored procedure, there is no return type tied to it, so we leave the
returnspart empty and we expect the user to fill in the appropriate schema.Schema
We do schema generation for a stored procedure, only if it has a
returnsassociated with it. Otherwise, we won't be able to generate a graphql schema for the stored procedure.