feat(api): add .as_scalar()
method for turning expressions into scalar subqueries
#8350
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.
Since there is no safe way to determine whether a table or a column contains a single cell we need to provide a way for the users to inform ibis that it should treat an expression as a scalar subquery. Previously it was the
.to_array()
method, but it only worked for table expressions.Note that when a scalar reduction is passed to certain API methods ibis is able to infer that the value should be turned into a scalar subquery and it implicitly does it. Using this method can be omitted in those cases.