Add alias support in typehinted queries #45
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
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.
Even when using raw SQL queries with
select().text(), users often want to cast the response values into native TableBase instances or raw field values. Previously we only supported TableBases or Field wrappers being passed intoselect()queries, so there was no way to retrieve a value that wasn't already defined in the python schema.This PR adds support for specifying aliases within the initial select() query. This uses our standard postprocessing layer to convert from SQL value response columns into our native objects, but allows users to specify any query value that appears within the SQL text.