Support named tuples as return values #1
Merged
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.
So, to be frank, this PR adds the ability to define tuples for DB models beforehand and use them as return types: consider the following example:
selectUserById
has return type annotated asUser
. It wasn't possible before becauseimportdb
expected onlyint
as identifier there, so the user had no choice but to copy and paste the whole tuple definition.Now by contrast it can be any identifier which is either
int
or evaluates totuple[...]
type.It is achieved by making
body
parameter inimportdb
be typed, so that compiler binds type annotations for the proc, which we can get implementation of later.I ran the tests with creating tables, inserting, selecting and updating data. All work as intended, should be backwards compatible, I guess.