Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unclear error message when calling a function with no parameters. #10915

Closed
jeffreyssmith2nd opened this issue Jun 14, 2024 · 0 comments · Fixed by #10916
Closed

Unclear error message when calling a function with no parameters. #10915

jeffreyssmith2nd opened this issue Jun 14, 2024 · 0 comments · Fixed by #10916
Labels
enhancement New feature or request

Comments

@jeffreyssmith2nd
Copy link
Contributor

Is your feature request related to a problem or challenge?

The changes in #10651 lead to a change in the error messages given when a function is called without any arguments. I think it can be made a little clearer to the user what actually went wrong.

The current error message in main:

"Error during planning: Error during planning: [data_types_with_aggregate_udf] Coercion from [] to the signature VariadicAny failed. and No function matches the given name and argument types 'selector_last()'. You might need to add explicit type casts.\n\tCandidate functions:\n\tselector_last(Any, .., Any)"

Describe the solution you'd like

An error that displays to the user that they called a function that requires arguments without providing any. One example could be:

"Error during planning: Error during planning: SUM does not support zero arguments. No function matches the given name and argument types 'SUM()'. You might need to add explicit type casts.\n\tCandidate functions:\n\tSUM(UserDefine
d)"

Describe alternatives you've considered

No response

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant