We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
DataFusion: v41.0.0
I want to be able to write the following query as a prepared statement:
PREPARE get_N_rand_ints_from_last_run(INT) AS SELECT id FROM "test" WHERE run_id = 'foo' ORDER BY random() LIMIT $1
I get the following error message:
Error during planning: Unexpected expression in LIMIT clause
It is impossible, as as it seems that the LIMIT clause supports only constants in it
datafusion/datafusion/sql/src/query.rs
Lines 101 to 114 in ac74cd3
Support using prepared statement arguments in the LIMIT clause
inapplicable
No response
The text was updated successfully, but these errors were encountered:
I think it can be easily supported after #9821
Sorry, something went wrong.
This issue refers to the PR #9815 that was closed due to inactivity; is there any way to make a similar PR?
I think it can be easily supported after #9821 This issue refers to the PR #9815 that was closed due to inactivity; is there any way to make a similar PR?
I plan to work on it in the next few days.
LIMIT
jonahgao
Successfully merging a pull request may close this issue.
Is your feature request related to a problem or challenge?
DataFusion: v41.0.0
I want to be able to write the following query as a prepared statement:
I get the following error message:
It is impossible, as as it seems that the LIMIT clause supports only constants in it
datafusion/datafusion/sql/src/query.rs
Lines 101 to 114 in ac74cd3
Postgres does support using prepared statement's arguments in the LIMIT clause:
Describe the solution you'd like
Support using prepared statement arguments in the LIMIT clause
Describe alternatives you've considered
inapplicable
Additional context
No response
The text was updated successfully, but these errors were encountered: